esphome / issues

Issue Tracker for ESPHome
https://esphome.io/
288 stars 34 forks source link

Upgrade to 1.14.4 cause ESP32 bootloop #1276

Closed definitio closed 3 years ago

definitio commented 3 years ago

Operating environment/Installation (Hass.io/Docker/pip/etc.):

Arch Linux, Python 3.8.

ESP (ESP32/ESP8266, Board/Sonoff):

ESP32

Affected component:

https://esphome.io/components/wifi.html ?

Description of problem: ESP32 doesn't start after upgrade.

Problem-relevant YAML-configuration entries:

wifi:
  ssid: !secret ssid
  password: !secret wifi_password

Logs (if applicable):

PASTE DEBUG LOG HERE
[19:45:10]Rebooting...
[19:45:10]ets Jun  8 2016 00:22:57
[19:45:10]
[19:45:10]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[19:45:10]configsip: 0, SPIWP:0xee
[19:45:10]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[19:45:10]mode:DIO, clock div:2
[19:45:10]load:0x3fff0018,len:4
[19:45:10]load:0x3fff001c,len:1044
[19:45:10]load:0x40078000,len:8896
[19:45:10]load:0x40080400,len:5828
[19:45:10]entry 0x400806ac
[19:45:10][E][pcf8574:012]: PCF8574 not available under 0x27
[19:45:10][E][component:092]: Component was marked as failed.
[19:45:10][E][component:092]: Component was marked as failed.
[19:45:10][E][component:092]: Component was marked as failed.
[19:45:10][E][component:092]: Component was marked as failed.
[19:45:10][E][component:092]: Component was marked as failed.
[19:45:10]Guru Meditation Error: Core  1 panic'ed (Interrupt wdt timeout on CPU1)
[19:45:10]Core 1 register dump:
[19:45:10]PC      : 0x4008c366  PS      : 0x00060134  A0      : 0x8008b523  A1      : 0x3ffb0970  
WARNING Decoded 0x4008c366: vListInsert at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/list.c:188
[19:45:10]A2      : 0x3ffb7ddc  A3      : 0x3ffb8074  A4      : 0x00000001  A5      : 0x00000001  
[19:45:10]A6      : 0x00060123  A7      : 0x00000000  A8      : 0x3ffb8074  A9      : 0x3ffb8074  
[19:45:10]A10     : 0x00000001  A11     : 0x00000001  A12     : 0x00000020  A13     : 0x00000000  
[19:45:10]A14     : 0x00000000  A15     : 0x00000000  SAR     : 0x00000014  EXCCAUSE: 0x00000006  
[19:45:10]EXCVADDR: 0x00000000  LBEG    : 0x40001609  LEND    : 0x4000160d  LCOUNT  : 0x00000000  
[19:45:10]
[19:45:10]Backtrace: 0x4008c366:0x3ffb0970 0x4008b520:0x3ffb0990 0x400897ab:0x3ffb09b0 0x400fde97:0x3ffb09f0 0x400fdf62:0x3ffb0a10 0x40087966:0x3ffb0a30 0x40087e9a:0x3ffb0a50 0x40110565:0x3ffb0ac0 0x4010ee2d:0x3ffb0ae0 0x4010f27b:0x3ffb0b00 0x4010dc05:0x3ffb0b70 0x4010e001:0x3ffb0bc0 0x4010e138:0x3ffb0c40 0x4010d0ce:0x3ffb0ca0 0x4010d735:0x3ffb0ce0 0x4015c9e6:0x3ffb0d00 0x4015cbda:0x3ffb0d50 0x4015cc2d:0x3ffb0d80 0x40110a23:0x3ffb0da0 0x40110b76:0x3ffb0dc0 0x400fc289:0x3ffb0de0 0x400eca58:0x3ffb0e00 0x400df7b5:0x3ffb0f00 0x400df814:0x3ffb0f30 0x400debe8:0x3ffb0f60 0x40173051:0x3ffb0f80 0x40173139:0x3ffb0fa0 0x400e10cd:0x3ffb0fc0 0x400ea9aa:0x3ffb1010 0x400f9333:0x3ffb1fb0 0x400899a5:0x3ffb1fd0
WARNING Found stack trace! Trying to decode it
WARNING Decoded 0x4008c366: vListInsert at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/list.c:188
WARNING Decoded 0x4008b520: vTaskPlaceOnEventList at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/tasks.c:3507
WARNING Decoded 0x400897ab: xQueueGenericReceive at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/queue.c:1996
WARNING Decoded 0x400fde97: esp_ipc_call_and_wait at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/ipc.c:116
WARNING Decoded 0x400fdf62: esp_ipc_call at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/ipc.c:123
WARNING Decoded 0x40087966: spi_flash_disable_interrupts_caches_and_other_cpu at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/spi_flash/cache_utils.c:120
WARNING Decoded 0x40087e9a: spi_flash_guard_start at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/spi_flash/flash_ops.c:162
 (inlined by) spi_flash_read at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/spi_flash/flash_ops.c:508
WARNING Decoded 0x40110565: nvs::nvs_flash_read(unsigned int, void*, unsigned int) at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_ops.cpp:70
WARNING Decoded 0x4010ee2d: nvs::Page::readEntry(unsigned int, nvs::Item&) const at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_page.cpp:849
WARNING Decoded 0x4010f27b: nvs::Page::findItem(unsigned char, nvs::ItemType, char const*, unsigned int&, nvs::Item&, unsigned char, nvs::VerOffset) at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_page.cpp:849
WARNING Decoded 0x4010dc05: nvs::Storage::findItem(unsigned char, nvs::ItemType, char const*, nvs::Page*&, nvs::Item&, unsigned char, nvs::VerOffset) at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_storage.cpp:557
WARNING Decoded 0x4010e001: nvs::Storage::readMultiPageBlob(unsigned char, char const*, void*, unsigned int) at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_storage.cpp:557
WARNING Decoded 0x4010e138: nvs::Storage::readItem(unsigned char, nvs::ItemType, char const*, void*, unsigned int) at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_storage.cpp:557
WARNING Decoded 0x4010d0ce: nvs_get_str_or_blob(unsigned int, nvs::ItemType, char const*, void*, unsigned int*) at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_api.cpp:521
WARNING Decoded 0x4010d735: nvs_get_blob at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_api.cpp:525
WARNING Decoded 0x4015c9e6: nvs_log_init
WARNING Decoded 0x4015cbda: misc_nvs_load
WARNING Decoded 0x4015cc2d: misc_nvs_init
WARNING Decoded 0x40110a23: wifi_init_in_caller_task
WARNING Decoded 0x40110b76: esp_wifi_init_internal
WARNING Decoded 0x400fc289: esp_wifi_init at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/wifi_init.c:62
WARNING Decoded 0x400eca58: WiFiGenericClass::mode(wifi_mode_t) at /home/username/.platformio/packages/framework-arduinoespressif32/libraries/WiFi/src/WiFiGeneric.cpp:250
 (inlined by) espWiFiStart at /home/username/.platformio/packages/framework-arduinoespressif32/libraries/WiFi/src/WiFiGeneric.cpp:140
 (inlined by) WiFiGenericClass::mode(wifi_mode_t) at /home/username/.platformio/packages/framework-arduinoespressif32/libraries/WiFi/src/WiFiGeneric.cpp:485
WARNING Decoded 0x400df7b5: esphome::wifi::WiFiComponent::wifi_mode_(esphome::optional<bool>, esphome::optional<bool>) at /home/username/Development/fw-mroom-blinds/src/esphome/components/wifi/wifi_component_esp32.cpp:545
WARNING Decoded 0x400df814: esphome::wifi::WiFiComponent::wifi_sta_pre_setup_() at /home/username/Development/fw-mroom-blinds/src/esphome/components/wifi/wifi_component_esp32.cpp:545
WARNING Decoded 0x400debe8: esphome::wifi::WiFiComponent::setup() at /home/username/Development/fw-mroom-blinds/src/esphome/components/wifi/wifi_component.cpp:138
WARNING Decoded 0x40173051: esphome::Component::call_setup() at /home/username/Development/fw-mroom-blinds/src/esphome/core/component.cpp:63
WARNING Decoded 0x40173139: esphome::Component::call() at /home/username/Development/fw-mroom-blinds/src/esphome/core/component.cpp:82
WARNING Decoded 0x400e10cd: esphome::Application::setup() at /home/username/Development/fw-mroom-blinds/src/esphome/core/application.cpp:37
WARNING Decoded 0x400ea9aa: setup() at /home/username/Development/fw-mroom-blinds/src/main.cpp:2197
WARNING Decoded 0x400f9333: loopTask(void*) at /home/username/.platformio/packages/framework-arduinoespressif32/cores/esp32/main.cpp:14
WARNING Decoded 0x400899a5: vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:355 (discriminator 1)
[19:45:11]
[19:45:11]Core 0 register dump:
[19:45:11]PC      : 0x40089e66  PS      : 0x00060034  A0      : 0x8008a5cd  A1      : 0x3ffbbf40  
WARNING Decoded 0x40089e66: uxPortCompareSet at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/include/freertos/portmacro.h:285
 (inlined by) vPortCPUAcquireMutexIntsDisabledInternal at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/portmux_impl.inc.h:86
 (inlined by) vPortCPUAcquireMutexIntsDisabled at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/portmux_impl.h:98
 (inlined by) vPortCPUAcquireMutex at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:394
[19:45:11]A2      : 0x3ffbf3cc  A3      : 0xb33fffff  A4      : 0x00060023  A5      : 0x003fffff  
[19:45:11]A6      : 0x00060021  A7      : 0x00000000  A8      : 0x0000cdcd  A9      : 0x0000cdcd  
[19:45:11]A10     : 0x0000abab  A11     : 0x00060023  A12     : 0x00060021  A13     : 0x3ffbbff0  
[19:45:11]A14     : 0x00000003  A15     : 0x00060123  SAR     : 0x0000001d  EXCCAUSE: 0x00000006  
[19:45:11]EXCVADDR: 0x00000000  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000  
[19:45:11]
[19:45:11]Backtrace: 0x40089e66:0x3ffbbf40 0x4008a5ca:0x3ffbbf70 0x4008c208:0x3ffbbf90 0x4008c1be:0x3ffba848
WARNING Found stack trace! Trying to decode it
WARNING Decoded 0x40089e66: uxPortCompareSet at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/include/freertos/portmacro.h:285
 (inlined by) vPortCPUAcquireMutexIntsDisabledInternal at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/portmux_impl.inc.h:86
 (inlined by) vPortCPUAcquireMutexIntsDisabled at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/portmux_impl.h:98
 (inlined by) vPortCPUAcquireMutex at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:394
WARNING Decoded 0x4008a5ca: vTaskSwitchContext at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/tasks.c:3507
WARNING Decoded 0x4008c208: _frxt_dispatch at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/portasm.S:406
WARNING Decoded 0x4008c1be: _frxt_int_exit at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/portasm.S:206
[19:45:11]
[19:45:11]Rebooting...
[19:45:11]ets Jun  8 2016 00:22:57
[19:45:11]
[19:45:11]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[19:45:11]configsip: 0, SPIWP:0xee
[19:45:11]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[19:45:11]mode:DIO, clock div:2
[19:45:11]load:0x3fff0018,len:4
[19:45:11]load:0x3fff001c,len:1044
[19:45:11]load:0x40078000,len:8896
[19:45:11]load:0x40080400,len:5828
[19:45:11]entry 0x400806ac
[19:45:11][E][ota:369]: Boot loop detected. Proceeding to safe mode.
[19:45:12][W][ota:036]: Last Boot was an unhandled reset, will proceed to safe mode in 0 restarts

Additional information and things you've tried: Flash erasing doesn't help. There are PCF8574 and other errors because nothing is connected to ESP32. I don't have DHT sensors, so it's not related to https://github.com/esphome/issues/issues/1269.

DoctorOctagonapus commented 3 years ago

I have the same issue on mine, again no DHT sensor. Mine eventually boots into I'm guessing safe mode and connects to wifi, but will not talk to ESPHome over OTA. Can't upload a new flash and can't read the logs. (I'm getting the logs using serial.) I'll attach a dump of my logs.

INFO Reading configuration /config/esphome/fishtank.yaml...
INFO Detected timezone 'GMT' with UTC offset 0 and daylight savings time from 28 March 01:00:00 to 31 October 02:00:00
INFO Starting log output from /dev/ttyUSB0 with baud rate 115200
[17:27:37]ets Jun  8 2016 00:22:57
[17:27:37]
[17:27:37]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[17:27:37]configsip: 0, SPIWP:0xee
[17:27:37]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[17:27:37]mode:DIO, clock div:2
[17:27:37]load:0x3fff0018,len:4
[17:27:37]load:0x3fff001c,len:1044
[17:27:37]load:0x40078000,len:8896
[17:27:37]load:0x40080400,len:5828
[17:27:37]entry 0x400806ac
[17:27:37][I][logger:156]: Log initialized
[17:27:37][C][status_led:014]: Setting up Status LED...
[17:27:37][C][ota:364]: There have been 0 suspected unsuccessful boot attempts.
[17:27:37][I][app:028]: Running through setup()...
[17:27:37][D][binary_sensor:034]: 'Fishtank Water Level': Sending initial state OFF
[17:27:37][D][binary_sensor:034]: 'Light Switch': Sending initial state ON
[17:27:37][D][binary_sensor:034]: 'Pump Switch': Sending initial state ON
[17:27:37][C][switch.gpio:011]: Setting up GPIO Switch 'Fishtank Light'...
[17:27:37][D][switch:021]: 'Fishtank Light' Turning ON.
[17:27:37][D][switch:045]: 'Fishtank Light': Sending state ON
[17:27:37][D][switch:021]: 'Fishtank Light' Turning ON.
[17:27:37][C][switch.gpio:011]: Setting up GPIO Switch 'Fishtank Pump'...
[17:27:37][D][switch:021]: 'Fishtank Pump' Turning ON.
[17:27:37][D][switch:045]: 'Fishtank Pump': Sending state ON
[17:27:37][D][switch:021]: 'Fishtank Pump' Turning ON.
[17:27:38][C][ads1115:014]: Setting up ADS1115...
[17:27:38][W][i2c:070]: Received NACK on transmit of address 0x48
[17:27:38][E][component:092]: Component was marked as failed.
[17:27:38][C][bh1750.sensor:012]: Setting up BH1750 'Fishtank Light Level'...
[17:27:38][W][i2c:070]: Received NACK on transmit of address 0x23
[17:27:38][E][component:092]: Component was marked as failed.
[17:27:38][C][dallas.sensor:032]: Setting up DallasComponent...
[17:27:38][E][dallas.sensor:200]: Reading scratchpad failed: reset
[17:27:38][C][ssd1306_i2c:010]: Setting up I2C SSD1306...
[17:27:38][W][i2c:076]: Unknown transmit error 5 for address 0x3C
[17:27:38][E][component:092]: Component was marked as failed.
[17:27:38][C][wifi:033]: Setting up WiFi...
[17:27:38]Guru Meditation Error: Core  1 panic'ed (Interrupt wdt timeout on CPU1)
[17:27:38]Core 1 register dump:
[17:27:38]PC      : 0x4008c32a  PS      : 0x00060f34  A0      : 0x8008b4e7  A1      : 0x3ffb0df0  
INFO Need to fetch platformio IDE-data, please stand by
INFO Running:  platformio run -d /config/esphome/fishtank -t idedata
WARNING Decoded 0x4008c32a: vListInsert at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/list.c:188
[17:27:42]A2      : 0x3ffb7d7c  A3      : 0x3ffb8074  A4      : 0x00000001  A5      : 0x00000001  
[17:27:42]A6      : 0x00060f23  A7      : 0x00000000  A8      : 0x3ffb8074  A9      : 0x3ffb8074  
[17:27:42]A10     : 0x00000001  A11     : 0x00000001  A12     : 0x00000020  A13     : 0x3ffbf938  
[17:27:42]A14     : 0x00000001  A15     : 0x00000001  SAR     : 0x0000001a  EXCCAUSE: 0x00000006  
[17:27:42]EXCVADDR: 0x00000000  LBEG    : 0x40001609  LEND    : 0x4000160d  LCOUNT  : 0x00000000  
[17:27:42]
[17:27:42]Backtrace: 0x4008c32a:0x3ffb0df0 0x4008b4e4:0x3ffb0e10 0x4008976f:0x3ffb0e30 0x400ec6f2:0x3ffb0e70 0x400ec7b2:0x3ffb0e90 0x4008792a:0x3ffb0eb0 0x40087e5e:0x3ffb0ed0 0x400fdfed:0x3ffb0f40 0x400fc8b5:0x3ffb0f60 0x400fcd03:0x3ffb0f80 0x400fb68d:0x3ffb0ff0 0x400fc197:0x3ffb1040 0x400fab11:0x3ffb10a0 0x400fb1bd:0x3ffb10e0 0x40148092:0x3ffb1100 0x40148286:0x3ffb1150 0x401482d9:0x3ffb1180 0x400fe49b:0x3ffb11a0 0x400fe5ee:0x3ffb11c0 0x400eac65:0x3ffb11e0 0x400e49b8:0x3ffb1200 0x400dd125:0x3ffb1300 0x400dd184:0x3ffb1330 0x400dc4b0:0x3ffb1360 0x4015d805:0x3ffb1380 0x4015d8c1:0x3ffb13a0 0x400dea95:0x3ffb13c0 0x400e259e:0x3ffb1410 0x400e8067:0x3ffb1fb0 0x40089969:0x3ffb1fd0
WARNING Found stack trace! Trying to decode it
WARNING Decoded 0x4008c32a: vListInsert at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/list.c:188
WARNING Decoded 0x4008b4e4: vTaskPlaceOnEventList at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/tasks.c:3507
WARNING Decoded 0x4008976f: xQueueGenericReceive at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/queue.c:1996
WARNING Decoded 0x400ec6f2: esp_ipc_call_and_wait at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/ipc.c:116
WARNING Decoded 0x400ec7b2: esp_ipc_call at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/ipc.c:123
WARNING Decoded 0x4008792a: spi_flash_disable_interrupts_caches_and_other_cpu at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/spi_flash/cache_utils.c:120
WARNING Decoded 0x40087e5e: spi_flash_guard_start at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/spi_flash/flash_ops.c:162
 (inlined by) spi_flash_read at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/spi_flash/flash_ops.c:508
WARNING Decoded 0x400fdfed: nvs::nvs_flash_read(unsigned int, void*, unsigned int) at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_ops.cpp:70
WARNING Decoded 0x400fc8b5: nvs::Page::readEntry(unsigned int, nvs::Item&) const at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_page.cpp:849
WARNING Decoded 0x400fcd03: nvs::Page::findItem(unsigned char, nvs::ItemType, char const*, unsigned int&, nvs::Item&, unsigned char, nvs::VerOffset) at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_page.cpp:849
WARNING Decoded 0x400fb68d: nvs::Storage::findItem(unsigned char, nvs::ItemType, char const*, nvs::Page*&, nvs::Item&, unsigned char, nvs::VerOffset) at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_storage.cpp:557
WARNING Decoded 0x400fc197: nvs::Storage::getItemDataSize(unsigned char, nvs::ItemType, char const*, unsigned int&) at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_storage.cpp:572
WARNING Decoded 0x400fab11: nvs_get_str_or_blob(unsigned int, nvs::ItemType, char const*, void*, unsigned int*) at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_api.cpp:521
WARNING Decoded 0x400fb1bd: nvs_get_blob at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/nvs_flash/src/nvs_api.cpp:525
WARNING Decoded 0x40148092: nvs_log_init
WARNING Decoded 0x40148286: misc_nvs_load
WARNING Decoded 0x401482d9: misc_nvs_init
WARNING Decoded 0x400fe49b: wifi_init_in_caller_task
WARNING Decoded 0x400fe5ee: esp_wifi_init_internal
WARNING Decoded 0x400eac65: esp_wifi_init at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/wifi_init.c:62
WARNING Decoded 0x400e49b8: WiFiGenericClass::mode(wifi_mode_t) at /root/.platformio/packages/framework-arduinoespressif32/libraries/WiFi/src/WiFiGeneric.cpp:250
 (inlined by) espWiFiStart at /root/.platformio/packages/framework-arduinoespressif32/libraries/WiFi/src/WiFiGeneric.cpp:140
 (inlined by) WiFiGenericClass::mode(wifi_mode_t) at /root/.platformio/packages/framework-arduinoespressif32/libraries/WiFi/src/WiFiGeneric.cpp:485
WARNING Decoded 0x400dd125: esphome::wifi::WiFiComponent::wifi_mode_(esphome::optional<bool>, esphome::optional<bool>) at /config/esphome/fishtank/src/esphome/components/wifi/wifi_component_esp32.cpp:545
WARNING Decoded 0x400dd184: esphome::wifi::WiFiComponent::wifi_sta_pre_setup_() at /config/esphome/fishtank/src/esphome/components/wifi/wifi_component_esp32.cpp:545
WARNING Decoded 0x400dc4b0: esphome::wifi::WiFiComponent::setup() at /config/esphome/fishtank/src/esphome/components/wifi/wifi_component.cpp:539
WARNING Decoded 0x4015d805: esphome::Component::call_setup() at /root/.platformio/packages/toolchain-xtensa32/xtensa-esp32-elf/include/c++/5.2.0/functional:1754
WARNING Decoded 0x4015d8c1: esphome::Component::call() at /config/esphome/fishtank/src/esphome/core/component.cpp:82
WARNING Decoded 0x400dea95: esphome::Application::setup() at /config/esphome/fishtank/src/esphome/core/application.cpp:37
WARNING Decoded 0x400e259e: setup() at /config/esphome/fishtank/src/main.cpp:560
WARNING Decoded 0x400e8067: loopTask(void*) at /root/.platformio/packages/framework-arduinoespressif32/cores/esp32/main.cpp:14
WARNING Decoded 0x40089969: vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:355 (discriminator 1)
[17:27:46]
[17:27:46]Core 0 register dump:
[17:27:46]PC      : 0x40089e2a  PS      : 0x00060034  A0      : 0x8008a591  A1      : 0x3ffbbf40  
WARNING Decoded 0x40089e2a: uxPortCompareSet at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/include/freertos/portmacro.h:285
 (inlined by) vPortCPUAcquireMutexIntsDisabledInternal at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/portmux_impl.inc.h:86
 (inlined by) vPortCPUAcquireMutexIntsDisabled at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/portmux_impl.h:98
 (inlined by) vPortCPUAcquireMutex at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:394
[17:27:46]A2      : 0x3ffbf3a0  A3      : 0xb33fffff  A4      : 0x00060023  A5      : 0x003fffff  
[17:27:46]A6      : 0x00060021  A7      : 0x00000000  A8      : 0x0000cdcd  A9      : 0x0000cdcd  
[17:27:46]A10     : 0x0000abab  A11     : 0x00060023  A12     : 0x00060021  A13     : 0x3ffbbff0  
[17:27:46]A14     : 0x00000003  A15     : 0x00060f23  SAR     : 0x0000001f  EXCCAUSE: 0x00000006  
[17:27:46]EXCVADDR: 0x00000000  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000  
[17:27:46]
[17:27:46]Backtrace: 0x40089e2a:0x3ffbbf40 0x4008a58e:0x3ffbbf70 0x4008c1cc:0x3ffbbf90 0x4008c182:0x3ffbbfb0 0x4008ced7:0x00000000
WARNING Found stack trace! Trying to decode it
WARNING Decoded 0x40089e2a: uxPortCompareSet at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/include/freertos/portmacro.h:285
 (inlined by) vPortCPUAcquireMutexIntsDisabledInternal at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/portmux_impl.inc.h:86
 (inlined by) vPortCPUAcquireMutexIntsDisabled at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/portmux_impl.h:98
 (inlined by) vPortCPUAcquireMutex at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:394
WARNING Decoded 0x4008a58e: vTaskSwitchContext at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/tasks.c:3507
WARNING Decoded 0x4008c1cc: _frxt_dispatch at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/portasm.S:406
WARNING Decoded 0x4008c182: _frxt_int_exit at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/portasm.S:206
WARNING Decoded 0x4008ced7: multi_heap_free at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/heap/multi_heap_poisoning.c:315
[17:27:46]
[17:27:46]Rebooting...

From here it will boot multiple times, sometimes connecting to wifi and waiting for an OTA update that it can't receive (because ESPHome won't talk to it). Eventually it boots into safe mode but ultimately boot loops again.

I have a number of components connected to this; a sensor via an ADC, an OLED display and a light sensor all over i2c, a onewire temperature sensor, plus various binary sensors, couple of switches, couple of lights, and two GPIO controlled relays. 1.14.3 was able to handle it all without issue but I flashed it with 1.14.4 via OTA and it never worked again.

MarcoV-git commented 3 years ago

Same problem here! It does connect to Wifi, because ping is working. It seems that the internal webserver is not starting, therefor you cannot access API- nor HTTP-endpoint. OTA flashing is still working, as long as you get the firmware uploaded before the ESP reboots... ;-) Currently no FTDI at hand, so no serial logs from me... v1.14.3 is still working fine.

DoctorOctagonapus commented 3 years ago

Anyone know if it's possible to roll the firmware back to 1.14.3? I'm running mine on HassOS.

HugoVonHory commented 3 years ago

I have the same issue caused by Dallas component, after upgrade it reboots several times with "Guru Meditation Error: Core 1 panic'ed (Interrupt wdt timeout on CPU1)" and switches to safe mode. It looks it isn't wifi issue, when Dallas removed from configuration ESP32 works again (binary sensors and switch in config). 22:16:29.821 -> [I][ota:267]: OTA update finished! 22:16:29.922 -> [I][app:137]: Rebooting safely... 22:16:29.957 -> ets Jun 8 2016 00:22:57 22:16:29.957 -> 22:16:29.957 -> rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) 22:16:29.957 -> configsip: 0, SPIWP:0xee 22:16:29.957 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 22:16:29.957 -> mode:DIO, clock div:2 22:16:29.990 -> load:0x3fff0018,len:4 22:16:29.990 -> load:0x3fff001c,len:952 22:16:29.990 -> load:0x40078000,len:6084 22:16:29.990 -> load:0x40080000,len:7944 22:16:29.990 -> entry 0x40080310 22:16:30.331 -> [I][logger:156]: Log initialized 22:16:30.331 -> [C][ota:364]: There have been 0 suspected unsuccessful boot attempts. 22:16:30.331 -> [I][app:028]: Running through setup()... 22:16:30.331 -> [D][binary_sensor:034]: 'Kotel Status': Sending initial state OFF 22:16:30.331 -> [C][dallas.sensor:032]: Setting up DallasComponent... 22:16:30.366 -> [C][wifi:033]: Setting up WiFi... 22:16:30.671 -> Guru Meditation Error: Core 1 panic'ed (Interrupt wdt timeout on CPU1) 22:16:30.671 -> Core 1 register dump: 22:16:30.671 -> PC : 0x4008bac6 PS : 0x00060134 A0 : 0x8008aca3 A1 : 0x3ffb1610 22:16:30.671 -> A2 : 0x3ffb7d7c A3 : 0x3ffb8074 A4 : 0x00000001 A5 : 0x00000001 22:16:30.671 -> A6 : 0x00060123 A7 : 0x00000000 A8 : 0x3ffb8074 A9 : 0x3ffb8074 22:16:30.705 -> A10 : 0x00000001 A11 : 0x00000001 A12 : 0x00000020 A13 : 0x00000000 22:16:30.705 -> A14 : 0x00000000 A15 : 0x00000000 SAR : 0x00000002 EXCCAUSE: 0x00000006 22:16:30.705 -> EXCVADDR: 0x00000000 LBEG : 0x40001609 LEND : 0x4000160d LCOUNT : 0x00000000 22:16:30.705 -> 22:16:30.705 -> Backtrace: 0x4008bac6:0x3ffb1610 0x4008aca0:0x3ffb1630 0x40088f3b:0x3ffb1650 0x400e770a:0x3ffb1690 0x400e77ca:0x3ffb16b0 0x400870f6:0x3ffb16d0 0x4008762a:0x3ffb16f0 0x400f8f91:0x3ffb1760 0x400f7859:0x3ffb1780 0x400f7ca7:0x3ffb17a0 0x400f663d:0x3ffb1810 0x400f6a39:0x3ffb1860 0x400f6b70:0x3ffb18e0 0x400f5b0a:0x3ffb1940 0x400f616d:0x3ffb1980 0x40142d4a:0x3ffb19a0 0x40142f3e:0x3ffb19f0 0x40142f91:0x3ffb1a20 0x400f943f:0x3ffb1a40 0x400f9592:0x3ffb1a60 0x400e5c7d:0x3ffb1a80 0x400e08c8:0x3ffb1aa0 0x400da7b5:0x3ffb1ba0 0x400da814:0x3ffb1bd0 0x400d9b40:0x3ffb1c00 0x4015807d:0x3ffb1c20 0x40158139:0x3ffb1c40 0x400dc125:0x3ffb1c60 0x400de546:0x3ffb1cb0 0x400e308f:0x3ffb1fb0 0x40089135:0x3ffb1fd0 22:16:30.774 -> 22:16:30.774 -> Core 0 register dump: 22:16:30.774 -> PC : 0x400895ee PS : 0x00060034 A0 : 0x80089d4d A1 : 0x3ffbbf40 22:16:30.774 -> A2 : 0x3ffbf338 A3 : 0xb33fffff A4 : 0x00060023 A5 : 0x003fffff 22:16:30.807 -> A6 : 0x00060021 A7 : 0x00000000 A8 : 0x0000abab A9 : 0x0000cdcd 22:16:30.807 -> A10 : 0x0000abab A11 : 0x00060023 A12 : 0x00060021 A13 : 0x3ffbbff0 22:16:30.807 -> A14 : 0x00000003 A15 : 0x00060f23 SAR : 0x0000001f EXCCAUSE: 0x00000006 22:16:30.807 -> EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000 22:16:30.841 -> 22:16:30.841 -> Backtrace: 0x400895ee:0x3ffbbf40 0x40089d4a:0x3ffbbf70 0x4008b964:0x3ffbbf90 0x4008b91a:0x3ffbbfb0 0x4008c66f:0x00000000 22:16:30.841 -> 22:16:30.841 -> Rebooting...

DoctorOctagonapus commented 3 years ago

Can confirm. I have a DS18b20 sensor, mine booted fine once I commented out all the code for that and reflashed.

Can't find anything in the changelogs relating to the Dallas component, so no idea what caused it to break.

I don't have any other DS18b20s on any other devices so no way of checking if this problem also affects ESP8266s.

definitio commented 3 years ago

I have one esp8266 with ds18b20 sensor. It works fine after update. The esp32 doesn't have 1-wire sensors.

matthewcooper commented 3 years ago

This problem also affects the ethernet connection I have POE ESP32 from Olimex and updating cause them not to connect. loggs.txt

Pulli0N commented 3 years ago

I have 2 divice First:
esphome: name: meteostation platform: ESP8266 board: nodemcuv2 dallas:

After update on 1.14.4 work fine

But second: esphome: name: aqua platform: ESP32 board: esp32doit-devkit-v1 dallas:

After update send error in log WARNING Initial connection failed. The ESP might not be connected to WiFi yet (Error connecting to 10.0.0.62: [Errno 111] Connection refused). Re-Trying in 1 seconds

But it exists on the network and OTA works If I comment the dallas section everything else works fine

asaworld commented 3 years ago

I am seeing this too. 1.14.4 works fine on most of my devices but the one that has a DHT and Dallas is failing if I include either of those in the config. I am getting the same error message as above :"Guru Meditation Error: Core 1 panic'ed (Interrupt wdt timeout on CPU1)". The first entry says it is not related to the issue with DHTs but for me either of these components being present is causing the issue. Downgrading to 1.14.3 fixed this.

csmart commented 3 years ago

I have the same problem, when dallas component is enabled version 1.14.3 works but version 1.14.4 is broken.

Git bisect seems to point to commit https://github.com/esphome/esphome/commit/072b2c445cd33a13d7029e9ce36dad9122fce162 (which has a number of dallas and dht changes).

[12:12 csmart ~/code/esphome ((072b2c445cd33a13...)|BISECTING)]$ git bisect bad
072b2c445cd33a13d7029e9ce36dad9122fce162 is the first bad commit
commit 072b2c445cd33a13d7029e9ce36dad9122fce162
Author: Otto Winter <otto@otto-winter.com>
Date:   Wed Dec 4 19:30:10 2019 +0100

    Add ESP8266 core v2.6.2 (#905)

    * Add ESP8266 core v2.6.2

    * Upstream ESP8266 Wifi fixes

    * Replace disable_interrupt with InterruptLock C++ class

    * Update code to use InterruptLock

    * Lint

    * Update dht.cpp

    * Improve InterruptLock docs, mark as ICACHE_RAM_ATTR

    * Fixes

 esphome/components/dallas/dallas_component.cpp     |  68 +++++-----
 esphome/components/dallas/esp_one_wire.cpp         |  26 ++--
 esphome/components/dht/dht.cpp                     | 141 ++++++++++++---------
 esphome/components/hx711/hx711.cpp                 |  31 ++---
 .../remote_transmitter_esp8266.cpp                 |  24 ++--
 esphome/components/uart/uart.cpp                   |  39 +++---
 esphome/components/wifi/wifi_component_esp8266.cpp |  59 ++++++++-
 esphome/core/helpers.cpp                           |  28 ++--
 esphome/core/helpers.h                             |  34 ++++-
 esphome/core/preferences.cpp                       |  22 ++--
 esphome/platformio_api.py                          |   1 +
 11 files changed, 291 insertions(+), 182 deletions(-)
csmart commented 3 years ago

@OttoWinter indeed, reverting this commit solves the problem for me.

barrenechea commented 3 years ago

The same happened to me.

I'm running ESPHome on Docker. Used to have the esphome/esphome:latest tag running. Just updated today, and my sensor got to a non-working state.

Tried to revert with the esphome/esphome:1.14.3 tag, but is broken, not being able to download resources from the internet.

I "solved" it by switching to the esphome/esphome:dev tag. I guess that image does not contain the broken commit.

DoctorOctagonapus commented 3 years ago

@SebastianBar Yeah I just tried to roll back as well. Says I'm not connected to the internet and won't compile. Starting to wish I'd saved a .bin file...

rostikk80 commented 3 years ago

same here - adding DHT platform creates a boot loop.

DaveTiff commented 3 years ago

Same here wont run unless I rem out DHT sensor.

leranp commented 3 years ago

Me too

rasweh commented 3 years ago

Same here. If I comment out the DHT sensor in the yaml configuration file then the ESP32 device boots fine - as soon as I try to enable the DHT sensor in the configuration the device goes into a boot loop with a guru meditation error.

PMaxx-Gaming commented 3 years ago

Having the same issue here; hopefully its figured out soon, as my dallas sensor is integral to my device and I can't seem to find a way to rollback the update.

asaworld commented 3 years ago

For those unable to roll back. I ran pip install esphome==1.14.3 pip uninstall platformio pip install platformio rm -rf .esphome builddirformyyaml Then it works fine.

DoctorOctagonapus commented 3 years ago

@asadenton is there an equivalent set of steps for those of us running on HassOS?

mbo18 commented 3 years ago

Is there a workaround for HassOS users? On 1.14.4, can't use DHT and with 1.14.3 I can't compile. @glmnet or @OttoWinter please help

mario-tux commented 3 years ago

Remove the DHT references in the yaml of the project; rebuild it and upload using USB (also using another computer with esphome-flasher). In this ways you can use your ESP even with esphome 1.14.4 but without H&T from DHT.

mbo18 commented 3 years ago

That's what I did, but I need my DHT :)

barrenechea commented 3 years ago

@mario-tux I wouldn't say that as a proper fix for the issue.

@DoctorOctagonapus I've never used HassOS, but I'm certain that it is a Docker supervisor. Can you set Docker configurations on it? If so, my previous message should help you.

mario-tux commented 3 years ago

@SebastianBar Yes, it is just a workaround waiting for the official fix. :-)

Using HassOS and the ESPHome addons you can revert to a previous version of ESPHome. Uninstall the stable addon, install the dev one and use in the addon configuration the field esphome_version. It's a powerful tool and you can even use a build-on-the-fly branch from a generic fork on GitHub. In this case you should use something like:

{
  "esphome_version": "v1.14.3"
}

I'm not using it as I can survive without DHT sensors but I used it in the past.

mbo18 commented 3 years ago

Just tried that but ESPHome 1.14.3 contains Platform.io 4.0.3 which is obsolete and does not compile. So ESPHome 1.14.3 is dead. I will wait for a fix

mario-tux commented 3 years ago

@mbo18 this surprise me as I was thinking the all was self-contained in the addons model. I used this system to use a personal fork (with PR or fix) waiting for the official adoption. One could fork and revert the bad commitment to get a personal working version of ESPHome 1.14.4.

HugoVonHory commented 3 years ago

I have switched to dev (1.15.0) as workaround and it works fo all my configs. Waiting for official fixed version.

larrelandin commented 3 years ago

I have switched to dev (1.15.0) as workaround and it works fo all my configs. Waiting for official fixed version.

Can confirm that this worked for me as well. I first tried reverting back to 1.14.3 but got errors when uploading. Added "esphome_version: dev" to my configuration and then it worked fine.

DoctorOctagonapus commented 3 years ago

I'll have to have another go at switching to dev. I tried adding the esphome/esphome:dev tag to my instance within Portainer but it just timed out.

fribse commented 3 years ago

Darned, I seem to be dodging bullets here. I couldn't understand this issue didn't show up for me, as I have quite a few DHT22 sensors, but then I discovered that they are all connected to an esp8266, and they work fine so far. And the Dallas sensor is offline until the pool is set up next weekend :-)

fhassine commented 3 years ago

For those unable to roll back. I ran pip install esphome==1.14.3 pip uninstall platformio pip install platformio rm -rf .esphome builddirformyyaml Then it works fine.

Thanks for the hint... my pio got corrupt as well.. Do you run this in a container, or online? (i am presuming your installation is docker'ed?)

DaveTiff commented 3 years ago

How can roll back to 1.14.3 using HASSIO on a PI

Many thanks

DoctorOctagonapus commented 3 years ago

@DaveTiff If you have a snapshot from before you updated you can restore from that, however none of your configs will compile due to the broken Platform.IO dependency.

If you install the ESPHome (dev) addon, you can start that up (obviously stop the main one first) and flash your borked device with the dev firmware. That's what I ended up doing to get my bad ESP32 back on.

DaveTiff commented 3 years ago

@DaveTiff If you have a snapshot from before you updated you can restore from that, however none of your configs will compile due to the broken Platform.IO dependency.

If you install the ESPHome (dev) addon, you can start that up (obviously stop the main one first) and flash your borked device with the dev firmware. That's what I ended up doing to get my bad ESP32 back on.

Hi, Thanks for the reply, I may have a snapshot taken 4 weeks ago, I will check and look at the DEV version.

Regards, Dave

rostikk80 commented 3 years ago

Is there any visibility as to when this might be fixed? My DHT is supposed to look after the wine cellar...

Haringstad commented 3 years ago

Tried the dev version, and uncommented the DHT section. But it's still russian roulette..... Bootloop, freeze, same type of errors as already mentioned before in this tread. I truly hope this gets solved! I love my ESPHome enabled devices!

enriquefernandez commented 3 years ago

I'm having the same issue with just the Dallas sensor (no DHT). Removing the Dallas platform and sensor from the configuration completely solves the issue.

stigvi commented 3 years ago

Is there any visibility as to when this might be fixed? My DHT is supposed to look after the wine cellar...

I am also wondering about this. If the dev version solves this, why isn't a fix pushed out immediately?

JonathanTreffler commented 3 years ago

My Node MCU ESP32 also gets stuck in a bootloop, if i add a dht11 sensor to the yaml configuration. After 10 failed boots it switches to safe mode. Luckily i have only updated only one of my esp32 chips so far.

230delphi commented 3 years ago

I can confirm same behavior with Dallas components. switched to Dev branch and it is working perfectly on 1.15

glmnet commented 3 years ago

Ok, https://github.com/esphome/esphome/commit/ea652e35879e554a478422eb0832d737ca6cc26c is the commit in dev which fixes this issue introduced in 1.14.4

As you know it only affects ESP32 the components

thanks @csmart for pointing the issue.

As workaround I could only suggest to use dev version

mbo18 commented 3 years ago

\o/ This is it! I can confirm that my DHT is back online after changing those 2 lines! And I'm still on 1.14.4

mario-tux commented 3 years ago

Ok, esphome/esphome@ea652e3 is the commit in dev which fixes this issue introduced in 1.14.4

I don't understand: this looks an old commit (already in 1.14.4) dated December 2019. Do you mean that this is the bad commitment and that the fix is revert it?

glmnet commented 3 years ago

Ok, esphome/esphome@ea652e3 is the commit in dev which fixes this issue introduced in 1.14.4

I don't understand: this looks an old commit (already in 1.14.4) dated December 2019. Do you mean that this is the bad commitment and that the fix is revert it?

no, it's not in 1.14.4

mario-tux commented 3 years ago

no, it's not in 1.14.4

Ok, you are right: it's an old commit in a not merged branch. But why people says that the current dev fix the problem: does the master include this commit?

glmnet commented 3 years ago

branch master is 1.14.4 branch dev (default) is dev

jaysalazar commented 3 years ago

Wish I would have seen this sooner, updated and using Dallas sensor. Any updates on official fix?

jazlichy commented 3 years ago

I had a Dallas one wire sensor working fine under 1.14.3. Upgraded to 1.14.4 & the ESP32 would no longer connect to to wifi. I manually wiped & reflashed over USB and still the same issue under 1.14.4. I assumed the ESP32 had bricked so flashed a new ESP32 and had the same error. I then commented all Dallas entries and the ESP32 returned to life. So now it works again but I have no Dallas temp sensors.

Hope this is helpful diagnosing the issue.

Still love ESPHome, bugs and all, amazing product.

Taigar2015 commented 3 years ago

+1 for the same issue. Using de dev version solved it (I am using the Hassio add on)