So, I have like 30 smart switches that have 4 buttons each and each button has 3 triggers (single, double and long press), that’s 360 possible automations there.
Since I have both smart switches and smart bulbs, and since HA doesn’t create entities for stateless buttons, I have no easy way of grouping them in order to maintain or just see the automations that each button does.
It would be awesome if HA would have a dedicated dashboard or interface for managing these types of smart switches/buttons.
Before someone says that smart switches and smart bulbs shouldn’t be used together, my smart switches are really SMART. If they are connected to a dumb bulb they will act like a normal smart light switch (and create an entity), but you can set them to keep the power always on (you can do that for each of the 4 circuits individually) and they became smart stateless buttons to invoke an automation. So, they work great with smart and dumb bulbs, and if anyone is interested the switches are these ones from Terncy: https://terncy.com/en-us/wallswitch-withneutral/ https://terncy.com/en-us/wallswitch-noneutral/
Can you explain what you mean by ‘stateless’ switches, because what you’re saying doesn’t make sense to me. All entities can be managed or grouped, so your definition of stateless switches doesn’t really translate into HA lingo.
They are actually switches (when connected to dumb bulbs) that can be set to function as stateless buttons if you desire.
So, if I have a smart bulb connected to it, I can choose to keep the power always on and that on/off switch becomes a stateless smart button with 3 triggers.
In my case, I’m using them as stateless buttons since my lightbulbs are also smart, that way I need to create an automation for each button to toggle the respective lightbulb on or off.
So these show up as button entities? If you use the area card, it basically does what you’re looking for. It’ll show all entities (including automations) related to that area. Also, if you click the automation it’ll tell you related entities as well.
Lastly, you can make a blueprint that assigns button presses to actions in a single automation. So there’s no guessing as to which automation goes to which button. Each button will have 1 automation with n actions.