RainMaker MQTT server

Stipa88
Posts: 12
Joined: Mon May 09, 2022 12:26 pm

RainMaker MQTT server

Postby Stipa88 » Sat Jan 28, 2023 5:39 pm

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? :D :D

I commend it, a well thought out system, but I want my own server (MQTT)

Tnx

ESP_Piyush
Posts: 257
Joined: Wed Feb 20, 2019 7:02 am

Re: RainMaker MQTT server

Postby ESP_Piyush » Sat Jan 28, 2023 5:49 pm

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.

Stipa88
Posts: 12
Joined: Mon May 09, 2022 12:26 pm

Re: RainMaker MQTT server

Postby Stipa88 » Sat Jan 28, 2023 6:22 pm

Hi

This is my situation.Image

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
My_network.png (16.62 KiB) Viewed 2747 times

ESP_Piyush
Posts: 257
Joined: Wed Feb 20, 2019 7:02 am

Re: RainMaker MQTT server

Postby ESP_Piyush » Wed Feb 01, 2023 5:23 pm

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.
Screenshot 2023-02-01 at 10.49.02 PM.png
Screenshot 2023-02-01 at 10.49.02 PM.png (53.81 KiB) Viewed 2590 times
If you use the underlying API, you can even add your own. custom data to tell esp32 to upgrade the other devices.

Stipa88
Posts: 12
Joined: Mon May 09, 2022 12:26 pm

Re: RainMaker MQTT server

Postby Stipa88 » Tue Feb 07, 2023 11:13 am

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

Who is online

Users browsing this forum: No registered users and 9 guests