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.
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.
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.
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.
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.
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.
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!