Don't auto-enable scene actions

[jason0x43]

Is your feature request related to a problem? Please describe.

I don't typically want to show all my scenes in the actions list on my Apple Watch, so I disable some of them in the companion app. That works well enough, except for dynamic scenes. Those are discarded and re-created every time HA restarts, so they keep ending up back in my actions list (I'm assuming because the app sees them as new scenes).

Describe the solution you'd like

I propose that scene actions not be automatically enabled (or that a switch is added to change the default behavior). They should be easy to enable, as they are now, but the user should be able to decide whether to add them.

Additional context

[unikitty37]

Is there a fix or workaround for this yet? It’s insanely annoying — I don’t want HA to make these decisions for me, because it usually gets it wrong!

[ErikvO]

This suggestion would also (partly?) solve my issue:
I have 18 scenes, but I only want to 2 of them available as scene actions. So I turn off the 16 I don't need. So far so good.
However, every once in a while the state resets and all scene actions are turned on again, causing me to have to disable the 16 unwanted scene actions again. This happens over and over and it starting to be irritating.
If scene actions were not enabled by default, either the problem is gone, or every once in a while the state will reset and no scene action would be enabled. Hopefully it would be the first option. If not, I would only need to enable 2 items.

[ronaldheft]

I've noticed all scenes will get re-enabled if you reloading add or edit any scene. It would be nice if the iOS app would remember which scenes were previously disabled, so they don't reappear when any scene is tweaked.

[jason0x43]

I would once again propose that scenes be disabled by default, or that the default behavior (enable or disable new scenes) be configurable. Having dynamically create scenes appearing in the action list is doubly annoying because those scenes are typically not meant to be manually triggered in the first place. 🙂

[reestr]

Alternatively please add a switch to enable or diable all of them. I have scenes automatically populated in HA from (I think?) the Hue integration. This means I have mutliple tens of scenes I need to all disable, one by one, just so I can add custom actions in for the widget.

[mindgam3s]

+1 this in incredibly annoying ...

[Teagan42]

Disabling the scene actions still seems to show them in the action sheet on my watch... I don't want ANY of these scenes in my watch - they are automated fully so this just takes up real estate on the tiny screen...

[pashdown]

I too would also like a way to keep the scenes from appearing on my watch automatically. Considering everything else has to be defined, I don't know why scenes are excepted.

[normand198]

Please implement this or at least give us an option to disable all scenes at once!

[bgoncal]

#2437

[moshiko2312]

I really can't understand the logic of this whole issue of opening the car play option to all users without controlled control, in my opinion it's one big bug and a security hole in the system.

For example, I run an office with 20 users who are not defined as administrators at all. They are just regular users without extended access to the system. I also use kiosk mode.

And now what happens is that as soon as a user who is not an administrator in the system connects his phone to his car or uses iPhone shortcuts, he actually has full access to all automations, scripts, and more...

This way my system is really exposed to the operation of a user who is not an administrator. It's very bad. I don't know what to do anymore. Everything I built is destroyed because of this.

You need to make an option in the system settings to allow the user to see the car play option or shortcuts on mobile, tablet, etc....

Please call this quickly and make a user management option.
And not restrict through the user's own device, but restrict through the Home Assistant server

This is very important because without this option, this whole thing goes against the Home Assistant management rules

And it's the same on Android

[bgoncal]

It’s the same in both apps because it’s not app related, you need to request this feature to home assistant core, it’s basically user access level that you are looking for, because even if we do an workaround in the app, your co workers would still be able to trigger scripts using the API if they want.