Since you are open to workarounds, make an input boolean that you check for being on in your automations or scripts. You can put that entity on a dashboard. Much simpler.
Thanks for your feedback. I actually got sidetracked today so couldnāt play with it much, but it seems I can set up a ābuttonā card to turn on/off automations similar to how I am able to do with scripts. So will probably end up creating a new tab where I can have a list of automations my family might want to turn on/off on demand.
This nice thing about input booleans vs buttons is that you can easily see if theyāre on or off. I have an automation that resets a bunch of ādisableā booleans for the notifications each day at midnight.
you can have a button which calls an automation or service, canāt you?
BTW Iāve read about 100+ unread post and itās sad how some users defend missing rbac or even disregard some otherās users legit use-cases just for sake of justifying this shortcoming.