-
Notifications
You must be signed in to change notification settings - Fork 23
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
Over-specified ClimateEntityFeature HVACMode(s) #137
Comments
I think this will be resolved by #155 |
@bmos Thanks. |
I now get entity does not support this service. Is this expected? I am on the latest version. I can longer turn off my Kumo's via Google. |
Changing _enable_turn_on_off_backwards_compatibility to True got things working again. |
Looks like we need to enable ClimateEntityFeature.TURN_OFF now. I can submit a PR if needed |
I am able to turn mine off and on via HA with all the latest updates. |
@bmos the issue is turning off via Google Assistant which expects to issue a climate.turn_off service call to the entity. I could also turn off directly from Home Assistant. |
Ah, got it. So perhaps the issue is with the Google Assistant integration? |
Logger: homeassistant.components.climate
Source: components/climate/init.py:354
Integration: Climate (documentation, issues)
First occurred: 9:33:20 AM (1 occurrences)
Last logged: 9:33:20 AM
Entity None (<class 'custom_components.kumo.climate.KumoThermostat'>) implements HVACMode(s): off, cool, dry, heat, fan_only and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/dlarrick/hass-kumo/issues
I think this relates to #130
The text was updated successfully, but these errors were encountered: