yes, that’s exactly what it means once this firmware rolls out.
Where do you find the overview tab? New to this beta.
This suddenly became a MUCH more important item for a lot of people.
You’re literally watching the birth of SmartLighting’s replacement… The ONLY reason I use SL anymore is for local automations. If this works as expected I won’t need it for that anymore. It also will cause me to make some of my basic webcore pistons into automations.
I’m personally following up on that one and the device limit. Both of those restrictions are in the client only, we’re working on getting it bumped up to a more reasonable limit.
Wait. STHM isn’t already local?!
I’ve got a couple questions. I’m sure local executions requires local capable devices but what happens in an instance where an automation may have a mix of cloud and local devices? Does it partially run or do the cloud devices restrict the entire automation from running?
I’m also still curious what this means about created or updated. Will existing automations that are capable of running local run local when firmware rolls out or does something need to be done to make them and if so what?
Additionally is there anyway to be able to tell in the app or somewhere whether the automation is eligible to run local or not?
the link is in the first post of this thread 
Don’t mind me. So excited about local rules I glossed right over it. 
“Rules that are created or updated after this feature is enabled are eligible for local execution…” So sounds like you’ll need to edit+save to see the Local execution notation next to the automation.
This is exacty what I want to know. l ready asked this question in this thread, but no one at ST has seen fit to answer…
Also like to know if enrolling in Centercode does this automatically sign me up for Beta (which I do not want to do, not feeling like being a guinea pig)…just like to read the extra info there.
Oddly enough I’m in the beta program - always get the emails and updates but for some reason Centercode doesn’t even show me as enrolled so I still can’t view the info.
Nope. Not even the leak detection… Trust me that one sucked when I migrated. I knew i was losing local leak intervention.
@blake.arnold since scenes have also gotten the rules api. Will scenes run locally as well? And if yes, will scenes inside automations be local? Thanks
Exactly, was thinking similarly about converting some of my Webcore pistons to automations.
Update has arrived! Time to play!
I have this firmware now too, although most of my automations cannot run locally due to most switches and bulbs being ZigBee device from IKEA or Lidl and my ZigBee lux sensor being Xoami.
@blake.arnold is there a reason why all ZigBee devices cannot be local execution?
Also will we ever get complex automations so we can add ‘Else’ or ‘Else If’
Its not about Zigbee or no, its about does it use a custom device handler. The device handler needs to be loaded on the hub to work locally and that wont happen with custom DTHs
For this reason I always try to make my devices Local. I have NYCE zigbee door hinge contact sensors. That device handler wont work locally but theres another that doesnt affect functionality at all that DOES work locally - so guess which one im using? For the bulbs for instance, can it just use the Zigbee RGB bulb device type and work?