Why do some routines run locally vs cloud?

Aside from devices still running custom DTHs that are in the cloud, is there a list of known things that prevent routines from running locally?

I’ve got several routines that I use to turn off all my outside lights in various circumstances. I have tried using a lighting group and a scene. Both of those seem to prevent local operation even though all the devices being controlled are on Edge drivers or using stock DTHs.

1 Like

Many scenes require the cloud (it used to be all), but I don’t know the exact details.

That’s the thing, we don’t know what forces cloud execution (I wonder if Samsung knows - because they certainly don’t seem like they want to tell us.)

2 Likes

I have made virtual momentary switches to replace my scenes and just placed those devices in a “Scenes” room to have local operation.

2 Likes

I find these things make Routines run in the cloud:

  • Scenes
  • Lighting Groups
  • Member Location
  • Devices from cloud->cloud integrations
  • Notification actions
  • Weather triggers
  • STHM triggers and actions
  • Any Day time precondition
  • Cloud virtual devices

Could be more but these are the ones I know of to date.

2 Likes

Using Devices from two different hubs in one routine. That would include the new station hub.

1 Like

I’m curious if anyone has an updated list? It appears that scenes (aka Manual routines) are now at least partially local. However, I’ve got a weird situation as I try to better make things local and useable when the internet is out. I’ve got several sets of blinds paired with Zooz scene controller. I’ve realized that when I have the blinds controlled as a manual routine and I set the either “open” or closed", the execution is via the cloud. However, if I either do not use the manual routine or I set blinds open by %, then the execution is local. No difference in equipment for each of these scenarios. Any idea what is going on?

I haven’t done any testing in quite awhile, so I don’t have a current list.

I’m not familiar enough with the Zooz scene controller, but I would think that if it has an Edge driver, then all functions of that device would be executed locally. You’re not including other Actions in the Manual Routine that would force cloud execution?

Yes ,Zooz edge driver and yes, all actions should be local. When the exact same configuration is used without a scene it is local, when I have a scene it is cloud- and then only for the blind open and close commands and not the other commands. There is nothing else beyond the blind controls in either scenario.

Can you show us a screenshot of the scene set up? You might have to go into edit mode.

1 Like

This one shows the Zooz device configuration, so you can see which ones are local.
This shows the automatic routine that calls a scene and is cloud based.
This shows the scene configuration which runs in the cloud.
This shows a different shade that does not use a scene and runs locally.

It might perhaps execute in the cloud but you can’t tell just by looking in the mobile app as local Scenes aren’t flagged in the same way as Routines are.

My evidence for what worked and what didn’t was when I lost internet for the day. But in my first picture I show the routine that triggers the scene. And there isa clear pattern amongst them.

Hi @homeagain

Could you enable support access to your account so I can check its details, please?

  1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM.
  2. Enable support access to your account:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (⋮) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

More info about this access here: https://support.smartthings.com/hc/en-us/articles/36170233944852-Enabling-Account-Data-Access-for-Support

1 Like

Yes access should already be granted and I’ve got the same email on the forum and ST. I’ve also found other situations where the “scene” and the routine yield different cloud vs local execution. The example here is the cleanest though and I’ll leave it the same for review and/or testing purposes.

Hi @homeagain

The engineering team is currently reviewing the issue. Could you please update the rule—for example, by making a small name change? Once that’s done, they’ll check the logs again.

I changed the naming of the “…North Shades closed” routine by adding a “1” to the name.

1 Like

Hi @homeagain
The team mentioned that the scene appears to have been created quite some time ago, and there’s a chance it was created before it could be configured to run locally.

As a next step, could you please modify the scene that’s included in the routine titled “North shades close”?
This will help us determine whether there’s any reason why it wouldn’t run locally now.

Let me know once you’ve made the change, thank you!

I changed the scene name to north shade closed1. It still shows up as in the cloud at the routine level.

I believe they meant to change something in the actions of the scene, not just the name.