Closed erkr closed 1 year ago
Hey there @balloob, @marcelveldt, mind taking a look at this issue as it has been labeled with an integration (hue
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
hue documentation hue source (message by IssueLinks)
This may be an incidental fluke where the color temperature was reported as 0 by the light. For example during a firmware update or a 3rd party Hue light not compliant to specs. Please keep an eye on it of the error returns or was just a one time thing. We do not have control over the data integrity. If Hue reports a value of 0 for the color temperature (which does not exist), than this error will popup. If this is something happening more often we can place a workaround for it in our code.
See https://github.com/home-assistant/core/issues/83969 I have it after the Hue Bridge update 1.55.195082050.
@erkr Do you also have NON-Philips bulbs? See https://github.com/home-assistant/core/issues/83969
@marcelveldt 👍 @Beer17HWAM yes I have many non Phipps devices, including some colour led strips
The problem
I noticed a divide by zero exception thrown by a HUE Integration event handler. It just happened while navigation in the front end (no control of lights). Not seen before. But there was not much flight time with core versions 2022.12.1 and 2022.12.3
What version of Home Assistant Core has the issue?
Core-2022.12.4
What was the last working version of Home Assistant Core?
Core-2022.11.*
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Philips HUE
Link to integration documentation on our website
https://www.home-assistant.io/integrations/hue/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response