Designing a connected home for disconnection
Offline behavior is part of a device experience, not an exception to it.
Draw the dependency path
A single home automation may depend on a sensor, local radio, controller, router, internet connection, and hosted account. Map each dependency before deciding what reliable means. A local protocol does not automatically make the entire routine local.
Make failure understandable
Distinguish unavailable, stale, and unknown state. A stale temperature reading is different from a fresh reading that happens to be unchanged. Preserve timestamps, show uncertainty, and keep manual control available wherever an action affects the physical environment.
Treat reconnecting as its own case
Buffered events can arrive late or more than once. Define when an old event should be discarded and which actions can be repeated safely. Recovery should not unexpectedly replay a long queue of physical actions.
A proposed test boundary
Start with a simulated sensor and actuator, inject a network interruption, and inspect the resulting event sequence. These are proposed test conditions for the interoperability concept; no device or platform has been certified or validated by the lab.