So, nach der kompletten Deinstallation von Matter/OTBR/Thread und Entfernung aller Thread-Hardware (SkyConnect mit Thread-only und dem ConBee II mit Thread-FW) und anschließendem Neustart von HA incl. Hardware habe ich alles neu Installiert.
Addon: Matter-Server, OpenThreadBorderRouter
Integrationen: Matter (beta), OpenThreadBorderRouter, Thread
Log-Matter-Server:
s6-rc: info: service s6rc-oneshot-runner: starting
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
-----------------------------------------------------------
Add-on: Matter Server
Matter WebSocket Server for Home Assistant Matter support.
-----------------------------------------------------------
Add-on version: 5.4.1
You are running the latest version of this add-on.
System: Home Assistant OS 12.1 (amd64 / generic-x86-64)
Home Assistant Core: 2024.3.1
Home Assistant Supervisor: 2024.03.0
-----------------------------------------------------------
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 matter-server: starting
s6-rc: info: service matter-server successfully started
s6-rc: info: service legacy-services: starting
[14:08:46] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[14:08:46] INFO: Using 'enp0s31f6' as primary network interface.
[14:08:47] INFO: Successfully send discovery information to Home Assistant.
2024-03-15 14:08:48 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2024-03-15 14:08:48 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1710508128.483453][126:126] CHIP:CTL: Setting attestation nonce to random value
[1710508128.483697][126:126] CHIP:CTL: Setting CSR nonce to random value
[1710508128.484449][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1710508128.484541][126:126] CHIP:DL: writing settings to file (/tmp/chip_kvs-olsTqH)
[1710508128.484602][126:126] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1710508128.484803][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1710508128.484845][126:126] CHIP:DL: writing settings to file (/data/chip_factory.ini-Fz2RHK)
[1710508128.484882][126:126] CHIP:DL: renamed tmp file to file (/data/chip_factory.ini)
[1710508128.484903][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1710508128.484936][126:126] CHIP:DL: writing settings to file (/data/chip_config.ini-zfvHJJ)
[1710508128.484971][126:126] CHIP:DL: renamed tmp file to file (/data/chip_config.ini)
[1710508128.484989][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1710508128.485026][126:126] CHIP:DL: writing settings to file (/data/chip_counters.ini-63BKaH)
[1710508128.485062][126:126] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1710508128.485299][126:126] CHIP:DL: writing settings to file (/data/chip_factory.ini-H7zXwL)
[1710508128.485413][126:126] CHIP:DL: renamed tmp file to file (/data/chip_factory.ini)
[1710508128.485481][126:126] CHIP:DL: NVS set: chip-factory/unique-id = "AACF34F9955A0E65"
[1710508128.485548][126:126] CHIP:DL: writing settings to file (/data/chip_factory.ini-22xwkL)
[1710508128.485654][126:126] CHIP:DL: renamed tmp file to file (/data/chip_factory.ini)
[1710508128.485666][126:126] CHIP:DL: NVS set: chip-factory/vendor-id = 65521 (0xFFF1)
[1710508128.485709][126:126] CHIP:DL: writing settings to file (/data/chip_factory.ini-AI7aUH)
[1710508128.485802][126:126] CHIP:DL: renamed tmp file to file (/data/chip_factory.ini)
[1710508128.485814][126:126] CHIP:DL: NVS set: chip-factory/product-id = 32769 (0x8001)
[1710508128.485856][126:126] CHIP:DL: writing settings to file (/data/chip_counters.ini-lOZsnK)
[1710508128.485930][126:126] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1710508128.485941][126:126] CHIP:DL: NVS set: chip-counters/reboot-count = 1 (0x1)
[1710508128.485982][126:126] CHIP:DL: writing settings to file (/data/chip_counters.ini-fq3wdI)
[1710508128.486069][126:126] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1710508128.486079][126:126] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1710508128.486119][126:126] CHIP:DL: writing settings to file (/data/chip_counters.ini-YAo8UJ)
[1710508128.486209][126:126] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1710508128.486220][126:126] CHIP:DL: NVS set: chip-counters/boot-reason = 0 (0x0)
[1710508128.486260][126:126] CHIP:DL: writing settings to file (/data/chip_config.ini-7uQZuJ)
[1710508128.486340][126:126] CHIP:DL: renamed tmp file to file (/data/chip_config.ini)
[1710508128.486352][126:126] CHIP:DL: NVS set: chip-config/regulatory-location = 0 (0x0)
[1710508128.486392][126:126] CHIP:DL: writing settings to file (/data/chip_config.ini-yHFvlI)
[1710508128.486479][126:126] CHIP:DL: renamed tmp file to file (/data/chip_config.ini)
[1710508128.486491][126:126] CHIP:DL: NVS set: chip-config/location-capability = 2 (0x2)
[1710508128.486790][126:126] CHIP:DL: Got Ethernet interface: enp0s31f6
[1710508128.486992][126:126] CHIP:DL: Found the primary Ethernet interface:enp0s31f6
[1710508128.487505][126:126] CHIP:DL: Failed to get WiFi interface
[1710508128.487513][126:126] CHIP:DL: Failed to reset WiFi statistic counts
2024-03-15 14:08:48 (MainThread) WARNING [PersistentStorage] Initializing persistent storage from file: /data/chip.json
2024-03-15 14:08:48 (MainThread) ERROR [root] [Errno 2] No such file or directory: '/data/chip.json'
2024-03-15 14:08:48 (MainThread) CRITICAL [root] Could not load configuration from /data/chip.json - resetting configuration...
2024-03-15 14:08:48 (MainThread) WARNING [root] No valid SDK configuration present - clearing out configuration
2024-03-15 14:08:48 (MainThread) WARNING [root] No valid REPL configuration present - clearing out configuration
2024-03-15 14:08:48 (MainThread) WARNING [CertificateAuthorityManager] Loading certificate authorities from storage...
2024-03-15 14:08:48 (MainThread) WARNING [CertificateAuthority] New CertificateAuthority at index 1
2024-03-15 14:08:48 (MainThread) WARNING [FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2024-03-15 14:08:48 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2024-03-15 14:08:48 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2024-03-15 14:08:48 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetching the latest PAA root certificates from DCL.
2024-03-15 14:08:49 (ThreadPoolExecutor-0_0) WARNING [py.warnings] /usr/local/lib/python3.11/concurrent/futures/thread.py:58: CryptographyDeprecationWarning: The parsed certificate contains a NULL parameter value in its signature algorithm parameters. This is invalid and will be rejected in a future version of cryptography. If this certificate was created via Java, please upgrade to JDK21+ or the latest JDK11/17 once a fix is issued. If this certificate was created in some other fashion please report the issue to the cryptography issue tracker. See https://github.com/pyca/cryptography/issues/8996 and https://github.com/pyca/cryptography/issues/9253 for more details.
result = self.fn(*self.args, **self.kwargs)
2024-03-15 14:09:00 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetched 129 PAA root certificates from DCL.
2024-03-15 14:09:00 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetching the latest PAA root certificates from Git.
2024-03-15 14:09:02 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetched 90 PAA root certificates from Git.
2024-03-15 14:09:02 (MainThread) WARNING [FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2024-03-15 14:09:03 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 209 ms, for event type 2
2024-03-15 14:09:03 (MainThread) INFO [matter_server.server.device_controller] Loaded 0 nodes from stored configuration
2024-03-15 14:09:03 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2024-03-15 14:09:03 (MainThread) INFO [matter_server.server.vendor_info] Loaded 0 vendors from storage.
2024-03-15 14:09:03 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2024-03-15 14:09:03 (MainThread) INFO [matter_server.server.vendor_info] Fetched 177 vendors from DCL.
2024-03-15 14:09:03 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
da steht m.M.n. nichts auffälliges drin.
Die Matter-Integration sieht gut aus (leider noch keine Geräte 
):
Die OTBR-Integration auch:
und dann noch die Thread-Integration:
und jetzt das “Problemkind”, die Log’s des OTBR-Addon’s (mit ConBee II):
[11:04:31] 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
[11:04:31] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Feb 29 2024 14:34:55) starting
-----------------------------------------------------------
Add-on: OpenThread Border Router
OpenThread Border Router add-on
-----------------------------------------------------------
Add-on version: 2.5.0
You are running the latest version of this add-on.
System: Home Assistant OS 12.1 (amd64 / generic-x86-64)
Home Assistant Core: 2024.3.1
Home Assistant Supervisor: 2024.03.0
-----------------------------------------------------------
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:04:32] INFO: Checking /dev/ttyACM0 identifying xHCI Host Controller from Linux 6.6.20-haos xhci-hcd.
[11:04:32] WARNING: No firmware found for the selected device, assuming firmware is installed.
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[11:04:32] INFO: Setup OTBR firewall...
[11:04:32] INFO: Starting otbr-agent...
otbr-agent[170]: [NOTE]-AGENT---: Running 0.3.0-2279c02-dirty
otbr-agent[170]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[170]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[170]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=115200&uart-flow-control
otbr-agent[170]: [NOTE]-AGENT---: Radio URL: trel://enp0s31f6
otbr-agent[170]: [NOTE]-ILS-----: Infra link selected: enp0s31f6
otbr-agent[170]: 00:00:00.011 [N] RoutingManager: BR ULA prefix: fdc7:1570:d817::/48 (loaded)
otbr-agent[170]: 00:00:00.011 [N] RoutingManager: Local on-link prefix: fd77:56c5:b5d1:30f2::/64
otbr-agent[170]: 00:00:00.034 [N] Mle-----------: Role disabled -> detached
otbr-agent[170]: 00:00:00.044 [N] Platform------: [netif] Changing interface state to up.
otbr-agent[170]: 00:00:00.053 [W] Platform------: [netif] Failed to process request#2: No such process
otbr-agent[170]: 00:00:00.053 [W] Platform------: [netif] ADD [U] fe80:0:0:0:ac1c:3af4:bc1c:61ae failed (InvalidArgs)
otbr-agent[170]: 00:00:00.053 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[170]: 00:00:00.053 [W] Platform------: [netif] ADD [U] fd23:8714:4d49:72f9:b551:cd06:851e:4a09 failed (InvalidArgs)
otbr-agent[170]: 00:00:00.053 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[170]: 00:00:00.053 [W] Platform------: [netif] ADD [U] fd23:8714:4d49:72f9:0:ff:fe00:2800 failed (InvalidArgs)
otbr-agent[170]: 00:00:00.054 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[170]: 00:00:00.054 [W] Platform------: [netif] Failed to process request#6: No such process
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
[11:04:33] INFO: Enabling NAT64.
Done
otbr-agent[170]: 00:00:00.407 [W] Platform------: [netif] Failed to process request#7: No such process
Done
Done
s6-rc: info: service otbr-agent-configure successfully started
[11:04:33] 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
otbr-agent[170]: 00:00:24.745 [N] Mle-----------: RLOC16 2800 -> fffe
otbr-agent[170]: 00:00:24.903 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[170]: 00:00:31.403 [N] RouterTable---: Allocate router id 10
otbr-agent[170]: 00:00:31.403 [N] Mle-----------: RLOC16 fffe -> 2800
otbr-agent[170]: 00:00:31.404 [N] Mle-----------: Role detached -> leader
otbr-agent[170]: 00:00:31.404 [N] Mle-----------: Partition ID 0x9acd63
otbr-agent[170]: 00:00:31.433 [W] Platform------: [netif] ADD [U] fd23:8714:4d49:72f9:0:ff:fe00:2800 failed (InvalidArgs)
otbr-agent[170]: 00:00:31.433 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[170]: 00:00:31.433 [W] Platform------: [netif] ADD [U] fd23:8714:4d49:72f9:0:ff:fe00:fc00 failed (InvalidArgs)
otbr-agent[170]: 00:00:31.433 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[170]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
otbr-agent[170]: 00:00:32.373 [W] Platform------: [netif] ADD [U] fd23:8714:4d49:72f9:0:ff:fe00:fc38 failed (InvalidArgs)
otbr-agent[170]: 00:00:32.373 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[170]: 00:00:32.374 [W] Platform------: [netif] ADD [U] fd23:8714:4d49:72f9:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[170]: 00:00:32.374 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[170]: 00:00:33.845 [W] Platform------: [netif] ADD [U] fdc7:1570:d817:1:e140:c455:cf33:122b failed (InvalidArgs)
otbr-agent[170]: 00:00:33.845 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[170]: 00:00:43.745 [W] Platform------: [netif] ADD [U] fd23:8714:4d49:72f9:0:ff:fe00:fc11 failed (InvalidArgs)
otbr-agent[170]: 00:00:43.745 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[170]: 01:07:23.393 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
otbr-agent[170]: 01:21:43.761 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
otbr-agent[170]: 02:21:20.585 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
otbr-agent[170]: 02:40:18.312 [W] P-RadioSpinel-: Handle transmit done failed: ChannelAccessFailure
Das Fehlerbild des OTBR mit dem SkyConnect sieht ähnlich aus, deshalb habe ich auf GitHub dazu mal ein Issue aufgemacht (s.o.).
