Firmware update via OTA fails frequently. #51
Comments
|
Allow us to install version 1.0.6 so that we can carry out comparative tests with version 1.1.1 |
|
Is there any relation with the timeout set to 60000 in the VS Code extension source code? |
|
After about 15 attempts, we managed to update the device!!! The new attempts below were using the Notebook with GSM-4G internet (Hotspot Smartphone) / WiFi (Notebook). Apparently, the results were "better". |
|
Hi @alvarolb Does the new version (1.1.2 )VS Code/Thinger Extension update fix this "bug"? |
|
Hi @alvarolb We tried to update the same device again. This time, the device has version 2.31.0 of the Arduino-Library/Thinger library. We tried 10 times, and all attempts failed. We tried to perform the OTA process on other devices, and the failures in the middle of the process are frequent. Apparently, this version of the OTA (perhaps the VS Code extension) is less tolerant to connection instability. Apparently, it would be necessary for the VS Code extension to be more tolerant to internet connection instability. |
|
Apparently, the failures are related to the signal strength (RSSI) of the Device (which is related to the quality of the WiFi connection and the intermittency of the internet). We tested the OTA update on a device with RSSI of -55 (on average) and the update was successful on the first attempt. However, other devices with RSSI signal strength of -75 and -82 fail during the update process. In other words, the VS Code extension has to be more tolerant of devices that have WiFi internet connection with low RSSI between -70 and -90. |
|
The latest versions should not affect stability, as they are maintenance updates that do not change the core of the OTA process. I believe the issue lies with the devices being under a weak signal, and sending large packets during the OTA update may be causing failures. The only configuration change I suggest for this setup is reducing the OTA chunk size on the device. You can use If this makes a difference, we could incorporate this option into the extension, allowing users to configure it as needed, without having to force an specific configuration on the device. |
|
Hello, @alvarolb I was able to update the device (ESP8266) more than once by configuring Furthermore, I understand that it is better for this configuration to be in the VS Code extension. The device may be in a remote/distant location and the User will not be able to change from Thanks |
|
Additionally, we noticed that when the communication failure occurs, the VS Code extension does not attempt to communicate with the device again. We notice this because the data transmission indicators are off. The VS Code Extension should send "pings" or transmission or reconnection attempts, right? |
We noticed that after recent updates (both in the VS Code Extension and in the Thinger-Arduino library), the OTA update fails frequently.
We have a device with Thinger-Arduino version 2.25.2 (ESP8266) connected to a router with rssi -77 (on average).
We are trying to perform an OTA update, but the process fails frequently in the middle of the update. On some devices we managed to update on the fourth or fifth attempt. As for the current one, we have been trying several times without success.
The previous version of the VS Code Extension was more stable.
The text was updated successfully, but these errors were encountered: