The problem that I’m having is that the value_template isn’t updating appropriately. If I change it to this: value_template: "{{ states('switch.living_room_fan') }}"
It works, but I don’t really want this to remain as a switch. This works for my lights, so I’m not sure what the fan element is expecting. These are all simple fan controls. All they do is turn on and off. I just wanted it to be a ‘fan’ element for the GUIs. Thanks!
You are creating a Template Fan called fan.living_room_fan but its value_template refers to sensor.bedroom_fan_status. Shouldn’t that be sensor.living_room_fan_status?
You’re using sensor.living_room_fan_status as a status indicator. Given that this fan can only be turned on and off, why didn’t you choose to create a binary_sensor? Then the value_template would be:
Shouldn’t both of those return a true statement? What first one is what I had when I built this as a switch, so I expected the same template to work as a fan. Thanks!
Whereas a binary_sensor only has two valid states, on an off, a sensor can have all kind of states. It all depends on how you configured it and, especially, what it is monitoring.
In this case, I have no idea what sensor.living_room_fan_status is monitoring. The fan? How?
OK, while I was busy typing, you answered the question.
Does the fan template require a literal ‘on’ or ‘off’? And I’m supplying true/ false? I guess I thought the value_template section with is_state() actually returned a boolean true/ false with the comparison.
If that’s the case, I guess I can change my sensor to binary_sensor and that should be an easy fix.
I’d appreciate it if you could tag my post as ‘Solution’ in order to make it easier for other users (who may be experiencing the same problem to find it. Only you, the author of this topic, can tag a post as ‘Solution’. It will automatically place a link to the solution under your first post.