Hello everyone,
I’ve been desperate for days with my Aqara U200 Lock.
It’s my first thread /matter device. And I can’t connect it to HomeAssistant.
I use an SLZ6M as a thread antenna slzb-06m.
This is connected via USB.
I selected the network under Thread as the preferred network. But don’t get a connection.I also have an Echo from Amazon with this one can connect the lock. Unfortunately, it doesn’t help me in HomeAssistant.
Please help me
If you have your U200 connected to an Echo, it means the U200 is using the Echo’s Thread network so no need to try to connect to Home Assistant’s OTBR/SLZ6M which will be yet another separate Thread network.
I think the next step for you would be to try to get Alexa to “Share” the U200 with HA’s Matter.
I don’t know the particular steps on how to do this, but take a look at these instructions to see if it works for you.
If not, I have seen from others that they use the Alexa app to turn on “sharing” somehow. They’ve mentioned something like using the “Other Assistants and Apps option within the settings of the lock device”. If you are able to turn on Sharing in Alexa App, it should provide you with a code, then go to HA “Add Device” using Matter, and along the way, enter in this code.
Thanks for the tip. I had that as an idea and tried it. Unfortunately, it also fails. But I see some errors in the Matter Log.
2024-12-09 22:42:18.168 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 11.
2024-12-09 22:42:48.176 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2024-12-09 22:42:53.279 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:97204261 on exchange 4465i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-12-09 22:42:58.271 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
2024-12-09 22:42:58.271 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed
2024-12-09 22:42:58.272 (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-12-09 22:42:58.274 (MainThread) ERROR [matter_server.server.client_handler] [140277206476864] Error while handling: commission_with_code: Commission with code failed for node 11.
It means the Matter Server was waiting to get mDNS-SD messages from the U200 but never received any. If the U200 is still connected to Alexa a a TBR, is Alexa on the same LAN as HA server? Is IPv6 enabled on your HA?
That might be a problem. I realized 2 VLANs via UniFi. HomeAssistant has 2 network cards and is directly on the same network. IPv6 is enabled.
Edit: Alexa is in the wrong WiFi, i will Change it and test again.
It works!!!
The echoes were in the wrong network.
I have one more question, does my SLZM06 even have a function now?
Or is it all over the Echo? And could I have saved myself the purchase?
Sometimes a second TBR (on the same Thread network) can help make the Thread network more resilient but it is not needed.
In your case, the challenge is that HA needs to get the Thread dataset/credentials from the Alexa TBR in order for HA’s OTBR to join the Alexa Thread network. If you used the iOS HA Companion App, then the iOS should have stored the Alexa Thread network credentials from which you should be able to use the Companion App to “send credentials to HA”. You do this by going to the Thread Integration (using the Companion App) and there should be a button to send the credentials to HA. After doing this, you should see an (i) symbol for the Alexa Thread network, then you can make it “preferred” at which point it should under the covers, configure the HA OTBR to join the Alexa Thread network. something like that
OK, thanks… I cant find any solution to Connect Amazon Echo and homeassistant otbr to one Network. I think Amazon have a own solution.