Local and not local

General Discussion
#1

Any idea why an Ikea motion sensor routine to turn on lights based on motion is run locally, but a routine using the same sensor and lights to turn them off based on no motion is not local?
Both routines are only triggered by the motion sensor and have no other conditions

image
image1668×689 88.4 KB

#2

try editing the one routine that is not local, add a space after the routine name and Save. see if it changes to Local

2 Likes
#3

We would need to see the complete routine, but my guess would be that there is a timer/duration of some kind in the turn off routine. Some of those will not run local even if the device is eligible to run local.

4 Likes
#4

The solution that @jkp is definitely the first thing to try. However vif that doesn’t work the what @JDRoberts said will be the next thing to investigate. You will need to provide a full screen shot of the automation to determine if something else is causing the automation from running locally.

1 Like
#5

Ok, I tried adding the space, made no difference.
Here are the two routines.
The one marked local has the home symbol beside it, the other one does not.
@JDRoberts @jkp

image
image1651×1426 139 KB

image
image1668×1423 114 KB

#6

you put it there for 5 minutes. When she has this condition she is not local

4 Likes
#7

Really?
Why on earth does the hub need to reference the cloud to wait for 5 mins

2 Likes
#8

The official explanation is that they haven’t finished moving all features from the cloud to local yet, but they aren’t promising exactly which features will be in the finished product. But right now, it’s not timers. :disappointed_relieved:

2 Likes
#9

It doesn’t. It does, however, need the code to handle ‘remains’ to have been implemented in the hub firmware. Or alternatively if the routine was written using the older ‘remainsEqual’ and that is to be superceded (all I know is that ‘remains’ has been documented and ‘remainsEqual’ hasn’t) it may need the Routines to be tweaked to generate different code. Or both.

2 Likes
#10

I’ve noticed that often when I edit routines now, they often end up being local when I’m done. So I went through many of my local devices that are triggered only by time and it appears that simply making and undoing an edit prompts a save, which then appears to make it local execution. Sounds like your approach is doing the same thing. I’m curious what other actions can be “moved” to local?

1 Like
#11

I’m seeing the exact same thing.

Oddly enough, in my motion detected rule I have it set to turn off the light(s) after 5 minutes.
That rule is listed as having local execution.