-
Notifications
You must be signed in to change notification settings - Fork 29
On/Off switch not in sync #68
Comments
Hmm, operation state is "ready" but power state is "off". I assume one of them is wrong. Can you monitor the event stream (e.g. by enabling debug logging) in which order and at what times which of those is reported? |
The power state is wrong. |
@DavidMStraub how can I give you the log file? |
If you don't want to host it here because it contains sensitive information, you can send it to me via the e-mail address you can see in the git commits. Otherwise, just post it here or in a Gist. |
Can I send it to the @tum address? |
@DavidMStraub are there any news? |
Hi, I finally had a look at the log file. The power state remains "Standby" all the time. I suspect that the event stream simply doesn't update this setting. Does the switch go to "on" state at all at any point? What happens when you manually switch it "on"? |
If the coffemaker is on and the switch is off, the switch goes back to off, if I toggle it. |
Curious. Right now, the pseudo code for determining the power state is as follows,
Your problem could probably be fixed by changing the order of the 2nd and 3rd if statement, since your machine reports an updated operation state, but not power state. The problem is that I'm not sure whether this won't screw up any other devices, e.g. if the update their power state but not their operation state. The best solution would be to check which value was changed most recently, but unfortunately this would require quite some refactoring of the underlying library. |
I have changed the order in switch.py (from line 142) and will test.
|
It was not working. |
I found out, it is only if I switch the maschine on directly on the maschine. If I switch it on with the home connect app or with ha, the switch state is right. |
Hi @DavidMStraub. |
Hi @DavidMStraub, I have more appliance connected to home assistant, the problme persist only for caffe maker, and only if I turn ON by the button on the machine like @Krocko reported. Maibe this log can help you to find the problem. homeconnect_app.txt Many Thanks for your job, I'm avalible to made some trobleshotting test. Reagards Ivan |
In the |
Yes I see, I don't know where the integration take this value... the postam response always correct "PowerState.on", I don't know where cache it. |
Oh OK, perhaps the value is fetched initially by Can you post a log where the actual API response is shown, perhaps using Postman or the |
Hi David in attacched debug log (homeassistant core and home_conect_beta) about the turn on caffe machine by button, following the output from postman, look like good: |
Hi. Are there any news on this? |
To me, this looks like a bug in the firmware of your coffee machine. The messages show LocalControlActive going true, and then back to false. The docs say this will go back to false after a period of time, rather than after an action completing. However OperationState and PowerState never change, even though ProgramProgress is increasing. It may be worth contacting Siemens to see if there is an update that can be applied. |
I don't think it is a bug in the coffee maker firmware. |
I have a Siemens coffee maker.
The attributes are right, but the on/off switch not.
The text was updated successfully, but these errors were encountered: