June 22, 20251 yr Author 4 minutes ago, Vr2Io said:That's why I suspect problem here, your Thread device were connect thr ZBT1's WiFi network and your phone in ISP's WiFi network.During commissioning, Phone and Thread device need in same network, so you may try commissioning (pairing Thread device) by HA instead Phone.Your HA have connect multiple network, one is usual home network and one is ZBT1 network. But me just one, all IPv4 / Thread also in one. I recommend in this way, at least this look more simple and work.Pairing a Matter over Thread device directly on HA without a phone is not convenient, as it requires a Bluetooth adapter and the machine where HA is installed needs to be physically near the device to commission.If nothing else works I'll buy a Bluetooth USB adapter but I would not consider that a solution... Edited June 22, 20251 yr by wblondel
June 22, 20251 yr 41 minutes ago, wblondel said:How do you do that? My device is NOT Matter over WiFi, but Matter over Thread.Both are same, when Thread device connect thr WiFi, that is Thread over WiFi, if connect thr zigbee, that is Thread over Zigbee. Edited June 22, 20251 yr by Vr2Io
June 22, 20251 yr Author 3 minutes ago, Vr2Io said:Both are same, when Thread device connect thr WiFi, that is Thread over WiFi, if connect thr zigbee, that is Thread over Zigbee.Sorry but Matter over WiFi and Matter over Thread are definitely different things 😅https://docs.silabs.com/matter/2.5.1/matter-fundamentals-introduction/#matter-enablement
June 22, 20251 yr 20 minutes ago, wblondel said:Pairing a Matter over Thread device directly on HA without a phone is not convenient, as it requires a Bluetooth adapter and the machine where HA is installed needs to be physically near the device to commission.If nothing else works I'll buy a Bluetooth USB adapter but I would not consider that a solution...Both correct.
June 23, 20251 yr Author I have some news.I am not sure if it is great news though 🤣I connected the Netgear switch directly to my ISP box downstairs with the 40m cable. I rebooted my NAS just in case, and tried to commission again the device, and........... it worked!Does that mean that the Asus RT-BE58U configured as a media bridge is somehow filtering things it shouldn't filter?Commissionning works with this:NAS ---> Mikrotik CRS305-1G-4S+ switch --> Netgear GS108v4 switch ---> ISP boxCommissionning doesn't work with this:NAS ---> Mikrotik CRS305-1G-4S+ switch --> Netgear GS108v4 switch ---> Asus RT-BE58U -----via Wi-Fi-----> ISP box Edited June 23, 20251 yr by wblondel
June 24, 20251 yr Congratulations, network bridge somehow trouble.Does HA success control Eve device ？ Edited June 24, 20251 yr by Vr2Io
June 24, 20251 yr Author 14 hours ago, Vr2Io said:Congratulations, network bridge somehow trouble.Does HA success control Eve device ？Yes, I can control the devices and get data from them using HA. I put back the original network setupNAS ---> Mikrotik CRS305-1G-4S+ switch --> Netgear GS108v4 switch ---> Asus RT-BE58U -----via Wi-Fi-----> ISP boxAnd it still works (control + data retrieval). It is only a problem for commissioning...
June 25, 20251 yr Author I edited my first post with the source of the issue. Edited June 25, 20251 yr by wblondel
July 3, 20251 yr Author Solution Alright, so after trying to make the commissioning work with other routers configured as a media bridge (which failed), I bought a pair of CPL. I connected one to my ISP box downstairs, and one to the Ethernet port of my NAS. Then I passed through the Ethernet NIC to the Home Assistant VM and configured the VM so that it uses only this NIC.It now works flawlessly.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.