Hello
I am using ESP32-C3.
I want to implement my own "RainMakerServer" for my ESP32 devices.
Is it possible to get the instructions, or source code of the server?
I commend it, a well thought out system, but I want my own server (MQTT)
Tnx
RainMaker MQTT server
-
- Posts: 307
- Joined: Wed Feb 20, 2019 7:02 am
Re: RainMaker MQTT server
The ESP RainMaker server side code is not open. However, the public deployment will always be free to use for small number of devices. For larger commercial deployments, we have paid options of private deployments.
Re: RainMaker MQTT server
Hi
This is my situation.
I would like to group the devices as follows:
- only the ESP Node is visible in the application (it acts as a "group" that contains my devices)
- The ESP node "contains" my devices
I can't do that right now
That's why I need my own implementation, especially for Flashing "my devices" via MQTT messages.
This is my situation.
I would like to group the devices as follows:
- only the ESP Node is visible in the application (it acts as a "group" that contains my devices)
- The ESP node "contains" my devices
I can't do that right now
That's why I need my own implementation, especially for Flashing "my devices" via MQTT messages.
- Attachments
-
- My_network.png (16.62 KiB) Viewed 4202 times
-
- Posts: 307
- Joined: Wed Feb 20, 2019 7:02 am
Re: RainMaker MQTT server
Multiple devices can indeed be supported with existing RainMaker as you can see in this example.
Moreover, while creating OTA Jobs via dashboard, you can provide some additional metadata via the "Advanced" section to give more info to the esp32 about what is to be done with the image.
If you use the underlying API, you can even add your own. custom data to tell esp32 to upgrade the other devices.
Moreover, while creating OTA Jobs via dashboard, you can provide some additional metadata via the "Advanced" section to give more info to the esp32 about what is to be done with the image.
If you use the underlying API, you can even add your own. custom data to tell esp32 to upgrade the other devices.
Re: RainMaker MQTT server
Why a mobile app,uses RainMaker API Service, why the mobile app is not simply an MQTT client?
Structure of MQTT response messages, when the message sent by ESP and mobile APP is not the same.
Example Send ESP to MQTT server:
Send: {"ESP_WiFi_Comm":{"Power":false}}
Recieive: {"ESP_WiFi_Comm":{"Power":false}}
Example Send mobileAPP to API Service
Send: PUT /{version}/user/nodes/ {"ESP_WiFi_Comm":{"Power":false}}
Recieive: { "status": "success", "description": "Success description"}
And in local control, the answer is another structure?
Pls, can you explain. Thank you
Structure of MQTT response messages, when the message sent by ESP and mobile APP is not the same.
Example Send ESP to MQTT server:
Send: {"ESP_WiFi_Comm":{"Power":false}}
Recieive: {"ESP_WiFi_Comm":{"Power":false}}
Example Send mobileAPP to API Service
Send: PUT /{version}/user/nodes/ {"ESP_WiFi_Comm":{"Power":false}}
Recieive: { "status": "success", "description": "Success description"}
And in local control, the answer is another structure?
Pls, can you explain. Thank you
Who is online
Users browsing this forum: No registered users and 62 guests