Trouble with RBoy Lock Smart App

[JDRoberts]

@helios

I forgot that some smart apps run in a cloud somewhere. Last night I was seeing my new door sensor incorrectly reporting the door state and the lock app not do things it seemed that it was supposed to. Since the sensor was a brand new installation (as in when I got home from work yesterday) it didn’t occur to me that the issues may be upstream.

This is less than ideal. None of us can afford to have our alarms, locks and so on not working correctly because of issues outside our control.

All Smartapps run in the cloud except SmartLighting and some parts of SHM , and those only run locally if all of the devices they refer to are eligible to run locally. Routines do not run locally. No other smartapps run locally at this time, not even the ones installed from the marketplace.

You can see what smartapps on your own account are eligible to run locally by checking the links posted in the community – created wiki FAQ article:

http://thingsthataresmart.wiki/index.php?title=FAQ

And see the following thread for more discussion of local processing:

Local Processing in Hub V2

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.