ESP32 Forum

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: asp_met_connect: mqtt_message_receive() returned -1
E (2316024) MQTT_CLIENT: QT connect failed

Nothing has changed, firmware or settings.

At the same time, the WiFi connection is maintained.

After resetting to factory settings and the connection process, nothing has changed.
The device is connected to Wi-Fi but there is no MQTT connection.

The reason may not be in the firmware, settings, or network access.

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.

Can you share your node id?

Node ID:
3XjduFh7MJa6hx6fmpg9DS

Here is a screenshot from the app.

We see that your node id (3XjduFh7MJa6hx6fmpg9DS) is amongst the ones deactivated recently for violating our fair usage policy. You may have to claim new certificates and ensure that the firmware does not send too many messages so that it does not get deactivated again.

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 device for commercial purposes. I'm still testing it.
I will disable this feature until I receive information.
What do I need to do now to unlock the node?

You can find information about time series data here. Basically, whenever you call esp_rmaker_param_update_and_report(), 2 MQTT messages get sent, one to update time series data and one to update the instantaneous param value as mentioned towards the end of the Usage section. The fair usage policy was already linked in the previous message and also a way to recover the node (do claiming once again, by erasing flash)

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 probably also automatically counted, but the developers do not know their exact number.
Because of this, unintentional traffic overflows may occur.

The MQTT PING messages sent every 120 seconds (as per default configured Keep Alive time don't get counted in this. Only explicit data publish messages get counted.