Thanks @nathancu, now I understand the dependency of the DTH I will try to find a standard DTH that works with my device types.
I have found one downside to what is considered local…
If I set an automation to switch a light of when motion stops it runs locally, however if I set a motionless duration it does not.
Got the update and as I suspected 1 out of my 18 automations was eligible for Local Execution 
This is mostly due to all my switches/dimmers/fan controllers needing a custom DTH for their full functionality.
Given the high number of issues I keep having (in random storms) I often have to exclude and reinclude devices. This has caused Smart Lighting, and I believe Automations, rules to either vanish or be left in a state that requires a bit of trial and error to figure out what it was supposed to do and what device needs to be added back for it to work. I guess this will make sense to those who have had the issue as I can’t think of an easy way to explain this better… For this reason I tend to prefer Webcore anyway as it is easier to restore broken pistons.
Yeah this is a really cool start, but it’s not a real game changer for me until:
yeah, location Mode is a stickler for me. I was able to get a couple existing ones to run local, though. Will do some testing and then see what I can move over from Smart Lighting.
I guess in the meantime I could use a combination of automations and local virtual switches to effectively replace scenes.
Automation1 => turn on virtual switch at X time
Automation2 => when virtual switch is turned on, do a bunch of things with local devices
And other automations could flip that virtual switch on and share the same end result.
Same goes for mode. Just represent the mode with switches instead of states.
My question is this
, are there any plans to move custom DTH to local execution. We all know it is certainly possible considering the competition does it. Otherwise local automations does absolutely nothing for me…90% of my automations include a device with custom handler and that’s not going to change unless ST kills custom DTH…in which case I will be transferring away immediately.
Sorry to ask a basic question but is there a way to test automations to see if they’re executing locally without disconnecting my internet?
How were you able to tell which ones were eligible and which weren’t? By looking at the devices or is there something in the app/automations that tells you?
Location mode is or isn’t capable of local execution? I can’t access the center code site so I can’t see the notes.
So far so good getting one to be identified as local:
Very good start. However as most devices do not support local execution, and most of my automations are complex we need a bit more to start actually benefitting from local automations. This is a big step in the right direction. Now if ST gets at least the ikea motion sensor and buttons to local and i will replace my switches with devices that support local execution on ST. Keep it going. I know you are a bit of tough spot at the moment but you are definitely on the right track!
Can anyone confirm whether existing eligible automations are local capable now or does something need to be done to make that happen?
Also what happens if you have a mix of cloud and local devices - do the cloud devices negate the entire automation from running locally?
@GRClark In case you missed it
You can see the tiny “L” in a black dot next to the ones running local.
Once the hub updates, you have to update an existing Automation. If all the devices and the capabilities defined in the CenterCode beta participants post are there, it should become local.
negates the entire automation
i win! 0 local… that is zero local automations. winner! winner! chicken dinner!
no one can beat me. LOL
You and me both because of custom DTHs.
Baby steps, hopefully local custom DTHs are next. 
lmao… I’m debating moving my SL stuff back over to Automations, at least the ones that comply with what should be local.
Zero local for me too because of either custom handlers or location mode. I understand this is still progress and for that I’m thankful, but looking forward to when these capabilities are expanded.
Hey guys, thank you for trying out the beta local execution. I’m excited we have gotten this far, and we’re working to add more features to our local roster. Making note of all the requests, the plan is to make local execution a first class platform feature. In this first release, our intent was to test out the framework and so a limited set of features is available, but we’ll be slowly adding support for more and more features on our quest to get most rules to work locally.
Thank you,
Adrian
