-
Notifications
You must be signed in to change notification settings - Fork 277
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
Home Assistant state changes aren't correctly sent to diyhue #835
Comments
Now I've done the other fixes the state does work - but it is slow and waits for syncs. We can do better than that by pushing changes as soon as they happen. |
This issue seems to be the same as #795 |
Same here, opening the app shows a different state the the actual state. Lights are managed with zigbee2mqtt and homeassistant. any update on this? |
Yeah, I also think this issue has been stale for a long time now. Maybe @Koenkk (the great dev of zigbee2mqtt) can help us with this? 😊 |
That would be awesome! |
I also have to issue that every change from diyHue is reflected correctly in HomeAssistant but not the other way around.
but diyHue and also the HueApp shows: The status in HomeAssistant: And I can also say: Yes, the lamp is at 100% brightness This is the log-entry in zigbee2mqtt:
Also changed the name in diyHue to the exact same name (without whitespaces), but this doesn't help, |
Should it matter if whether Home Assistant or Homebridge is used? Personally I use Homebridge and the light state is not working as it should. |
Describe the bug
Lights in diyhue should update when the light state is updated from Home Assistant. The state should also load correctly on start up / discovery.
Steps to Reproduce
Connect to Home Assistant and discover devices. All are discovered as off even if they are on.
Expected behavior
States should be correctly discovered.
Logs
Docker Info (please complete the following information):
Checklist
Additional context
I am looking into this issue with the other Home Assistant ones.
The text was updated successfully, but these errors were encountered: