#HA Companion App "Can't reach device" while adding Matter device.
1 messages · Page 1 of 1 (latest)
Topology:
Network
WIFI
Android
Home Assistant App
Server
MACVLAN
HA Container
Openthread Border Router Container
Matter container
MDNS works between:
- android TO containers
- containers TO containers
- containers TO android
So communication should be enabled.
hmm. I might''ve reset the border router- resetting credentials...
nope.
matter-1 | 2025-10-20 19:31:33.912 (Dummy-2) CHIP_ERROR [chip.native.DIS] Packet too small for mDNS data: 10 bytes
matter-1 | 2025-10-20 19:47:07.717 (Dummy-2) CHIP_ERROR [chip.native.DIS] Packet too small for mDNS data: 10 bytes
matter-1 | 2025-10-20 19:47:19.984 (Dummy-2) CHIP_ERROR [chip.native.DIS] Packet too small for mDNS data: 10 bytes
I've run out of ideas.
The HA companion app just seems to get stuck and I don't know why.
Tried placing it directly next to the threat radio to make sure the device has signal... Same thing occurs.
I can't interpret the openthread-border-router logs
openthread-border-router-1 | Oct 20 23:16:11 567192cd1f6f otbr-web[71]: [CRIT]-WEB-----: Stopping web server
oop., although something is still listening on port 8081
let's see if I can get useful information out of ADB logs
It looks like the Thread integration in HA keeps losing sight of the Border Router.
It shows up when I restart openthread-border-router, but disappears a bit later.
I don't see any obvious failures. Fails silently.
I see some radio messages pass by and the openthread-border-router web interface shows a child node, hwich I think is this device...
but home assistant seems to be disconnected from border router then