Yeap! But still the same, could be a bug or really was removed.
I find (under Android at least) if you edit a routine that was local, but change it in a way that might make it unlocal it will still show local until you redraw the whole list of routines by leaving that device and returning. Trial and error to figure out what might be local or not takes a bit longer.
Exacrly what happened. I knew that beforehand and fornsome reason didn’t think about it. I was just amazed how it showed local. 
1 Like
Hi, @Dienzora
I asked the Engineering team about this and the answer is that the Remains conditions are currently being run in the cloud because it requires additional data to be properly evaluated. We are working to have them running in the Hub as well in the future, still not sure when.
1 Like
Still not local for me. 
Are you running the new firmware 45.9 on you hub (Aeotec, V2 or V3)?
If yes, try do creating a new routine delaying some sensor.
I’ve been monitoring this action for months now as I really want it local but it seems that it works for some folk and not others.
It’s bizarre. I’ve never had it working for me.
Are you using Zigbee devices with drivers running on your hub?
100% yes.
I’ve double checked and triple checked.
Could you share some automation you did that didn’t run ?
As you can see. It’s local but as soon as I add a timer, it’s not local. Very frustrating as it works for some folk.
Can’t understand. Some others here in Brazil also can do it
Yeah looks like a region thing.
Thanks, now its working.
1 Like
Finally!!
Local here too. Thank you.
1 Like