Paste a safe portion of a Home Assistant or smart-home error message. The decoder matches words in your browser and points to the closest Troubliq diagnostic. It does not upload or store the text.
51 matches available. Enter part of an error or choose a system.
Matching errors and symptoms
| Error or symptom | System | Likely diagnostic layer | Solution |
|---|---|---|---|
NCP entered failed state |
ZHA | Coordinator serial, firmware or connection failure | Open guide |
Device interview failed |
Zigbee2MQTT | The device joined but descriptor or cluster discovery did not complete | Open guide |
Failed to interview device |
Zigbee2MQTT | Keep the device awake and separate support problems from radio problems | Open guide |
Device is unavailable |
Matter | Check fabric membership, controller reachability and the Matter server | Open guide |
Thread credentials synced but commissioning fails |
Matter / Thread | Verify the preferred dataset, border router, phone and local IPv6 path | Open guide |
Node is dead |
Z-Wave JS | Distinguish a sleeping node from a powered or route failure | Open guide |
Node unavailable |
Z-Wave JS | Check power, wake interval, routes and failed-node status | Open guide |
Entity unavailable after restart |
MQTT | Check broker connection, discovery replay, retained availability and birth messages | Open guide |
Cannot connect to ESPHome API |
ESPHome | The device may be on Wi-Fi while its native API is unreachable | Open guide |
ESPHome device offline but on Wi-Fi |
ESPHome | Verify the API address, encryption key, DNS and logs | Open guide |
Accessory is already paired |
HomeKit Device | The accessory retains pairing ownership and needs ownership-safe recovery | Open guide |
Backup requires encryption key |
Home Assistant backup | Locate the emergency kit or correct recovery key before restoring | Open guide |
Automation did not trigger |
Home Assistant automation | Use traces to separate trigger, condition and action failures | Open guide |
Automation is already running |
Home Assistant automation | Inspect automation mode, waits and overlapping runs | Open guide |
Automation runs twice |
Home Assistant automation | Compare traces, trigger IDs and duplicate definitions | Open guide |
Sensor not available in Energy dashboard |
Home Assistant Energy | Check unit, device class, state class and long-term statistics | Open guide |
Duplicate devices |
Home Assistant | Find the source integration before deleting registry entries | Open guide |
Service Unavailable |
Alexa Devices | Separate an upstream service failure from authentication or local connectivity | Open guide |
Reauthentication required |
Tuya | Check the correct account, region, cloud access and shared devices | Open guide |
Subscription not found |
Google Nest | Inspect Device Access and Pub/Sub configuration before recreating the integration | Open guide |
invalid_grant |
Google Nest | Reauthorize the existing integration and verify the OAuth project | Open guide |
Bluetooth proxy unavailable |
Bluetooth / ESPHome | Check proxy connectivity, coverage, advertisements and encryption | Open guide |
WebSocket connection failed |
Node-RED | Validate the Home Assistant URL, token, add-on settings, DNS and TLS | Open guide |
Hue room or zone missing |
Philips Hue | Check bridge group behavior, disabled groups and integration options | Open guide |
WLED unavailable after IP change |
WLED | Verify DHCP, the current address and any MAC-address mismatch | Open guide |
Shelly unavailable |
Shelly | Check power, current IP, local protocol access, firmware and VLAN rules | Open guide |
Kasa or Tapo unavailable |
TP-Link | Check local discovery, credentials, addressing and supported integration behavior | Open guide |
Samsung TV unavailable |
Samsung TV | Verify IP, permissions, subnet, MAC address and Wake on LAN | Open guide |
Reolink camera unavailable |
Reolink | Check power, IP, credentials, ports, streams and integration logs | Open guide |
SwitchBot not discovered |
SwitchBot | Check Bluetooth mode, coverage, encryption and competing connections | Open guide |
Ecobee integration unavailable |
Ecobee | Check cloud status, authentication, account access and entity refresh | Open guide |
Could not load Home Assistant |
Home Assistant frontend | Separate browser, proxy and network-path failures from a Core startup failure | Open guide |
Unable to connect to Home Assistant |
Home Assistant frontend | Test the local IP, another client and Core status before changing configuration | Open guide |
Loading data |
Home Assistant frontend | Check cached frontend resources, custom dashboards, proxy WebSockets and Core health | Open guide |
Zigbee devices unavailable after update |
ZHA | Confirm integration startup, coordinator visibility and the stable serial path | Open guide |
Z-Wave devices unavailable after update |
Z-Wave JS | Check the Z-Wave JS server, controller path and first startup error | Open guide |
Coordinator failed to initialize |
ZHA | Inspect serial path, permissions, port conflicts, firmware and USB visibility | Open guide |
Home Assistant Core unresponsive |
Home Assistant Core | Preserve a timeline and distinguish memory pressure from a blocked event loop | Open guide |
Watchdog restarted Home Assistant Core |
Home Assistant Core | Correlate the restart with Recorder, integrations, add-ons, memory and storage evidence | Open guide |
Connection lost. Reconnecting… |
Home Assistant Core | Determine whether Core stopped responding or only the frontend network path failed | Open guide |
Installed version for zha resolved to None |
ZHA | Package metadata or installation-state failure; preserve logs before reinstalling or restoring | Open guide |
Unable to install package zha |
ZHA | Check the first package, metadata, storage and DNS error rather than resetting the mesh | Open guide |
Failed to parse METADATA file |
Home Assistant Core | Python package metadata or filesystem state failed; protect the backup and diagnose the installation | Open guide |
Setup failed for 'zha': Requirements for zha not found |
ZHA | ZHA dependencies did not load; diagnose package installation before touching paired devices | Open guide |
This entity is no longer being provided / Error connecting to bridge / [Errno 113] Host is unreachable |
Osram Lightify | Open 2026.9.3 report; verify bridge reachability and preserve the first traceback before deleting anything | Open current issue record |
This entity is no longer being provided by the netatmo integration |
Netatmo | Open 2026.9.3 battery-entity report; confirm other Netatmo entities still work | Open current issue record |
Automatic backup list shows only the newest backup |
Home Assistant backup | Confirm older backup files still exist at the destination before deleting or recreating anything | Open current issue record |
cannot import name RECOMMENDED_USE_GOOGLE_SEARCH_TOOL |
Google Generative AI | Open integration import report; preserve versions and avoid manual package edits | Open current issue record |
LibraryShutdown / invalid PDUStatus / AccessoryDisconnectedError |
Onvis SMS2 / HomeKit over Thread | Pairing report; preserve ownership and Thread credentials before reset | Open current issue record |
Restore backup: Unknown error |
Home Assistant backup | Keep the original backup unchanged and verify installation version and recovery key | Open current issue record |
Setup failed for 'zwave_js': Requirements for zwave_js not found |
Z-Wave JS | Z-Wave JS dependencies did not load; preserve keys and avoid excluding nodes | Open guide |
sqlite3.DatabaseError: database disk image is malformed |
Home Assistant Recorder | Preserve a full backup, confirm free storage, then diagnose SQLite and the underlying storage or power layer before deleting anything | Open guide |
How to interpret a match
- Confirm the complete message and the line immediately before it.
- Identify whether one device, one integration, one protocol or the whole system is affected.
- Open the linked guide and perform the least-destructive checks first.
- Change one setting at a time and record the result.
- Verify the repair through normal update or wake cycles—not only a green dashboard icon.
Before sharing a log, remove sensitive values with the Home Assistant Log Sanitizer and manually review the result.
No direct match?
Search using the stable nouns and verbs in the error. Remove timestamps, entity IDs, IP addresses, device names and counters. Then use the Device Unavailable Diagnostic or the Smart-Home Diagnostic Decision Tree.
Method and limitations
This decoder is a curated routing tool, not a replacement for the complete log or official documentation. Similar wording can describe different failures. Every result must be confirmed against the affected component, versions and surrounding log context. Troubliq does not claim hands-on testing of every device.
Last reviewed: September 24, 2026. Read the research and review method or report a correction.