Lovelace Fan Control Entity Row

petro · December 26, 2019, 6:49pm

your speed template is set up incorrectly.

Three4Nine · December 26, 2019, 8:34pm

I ended up finding the previous forum to this and that card had a mod for my zigbee fan. Just doing some work on the custom themes from this project to get the colors right now.

tomgreene · January 8, 2020, 2:56pm

I have implemented this with Lutron PD-FSQN and it will always set the speed to medium, despite the entity showing that the states are off,low,medium,high. Do I need to do something else for this device to get the entity row plugin to work properly?

finity · January 9, 2020, 2:18am

I don’t have one of those devices so it’ll be hard for me to say exactly what the issue is.

what platform doers that device use? zwave, mqtt, etc?

Did you have to code the config for the fan controller or did it create a “fan.” entity in HA automatically?

tomgreene · January 9, 2020, 12:19pm

Being a Lutron device, I’m not even sure how to answer the question of what type of device it is. They are auto-configured with the Lutron bridge integration into HA. But yes, just auto-configured by HA.

petro · January 9, 2020, 12:37pm

That’s the answer

finity · January 9, 2020, 1:49pm

I’m assuming that the integration creates a fan entity in HA that has three speeds (and “off”) that are controllable from the pop-up box?

what is the state of the fan entity when the fan is running in some speed? is the state “on” or is it the selected speed?

tomgreene · January 9, 2020, 2:05pm

Yes the integration creates the fan entity with the 3 speeds and off. They are controllable through the box and they work properly that way. Additionally when I set it to low or high through the other card, the speed in the Fan Control Entity Row card updates properly. It’s just setting the speed through this card that is apparently causing me issues!

State is: “on” and the attribute of ‘speed’ takes on low, medium or high.

finity · January 10, 2020, 2:34am

without being able to see the messages being sent around I’m not sure I can even begin to troubleshoot this issue.

I see no reason that particular fan controller should work any differently than any other 3 speed fan entity in HA. And as far as I know I haven’t heard of anyone else experiencing similar issues with it.

Can you see the commands being sent between HA and your hub when you change the speeds using the entity row and compare that to the commands when you use the pop up box?

as an alternative, you could create an MQTT template fan and use that to switch the actual fan entity speeds but then you will end up with two entities controlling the same fan which is obviously not ideal.

Otherwise I’m not sure I can help.

GeorgeIoak · January 31, 2020, 7:53pm

I tried to find “Fan Control Entity Row” in the Community Hass.io Add-ons and I don’t see it. I manually added it but when I reload the UI I get this:

Custom element doesn't exist: fan-control-entity-row.
entity: switch.garageafs_high_speed
type: 'custom:fan-control-entity-row'
name: Garage Air Filter
customTheme: false

I have the js file in the config/www directory and in my ui-lovelace.yaml file I have

title: My Home
resources:
  - url: /root/config/www/fan-control-entity-row.js
    type: js

and also:


      - type: entities
        title: Garage AFS
        show_header_toggle: false
        entities:
        ## USE THIS CONFIG TO HAVE IT MATCH YOUR THEME ##
          - entity: switch.garageafs_high_speed
            type: custom:fan-control-entity-row
            name: Garage Air Filter
            customTheme: false

Right now I’m just trying to test getting the card to display as I have a Sonoff 4 Channel Pro hooked up to an air filtration system that uses 3 separate relays for the speed control. I know I’ll have to do some work to get that actually working correctly but I thought I’d start with the UI first since the individual switches work in the UI now.

finity · January 31, 2020, 10:01pm

That’s because it’s not in the hassio add-ons. It’s installed thru the HACS custom component:

And normally when you have to install components manually and the file is located in the /www/ directory you have to add them to the lovelace config like:

title: My Home
resources:
  - url: /local/fan-control-entity-row.js
    type: js

in this case “/config/www/” = “/local/”

GeorgeIoak · January 31, 2020, 10:34pm

OK, it’s been a few years since I messed with HA so I’m back to being a noob. I had tried using just like in your example and got the error so I thought wasn’t finding the js file.

I don’t have HACS installed but I think for now I’ve accomplished the same result or should I undo my changes and go through the HACS path?

finity · January 31, 2020, 10:43pm

I always recommend using HACS. It (almost… ) makes things idiot proof.

As long as you follow the instructions in the install page of HACS for each component exactly as written regarding the way to add it your resources section in Lovelace you will be fine there.

But if you think you have it done correctly otherwise (in the above you don’t…) then you can do it that way too.

But HACS is just way easier.

GeorgeIoak · January 31, 2020, 11:10pm

OK, I think installing HACS was more steps than what I did before but I just restarted and the card is loaded properly with the buttons now so that’s a step forward.

Now I just need to figure out how to get this to work with my setup. Each speed is just a different POWER command, Low is Power1, Medium is Power2, High is Power3:

- platform: mqtt
  name: "GarageAFS Low Speed"
  state_topic: "stat/Garage_AFS/POWER1"
  command_topic: "cmnd/Garage_AFS/POWER1"
  availability_topic: "tele/Garage_AFS/LWT"
  qos: 1
  payload_on: "ON"
  payload_off: "OFF"
  payload_available: "Online"
  payload_not_available: "Offline"
  retain: true

finity · January 31, 2020, 11:20pm

I’m not sure how that will work.

You will have to find someway to translate each “speed” into a combined “fan” entity that sends the different command topics for each speed and retrieves the fan state and speed for each speed.

you might take a look at my config for converting a “dumb” fan that uses an rf transmitter that doesn’t have any speed/state feedback into a fan entity for use with the control row.

it’s here and the section you are looking for starts on row 41. Be warned that it’s pretty long and involved tho:

github.com

finity69x2/Home-Assistant/blob/ae36b0dbfe25555bdbea2f35efa90752694bf35d/packages/fan_package.yaml

## NOTE: it seems that in later versions of Tasmota the iFan02 configuration uses a different state topic 
## than the original as listed below.
## The new topic for both state_topic and speed_topic is "stat/sonoff_MBR_fan/FANSPEED"

## iFan02 or iFan03 flashed with Tasmota:

fan:
  - platform: mqtt  
    name: "Master Bedroom Fan"
    command_topic: "cmnd/sonoff_MBR_fan/FanSpeed"
    speed_command_topic: "cmnd/sonoff_MBR_fan/FanSpeed"    
    state_topic: "stat/sonoff_MBR_fan/RESULT"
    speed_state_topic: "stat/sonoff_MBR_fan/RESULT
    state_value_template: >
      {% if value_json.FanSpeed is defined %}
        {% if value_json.FanSpeed == 0 -%}0{%- elif value_json.FanSpeed > 0 -%}4{%- endif %}
      {% else %}
        {% if states.fan.master_bedroom_fan.state == 'off' -%}0{%- elif states.fan.master_bedroom_fan.state == 'on' -%}4{%- endif %}
      {% endif %}
    speed_value_template: "{{ value_json.FanSpeed }}"

This file has been truncated. show original

GeorgeIoak · January 31, 2020, 11:49pm

OK, thanks for the tip. In my old setup I had created an automation (jet_afs.yaml) and then in my groups.yaml I had this:

jet_speed_control:
  name: Jet AFS Speed
  control: hidden
  entities:
    - input_select.afs_speed

This is all from a few years ago so some of those brain cells are dead now

GeorgeIoak · February 2, 2020, 6:32pm

OK, I’ve been digesting your code and reviewing what I had done a few years ago and fortunately there are a lot of similarities. I do have a couple of questions though:

sunroom_fan_off:
  alias: Sunroom Fan Off
  sequence:
    - service: switch.turn_on
      entity_id: switch.sunroom_fan_0
      # data:
        # packet: 'JgA0ACsMKw0PKA8pDygPKQ8oKw0PKA8oDykPAAEGKw0qDQ8pDygPKA8pDygrDQ8oDykPKA8ADQUAAAAA'
    - service: input_boolean.turn_off
      data:
        entity_id: input_boolean.sunroom_fan_state ```

If you’re turning off the fan why do you start with - service: switch.turn_on?

In your automations section you have a bunch of toggles where you turn on for 1 second and then turn off. Are those code blocks used anywhere? I think only the script section is actually used and maybe those are for something else?

Scripts are new to me and I currently only have automations defined. Is there a reason to use a script block over an automation block?

finity · February 2, 2020, 8:25pm

Those are really good questions.

It’s been so long since I’ve looked at the code I really can’t remember the details anymore.

I’ll have to dig in myself and try to jog my memory.

Or maybe it’s all just bad coding that I did a long time back and things need to be changed to make more sense. it really could go either way at this point.

GeorgeIoak · February 2, 2020, 8:38pm

OK, I feel the same so no worries! I’m making changes now to see if I can get this to work. I haven’t messed with packages before but I can see how useful it is to keep everything in 1 spot.

GeorgeIoak · February 6, 2020, 9:23pm

I’ve got it all working now, it’s a bit messy but at least it works. I’m on to my next challenge and thought I’d ask here first before I start from scratch. I’d like to enhance this now so that you have an option to run the fan for a set amount of time. I’m thinking either a fixed button choice for time (say 30, 60, 90min) or a slider that jumps by 30min steps (I want this to be easy to use with a touch screen).

So the fan operation works the same but if you select a time the fan will run for that set time and then turn off.