Hi Josh, For the usage instructions for Insights, have you checked the docs here ? The time series functionality in RainMaker is geared towards end user use cases and aggregations are restricted to the the specific parameter for the specific device. This can be enabled in firmware by simply adding t...

Devices not connected to ESP RainMaker cloud directly cannot be part of RainMaker automations. If you want to control 3rd party devices, you can check the Automations in Google Home or the Routines in Alexa which allows cross-vendor integrations.

Did you just reboot the board or pressed and held the boot button for 3+ or 10+ seconds as mentioned under the Resetting the board section of the docs?

Nova Home is built for specific smart home use cases like lights and switches and supports only single devices, not multiple devices in single node. So, assuming that the 2 screens mean 2 tiles of devices, that would not be possible in Nova Home. ESP RainMaker app could be suitable. However, the use...

Hi Pulkit,

With no information at all about what firmware is being used, it would be almost impossible to help here. Can you share more details?

Please check out these videos by some hobbyists to understand how to integrate temperature sensors in ESP RainMaker: Using RainMaker with Arduino IDE in ESP32 Temperature and Humidity Monitor Using ESP RainMaker After that, check my comment here to understand how to implement any standard device typ...

Please check my comment here for some pointers. Your motion sensor device creation logic seems fine, since it indeed sets the device type to esp.device.motion-sensor, but you can skip the power parameter if the motion sensor does not need any control. The motion detection state parameter, however, s...

As mentioned in the Standar device type docs, Name, Power, Media State, Media Control App Selector, Input Selector, Volume are all mandatory parameter for TV. Can you try adding these?

Are you using esp-idf of Arduino? Can you share your current snippet which creates the device so that we can suggest appropriate changes?

Currently, the value types are documented only in the C API docs.