What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Keep the control loop inside your home. Put automations on an always-on local controller, choose devices that communicate over Zigbee, Z-Wave, Matter, Thread or ESPHome, and test them with the internet disconnected. A cloud outage can remove a vendor’s app, remote access, cloud voice commands, notifications and analytics, but it does not automatically stop a device that is controlled locally. Home Assistant describes the principle plainly: it runs on hardware in your home and can keep working when the internet is down.
What actually stops working when a smart-home cloud goes offline?
The first distinction is between your local network and the internet connection (the WAN). Your router, Wi-Fi access points, Ethernet switches and local controller can remain available even when the connection to the vendor’s servers fails. Devices that receive commands across that local network can continue operating; functions that require a remote server cannot.
As an Amazon Associate I earn from qualifying purchases.
Functions commonly lost in a cloud outage
- The manufacturer’s phone app may fail to sign in or show devices.
- Control while you are away from home stops unless you have another remote-access path.
- Cloud voice integrations and routines, such as commands routed through an online assistant, stop responding.
- Push notifications, vendor-hosted schedules, telemetry, account dashboards and cloud analytics may disappear.
- Camera recording or live viewing can fail when video is relayed or stored by the vendor.
- Firmware delivery, device enrollment and other server-side management may be unavailable.
Functions that can continue locally
- A locally hosted automation can still turn a light on when a motion sensor reports activity.
- A schedule stored on a local controller can run without an internet route.
- Direct commands over a powered Wi-Fi, Zigbee, Z-Wave, Thread or Matter network can continue.
- Manual controls on the device, such as a wall switch or button, are generally independent of the vendor’s cloud path.
These outcomes depend on power, the local network and the device’s implementation. If the router, controller or radio coordinator is also down, local control will fail even though the vendor’s servers are healthy.
Which smart-home protocols work without internet access?
Local protocols carry commands inside the home. They are the foundation of a resilient installation, but a protocol label alone is not a guarantee: the controller, device firmware and particular feature must all support local execution.
#1 Best Overall
- Powered by SmartThings: Connect, monitor, and automate your home through the SmartThings app. Build a reliable, unified smart home using Samsung's proven ecosystem
- Matter + Zigbee Smart Home Hub: Supports the newest Matter standard plus Zigbee for lighting, sensors, plugs, switches, thermostats, and more - thousands of compatible devices. PLEASE NOTE: Z-Wave not supported
- Easy Setup with Wi-Fi or Ethernet: Get started in minutes using Wi-Fi or a wired Ethernet connection for apartments, houses, and expanding smart home systems - Z-Wave not supported
- Automations That Work for You: Create custom routines for security, lighting, comfort, and energy savings. Many local automations continue working even if your internet goes offline
- Wide Device Compatibility: Connect compatible smart devices from Aeotec and many other brands to build a unified system for lighting, voice control, energy management, and climate settings
| Protocol | Where commands can run | What remains possible during WAN loss | Important dependency |
|---|---|---|---|
| Zigbee | Between a local coordinator and devices | Local lights, sensors, switches and automations can continue while the coordinator and network have power | A Zigbee coordinator and a local automation host are required |
| Z-Wave | Through a local Z-Wave controller | Local device control and rules can continue without the vendor’s internet service | The controller must remain powered and retain its device configuration |
| Matter over Wi-Fi | On the home IP network | Local Matter commands can work when Wi-Fi and the controller are available | Remote control still needs an internet-connected controller and cloud path |
| Matter over Thread | Across a local Thread mesh | Local Matter commands can work over the Thread network | You need a powered Thread border router and Matter controller |
| ESPHome | On the device and local controller | Locally integrated sensors, switches and automations can continue | The device must be configured for local operation before the outage |
Home Assistant identifies Zigbee, Z-Wave, Matter, Thread and ESPHome as local options. A local link does not make every feature local: cameras, vendor-specific intelligence, over-the-air updates and telemetry can still call home.
What local architecture keeps the most devices usable?
Use a local controller as the decision-maker, local device links as the transport, and cloud services only as optional extensions.
1. Always-on controller
Run Home Assistant on hardware that stays in the house. Home Assistant Green is its recommended plug-and-play option; a Raspberry Pi, mini PC, NUC or virtual machine can also host it. The controller stores integrations, device state and automations so those decisions do not depend on an external account.
2. Local radios and bridges
Choose a controller with the radio your devices need, or add an adapter. Home Assistant Connect ZBT-2 can provide Zigbee, Thread and Matter radio support where required. A bridge is still necessary for devices whose native protocol is not built into the controller.
3. Automations that execute locally
Build schedules, scenes and sensor-triggered rules in the local controller. Do not assume that a routine created in a manufacturer’s app is local; it may be stored and evaluated on the vendor’s servers.
4. Optional cloud services
Keep cloud access for remote control, online voice assistants, notifications, vendor analytics or updates when those benefits justify the dependency. Treat each one as a convenience layer, not as the only way to operate essential lights, locks or heating.
5. Power and network continuity
A local design still needs electricity and a functioning home network. Keep the controller, router, access points and radio coordinator on reliable power; a UPS can preserve short outages, but it cannot replace a failed broadband service for remote access.
Is Matter enough to protect a smart home from a cloud shutdown?
Matter improves local interoperability, but it is not a promise that every feature is cloud-free. Google says Matter-enabled devices are designed to work locally over the existing home network without connecting to the internet to carry out commands.
What Matter does locally
A Matter controller can send commands to Matter devices over Wi-Fi or Thread inside the home. Basic actions such as switching, dimming, sensing or changing a supported setting can therefore continue when the WAN is unavailable.
Rank #2
- Echo Hub — An easy-to-use smart home control panel redesigned for your home. Arrange controls on your dashboard to quickly adjust devices, view cameras, start routines, and more.
- Customize your dashboard — Arrange devices into sections and resize them to focus on what matters most. Create a personalized layout that matches how your family uses their connected devices.
- Reimagined for your home - With an Alexa+ and compatible Ring subscription (sold separately), get Ring camera event summaries to stay in the know. Search your Ring footage using simple voice commands. Create routines by voice, activate modes to manage multiple devices at once, and chat with Alexa to easily control your smart home.
- Home security for the whole family — Use Echo Hub to easily arm and disarm your compatible security system, making it easy for everyone in your family to manage home security. Use the Alexa app and compatible cameras, locks, alarms, and sensors to check in while you're out.
- Works with thousands of Alexa compatible devices — WiFi, Bluetooth, Zigbee, Matter, Sidewalk, and Thread devices sync seamlessly with the built-in smart home hub.
What still needs the internet
The Connectivity Standards Alliance describes Matter as a local connectivity technology and notes that Matter-only devices require an internet-connected controller for control while you are away from home. Remote access needs an online path, and vendor services may still handle account functions, telemetry, firmware distribution, camera streaming or proprietary intelligence.
Recommended Free Tools
Thread-specific requirements
Thread devices need a powered Thread border router, while Matter control needs a compatible controller. If either is missing or loses power, the Thread device may appear unavailable even though the internet itself is working.
How do you migrate devices before a vendor shuts down its service?
Do the migration while the vendor’s servers still work. That gives you time to retrieve credentials, install firmware, identify reset procedures and confirm that each device has a local replacement path.
- Inventory every device. Record its model, firmware, room, power source, protocol, current account and the automations that depend on it. Mark devices that are cloud-only or whose local behavior is unknown.
- Separate essential from optional functions. Prioritize entry locks, lighting, heating, leak detection and alarms. Decide which remote notifications, voice commands and analytics can be lost without affecting safety.
- Check the local control method. Look for Zigbee, Z-Wave, Matter, Thread or ESPHome support and confirm whether the model needs a bridge, coordinator or border router. A device that merely has Wi-Fi is not necessarily locally controllable.
- Install the local controller. Set up Home Assistant Green or another supported host, connect it to the home network and add the required radio adapter. Keep the controller on the same LAN as Wi-Fi devices.
- Pair or import devices while the old service is available. Follow the device’s documented pairing or reset process. Some products must be factory-reset before joining a new controller; record the reset sequence before removing the old integration.
- Recreate automations locally. Move schedules, scenes and sensor rules into the local controller. Test each trigger and action independently before deleting the cloud routine.
- Back up the controller. Home Assistant says it creates an automatic backup before each update. Also create a manual backup after major pairing or automation changes and keep a copy away from the controller.
- Document recovery details. Save model numbers, pairing codes, network names, reset instructions, radio channel information and the location of backups. This shortens recovery if hardware fails after the shutdown.
- Run an offline test. Disconnect the WAN while leaving the router, controller and radios powered. Confirm local controls, schedules and safety automations, then restore internet access and verify that optional cloud functions return.
How should you test local operation?
Test the exact failure you want to survive rather than assuming that a device is local because it responds once.
| Test | How to perform it | Expected result | If it fails |
|---|---|---|---|
| Basic device command | Block the WAN but keep the LAN powered; operate a switch or sensor from the local controller | The device responds with normal local delay | Check whether the command is routed through a cloud integration |
| Scheduled automation | Set a short test schedule, remove internet access and wait for it to run | The schedule fires on time | Rebuild the rule on the local controller instead of the vendor service |
| Sensor-triggered rule | Trigger motion, contact or temperature input while offline | The local action occurs | Check the sensor’s radio link, battery and controller automation trace |
| Remote access | Use a phone on cellular data while the home WAN is disconnected | Remote control fails or is unavailable | This is expected unless you have a separate internet path; local resilience does not equal remote access |
| Power recovery | Restart the controller and radio coordinator | Devices reconnect and automations resume | Restore a backup or re-pair only the devices that did not recover |
What does a real cloud shutdown look like?
Belkin’s Wemo notice illustrates why testing before a deadline matters. Belkin says Wemo cloud-dependent features, including the Wemo app, remote access, Amazon Alexa and Google Assistant, stop working on January 31, 2026. It says devices configured with Apple HomeKit before that date may continue operating locally and that its Thread-based products are unaffected.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →That is a model-specific migration example, not a guarantee for every Wemo product or another manufacturer. The practical lesson is to read the shutdown notice for exact models, dates and prerequisites, then complete local pairing before the stated cutoff.
Which control model is best for outage resilience?
The trade-off is between convenience and independence. The more decisions a vendor cloud makes for you, the more functions disappear when that service is unavailable.
| Control model | Where commands run | WAN-loss behavior | Account dependence | Remote access | Setup and recovery |
|---|---|---|---|---|---|
| Cloud-only device | Vendor servers | App, schedules and automations may stop | High | Built in while service exists | Simple initially; difficult if service closes |
| Local controller with Zigbee or Z-Wave | Home controller and local radio | Core control and automations can continue | Low after pairing | Requires a separate secure remote path | More initial setup; backups are portable |
| Local Matter over Wi-Fi | Home IP network and Matter controller | Local commands can continue | Lower for basic control; vendor features may remain dependent | Needs an internet-connected controller | Controller and ecosystem compatibility matter |
| Local Matter over Thread | Thread mesh and Matter controller | Local commands can continue if border router is powered | Lower for basic control | Needs an internet-connected controller | Requires Thread border-router planning |
| ESPHome integrated locally | Device firmware and local controller | Configured functions can continue | Low | Separate remote path required | Flexible, but configuration should be documented |
What about cameras, voice assistants and media?
These categories commonly retain cloud dependencies even in an otherwise local installation. A camera may expose basic local streaming but use the vendor for remote viewing, recording, object recognition or notifications. A voice assistant generally sends speech to an online service, so commands routed through that assistant can fail during an outage. Media casting, account authentication and subscription checks may also require internet access.
Keep essential actions available through a local switch, dashboard or automation. Treat cloud voice, off-site video storage and vendor intelligence as optional layers, and verify each advertised local mode rather than inferring it from the protocol name.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
- [Multi-Protocol Hub with Matter Bridge] The M3 is a versatile hub supporting Aqara Zigbee and Thread devices. It integrates third-party devices into the Aqara Home app. Supports advanced Matter bridge functionality, enabling Aqara-exclusive scenes and signals to sync with Matter ecosystems such as Home Assistant for seamless integration. Supports up to 127 Aqara Zigbee devices （** Not third-party Zigbee devices) and 127 Thread devices (Repeaters are needed).
- [Edge Compatibilities and Local Automations] The M3 serves as an Edge Hub, prioritizing local control and automation. Upon integration, it supersedes existing Aqara hubs, shifting the automations among them to local operation (Some cloud-based notifications still require internet). Upgrade-friendly, it supports migrating Zigbee devices from older Aqara hubs.
- [Smart IR Blaster with Feedback and Learning] The 360°IR blaster not only sends commands but also provides accurate status updates by detecting traditional remote use. It connects IR air conditioning units to Matter, functioning as an AC thermostat when paired with an Aqara Temperature and Humidity Sensor. (Note: Only one AC device can be exposed to Matter. Functionality may vary based on the Matter integration app. For Apple Home exposure, use Matter integration instead of HomeKit.)
- [Optimal Wired and Wireless Connectivity] Offering both wired and wireless solutions, the smart home hub M3 provides dual-band Wi-Fi (2.4/5 GHz) with advanced WPA3 security, and a Power over Ethernet (PoE) port. The addition of a USB-C port allows for mini-UPS and power bank connections, delivering unparalleled stability. (2A USB power adapter is not included. ) . Note: To ensure a stable connection, place the Hub M3 between 6 to 19 feet from the router.
- [Privacy-Focused with Encrypted Storage, Easy Setup and Versatile Placement] The M3 prioritizes privacy by excluding microphone or camera components. It boasts 8GB end-to-end encrypted local storage, for device lists, configuration parameters, and automation configuration data. Additionally, it includes a mount and screws for flexible placement on flat surfaces, walls, or ceilings. Magic Pair technology ensures effortless detection by the Aqara Home app upon power-up.
How do updates and recovery work without the cloud?
Local control and software maintenance are separate concerns. A device can continue its existing functions offline while being unable to download a new firmware image. Plan updates while internet access is available, and do not begin a migration immediately before a known shutdown unless you have a tested rollback.
- Keep the controller’s backups on separate storage.
- Record the versions and settings that worked during your offline test.
- Update one device or integration at a time, then verify automations.
- Retain the old controller or bridge until the replacement has passed testing.
- For a failed pairing, use the documented factory-reset sequence and restore the controller backup before attempting a full rebuild.
What are the most common failure modes?
The device works in the manufacturer app but not locally
That usually indicates a cloud-only integration or a local feature that was never enabled. Check the model’s protocol and local-control documentation, then replace the cloud routine with a supported local integration.
Local automations stop after the router restarts
Confirm that the controller has a fixed or discoverable address, that the radio coordinator reconnects, and that devices rejoin the same network. Battery devices may need time to check in after the network returns.
Matter devices appear online but remote control fails
This is normal when the WAN is unavailable. Matter’s local path can remain healthy while away-from-home control fails because it needs an internet-connected controller and cloud route.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteOnly advanced features fail
Separate the basic local command from cloud services such as notifications, telemetry, camera analysis and OTA updates. Preserve the local function and decide whether the advanced feature is worth retaining as a dependency.
How can you make the setup easier to maintain?
- Prefer products documented for local control and tested with your chosen controller.
- Keep one naming scheme for rooms, devices and automations so a migration is auditable.
- Use manual controls for critical lights, locks and heating instead of relying on a phone app.
- Review the setup after every firmware or controller update.
- Schedule an offline test at least after a major platform change and before a vendor’s published shutdown date.
Frequently Asked Questions
Will smart lights work if my internet service is cut but my Wi-Fi is still on?
They can, if the lights and their controller communicate locally and the automation is stored inside the home. A Wi-Fi connection to the router is not the same as an internet connection to the vendor.
Can I control Matter devices from outside my house without a cloud service?
Not with Matter alone. Matter’s local protocol handles in-home commands; away-from-home control requires an internet-connected controller and a remote-access path.
Do I need a separate hub for Thread devices?
You need a powered Thread border router and a Matter controller. A controller or adapter that provides those roles can avoid buying multiple boxes, but compatibility must be checked for the specific device.
What should I save before a smart-home company closes its servers?
Save controller backups, device model and firmware details, pairing codes, reset instructions, network information and a list of automations. Complete local pairing and an internet-disconnected test while the original service still operates.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
