Certain Automations and device types can utilize local processing with the SmartThings Hub (2018), SmartThings Hub v2 (2015), and SmartThings Wifi.
What runs locally?
Some preconfigured automations can run locally.
Manual, on-demand control of a device or SmartApp through the SmartThings mobile app always requires an internet connection to the cloud and cannot be performed locally.
How can I set up an automation to run locally?
For an automation to execute locally, the following three criteria must be met:
1. Device must be able to run locally
The majority of supported devices that communicate via Zigbee or Z-Wave are eligible to run locally.
If you have an existing SmartThings setup, you can check if your connected devices can run locally:
- Log in to the SmartThings IDE
- Click on My Locations
- If you have more than one Location, click on its name
- Navigate to My Devices
- Check next to the name of your device for its execution location.
2. Automations must be able to run locally
Smart Home Monitor and Smart Lights are Automations that allow you to configure “child Automations” with the ability to run locally. The SmartThings Home Monitor “child Automations” that can run locally include Alert with Lights, Alert with Sirens, Close Valves (for Leaks), and Unlock doors (for Smoke). SmartThings Home Monitor and Smart Lights are the only Automations with local processing capabilities at this time. We are working on additional local Automation options.
Additionally, mode changes cannot process locally. Using this as a trigger for Smart Lights will prevent the automations from performing without an active internet connection. Use a different trigger, such as At a specific time instead to ensure your Automations can run locally.
3. Most cloud, LAN, and virtual devices may NOT be included
If any cloud or virtual device is added to an Automation, the Automation will not run locally. Most LAN devices will not be able to run locally, with the exception of Philips Hue devices with firmware v0.19.17. These cloud, LAN, and virtual devices are reliant on an active internet connection. This includes mobile presence devices, as well. Any Automations triggered by mobile presence will not execute in the event of an internet outage.
- A Smart Lights Automation that controls a SYLVANIA bulb (ZigBee) will run locally.
- However, a Smart Lights Automation that controls a SYLVANIA (ZigBee) and a LIFX bulb (cloud-to-cloud) will not run locally.
Are there any other requirements?
Remember the following to ensure that your local devices and Automations perform as expected:
- SmartThings Hub (2018), SmartThings Hub v2 (2015), Samsung Connect Home, and SmartThings Wifi are capable of local processing; the first-generation SmartThings Hub v1 (2013) does not have these capabilities. Read this article if you are uncertain of which Hub you own.
- SmartThings Hub v2 (2015) also has battery-backup. To execute local commands during a power outage, the Hub v2 must have 4 AA batteries installed. There are 4 AA batteries included with Hub v2 but are not preinstalled. This battery backup is expected to last up to 10 hours.
- Devices that are not battery powered and require a persistent power source will not respond in the event of a power outage.
- An active internet connection is always required to manually control your devices and Automations via the SmartThings mobile app.
- During an internet outage, the Hub will not be able to talk to the SmartThings cloud or mobile app; you will not be notified via the app of a local event until internet is restored.
What does local processing look like?
If your devices and Automations meet all the above criteria, they will be able to run locally when an internet and/or power outage occurs.
- In the event of an internet outage, a Smart Lights automation that tells your SYLVANIA bulb to turn on at 6:00 PM will locally execute.
- In the event of an internet and/or power outage, a SmartThings Home Monitor automation that tells your Aeon Labs Siren to sound when motion is detected by a Samsung SmartThings Motion Sensor will locally execute.