Matter hub added but not usable

[Damfer03]

Hello,

The matter hub has been added successfully but the entities exposed are not usable. They all show as offline. Would someone know why please ?

[RiDDiX]

Did you use IPv6 / enabled it within your router?

Could you also share your debug logs?

[Damfer03]

Hey, so I managed to finally set the IPv6 ULA, but still nothing, the same error showing up "offline".

I didn't have this issue with the previous matter hub

[RiDDiX]

Do you use docker version or add-on / app version?

[Damfer03]

Add-on

[RiDDiX]

Within HA - Settings - Apps - Home-Assistant-Matter-Hub - Configuration - Log type debug (Set up for debug logging)
Then HA - Settings - Apps - Home-Assistant-Matter-Hub - Log (Here are the actual logs / debug logs)

Try to commission a bridge to a controller and send me here the full debug logs. Then I'll check on them.

[Damfer03]

Sorry, here it is, thank you !

3fd9e6b0_hamh_2026-06-19T21-55-42.916Z.log

[RiDDiX]

Each Matter bridge needs its own port. Both of yours are on 5540, so only the first one can bind it and the second fails with the address-in-use error, which is why all its entities show offline.

Give the second bridge a unique port (e.g. 5541) in its settings and restart it. Next alpha also handles this automatically: on startup a clashing bridge gets moved to a free port instead of failing.

[Damfer03]

Thank you, I will try this and let you know !

[Damfer03]

Hey, just did it again with the port 5541, but the devices are still offline... Here are the logs if you could please help

Thank you

3fd9e6b0_hamh_2026-06-25T16-39-55.913Z.log

[RiDDiX]

Good news, the port fix worked. The log shows the bridge pairing all the way through, Google opens a session over your fd18: address and finishes fine.

The thing with Google is your phone only does the pairing, then a Nest hub takes over and keeps it alive. Nothing comes back after the pairing here, so that hub is not reaching the bridge, that is the offline.

So check the Nest hub is on the same network as Home Assistant and can reach that fd18: address (not a separate VLAN or IoT/guest WiFi).

If you can, leave debug logging on for 10-15 min after pairing and send that, this log stops right after the pairing so it does not show the offline part.