esphome / issues

Issue Tracker for ESPHome
https://esphome.io/
290 stars 36 forks source link

OTA over WireGuard failed #5584

Open tomeriva opened 8 months ago

tomeriva commented 8 months ago

The problem

When connecting esp32 device to home wifi directrly, OTA work as expected. When esp32 device connected via wireguard from remote location, the OTA is not working.

For more details: https://www.facebook.com/groups/2431447663796200/posts/3724005094540444

Which version of ESPHome has the issue?

2024.2.2

What type of installation are you using?

Home Assistant Add-on

Which version of Home Assistant has the issue?

2024.3.0

What platform are you using?

ESP32

Board

ESP32S CP2102 TYPE-C

Component causing the issue

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

[V][ota:185]: OTA features is 0x01
[V][ota:205]: Auth: Nonce is 3ef637128fb582e7af7598d97fa526dd
[V][ota:225]: Auth: CNonce is a38d4b0e8d6a380e87c7198542b88480
[V][ota:232]: Auth: Result is da5d20167ca038b26c3ba741da0099f0
[V][ota:240]: Auth: Response is da5d20167ca038b26c3ba741da0099f0
[V][ota:268]: OTA size is 971920 bytes
[167646][D][Updater.cpp:133] begin(): OTA Partition: app1
[V][ota:285]: Update: Binary MD5 is cbd8fd7b8a057af548af2691e11a4a19
E (185121) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (185121) task_wdt: - loopTask (CPU 1)
E (185121) task_wdt: Tasks currently running:
E (185121) task_wdt: CPU 0: IDLE
E (185121) task_wdt: CPU 1: IDLE
E (185121) task_wdt: Aborting.
abort() was called at PC 0x400f9c38 on core 0
Backtrace:0x400837e1:0x3ffbeaec |<-CORRUPTED
ELF file SHA256: 0000000000000000
Rebooting...

Additional information

431314042_10231055376557166_3399000983340441769_n

eugenscobich commented 7 months ago

Hi, I'm experiencing the same issue. OTA over WIFI works as expected, OTA over LAN8720 fails randomly on different percentage of uploading. I'm using such kind o board https://www.waveshare.com/wiki/LAN8720_ETH_Board. Previously, it was connected via wires but when I soldered it direct to my custom PCB the issue haven't gone.

This are my logs:

[1B][0;36m[D][ota:154]: Starting OTA Update from 192.168.100.33...[1B][0m
[1B][0;36m[D][ota:330]: OTA in progress: 0.2%[1B][0m
[1B][0;36m[D][ota:330]: OTA in progress: 1.4%[1B][0m
[1B][0;36m[D][ota:330]: OTA in progress: 5.3%[1B][0m
[1B][0;36m[D][ota:330]: OTA in progress: 5.5%[1B][0m
[1B][0;36m[D][ota:330]: OTA in progress: 9.2%[1B][0m
[1B][0;36m[D][ota:330]: OTA in progress: 9.4%[1B][0m
E (82331) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (82331) task_wdt:  - loopTask (CPU 1)
E (82331) task_wdt: Tasks currently running:
E (82331) task_wdt: CPU 0: IDLE
E (82331) task_wdt: CPU 1: IDLE
E (82331) task_wdt: Aborting.
abort() was called at PC 0x400e748d on core 0
Backtrace:0x400835a5:0x3ffbe7bc |<-CORRUPTED

If I flush the configuration using USB, ethernet communication seems to be OK.

github-actions[bot] commented 3 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.