LD2450 `target_x_` Sensor States Become `unknown` When No Target is Detected

[Happy-Cadaver]

After updating ESPHome from 2026.2.4 to 2026.3.3, and updating the firmware for the MTR-1 to 26.3.2.1, the target_x_ sensors all become unknown when there is no target except for direction which becomes NA. This happened to both of my devices.

I have tried rolling ESPHome back to 2026.2.4 but the behaviour is the same. I have rebooted the device but the behaviour is the same. I have also tried Clean All Files, Clean Build Files, Validate, and then reinstall the firmware but the behaviour remains unchanged.

I'm including downloaded logs where I intentionally trigger the sensor and then let it go unknown, it shows the state as nan.

Please let me know if I can provide any other information, thanks.

logs_apollo-mtr-1-1215bc_logs.txt

[bharvey88]

Thanks for opening this issue! - can you help me test the PR I just submitted?

Follow these directions to switch to the beta branch then instead of typing "beta" type in "fix/ld2450-nan-when-no-target"

then save and install and confirm the entities act as they used to.

This was a breaking change in esphome that we are now working around in our yaml.

[Happy-Cadaver]

Responded in Discord, but for completeness yes the sensors now act as they used to.

Thank you!

[bharvey88]

Thanks for testing the fix and confirming, and for the detailed report with logs — made tracking this down much easier!

The fix was merged to beta in #91 and will be included in the next stable release. You can stay on the beta branch in the meantime or switch back to stable once the release goes out. Closing as completed.