@Jason_Brown
At present none of the smartapps run locally, official or not, except for smartlighting and a few parts of smart home monitor. Even routines don’t run locally.
And smart lighting only runs locally with a specific subset of devices.
Continuing the discussion from What's the deal with Nest? :
Correct.
I was answering this question below in the global sense. i.e., There will always be the possibility of various benefits available to Official Device Handlers and SmartApps that are not available to un-certified Community Developed ones. At the moment, the local processing benefit is inapplicable to Nest in either case.
I’m not sure ST has guaranteed that community developed SmartApps/Device Types will be included in local processing right after certification. Yes, it may be included down the road, and this is not yet clear on how or what the process is to enable community developed stuffs to run locally.
Here is a list of the Device Handlers that are confirmed working with local processing (I personally tested that these show up in the “LocalDevice List”) as of Dec 8, 2017:
Device Type Run Locally Execute Commands Locally Minimum HubCore Version
Aeon Home Energy Meter TRUE FALSE n/a
Aeon Illuminator Module TRUE FALSE n/a
Aeon Key Fob TRUE FALSE n/a
Aeon Minimote TRUE FALSE n/a
Aeon Multisensor TRUE FALSE n/a
Aeon Multisensor Gen5 TRUE FALSE n/a
Aeon Outlet TRUE FALSE n/a
Aeon Siren TRUE FALSE n/a
Arrival Sensor TRUE FALSE n/a
CentraLite Thermostat TRUE FALSE n/a
Dimmer Switch TRUE FALSE n/a
Fortrezz Water Valve TRUE FALSE n/a
GE Link Bulb …
1 Like