-
Notifications
You must be signed in to change notification settings - Fork 29
Feature request: Implement hood controls under the fan domain #80
Comments
Good idea. Since my hood is dumb, this and #57 would benefit from a volunteer. |
I can try and give it a go, but can't promise that I'll get very far |
Not sure what's the best way to map Home Connect fan programs/options/settings to the available Fan speed_list of HA. HA fan speed_list: SPEED_OFF, SPEED_LOW, SPEED_MEDIUM, SPEED_HIGH. HC fan program options: Automatic mode, Fan Setting, Fan Run-on (Delayed shut off) The availability of HC Fan programs/options/settings differ per model, which make the mapping extra challenging. Any ideas / proposals? |
For mapping values to each other, arbitrarily picking the lowest (FanStage01), highest (IntensiveStage2) and something in the middle and mapping them to HA values would be a workable compromise IMHO (I can see how different HC options would make this a pain though) There's a hacky solution which is to use the template fan and hide the switch entities |
In any case, the fine-grained options will always be available through service calls, right? So having only limited (and somewhat arbitrary) options available through the fan integration seems justifyable. |
I do not know how to use a service call in combination with HC. |
I meant the services that are part of the beta version: see here I thought that perhaps with |
OK, I will give it a try. |
I think that hood controls (power, speed) would be more correctly placed as a fan in Home Assistant rather than a switch
The text was updated successfully, but these errors were encountered: