Dirigera hub and Home-Assistant with matter

Dirigera hub and Home-Assistant

Hi
I’m trying to connect a dirigera Hub to Home Assistant, but I’m not sure how to do that.

My setup looks like this:

  • Home-assitant is running containerized (rootful podman under fedora)
  • For matter I’m using the beta matter server from matterjs-server/docker/matterjs-server at main · matter-js/matterjs-server · GitHub
    CONTAINER_IMAGE: Package matterjs-server · GitHub. This image does not require supervisor
  • both containers run inside the host network and ipv6 is enabled
  • Dirigera Hub is using Firmare version 2.934.0 (latest at the time of writing)
  • I’ve made the dirigera thread network the default network in the thread integration of Home assistant.
  • sucessfully added matter-server to home-assistant

What I tried to do next is add the dirigera hub as matter device to home-assistant. using the following steps:
see also

  • in the companion App go to Setting → Inegrations → Matter → Add device
  • Select no it’s new
  • Do not use qr-code
  • Go into IKEA Home Connect
  • Dirgera Hub → Integrations → Connect with a code → Copy Code
  • In Home-assistant App enter the code

This fails and I see the following error in the matter-server logs

2026-03-22 08:11:18.048 INFO   ConfigStorage        Set config key nextNodeId to 19
2026-03-22 08:11:18.393 INFO   CommissioningClient  Operational address for undefined set to udp://[fe80::e2d8:e8a9:8868:707f%24]:5540
2026-03-22 08:11:18.393 INFO   Endpoint             server-1-fff1.peer3 ready endpoint#: (unassigned) type: RootNode (0x16) behaviors: 💤parts ✓index ✓commissioning ✓network
2026-03-22 08:11:18.415 INFO   Controller~missioner Establish PASE to device
2026-03-22 08:11:44.182 INFO   Session              •unsecured#65c11c64aef32d43 Session ended
2026-03-22 08:11:44.182 WARN   Commission~onnection Address udp://[fe80::e2d8:e8a9:8868:707f%24]:5540 unreachable for known-address-0-udp://[fe80::e2d8:e8a9:8868:707f%24]:5540
2026-03-22 08:11:44.184 ERROR  WebSocketC~erHandler [0] Failed to handle websocket request Commission failed: Could not connect to device
    at Function.nodeCommissionFailed (/app/node_modules/@matter-server/ws-controller/src/types/WebSocketMessageTypes.ts:517:16)
    at ControllerCommandHandler.commissionNode (/app/node_modules/@matter-server/ws-controller/src/controller/ControllerCommandHandler.ts:996:31)
    at async WebSocketControllerHandler.#handleCommissionOnNetwork (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:662:28)
    at async WebSocketControllerHandler.#handleWebSocketRequest (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:403:30)
  Caused by: [peer-communication] Could not connect to device
    at ControllerCommissioner.#establishPaseFromCandidates (/app/node_modules/@matter/protocol/src/peer/ControllerCommissioner.ts:289:23)
    at async ControllerCommissioner.commission (/app/node_modules/@matter/protocol/src/peer/ControllerCommissioner.ts:215:29)
    at async CommissioningClient.commission (/app/node_modules/@matter/node/src/behavior/system/commissioning/CommissioningClient.ts:229:13)
    at async ClientNode.commission (/app/node_modules/@matter/node/src/node/ClientNode.ts:132:9)
    at async MatterController.commission (/app/node_modules/@project-chip/matter.js/src/MatterController.ts:516:13)
    at async CommissioningController.commissionNode (/app/node_modules/@project-chip/matter.js/src/CommissioningController.ts:453:24)
    at async ControllerCommandHandler.commissionNode (/app/node_modules/@matter-server/ws-controller/src/controller/ControllerCommandHandler.ts:990:22)
    at async WebSocketControllerHandler.#handleCommissionOnNetwork (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:662:28)
    (see parent frames)

Things I thought

  • since the dirigera hub acts as a matter controller I may need to add it as a hub not a device
  • Home-assistant should have its own thread border router (didn’t set this up since I wanted to avoid another container with Thread USB dongle )

There is obviously some connection problem, but what am I doing wrong ?

DIRIGERA only acts a Matter controller for the IKEA Home Smart app, not for Home Assistant (HA has the Matter server for that). For HA it only acts as Matter bridge so Zigbee devices added to DIRIGERA are visible in HA. If you don’t have Zigbee devices connected to DIRIGERA and just want to use it as Thread border router you don’t even need to add it to HA.

That’s not needed either.

Thanks for your quick answer

I stopped trying to add the dirigera hub to home-assistant. Instead I tried to add 2 devices which I already had connected to the dirigera hub as matter devices to Home-assistant

For pairing the devices I needed to generate a Pairing Code in the IKEA Home Connect app for the 2 devices.
With that the two devices (Myggspray and Mygbett) were successfully added to HA.
As you said, there is no need to add the dirigera hub to home-assistant.
Just configure the thread network created by the dirigera hub as default network in HA. I think this feature (adding matter devices) to multiple Matter Controlers is called multi-admin. So far this seems to work well.

I also tried to add Matter devices directly to HA without adding them to IKEA Home Connect. That also works.

For zigbee devices I currently use zigbee2mqtt. You mentioned that I could use the dirigera Hub for that. Do you know how would I have to do this ?

Since you are using Z2M already there’s no point in doing that, you will lose features when bridging IKEA Zigbee devices to Matter using DIRIGERA as Matter bridge.

Now that I know how things are supposed to work I’m now hit by

Just FYI if you also see your ikea devices not emitting events after some idle time (e.g. 30 mins). So far there is only a workaround to ping affected devices regulairily e.g. using GitHub - joshuakimrub/matter-node-pinger: Simple workaround script for updating the states of the new battery powered Ikea matter devices · GitHub