Hello,
I run HAOS on a DS720+ with SSD. I have have spent hours trying to get the zbt-1 set up correctly. Been a bunch of problems, but now, I at least getting closer.
Anyhow, something is still not correct. In my log in Open Thread, it says.
00:00:38.667 [W] DuaManager----: Failed to perform next registration: NotFound
I can not add the boarder router credential to google services. I managed to do it twice, then I figured out I had problem with the router settings and now, it’s looked
I can access the zbt-1 trough port 8080, so it looks right.
The last thing to add. when i use HA phone app and try to add a matter device, it says it’s currently not available.
I might have left out important info… anyone, any idea?
This indicate a warning and it is often not critical.
The Matter and Thread integrations and addons spew out a lot of those warnings.
First make sure have set the preferred Thread network in HA by going to Settings → Integrations → Thread → click the gear → click the three dots next to your network and set the network to be used for router in Android and iOS.
Next go to you phone and start up the Companion App.
Click the Settings → Companion App → Troubleshooting → Sync Thread Credentials
Click the Sync option twice.
It should say Home Assistant and this device use the same credentials. If it says it sync the credentials again, then you need to go to your phones settings menu and search for Google Play Cache and clear it (this might delete other stored information too on your phone).
When you have clear the cache, then sync the Thread Credentials again in the Companion App as described above.
Thanks WallyR, done all that a few times. I had a problem with the usb in my DS with VMM. I have cleared the google services twice before I wrote here. Did not mention that. I almost lost my timeline on google maps (10 years of visited sites) I feel that it dod not really help. Today, I tried again to aff a matter device. This time, it asked me to scan a QR code. It said the settings were not right. The strange thing was, the name of the thread router was not the last one i had set yesterday.
Is the name of the thread router totaly unimportant? Can the credentials be correct otherwise? Does google need to restart the account in any kind of way before you can sync the boarder router? Anyhow,I feel that i really lack the control of the settings in google services. I have a 1m usb cable. Quite thick USB2. Not shore if it is shielded. I know that ZBT-1 is sensitve. I have tried without the cable as well.
The fault I get not, says, it was not possible connect to the thread networ, check if the device is compatible with the network kind. (Translated) I have tried to connect a Ikea Myggbett.
I have tried a bit more and can only find that my matter server works, but, not with a local ipv6 address. It catches the public ipv6 address as google done like. Any idea of a fix for that?
Spent even more hours with this. I have deleted the public ipv6, but my DSM is forcing them back. I managed to delete the ipv6 addresses without the local fe80 and then with service browser check that i really had fe80 under the matter server. All good I thought. But google wont accept the update anyways… Is there any additional settings for matter server from SSH? Force matter server to always use the local ipv6?
When using Matter over Thread, Matter and HA need a “routable” IPv6 address, so link-local FE80 is not going to work. HA/Matter/OTBR can work using a global/public IPv6 address prefix.
That can’t be true, because then it would not work in a network setup with no IPv6 provided from the ISP or where the user have specifically configured it to provide it.
Yes, one needs either a ULA or a GUA, both of which are routable IPv6 addresses in order for the Matter Server to talk to Thread devices. (I too had a typo, so edited my post which now says Link Local Addresses can NOT be routed across a TBR)
