-
Notifications
You must be signed in to change notification settings - Fork 38
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
Fan Comfort-Breeze Preset-Mode not working #108
Comments
I am not sure if exploding banana changed, it but that is not the correct format for a service call that used to work. The service call can only submit a single: function, functionclass, value set. If you figure out the right calls, you need to send each line individually. However, if you set the preset correctly, the API should I updated to latest 3.2.0 and services do not seem to be working at all for me. Maybe the change to "actions" is causing an issue. |
oops. sorry, I was going to reply then hit wrong button. just setting the presetmode should set those automatically. I just updated to 3.2.0 and "actions" do not work at all for me (they do not even show up). Maybe the change from services to actions messed something up. |
Closing as its a duplicate of #94 |
The more I think about this, I am not sure its related to services. Re-opening |
After reviewing the actions docs for fans @ https://www.home-assistant.io/integrations/fan/#action-fanturn_on, I am not sure you can set all of those things in a single call in HA. Here is how I can turn on the fan with comfort breeze action: fan.turn_on
target:
device_id:
- ff14ba93017f3f0b5084bb384120f652
data:
preset_mode: breeze |
@niharmehta I am going to close this issue for now. Please re-open it if the issue persists with 4.1.1 or later (this had a small fix for preset). |
Thank you! Will test it out this weekend. |
Using Hubspace supported Tager fan. Speed and direction in service calls and button works fine.
However, within the UI or service calls to start 'comfort-breeze' preset mode, does not work. When activating this in the Hubspace App, the preset-mode state changes to 'breeze' :
The text was updated successfully, but these errors were encountered: