Am I configuring my fan input select correctly?

Configuration
1

I wanted to add a tile card to control a 6-speed fan, but wanted to use numeric buttons instead of the slider.

I have something that works well, but can someone please let me know if there’s a simpler way to do this? Or have I completed this correctly?

First I created an input_select and made my 6 speed + off options.

image
image660×806 15.8 KB

Then I created an automation so that each option changes the fan speed when selected.

image
image1378×1124 53.3 KB

Then I added a tile card and used the ‘Custom Features’ HACS integration to create a selector feature and added the 7 options to that (this part was surprisingly easy).

image
image648×171 5.46 KB

It seems like a lot of work to do something which seems quite simple and should be built in. Have I done something strange or is this the correct way to do it?

Also, what would be the best way to update the input_select option if the fan speed was set through another method like in the more info panel? Another automation to update the input_select when fan speed changes?

And if I were to expand this to other fans, would I just duplicate everything?

Thanks in advance.

2

Please share the yaml of your automation. Correctly formatted text. Not a screenshot.

You probably want something like this if using fan percentage:

triggers:
  - trigger: state
    entity_id: input_select.study_fan
    not_to:
      - unknown
      - unavailable
action:
  - action: fan.set_percentage
    target:
      entity_id: fan.study_fan
    data:
      percentage: "{{ (100 * states('input_select.study_fan')|float / 6 )|int }}"
3

For a 6 step fan you are on the right track from what I’ve experienced.

image
image836×288 66.1 KB

image
image796×284 65.6 KB

I use multiple custom cards and template sensors for button control. The SVGs are assigned to the direction and speed(not necessary and needs streamlined)

4

That’s a really clever solution. I tried implementing it with no luck unfortunately.

Either way I was more wondering whether the way to implement something seemingly simple is through the use of input selects, automations and custom integrations… which appears to be the case.

I’ve added my automation for reference. Happy for feedback on it but it’s pretty simple, which I like.

triggers:
  - trigger: state
    entity_id:
      - input_select.study_fan
    id: Study Fan Speed 0
    to: Speed 0
  - trigger: state
    entity_id:
      - input_select.study_fan
    id: Study Fan Speed 1
    to: Speed 1
  - trigger: state
    entity_id:
      - input_select.study_fan
    id: Study Fan Speed 2
    to: Speed 2
  - trigger: state
    entity_id:
      - input_select.study_fan
    id: Study Fan Speed 3
    to: Speed 3
  - trigger: state
    entity_id:
      - input_select.study_fan
    id: Study Fan Speed 4
    to: Speed 4
  - trigger: state
    entity_id:
      - input_select.study_fan
    id: Study Fan Speed 5
    to: Speed 5
  - trigger: state
    entity_id:
      - input_select.study_fan
    id: Study Fan Speed 6
    to: Speed 6
conditions: []
actions:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - Study Fan Speed 0
        sequence:
          - action: fan.set_percentage
            metadata: {}
            data:
              percentage: 0
            target:
              entity_id: fan.study_fan
      - conditions:
          - condition: trigger
            id:
              - Study Fan Speed 1
        sequence:
          - action: fan.set_percentage
            metadata: {}
            data:
              percentage: 16
            target:
              entity_id: fan.study_fan
      - conditions:
          - condition: trigger
            id:
              - Study Fan Speed 2
        sequence:
          - action: fan.set_percentage
            metadata: {}
            data:
              percentage: 33
            target:
              entity_id: fan.study_fan
      - conditions:
          - condition: trigger
            id:
              - Study Fan Speed 3
        sequence:
          - action: fan.set_percentage
            metadata: {}
            data:
              percentage: 50
            target:
              entity_id: fan.study_fan
      - conditions:
          - condition: trigger
            id:
              - Study Fan Speed 4
        sequence:
          - action: fan.set_percentage
            metadata: {}
            data:
              percentage: 66
            target:
              entity_id: fan.study_fan
      - conditions:
          - condition: trigger
            id:
              - Study Fan Speed 5
        sequence:
          - action: fan.set_percentage
            metadata: {}
            data:
              percentage: 83
            target:
              entity_id: fan.study_fan
      - conditions:
          - condition: trigger
            id:
              - Study Fan Speed 6
        sequence:
          - action: fan.set_percentage
            metadata: {}
            data:
              percentage: 100
            target:
              entity_id: fan.study_fan
mode: single

Very nice glad you found a solution.

5

If you want simple, assign each speed via a script based on the fan percentage. Then reference that script via the card button.

alias: Fan Speed 1
sequence:
  - data:
      percentage: 16
    target:
      entity_id: fan.xxxxx
    action: fan.set_percentage

If you are happy with your method then it’s a non issue

6

The states Tom expected was numeric only.
Your states have Speed 0 and so on.
Remove the Speed

Or if you want speed in the states, then use this:

"{{ (100 * states('input_select.study_fan').replace('Speed ', '') | float / 6 )|int }}"

All credit to Tom.

2 Likes
7

I actually just realised this after posting my comment and managed to get it working. Thanks for also pointing this out!

I actually tried this at first but felt like it became a bit cumbersome… but maybe I did someting wrong. I feel like I have a bit of a solution now anyway.

I still feel like this is a lot of work for something simple. Maybe just a shortcoming of hass, or just how home automation is.

Thanks all for the help. I marked Tom’s first post as solution as that’s what I ended up going with.

8

That’s all that matters :thinking:

9

It’s the result of integrating a multitude of different brands/fan types with specific features. Then you need to manage updates and bug fixes for those APIs.

10

That’s very true. I guess making sure integrations work is the more important part. I love seeing all the great work being put into home assistant with each release, definitely the best and most collaborated open source software which exists.

I completely forgot, but I still need a solution to automatically select the input_select when the fan speed changes outside of that. Basically the reverse of the automation above. I’ll have a play around with creating an automation but if anyone has a good solution I would be grateful

11

I run Modern Forms fans and the integration adjusts whether I am using HA of the MF apps.

Data is relayed between the MF app and HA. The integration DOES matters, but in most cases HA has a work around if there is no direct integration available . It just may be more convoluted as we discussed earlier.

12

What brand is your fan?

13

I actually use a Bond Bridge RF Controller, so the fans are dumb but the fan speed is tracked through the Bond service. It actually works incredibly well after recording the frequencies of the remote with the bridge.

I know I’m never going to have the physical remote synced up with the bridge, it’s impossible to do, but my plan is to get away from using the physical remote and installing mounted tablets in rooms anyway, so all fan speed commands are from HASS.

Anyway I’m pretty sure I just need the input select to change based on the fan speed, in those cases when the input select isn’t used to change the fan speed. Like if I change the speed in the entity itself.

14

Are the speeds sensors ?

15

I don’t believe so, just the percentage state of the fan speed. I’m not amazing with hass so I might be understanding wrong. Just to clarify, the bond bridge works by pressing a fan speed button on the physical remote and then recording that number in the bond app. So I’m just assigning that number from the remote to the service.

Anyway I made a small automation to change the input select option to 0 when the fan is turned off with a toggle button. I would like it to change to the last non-zero option when toggled again to back on, but not sure how to do that. I would also like to extend the functionality to all other options, but may just have to duplicate the below logic for that. However I can only see the states of on and off… Not sure how to change type to the speed percentage

Just to better explain what I’m trying to achieve

triggers:
  - type: turned_off
    device_id: df541595ac16f5fb8c951f34a1bcf71c
    entity_id: b3a31630fea7f31c7be50e75fc35bd9c
    domain: fan
    trigger: device
conditions: []
actions:
  - action: input_select.select_option
    metadata: {}
    data:
      option: "0"
    target:
      entity_id: input_select.study_fan
mode: single
17

Ah. The button labels were just 0, 1, 2 ,3… I did not suspect they had changed the names.

18

Has someone in here with a percent controlled fan tried the tile card with with the fan speed feature enabled? Features for dashboard cards - Home Assistant

Does this do everything James wants without the need for an input select and automations?

19

It works for one of my fans with 3 speeds, but not ones with 6 speeds. It uses a slider instead, which isn’t too bad but I prefer buttons.

I also want to change the icons of the buttons for my 3 speed fan, so it’s likely I will use the same setup as my 6 speed fan, once I figure out my second issue.

Edit:
I decided to just stick to the automation of making the input select 0 when fan is triggered off, without the option to trigger it on. The numbers can be pressed to turn it on. It works well enough

1 Like