LD2450 Not Communicating after firmware update

[thegreatco]

So this all started with the occupancy sensor reporting 'Unknown' in Home Assistant. I read through the troubleshooting docs and it recommended updating the LD2450 firmware. So I upgraded the firmware first to to v2.14.25112412 and the logs were filled with:

[W][LD2450:1172]: Expected 30 bytes but received 150!

So I figured that was too new, so I installed the v2.04.23101915 firmware and now I get

[W][LD2450:1172]: Expected 30 bytes but received 46!
[W][LD2450:1172]: Expected 30 bytes but received 46!
[W][LD2450:1172]: Expected 30 bytes but received 46!
[W][LD2450:1172]: Expected 30 bytes but received 45!
[W][LD2450:1172]: Expected 30 bytes but received 47!
[W][LD2450:1172]: Expected 30 bytes but received 47!

I tried flashing directly from ESPHome as well as your website, but I still encounter the error. This is happening on all 4 of my Everything Presence Lite devices.

[thegreatco]

I was able to get the LD2450 to start talking again after using the HLKRadarTool to do a factory reset on the sensor. But if I try to toggle the mmWave Bluetooth switch on I get a bunch of warnings in the logs

[12:44:44.558][D][switch:022]: 'mmWave Bluetooth' Turning ON.
[12:44:44.622][D][switch:022]: 'mmWave Configuration Mode' Turning ON.
[12:44:44.622][D][switch:065]: 'mmWave Configuration Mode' >> ON
[12:44:44.622][D][switch:065]: 'mmWave Bluetooth' >> ON
[12:44:45.153][D][bh1750.sensor:157]: 'Illuminance': Illuminance=36.3lx
[12:44:46.594][W][LD2450:1172]: Expected 30 bytes but received 14!
[12:44:47.125][D][bh1750.sensor:157]: 'Illuminance': Illuminance=36.3lx
[12:44:48.639][D][button:022]: 'Reboot mmWave Sensor' Pressed.
[12:44:48.654][D][switch:022]: 'mmWave Configuration Mode' Turning ON.
[12:44:48.654][W][LD2450:1172]: Expected 30 bytes but received 14!
[12:44:49.163][D][bh1750.sensor:157]: 'Illuminance': Illuminance=36.2lx
[12:44:49.666][W][LD2450:1172]: Expected 30 bytes but received 12!
[12:44:50.606][D][switch:026]: 'mmWave Configuration Mode' Turning OFF.
[12:44:50.703][D][switch:065]: 'mmWave Configuration Mode' >> OFF
[12:44:50.703][W][LD2450:1172]: Expected 30 bytes but received 12!
[12:44:51.176][D][bh1750.sensor:157]: 'Illuminance': Illuminance=36.2lx
[12:44:51.486][D][sensor:129]: 'Target 1 Resolution' >> 0 mm
[12:44:51.525][D][sensor:129]: 'Target 1 Distance' >> 0 mm
[12:44:51.525][D][sensor:129]: 'Target 1 Angle' >> 0 °

If I turn it off:

[12:45:24.387][D][switch:026]: 'mmWave Bluetooth' Turning OFF.
[12:45:24.459][D][switch:022]: 'mmWave Configuration Mode' Turning ON.
[12:45:24.459][D][switch:065]: 'mmWave Configuration Mode' >> ON
[12:45:24.459][D][switch:065]: 'mmWave Bluetooth' >> OFF
[12:45:25.198][D][bh1750.sensor:157]: 'Illuminance': Illuminance=23.0lx
[12:45:25.210][D][sensor:129]: 'Illuminance' >> 23 lx
[12:45:26.336][W][LD2450:1172]: Expected 30 bytes but received 14!
[12:45:27.220][D][bh1750.sensor:157]: 'Illuminance': Illuminance=20.6lx
[12:45:27.266][D][sensor:129]: 'Illuminance' >> 21 lx
[12:45:28.346][D][button:022]: 'Reboot mmWave Sensor' Pressed.
[12:45:28.391][D][switch:022]: 'mmWave Configuration Mode' Turning ON.
[12:45:28.391][W][LD2450:1172]: Expected 30 bytes but received 14!
[12:45:29.194][D][bh1750.sensor:157]: 'Illuminance': Illuminance=19.7lx
[12:45:29.395][W][LD2450:1172]: Expected 30 bytes but received 12!
[12:45:30.330][D][switch:026]: 'mmWave Configuration Mode' Turning OFF.
[12:45:30.398][D][switch:065]: 'mmWave Configuration Mode' >> OFF
[12:45:30.398][W][LD2450:1172]: Expected 30 bytes but received 12!
[12:45:31.111][D][sensor:129]: 'Target 1 Speed' >> 0.00 m/s
[12:45:31.115][D][sensor:129]: 'Target 1 Resolution' >> 0 mm
[12:45:31.115][D][sensor:129]: 'Target 1 Distance' >> 0 mm
[12:45:31.115][D][sensor:129]: 'Target 1 Angle' >> 0 °

It eventually recovers and starts returning tracking data, but the bluetooth never turns off as the device is still visible in the HLKRadarTool app.

If I try to press the Factory Reset mmWave Sensor button, I get:

[12:48:22.221][D][button:022]: 'Factory Reset mmWave Sensor' Pressed.
[12:48:22.221][D][main:563]: Performing Factory Reset
[12:48:22.221][D][switch:022]: 'mmWave Configuration Mode' Turning ON.
[12:48:22.221][D][switch:065]: 'mmWave Configuration Mode' >> ON
[12:48:22.437][D][bh1750.sensor:157]: 'Illuminance': Illuminance=33.8lx
[12:48:24.102][W][LD2450:1172]: Expected 30 bytes but received 12!
[12:48:24.407][D][bh1750.sensor:157]: 'Illuminance': Illuminance=33.8lx
[12:48:26.117][D][switch:026]: 'mmWave Configuration Mode' Turning OFF.
[12:48:26.142][D][switch:065]: 'mmWave Configuration Mode' >> OFF
[12:48:26.142][W][LD2450:1172]: Expected 30 bytes but received 12!
[12:48:26.433][D][bh1750.sensor:157]: 'Illuminance': Illuminance=33.6lx
[12:48:26.757][D][sensor:129]: 'Target 1 Angle' >> 16 °
[12:48:26.757][D][sensor:129]: 'Target 1 Distance' >> 348 mm
[12:48:26.757][D][sensor:129]: 'Target 1 X' >> -96 mm
[12:48:26.757][D][sensor:129]: 'Target 1 Y' >> 334 mm

And it didn't work when I tried it, it only through the HLKRadarTool app.

[Richspr]

Hi Lewis, I have a similar issue, I have been trying to install the v1.4.2 firmware, When using the installer page linked from the Zone config app. It see the device and then goes thought the steps of set up but then it just keeps going round in a loop. Asking do you want to install the updates, etc.
Logs gives this:
[13:03:05]rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]ets Jul 29 2019 12:21:46
[13:03:05]
[13:03:05]rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]ets Jul 29 2019 12:21:46
[13:03:05]
[13:03:05]rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]invalid header: 0xffffffff
[13:03:05]ets Jul 29 2019 12:21:46

Now can't see the device Zone app

[tylerasselin]

Looks like I'm experiencing this issue as well. One of my EPL devices' Occupancy started going Unknown yesterday around mid-day. My other EPL device hasn't displayed this behavior yet.

Occupancy will show again for a while If I unplug the device for some time and then plug it back in, but the Unknown behavior does return. I updated the mmWave sensor firmware using the HLKRadarTool. The device logs are showing a bunch of these now:

[08:59:47.768][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:48.075][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:48.417][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:48.633][D][bh1750.sensor:157]: 'Illuminance': Illuminance=1.5lx
[08:59:48.711][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:49.099][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:49.412][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:49.750][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:50.122][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:50.460][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:50.640][D][bh1750.sensor:157]: 'Illuminance': Illuminance=1.5lx
[08:59:50.757][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:51.149][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:51.470][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:51.863][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:52.190][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:52.509][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:52.682][D][bh1750.sensor:157]: 'Illuminance': Illuminance=1.5lx
[08:59:52.887][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:53.194][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:53.503][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:53.854][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:54.217][W][LD2450:1172]: Expected 30 bytes but received 150!
[08:59:54.550][W][LD2450:1172]: Expected 30 bytes but received 150!

EDIT: I was able to get things working again after factory resetting the mmWave sensor with the HLKRadarTool app

[ABdataman]

Same issue here, installed the v1.4.2 HA | LD2450 | Bluetooth Enabled | No CO2 Module firmware following the instructions, now the device is non-functional

[10:47:09]rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[10:47:09]invalid header: 0xffffffff
[10:47:09]invalid header: 0xffffffff
[10:47:09]invalid header: 0xffffffff
[10:47:09]invalid header: 0xffffffff
[10:47:09]invalid header: 0xffffffff
[10:47:09]invalid header: 0xffffffff
[10:47:09]invalid header: 0xffffffff

Appears not to be an isolated issue.

[EverythingSmartHome]

So this all started with the occupancy sensor reporting 'Unknown' in Home Assistant. I read through the troubleshooting docs and it recommended updating the LD2450 firmware. So I upgraded the firmware first to to v2.14.25112412 and the logs were filled with:

[W][LD2450:1172]: Expected 30 bytes but received 150!

So I figured that was too new, so I installed the v2.04.23101915 firmware and now I get

[W][LD2450:1172]: Expected 30 bytes but received 46!
[W][LD2450:1172]: Expected 30 bytes but received 46!
[W][LD2450:1172]: Expected 30 bytes but received 46!
[W][LD2450:1172]: Expected 30 bytes but received 45!
[W][LD2450:1172]: Expected 30 bytes but received 47!
[W][LD2450:1172]: Expected 30 bytes but received 47!

I tried flashing directly from ESPHome as well as your website, but I still encounter the error. This is happening on all 4 of my Everything Presence Lite devices.

The original issue here is updating to 2.14, there is a note in the docs specifically about this version and how it changes the baud rate: https://docs.everythingsmart.io/s/products/doc/how-to-update-ld2450-firmware-hag7PcYn8N#h-update-the-firmware-using-the-hlkradartool-app

The other warnings are fine and nothing to be concerned about when pressing the bluetooth or factory reset buttons, so long as they aren't appearing during normal tracking.

[EverythingSmartHome]

@Richspr @ABdataman these are very different issues not related to the OP - can you please flash from the docs here: https://docs.everythingsmart.io/s/products/doc/restore-or-update-your-epl-to-factory-settings-using-a-computer-orj7PBBOJZ

This should resolve the issue

[Richspr]

Hi thanks for the info, I have now re flashed the unit and it back working. Not sure why this went wrong but pleased its is back and working.
Thanks again.

[EverythingSmartHome]

Closing this one off as the original issue here was the unsupported LD2450 firmware path, and the later warnings shown during Bluetooth/config mode are expected transient warnings rather than a separate EPL bug. The current docs already cover both the supported LD2450 firmware path and the restore/reflash route if the device gets into a bad state:\n\n- https://docs.everythingsmart.io/s/products/doc/how-to-update-ld2450-firmware-hag7PcYn8N\n- https://docs.everythingsmart.io/s/products/doc/restore-or-update-your-epl-to-factory-settings-using-a-computer-orj7PBBOJZ