Smart Doorbell Shows Offline in Home Assistant: Step-by-Step Repair Guide
If your smart doorbell shows offline in Home Assistant, start by checking its native app and your network. In most cases, the camera is still running but the integration lost connection. The counter-intuitive truth: a doorbell that works perfectly in its own app can show as offline in Home Assistant due to integration, API, or protocol issues — not a dead device. Here’s a practical repair guide.
Early Checkpoints (Before Deep Troubleshooting)
Run through these five quick checks. They take under two minutes and often solve the problem.
- Power: Is the doorbell still lit or responding to presses? If it rings but shows offline, power is fine.
- Wi-Fi signal: Open the doorbell’s native app and check signal strength. Below 2 bars? Move closer or add a repeater.
- Integration status: In Home Assistant, go to Settings → Devices & Services → Integrations. Look for a yellow or red warning on your doorbell integration.
- Device firmware: Check the doorbell’s app for pending firmware updates. A forced update can break third-party integrations.
- Hub/coordinator status: If using Zigbee (ZHA/Zigbee2MQTT) or Thread, confirm the coordinator is online. A dead coordinator makes all its devices appear offline.
Likely Causes (Buckets to Rule Out Fast)
| Cause Bucket | What to Look For | Quick Fix |
|---|---|---|
| Network connectivity | Doorbell app shows online, but HA can’t reach it | Check router’s 2.4GHz band, static IP, or firewall rules |
| Integration API break | Doorbell firmware updated | Re-authenticate or re-install the integration |
| Zigbee/Thread coordinator | Other Zigbee devices also offline | Restart coordinator or re-flash Zigbee2MQTT |
| Battery power (wireless models) | Doorbell responds only when pressed | Replace or charge battery; check voltage |
| Protocol mismatch | Using Matter with a non-certified bridge | Verify Matter controller compatibility (Apple Home, Google Home, SmartThings) |
| Stale HA cache or addon | Integration logs show connection but no data | Restart just the integration addon (e.g., Zigbee2MQTT, Tapo Controller) from the Supervisor panel |
Ordered Action Steps (Operator Flow)
Step 1 – Verify the Doorbell in Its Own App
Open the doorbell’s manufacturer app (e.g., Tapo, Ring, Eufy, Arlo). Can you see live video? Does pressing the doorbell trigger a notification? If yes, your doorbell hardware and network are fine. Proceed to Step 2. If not, fix the native app issue first — likely power or Wi-Fi.
Step 2 – Check Home Assistant Integration Logs
Go to Settings → System → Logs. Filter by the integration name (e.g., `tapocontrol`, `ring`, `eufy`). Look for error messages like:
- `Timeout connecting to device`
- `Invalid token`
- `Failed to update`
If you see token or authentication errors, re-authenticate the integration. For timeouts, check network latency between HA and the doorbell.
Step 3 – Restart the Integration (Not the Whole System)
Disable and re-enable the integration:
1. Settings → Devices & Services → Integrations
2. Click the three dots on your doorbell integration → Disable
3. Wait 10 seconds → Enable
This often clears stale connection states without disrupting other automations.
Step 4 – Check Your Zigbee/Thread Coordinator (if applicable)
If your doorbell uses Zigbee (e.g., Aqara G4, Zigbee2MQTT with a doorbell sensor), verify the coordinator:
- For ZHA: Go to Settings → Devices & Services → ZHA → check device count and signal strength.
- For Zigbee2MQTT: Open the Zigbee2MQTT dashboard. Is the coordinator online? Are other routers reachable?
- For Thread (via Matter): Use your Thread border router app (Apple Home, Google Home) to confirm the device is still on the Thread network.
If the coordinator is offline, restart it. If multiple Zigbee devices dropped, consider interference (e.g., USB 3.0 ports near the coordinator, metal barriers).
Step 5 – Update Firmware on Doorbell and Home Assistant
Firmware updates are the most common cause of integration breaks. Check the doorbell’s app for updates. Then update Home Assistant (Settings → System → Updates) and any relevant add-ons (Zigbee2MQTT, Tapo Controller, etc.). Reboot after updates.
Step 6 – Re-Pair the Device (Last Resort)
Only do this if every other step fails. Physical access required.
- For Wi-Fi doorbells: Put the doorbell into pairing mode, then delete the integration in HA, then re-add.
- For Zigbee/Thread: Use the coordinator’s “permit join” function, then factory reset the doorbell (usually a pinhole button). Re-pair.
Escalation signal – stop here if this happens: After re-pairing, if the doorbell’s native app also reports “offline” or disconnects within 24 hours, the hardware likely has a failing Wi-Fi radio or battery power circuit. Do not attempt further software fixes. Contact the manufacturer’s support line or check your warranty. Replace the unit if out of warranty — repeated re-pairing will not fix a dying radio.
Checklist: Quick Decision Aid
Use this to decide whether to proceed with software fixes or escalate.
| Check Item | Pass | Fail |
|---|---|---|
| Doorbell’s native app shows live feed | ✅ | ❌ → Fix native app first |
| Home Assistant integration logs show no errors | ✅ | ❌ → Address specific error |
| Doorbell firmware is up to date | ✅ | ❌ → Update firmware |
| Coordinator/router (if Zigbee/Thread) is online | ✅ | ❌ → Restart coordinator |
| Doorbell is within 15 meters of the Wi-Fi AP or coordinator | ✅ | ❌ → Move closer or add extender |
| You have not changed router settings recently | ✅ | ❌ → Check firewall, port forwarding, band steering |
If 4 or more pass, skip to Step 5 (re-pair). If fewer than 3 pass, start from Step 1.
Counter-Intuitive Angle: Offline in HA ≠ Dead Device
A doorbell that is offline in Home Assistant often still functions normally in its own ecosystem. For example, the Tapo 2K Wireless Smart Video Doorbell with Chime (D210) uses a cloud-based API. When its firmware updates, the local API endpoints change, breaking the Tapo Controller integration in Home Assistant. The doorbell still rings, records, and streams in the Tapo app — but HA sees nothing. This is not a hardware fault; it’s a protocol drift that requires re-authentication or integration updates.
A Common Recurrence Pattern (and How to Avoid It)
You follow every step, the doorbell comes back online, but 48 hours later it’s offline again. This pattern usually traces back to network instability — specifically, router band steering or short DHCP leases.
Most Wi-Fi smart doorbells only support the 2.4GHz band. If your router uses band steering (pushing devices to 5GHz when possible), the doorbell may appear connected but can’t complete the handshake with Home Assistant. The fix: create a dedicated 2.4GHz SSID for IoT devices and assign a static DHCP reservation for the doorbell’s IP address. If the problem still recurs, try a dedicated Wi-Fi extender placed within line of sight of the doorbell. A USB extension cable for a Zigbee coordinator (moving it away from USB 3.0 ports) can prevent similar signal interference.
FAQ
Why does my doorbell show offline but still rings when pressed?
The doorbell’s chime and mechanical button operate independently of network connectivity. The “offline” status in Home Assistant reflects the loss of the real-time data stream (video, motion events), not the button itself.
Does a firmware update cause the integration to break?
Yes — especially for cloud-dependent integrations. The doorbell’s manufacturer may change API calls or authentication methods without notice. Check the integration’s GitHub page for known issues.
Should I restart Home Assistant completely?
Only after you’ve tried restarting the integration individually. A full reboot can mask the root cause. If you must reboot, first check the HA logs for clues.
My doorbell is a Zigbee model (e.g., Aqara G4) — does the same guide apply?
Partially. The early checks (power, native app) still matter, but the likely cause shifts to coordinator health or signal interference. Focus on Step 4 and use a USB extension cable for the coordinator if needed.
How can I prevent future offline issues?
Use a static DHCP reservation for the doorbell’s IP, create a dedicated 2.4GHz SSID, update Home Assistant to the latest stable version, and subscribe to integration update notifications via HACS or GitHub.
This guide covers the most common scenarios. If the doorbell still shows offline after all steps, and the native app is also down, you may have a hardware failure. Verify locally whether warranty or replacement is an option.
Explore This Topic
- Back to Smart Home Troubleshooting
- Back to Device Connectivity & Offline Fixes
Related guides in this cluster:
- Smart Plug Shows Offline in Home Assistant: Step-by-Step Repair Guide
- Smart Switch Shows Offline in Home Assistant: Step-by-Step Repair Guide
- Smart Plug Shows Offline in Google Home: Step-by-Step Repair Guide
Smart home integrator and troubleshooting specialist with 8+ years of hands-on experience across Zigbee, Z-Wave, Wi-Fi, Matter, and Thread protocols. Works daily with Home Assistant, Alexa, Google Home, and Apple HomeKit ecosystems. Believes that no smart home problem should require a factory reset as the first step.