-
Notifications
You must be signed in to change notification settings - Fork 21
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
PowerState not updated #103
Comments
It sounds almost as if it's a hard power off rather than a suspend/soft power off? |
i send the command over mqtt. The Homeconnect-app shows "Standby". So there is no hardpower off |
Have you got the devices.json output? There maybe another field other than powerstate that reflects the change? The logs would also probably show what state gets updated when you send the power off command. |
if i look in homeassistant, last 10 messages, it got the PowerState 'On', or PowerState: Standby. Could there be an issue, that "StandBy" is not recognized? Last Received MQTT State:
|
It looks like its defined as a binary, so probably can't handle Standby at the moment! |
https://api-docs.home-connect.com/settings/#power-state Probably a breaking change to update, as I suspect a lot of automations look at PowerState |
I try to use this integration with my coffeemaker.
On thing i recognized, the PowerState never changes.
If i turn off my coffeemaker, the state in Homeassistant is always "on".
If i turn it off, reload the add-on in homeassistant, the state changes to standby.
Is there any workaround or possible fix?
The text was updated successfully, but these errors were encountered: