Open radek-kafka opened 1 year ago
I can confirm the unstable connection since 2023.3 and HA 2023.3.5
ESP32:
[15:26:10][D][homeassistant.sensor:024]: 'sensor.power_consumption': Got state 83.00
[15:26:10][D][api.connection:159]: Home Assistant 2023.3.5 (192.168.1.25) requested disconnected
[15:26:10][D][api:102]: Accepted 192.168.1.25
[15:26:11][D][api.connection:920]: Home Assistant 2023.3.5 (192.168.1.25): Connected successfully
[15:26:12][D][api:102]: Accepted 192.168.1.25
[15:26:12][D][api.connection:920]: Home Assistant 2023.3.5 (192.168.1.25): Connected successfully
[15:26:13][D][homeassistant.sensor:024]: 'sensor.power_consumption': Got state 86.00
[15:26:14][D][homeassistant.sensor:024]: 'sensor.power_consumption': Got state 84.00
after that, there seem to be 2 parallel connections! I get the sensor reading duplicated each second.
[15:26:17][D][homeassistant.sensor:024]: 'sensor.power_consumption': Got state 86.00
[15:26:17][D][homeassistant.sensor:024]: 'sensor.power_consumption': Got state 86.00
[15:26:18][D][homeassistant.sensor:024]: 'sensor.power_consumption': Got state 88.00
[15:26:18][D][homeassistant.sensor:024]: 'sensor.power_consumption': Got state 88.00
[15:26:19][D][homeassistant.sensor:024]: 'sensor.power_consumption': Got state 84.00
[15:26:19][D][homeassistant.sensor:024]: 'sensor.power_consumption': Got state 84.00
HA log message:
2023-03-21 15:26:10.836 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for garage-controller @ 192.168.1.20: Connection cancelled
10 min later the ESP device is offline and does not reconnect!
The duplicate connection seems to be unrelated.
But now I can't downgrade the ESP anymore. Clean re-compile with 2023.2.4 and reflash does not fix the instabillity. The ESP32 keeps crashing after random time frames. Sometimes 10 minutes, sometimes a few seconds. 😞
Mine is after last updates stable. I do not see messages like before. 2023.3.1 looks to me better .
Does not look from the changelog like it could fix it... I will try 2023.3.2 then again.
After several clean ups and reflashes my ESP seems to be stable again with 2023.2.4
I'm having a similar issue. Since a certain update (don't remember which). In ESPHome it shows online, but nothing works. I can't ping it, I get no data in HA and the web interface doesn't work.
In the logs I get this ----- start ----- [I][mqtt:216]: MQTT Connected!
abort() was called at PC 0x401e53d7 on core 1
Backtrace:0x40083725:0x3fff56f00x400930e5:0x3fff5710 0x400986a9:0x3fff5730 0x401e53d7:0x3fff57b0 0x401e541e:0x3fff57d0 0x401e6501:0x3fff57f0 0x401e4e10:0x3fff5810 0x401e57ad:0x3fff5830 0x401e5e12:0x3fff5850 0x401e5e45:0x3fff5880 0x400dafef:0x3fff58a0 0x400db09e:0x3fff5910 0x400da7f2:0x3fff5960 0x400eea25:0x3fff59a0 0x401ff42e:0x3fff5a10 0x400ef7c6:0x3fff5a40 0x400ee7a6:0x3fff5a90 0x400ee7be:0x3fff5b00 0x401e8581:0x3fff5b20 0x401e85fd:0x3fff5b50 0x401e8de6:0x3fff5b70
ELF file SHA256: 0000000000000000
Rebooting... ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0030,len:1184 load:0x40078000,len:13132 load:0x40080400,len:3036 entry 0x400805e4 [I][logger:258]: Log initialized [C][ota:469]: There have been 1 suspected unsuccessful boot attempts. ----- end -----
After 10 unsuccessful boot attempts I get nothing more in the logs. But sometime I get this after the 10th boot attempt :
----- start ----- [C][ota:469]: There have been 10 suspected unsuccessful boot attempts. [D][esp32.preferences:113]: Saving 1 preferences to flash... [D][esp32.preferences:142]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed [E][ota:476]: Boot loop detected. Proceeding to safe mode. ----- end -----
Then I can ping it, but nothing else works.
ESPHome is currently on 2023.3.2. I have tried it with previous versions also. I hoped it would have been fixed. I just did a clean build again, but still the same problem.
I'm using an ESP-WROOM-32 board and this is the config : esphome: name: bureau platform: ESP32 board: esp32dev
Is that still correct? It has worked before, but maybe something changed. I read in a post somewhere that the person changed it to edp-idf and that fixed it, but I like to be certain before I change anything.
My ESP-WROOM-32 is now stable with 2023.3.2. I guess there was something not re-compiled correctly. I'm using esphome in a docker container, so I removed the container, all related images and cleaned cached stuff multiple times. Including the config directory (only left the device yaml files there). Then rebuilt and reflashed multiple times with 2023.2.4 until it was stable again. Then did the same with 2023.3.2 and it works now.
I'm running ESPHome under Home Assistant. I already did "Clean build files" several times. Do you know how I can clean up ESPHome to re-compile everything?
Mh no experiance with that. You could try to delete all files below config/esphome/ (except your yaml config files) the command pio system prune was also helpfull in the docker version. But I don't know if the HA integrated version has a command line interface? As a last resort you could try to remove /reinstall the add-on
I removed everything from config/esphome, except for yaml files. Re-installed, but still the same problem.
Hi There,
The interval and window length does not play well with Wi-Fi. Current recommendation is to leave the interval and window on the defaults for Wifi ESP controllers.
esp32_ble_tracker:
scan_parameters:
interval: 1100ms
window: 1100ms
active: true
Change to these defaults:
esp32_ble_tracker:
scan_parameters:
interval: 320ms
window: 30ms
active: true
Hope it helps.
I'm having the exact problem. Several ESP32 devices, all identical, and one stopped working after updating to latest ESPHome. No error messages. Data shows up on terminal monitor but HA can't get any data. A clean install to a new device does nothing.
I also noticed that ESPHome no longer cleans up unused devices. When changing the name to debug, the previous ESPHome device is still in the HA logs even after deleting the ESPHome device.
Same problem here:
2022.12.8 Feb 10 2023 is working
2023.9.0b2, 2023.10.0-dev, 2023.8.3 has problems - not working.
16:22:26][W][system:171]: Synchronized sntp clock
[16:22:26][I][mqtt:279]: MQTT Connected!
[16:22:28]
[16:22:28]abort() was called at PC 0x401fccbf on core 0
[16:22:28]
[16:22:28]
[16:22:28]Backtrace:0x40083829:0x3ffd7dc00x4009491d:0x3ffd7de0 0x40099ee1:0x3ffd7e00 0x401fccbf:0x3ffd7e80 0x401fcd06:0x3ffd7ea0 0x401fcc67:0x3ffd7ec0 0x401fb95e:0x3ffd7ee0 0x400d4c19:0x3ffd7f00 0x4011ed59:0x3ffd7f20 0x40145d1d:0x3ffd7f40 0x40147b77:0x3ffd7f60
WARNING Found stack trace! Trying to decode it
WARNING Decoded 0x40083829: panic_abort at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/esp_system/panic.c:402
WARNING Decoded 0x4009491d: esp_system_abort at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/esp_system/esp_system.c:128
WARNING Decoded 0x40099ee1: abort at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/newlib/abort.c:46
WARNING Decoded 0x401fccbf: __cxxabiv1::__terminate(void (*)()) at /builds/idf/crosstool-NG/.build/HOST-x86_64-apple-darwin12/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:47
WARNING Decoded 0x401fcd06: std::terminate() at /builds/idf/crosstool-NG/.build/HOST-x86_64-apple-darwin12/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:57
WARNING Decoded 0x401fcc67: __cxa_throw at /builds/idf/crosstool-NG/.build/HOST-x86_64-apple-darwin12/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:95
WARNING Decoded 0x401fb95e: operator new(unsigned int) at /builds/idf/crosstool-NG/.build/HOST-x86_64-apple-darwin12/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/new_op.cc:54
WARNING Decoded 0x400d4c19: esphome::esp32_ble::ESP32BLE::gap_event_handler(esp_gap_ble_cb_event_t, esp_ble_gap_cb_param_t*) at /Users/petsie1612/ips_apps/esphome-lab/.esphome/build/mqtt-test/src/esphome/components/esp32_ble/ble.cpp:173
WARNING Decoded 0x4011ed59: btc_gap_ble_cb_to_app at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/bt/host/bluedroid/btc/profile/std/gap/btc_gap_ble.c:55
(inlined by) btc_gap_ble_cb_handler at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/bt/host/bluedroid/btc/profile/std/gap/btc_gap_ble.c:1156
WARNING Decoded 0x40145d1d: btc_thread_handler at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/bt/common/btc/core/btc_task.c:196
WARNING Decoded 0x40147b77: osi_thread_run at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/bt/common/osi/thread.c:68
[16:22:29]
[16:22:29]
[16:22:29]
[16:22:29]
[16:22:29]ELF file SHA256: 0000000000000000
[16:22:29]
[16:22:29]Rebooting...
[16:22:29]ets Jun 8 2016 00:22:57
[16:22:29]
[16:22:29]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[16:22:29]configsip: 0, SPIWP:0xee
[16:22:29]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[16:22:29]mode:DIO, clock div:2
[16:22:29]load:0x3fff0030,len:1184
[16:22:29]load:0x40078000,len:13132
[16:22:29]load:0x40080400,len:3036
....
[16:22:34][W][system:171]: Synchronized sntp clock
[16:22:34][I][mqtt:279]: MQTT Connected!
[16:22:36]
[16:22:36]abort() was called at PC 0x401fccbf on core 0
[16:22:36]
[16:22:36]
[16:22:36]Backtrace:0x40083829:0x3ffd7e500x4009491d:0x3ffd7e70 0x40099ee1:0x3ffd7e90 0x401fccbf:0x3ffd7f10 0x401fcd06:0x3ffd7f30 0x401fcfe1:0x3ffd7f50 0x401fb950:0x3ffd7f70 0x400d4c19:0x3ffd7f90 0x4011ed59:0x3ffd7fb0 0x40145d1d:0x3ffd7fd0 0x40147b77:0x3ffd7ff0
WARNING Found stack trace! Trying to decode it
WARNING Decoded 0x40083829: panic_abort at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/esp_system/panic.c:402
WARNING Decoded 0x4009491d: esp_system_abort at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/esp_system/esp_system.c:128
WARNING Decoded 0x40099ee1: abort at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/newlib/abort.c:46
WARNING Decoded 0x401fccbf: __cxxabiv1::__terminate(void (*)()) at /builds/idf/crosstool-NG/.build/HOST-x86_64-apple-darwin12/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:47
WARNING Decoded 0x401fcd06: std::terminate() at /builds/idf/crosstool-NG/.build/HOST-x86_64-apple-darwin12/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:57
WARNING Decoded 0x401fcfe1: __cxa_allocate_exception at /builds/idf/crosstool-NG/.build/HOST-x86_64-apple-darwin12/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/eh_alloc.cc:300
WARNING Decoded 0x401fb950: operator new(unsigned int) at /builds/idf/crosstool-NG/.build/HOST-x86_64-apple-darwin12/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/new_op.cc:54
WARNING Decoded 0x400d4c19: esphome::esp32_ble::ESP32BLE::gap_event_handler(esp_gap_ble_cb_event_t, esp_ble_gap_cb_param_t*) at /Users/petsie1612/ips_apps/esphome-lab/.esphome/build/mqtt-test/src/esphome/components/esp32_ble/ble.cpp:173
WARNING Decoded 0x4011ed59: btc_gap_ble_cb_to_app at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/bt/host/bluedroid/btc/profile/std/gap/btc_gap_ble.c:55
(inlined by) btc_gap_ble_cb_handler at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/bt/host/bluedroid/btc/profile/std/gap/btc_gap_ble.c:1156
WARNING Decoded 0x40145d1d: btc_thread_handler at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/bt/common/btc/core/btc_task.c:196
WARNING Decoded 0x40147b77: osi_thread_run at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/bt/common/osi/thread.c:68
[16:22:37]
[16:22:37]
[16:22:37]
[16:22:37]
[16:22:37]ELF file SHA256: 0000000000000000
[16:22:37]
[16:22:37]Rebooting...
[16:22:37]ets Jun 8 2016 00:22:57
[16:22:37]
[16:22:37]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[16:22:37]configsip: 0, SPIWP:0xee
[16:22:37]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[16:22:37]mode:DIO, clock div:2
[16:22:37]load:0x3fff0030,len:1184
[16:22:37]load:0x40078000,len:13132
[16:22:37]load:0x40080400,len:3036
[16:22:37]entry 0x400805e4
[16:22:37][I][logger:268]: Log initialized
[16:22:37][C][ota:473]: There have been 3 suspected unsuccessful boot attempts.
[16:22:37][D][esp32.preferences:114]: Saving 1 preferences to flash...
[16:22:37][D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[16:22:37][I][app:029]: Running through setup()...
[16:22:37][D][template.switch:046]: Restored state OFF
[16:22:37][D][switch:016]: 'Boot Counter reset' Turning OFF.
The problem
Hi,
my M5Atom is restarting after the update to new version 2023.3 today.. I have tried multiple reboots but still same.. Lot of disconnects from WiFi, crashes etc..
See the logs .. Many thanks Radek
Which version of ESPHome has the issue?
2023.3
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2023.2
What platform are you using?
ESP32
Board
M5AtomLite
Component causing the issue
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response