Power cuts, Wi-Fi and smart homes: making it reliable
A routine is only useful if you understand what it depends on. Power, the internet connection and the network inside the house are different parts of that picture. Ask about each one when planning a smart home.
Keep everyday coordination local
The Hearth architecture in development uses compatible Zigbee and Wi-Fi devices with a local Home Assistant hub on hardware in the home. Compatible local controls can work without internet while power and the required hub, network and devices remain available.
This is not a promise that every device or feature works offline. Remote access and chosen cloud integrations need connectivity; the proposed devices, accounts and recurring dependencies must be assessed for each setup.
Separate internet loss from a local network problem
The internet connection brings outside services into the home. Wi-Fi is part of the network used by devices inside it. Local coordination still needs functioning equipment and a way to communicate with the selected devices.
During the walkthrough, ask which proposed devices use Zigbee and which use Wi-Fi. Ask what happens to each routine if the internet connection drops, and separately what happens if the local network is unavailable. Confirm what manual controls remain usable.
Treat power as its own question
Running the hub locally does not establish a power-backup arrangement. As our Indian-home engineering notes explain, backup power must be planned separately from internet independence. The published package list does not specify backup equipment or runtime. Ask:
- Which hub, network equipment and devices would remain powered in this home?
- Which agreed controls and routines would remain available?
- What should the household expect when power and connectivity return?
- Which failure and recovery behaviours have been checked on the selected hardware?
Use the answers to understand the proposed installation. Internet-loss behaviour does not establish mains-power-loss behaviour or a backup duration.
Look for the result, not just the command
Reconciliation is part of the intended architecture: compare the requested action with reported device state and flag a mismatch. An activity timeline is intended to help explain actions and their reasoning. These capabilities are in development, and device feedback support and commissioning need assessment.
Hearth’s current hardware work starts with an own-room bench prototype. Existing physical switches are intended to remain usable if the hub or network fails; manual fallback is a requirement to verify. The browser simulation and sample-data screens are not evidence that a physical home has passed those checks.
Pump stop safeguards still need development and testing. Automation must not be relied on as tested flood protection or as a replacement for certified safety systems.
Bring a reliability checklist to the walkthrough: internet, local network, power, manual controls and recovery. Ask which behaviours can be demonstrated now and which still need development or checks for your home’s scope.