NoAddress during device connection

Armaell · December 6, 2024, 11:30pm

Hi everyone,

Well I’m not really sure where is my problem, the conbee, my configuration or even my phone.

So, I got Home Assistant OS in a VM so I can use the supervisor and install the addons.
Also a Conbee II flashed with OpenThread firmware.
And my Matter/Thread device is a Nuki Lock Pro 4 freshly bought

Then I mostly followed Phoscon guide

So I configured the Open Thread Border Router Add-on

 Add-on: OpenThread Border Router
 OpenThread Border Router add-on
-----------------------------------------------------------
 Add-on version: 2.12.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 14.0  (amd64 / qemux86-64)
 Home Assistant Core: 2024.12.1
 Home Assistant Supervisor: 2024.11.4
[.....]
[00:02:17] 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

And the Matter Server Add-on

2024-12-07 00:03:27.220 (MainThread) INFO [matter_server.server.device_controller] Loaded 0 nodes from stored configuration
2024-12-07 00:03:27.223 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.

On the integration side :

The Thread integration added itself
The Matter (BETA) integration was in the Discovered and is added with one click
But no Open Thread Border Router integration in sight.
I try [+ ADD INTEGRATION] button, but it require an url that I can’t find anywhere in the phoscon doc, home assistant doc or the add logs. I end up finding on reddit the url http://homeassistant.local:8081/ which seems to work. But this is my first worry of something not quite working.

But at least I get this in my Thread integration
Untitled

I then open my Android phone,
And in Home Assistant I click on the Settings > Companion app > Troubleshooting > Sync Thread credentials.

Quick tour on my Nuki app to enable Matter/Thread and then back on the Home Assistant app, do the [+ ADD INTEGRATION] and choose Add Matter Device. Scan the QR Code

Steps goes :

Searching for device…
Connecting to device
Generating Matter credentials
Checking network connectivity to MY_AWESOME_WIFI
Can’t connect to thread network ha-tread-6796

And when I check my Open Thread Border Router Add-on logs

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:27.286 [N] Mle-----------: RLOC16 4800 -> fffe
00:00:27.330 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:33.830 [N] RouterTable---: Allocate router id 18
00:00:33.830 [N] Mle-----------: RLOC16 fffe -> 4800
00:00:33.832 [N] Mle-----------: Role detached -> leader
00:00:33.832 [N] Mle-----------: Partition ID 0x16a747f9
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:00:34.836 [W] DuaManager----: Failed to perform next registration: NotFound

[Here I start the paring]

00:01:00.498 [W] Mle-----------: Failed to process Parent Request: Duplicated
00:01:02.520 [W] P-RadioSpinel-: Error processing result: NoAddress
00:01:02.520 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:01:04.316 [W] Mle-----------: Failed to process Parent Request: Duplicated
00:01:06.340 [W] P-RadioSpinel-: Error processing result: NoAddress
00:01:06.340 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:01:09.369 [W] P-RadioSpinel-: Error processing result: NoAddress
00:01:09.369 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:01:13.433 [W] P-RadioSpinel-: Error processing result: NoAddress
00:01:13.433 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:01:19.494 [W] P-RadioSpinel-: Error processing result: NoAddress
00:01:19.494 [W] P-RadioSpinel-: Error waiting response: NoAddress

After multiple failure, I end up trying to just pair my device to my Google Assistant, it still try to connect to Home assistant border router !! I get the same error and also the same logs in the border router addon-on ???

So yeah, I’m really not sure where is the problem, and that last mixup even while trying with Google Assistant is really strange.

Anyway, thank you for reading my problems

alpolle · December 12, 2024, 8:09am

hi @Armaell ,
were you actually able to solve your issue?
I’ve got absolutely same problem with my Nuki Pro 4, but what weird is - i had it working before and the integration with HA and Matter/OpenThread was working absolutely fine.
But then one day HA just lost connectivity with Nuki and i am not able to bring it back.
I have a feeling that it caused by latest Nuki firmware (4.4.9) as the upgrade time/date correlates with the date/time when the metrics stopped appearing in HA.
P.S. I have other Matter devices in my network, and all of them working fine…

Armaell · December 12, 2024, 8:38am

Hi @alpolle, thanks for your anwser

I did not try since then. I managed to connect them by Wifi/mqtt so it works as a workaround for now.

I guess I’ll have to try to buy some other Thread/Matter device to try and then maybe another alternative to the Conbee to try to find who is responsible. But I’m not really keen for new expenses right now.

For now I guess I’ll be hoping that the problem is on Nuki’s side and that a new firmware will fix it.

alpolle · December 12, 2024, 8:45am

ok, good to know that at least MQTT works fine - will try it hopefully later today.

wmaker · December 13, 2024, 1:31am

This one I am puzzled about. 'RadioSpinel" is a low level interface where the OTBR is trying to use what I think is the 802.15.4 Stack on the ConBee, but throwing an error. Since this is at such a low level (below the Thread protocol stack), I would suspect that the problem is somewhere in the ConBee/USB area. The description of the device in the OTBR Config showing it is using an Thread RCP looks correct, so I really don’t have any ideas what the problem may be. Possibly Baud Rate? Not sure…

pchaves1 · December 22, 2024, 12:42pm

I’m Having the same issue using a Smlight SLZB-06M (Matter-over-Thread ) as a OpenThread Border Router. I have a Unifi network and a UDMP already configured with DHCPv6.
The HA log says:

s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[11:34:52] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[11:34:52] INFO: Setup OTBR firewall…
[11:34:52] INFO: Starting otbr-agent…
[NOTE]-AGENT—: Running 0.3.0-b041fa52-dirty
[NOTE]-AGENT—: Thread version: 1.3.0
[NOTE]-AGENT—: Thread interface: wpan0
[NOTE]-AGENT—: Radio URL: spinel+hdlc+uart:///tmp/ttyOTBR?uart-baudrate=460800&uart-init-deassert
[NOTE]-AGENT—: Radio URL: trel://enp6s18
[NOTE]-ILS-----: Infra link selected: enp6s18
tiocmbic: Inappropriate ioctl for device
50d.16:40:17.292 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.068 [N] RoutingManager: BR ULA prefix: fd26:a6:c75::/48 (loaded)
00:00:00.068 [N] RoutingManager: Local on-link prefix: fdbb:94e1:a652:dfd7::/64
00:00:00.090 [N] Mle-----------: Role disabled → detached
00:00:00.122 [N] P-Netif-------: Changing interface state to up.
00:00:00.141 [W] P-Netif-------: Failed to process request#2: No such process
00:00:00.142 [W] P-Netif-------: Failed to process request#6: No such process
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-configure: starting
[11:34:53] INFO: Enabling NAT64.
Done
00:00:00.337 [W] P-Netif-------: Failed to process request#7: No such process
Done
Done
s6-rc: info: service otbr-agent-configure successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
[11:34:53] 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
Default: mDNSCoreReceiveResponse: Received from fdbb:94e1:a652:dfd7:2687:eaaf:e2b8:baaa:5353 26 c.b.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.0.0.d.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 C.B.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.0.0.D.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fdbb:94e1:a652:dfd7:2687:eaaf:e2b8:baaa:5353 26 8.1.9.a.b.7.5.3.0.7.3.3.5.6.e.4.1.0.d.2.4.8.9.f.0.a.8.0.1.0.0.2.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 8.1.9.A.B.7.5.3.0.7.3.3.5.6.E.4.1.0.D.2.4.8.9.F.0.A.8.0.1.0.0.2.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fdbb:94e1:a652:dfd7:2687:eaaf:e2b8:baaa:5353 26 6.e.b.0.4.e.a.e.4.a.b.1.a.1.3.b.0.0.0.0.0.0.0.0.1.0.0.0.0.0.d.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 6.E.B.0.4.E.A.E.4.A.B.1.A.1.3.B.0.0.0.0.0.0.0.0.1.0.0.0.0.0.D.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fdbb:94e1:a652:dfd7:2687:eaaf:e2b8:baaa:5353 26 c.b.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.d.2.4.8.9.f.0.a.8.0.1.0.0.2.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 C.B.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.D.2.4.8.9.F.0.A.8.0.1.0.0.2.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::42:d4ff:fe85:ff01:5353 26 1.0.f.f.5.8.e.f.f.f.4.d.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 1.0.F.F.5.8.E.F.F.F.4.D.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::42:a7ff:fe1c:2604:5353 26 4.0.6.2.c.1.e.f.f.f.7.a.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 4.0.6.2.C.1.E.F.F.F.7.A.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::ce1:46ff:fe20:eae6:5353 26 6.e.a.e.0.2.e.f.f.f.6.4.1.e.c.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 6.E.A.E.0.2.E.F.F.F.6.4.1.E.C.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::60d8:3ff:fe55:ae07:5353 26 7.0.e.a.5.5.e.f.f.f.3.0.8.d.0.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 7.0.E.A.5.5.E.F.F.F.3.0.8.D.0.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::bc8a:15ff:fe58:95a4:5353 26 4.a.5.9.8.5.e.f.f.f.5.1.a.8.c.b.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 4.A.5.9.8.5.E.F.F.F.5.1.A.8.C.B.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::4816:edff:fe19:b5e6:5353 26 6.e.5.b.9.1.e.f.f.f.d.e.6.1.8.4.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 6.E.5.B.9.1.E.F.F.F.D.E.6.1.8.4.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from 192.168.107.63:5353 26 63.107.168.192.in-addr.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 63.107.168.192.in-addr.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::2c60:8eff:fed7:aeb2:5353 26 2.b.e.a.7.d.e.f.f.f.e.8.0.6.c.2.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 2.B.E.A.7.D.E.F.F.F.E.8.0.6.C.2.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::38b1:c7ff:fe38:5c4:5353 26 4.c.5.0.8.3.e.f.f.f.7.c.1.b.8.3.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 4.C.5.0.8.3.E.F.F.F.7.C.1.B.8.3.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from 172.30.32.1:5353 26 1.32.30.172.in-addr.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 1.32.30.172.in-addr.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::acc9:46ff:fe33:3b66:5353 26 6.6.b.3.3.3.e.f.f.f.6.4.9.c.c.a.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 6.6.B.3.3.3.E.F.F.F.6.4.9.C.C.A.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from 172.17.0.1:5353 26 1.0.17.172.in-addr.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 1.0.17.172.in-addr.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::84c3:ff:fe44:b1a1:5353 26 1.a.1.b.4.4.e.f.f.f.0.0.3.c.4.8.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 1.A.1.B.4.4.E.F.F.F.0.0.3.C.4.8.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::e8e2:3fff:fed5:1c13:5353 26 3.1.c.1.5.d.e.f.f.f.f.3.2.e.8.e.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 3.1.C.1.5.D.E.F.F.F.F.3.2.E.8.E.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::e879:c5ff:fe1c:41aa:5353 26 a.a.1.4.c.1.e.f.f.f.5.c.9.7.8.e.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 A.A.1.4.C.1.E.F.F.F.5.C.9.7.8.E.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::fcf5:eaff:fec9:a9a8:5353 26 8.a.9.a.9.c.e.f.f.f.a.e.5.f.c.f.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 8.A.9.A.9.C.E.F.F.F.A.E.5.F.C.F.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::988e:cdff:fed3:bbbe:5353 26 e.b.b.b.3.d.e.f.f.f.d.c.e.8.8.9.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 E.B.B.B.3.D.E.F.F.F.D.C.E.8.8.9.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::c0f6:fdff:fec9:1851:5353 26 1.5.8.1.9.c.e.f.f.f.d.f.6.f.0.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 1.5.8.1.9.C.E.F.F.F.D.F.6.F.0.C.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::60fd:81ff:fe0b:a49f:5353 26 f.9.4.a.b.0.e.f.f.f.1.8.d.f.0.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 F.9.4.A.B.0.E.F.F.F.1.8.D.F.0.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::1ceb:f3ff:fee6:c9f8:5353 26 8.f.9.c.6.e.e.f.f.f.3.f.b.e.c.1.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 8.F.9.C.6.E.E.F.F.F.3.F.B.E.C.1.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
Default: mDNSCoreReceiveResponse: Received from fe80::1:ebff:fe64:4d97:5353 26 7.9.d.4.4.6.e.f.f.f.b.e.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR HomeAsssistant-254.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding 22 7.9.D.4.4.6.E.F.F.F.B.E.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR HomeAsssistant.local.
00:00:26.760 [N] Mle-----------: RLOC16 0800 → fffe
00:00:27.246 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:33.746 [N] RouterTable—: Allocate router id 2
00:00:33.746 [N] Mle-----------: RLOC16 fffe → 0800
00:00:33.750 [N] Mle-----------: Role detached → leader
00:00:33.750 [N] Mle-----------: Partition ID 0x196b06d2
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:00:35.639 [W] DuaManager----: Failed to perform next registration: NotFound
00:07:22.234 [W] P-RadioSpinel-: Error processing result: NoAddress
00:07:22.234 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:07:22.727 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:105, chksum:6d03, ecn:no, to:d207c5418ce9fbe3, sec:no, error:NoAck, prio:net, radio:all
00:07:22.727 [N] MeshForwarder-: src:[fe80:0:0:0:10ad:d822:f87:7fb6]:19788
00:07:22.727 [N] MeshForwarder-: dst:[fe80:0:0:0:d007:c541:8ce9:fbe3]:19788
00:35:15.921 [W] P-RadioSpinel-: Error processing result: NoAddress
00:35:15.921 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:35:16.198 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:195, chksum:8ac1, ecn:no, to:ae19e65fc44b57c6, sec:yes, error:NoAck, prio:net, radio:all
00:35:16.198 [N] MeshForwarder-: src:[fe80:0:0:0:10ad:d822:f87:7fb6]:19788
00:35:16.198 [N] MeshForwarder-: dst:[fe80:0:0:0:ac19:e65f:c44b:57c6]:19788
00:39:01.263 [W] P-RadioSpinel-: Error processing result: NoAddress
00:39:01.263 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:40:55.930 [W] P-RadioSpinel-: Error processing result: NoAddress
00:40:55.930 [W] P-RadioSpinel-: Error waiting response: NoAddress

Any advice?

wmaker · December 22, 2024, 5:04pm

Just an FYI, a couple of the Matter/Thread HA developers discussed on Discord, that using this stick is not recommended for Thread as they believe there is too much delay involved between HA and this stick when using it over Ethernet.
“we conclude that the approach of RCP over IP is dangerous. Multiple occurances of a radio/firmware lockup where the OTBR can no longer communicate with the stick, then leading into a mess. So we actually do not recommend these sticks for Thread when using the ethernet connection. Instead just use the USB-connection or use them for Zigbee (where one could argue again how smart it is to forward the serial protocol over IP).”

pchaves1 · December 28, 2024, 12:08pm

I’m using it with USB cable, with skyConnect i have the same issue. No ideas right now…

zgbee · January 5, 2025, 10:41am

I also just suddenly started getting these errors this morning. At least, I think the errors just started today - my matter devices were working last night, but were not this morning, and I noticed the same P-RadioSpinel errors documented here.

Connected via SkyConnect USB stick (dedicated to Thread). I have a Nuki doorlock, and a Meross presence detector.

Oddly, the Nuki app seems to indicate that the lock is successfully connected to the server via Matter, but home assistant’s device page shows it as unavailable.

My full log:

-----------------------------------------------------------
 Add-on: OpenThread Border Router
 OpenThread Border Router add-on
-----------------------------------------------------------
 Add-on version: 2.12.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 14.1  (amd64 / qemux86-64)
 Home Assistant Core: 2025.1.0
 Home Assistant Supervisor: 2024.12.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[11:33:53] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[11:33:53] INFO: Setup OTBR firewall...
[11:33:53] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-b041fa52-dirty
[NOTE]-AGENT---: Thread version: 1.3.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB1?uart-baudrate=460800&uart-flow-control
[NOTE]-AGENT---: Radio URL: trel://enp0s3
[NOTE]-ILS-----: Infra link selected: enp0s3
49d.18:10:53.840 [W] P-SpinelDrive-: Error processing frame: Drop
49d.18:10:53.844 [W] P-SpinelDrive-: Error processing frame: Drop
49d.18:10:53.844 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.075 [N] RoutingManager: BR ULA prefix: fddc:bed6:926f::/48 (loaded)
00:00:00.081 [N] RoutingManager: Local on-link prefix: fda3:f697:733a:3303::/64
00:00:00.159 [N] Mle-----------: Role disabled -> detached
00:00:00.167 [N] P-Netif-------: Changing interface state to up.
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-configure: starting
00:00:00.203 [W] P-Netif-------: Failed to process request#2: No such process
00:00:00.204 [W] P-Netif-------: Failed to process request#6: No such process
[11:33:54] INFO: Enabling NAT64.
00:00:00.244 [W] P-Netif-------: Failed to process request#7: No such process
Done
Done
00:00:00.245 [W] P-Daemon------: Failed to write CLI output: Broken pipe
Done
s6-rc: info: service otbr-agent-configure successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
[11:33:54] 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.969 [N] Mle-----------: RLOC16 b000 -> fffe
00:00:27.688 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:34.188 [N] RouterTable---: Allocate router id 44
00:00:34.188 [N] Mle-----------: RLOC16 fffe -> b000
00:00:34.203 [N] Mle-----------: Role detached -> leader
00:00:34.204 [N] Mle-----------: Partition ID 0x30278117
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:00:36.823 [W] DuaManager----: Failed to perform next registration: NotFound
00:01:10.561 [W] Nat64---------: no mapping found for the IPv4 address
00:02:15.022 [W] P-RadioSpinel-: Error processing result: NoAddress
00:02:15.022 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:03:00.814 [W] DnssdServer---: Upstream query transaction 0 closed: ResponseTimeout.
00:03:10.796 [W] DnssdServer---: Upstream query transaction 0 closed: ResponseTimeout.
00:03:10.874 [W] Nat64---------: no mapping found for the IPv4 address

zgbee · January 5, 2025, 6:34pm

So, I resolved the issue with the Meross presence detector by resetting it and re-pairing the device with matter from the Add Device section on companion app.

My openthread logs still look the same with the similar errors, but the “new” device was picked up by Home Assistant. The device name is the same, but the events now have the device name pre-pended to them.

i.e. my old automation for Device named Main Bath Presence Sensor was waiting for a trigger of Occupancy became occupied.

Now, the device name is the same, but I have to wait for a trigger of Main Bath Presence Sensor Occupancy became occupied

The reset also unpaired the device from the Meross app on my phone and the app seemed to get confused when trying to re-add the same device, so I might have to reset everything again to get that working (so I can modify the more advanced settings of the device).

Anyway, I haven’t tried this with my Nuki yet, and the whole process is quite annoying, but at least I have my sensor working again.