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 shows only such messages:
E (530128) TRANSPORT_BASE: poll_read select error 113, errno = Software caused connection abort, fd = 48
E (530128) MQTT_CLIENT: Poll read error: 119, aborting connection
I use Arduino IDE
Below is a screenshot from the dashboard.
The device suddenly lost access to MQTT
-
- Posts: 9
- Joined: Thu Sep 26, 2024 7:02 am
-
- Posts: 9
- Joined: Thu Sep 26, 2024 7:02 am
Re: The device suddenly lost access to MQTT
Screenshot from dashboard
- Attachments
-
- OTA_error.png (43.84 KiB) Viewed 232 times
-
- Posts: 296
- Joined: Wed Feb 20, 2019 7:02 am
Re: The device suddenly lost access to MQTT
The log message seems to be incomplete. Since app rollback is enabled by default, when the node reboots into new firmware, it waits for an MQTT connection before it can report OTA success. If it cannot connect or there is some crash, it boots back into older firmware and reports rejected saying that the firmware rolled back. Can you check the subsequent logs to see if this is what has happened?
-
- Posts: 9
- Joined: Thu Sep 26, 2024 7:02 am
Re: The device suddenly lost access to MQTT
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) .
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) .
Who is online
Users browsing this forum: No registered users and 8 guests