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.

We were making some quota calculation changes the past few days and have also decided to make the default quota 20 for all users. If you try to claim right now, your quota should automatically increase to 20. Can you give it a shot and check?

For regular led_light example with credentials generated using admin CLI - You should disable claiming (even if not, the credentials will be read from the fctry nvs binary, not via claiming). References can be found in the customer docs . - Read MQTT Host from ESP_RMAKER_MQTT_HOST, Read Node ID from...

Yes, the understanding is correct. Formatting the data into correct JSON representation and sending on the topics is equivalent to calling the C APIs. You can write your own wrappers for time series data.

Water level sensor is not a standard device/parameter, so you will have to create custom ones Eg. custom device: my_device = new Device("Water Sensor", "my.device.water-sensor", NULL); custom param: Eg. Param sensor("Level", "my.param.water-level", value(0), PROP_FLAG_READ); Add custom param to the ...

Currently, we do not have an API for this, but you can format the data as per the specifications mentioned here . Meanwhile, even though sending a message once per minute fits into our fair usage policy, a data point every second is still quite a huge data. Does your use case really require such hig...