SONOFF Zigbee 3.0 & Thread Dongle Lite (EFR32MG21) doesn't work

Hi guys,
I’m a hughe fan of Home Assistant and typically solve my issues using google. Unfortunately this stime that doesn’t work…

I use a sonoff zigbee dongle " ZBDongle-E USB Dongle Plus, EFR32MG21 + CH9102F/CP2102N Stick" with zigbee2mqtt which works like a charm. Now I bought the above mentioned sonoff Lite stick to upgrade my network to use thread additionally. Unfortunately it seems to be impossible to add eve thermostats to home assistant… I open the companion app on my iphone - say add integration - matter - new device - and - it just doenst show up - what am I missing??? OPenThread Border Router is running. in “tread” deivce ha-thread-e125 ia my prefered network (I also have a apple tv which shows up)

Looking into the protocol I get

Done

00:00:00.390 [W] P-Daemon------: Daemon read: Connection reset by peer

s6-rc: info: service otbr-agent-configure successfully started

s6-rc: info: service otbr-agent-rest-discovery: starting

[12:12:46] INFO: Successfully sent discovery information to Home Assistant.

s6-rc: info: service otbr-agent-rest-discovery successfully started

s6-rc: info: service legacy-services: starting

s6-rc: info: service legacy-services successfully started

00:00:26.919 [N] Mle-----------: RLOC16 e400 → fffe

00:00:27.183 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset

00:00:33.683 [N] RouterTable—: Allocate router id 57

00:00:33.683 [N] Mle-----------: RLOC16 fffe → e400

00:00:33.686 [N] Mle-----------: Role detached → leader

00:00:33.686 [N] Mle-----------: Partition ID 0x3b759115

[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!

00:00:35.801 [W] DuaManager----: Failed to perform next registration: NotFound

00:06:40.993 [N] TrelLink------: Peer fa48c1XXXa1 rx sock-addr differs the previously saved one

00:06:40.993 [N] TrelLink------: Rcvd sock-addr:[fdad:7313:4aa8:0XXX:8c3e]:51969

00:06:40.993 [N] TrelLink------: Prev sock-addr:[2a02:810b:XXXXX:af53:e82a]:51969

00:06:40.993 [N] TrelLink------: Updating the peer sock-addr to the newly received

Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface XXX:7580/vetha2e63b7/53

Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface XXXX:7580/vetha2e63b7/53

Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface XXXXX:7580/vetha2e63b7/53

Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7c05:71ff:fea7:7580/vetha2e63b7/53

Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface XXXXX:7580/vetha2e63b7/53

Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface XXXXX:7580/vetha2e63b7/53

Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface XxXXX:7580/vetha2e63b7/53

Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface XXXXX:7580/vetha2e63b7/53
<<

Any ideas how to fix that - I really apreciate any help - wasted a lot of time the last couple of days trying to fix that

Sascha

Were you able to fix this on yours? I’m seeing the TREL messages in my OTBR logs too but all my Thread devices stay online.

I’m seeing this in my OTBR logs in HA, and my ZBT-2 is
part of existing Apple thread network at my smart home.

Any advice from anyone?

I’m using a Eero max 7 with ipv6 enabled and again, everything is ‘working’ just trying to clean up logs for smoothest running home.

Thanks!

2d.05:18:07.981 [N] TrelLink------: Prev sock-addr:[2600:4040:ad25:b800:834:d1aa:a1ec:bbdc]:65039
2d.05:18:07.981 [N] TrelLink------: Updating the peer sock-addr to the newly received
2d.05:18:11.679 [N] TrelLink------: Peer 82041f1d8088f660 rx sock-addr differs the previously saved one
2d.05:18:11.679 [N] TrelLink------: Rcvd sock-addr:[fd54:b579:4453:42b2:18df:603b:3e4e:4904]:56949
2d.05:18:11.679 [N] TrelLink------: Prev sock-addr:[2600:4040:ad25:b800:143d:7f33:f111:9e14]:56949
2d.05:18:11.679 [N] TrelLink------: Updating the peer sock-addr to the newly received
2d.05:18:16.854 [N] TrelLink------: Peer 1af398cf6d0b7be0 rx sock-addr differs the previously saved one

Also, after searching some more, there’s an open GitHub from mid December 25’ with this exact topic.

“TREL breaks Matter/Thread device commissioning on ZBT-2 #4265

Here → TREL breaks Matter/Thread device commissioning on ZBT-2 · Issue #4265 · home-assistant/addons · GitHub