You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the new iOS version the setting for Fan mode (manual or auto) is inside a sub-setting menu and it's not very easy to use siri stock voice commands to just on and off the fan
Solution
Allow a config to map on and off buttons to any of the three modes (auto, on or circ). This effectively would block users from using the third mode on homekit, but it would allow to decide of a default behavior for devices that don't have shortcuts, such as Apple TV
Alternatives
Currently the alternative is to use a siri shortcut as we can control the target mode and the fan mode. However this work around doesn't seem to work on devices like Apple TV
Additional context
No response
The text was updated successfully, but these errors were encountered:
I don't want to hide the fan, I just want a simpler fan UI, that is just On/Off, no fan mode.
My personal preference is On = On and Off = Auto. But I am sure some other people would prefer On = On and Off = Circ (which is the current implementation if the fan mode is set to Manual)
Having a simpler UI means that we can control the fan with siri voice command on simpler Apple OS like TvOS, as siri doesn't seem able to change the fan mode (auto/manual) on anything else than iOS/MacOS
Problem
With the new iOS version the setting for Fan mode (manual or auto) is inside a sub-setting menu and it's not very easy to use siri stock voice commands to just on and off the fan
Solution
Allow a config to map on and off buttons to any of the three modes (auto, on or circ). This effectively would block users from using the third mode on homekit, but it would allow to decide of a default behavior for devices that don't have shortcuts, such as Apple TV
Alternatives
Currently the alternative is to use a siri shortcut as we can control the target mode and the fan mode. However this work around doesn't seem to work on devices like Apple TV
Additional context
No response
The text was updated successfully, but these errors were encountered: