Can't connect Matter over Thread devices

Configuration Matter/Thread
,
1

Hello,

I am having trouble connecting my Nanoleaf Essentials LED strip, Eve Smart Switch or smart window sensors with Home Assistant.

When I go to connect, previously the screen stuck on “checking network connection” (no idea if this is the exact translation, but after the last update I get the message "cannot connect to (the name of my Thread Router).

What have I already tried?

  • Other device to pair;
  • Google Play Services data removed;
  • Google Home reinstalled;
  • Clean install of Home Assistant :frowning: .

So far nothing has helped, that’s why I created this topic. I hope you can help me further.

Information:

  • Home Assistant OS in Proxmox VM;
  • Matter Server 6.3.1 (latest version at time of writing);
  • OpenThread Border Router 2.9.0 (latest version at time of writing);
  • Thread integration;
  • Matter (BETA);
  • SkyConnect USB.

I’m not running the multiprotocol version, only Thread.

Logs

Matter Server Logs 
2024-07-22 13:08:22.900 (MainThread) WARNING [PersistentStorage] Initializing persistent storage from file: /data/chip.json
2024-07-22 13:08:22.901 (MainThread) WARNING [PersistentStorage] Loading configuration from /data/chip.json...
2024-07-22 13:08:22.947 (MainThread) WARNING [CertificateAuthorityManager] Loading certificate authorities from storage...
2024-07-22 13:08:22.947 (MainThread) WARNING [CertificateAuthority] New CertificateAuthority at index 1
2024-07-22 13:08:22.948 (MainThread) WARNING [CertificateAuthority] Loading fabric admins from storage...
2024-07-22 13:08:22.948 (MainThread) WARNING [FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2024-07-22 13:08:22.948 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2024-07-22 13:08:22.948 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2024-07-22 13:08:22.950 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).
2024-07-22 13:08:22.950 (MainThread) WARNING [FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2024-07-22 13:08:22.992 (MainThread) INFO [matter_server.server.device_controller] Loaded 0 nodes from stored configuration
2024-07-22 13:08:22.996 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2024-07-22 13:08:22.998 (MainThread) INFO [matter_server.server.vendor_info] Loaded 226 vendors from storage.
2024-07-22 13:08:22.998 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2024-07-22 13:08:23.179 (MainThread) INFO [matter_server.server.vendor_info] Fetched 224 vendors from DCL.
2024-07-22 13:08:23.179 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
OTBR Logs 
00:00:36.589 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:00:57.530 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:01:22.152 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:02:00.548 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:02:09.140 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:02:18.862 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:02:32.344 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:02:46.548 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:02:57.083 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:03:09.971 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:03:20.261 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:03:32.178 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:03:47.746 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:03:57.738 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:04:12.785 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:04:24.806 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
00:04:36.490 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure

If I have forgotten to mention something, please let me know and I will add it to this post.

Thank you very much in advance for the help :slight_smile:

2

This for sure is a problem. I would suggest checking the early part of the OTBR Log, to see what firmware it thinks is running on the SkyConnect.

ChannelAccessFailure generally means the SkyConnect is trying to send a packet over the radio, and it waits for no RF activity in order to “gain access to the RF channel” but here it can’t due to too much RF activity on that particular channel/frequency. It could be OTBR is simply using a crowded channel, perhaps used by WiFi.

3

Thank you for your quick response!

I restarted the add-on, and this shows up in the logs:

[20:44:35] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Jul  2 2024 09:04:20) starting
-----------------------------------------------------------

 Add-on: OpenThread Border Router
 OpenThread Border Router add-on
-----------------------------------------------------------
 Add-on version: 2.9.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 12.4  (amd64 / qemux86-64)
 Home Assistant Core: 2024.7.3
 Home Assistant Supervisor: 2024.06.2
-----------------------------------------------------------
 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:44:36] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[20:44:36] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
2024-07-24 20:44:36.446 homeassistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.4.0', 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-07-24 20:44:36.446 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-07-24 20:44:38.453 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
2024-07-24 20:44:39.564 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-07-24 20:44:39.564 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:44:39] INFO: Setup OTBR firewall...
[20:44:39] 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:44:40] INFO: Successfully sent discovery information to Home Assistant.
4

OK… That flash type/version is the same as mine.

5

I solved the problem, finally.

In Proxmox I had linked the USB port (“Use USB port”). I changed this to “Use Vendor ID/Device ID”, now the Skyconnect works properly.

1 Like