Thank you so much for such a detailed answer.

There are no error messages in Arduino during subsequent reboots.
The device is loaded on an already NEW firmware (which was allegedly rejected).

I have tested this on two devices: ESP32 (16Mb) and ESP32 S3 (8Mb) .

Screenshot from dashboard

Thank you for the complete answer. I also wanted to note one observation in the OTA process. The dashboard shows that OTA is rejected, but the behavior of the device shows that the new firmware has been successfully downloaded and updated. The device is running on the new firmware. The port monitor ...

Thanks for the help and information. For everyone who will read this branch: NO MORE THAN 25000 messages from the node per day!! As I understand it, the MQTT client automatically generates PING messages to support the connection. More often than the session timeout occurs. These messages are probabl...

Thanks for the reply. The firmware uses the parameter with " PROP_FLAG_READ | PROP_FLAG_TIME_SERIES". To monitor the supply voltage once every 10 seconds. Where can I find the usage policy? The documentation for the PROP_FLAG_TIME_SERIES property does not say anything about this. I plan to use the d...

Here is a screenshot from the app.

Node ID:
3XjduFh7MJa6hx6fmpg9DS

I also have another device based on ESP 32 S3.
With the same firmware.
It worked smoothly, but at the same time it reset the WiFi settings and switched to PROVISION mode.

I use Rainmaker Arduino. ESP32 After three weeks of stable operation, the device suddenly (09/26/2024 04:50) stopped connecting to MQTT. With error: E (2316017) MQTT_CLIENT: mqtt_message_receive: transport_read() error: errno=119 E (2316018) esp_mlt_glue: MQTT_EVENT_ERROR E (2316018) MQTT_CLIENT: as...