Closed jjvandenberg closed 1 year ago
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!
(message by CodeOwnersMention)
opentherm_gw documentation opentherm_gw source (message by IssueLinks)
Thank you for the report, but unfortunately this is done by design.
The hvac_modes
setting is a concept used by some thermostat and AC manufacturers to determine how the device controls the temperature. This setting only exists only in the controlling device and does not get transmitted to the devices it controls.
Since the OpenTherm Gateway is not a part of the thermostat, but rather sits between the thermostat and the boiler while listening to and influencing the communication between the two, it has no idea of any such concept. The best we could do in theory would be to make an educated guess as to which of the modes would fit the currently active control method(s). However, due to differences between manufacturers this guess would not always be accurate, especially since in most modes the allowed control methods are not necessarily always on
.
Finally, because these modes do not exist in the OpenTherm protocol used to communicate between the thermostat, boiler and gateway, it is impossible to determine which modes are supported on the thermostat. It is also not possible to set these modes on the thermostat from the OpenTherm Gateway. Due to the way the Home Assistant UI is designed it will always give the impression that this is a configurable item, rather than a read-only value.
Because of the above, the hvac_modes
property was not implemented in the OpenTherm Gateway integration.
Thanks for the detailed and substantiated answer. I'm going to check with the developer of the thermostat to ignore an unset hvac mode so it doesn't result in an error. Keep up the good work :-)
For reference, which thermostat are you using that is giving you an error?
Hi,
It is the really cool work of https://github.com/joBr99/nspanel-lovelace-ui
It brings lovelace items to the Sonoff NS Panel
The thermostat doesn’t recognize an empty hvac property, so it gives an error in the gui, (first pic)
Second pic is seen after manual adding ”heat” to hvac_mode, but this is reset after a minut or so.
Third picture is a screendump seen from an airco unit.
Van: mvn23 @.> Verzonden: Monday, 1 May 2023 11:11 Aan: home-assistant/core @.> CC: jjvandenberg @.>; State change @.> Onderwerp: Re: [home-assistant/core] Opentherm integration has empty HVAC property (Issue #92300)
For reference, which thermostat are you using that is giving you an error?
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/92300#issuecomment-1529507964 , or unsubscribe https://github.com/notifications/unsubscribe-auth/APYOZDVAG7HZI4NCVROVN73XD54Z7ANCNFSM6AAAAAAXRBG3U4 . You are receiving this because you modified the open/close state. https://github.com/notifications/beacon/APYOZDWSECUGMNVJ6MTRJBLXD54Z7A5CNFSM6AAAAAAXRBG3U6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS3FJYHY.gif Message ID: @. @.> >
The problem
the hvac_modes property is empty, it should contain (at least) the heat value to indicate this integration is able to control heating.
for example an airco unit has these: hvac_modes:
this is used by thermostat integrations.
What version of Home Assistant Core has the issue?
core-2023.4.6
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Supervised
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
Anything in the logs that might be useful for us?
No response
Additional information
No response