Entity state
A screenshot of the entity state, recent history, or diagnostics.
Home Assistant device offline
Use this flow when a Home Assistant device or entity is unavailable, unknown, or stale. The goal is to verify power, recent changes, and logs before you start restarting the whole stack.
Safety first: avoid flattening network security or repeatedly rebooting
the whole stack before you collect logs and diagnostics.
What this flow is for
This flow is for Home Assistant devices or entities that show as unavailable, unknown, or stale, but the real cause is still unclear.
First safe checks
- Check whether the entity is unavailable, unknown, or just stale.
- Confirm the device has power or a healthy battery.
- Ask what changed recently: location, battery, SSID, firmware, coordinator, or integration.
- Collect logs before restarting the integration or the whole stack.
Evidence requests
Ask for the best evidence first
Power check
A quick note on battery level or whether the device still has stable power.
Recent change
What changed right before the device went offline.
Likely causes
Most likely problem buckets
Power or battery issue
The device is offline because its current power path is weaker than expected.
Network or mesh path problem
The device lost a reliable Wi-Fi, Zigbee, or routing path.
Integration issue
Credentials, sessions, or the integration path itself no longer look healthy.
Location or range change
The device moved far enough that the old signal path no longer works.
Next safe steps
Take one step at a time
ACT-AUTO-001
Confirm the entity state and the device's current power or battery condition.
ACT-AUTO-003
Collect logs and diagnostics before restarting the integration or the whole stack.
ACT-AUTO-006
Wake or re-pair sleepy devices close to the coordinator or AP when appropriate.
ACT-AUTO-010
Inspect network isolation, mesh quality, or integration credentials depending on device type.
Best follow-up ask
Is the entity unavailable, unknown, or stale, and what changed right before it went offline?
When to stop and hand off
Escalate when the same device repeatedly goes offline after wake or re-pair and a basic integration review still does not explain it.
Support links
Use the next page that matches the new symptom
If the device comes back but automations still fail, or if pairing becomes the real problem, switch to the closest recovery page instead of repeating the same checks.
Open automation-did-not-run flow Open Zigbee pairing guide