Fan control on thermostat #211
-
Beta Was this translation helpful? Give feedback.
Replies: 14 comments 3 replies
-
The "variable" speed fan control should still control you fan, even if single speed. It'll either be on or off ie: if you drag the variable speed fan to 0, it should turn off If not we can look at diagnosing further. And perhaps an option enhancement down the track could be just on/off fan support for non variable speed fans |
Beta Was this translation helpful? Give feedback.
-
That’s what I had tried, but it definitely neither responds to the fan control in the Home app nor reliably reflects the current state of the fan. Here’s where it gets interesting. In the process of collecting data I tried several combinations using the Google Home app to control the fan to see if either Home or Eve showed the current fan state. It seems I can now turn the fan on and off in the Eve app by simply setting the variable speed control under Thermostat to 100% or 0%, respectively. It definitely didn’t do this earlier. The variable fan speed that I set in the Thermostat is also reflected in the Ventilation Fan section, and the Active toggle is set as expected. Finally, I’ll note that I can’t set anything other than 0% or 100% for the fan speed in the Eve app. Even with things in this state the fan speed control in the Home app still doesn’t have any effect. I’m able to set any speed I like with no effect, and nothing is logged in Homebridge. |
Beta Was this translation helpful? Give feedback.
-
OK. I'll go back and test against my single speed fan setup first (Nest Thermostat E though) and see if thats still correct (Winter here, so no need for fan atm) After that, we can see where things are at |
Beta Was this translation helpful? Give feedback.
-
Ok. think found out why :-) small coding error Would you be happy to test an alpha channel version? Would probably need to remove the accessory from HomeBridge cache also |
Beta Was this translation helpful? Give feedback.
-
Sure, no problem. Point me in the right direction, boss. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Problem solved. Thank you! A few nice-to-have enhancements would help the non-techies in my household with the transition away from the homebridge-nest plugin:
If you’re willing to consider these, I can open one or more issues to track them. Let me know what you think. |
Beta Was this translation helpful? Give feedback.
-
That’s great to hear. I’ll look into point 1 Point 2 can already be done via HomeKit itself. the runtime is set at 15mins to align with the Nest app. Can see what effect has it makes or configurable |
Beta Was this translation helpful? Give feedback.
-
Thanks! I do see now that I can break out the fan as a separate accessory in HomeKit, as well. I had no idea. The Google Home app wants me to select a run time, then hit Run Fan. It starts at 15 minutes but has a list of times, at least on my 4th gen. |
Beta Was this translation helpful? Give feedback.
-
What range of values does it allow?? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
The current code uses what ever fan runtime has been configured via the app, so if you change the runtime via Nest App or Google Home it would us that setting. I that suitable or should it be configurable in this plugin? |
Beta Was this translation helpful? Give feedback.
-
Ah, whatever I set in the Google Home app is “sticky.” That works for me. It’s probably worth documenting that behavior explicitly. |
Beta Was this translation helpful? Give feedback.
-
Looks good to me. Thank you for taking care of this, and for your patient explanations! |
Beta Was this translation helpful? Give feedback.
try [email protected]
probably have to remove the thermostat/fan again from cache, Even though I'm removing some things internal, not quite yet reflected in HomeKit dynamically, so hence the need to remove from cache (atm)