Here are the configs
- Thread
I own a Home Assistant Yellow and ran into similar issues with connecting my Matter-enabled plugs. I had the same integrations installed as well as multi-protocol support. It was not until I installed the integration for Zigbee Home Automation that I was able to connect my devices.
Perhaps try that and see if it changes anything for you.
1 Like
I know it’s not very helpful, but I have the same problem. The only difference is that I have two SkyConnect sticks installed on my Intel NUC. One flashed with the Zigbee firmware, the other with the Thread firmware.
Same result as yours, “Can’t connect to thread network home-assistant”.
Help is required.
I’ve successfully add an Matter / Thread device (Eve Smart Plug) with SkyConnect-Stick as Open Thread Border Router.
I follow the guide from KolBusa
https://community.home-assistant.io/t/thread-border-router-required-with-eve-and-matter/562937/21
Thank’s to KolBusa 
If necessary, I can provide a coherent guide
Please do !
I’m a Little green in triggering the websocket stuff
I have installed the following AddOns:
- Matter Server
- OpenThread Border Router - here you have to select the SkyConnect stick under Device
The following are installed under Integrations:
- Matter
- Open Thread Border Router
- Thread
Restart Home Assistant once after installation.
You need the following information for web socket communication:
- Settings → Devices and services → Thread → Configure → press the “i” symbol → Active dataset TLVs: 0e080000000000010000000300000f35060004001fffe00208e34cb63b988011600708ed1dd37a69db4a4d0510f34b8d065cf2fd3cb2bbdd3551b94ca4030e686f6d652d617383697374616e740152bf9f0410f2c39e3949ca653fab5ca0b1dd3740b20c0402a0f7f8
- Matter Device Code from the sticker on the Thread device: 3283-601-5270 the hyphens must be removed
- IP-Adress of the Home Assistant Host
Settings → System → Network → Network adapter: 192.168.178.11
To send something via the web socket, I used the Chrome AddOn Web Socket King Client is used and the Chrome Browser. Postman or similar tools also work in a very similar way.
Start the corresponding tool in my case Web Socket King Client in Chrome.
The top input line (to the left of Connect) should contain the following:
ws://192.168.178.11:5580/ws
(our determined IP address + port)
Press Connect
The message to be sent is entered in the field below:
{
"message_id": "1",
"command": "set_thread_dataset",
"args": {
"dataset": "0e080000000000010000000300000f35060004001fffe00208e34cb63b988011600708ed1dd37a69db4a4d0510f34b8d065cf2fd3cb2bbdd3551b94ca4030e686f6d652d617383697374616e740152bf9f0410f2c39e3949ca653fab5ca0b1dd3740b20c0402a0f7f8"
}
}
The determined Active dataset TLVs are entered here (the long character string).
Press Send
Replace the code from just now with the second message in which the Matter Device Code must be sent:
{
"message_id": "2",
"command": "commission_with_code",
"args": {
"code": "32836015270"
}
}
Press Send
The OUTPUT window should then display a message with (or similar):
{
“message_id”: “2”,
“error_code”: 0,
}
The new Matter / Thread device should appear immediately in the Home Assistant.
Settings → Devices & services → Matter → 1 Device →
2 Likes
Hi @Sascha-HA
Thanks for your guide.
I have all add ons installed and running fine. Nothing special the logs.
Silicon Labs Multiprotocol - Current version: 2.4.3
OpenThread Border Router -Current version: 2.4.3
Matter Server - Matter Server - Current version: 5.0.2
Integrations are present
-
Settings → Devices and services → Thread → Configure → press the “i” symbol → Active dataset
Active dataset TLVs: 0e080000000000050000000300000f35060004001fffe00208dc2c9f749874de3b0708fdd4bd8d8660317f0510ff11c2bacb64363da2eaf97ee32e42a6030e686f6d652d617373697374616e74010274740410fcbffeed26e1f6935a61ad1fa88a15f50c0402a0f7f8 -
Matter Device Code from the sticker on the Thread device: 2574-654-3095 the hyphens must be removed
-
IP-Adress of the Home Assistant Host
Settings → System → Network → Network adapter: 192.168.86.41
Sending These 2 messages via WebSocket King
Matter Server log is complaining about the JSON being invalid 
Which is strange to me as, for the set_thread_dataset payload I did get output back through the websocket.
Am I doing something wrong, typo somewhere ?
PS: Matter device is the Aqara P2 door and window sensor
The message after the command “Disconnected from …” could be caused by a syntax error. The formatting was unfortunately destroyed by the forum. This is the correct formatting, sorry:
{
"message_id": "1",
"command": "set_thread_dataset",
"args": {
"dataset": "0e080000000000010000000300000f35060004001fffe00208e34cb63b988011600708ed1dd37a69db4a4d0510f34b8d065cf2fd3cb2bbdd3551b94ca4030e686f6d652d617383697374616e740152bf9f0410f2c39e3949ca653fab5ca0b1dd3740b20c0402a0f7f8"
}
}
{
"message_id": "2",
"command": "commission_with_code",
"args": {
"code": "32836015270"
}
}
(I have also corrected my post above)
Thanks again.
The JSON worked this time around.
The matter log now indicates it’s missing a bluetooth controller to finish the setup
2024-01-12 23:29:52 core-matter-server matter_server.server.device_controller[210] INFO Starting Matter commissioning with code using Node ID 5.
2024-01-12 23:29:52 core-matter-server chip.CTL[210] ERROR Commissioning discovery over BLE failed: src/platform/Linux/BLEManagerImpl.cpp:687: CHIP Error 0x00000003: Incorrect state
2024-01-12 23:29:52 core-matter-server chip.-[210] ERROR src/platform/Linux/BLEManagerImpl.cpp:687: CHIP Error 0x00000003: Incorrect state at src/controller/SetUpCodePairer.cpp:324
2024-01-12 23:29:52 core-matter-server chip.BLE[210] ERROR No adapter available for new connection establishment
2024-01-12 23:30:22 core-matter-server chip.CTL[210] ERROR Discovery timed out
2024-01-12 23:30:22 core-matter-server chip.ZCL[210] ERROR Secure Pairing Failed
2024-01-12 23:30:22 core-matter-server matter_server.server.client_handler[210] ERROR [140737230312656] Error handling message: CommandMessage(message_id=‘2’, command=‘commission_with_code’, args={‘code’: ‘25746543095’})
Traceback (most recent call last):
File “/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py”, line 188, in _run_handler
result = await result
^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py”, line 196, in commission_with_code
raise NodeCommissionFailed(
matter_server.common.errors.NodeCommissionFailed: Commission with code failed for node 5
2024-01-12 23:30:23 core-matter-server chip.DIS[210] ERROR Timeout waiting for mDNS resolution.
Guess i’m stuck now, as I don’t have a BLE on my HA
BLE is mandentory.
What kind of system do you have (Raspberry / NUC / etc.)?
Can you use a Bluetooth Dongel, maybe?
1 Like
Running HAOS as a VM on Synology NAS
Yeah. Asking around at friends for a BLE Dongle.
Seems a waste of money for a one time thing
@Sascha-HA So i spend a couple of bucks on a Ugreen BLE… Arrived today.
- installed easly + mounted to the VM
- added bluetooth integration through devices
Bluetooth radio available
Great
Running the JSONs again.
Matter add-on disagrees:
2024-01-18 20:04:42 core-matter-server matter_server.server.device_controller[210] INFO Starting Matter commissioning with code using Node ID 8.
2024-01-18 20:04:42 core-matter-server chip.CTL[210] ERROR Commissioning discovery over BLE failed: src/platform/Linux/BLEManagerImpl.cpp:687: CHIP Error 0x00000003: Incorrect state
2024-01-18 20:04:42 core-matter-server chip.-[210] ERROR src/platform/Linux/BLEManagerImpl.cpp:687: CHIP Error 0x00000003: Incorrect state at src/controller/SetUpCodePairer.cpp:324
2024-01-18 20:04:42 core-matter-server chip.BLE[210] ERROR No adapter available for new connection establishment
Do I need to do anything in HA to connect the bluetooth integration with Matter add on?
Thank you very much. That worked 
Annoying that I couldn’t connect the device with the Home Assistant Companion App because Google only saved my old network
Thanks for the good guide @Sascha-HA . So far I had the same problems with connecting Onvis smart plugs and other devices via Matter over Thread.
Now I followed all steps, everything straight forward.
But when starting the commision via websocket I get this error in the Matter addon:
2024-01-22 21:34:35 core-matter-server matter_server.server.device_controller[224] INFO Starting Matter commissioning with code using Node ID 10 (attempt 0/3).
[New Thread 0xffffe37e81e0 (LWP 231)]
[New Thread 0xffffe2fe71e0 (LWP 232)]
[New Thread 0xffffe27e61e0 (LWP 233)]
2024-01-22 21:34:35 core-matter-server chip.DL[224] ERROR Long dispatch time: 281 ms, for event type 2
2024-01-22 21:34:45 core-matter-server chip.CTL[224] ERROR Commissioning discovery over BLE failed: src/platform/Linux/bluez/ChipDeviceScanner.cpp:173: CHIP Error 0x00000032: Timeout
2024-01-22 21:34:45 core-matter-server chip.-[224] ERROR src/platform/Linux/bluez/ChipDeviceScanner.cpp:173: CHIP Error 0x00000032: Timeout at src/controller/SetUpCodePairer.cpp:324
2024-01-22 21:34:45 core-matter-server chip.BLE[224] ERROR BLE scan error: src/platform/Linux/bluez/ChipDeviceScanner.cpp:173: CHIP Error 0x00000032: Timeout
2024-01-22 21:35:06 core-matter-server chip.DIS[224] ERROR Timeout waiting for mDNS resolution.
2024-01-22 21:35:17 core-matter-server chip.CTL[224] ERROR Failed to perform commissioning step 25
2024-01-22 21:35:22 core-matter-server matter_server.server.device_controller[224] INFO Starting Matter commissioning with code using Node ID 10 (attempt 1/3).
2024-01-22 21:35:24 core-matter-server chip.DL[224] ERROR Long dispatch time: 2760 ms, for event type 2
The plug is right nex to the BT dongle. My setup:
- HA Green
- HA Os 2024.1.5
- SkyConnect (Multiprotocol active)
- BT: SABRENT BT-UB40
- FritzBox 7590
Does anyone have an idea what this is pointing to?
For anyone encountering this mDNS resolution problem: it was a misconfiguration on my main FritzBox router. Even after resetting it to default settings, the error occurred.
After some research I found that i have to activate the 6to4 tunnel protocol option for IPv6 of the router. After that everything went flawless, even no need for websocket messages.
So I found out what the issue was for me.
There is one section in on of the live streams of Home Assistant, where they explain why some people might get the message: Can’t connect to thread network home-assistant
See here: https://youtu.be/rEugjMk-4II?t=5611 (watch from here for about 5 min)
The issue seems the Tread credentials from Home Assistant are not being stored in the Android phone.
I used a second Android phone (Samsung Galaxy S8) and with that I was able to store the correct credentials and connect my Matter over Thread devices.
With my main mobile phone (Samsung Galaxy S20) was not able to add the devices. I even reset the Google Play Services storage, as is being explained in the video a bit later. But I did not get it to work.
Update: On my ‘new’ Samsung phone there seem to be different ways to clear the storage for Google Play Services. If I went through the settings menu to the app the way to clear the storage was different than to when I go to the app info directly and then clear the storage. The way through the mobile phone settings worked for me in the end.
In my case I think I gave myself a problem by commissioning a device to Google Nest Hub first, before trying one with HA. The phone really really doesn’t want to be disloyal to its first thread network 
I have the same situation.
The existing tools work, but I can’t add new ones.
I use SSL, so ws access does not work as you described.
(SSL was needed for voice control if I remember correctly).
Do you have a solution in this case as well?