Closed shauder closed 4 years ago
Hey there @balloob, mind taking a look at this issue as its been labeled with a integration (hue
) you are listed as a codeowner for? Thanks!
This issue seems to be linked to a problem I saw after moving from 100.1 to 101.2 - I have two Hue bridges - 4 motion detectors on each - on one of them, although the motion detectors are fine the temp & lux level values all changed to 'Unknown'. Revrting to 100.1 fixed it immediately. Thanks.
I have motion sensors but they are in a box since I switched to the wyze ones. I can control all my lights still it seems but this error does not go away. The motion sensors are still paired to my bridges, I forgot to remove them, I can see if only the ones on one bridge work when I am home.
My hue motion sensor no longer shows the temp or light level values. (Ive just upgraded to 101.3). Numerous reboots / and Hassbian update made no difference. Please could your repair.
Should be fixed with https://github.com/home-assistant/home-assistant/pull/28679
Home Assistant release with the issue: 0.101.0 - Frontend version: 20191025.1 - latest
Last working Home Assistant release (if known): 0.100.3
Operating environment (Hass.io/Docker/Windows/etc.): Docker on Linux
Integration: https://www.home-assistant.io/integrations/hue
Description of problem: I am seeing a new error after upgrading. The error does not seem to prevent the Hue lights from working. I have 3 Hue hubs integrated with HA and this error appears 2 times. Seems like the error is happening only when there are more than one Hub.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant): They were setup through the Frontend UITraceback (if applicable):
I also see this error
Additional information: It still seems to connect to all 3 hubs and lights work as expected but these errors did not exist until upgrading.
I restarted many times to make sure it wasn't just a one time thing.