What Happens If Home Assistant Goes Down?

The short answer: Home Assistant stops, not necessarily the whole home

When Home Assistant Core—the main Home Assistant software—is unavailable, it cannot notice events, run automatic routines (called automations), update its dashboard, or send commands on your behalf. A motion light that depends on Home Assistant will not turn on automatically, though its ordinary wall switch may still work. A dashboard button will not control the room. Routines that connect different systems—such as a motion sensor telling a smart plug what to do—pause because Home Assistant was the link between them.

That does not mean every connected device becomes useless. A conventional hard-wired switch that directly controls its light or fixture still works. A thermostat may keep a set temperature or protection rule stored in the thermostat itself. A lock with a working key cylinder can still use its key. A separate hub, device schedule, or directly paired remote may continue doing work that never needed the main Home Assistant software.

The exact answer therefore depends on where each decision lives. Treat Home Assistant as one part of the control path, then deliberately decide what should happen when that part is missing. The goal is not to keep every convenience automation alive. It is to keep the house understandable, safe, and usable until Home Assistant returns.

First, identify what actually went down

“Home Assistant is down” can describe several failures with different effects. Check the Home Assistant computer, home network, and power before assuming every device has failed.

A Core restart is narrower than a whole-computer failure. On Home Assistant OS, the Supervisor runs the main software and optional add-on services separately, so an add-on that does not depend on Core may continue during a Core restart. Home Assistant Container installations do not have Supervisor-managed add-ons. Either way, Home Assistant automations do not run until Core returns. If the computer, storage, power, or shared network fails, more of those pieces disappear together.

If the problem is only the internet, use Tara's guide to what smart-home controls can do during an internet outage. If utility power is the concern, plan a battery backup and safe Home Assistant shutdown rather than repeatedly cutting power to the computer.

What can keep working without Home Assistant?

Ordinary physical controls

A conventional wall switch, a dimmer that controls its own light or fixture, the buttons on a thermostat, and a physical door key do not need a Home Assistant automation. Keep those controls reachable and familiar. A smart bulb behind a wall switch is a special case: the switch may make the lamp light, but removing power also disconnects the bulb from its network. Decide whether that is an acceptable emergency behavior for the room.

Device-owned behavior and independent hubs

Some devices hold a schedule, set temperature, countdown, or protection rule themselves. Some dedicated hubs also run their own lighting or shade behavior. Those functions can continue if the device or hub is powered and the rule genuinely lives there. A wall dimmer or manufacturer-paired remote is a better fallback than assuming a vendor phone app will always be available. For example, Lutron states that a Caséta Smart Hub is not required for a directly paired Pico remote to control a Caséta device; your exact pairing and programmed behavior still need an outage test.

Direct Zigbee and Z-Wave control

Zigbee is a low-power network used by many smart-home sensors and controls. ZHA, Home Assistant's built-in Zigbee connection, can create a binding between a compatible remote or switch and another device or group. Home Assistant's documentation says those bound commands bypass ZHA. A supported binding can therefore keep a basic light control working even while ZHA or Home Assistant is unavailable. Binding support and button behavior differ by device, so do not assume every Zigbee product can do this.

Z-Wave is another low-power device network. It has a related direct link called an association. A supported device can send basic commands directly to another Z-Wave device without routing the decision through a Home Assistant automation. Association groups and the commands they send are device-specific, so check the manuals for both devices. They are useful for a deliberate fallback, not a replacement for every automation.

If an essential control uses Matter, the cross-brand smart-home standard, do not assume it has the same option. Tara's Matter switch-to-light binding guide explains that narrower case without promising that every Matter device can work through a direct fallback.

What normally stops when Home Assistant is unavailable?

• Automations, scripts, and scenes run by Home Assistant: the main software is no longer noticing events or carrying out the steps.
• Dashboards and Home Assistant app commands: the screen cannot reach the main software to show current status or send a command.
• Rules between different systems: a sensor on one system cannot trigger a device on another if Home Assistant is the only link between them.
• Home Assistant notifications and exposed voice controls: new requests, alerts, and messages that pass through Core wait or fail.
• Radio adapters attached to the failed computer: a USB Zigbee or Z-Wave adapter and its control software stop if the whole computer loses power.

A vendor's internet-based app might still reach a device through the vendor's online service while Home Assistant is down, provided the device, router, internet connection, and vendor service are all available. That can be convenient, but it is a long chain to treat as the only fallback for an important household function.

Build a graceful fallback in six steps

1. Choose the essential functions. Start with lighting at entrances and stairs, access, basic climate control, water control, and a safe way to identify a beeping device. Never silence or bypass a smoke, carbon-monoxide, security, or equipment alarm except through its manufacturer-approved procedure. Not every scene needs a backup.
2. Preserve a physical action. A person should be able to operate the essential function without opening a Home Assistant dashboard. Label an unfamiliar button or remote.
3. Move only the necessary fallback closer to the device. Use a device-owned schedule, an independent hub control, a compatible direct binding, or a Z-Wave association when it solves a real outage need.
4. Keep safety protection independent. Smoke and carbon-monoxide alarms, equipment limits, emergency unlocking, and other manufacturer safety features should not rely on a convenience automation.
5. Protect recovery. Use reliable storage, graceful shutdown, an automatic backup stored somewhere besides the Home Assistant computer, and the credentials or emergency kit needed to restore it. Tara's Home Assistant backup guide covers the recovery side.
6. Write down the household version. One page should say what still works, which controls to use, and who knows how to restore the system.

Do not create a hidden maze of duplicate automations across Home Assistant, vendor apps, Alexa, Apple Home, Google Home, and SmartThings just to chase uptime. Each extra owner makes normal troubleshooting harder. Put the essential fallback in one understandable place and test it.

Run a safe 15-minute restart test

This is a Core-restart test only. Passing it does not prove what will work if the whole computer, router, or power supply fails.

1. Pick a safe time and tell the household. Do not test while a door, gate, heater, pump, or other important process is mid-cycle.
2. Write down the expected fallback. Choose two or three ordinary actions, such as switching on a hall light, changing the thermostat at its own controls, and unlocking a door with the normal backup method.
3. Use Home Assistant's supported restart control. Do not pull the power plug to simulate a Core restart. An abrupt power cut tests storage risk as much as control resilience.
4. Try the physical controls while Core restarts. Confirm which lights, remotes, thermostats, locks, and hub-owned routines work without the app.
5. Confirm recovery. When Home Assistant returns, check the dashboard, automations, radios, and the devices most important to the household. The post-restart unavailable-device checklist is useful if something does not reconnect.
6. Record the surprise. Fix one confusing dependency, update the household note, and test again before calling the fallback dependable.

Would a second Home Assistant server solve it?

Not by itself. A spare computer does not automatically restore your Home Assistant settings, reconnect Zigbee or Z-Wave adapters, use the old computer's address on the home network, or recover security keys and add-on data. Two live servers trying to control the same devices can make the failure harder to understand.

A tested full backup can restore much of the installation, but attached radio adapters and their controller data still need the documented move or restore path. For most homes, the first resilience gains are simpler: preserve physical controls, back up Home Assistant away from its computer, use protected power, keep essential network equipment stable, and document recovery. A prepared spare machine can shorten recovery, but it is a restore plan—not automatic takeover unless the whole design was built and tested for it.

If you do plan a second computer, list every shared dependency before buying it. The radio adapter, router, storage, separate device hub, or power source may be the part that can still stop both systems.

Draw a firm line around safety and access

Home Assistant is excellent for convenience, visibility, and additional warnings. It should not be the only layer protecting people or property. Use certified smoke and carbon-monoxide alarms that meet local code. Choose locks, garage doors, and water shutoffs with a manufacturer-approved local or manual access method. Preserve any manufacturer-provided thermostat equipment limits or freeze protection, and keep its documented manual controls usable.

A Home Assistant notification can supplement a dedicated alarm, not replace it. A clever automation can close a valve early, but it should not hide the valve's manual control. If an outage turns a safety device into an unknown state, stop and redesign that path before adding more automation.

Tara's practical approach

Resilience starts with a simple question for every important room: “What can a person do if the server is unavailable?” The answer should be visible at the wall or device, not buried in an administrator's phone. Then add only the direct links and independent controls that solve a real household need.

A configured Home Assistant smart-home system should include normal physical controls, protected power, recovery from a backup stored away from the Home Assistant computer, and a short outage test—not just a larger automation count. That makes the home calmer during maintenance and easier for another resident to use.

Frequently asked questions

Will my lights still work if Home Assistant is down?

A conventionally wired wall switch that directly controls its light or fixture, or the device's own physical control, can still work. Home Assistant automations and dashboard commands do not. Smart bulbs, relays, direct device links, remotes, and separate hubs vary, so test each important room while Home Assistant is safely stopped.

What happens to automations while Home Assistant restarts?

Home Assistant Core is not responding to events or running its automations during the restart. Separate hubs may continue. On Home Assistant OS, some add-on services that do not depend on Core may also continue, but anything that needs Core waits until it is available again.

Does Zigbee work when Home Assistant is down?

ZHA, Home Assistant's built-in Zigbee connection, stops providing ordinary app and automation control. Compatible Zigbee devices with a direct link called a binding can still exchange bound commands, and their physical controls may still work. That behavior is device-specific and must be tested.

Does Z-Wave work when Home Assistant is down?

Home Assistant automations and app control stop. A supported direct link, called a Z-Wave association, can let one device control another, but it does not replace all controller functions and support varies by device.

Is an internet outage the same as Home Assistant going down?

No. If the Home Assistant computer and home network are still running, devices and automations that stay inside the home can continue during an internet outage. Vendor services, remote access, and voice or notifications that need the internet may not.

Should I keep a second Home Assistant computer ready?

A second computer does not automatically inherit your settings, device connections, radio adapters, network address, or security keys. Most homes get more practical resilience first from physical controls, a tested full backup, protected power, and a documented restore path.