-
-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESPHome connection closed if numeric sensor has non-numeric value #93722
Comments
Hey there @OttoWinter, @jesserockz, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) esphome documentation |
inf isn't a valid value for that unit of measurement That seems like a bug in the esphome component However it shouldn't cause a disconnection |
The problem
This issue is related to #92479 except it disconnects the whole ESPHome node, including working sensors and connects back again when the value of that specific sensor is numeric again.
If #85605 introduced this bug, please revert those changes as they prevent me from permanently upgrading from Home Assistant 2023.4.6.
The buggy sensor is "calculated_lux" component of TSL2591 Ambient Light Sensor(https://esphome.io/components/sensor/tsl2591.html#tsl2591-ambient-light-sensor). It's either "0" or "inf" at night.
Not a pressing issue on older versions of HA Core.
What version of Home Assistant Core has the issue?
2023.5.x
What was the last working version of Home Assistant Core?
2023.4.6
What type of installation are you running?
Home Assistant OS
Integration causing the issue
esphome
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
As I was testing HA 2023.5.4, i've still got a Riemann sensor reset wich shouldn't occur since #93137.
The text was updated successfully, but these errors were encountered: