Skip to content
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

Plugwise Smile Anna shows OnOff Heating incorrectly sometimes #81839

Closed
dotnetniet opened this issue Nov 9, 2022 · 4 comments · Fixed by #83345
Closed

Plugwise Smile Anna shows OnOff Heating incorrectly sometimes #81839

dotnetniet opened this issue Nov 9, 2022 · 4 comments · Fixed by #83345
Assignees

Comments

@dotnetniet
Copy link

dotnetniet commented Nov 9, 2022

The problem

I found a problem with my Plugwise Smile Anna heating binary_sensor.onoff_heating. It is showing sometimes the inverse of the actual state of the heating system.
I have an OnOff, not an OpenTherm system, so that can be the cause.

I looked at the core/domain_objects xml output and saw that the value of intended_central_heating_state was showing on, but the value of central_heating_state was off and that was the correct value.
This invalid state was shown the whole day and eventually corrected itself the next morning.

It seems that the value of intended_central_heating_state is not the correct value for an OnOff system and the central_heating_state should be used.

Screenshot_20221109-085124_DuckDuckGo

What version of Home Assistant Core has the issue?

2022.11.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Plugwise

Link to integration documentation on our website

https://www.home-assistant.io/integrations/plugwise/

Diagnostics information

config_entry-plugwise-8506b36cea71da5f80d81a6972805914.json-1-1.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Nov 9, 2022

Hey there @CoMPaTech, @bouwew, @brefra, @frenck, mind taking a look at this issue as it has been labeled with an integration (plugwise) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of plugwise can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Change the title of the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign plugwise Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


plugwise documentation
plugwise source
(message by IssueLinks)

@bouwew
Copy link
Contributor

bouwew commented Nov 9, 2022

@dotnetniet thanks for adding the detailed description.

I remember already creating some code to handle this situation but looking back at the code I see it's only implemented for the Adam + OnOff combination. Should be a quick fix to included it for the Anna + OnOff combination.

@bouwew
Copy link
Contributor

bouwew commented Nov 25, 2022

This should be fixed via #82146

@dotnetniet
Copy link
Author

@bouwew, it works great now 👌

@github-actions github-actions bot locked and limited conversation to collaborators Jan 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants