Channel Access Failure

Configuration Matter/Thread
1

I’m trying to setup Thread and using a “Eve Energy” over Matter/Thread.

Setup:
Home Assistant OS 13.1
Core 2024.9.2
HW: Raspberry Pi 4

  • Sky Connect (latest Firmware)

I’m having only 1 Thread-Network: HomeAssistant. I made it my preferred Netword. Share the Cred with my iPhone.
When adding the Matter-Device, it stops after many seconds with “FAILED”

Debug of OTBR:

[20:30:17] INFO: The otbr-web is disabled.
s6-rc: info: service mdns: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service mdns successfully started
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service banner: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
[20:30:18] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Aug 26 2024 16:52:48) starting

-----------------------------------------------------------
 Add-on: OpenThread Border Router
 OpenThread Border Router add-on
-----------------------------------------------------------
 Add-on version: 2.10.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.1  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.9.2
 Home Assistant Supervisor: 2024.09.1
-----------------------------------------------------------
 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
[20:30:20] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[20:30:20] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
2024-09-19 20:30:22.227 homeassistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.4.3', ezsp_version=None, ot_rcp_version='SL-OPENTHREAD/2.4.0.0_GitHub-7074a43e4' (2.4.0.0), cpc_version=None, fw_type=<FirmwareImageType.OT_RCP: 'ot-rcp'>, baudrate=460800)
2024-09-19 20:30:22.228 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-09-19 20:30:24.247 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
2024-09-19 20:30:25.380 homeassistant universal_silabs_flasher.flasher INFO Detected ApplicationType.SPINEL, version 'SL-OPENTHREAD/2.4.0.0_GitHub-7074a43e4' (2.4.0.0) at 460800 baudrate (bootloader baudrate None)
2024-09-19 20:30:25.381 homeassistant universal_silabs_flasher.flash INFO Firmware version 'SL-OPENTHREAD/2.4.0.0_GitHub-7074a43e4' (2.4.0.0) is flashed, not re-installing
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[20:30:26] INFO: Setup OTBR firewall...
[20:30:27] INFO: Starting otbr-agent...
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
s6-rc: info: service otbr-agent-configure: starting
Done
s6-rc: info: service otbr-agent-configure successfully started
[20:30:28] 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
[NOTE]-AGENT---: Running 0.3.0-b66cabf-dirty
[NOTE]-AGENT---: Thread version: 1.3.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=460800&uart-flow-control
[NOTE]-AGENT---: Radio URL: trel://end0
[NOTE]-ILS-----: Infra link selected: end0
49d.17:23:50.692 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.052 [N] RoutingManager: BR ULA prefix: fd01:3b85:19d::/48 (loaded)
00:00:00.052 [N] RoutingManager: Local on-link prefix: fd49:e125:7b71:6e0a::/64
00:00:00.089 [N] Mle-----------: Role disabled -> detached
00:00:00.121 [N] P-Netif-------: Changing interface state to up.
00:00:00.158 [W] P-Netif-------: Failed to process request#2: No such process
00:00:00.159 [W] P-Netif-------: Failed to process request#6: No such process
00:00:00.373 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:00.577 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:00.811 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:01.033 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:01.274 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:01.466 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:01.694 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:01.932 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:02.163 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:02.421 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:02.642 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:02.872 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:03.091 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:03.297 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:03.505 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:03.750 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:04.004 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:04.231 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:04.426 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:04.653 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:04.872 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:05.125 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:07.735 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:08.723 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:09.773 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:09.992 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:15.068 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:19.972 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:25.327 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:26.206 [N] Mle-----------: RLOC16 8c00 -> fffe
00:00:26.810 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:27.067 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:27.808 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:28.569 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:29.788 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:31.051 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:32.295 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:32.675 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:33.311 [N] RouterTable---: Allocate router id 35
00:00:33.311 [N] Mle-----------: RLOC16 fffe -> 8c00
2

The following may not be very helpful, but another user seems to have experienced the same problem:

3

Are your IPv6 settings set to automatic in HAOS and do you only have one NIC configured?

4

Yes, IPv6 is on Auto, and there is only one NIC

5

Okay, it just looks like your bridge is using an IPv6 address outside the fe80 network that is normally used.
HA have really bad tools to manage IPv6, so if your router is providing an IPv6 address that is “unexpected” to HA then it may fail.

7

Alright. Should the Router provide an IPv6-Adress for HA? Or is it enought to have it on “Auto”, even the Network-Subnet has IPv6 disabeled?

8

Mine now run with just the auto generated IPv6 address of the device itself, so a fe80 address.
I got weird cases with an IPv6 address from the router, because HA would choose what IPv6 address it wanted to use at random.
Removing the IPv6 address provided by the router from HA mde it work somewhat.
Having an IPv6 address on the router prevented the NAT64 option to work, because HA could not be configured to ignore the broadcast with router information, so it tried to use IPv6 to access the internet with only local addresses available.
Removing IPv6 entirely from the routers internal network and only relying on the devices own auto-configuration made it work.

9

ChannelAccessFailure should be more related to the inability of the Thread Radio (USB SkyConnect stick) to send a packet over the RF using 802.15.4. Although the OTBR can talk to the SkyConnect (OTBR can see the flash version running on the SkyConnect), the flash code can’t send a packet out over the radio. I don’ know what is causing it, but I would shutdown the OTBR, unplug, plug-back-in the SkyConnect and restart OTBR. Make sure the SkyConnect is using an extender cable so as the SkyConnect is several inches away from your RaspberryPi.

10

I disabled ipv6 in my subnet. So now HA should only have the self-assigned address on “auto” and a static ipv4.

I tried restarting OBTR with re-plugging SkyConnect, but the error still occures. (USB-Extender was always in place)

Coult it be, that it is a Hardware-Issue of the SkyConnect?
I already ordered a SKZB-06, but it will take some time to be deliviered…

11

What firmware are on your sky connect?
Zigbee only or Matter only or dual protocol?

12

I’m using this Firmware: OpenThread (RCP) SL-OPENTHREAD/2.4.0.0_GitHub-7074a43e4

13

It looks like a dual proto ol firmware, so what are the output from your multi protocol addon when you restart that one?

14

Multiprotocol Output:

-----------------------------------------------------------
 Add-on: Silicon Labs Multiprotocol
 Zigbee and OpenThread multiprotocol add-on
-----------------------------------------------------------
 Add-on version: 2.4.5
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.1  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.9.2
 Home Assistant Supervisor: 2024.09.1
-----------------------------------------------------------
 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
[19:37:29] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[19:37:29] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
2024-09-22 19:37:31.650 homeassistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.3.1', ezsp_version='7.3.1.0', ot_rcp_version='SL-OPENTHREAD/2.3.1.0_GitHub-e6df00dd6' (2.3.1.0), cpc_version='4.3.1-4f7f9e99-dirty-de58d93e' (4.3.1), fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>, baudrate=460800)
2024-09-22 19:37:31.651 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-09-22 19:37:33.671 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2024-09-22 19:37:33.705 homeassistant universal_silabs_flasher.flasher INFO Detected ApplicationType.CPC, version '4.3.1-4f7f9e99-dirty-de58d93e' (4.3.1) at 460800 baudrate (bootloader baudrate None)
2024-09-22 19:37:33.706 homeassistant universal_silabs_flasher.flash INFO Firmware version '4.3.1-4f7f9e99-dirty-de58d93e' (4.3.1) is flashed, not re-installing
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service cpcd-config: starting
[19:37:34] INFO: Using known baudrate of 460800 for cpcd!
[19:37:35] INFO: Generating cpcd configuration.
s6-rc: info: service cpcd-config successfully started
s6-rc: info: service cpcd: starting
[19:37:35] INFO: Starting cpcd...
WARNING in function 'main' in file /usr/src/cpc-daemon/main.c at line #186 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
s6-rc: info: service cpcd successfully started
s6-rc: info: service zigbeed: starting
s6-rc: info: service otbr-agent: starting
s6-rc: info: service zigbeed successfully started
[19:37:36] INFO: Starting zigbeed...
[19:37:35:597048] Info : [CPCd v4.3.1.0] [Library API v3] [RCP Protocol v4]
[19:37:35:597421] Info : Git commit: 133b29678b3d0bc7578e098d2f46b4d5bcd2ebb4 / branch: 
[19:37:35:597425] Info : Sources hash: ff8300587e7e4ab1def7a89a272c0baef32f9eb3bff9b0ba06b94e655d652367
[19:37:35:597432] WARNING : In function 'main' in file /usr/src/cpc-daemon/main.c at line #186 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
[19:37:35:597600] Info : Reading cli arguments
[19:37:35:597617] Info : /usr/local/bin/cpcd 
[19:37:35:601773] Info : Reading configuration
[19:37:35:601790] Info :   file_path = /usr/local/etc/cpcd.conf
[19:37:35:601794] Info :   instance_name = cpcd_0
[19:37:35:601797] Info :   socket_folder = /dev/shm
[19:37:35:601800] Info :   operation_mode = MODE_NORMAL
[19:37:35:601802] Info :   use_encryption = false
[19:37:35:601805] Info :   binding_key_file = /etc/binding-key.key
[19:37:35:601808] Info :   stdout_tracing = false
[19:37:35:601811] Info :   file_tracing = false
[19:37:35:601813] Info :   lttng_tracing = false
[19:37:35:601816] Info :   enable_frame_trace = false
[19:37:35:601818] Info :   traces_folder = /dev/shm/cpcd-traces
[19:37:35:601821] Info :   bus = UART
[19:37:35:601823] Info :   uart_baudrate = 460800
[19:37:35:601827] Info :   uart_hardflow = true
[19:37:35:601829] Info :   uart_file = /dev/ttyUSB0
[19:37:35:601832] Info :   fu_recovery_pins_enabled = false
[19:37:35:601835] Info :   fu_connect_to_bootloader = false
[19:37:35:601838] Info :   fu_enter_bootloader = false
[19:37:35:601840] Info :   restart_cpcd = false
[19:37:35:601843] Info :   application_version_validation = false
[19:37:35:601845] Info :   print_secondary_versions_and_exit = false
[19:37:35:601848] Info :   use_noop_keep_alive = false
[19:37:35:601850] Info :   reset_sequence = true
[19:37:35:601853] Info :   stats_interval = 0
[19:37:35:601856] Info :   rlimit_nofile = 2000
[19:37:35:601859] Info : ENCRYPTION IS DISABLED 
[19:37:35:601861] Info : Starting daemon in normal mode
[19:37:35:618143] Info : Connecting to Secondary...
[19:37:35:695933] Info : RX capability is 256 bytes
[19:37:35:695961] Info : Connected to Secondary
[19:37:35:699063] Info : Secondary Protocol v4
[19:37:35:706793] Info : Secondary CPC v4.3.1
[19:37:35:710131] Info : Secondary bus bitrate is 460800
[19:37:35:717408] Info : Secondary APP v4.3.1-4f7f9e99-dirty-de58d93e
[19:37:35:717677] Info : Daemon startup was successful. Waiting for client connections
[19:37:36] INFO: Setup OTBR firewall...
[19:37:37] INFO: Starting otbr-agent...
otbr-agent[301]: [NOTE]-AGENT---: Running 0.3.0
otbr-agent[301]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[301]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[301]: [NOTE]-AGENT---: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0
otbr-agent[301]: [NOTE]-ILS-----: Infra link selected: end0
otbr-agent[301]: 49d.17:06:42.483 [C] Platform------: mCpcBusSpeed = 115200
[19:37:37:051939] Info : New client connection using library v4.3.1.0
[19:37:37:055860] Info : Opened connection socket for ep#12
[19:37:37:055986] Info : Endpoint socket #12: Client connected. 1 connections
[19:37:37:369854] Info : New client connection using library v4.3.1.0
[19:37:37:374110] Info : Endpoint socket #12: Client connected. 2 connections

[...]

otbr-agent[301]: 00:00:04.946 [N] MeshForwarder-:     src:[fe80:0:0:0:541f:e88b:5b2e:6e00]:5355
otbr-agent[301]: 00:00:04.946 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:1:3]:5355
otbr-agent[301]: 00:00:05.886 [W] Platform------: Handle transmit done failed: ChannelAccessFailure
otbr-agent[301]: 00:00:05.886 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:82, chksum:10ac, ecn:no, to:0xffff, sec:no, error:ChannelAccessFailure, prio:net
otbr-agent[301]: 00:00:05.886 [N] MeshForwarder-:     src:[fe80:0:0:0:541f:e88b:5b2e:6e00]:19788
otbr-agent[301]: 00:00:05.886 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
otbr-agent[301]: 00:00:10.849 [W] Platform------: Handle transmit done failed: ChannelAccessFailure
otbr-agent[301]: 00:00:10.849 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:82, chksum:f65a, ecn:no, to:0xffff, sec:no, error:ChannelAccessFailure, prio:net
otbr-agent[301]: 00:00:10.849 [N] MeshForwarder-:     src:[fe80:0:0:0:541f:e88b:5b2e:6e00]:19788
otbr-agent[301]: 00:00:10.849 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
otbr-agent[301]: 00:00:16.136 [W] Platform------: Handle transmit done failed: ChannelAccessFailure
otbr-agent[301]: 00:00:16.136 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:82, chksum:df20, ecn:no, to:0xffff, sec:no, error:ChannelAccessFailure, prio:net
otbr-agent[301]: 00:00:16.136 [N] MeshForwarder-:     src:[fe80:0:0:0:541f:e88b:5b2e:6e00]:19788
otbr-agent[301]: 00:00:16.136 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
otbr-agent[301]: 00:00:21.246 [W] Platform------: Handle transmit done failed: ChannelAccessFailure
otbr-agent[301]: 00:00:21.247 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:82, chksum:7773, ecn:no, to:0xffff, sec:no, error:ChannelAccessFailure, prio:net
otbr-agent[301]: 00:00:21.247 [N] MeshForwarder-:     src:[fe80:0:0:0:541f:e88b:5b2e:6e00]:19788
otbr-agent[301]: 00:00:21.247 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
otbr-agent[301]: 00:00:26.723 [W] Platform------: Handle transmit done failed: ChannelAccessFailure
otbr-agent[301]: 00:00:26.724 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:82, chksum:464c, ecn:no, to:0xffff, sec:no, error:ChannelAccessFailure, prio:net
otbr-agent[301]: 00:00:26.724 [N] MeshForwarder-:     src:[fe80:0:0:0:541f:e88b:5b2e:6e00]:19788
otbr-agent[301]: 00:00:26.724 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
otbr-agent[301]: 00:00:28.234 [N] Mle-----------: RLOC16 a800 -> fffe
otbr-agent[301]: 00:00:28.239 [W] Platform------: [netif] Failed to process request#5: Unknown error -95
otbr-agent[301]: 00:00:28.309 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[301]: 00:00:28.543 [W] Platform------: Handle transmit done failed: ChannelAccessFailure
otbr-agent[301]: 00:00:28.543 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:84, chksum:f88b, ecn:no, to:0xffff, sec:no, error:ChannelAccessFailure, prio:net
otbr-agent[301]: 00:00:28.543 [N] MeshForwarder-:     src:[fe80:0:0:0:541f:e88b:5b2e:6e00]:19788
otbr-agent[301]: 00:00:28.543 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
otbr-agent[301]: 00:00:29.254 [W] Platform------: Handle transmit done failed: ChannelAccessFailure
otbr-agent[301]: 00:00:29.254 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:84, chksum:7f7c, ecn:no, to:0xffff, sec:no, error:ChannelAccessFailure, prio:net
otbr-agent[301]: 00:00:29.254 [N] MeshForwarder-:     src:[fe80:0:0:0:541f:e88b:5b2e:6e00]:19788
otbr-agent[301]: 00:00:29.254 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
otbr-agent[301]: 00:00:30.035 [W] Platform------: Handle transmit done failed: ChannelAccessFailure
otbr-agent[301]: 00:00:30.035 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:84, chksum:e2a9, ecn:no, to:0xffff, sec:no, error:ChannelAccessFailure, prio:net
otbr-agent[301]: 00:00:30.035 [N] MeshForwarder-:     src:[fe80:0:0:0:541f:e88b:5b2e:6e00]:19788
otbr-agent[301]: 00:00:30.036 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
otbr-agent[301]: 00:00:31.279 [W] Platform------: Handle transmit done failed: ChannelAccessFailure
otbr-agent[301]: 00:00:31.279 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:84, chksum:b90d, ecn:no, to:0xffff, sec:no, error:ChannelAccessFailure, prio:net
otbr-agent[301]: 00:00:31.280 [N] MeshForwarder-:     src:[fe80:0:0:0:541f:e88b:5b2e:6e00]:19788
otbr-agent[301]: 00:00:31.280 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
otbr-agent[301]: 00:00:32.561 [W] Platform------: Handle transmit done failed: ChannelAccessFailure
otbr-agent[301]: 00:00:32.562 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:84, chksum:cd56, ecn:no, to:0xffff, sec:no, error:ChannelAccessFailure, prio:net
otbr-agent[301]: 00:00:32.562 [N] MeshForwarder-:     src:[fe80:0:0:0:541f:e88b:5b2e:6e00]:19788
otbr-agent[301]: 00:00:32.562 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
otbr-agent[301]: 00:00:33.798 [W] Platform------: Handle transmit done failed: ChannelAccessFailure
otbr-agent[301]: 00:00:33.798 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:84, chksum:5c0e, ecn:no, to:0xffff, sec:no, error:ChannelAccessFailure, prio:net
otbr-agent[301]: 00:00:33.798 [N] MeshForwarder-:     src:[fe80:0:0:0:541f:e88b:5b2e:6e00]:19788
otbr-agent[301]: 00:00:33.798 [N] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
otbr-agent[301]: 00:00:34.810 [N] RouterTable---: Allocate router id 42
otbr-agent[301]: 00:00:34.811 [N] Mle-----------: RLOC16 fffe -> a800
otbr-agent[301]: 00:00:34.815 [N] Mle-----------: Role detached -> leader
otbr-agent[301]: 00:00:34.816 [N] Mle-----------: Partition ID 0x4de00e9e
otbr-agent[301]: 00:00:34.850 [W] Platform------: [netif] Failed to process request#6: Unknown error -17
otbr-agent[301]: 00:00:35.077 [W] Platform------: Handle transmit done failed: ChannelAccessFailure
otbr-agent[301]: 00:00:35.078 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:96, chksum:a0c9, ecn:no, to:0xffff, sec:no, error:ChannelAccessFailure, prio:net
15

That is the correct firmware for OTBR.

16

Could you try to restart the entire host (not just ha core)?

It seems like the ff02 network is unavailable and that means no auto configuration of IPv6 can be done.
I am not sure if a restart will solve it, but it is first thing to try.

17

I restared the host several times the last few days.
How can i check the auto-config of ipv6?

HA - IP Information:

IPv4
[…]

IPv6
IP-Adresse: fe80::8ec0:272a:5565:5874/64
Methode: auto

18

The IP configuration looks like mine, but it does not list the ff02 network.
I do not know where you can see that information in HAOS. Sorry.
I know IPv6 needs that network for lots of basic features.

19

This definitly indicates a RF issue, the OTBR is not able to send a frame because the SkyConnect determine it is not OK to send right now. This is either because of interference from devices (e.g. USB 3.0 devices are known to interfere with 2.4GHz quite a bit, make sure to have any such devices/cables away from the SkyConnect), or the communication channel is just busy. E.g. Zigbee and WiFi use potentially the same or an overlapping channel. ZigBee and Wi-Fi Coexistence | MetaGeek website has a good overview of channels and how they overlap.

You can change the channel of your Thread network in the Thread configuration panel in the three dot menu behind your OpenThread Border Router.

20

Thats a good point.
I have my AccessPoint ~50cm next to SkyConnect. I will try to temporarly disconnect my AP and give it a try, as soon as I’m back home.

1 Like
21

Update:

I tried it with my Ap disconnected. No Wifi anywhere near to the Skyconnect.

But, same Error…
tried restarting the host, changing the channel… I really hope it is an harware-issue and the new one will work