Local Scene Execution

[blueyetisoftware]

I frequently see requests and conversation about running scenes locally. I figured I would share this trick even though it may seem obvious. Using the Edge environment, and virtual devices, you can setup a virtual switch or virtual momentary button that triggers an automation. That automation can be setup in the same way you would have setup the scene. If all of the devices being controlled are local, then your “scene” automation will run locally as well. Instead of using scenes, you just use these virtual devices. This can also give a scene an on/off state if desired. They are also compatible with voice control. Here is a link to a virtual device driver that has these switch and buttons:

[ST Edge] Virtual Hub Kit [BETA]

This will be an open beta, as the driver is not expected to need many updates. Any updates will happen automatically if they are released. Those updates will be announced in this thread, so please watch for notifications. There are some other quality virtual device drivers. The intent of this driver is to enable users to create their own smart apps / devices to enable automations that are not possible with their physical devices. For example, associating a relay/contact sensor to make a door. Follow the invite link below to install the driver. This will create a Virtual Hub in a “No Room Assigned” room within the ST app. You can use this virtual hub to create further devices. Here is a Garage Door Example connecting a relay and contact sensor to automate the door. You should consider t…

[blueyetisoftware]

@TAustin I may use your driver as inspiration for a dedicated “Scene Control Driver” that somehow brings in a bunch of icons and just creates virtual buttons. This would also allow scenes to be associated with rooms, which I think makes them a little stronger than the current scenes for some setups.

[nayelyz (Developer Support Team)]

@blueyetisoftware

I would hope the ST dev team could use this concept to move the actual scenes over as well, which makes the setup and UI cleaner.

Just to confirm, are you referring to a use case like the one below?

• We have a scene with local-execution devices
• When we create an automation, we set in “actions” (Then) “run a scene” and this routine still executes local

I see that using “run a scene” makes the Routine run in the Cloud…

[blueyetisoftware]

@nayelyz

Just to confirm, are you referring to a use case like the one below?

Yes. It seems that they run in the cloud in all cases. If all devices run locally, it would be nice if the scene ran locally. For example, I think these should be equivalent, but they are not.

Edge Scene Controller → Press Button → [Automation] → Turn On Edge Light
Edge Scene Controller → Press Button → Run Scene → [Scene Actions] → Turn On Edge Light

The case that uses the scene goes out to the internet. My comment at the top is for users to reimplement scenes as virtual automations as a workaround.

[nayelyz (Developer Support Team)]

@blueyetisoftware

Yes. It seems that they run in the cloud in all cases. If all devices run locally, it would be nice if the scene ran locally

Got it. I’ll check that with the team to get their feedback and let you know.

[andresg]

@blueyetisoftware we checked with the team and they told us that they are aware of it and this change (allowing Scenes to run locally) is in development.

[henrypscott]

It’s nearly a year later, yet from what I can tell, all Scenes still run in the cloud.

I have one Scene in particular which controls multiple lights, and for reasons I don’t understand, the command for one set often doesn’t execute, but I suspect it’s related to the cloud execution.

I’m now trying the workaround described here (i.e., and Edge-based virtual button that initiates a Routine with the same steps that were previously part of a Scene), and so far it appears to be working consistently.