You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having issues with ConBee II with the newest thread firmware ot-rcp-cb2_0x01010700.GCF when adding a matter over thread device (Aqara U200) to HA and I see I'm not alone - check here and here
I'm having the same - I followed guide from phoscon and I was trying to comission device using android phone, directly from HA (via matter ui) - nothing. It always timeouts when waiting for device to connect to thread device with an error "No connection to Thread network ha-thread-..."
HA is running on a VM, USB shared from the host with Bluetooth and ConBee II itself (it was working well while managing my zigbee network). I verfied and tried everyting I could find on the internet including this great post about matter troubleshooting.
Logs below are when I used local USB BT stick to comission directly from matter UI, providing dataset and pin for matter. It's the most verbose I could get
I am having issues with ConBee II with the newest thread firmware ot-rcp-cb2_0x01010700.GCF when adding a matter over thread device (Aqara U200) to HA and I see I'm not alone - check here and here
I'm having the same - I followed guide from phoscon and I was trying to comission device using android phone, directly from HA (via matter ui) - nothing. It always timeouts when waiting for device to connect to thread device with an error "No connection to Thread network ha-thread-..."
HA is running on a VM, USB shared from the host with Bluetooth and ConBee II itself (it was working well while managing my zigbee network). I verfied and tried everyting I could find on the internet including this great post about matter troubleshooting.
Logs below are when I used local USB BT stick to comission directly from matter UI, providing dataset and pin for matter. It's the most verbose I could get
I'm happy to provide more info if required.
The text was updated successfully, but these errors were encountered: