In this guideJump to a section
“Local control” is not one yes-or-no property. A hub can discover sensors on your network while a vendor cloud runs the automation. It can keep a rule working without internet but lose remote notifications. Write down the action you need before choosing the hub.
This is a selection checklist. To document an installed system, use the offline smart-home audit. For protocol differences use Matter vs Thread vs Zigbee vs Z-Wave.
Ask which part stays local
| Requirement | Question for the maker | Inadequate proof |
|---|---|---|
| Sensor and light compatibility | Are exact models and firmware supported? | “Works with Zigbee” on a listing |
| Automation execution | Does this specific rule run on the hub? | The device merely pairs locally |
| Thread network | Is a border router supplied or required? | A Thread logo without architecture |
| Matter controller | Does it support the intended Matter device type? | Confusing a controller with a radio |
| Backup/restore | Can local settings and pairings be recovered? | An account backup with no restore plan |
| Outage behavior | What works without ISP, router, or hub power? | Generic “offline” branding |
The Connectivity Standards Alliance FAQ explains that Matter runs over supported networks. The Thread Group distinguishes network border routers from application control. One device can perform multiple roles, but buyers must verify them rather than assume interoperability.
Test the right failure
ISP-only outage: with the router and hub still powered, a documented local automation may keep operating; cloud alerts may not.
Router power loss: even local IP devices may lose the path to a controller. A separate Zigbee sensor could still speak to a powered hub without restoring the entire automation.
Hub power loss: battery sensors alone do not execute the hub’s rules. A power bank or UPS must be chosen by exact voltage, connectors, electrical rating, runtime and maker instructions, not a universal claim.
An internet test is not permission to disconnect smoke alarms, home entry locks, medical devices or hazardous appliance controls. Use a benign light/sensor rule. Record how you restored the normal configuration.
Do not ignore support and security
Local devices still need security updates and protected administrator accounts. Ask when the hub, radio add-on and any bridge stop receiving updates, whether old integrations are deprecated and how the home continues if the hub fails. If cameras are connected, follow the FTC guidance on secured viewing and updates.
Prefer a manual override for every convenience automation. Never depend exclusively on a remote app to enter your home or to activate required life-safety equipment.
Local hub verification card
| Device/requirement | Exact maker documentation | Controlled test | Manual fallback |
|---|---|---|---|
| Three household device models | |||
| Local trigger and action | |||
| Matter/Thread/bridge functions | |||
| Offline network and power needs | |||
| Backup, restore and updates |
The next action is to send the card to a prospective maker or dealer with your actual model list. Replacing a working hub without evidence of a missing function is not an SEO-driven buying requirement.