toxic totem
Dear Team,
i'm using HA on mi PI4 and just bought an SLZB-06 Thread Border Router. The configuration wirked...had some issues but now, seams to be all okey.
I've tried since hours to commission my eve motion sensors, but unfortunatley, i've not been able to pass the network check.
What can i do.....all devices are in the same network.
I've tried 2.4 GHZ Wifi with no security, with security....but nothing worked.
Any sugguestions?
Thanks for your help.
Regards from Switzerland
dusty flint
Have you synchronized the Thread network keys to your mobile phone?
https://www.home-assistant.io/integrations/thread/#to-make-home-assistant-your-first-thread-network Step 3
toxic totem
hi jorg, yes i've did it more than once. according the commissioning process it passed the step to pass the credentials.
maiden swan
If you go to Home Assistant Settings --> Integrations --> Thread --> Configure
You should see the "ha-thread..." network listed with the Open Thread Border Router underneath.
Do you see a small "lock" icon next to it like this?
If you don't see that, can you try clicking the 3 dots next to it and select "Use for Android + iOS credentials"
toxic totem
hi marcelveldt, thanks for the hint. but i see it. and my companion app syncronised the credentials.
my matter server shows the following errors:
2024-09-25 23:02:23.179 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to advertise records: src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable
2024-09-25 23:02:23.211 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 298 ms, for event type 2
can anyone tell me what this could mean? at the end it stats " matter server successfully initialized"
maiden swan
If that is only logged at startup, its fine. Its the matter sdk trying to bind to an internal network
toxic totem
thanks marcel. Where should i see, that the system is trying to connect a Matter device? Shouldn this be logged somewhere?
toxic totem
do you know how i can read the log, when you try to visit OTBR's ip:6638 port?
toxic totem
New test using the matter dashboard in HA did also not work.
2024-09-28 00:02:12.683 (MainThread) ERROR [matter_server.server.client_handler] [547919618960] Error while handling: commission_with_code: Commission with code failed for node 1.
topaz furnace
I'm having a similar issue. 4 months ago, I was adding devices to my Matter over Thread network just fine. Now, when I try to do it, I'm stuck at the checking network connectivity stage of things, and it never gets past that. I've changed nothing on my network. Still using my Smartphone HA companion app on the WiFi for the network that my HA is on.
Did you figure out how to re-connect/ re-adopt your Matter devices?
toxic totem
hi jazzman, thanks for your message. no...still nothing is working. How was your config when it was working?
topaz furnace
It's kind of a long story. I'm still working on it.
I have Pi4 running HA, bought the NabuCasa SkyConnect dongle, and have some Eve Energy Smart Plugs and Aqara motion and light sensors. They were easily setup 4 months ago. Now, I'm stuck on the Samsung Galaxy smart phone when I try to add a device. It's something wrong with the Android side of things, as I never get past the "checking network connectivity" section of the new device adoption. I've tried a lot of different things to troubleshoot, but I'm still stuck.
Where are you getting stuck? Same spot?
See my discussion here if you'd like to read more. https://discord.com/channels/330944238910963714/1291367036131217505
toxic totem
thanks for your link....i'm stuck at the same place. Just bought a 6M. will try this new config. hopefully it is working than. will inform you
toxic totem
i've just installed the SLZB-06M. Had some issues with the new Thread, but got it to work. This time i've been able to get further in the commissionig Process....1 Step further than before. i passed the Network check and it tried to register the device....but after that it couldn't find the device on my network.
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:00:38.051 [W] DuaManager----: Failed to perform next registration: NotFound
00:03:25.265 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:83, chksum:4e13, ecn:no, to:0x1001, sec:yes, error:NoAck, prio:low, radio:all
00:03:25.265 [N] MeshForwarder-: src:[fd76:9d50:9ca8:1e8a:b3a3:7986:8e41:a5f1]:53536
00:03:25.265 [N] MeshForwarder-: dst:[fd76:9d50:9ca8:1e8a:e392:54e7:9047:8d80]:49155
00:04:58.236 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:99, chksum:4ab0, ecn:no, to:0x1001, sec:yes, error:NoAck, prio:low, radio:all
00:04:58.236 [N] MeshForwarder-: src:[fd33:7b43:7a8f:0:da64:373c:c348:3720]:55866
00:04:58.236 [N] MeshForwarder-: dst:[fdb2:19d1:ed31:1:977:8988:157f:4f83]:5540
toxic totem
if some one is interesseted....i've found the solution and it is working perfectly.
quiet mortar
What was it?
toxic totem
WIfi Password complexity ..... created a new wifi with e easy PW (WPA/WPA2) and now it is working. already 2 Devices connected
fallen crest
WIfi Password complexity ..... created a new wifi with e easy PW (WPA/WPA2) and ...
Can you show us how your WiFi password looked like? Can’t imagine that there are still WiFi password complexity issues nowadays, where we can generate anonymous passwords by a password manager. However… great that you solved your issue.
topaz furnace
I tried this, making a new WiFi SSID linked to my IoT VLAN. I used WPA2. Only lowercase alphabetical characters for a password that was 13 characters long. Still not working for me.