OpenTherm setpoint temperature does not stick

[stephan890]

The problem

the setpoint override service does not function properly with PIC firmware 5.6 and above. In fw 5.6 the CS-command expiry timer is 'fixed'. PIC documentation states : "A CS command with a value of 8 or higher must be repeated at least every minute as long as adjustment is needed." With a newer PIC firmware when I set the setpoint through the service it is set, but is is reset within 2 minutes. If I revert back to PIC fw 5.4 the setpoint stays set. It might be that the CS command was never implemented like intended by the PIC firmware and was functional because the CS-expiry timer previously updated if a PR-command was issued.

What version of Home Assistant Core has the issue?

2023.3.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

OpenTherm Gateway

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

Code owners of `opentherm_gw` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign opentherm_gw` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

opentherm_gw documentation opentherm_gw source _{^{(message by IssueLinks)}}

[mvn23]

This is a duplicate of #87097 and the behavior is by design. The repetition requirement is a safety feature to make sure the controlling program is still 'in control'. As neither Home Assistant nor pyotgw issue the CS command directly (except that we try to clear any override on a clean shutdown) but rather only do so after a specific service call, the repetition should also be handled by the automation requiring the setpoint to be maintained. This way we can make sure the automation is still working as expected and remains in control of the setpoint.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.