Problem category
Smart Home
Controllers, devices, and integrations.
ESPHome Device Is Online but Unavailable in Home Assistant
When an ESPHome device is on the network but Home Assistant cannot use it, separate endpoint identity, reachability from the HA runtime, native API port 6053, encryption, and runtime stability before reflashing.
Frigate Says “No Frames Have Been Received”
Use the exact Frigate 0.17.2 Stream Offline message and FFmpeg evidence to separate camera reachability, RTSP authentication/path, input preset, and decode failures without exposing camera credentials.
Home Assistant Matter Device Is Unavailable After Pairing
Start after successful Matter commissioning, then separate Matter Server health, Wi-Fi versus Thread transport, border-router continuity, IPv6, and multicast evidence without resetting the device or fabric.
Home Assistant Cannot Add a Matter over Thread Device
Confirm the device is a Matter-over-Thread unit that was never commissioned, then separate the Companion commissioning entry, border-router visibility, Thread credentials, and the local network stage before changing anything.
Home Assistant Blocks Requests from a Reverse Proxy Until It Is Trusted
Confirm direct access works, verify that Trust X-Forwarded-For and the proxy address are set as a network CIDR, then save and confirm the restart within the Home Assistant 2026.8 revert window.
Home Assistant Thread Border Router Not Found: Check Discovery, Credentials and the OTBR App
Confirm an expected Thread border router is missing from the Thread integration overview, then separate integration state, router type, announcements, and credential evidence without touching any Matter device or fabric.
Mosquitto Rejects the MQTT Client Connection
Prove TCP reachability to the broker first, then read the MQTT CONNACK refusal code and match the listener-specific authentication on Mosquitto 2.1.x before changing any broker configuration.
Zigbee2MQTT Cannot Open the Adapter Serial Port
Separate a missing USB device from an incorrect serial path, runtime mapping, access denial or a competing coordinator owner.
Z-Wave JS Node Is Dead but the Controller Is Online
Use the exact Z-Wave JS node status to separate Dead from Asleep/Awake, then check communication evidence, power, and mesh path without removing the node or rebuilding the network.