How the system comes together
local sensors (sense)
local hub and LAN (control)
the offline scene list (actions)
a signed offline-capability table handed to the client (operation).
What makes the delivery work
locks, lighting, and core scenes offline as the baseline; cloud features such as voice assistants labelled separately; tested on site, not taken from vendor claims.
Who it’s for
- Smart Home Integrators
- US or Canadian project owners working with an appropriately qualified local installer
The project challenge
- Cloud outages can leave users unsure which controls still work locally.
What the system should achieve
- Create an offline capability table from a deliberate WAN-disconnect test.
Recommended system architecture
- Inventory exact models → choose controller and vendor bridge boundaries → map supported states/actions → test a pilot
- Keep proprietary advanced features in their vendor app when the standard bridge does not expose them.
Equipment & ecosystem choices
- Documented vendor bridges/controllers, IP network and only supported device types
- Possible Aqara and Philips Hue branches; no direct third-party Zigbee pairing assumption
Installation & technical requirements
- Record model, region, firmware, pairing owner and recovery steps; test each requested rule before replicating it.
- Site acceptance focus: Create an offline capability table from a deliberate WAN-disconnect test.
Compatibility & construction constraints
- Matter, Zigbee and Thread have different roles. A shared protocol logo does not prove all features, controllers or commercial workflows are compatible.
- Do not claim all automation, voice or notifications remain available without testing.
Make it your own
- For offline-capable controls assessment, confirm room/door/zone counts, agreed controls, notification recipients and installation stage.
- Specific decision: Do not claim all automation, voice or notifications remain available without testing.
Preliminary equipment plan
- Start with one representative unit of every model/firmware combination, its required controller/bridge and a pilot network; scale only after acceptance.
- Scale by the surveyed scope for offline-capable controls assessment, not by a fixed package advertised without a site schedule.
What shapes the budget
- Model combinations, rule count, network changes, licenses if applicable and maintenance ownership.
- Country/city, labor, taxes, shipping, warranty route and confirmed supply source; no price or stock is assumed.
