Lite keeps bootlooping

[martijn-brant]

Just received my batch of Lite's, thanks for that. However, I'm having some issues with it getting stable into Hass. My Hass doesnt have bluetooth so I used the manual installation guide on the wiki. Used the website to load a non-BLE fw on the device and have it join to my wifi. It works, I can join it into Hass.

Later I tried adopting it into the ESPHome dashboard, causing it to reinstall the fw. Have been getting really weird results so I wiped the device again using the wiki page, starting fresh. However, when I reboot the device after flashing, it seems to go into bootloop. I was able to get the logs via USB:

ets Jul 29 2019 12:21:46

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:6652
ho 0 tail 12 room 4
load:0x40078000,len:15052
load:0x40080400,len:3836
entry 0x4008069c
I (29) boot: ESP-IDF 4.4.7 2nd stage bootloader
I (29) boot: compile time 23:03:48
I (29) boot: Multicore bootloader
I (32) boot: chip revision: v3.1
I (36) boot.esp32: SPI Speed      : 40MHz
I (41) boot.esp32: SPI Mode       : DIO
I (45) boot.esp32: SPI Flash Size : 4MB
I (50) boot: Enabling RNG early entropy source...
I (55) boot: Partition Table:
I (59) boot: ## Label            Usage          Type ST Offset   Length
I (66) boot:  0 otadata          OTA data         01 00 00009000 00002000
I (73) boot:  1 phy_init         RF data          01 01 0000b000 00001000
I (81) boot:  2 app0             OTA app          00 10 00010000 001c0000
I (88) boot:  3 app1             OTA app          00 11 001d0000 001c0000
I (96) boot:  4 nvs              WiFi data        01 02 00390000 0006d000
I (103) boot: End of partition table
I (108) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=32880h (206976) map
I (191) esp_image: segment 1: paddr=000428a8 vaddr=3ffb0000 size=03350h ( 13136) load
I (196) esp_image: segment 2: paddr=00045c00 vaddr=40080000 size=0a418h ( 42008) load
I (214) esp_image: segment 3: paddr=00050020 vaddr=400d0020 size=a41c0h (672192) map
I (458) esp_image: segment 4: paddr=000f41e8 vaddr=4008a418 size=0ab18h ( 43800) load
I (486) boot: Loaded app from partition at offset 0x10000
I (486) boot: Disabling RNG early entropy source...
I (498) cpu_start: Multicore app
I (498) cpu_start: Pro cpu up.
I (498) cpu_start: Starting app cpu, entry point is 0x40081f94
I (486) cpu_start: App cpu up.
I (516) cpu_start: Pro cpu start user code
I (516) cpu_start: cpu freq: 160000000
I (516) cpu_start: Application information:
I (521) cpu_start: Project name:     everything-presence-lite
I (527) cpu_start: App version:      2024.6.6
I (532) cpu_start: Compile time:     Jul 10 2024 23:03:04
I (538) cpu_start: ELF file SHA256:  2f27a2236b36d4f3...
I (544) cpu_start: ESP-IDF:          4.4.7
I (549) cpu_start: Min chip rev:     v0.0
I (554) cpu_start: Max chip rev:     v3.99 
I (558) cpu_start: Chip rev:         v3.1
I (563) heap_init: Initializing. RAM available for dynamic allocation:
I (570) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (576) heap_init: At 3FFB7C08 len 000283F8 (160 KiB): DRAM
I (583) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (589) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (595) heap_init: At 40094F30 len 0000B0D0 (44 KiB): IRAM
I (603) spi_flash: detected chip: gd
I (606) spi_flash: flash io: dio
W (610) spi_flash: Detected size(8192k) larger than the size in the binary image header(4096k). Using the size in the binary image header.
I (625) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
[I][logger:156]: Log initialized
[C][safe_mode:079]: There have been 9 suspected unsuccessful boot attempts
[D][esp32.preferences:114]: Saving 1 preferences to flash...
[D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[I][app:029]: Running through setup()...
[C][i2c.idf:017]: Setting up I2C bus...
[I][i2c.idf:252]: Performing I2C bus recovery
[D][esp-idf:000]: I (1123) gpio: GPIO[22]| InputEn: 1| OutputEn: 1| OpenDrain: 1| Pullup: 1| Pulldown: 0| Intr:0 

[D][esp-idf:000]: I (1135) gpio: GPIO[21]| InputEn: 1| OutputEn: 1| OpenDrain: 1| Pullup: 1| Pulldown: 0| Intr:0 

[C][uart.idf:073]: Setting up UART 1...
[D][esp-idf:000]: I (1170) uart: queue free spaces: 20

[C][status_led:056]: Setting up Status LED...
[D][esp-idf:000]: I (1171) gpio: GPIO[14]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 

[D][number:012]: 'Illuminance Offset': Sending state 0.000000
[D][number:012]: 'Occupancy Off Delay': Sending state 15.000000
[D][number:012]: 'Max Distance': Sending state 600.000000
[D][number:012]: 'Zone 1 Begin X': Sending state -4000.000000
[D][number:012]: 'Zone 1 End X': Sending state 4000.000000
[D][number:012]: 'Zone 1 Begin Y': Sending state 0.000000
[D][number:012]: 'Zone 1 End Y': Sending state 6000.000000
[D][number:012]: 'Zone 1 Occupancy Off Delay': Sending state 15.000000
[D][number:012]: 'Zone 2 Begin X': Sending state -4000.000000
[D][number:012]: 'Zone 2 End X': Sending state -4000.000000
[D][number:012]: 'Zone 2 Begin Y': Sending state 0.000000
[D][number:012]: 'Zone 2 End Y': Sending state 0.000000
[D][number:012]: 'Zone 2 Occupancy Off Delay': Sending state 15.000000
[D][number:012]: 'Zone 3 Begin X': Sending state -4000.000000
[D][number:012]: 'Zone 3 End X': Sending state -4000.000000
[D][number:012]: 'Zone 3 Begin Y': Sending state 0.000000
[D][number:012]: 'Zone 3 End Y': Sending state 0.000000
[D][number:012]: 'Zone 3 Occupancy Off Delay': Sending state 15.000000
[D][number:012]: 'Zone 4 Begin X': Sending state -4000.000000
[D][number:012]: 'Zone 4 End X': Sending state -4000.000000
[D][number:012]: 'Zone 4 Begin Y': Sending state 0.000000
[D][number:012]: 'Zone 4 End Y': Sending state 0.000000
[D][number:012]: 'Zone 4 Occupancy Off Delay': Sending state 15.000000
[C][light:035]: Setting up light 'ESP32 LED'...
[D][status_led:039]: 'ESP32 LED': Setting initial state
[D][status_led:050]: 'ESP32 LED': Setting state OFF
[D][light:036]: 'ESP32 LED' Setting:
[D][light:041]:   Color mode: 
[D][template.switch:046]:   Restored state OFF
[D][switch:016]: 'mmWave Bluetooth' Turning OFF.
[D][switch:012]: 'mmWave Configuration Mode' Turning ON.
[D][switch:055]: 'mmWave Configuration Mode': Sending state ON
[D][switch:055]: 'mmWave Bluetooth': Sending state OFF
[C][bh1750.sensor:041]: Setting up BH1750 'Illuminance'...
[C][wifi:047]: Setting up WiFi...
[D][esp-idf:000]: I (1382) wifi:
[D][esp-idf:000]: wifi driver task: 3ffc9160, prio:23, stack:6656, core=0
[D][esp-idf:000]: 

[D][esp-idf:000][wifi]: I (1398) system_api: Base MAC address is not set

[D][esp-idf:000][wifi]: I (1398) system_api: read default base MAC address from EFUSE

[D][esp-idf:000][wifi]: I (1411) wifi:
[D][esp-idf:000][wifi]: wifi firmware version: 1fd20f4
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (1428) wifi:
[D][esp-idf:000][wifi]: wifi certification version: v7.0
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (1449) wifi:
[D][esp-idf:000][wifi]: config NVS flash: enabled
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (1459) wifi:
[D][esp-idf:000][wifi]: config nano formating: disabled
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (1480) wifi:
[D][esp-idf:000][wifi]: Init data frame dynamic rx buffer num: 32
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (1500) wifi:
[D][esp-idf:000][wifi]: Init static rx mgmt buffer num: 5
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (1510) wifi:
[D][esp-idf:000][wifi]: Init management short buffer num: 32
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (1531) wifi:
[D][esp-idf:000][wifi]: Init dynamic tx buffer num: 32
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (1551) wifi:
[D][esp-idf:000][wifi]: Init static rx buffer size: 1600
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (1562) wifi:
[D][esp-idf:000][wifi]: Init static rx buffer num: 10
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (1582) wifi:
[D][esp-idf:000][wifi]: Init dynamic rx buffer num: 32
[D][esp-idf:000][wifi]: 

[D][esp-idf:000]: I (1603) wifi_init: rx ba win: 6

[D][esp-idf:000]: I (1604) wifi_init: tcpip mbox: 32

[D][esp-idf:000]: I (1613) wifi_init: udp mbox: 6

[D][esp-idf:000]: I (1613) wifi_init: tcp mbox: 6

[D][esp-idf:000]: I (1623) wifi_init: tcp tx win: 5760

[D][esp-idf:000]: I (1633) wifi_init: tcp rx win: 5760

[D][esp-idf:000]: I (1643) wifi_init: tcp mss: 1440

[D][esp-idf:000]: I (1643) wifi_init: WiFi IRAM OP enabled

[D][esp-idf:000]: I (1654) wifi_init: WiFi RX IRAM OP enabled

[C][wifi:060]: Starting WiFi...
[C][wifi:061]:   Local MAC: 30:C9:22:F1:B3:E8
[D][wifi:073]: Loaded saved wifi settings: wifinamecensored-NOT
[D][esp-idf:000][wifi]: I (1677) phy_init: phy_version 4791,2c4672b,Dec 20 2023,16:06:06

[D][esp-idf:000][wifi]: I (1763) wifi:
[D][esp-idf:000][wifi]: mode : sta (30:c9:22:f1:b3:e8)
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (1764) wifi:
[D][esp-idf:000][wifi]: enable tsf
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (1770) wifi:
[D][esp-idf:000][wifi]: Set ps type: 1

[D][esp-idf:000][wifi]: 

[D][wifi:481]: Starting scan...
[D][status_led:030]: Restoring light state OFF
[D][esp-idf:000][wifi]: I (1799) wifi:
[D][esp-idf:000][wifi]: Set ps type: 1

[D][esp-idf:000][wifi]: 

[W][component:157]: Component wifi set Warning flag: scanning for networks
[D][binary_sensor:036]: 'Occupancy': Sending state ON
[D][binary_sensor:036]: 'Target 1 Active': Sending state ON
[D][binary_sensor:036]: 'Target 2 Active': Sending state ON
[D][binary_sensor:036]: 'Target 3 Active': Sending state ON
[D][sensor:094]: 'Target 1 X': Sending state -4.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Y': Sending state -255.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Speed': Sending state -0.01000 m/s with 2 decimals of accuracy
[D][sensor:094]: 'Target 1 Resolution': Sending state 772.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Distance': Sending state 255.03137 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Angle': Sending state -180.89868 ° with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 X': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Y': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Speed': Sending state 0.00000 m/s with 2 decimals of accuracy
[D][sensor:094]: 'Target 2 Resolution': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Distance': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Angle': Sending state 0.00000 ° with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 X': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 Y': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 Speed': Sending state 0.00000 m/s with 2 decimals of accuracy
[D][sensor:094]: 'Target 3 Resolution': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 Distance': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 Angle': Sending state 0.00000 ° with 0 decimals of accuracy
[D][binary_sensor:036]: 'Zone 1 Occupancy': Sending state ON
[D][sensor:094]: 'Zone 1 Target Count': Sending state 2.00000  with 0 decimals of accuracy
[D][sensor:094]: 'Zone 2 Target Count': Sending state 0.00000  with 0 decimals of accuracy
[D][sensor:094]: 'Zone 3 Target Count': Sending state 0.00000  with 0 decimals of accuracy
[D][sensor:094]: 'Zone 4 Target Count': Sending state 0.00000  with 0 decimals of accuracy
[D][binary_sensor:036]: 'Target 2 Active': Sending state OFF
[D][binary_sensor:036]: 'Target 3 Active': Sending state OFF
[D][sensor:094]: 'Target 1 X': Sending state -8.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Y': Sending state -511.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Speed': Sending state 0.00000 m/s with 2 decimals of accuracy
[D][sensor:094]: 'Target 1 Resolution': Sending state 1.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Distance': Sending state 511.06262 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Angle': Sending state -180.89693 ° with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 X': Sending state -64.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Y': Sending state -772.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Speed': Sending state -2.58000 m/s with 2 decimals of accuracy
[D][sensor:094]: 'Target 2 Resolution': Sending state 16380.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Distance': Sending state 774.64832 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Angle': Sending state -184.73907 ° with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 X': Sending state -57.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 Speed': Sending state -317.72000 m/s with 2 decimals of accuracy
[D][sensor:094]: 'Target 3 Resolution': Sending state 16379.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 Distance': Sending state 57.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 Angle': Sending state 90.00000 ° with 0 decimals of accuracy
[D][sensor:094]: 'Zone 1 Target Count': Sending state 0.00000  with 0 decimals of accuracy
[D][binary_sensor:036]: 'Target 2 Active': Sending state ON
[D][binary_sensor:036]: 'Target 3 Active': Sending state ON
[D][bh1750.sensor:159]: 'Illuminance': Got illuminance=38.6lx
[D][sensor:094]: 'Illuminance': Sending state 38.59744 lx with 1 decimals of accuracy
[D][sensor:094]: 'Target 1 X': Sending state -4.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Y': Sending state -164.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Resolution': Sending state 772.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Distance': Sending state 164.04877 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Angle': Sending state -181.39719 ° with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 X': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Y': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Speed': Sending state 0.00000 m/s with 2 decimals of accuracy
[D][sensor:094]: 'Target 2 Resolution': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Distance': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Angle': Sending state 0.00000 ° with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 X': Sending state -3.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 Speed': Sending state 137.92000 m/s with 2 decimals of accuracy
[D][sensor:094]: 'Target 3 Resolution': Sending state 16400.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 Distance': Sending state 3.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Zone 1 Target Count': Sending state 2.00000  with 0 decimals of accuracy
[D][binary_sensor:036]: 'Target 2 Active': Sending state OFF
[D][wifi:496]: Found networks:
[I][wifi:540]: - 'wifinamecensored-NOT' [redacted]▂▄▆█
[D][wifi:541]:     Channel: 11
[D][wifi:542]:     RSSI: -37 dB
[I][wifi:540]: - 'wifinamecensored-NOT' [redacted]▂▄▆█
[D][wifi:541]:     Channel: 11
[D][wifi:542]:     RSSI: -71 dB
[I][wifi:540]: - 'wifinamecensored-NOT' [redacted]▂▄▆█
[D][wifi:541]:     Channel: 1
[D][wifi:542]:     RSSI: -76 dB
[D][wifi:545]: - [redacted] [redacted]▂▄▆█
[D][wifi:545]: - [redacted] [redacted]▂▄▆█
[D][wifi:545]: - [redacted] [redacted]▂▄▆█
[D][wifi:545]: - [redacted] [redacted]▂▄▆█
[D][wifi:545]: - [redacted] [redacted]▂▄▆█
[D][wifi:545]: - [redacted] [redacted]▂▄▆█
[D][wifi:545]: - [redacted] [redacted]▂▄▆█
[D][wifi:545]: - [redacted] [redacted]▂▄▆█
[I][wifi:312]: WiFi Connecting to 'wifinamecensored-NOT'...
[D][esp-idf:000][wifi]: I (4492) wifi:
[D][esp-idf:000][wifi]: new:<11,0>, old:<1,0>, ap:<255,255>, sta:<11,0>, prof:1
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (4723) wifi:
[D][esp-idf:000][wifi]: state: init -> auth (b0)
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (4729) wifi:
[D][esp-idf:000][wifi]: state: auth -> assoc (0)
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (4738) wifi:
[D][esp-idf:000][wifi]: state: assoc -> run (10)
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (4780) wifi:
[D][esp-idf:000][wifi]: connected with wifinamecensored-NOT, aid = 1, channel 11, BW20, bssid = 02:ec:da:17:b6:db
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (4781) wifi:
[D][esp-idf:000][wifi]: security: WPA2-PSK, phy: bgn, rssi: -41
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (4796) wifi:
[D][esp-idf:000][wifi]: pm start, type: 1

[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (4814) wifi:
[D][esp-idf:000][wifi]: <ba-add>idx:0 (ifx:0, 02:ec:da:17:b6:db), tid:6, ssn:2, winSize:64
[D][esp-idf:000][wifi]: 

[D][esp-idf:000][wifi]: I (4865) wifi:
[D][esp-idf:000][wifi]: AP's beacon interval = 102400 us, DTIM period = 1
[D][esp-idf:000][wifi]: 

[D][button:010]: 'Reboot mmWave Sensor' Pressed.
[D][sensor:094]: 'Target 1 X': Sending state -2.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Y': Sending state -163.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Speed': Sending state -7.72000 m/s with 2 decimals of accuracy
[D][sensor:094]: 'Target 1 Resolution': Sending state 258.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Distance': Sending state 163.01227 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 1 Angle': Sending state -180.70297 ° with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 X': Sending state -45.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Speed': Sending state -317.72000 m/s with 2 decimals of accuracy
[D][sensor:094]: 'Target 2 Resolution': Sending state 16379.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Distance': Sending state 45.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 2 Angle': Sending state 90.00000 ° with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 X': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 Speed': Sending state 0.00000 m/s with 2 decimals of accuracy
[D][sensor:094]: 'Target 3 Resolution': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 Distance': Sending state 0.00000 mm with 0 decimals of accuracy
[D][sensor:094]: 'Target 3 Angle': Sending state 0.00000 ° with 0 decimals of accuracy
[D][sensor:094]: 'Zone 1 Target Count': Sending state 1.00000  with 0 decimals of accuracy
[D][bh1750.sensor:159]: 'Illuminance': Got illuminance=38.7lx
[D][sensor:094]: 'Illuminance': Sending state 38.71063 lx with 1 decimals of accuracy
[D][binary_sensor:036]: 'Target 2 Active': Sending state ON
[D][binary_sensor:036]: 'Target 3 Active': Sending state OFF
[D][esp-idf:000][sys_evt]: I (5812) esp_netif_handlers: sta ip: 10.0.20.40, mask: 255.255.255.0, gw: 10.0.20.1

[I][wifi:616]: WiFi Connected!
[C][wifi:427]:   Local MAC: 30:C9:22:F1:B3:E8
[C][wifi:432]:   SSID: [redacted]
[C][wifi:435]:   IP Address: 10.0.20.40
[C][wifi:439]:   BSSID: [redacted]
[C][wifi:440]:   Hostname: 'everything-presence-lite-f1b3e8'
[C][wifi:442]:   Signal strength: -40 dB ▂▄▆█
[C][wifi:446]:   Channel: 11
[C][wifi:447]:   Subnet: 255.255.255.0
[C][wifi:448]:   Gateway: 10.0.20.1
[C][wifi:449]:   DNS1: 10.0.20.1
[C][wifi:450]:   DNS2: 0.0.0.0
[C][api:025]: Setting up Home Assistant API server...
[D][button:010]: 'get_mmwave_firmware' Pressed.
[D][switch:012]: 'mmWave Configuration Mode' Turning ON.
[I][app:062]: setup() finished successfully!
[D][esp-idf:000][wifi]: I (5893) wifi:
[D][esp-idf:000][wifi]: <ba-add>idx:1 (ifx:0, 02:ec:da:17:b6:db), tid:0, ssn:0, winSize:64
[D][esp-idf:000][wifi]: 

E (10873) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (10873) task_wdt:  - loopTask (CPU 0)
E (10873) task_wdt: Tasks currently running:
E (10873) task_wdt: CPU 0: IDLE0
E (10873) task_wdt: CPU 1: IDLE1
E (10873) task_wdt: Aborting.

abort() was called at PC 0x400fd1e8 on core 0


Backtrace: 0x40082966:0x3ffb0860 0x400896e5:0x3ffb0880 0x4008f89a:0x3ffb08a0 0x400fd1e8:0x3ffb0910 0x400832e9:0x3ffb0930 0x40170c83:0x3ffbace0 0x400fd939:0x3ffbad00 0x4008aabc:0x3ffbad20




ELF file SHA256: 2f27a2236b36d4f3

Rebooting...

The most important being:

E (10873) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (10873) task_wdt:  - loopTask (CPU 0)

So again, when flashing fresh FW via the wiki, the sensor works and I can add it to Hass. When opening the logs via USB, it still works. The moment you reboot the device (via the reboot button in the UI), it goes into this bootloop.

Also having a lot of issues trying to get this natively into esphome dash on my hass install but I'm guessing this bootloop is more important and could be the cause of all this.

[martijn-brant]

Another log. Flashed it via wiki, joined wifi, added to hass, seeing values in hass (sensor working), load up logs via usb via wiki page, press reboot .. get stuck in bootloop?

esp-web-tools-logs.txt

[EverythingSmartHome]

Thanks for the details, I'm not able to replicate this issue currently. Do you know if its happening on more than one unit?

[martijn-brant]

Just tried another. My exact steps:

• Open new unit from sealed box
• Open https://everythingsmarthome.github.io/everything-presence-lite/updating.html
• HA --> LD2450 --> No Bluetooth (not that it matters) --> Connect
• Connect ESP with supplied cable (tried multiple ports)
• Select device in Edge Serial connection box
• Install Everything...
• (have to hold BOOT button on ESP unit for it to be succesfull
• Flash is succesful
• Join to Wifi, works.
• Add unit to HA with IP from DHCP logs
• Sensor works in HA
• Open Logs screen on Wiki page
• Press Restart Device button
• Device goes into bootloop of 10 ~ 15 sec

Exact same result

[EverythingSmartHome]

Thanks for confirming! Does it only happen with the logs open out of interest?

[martijn-brant]

When I just power the units, the LED sometimes blinks (which it only does during boot i'm guessing?) and it pops up and drops from wifi, HA can't find it.

[martijn-brant]

I've also tried this ESPHome code rather than using the wiki, same results

substitutions:
  name: "ep-lite-f1b3e8"
  friendly_name: "ep-lite-f1b3e8"
  illuminance_update_interval: "2s"
  hidden_ssid: "false"
  log_level: VERBOSE

packages:
  # Git repo examples
  everything-presence-lite-ha:
    url: https://github.com/EverythingSmartHome/everything-presence-lite/
    ref: main # optional
    files: [everything-presence-lite-ha.yaml]
    refresh: 1d # optional

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

[martijn-brant]

To add to this: ESPHome 2024.6.6

[martijn-brant]

OK, so I think Wifi is part of the problem. When Googling into that exact error, I found some references to Wifi. I was connecting this to an isolated vlan, with no access to internet or LAN.. only to HA itself. When I supply my main wifi creds (without any restrictions), it seems to work just fine. This is very weird to me.

[martijn-brant]

The reboot of the device seems to be related to wifi not being able to find clients/HA(?) and thus it throws a reboot it seems. Searching for idx:1 (ifx:0, 02:ec:da:17:b6:db), tid:0, ssn:0, winSize:64 and esphome seems to find a few GH issues with similar issues but no solution. I also tried an internet-connected VLAN wifi that can't talk to LAN but can talk to HA and internet and that seems to work as well. The non-working wifi network has identical settings and other esphome devices have no issues with this network at all.

[martijn-brant]

Hmm I don't think it's wifi.. it seems to be firewall related. When I change my isolation rule for the "Network of Things" wifi network (aka no internet, no LAN, only access to HA) to Allow instead of Drop, the boot loop goes away and the sensor works just fine. However when I block it again, it goes into bootloop. I saw in the firewall logging it's trying to access 185.199.110.153 which resolves to GitHub Pages. Could it be trying to parse an update manifest and when it can't access that, it fails?

Just tested with this ESPHome template (basically taking the external URLs out if it) and now it works just fine even with the firewall blocking everything.

substitutions:
  name: "ep-lite-f1b3e8"
  friendly_name: "ep-lite-f1b3e8"
  illuminance_update_interval: "2s"
  hidden_ssid: "false"
  log_level: DEBUG

# packages:
#   # Git repo examples
#   everything-presence-lite-ha:
#     url: https://github.com/EverythingSmartHome/everything-presence-lite/
#     ref: main # optional
#     files: [everything-presence-lite-ha-no-ble.yaml]
#     refresh: 1d # optional



wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  #power_save_mode: NONE
  #fast_connect: TRUE
  
# update:
#   - platform: http_request
#     id: update_http_request
#     name: Firmware
#     source: https://everythingsmarthome.github.io/everything-presence-lite/everything-presence-lite-ha-manifest.json


dashboard_import:
  package_import_url: github://everythingsmarthome/everything-presence-lite/everything-presence-lite-ha.yaml@main
  import_full_config: false # or true



packages:
  device_base:
    url: https://github.com/EverythingSmartHome/everything-presence-lite/
    file: common/everything-presence-lite-base.yaml
  ld2450_base:
    url: https://github.com/EverythingSmartHome/everything-presence-lite/
    file: common/ld2450-base.yaml
  # bluetooth_base:
  #   url: https://github.com/EverythingSmartHome/everything-presence-lite/
  #   file: common/bluetooth-base.yaml

Is this an ESPHome bug for update: or dashboard_import: components?

Edit: Simplified code with package references.

[martijn-brant]

The dashboard_import sections seems the have no effect on anything. The update: section triggers the bootloops. I've been looking into the esphome docs on update: but can't find anything on debug logging for it or for it to fail gracefully.

[EverythingSmartHome]

Thanks for the updates and investigation. I would suspect from what you describe it's possibly a bug in relation to the new update mechanism in ESPHome, the http_request component.

This would really need to be reported upstream to ESPHome as this isn't related to hardware or anything specific with custom EP1 code (from what you described)

[MrMDavidson]

I've the same issue and have a similarly configured network. An interim option people can do, so they don't have to copy/paste the entire source YAML from @EverythingSmartHome into their own projects is to use the !remove functionality of ESPHome.

1. Adopt the device as per normal
2. Edit the YAML of the adopted device. Add the following somewhere in the YAML as a top-level-item (ie. update has no spaces before it on the line)

update:
  - platform: http_request
    id: !remove update_http_request

3. Do a Clean Build Files
4. Install - Note: If your device is bootlooping you'll probably have to install this over USB.

Disclaimer: I've not played around with the http_request update component so I'm not sure what impact this will have. I presume it'll still grab the latest on a rebuild but you'll lose update notifications of any upstream EverythingSmartHome changes.

[vhsdream]

Confirming I also have the same issue, with an EPL flashed with the non-BLE firmware. For me it really only happened when I attempted to update. I did get a notification to update, attempted it, and then the bootloop occurred. Had to open the case and reinstall fresh while pressing the boot button as it was continued to bootloop via USB - the serial connection would appear and then disappear over and over.

[EverythingSmartHome]

When you did the update, was that from your own ESPHome addon?

Also, this issue is related to when internet is blocked, is internet blocked on your device?

[vhsdream]

When you did the update, was that from your own ESPHome addon?

Also, this issue is related to when internet is blocked, is internet blocked on your device?

Hi there,

Yes it was via the update notification:

It appears the update goes through, but then connection drops. I then am unable to even connect via USB unless I crack the case and hold the boot button.

The device is on a separate VLAN but is not restricted from the internet.

[EverythingSmartHome]

Can you please check the logs over USB when this occurs? You should be able to do this without opening the case.

[shresth45]

Confirming I also have the same issue, with an EPL flashed with the non-BLE firmware. For me it really only happened when I attempted to update. I did get a notification to update, attempted it, and then the bootloop occurred. Had to open the case and reinstall fresh while pressing the boot button as it was continued to bootloop via USB - the serial connection would appear and then disappear over and over.

Exactly the same situation here

[EverythingSmartHome]

This should now be resolved in #122, please update to version 1.0.7. A fix is coming in ESPHome 2024.7.2 but this workaround does the same thing for now.

[grigi]

I am experiencing the same issue as described here, I installed your version 1.0.7 and it doesn't resolve it.
It still bootloops all the time.

I'll try martjin's suggested workaround.

Update: His workaround works.

[dsander]

I just hit the same problem, even with ESPHome 2024.7.2 the device does not work without giving it internet access. This is very confusing to me, are there only a few people denying internet access to their ESPHome devices? I could not find anything in their issue tracker.

Didn't spend too much time on the issue because it seems obvious, but maybe I am missing something esphome/issues#6104

[cptquad]

I just got a pair of these today, it worked ok out of the box but when I imported the config into esphome and flashed it the boot loop started.

I am also running an isolated network with internet access blocked.

martijn's workaround works for me too :)

[mlauweri]

I just received a pair of these as well and I'm also suffering from the bootloop issue, in case I connect them to my NoT (Network of Things, i.e. only local access/no internet access) network .
The bootloop also persists on my IoT network
The device only works on my main network and my guest network.
Disabling my firewall rules for my NoT and IoT networks on my router don't seem to help, so I'm a bit puzzled, especially since the device is running the latest firmware: 1.0.8 (ESPHome 2024.7.3).

Anybody has any clue how to get this device working on a NoT network?

[martijn-brant]

@mlauweri Take a look at my post here to have a short code snippet that takes out the update check and dashboard referrence. This makes it 100% local, no issues: #114 (comment)

[mlauweri]

@mlauweri Take a look at my post here to have a short code snippet that takes out the update check and dashboard referrence. This makes it 100% local, no issues: #114 (comment)

Thanks Martijn, somehow I was expecting the new firmware to be fixing the issue.
Anyway I can confirm that applying your template as a workaround has fixed the issue. :)

[wneessen]

I have occasional boot loops too. Contrary to the others I do not have a limited network for that device. I checked my DNS logs and the device is fetching the https://everythingsmarthome.github.io URL just fine every 5-10 minutes.

The sensor worked fine all day yesterday but just 30 minutes ago it went into the same boot loop like described here: #114 (comment)

After like 15 minutes of looping it finally connected again and is providing data to HASS.

I received the devices two Friday. Only one seems to be having the issue so far, the 2nd device hasn't run into a boot loop yet.

[wneessen]

Apparently tonight at around 1pm it was also unavailable for like 10 minutes.