I just switched from Python Matter Server to the beta of the matter.js. Interested in other exchanging people’s experiences.
I’m running Home Assistant Greet with Matter Server 8.2.2 add-on. I’ve been using Python Matter Server about a year and it works, but just recently had some memory issue with it crashing. I have about 50 Matter devices. So I’m risking the beta ironically for more stability.
When you first start the add-on with matter.js enabled, it copied all your devices from the old configuration. This takes a long ass time. For my 50 devices, about 10 minutes. You can watch it happening in the add-on logs so you know it’s not just dead. The web UI won’t work until this process is complete. After that everything came online, quite fast actually, and so far it works
The add on is using 500MB of RAM, vs ~100MB for Z2M, that’s progress I guess. Add-on has a cool (if unstable it tends to rotate continuously) graph view for Thread and Wifi, and displays Thread signal strengths, which is a great step forward
I tried to add a new Matter of Wifi device (a powerboard) but so far it fails. The Matter set up works with the phone, however then the ‘Add to Home Assistant’ stage fails. Each time the log looks like this. Possibly and mDNS issue.
2026-02-22 21:26:42.707 INFO ConfigStorage Set config key nextNodeId to 104
2026-02-22 21:26:42.723 INFO PeerCommissioner Connecting to device with identifier {"shortDiscriminator":9} and 1 scanners and knownAddress "undefined"
2026-02-22 21:26:42.723 INFO ControllerDiscovery Start Discovering devices using identifier {"shortDiscriminator":9} ...
2026-02-22 21:26:42.724 INFO MdnsClient Registered waiter for query _S9._sub._matterc._udp.local (268) with timeout 30000
...
2026-02-22 21:27:12.724 INFO MdnsClient Finishing waiter for query _S9._sub._matterc._udp.local (268), resolving: true
2026-02-22 21:27:12.725 INFO ControllerDiscovery Found 0 devices using identifier {"shortDiscriminator":9}
2026-02-22 21:27:12.726 ERROR WebSocketC~erHandler [0] Failed to handle websocket request Commission failed: No device discovered using identifier {"shortDiscriminator":9}! Please check that the relevant device is online.
at Function.nodeCommissionFailed (/opt/matterjs/node_modules/@matter-server/ws-controller/src/types/WebSocketMessageTypes.ts:517:16)
at ControllerCommandHandler.commissionNode (/opt/matterjs/node_modules/@matter-server/ws-controller/src/controller/ControllerCommandHandler.ts:951:31)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async WebSocketControllerHandler.#handleCommissionWithCode (/opt/matterjs/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:592:28)
at async WebSocketControllerHandler.#handleWebSocketRequest (/opt/matterjs/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:384:30)
Caused by: [commissionable-device-discovery-failed] No device discovered using identifier {"shortDiscriminator":9}! Please check that the relevant device is online.
at <anonymous> (/opt/matterjs/node_modules/@matter/protocol/src/peer/ControllerDiscovery.ts:65:23)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
This error code would suggest that the device has already been added to the Matter fabrics. Are you sure it has not been paired with other hub (Google and/or Apple?)
Is it possible the phone was on 5GHz band of WiFi? Or was the phone on a different VLAN/IP-subnet?
The iPhone gives the device the WiFi credentials based on the WiFi the phone is using at the time of commissioning.
My personal experience is that I can commission devices with my Android smartphone being connected over 5 GHz. Did this with a couple of Eve devices no later than a few days ago.
It will depend on whether or not the device supports the 5GHz band.
My guess is that it is probably not the problem here, as the OP says the “Matter set up works with the phone” which probably means the device joined the WiFi network and the phone is seeing mDNS advertisements from the device…but seems HA Matter Server is not seeing these.
Correct. I overlooked that the OP was talking about Matter over WiFi.
But again: Tapo P110M here can be connected with the Matter Server - can’t tell if they do this on 5 or 2.4G. So I would rather point to the device not being compatible.
Sorry but noo this is no error code! This is just the discovery identifier … and the error means what is written there:
No device discovered ... Please check that the relevant device is online.
So it was not found via MDNS in the network.
When the device is fresh then it can only be paired via BLE, so HA app is the best or add a BLE UST stick to the host and configure the Matter server to use it
Outside of this; what issues were you having with the Python Matter Server? I have been having lots of thread instability for the last 3-4 weeks (ever since upgrading my Inovelli White Switches to the latest firmware release). I plan to migrate to matter.js as well but waiting for my C5 Lite first as I think part of my problem is the 2GB of memory in my Yellow. The firmware release exposed power utilization for each of my 33 White Switches. Which is amazing; but I think the amount of data is just overwhelming my Yellow Thread; causing it to crash.
