did the same and it nearly worked … but instead of your successfull integration I ended up with an error in the nuki app … will try again and post some more details once i am back home
thanx
1 Like
Did you ever get this working? Could you post steps?
I wanted to share my success story in getting some TP-Link Tapo plugs discovered through Matter. No matter what I tried, I couldn’t get the plugs adopted in Home Assistant nor Google Home. I then found the solution on YouTube!
YouTube creator Eric Welander gave me the solution in his “BEFORE getting Matter devices” video that IPV6 needs to be enabled on your network to allow Matter devices to get a required IPV6 address!!! I had disabled IPV6 on my OPNsense firewall across all networks and the WAN. Nobody mentions enabling IPV6 for Matter and I never saw it mentioned in the HA docs! Once enabled and configured, the plugs were instantly found and adopted!
I just wanted to share the solution in case anybody else is having adoption issues.
3 Likes
Thanks a lot! I have been trying for days to connect Aquara U200 to HA via matter (connected to Amazon ECHO). My IPV6 was disabled, enabling it did the trick!
1 Like
I have registered Aqara U200 on a network without IPv6 enabled… it could be a coincidence but maybe it is due to problems with multicast traffic (mDNS) on your network?
May I ask, what do you mean by this?
Do you mean to say that your home’s internet router’s LAN interface is not enabled for IPv6?
Yes, router/firewall and switchs with ipv6 and MLD disabled, no DHCPv6 (statefull)
Despite having these functions disabled, HA, Matter server and Thread devices will automatically use ipv6 (stateless). should “autoconfigure”
all within the same VLAN.
Although I am really testing with virtualized HAOS inside a QNAP NAS and it does not seem that communication is established through stateless IPv6… I have to do some more testing and verify that the Zyxel ATP firewall does not block multicast traffic (mDNS)
1 Like
OK, that’s what I thought you meant …
Its the Thread Border Router (TBR) that is sending out IPv6 SLAAC advertised prefixes over the LAN that HA (and others) uses to autoconfigure its IPv6 addresses and this is what makes Matter over Thread work. Note that if there is no TBR, then Matter over WiFi doesn’t work so well unless something like the home router has IPv6 enabled on its LAN side and sending out SLAAC advertised prefixes.
1 Like
I’m using TBR on HAOS with Sonoff ZBDongle-E with QNAP VM passtrough…
But the IPv6 communication between wifi/mobile and HA seems not to work to link a new device… I can ping with IPv6, on the network but not against HA… even with fixed IPv6 or setting a DHCPv6 server (statefull) with a prefix, HA seems not to acquire it… the curious thing is that the same virtual switch gives access with IPv4 without problem …
1 Like
I’m posting in this thread instead of starting a new one.
I have successfully added my Aqara U200 in Google Home.
In Home Assistant I have as prefered network the one my nest devices created and I have synced crendentials multiple times and with multiple devices.
IP6 works fine in my network, it is activated in my NAS and I can see that Home Assistant get an IP6 IP.
I tried adding the Aqara U200 in home Assistant via Google Home app with Android and iOS devices with no luck.
I have started from scratch (resetting U200) with exactly the same results.
The only thing that I haven’t tried is to use Conbee II as thread router and add it to the same network with OTBR.
Any help appreciated.
What NAS do you use? IPv6 stateless?
Ugeeen NAS running True NAS scale. Not sure about the stateless thing 
[Home Assistant Matter Server to commission a device directly]
Today I tried a Bluetooth adapter, but I think it is not compatible…
UGREEN Bluetooth Adapter 5.4 [CM748]
2024-10-28 08:24:07.387 (MainThread) ERROR [matter_server.server] Error doing task: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 214, in _run_handler
raise err
File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 197, in _run_handler
result = await result
^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py", line 456, in set_thread_operational_dataset
await self._chip_device_controller.set_thread_operational_dataset(dataset)
File "/usr/local/lib/python3.11/site-packages/matter_server/server/sdk.py", line 183, in set_thread_operational_dataset
threadOperationalDataset=bytes.fromhex(dataset),
^^^^^^^^^^^^^^^^^^^^^^
ValueError: non-hexadecimal number found in fromhex() arg at position 2
2024-10-28 08:26:35.865 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 1.
2024-10-28 08:26:35.985 (Dummy-2) CHIP_ERROR [chip.native.DL] Disabling CHIPoBLE service due to error: src/platform/Linux/BLEManagerImpl.cpp:596: Ble Error 0x00000401: BLE adapter unavailable
2024-10-28 08:26:35.985 (Dummy-2) CHIP_ERROR [chip.native.CTL] Commissioning discovery over BLE failed: src/platform/Linux/BLEManagerImpl.cpp:743: Ble Error 0x00000401: BLE adapter unavailable
2024-10-28 08:26:35.987 (Dummy-2) CHIP_ERROR [chip.native.-] src/platform/Linux/BLEManagerImpl.cpp:743: Ble Error 0x00000401: BLE adapter unavailable at src/controller/SetUpCodePairer.cpp:324
2024-10-28 08:26:35.987 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 108 ms, for event type 3
2024-10-28 08:27:05.884 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2024-10-28 08:27:05.884 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed
2024-10-28 08:27:05.885 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to establish secure session to device: src/controller/python/ChipDeviceController-ScriptDevicePairingDelegate.cpp:89: CHIP Error 0x00000003: Incorrect state
2024-10-28 08:27:05.885 (MainThread) ERROR [matter_server.server.client_handler] [140417963409104] Error while handling: commission_with_code: Commission with code failed for node 1.
2024-10-28 08:28:22.775 (MainThread) ERROR [matter_server.server] Error doing task: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 214, in _run_handler
raise err
File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 197, in _run_handler
result = await result
^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py", line 456, in set_thread_operational_dataset
await self._chip_device_controller.set_thread_operational_dataset(dataset)
File "/usr/local/lib/python3.11/site-packages/matter_server/server/sdk.py", line 183, in set_thread_operational_dataset
threadOperationalDataset=bytes.fromhex(dataset),
^^^^^^^^^^^^^^^^^^^^^^
ValueError: non-hexadecimal number found in fromhex() arg at position 2
2024-10-28 08:29:00.643 (MainThread) ERROR [matter_server.server] Error doing task: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 214, in _run_handler
raise err
File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 197, in _run_handler
result = await result
^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py", line 456, in set_thread_operational_dataset
await self._chip_device_controller.set_thread_operational_dataset(dataset)
File "/usr/local/lib/python3.11/site-packages/matter_server/server/sdk.py", line 183, in set_thread_operational_dataset
threadOperationalDataset=bytes.fromhex(dataset),
^^^^^^^^^^^^^^^^^^^^^^
ValueError: non-hexadecimal number found in fromhex() arg at position 0
2024-10-28 08:29:25.915 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 2.
2024-10-28 08:29:25.921 (Dummy-2) CHIP_ERROR [chip.native.CTL] Commissioning discovery over BLE failed: src/platform/Linux/BLEManagerImpl.cpp:743: Ble Error 0x00000401: BLE adapter unavailable
2024-10-28 08:29:25.921 (Dummy-2) CHIP_ERROR [chip.native.-] src/platform/Linux/BLEManagerImpl.cpp:743: Ble Error 0x00000401: BLE adapter unavailable at src/controller/SetUpCodePairer.cpp:324
2024-10-28 08:29:55.928 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2024-10-28 08:29:55.929 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed
2024-10-28 08:29:55.929 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to establish secure session to device: src/controller/python/ChipDeviceController-ScriptDevicePairingDelegate.cpp:89: CHIP Error 0x00000003: Incorrect state
2024-10-28 08:29:55.930 (MainThread) ERROR [matter_server.server.client_handler] [140417963409040] Error while handling: commission_with_code: Commission with code failed for node 2.
On the other hand, when starting the process it asks for the “Dataset ID” of the Thread network, when is it really referring to the Extended Pan ID?
Using “Dataset id” show error:
Error setting Thread dataset: non-hexadecimal number found in fromhex() arg at position 2
NOTE: The first time you set the property to 1, it is reset to 0
Settings ->Add-ons → Matter Server → Configuration I then set the Bluetooth Adapter ID to 1
The Dataset id that Matter server is looking for is the Thread Integrations “Active dataset TLVs” string.
Ha Ha …
yeah before they came out with that webpage, I had to use Python code to call a Matter Server API to do the same thing.
Also be aware, I don’t think the settings persist, meaning if you restart the Matter Server AddOn, and want to pair a new device afterwards, you’ll probably have to redo the settings again in the GUI
1 Like
@dimmanramone did you resolve this? I have same/similar. I cannot get my Matter device (also U200) added to HA. Fine adding to Google Home, but would not add to HA directly, and also does not accept the ‘share’ from Google Home method of adding.
@manta99 Yes I got it working. i deployed a matter server docker container in a raspberry pi instead, that has bluetooth. Then I used that matter server in home assistant and it took 3 seconds to pair. I think just for the pairing you need to have bluetooth. I hade the matter server first installed in my NAS that doesn’t have BT and that is probably why i couldn’t pair it with home assistant.
Check this post too