Open 19leva89 opened 9 months ago
YES ! I (and others) have this problem regularly with Arlec PC191HA (which uses a WB2S module).
The firmware DID compile and upload successfully.
The key is in the first line from the run LOG from the device ... where we find that the device is still running a version of the firmware.
[16:18:52][I][app:102]: ESPHome version 2023.9.3 compiled on Oct 6 2023, 20:33:09
Conclusion is that the firmware did upload correctly - but the device did not automatically activate the new firmware when it reset.
A power cycle of the device will hopefully trigger the firmware to activate; though you may need to leave the device unplugged for a couple of hours.
Did anybody come up with a good solution or workaround for this.
I think I am experiencing the same issue with 2 of my Shelly Plus 2PM devices. I was able to OTA flash them from the original firmware to Tasmota and then I OTA-flashed a basic config of esphome to it. Then I used esphome to OTA-flash another config to it, all without problems. The current firmware I have, however seems to stick and I am not able to make any changes and get it to load a new firmware. The esphome upload seems to succeed, but it still boots up with the old Firmware. I created another issue #5720, where I did not realize the reason. Now I know it is because the new Firmware is not loading.
I did try to remove the power from these devices and turn it back on. This does not help, unfortunately. Also tried keeping them without power for up to 90 minutes, with no effect. Really annoying.. Would be super happy if someone has an idea on what to do here.
Try doing the update again right away without power cycling it.
More than seven months have already passed since my first post, but the problem has not been solved! To update the firmware, you need to flash the ESP manually, it cannot be flashed over the air.
Now I have installed version 2024.4.2, but when I try to update to 2024.5.0 I still get the same error as 7 months ago(
INFO ESPHome 2024.5.0
INFO Reading configuration /config/esphome/xiaomi-ir.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing xiaomi-ir (board: esp32dev; framework: arduino; platform: platformio/espressif32@5.4.0)
--------------------------------------------------------------------------------
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
- toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch5
Dependency Graph
|-- AsyncTCP-esphome @ 2.1.3
|-- WiFi @ 2.0.0
|-- FS @ 2.0.0
|-- Update @ 2.0.0
|-- ESPAsyncWebServer-esphome @ 3.2.0
|-- ESPmDNS @ 2.0.0
|-- noise-c @ 0.1.4
|-- ArduinoJson @ 6.18.5
|-- HeatpumpIR @ 1.0.23
|-- IRremoteESP8266 @ 2.8.4
RAM: [= ] 13.4% (used 43764 bytes from 327680 bytes)
Flash: [====== ] 58.2% (used 1068097 bytes from 1835008 bytes)
========================= [SUCCESS] Took 24.00 seconds =========================
INFO Successfully compiled program.
INFO Connecting to 192.168.31.47
INFO Uploading /data/build/xiaomi-ir/.pioenvs/xiaomi-ir/firmware.bin (1073872 bytes)
Uploading: [============================================================] 100% Done...
INFO Upload took 10.18 seconds, waiting for result...
INFO OTA successful
INFO Successfully uploaded program.
INFO Starting log output from 192.168.31.47 using esphome API
INFO Successfully connected to xiaomi-ir @ 192.168.31.47 in 11.477s
INFO Successful handshake with xiaomi-ir @ 192.168.31.47 in 0.066s
[09:46:34][I][app:100]: ESPHome version 2024.4.2 compiled on May 2 2024, 22:07:27
19leva89, did you try power cycling the device after uploading the firmware ?
Did you try powering the device off for 10 minutes after uploading the firmware ?
Not the ideal solution I know, but if your device also behaves this way then possibly the developers can program a power cycle rather than just a reset after a successful firmware upload.
Or try uploading twice without power cycling which I already suggested. Did you try it?
Did you try power cycling the device after uploading the firmware ? Did you try powering the device off for 10 minutes after uploading the firmware ?
I tried it - it doesn't help!
Or try uploading twice without power cycling which I already suggested. Did you try it?
I tried it - it doesn't help!
If I connect to a PC via UART, then everything is flashed without problems
The problem
I have a device on ESP-32 (ESP32-D0WD-V3). After installing the firmware via ESP-Home, you can update it once over the air (OTA) and it doesn’t want to update anymore, although it says that it was updated and everything is OK (I’m attaching the log). Has anyone encountered this problem and is there a way out of this situation?
Which version of ESPHome has the issue?
2023.10.0
What type of installation are you using?
Docker
Which version of Home Assistant has the issue?
2023.10.3
What platform are you using?
ESP32
Board
ESP32-D0WD-V3
Component causing the issue
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response