The answer to “does smartthings work without internet” is yes, but only for part of the system. An automatic routine can keep running when a powered SmartThings hub, every device in the routine, and every feature used by that routine all support local execution. Cloud-linked devices, voice assistants, notifications, and remote app commands should be treated as unavailable until the connection returns.
Don’t buy another hub yet. Test the routine that matters most.
Why losing the cloud doesn’t stop every routine
SmartThings has two places where automation logic can run. One is the SmartThings Cloud. The other is a compatible hub inside your home. The same app can contain routines that use either path, so “my SmartThings setup” isn’t one useful category during an outage.
Samsung’s Rules documentation gives the deciding rule: a Rule can execute on the hub only when every device feature and service involved supports local execution. If one part doesn’t, SmartThings runs that Rule in the cloud. This means one notification, linked account, or unsupported condition can change the fate of an otherwise local sensor-to-light routine.
The device path matters too. SmartThings says its hub-connected devices use Edge drivers to run locally on a hub. That group includes supported Matter over Wi-Fi or Thread, Zigbee, Z-Wave, and LAN devices. A product using one of those labels isn’t automatically local, though. It still has to connect through a supported hub integration rather than through the manufacturer’s internet account.
One cloud-only step changes the answer
Use this table as a prediction, then prove it with a test:
| Part of the setup | Likely result when internet fails | What decides it |
|---|---|---|
| Physical switch or sensor talking to a hub-connected device | Can keep working | Both devices and the routine features support local execution |
| Device added by linking a manufacturer’s account | Usually stops | The command has to reach that company’s cloud |
| Voice command through Alexa or Google Assistant | Don’t rely on it | Speech recognition and account links use online services |
| Push notification or control while away from home | Stops until service returns | Your phone must reach SmartThings over the internet |
| Local routine with one cloud-only action | Treat the whole routine as cloud-dependent | Every feature has to qualify for local execution |
The useful distinction isn’t Wi-Fi versus Zigbee. It’s local path versus cloud path. A Matter-over-Wi-Fi device may run through the hub locally, while a different Wi-Fi device with a linked manufacturer account may need two cloud services for one command.
Does SmartThings work without internet in your house
- Confirm there is a powered hub. Find the SmartThings or compatible hub that owns the devices in the routine. A phone running the SmartThings app isn’t a substitute. If the same outage also cuts household power, the hub, router, switches, and sensors need power before local execution matters. For this test, leave the local network powered.
- Trace every device to the hub. Open each device in the routine and identify how it was added. A Zigbee, Z-Wave, Matter, or supported LAN device attached to the hub is a local candidate. A device added by signing into another brand’s account is cloud-linked. Don’t infer the path from the product logo; write the integration path beside each device.
- Simplify and test the routine. Copy your important routine. Keep one physical trigger and one device action, such as motion detected then lamp on. Remove notifications, voice-assistant steps, phone-location conditions, weather, and linked services from the copy. Disconnect the router’s WAN cable without turning off Wi-Fi or hub power, trigger the sensor, and record whether the action occurs.
That last detail prevents a bad test. Turning off the router destroys the local network as well as the internet connection. You learn only that an unpowered network doesn’t work. Disconnecting the modem or WAN cable leaves the hub and local devices able to communicate while taking the cloud out of the path.
Run the test twice. The first run checks whether the stripped-down routine is local enough to survive. The second adds one removed feature back. If the second version fails, you have found the feature that makes the routine cloud-dependent.
If the routine still stops
Don’t factory-reset anything during this test. A reset erases evidence about the driver, pairing, and routine. If the hub shows offline while the WAN is connected, check the SmartThings service status before changing your network.
Start with power. Wait until the hub’s status light shows it has finished booting.
Next, remove one device at a time. Swap a cloud-linked bulb for a hub-connected switch, or a phone trigger for a physical button. Find the first handoff that leaves your home.
“No Internet = no local control, no automation?”
That question from a SmartThings Community outage report shows why app tapping is a poor diagnosis. Automatic routines and app commands don’t prove the same path. Use the real sensor or schedule, then watch the target device.
If the simple sensor-to-device copy works, the hub and its radio are doing their job. Add features back one at a time. If it fails as soon as you add a notification, move that notification into a second, cloud-dependent routine. The essential action stays local. The alert catches up when service returns.
If the simple copy doesn’t work, check the exact driver and integration for both devices. SmartThings Edge runs hub-connected device drivers locally, but the fact that a device appears in the app doesn’t prove it uses an Edge path. A linked-account integration can present the same kind of tile while sending commands outside your home.
Stop when the remaining device supports only its manufacturer’s cloud. No router setting can turn a cloud API into a local radio. Keep it if offline operation is optional, or choose a hub-connected replacement when outage behavior is a requirement.
Test the WAN, not your Wi-Fi
An internet outage and a home-network outage are different failures. Your router can keep assigning local addresses and moving traffic between the hub and LAN devices after its WAN connection disappears. If you unplug the whole router, LAN devices vanish too, and a successful local routine may fail for the wrong reason.
Write a tiny outage card before you test. Six lines are enough: hub powered, router powered, WAN disconnected, trigger used, expected action, actual action. That record beats a screenshot of an offline app tile, and it makes the next outage predictable for anyone else in the house.
Pick an automatic routine with a physical result. A contact sensor turning on a lamp is better than a push notification because you can see the result without asking the cloud. Avoid a door lock, alarm, heater, or anything safety-critical for the first experiment.
This is also where you decide how much offline operation you actually need. Lights and a leak shutoff earn a local path. A weather announcement can wait.
The smart-home troubleshooting map helps separate network, radio, and load faults before you reset a device. If your outage plan includes physically relocating a hub or router, use the home installation guide to check placement and mounting without confusing a signal problem with a software problem.
Now answer “does SmartThings work without internet” for your own house: disconnect only the WAN, trigger one essential automatic routine, and write down which physical action still happens.
Bolt & Bulb covers what goes wrong after the unboxing: devices that drop off Wi-Fi, dimmers that flicker with LED bulbs, locks that will not fit a rental door. The site draws on manufacturer documentation, platform support pages and release notes, and attributed owner reports in public forums.