RainMaker services begin after getting IP address. Typical logs for working use case are these: I (3464) wifi:connected with MYSSID_2GEXT, aid = 11, channel 4, BW20, bssid = 2c:30:33:54:ba:d9 I (3474) wifi:security: WPA2-PSK, phy: bgn, rssi: -51 I (3474) wifi:pm start, type: 1 I (3474) wifi:dp: 1, b...

Do you mean that the exact same firmware that was working earlier is not working anymore? Or was this re-compiled with some different ESP IDF version (please provide idf version)? Is this with the standard switch example available on GitHub?

A fix for this issue has been provided in the latest app v3.3.2, released on 28 May.

Can you provide information about the board being used here? I see this event in between I (126940) app_reset: Release button to trigger factory reset. which means that there is some false button press event detected and then a button release event got triggered much later here I (424570) app_main: ...

The time series data is stored on the cloud. The apps just query for it whenever required to plot the graphs.

By client side, do you mean device? Currently they have no way to know the groups they are part of. One of our customers had created a custom RainMaker service to push the group id to nodes, but it was mostly used for mesh node group control, in which the cloud did not have much role to play, apart ...

Thread support will be available cleanly in ESP RainMaker firmware and phone apps in about 4-5 weeks time.

Have you tried using ESP_RMAKER_PARAM_SPEED instead of ESP_RMAKER_PARAM_RANGE for the speed parameter?

Hi Josh, The RainMaker OTA functionality itself does not require the zip file, but just the binary. So, as a quick fix, you can simply upload the firmware binary file and use that for OTA. The package itself is required for Insights logs parsing and can be uploaded later after we debug and find a fi...

Sorry for missing this out. Just pass PROP_FLAG_READ as properties while creating your parameter using esp_rmaker_param_create() . An example can be found here.