Matter can't connect to Thread device via IPv4?

I try to set up my HA with new Matter (matter-js Server) using WiFi and Thread.

I have a problem with pairing devices with WiFi and also with Thread. Connecting my bulb using the companion app works until it states that it tries to test connection with the Thread network. In the same moment the bulb turns blue indicating that connection is made and it tries to set up with the Thread network.

After a minute (or so) the pairing fails with a message stating on the app that it cant reach the device (which one?) and asking if my Wifi is on. But this is a Thread bulb and the mobile is conencted to the Wifi.

Looking in the log file of the matter-js server I see some error messages:

2026-07-13T19:20:17.100739124+02:00 stdout F 2026-07-13 19:20:17.100 INFO   ConfigStorage        Set config key nextNodeId to 13
2026-07-13T19:20:17.232595119+02:00 stdout F 2026-07-13 19:20:17.231 INFO   CommissioningClient  Operational address for undefined set to udp://192.168.44.113:5540
2026-07-13T19:20:17.234349727+02:00 stdout F 2026-07-13 19:20:17.233 INFO   Endpoint             server-1-fff1.peer1 ready endpoint#: 0 type: RootNode (0x16) behaviors: 💤parts ✓index ✓commissioning ✓network
2026-07-13T19:20:17.247056316+02:00 stdout F 2026-07-13 19:20:17.246 INFO   Controller~missioner Establish PASE to device
2026-07-13T19:20:32.371463996+02:00 stdout F 2026-07-13 19:20:32.370 INFO   Session              •unsecured#4666287a450467ed Session ended
2026-07-13T19:20:32.373336399+02:00 stderr F 2026-07-13 19:20:32.372 WARN   Commission~onnection Address udp://192.168.44.113:5540 unreachable for known-address-0-udp://192.168.44.113:5540
2026-07-13T19:20:32.472079124+02:00 stderr F 2026-07-13 19:20:32.377 ERROR  WebSocketC~erHandler [1] WebSocket error response (commission_on_network) a2d5d4b9932d47379f2ba71c6836aff2 Commission failed: Could not connect to device
2026-07-13T19:20:32.472079124+02:00 stderr F     at ServerError.nodeCommissionFailed (/app/node_modules/@matter-server/ws-controller/src/types/WebSocketMessageTypes.ts:104:16)
2026-07-13T19:20:32.472079124+02:00 stderr F     at ControllerCommandHandler.commissionNode (/app/node_modules/@matter-server/ws-controller/src/controller/ControllerCommandHandler.ts:1192:31)
2026-07-13T19:20:32.472079124+02:00 stderr F     at async WebSocketControllerHandler.#commissionWithRetry (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:921:47)
2026-07-13T19:20:32.472079124+02:00 stderr F     at async WebSocketControllerHandler.#handleCommissionOnNetwork (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:1031:24)
2026-07-13T19:20:32.472079124+02:00 stderr F     at async WebSocketControllerHandler.#handleWebSocketRequest (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:655:30)
2026-07-13T19:20:32.472079124+02:00 stderr F   Caused by: [peer-communication] Could not connect to device
2026-07-13T19:20:32.472079124+02:00 stderr F     at ControllerCommissioner.#establishPaseFromCandidates (/app/node_modules/@matter/protocol/src/peer/ControllerCommissioner.ts:322:23)
2026-07-13T19:20:32.472079124+02:00 stderr F     at async ControllerCommissioner.commission (/app/node_modules/@matter/protocol/src/peer/ControllerCommissioner.ts:232:29)
2026-07-13T19:20:32.472079124+02:00 stderr F     at async CommissioningClient.commission (/app/node_modules/@matter/node/src/behavior/system/commissioning/CommissioningClient.ts:275:52)
2026-07-13T19:20:32.472079124+02:00 stderr F     at async ClientNode.commission (/app/node_modules/@matter/node/src/node/ClientNode.ts:135:9)
2026-07-13T19:20:32.472079124+02:00 stderr F     at async MatterController.commission (/app/node_modules/@project-chip/matter.js/src/MatterController.ts:532:13)
2026-07-13T19:20:32.472079124+02:00 stderr F     at async CommissioningController.commissionNode (/app/node_modules/@project-chip/matter.js/src/CommissioningController.ts:467:24)
2026-07-13T19:20:32.472079124+02:00 stderr F     at async ControllerCommandHandler.commissionNode (/app/node_modules/@matter-server/ws-controller/src/controller/ControllerCommandHandler.ts:1186:22)
2026-07-13T19:20:32.472079124+02:00 stderr F     at async WebSocketControllerHandler.#commissionWithRetry (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:921:47)
2026-07-13T19:20:32.472079124+02:00 stderr F     (see parent frames)
2026-07-13T20:11:27.321729803+02:00 stdout F 2026-07-13 20:11:27.320 INFO   BorderRouterRegistry BR instance dropped (no valid xa) qname="OpenThread BorderRouter #6790._meshcop._udp.local" source=meshcop xa=missing nn="" vn=""

I wonder what the device 192.168.44.113 is. I know 5540 is Matter operational port. But none of the devices I know has a 192.168.44.113 so I assumes it is the bulb?
I thought the pairing goes through Bluetooth and Thread. And Thread is Ipv6?

So where is this Ipv4 coming from? And why might I have connection problems? The listing in my router names the entry as espressif as name.

Question: What might be wrong, where do I need to look?

Make sure IPv6 is enabled in HA. I had the same problem.

IPv6 is enabled in all three containers. They all have IPv4 and IPv6 connectivity. Ip addresses are correct, routes seems ok, HA, Matter and OTBR have advertised with mDNS.

+ bridge0 IPv6 75D80F67D024A2F2-000000000001B669             _matter._tcp         local
+ bridge0 IPv4 75D80F67D024A2F2-000000000001B669             _matter._tcp         local
+ bridge0 IPv6 ACDF068E281FCA5D-F55ED0801B693D0C             _matter._tcp         local
+ bridge0 IPv4 ACDF068E281FCA5D-F55ED0801B693D0C             _matter._tcp         local
+ bridge0 IPv6 Home                                          _home-assistant._tcp local
+ bridge0 IPv4 Home                                          _home-assistant._tcp local
+ bridge0 IPv6 OpenThread BorderRouter #6790                 _meshcop._udp        local
+ bridge0 IPv4 OpenThread BorderRouter #6790                 _meshcop._udp        local
+ bridge0 IPv6 otTREL135232d590a96790                        _trel._udp           local
+ bridge0 IPv4 otTREL135232d590a96790                        _trel._udp           local
+ bridge0 IPv6 pi-iot0 [ae:7a:0f:08:93:80]                   Workstation          local
+ bridge0 IPv4 pi-iot0 [ae:7a:0f:08:93:80]                   Workstation          local

1 Like