I have an input boolean virtual switch set up, but when I go to automations, I don't see the switch entity and have to use perform action "input boolean" on it.
This should be fixed where whatever you set it up as (switch), it should show up in "switch" on automation choices to control.
#Input Booleans should be an entity that can be used just like any other in automations.
abstract current
regal rivet
The boolean is the virtual switch, there is no switch entity
You can create a template switch, if you want a switch
If you want to propose that to be done automatically then post a feature request or WTH on the forum
limber joltBOT
abstract current
Template switch what causes "switch" in the automation?
regal rivet
Yes, if you want an actual switch entity
The boolean is your virtual switch, it just isn't an actual switch
abstract current
Right. But with homeseer, it acts as an actual switch to make it easier to work with.
regal rivet
HA works differently to HomeSeer
For any entity you always use the services that match the entity - input_boolean.turn_on for input_boolean.whale_bay_doors for example
You can (almost) always wrap things with templates, but it's just adding complexity you don't really need
abstract current
Seems having to build templates for everything is adding complexity that could be simpler.
Don't get me wrong. I love HA a lot more than HS. A lot more flexible and works with my solar inverters. But there's just stuff that doesn't have to be complicated. When I programmed (in line basic), I wrote programs to idiot proof it a lot and went out of my way to program to make it simpler for the user.