With the SLZB, I first tried to have it setup via USB to my HA server and it was/is detected etc, however the Thread network didn’t seem to connect so I changed the settings to use it via Network. The device still has the USB connected to the HA server. I used this guide.
Here’s the config I used for it in the OpenThread add-on:
I just noticed new errors in the OpenThread Boarder Router add-on log too:
12:31:37.594 [W] P-RadioSpinel-: RCP failure detected
12:31:37.594 [W] P-RadioSpinel-: Trying to recover (1/2)
12:31:37.715 [C] P-RadioSpinel-: RCP => [C] Platform------: Reset info: 0x3 (EXT)
12:31:37.715 [C] P-RadioSpinel-: RCP => [C] Platform------: Extended Reset info: 0x301 (PIN)
12:31:37.715 [N] P-RadioSpinel-: RCP recovery is done
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b85d:44ff:fea7:c0a3/vethc197612/53
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b85d:44ff:fea7:c0a3/vethc197612/53
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b85d:44ff:fea7:c0a3/vethc197612/53
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b85d:44ff:fea7:c0a3/vethc197612/53
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b85d:44ff:fea7:c0a3/vethc197612/53
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b85d:44ff:fea7:c0a3/vethc197612/53
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b85d:44ff:fea7:c0a3/vethc197612/53
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::b85d:44ff:fea7:c0a3/vethc197612/53
19:21:30.964 [W] Nat64---------: incoming message is an IPv4 datagram but no NAT64 prefix configured, drop
19:21:31.662 [W] Nat64---------: incoming message is an IPv4 datagram but no NAT64 prefix configured, drop
19:22:01.269 [W] Nat64---------: incoming message is an IPv4 datagram but no NAT64 prefix configured, drop
19:22:02.060 [W] Nat64---------: incoming message is an IPv4 datagram but no NAT64 prefix configured, drop