Closed Wummeke closed 5 years ago
Hey there @mvn23, mind taking a look at this issue as its been labeled with a integration (opentherm_gw
) you are listed as a codeowner for? Thanks!
This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people.
This is likely related to the update of the climate component. I will take a look soon (probably tonight or later this week).
@mvn23 maybe I can save you some time:
I compared your code with another climate component and I noticed yours was missing a property. I tried to fixed it like this:
I added this on line 44
self._operation_list = [HVAC_MODE_OFF, HVAC_MODE_HEAT]
and then added this property on line 137:
def hvac_modes(self):
"""Return the list of available hvac operation modes."""
return self._operation_list
And the climate component is now loading. But it seems to be only part of the solution. At least I don't have errors anymore in my log about this component when starting HA and the component loads. But it doesn't seem to function yet.
Opened a PR to add HVAC modes. https://github.com/home-assistant/home-assistant/pull/25268
There does not seem to be a way to change the HVAC mode, so I am returning an empty list.
Looking at the code, I think that should probably always return AUTO as hvac_mode. The hvac_action should return what is currently hvac_mode since it checks if it is actively heating.
Thanks for the PR. I haven't read up a lot on the new climate component, so I may mix up some terminology here.
The OpenTherm Gateway does not support setting an operation mode (preset or hvac_mode?). It does have an 'away mode' feature but this can not be set from the serial interface. The device can only report whether or not it is active. This is implemented as preset_mode
at the moment.
The standard mode of operation of the Gateway has only a single target temperature. From what I understand, AUTO is like an auto-learning/AI mode, while HEAT_COOL has a specific target temperature range. In my opinion it is neither of those, but I also understand that this terminology is under discussion at the moment.
The actual state of the system is currently implemented as hvac_mode
, but as I understand it this should be reported under hvac_action
with the CURRENT_HVAC_*
variables as @balloob suggested.
Please let me know if my understanding of the new climate component is correct in this regard. #25268 should get the climate platform back to a working state, but we may need to make some more changes before it's fully up to date with the new climate component architecture.
In that case it should just report HVAC_MODE_HEAT (or COOL if it's cooling).
Home Assistant release with the issue: 0.96
Last working Home Assistant release (if known): 0.95 with old configuration
Operating environment (Hass.io/Docker/Windows/etc.): docker
Component/platform: opentherm_gw
Description of problem: Sonsors are added, but no climate component. In Log an error is shown
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Additional information: relevant log entries: