Not able to add any Matter/Thread Device

I succesfully integrated Matter Devices via WLAN (e.g. Sonoff Smart Plug-in).
Matter devices via Thread (e.g. eve door & window) don’t work. Driving me nuts since weeks. Scanned the forum through several threads but can’t find anything. First I tried with the SkyConnect multiprotocol then I ordered a Conbee II and flashed it with the Dresden-Electronic-RCP firmware.

Seems to me there is no connection between the matter server and the OTBR.

When I try to connect the device with the HA-companion-app it says “Thread Border Router required”.

Can please anyone help me with that? Thx a lot!

Here the log from the Open Thread Border Router after starting:

[09:04:07] INFO: Web UI and REST API port are exposed, starting otbr-web.
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
[09:04:07] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Feb 29 2024 14:39:08) 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.0  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.3.0
 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
[09:04:09] INFO: USB device is missing manufacturer or product name.
[09:04:09] 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
[09:04:10] INFO: Setup OTBR firewall...
[09:04:10] INFO: Starting otbr-agent...
otbr-agent[171]: [NOTE]-AGENT---: Running 0.3.0-2279c02-dirty
otbr-agent[171]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[171]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[171]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=115200&uart-flow-control
otbr-agent[171]: [NOTE]-AGENT---: Radio URL: trel://end0
otbr-agent[171]: [NOTE]-ILS-----: Infra link selected: end0
otbr-agent[171]: 00:00:00.014 [N] RoutingManager: BR ULA prefix: fdb5:e37a:ac8e::/48 (loaded)
otbr-agent[171]: 00:00:00.014 [N] RoutingManager: Local on-link prefix: fde2:c27b:4173:fbed::/64
otbr-agent[171]: 00:00:00.104 [N] Mle-----------: Role disabled -> detached
otbr-agent[171]: 00:00:00.142 [N] Platform------: [netif] Changing interface state to up.
otbr-agent[171]: 00:00:00.160 [W] Platform------: [netif] Failed to process request#2: No such process
otbr-agent[171]: 00:00:00.161 [W] Platform------: [netif] ADD [U] fe80:0:0:0:384e:6d9b:42e1:eab5 failed (InvalidArgs)
otbr-agent[171]: 00:00:00.162 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[171]: 00:00:00.165 [W] Platform------: [netif] ADD [U] fd17:bea5:b1ae:2d0a:75c6:20f6:e9f9:c432 failed (InvalidArgs)
otbr-agent[171]: 00:00:00.166 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[171]: 00:00:00.167 [W] Platform------: [netif] ADD [U] fd17:bea5:b1ae:2d0a:0:ff:fe00:4400 failed (InvalidArgs)
otbr-agent[171]: 00:00:00.168 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[171]: 00:00:00.169 [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
s6-rc: info: service otbr-web: starting
s6-rc: info: service otbr-web successfully started
[09:04:11] INFO: Starting otbr-web...
otbr-web[259]: [INFO]-WEB-----: Running 0.3.0-2279c02-dirty
otbr-web[259]: [INFO]-WEB-----: Border router web started on wpan0
[09:04:11] INFO: Enabling NAT64.
otbr-agent[171]: 00:00:00.579 [W] Platform------: [netif] Failed to process request#7: No such process
Done
Done
Done
s6-rc: info: service otbr-agent-configure successfully started
[09:04:11] 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[171]: 00:00:28.420 [N] Mle-----------: RLOC16 4400 -> fffe
otbr-agent[171]: 00:00:28.545 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[171]: 00:00:35.045 [N] RouterTable---: Allocate router id 17
otbr-agent[171]: 00:00:35.045 [N] Mle-----------: RLOC16 fffe -> 4400
otbr-agent[171]: 00:00:35.047 [N] Mle-----------: Role detached -> leader
otbr-agent[171]: 00:00:35.048 [N] Mle-----------: Partition ID 0x3d555f3c
otbr-agent[171]: 00:00:35.138 [W] Platform------: [netif] ADD [U] fd17:bea5:b1ae:2d0a:0:ff:fe00:4400 failed (InvalidArgs)
otbr-agent[171]: 00:00:35.138 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[171]: 00:00:35.142 [W] Platform------: [netif] ADD [U] fd17:bea5:b1ae:2d0a:0:ff:fe00:fc00 failed (InvalidArgs)
otbr-agent[171]: 00:00:35.142 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[171]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
otbr-agent[171]: 00:00:35.443 [W] Platform------: [netif] ADD [U] fd17:bea5:b1ae:2d0a:0:ff:fe00:fc38 failed (InvalidArgs)
otbr-agent[171]: 00:00:35.444 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[171]: 00:00:35.447 [W] Platform------: [netif] ADD [U] fd17:bea5:b1ae:2d0a:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[171]: 00:00:35.447 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[171]: 00:00:37.550 [W] Platform------: [netif] ADD [U] fdb5:e37a:ac8e:1:e2b3:c903:242a:35e7 failed (InvalidArgs)
otbr-agent[171]: 00:00:37.550 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[171]: 00:00:45.767 [W] Platform------: [netif] ADD [U] fd17:bea5:b1ae:2d0a:0:ff:fe00:fc11 failed (InvalidArgs)
otbr-agent[171]: 00:00:45.767 [W] Platform------: [netif] Failed to process event, error:InvalidArgs

Here the log from the Matter Server after starting:

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.0  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.3.0
 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
[09:18:08] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[09:18:08] INFO: Upgrading Python Matter Server to latest pre-release
Requirement already satisfied: python-matter-server[server] in /usr/local/lib/python3.11/site-packages (5.8.1)
Collecting python-matter-server[server]
  Downloading python_matter_server-5.9.0b0-py3-none-any.whl.metadata (14 kB)
Requirement already satisfied: aiohttp in /usr/local/lib/python3.11/site-packages (from python-matter-server[server]) (3.9.3)
Requirement already satisfied: aiorun in /usr/local/lib/python3.11/site-packages (from python-matter-server[server]) (2023.7.2)
Requirement already satisfied: async-timeout in /usr/local/lib/python3.11/site-packages (from python-matter-server[server]) (4.0.3)
Requirement already satisfied: coloredlogs in /usr/local/lib/python3.11/site-packages (from python-matter-server[server]) (15.0.1)
Requirement already satisfied: dacite in /usr/local/lib/python3.11/site-packages (from python-matter-server[server]) (1.8.1)
Requirement already satisfied: orjson in /usr/local/lib/python3.11/site-packages (from python-matter-server[server]) (3.9.15)
Requirement already satisfied: home-assistant-chip-clusters==2024.2.2 in /usr/local/lib/python3.11/site-packages (from python-matter-server[server]) (2024.2.2)
Requirement already satisfied: home-assistant-chip-core==2024.2.2 in /usr/local/lib/python3.11/site-packages (from python-matter-server[server]) (2024.2.2)
Requirement already satisfied: cryptography==42.0.5 in /usr/local/lib/python3.11/site-packages (from python-matter-server[server]) (42.0.5)
Requirement already satisfied: zeroconf==0.131.0 in /usr/local/lib/python3.11/site-packages (from python-matter-server[server]) (0.131.0)
Requirement already satisfied: cffi>=1.12 in /usr/local/lib/python3.11/site-packages (from cryptography==42.0.5->python-matter-server[server]) (1.16.0)
Requirement already satisfied: aenum in /usr/local/lib/python3.11/site-packages (from home-assistant-chip-clusters==2024.2.2->python-matter-server[server]) (3.1.15)
Requirement already satisfied: construct in /usr/local/lib/python3.11/site-packages (from home-assistant-chip-core==2024.2.2->python-matter-server[server]) (2.10.70)
Requirement already satisfied: rich in /usr/local/lib/python3.11/site-packages (from home-assistant-chip-core==2024.2.2->python-matter-server[server]) (13.7.1)
Requirement already satisfied: pyyaml in /usr/local/lib/python3.11/site-packages (from home-assistant-chip-core==2024.2.2->python-matter-server[server]) (6.0.1)
Requirement already satisfied: ipdb in /usr/local/lib/python3.11/site-packages (from home-assistant-chip-core==2024.2.2->python-matter-server[server]) (0.13.13)
Requirement already satisfied: deprecation in /usr/local/lib/python3.11/site-packages (from home-assistant-chip-core==2024.2.2->python-matter-server[server]) (2.1.0)
Requirement already satisfied: ecdsa in /usr/local/lib/python3.11/site-packages (from home-assistant-chip-core==2024.2.2->python-matter-server[server]) (0.18.0)
Requirement already satisfied: ifaddr>=0.1.7 in /usr/local/lib/python3.11/site-packages (from zeroconf==0.131.0->python-matter-server[server]) (0.2.0)
Requirement already satisfied: aiosignal>=1.1.2 in /usr/local/lib/python3.11/site-packages (from aiohttp->python-matter-server[server]) (1.3.1)
Requirement already satisfied: attrs>=17.3.0 in /usr/local/lib/python3.11/site-packages (from aiohttp->python-matter-server[server]) (23.2.0)
Requirement already satisfied: frozenlist>=1.1.1 in /usr/local/lib/python3.11/site-packages (from aiohttp->python-matter-server[server]) (1.4.1)
Requirement already satisfied: multidict<7.0,>=4.5 in /usr/local/lib/python3.11/site-packages (from aiohttp->python-matter-server[server]) (6.0.5)
Requirement already satisfied: yarl<2.0,>=1.0 in /usr/local/lib/python3.11/site-packages (from aiohttp->python-matter-server[server]) (1.9.4)
Requirement already satisfied: humanfriendly>=9.1 in /usr/local/lib/python3.11/site-packages (from coloredlogs->python-matter-server[server]) (10.0)
Requirement already satisfied: pycparser in /usr/local/lib/python3.11/site-packages (from cffi>=1.12->cryptography==42.0.5->python-matter-server[server]) (2.21)
Requirement already satisfied: idna>=2.0 in /usr/local/lib/python3.11/site-packages (from yarl<2.0,>=1.0->aiohttp->python-matter-server[server]) (3.6)
Requirement already satisfied: packaging in /usr/local/lib/python3.11/site-packages (from deprecation->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (23.2)
Requirement already satisfied: six>=1.9.0 in /usr/local/lib/python3.11/site-packages (from ecdsa->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (1.16.0)
Requirement already satisfied: ipython>=7.31.1 in /usr/local/lib/python3.11/site-packages (from ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (8.22.2)
Requirement already satisfied: decorator in /usr/local/lib/python3.11/site-packages (from ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (5.1.1)
Requirement already satisfied: markdown-it-py>=2.2.0 in /usr/local/lib/python3.11/site-packages (from rich->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (3.0.0)
Requirement already satisfied: pygments<3.0.0,>=2.13.0 in /usr/local/lib/python3.11/site-packages (from rich->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (2.17.2)
Requirement already satisfied: jedi>=0.16 in /usr/local/lib/python3.11/site-packages (from ipython>=7.31.1->ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (0.19.1)
Requirement already satisfied: matplotlib-inline in /usr/local/lib/python3.11/site-packages (from ipython>=7.31.1->ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (0.1.6)
Requirement already satisfied: prompt-toolkit<3.1.0,>=3.0.41 in /usr/local/lib/python3.11/site-packages (from ipython>=7.31.1->ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (3.0.43)
Requirement already satisfied: stack-data in /usr/local/lib/python3.11/site-packages (from ipython>=7.31.1->ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (0.6.3)
Requirement already satisfied: traitlets>=5.13.0 in /usr/local/lib/python3.11/site-packages (from ipython>=7.31.1->ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (5.14.1)
Requirement already satisfied: pexpect>4.3 in /usr/local/lib/python3.11/site-packages (from ipython>=7.31.1->ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (4.9.0)
Requirement already satisfied: mdurl~=0.1 in /usr/local/lib/python3.11/site-packages (from markdown-it-py>=2.2.0->rich->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (0.1.2)
Requirement already satisfied: parso<0.9.0,>=0.8.3 in /usr/local/lib/python3.11/site-packages (from jedi>=0.16->ipython>=7.31.1->ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (0.8.3)
Requirement already satisfied: ptyprocess>=0.5 in /usr/local/lib/python3.11/site-packages (from pexpect>4.3->ipython>=7.31.1->ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (0.7.0)
Requirement already satisfied: wcwidth in /usr/local/lib/python3.11/site-packages (from prompt-toolkit<3.1.0,>=3.0.41->ipython>=7.31.1->ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (0.2.13)
Requirement already satisfied: executing>=1.2.0 in /usr/local/lib/python3.11/site-packages (from stack-data->ipython>=7.31.1->ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (2.0.1)
Requirement already satisfied: asttokens>=2.1.0 in /usr/local/lib/python3.11/site-packages (from stack-data->ipython>=7.31.1->ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (2.4.1)
Requirement already satisfied: pure-eval in /usr/local/lib/python3.11/site-packages (from stack-data->ipython>=7.31.1->ipdb->home-assistant-chip-core==2024.2.2->python-matter-server[server]) (0.2.2)
Downloading python_matter_server-5.9.0b0-py3-none-any.whl (99 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 99.6/99.6 kB 3.7 MB/s eta 0:00:00
Installing collected packages: python-matter-server
  Attempting uninstall: python-matter-server
    Found existing installation: python-matter-server 5.8.1
    Uninstalling python-matter-server-5.8.1:
      Successfully uninstalled python-matter-server-5.8.1
Successfully installed python-matter-server-5.9.0b0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

The log from the OTBR after I try to connect the device doesn’t change at all.

Here the log from the Matter Server after I try to connect the device:

[09:18:14] INFO: Using 'end0' as primary network interface.
[09:18:15] INFO: Successfully send discovery information to Home Assistant.
Reading symbols from /usr/local/bin/python...
(No debugging symbols found in /usr/local/bin/python)
Starting program: /usr/local/bin/python /usr/local/bin/matter-server --storage-path /data --port 5580 --log-level info --primary-interface end0 --fabricid 2 --vendorid 4939 --listen-address 172.30.32.1
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ff44f01e0 (LWP 243)]
[Detaching after vfork from child process 244]
2024-03-17 09:18:20 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2024-03-17 09:18:20 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1710663508.800400][240:240] CHIP:CTL: Setting attestation nonce to random value
[1710663508.800871][240:240] CHIP:CTL: Setting CSR nonce to random value
[New Thread 0x7ff10191e0 (LWP 245)]
[1710663508.803233][240:240] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1710663508.803669][240:240] CHIP:DL: writing settings to file (/tmp/chip_kvs-JRDyXn)
[1710663508.803945][240:240] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1710663508.804432][240:240] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1710663508.804825][240:240] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1710663508.805019][240:240] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1710663508.805596][240:240] CHIP:DL: writing settings to file (/data/chip_counters.ini-O2Pfcl)
[1710663508.806264][240:240] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1710663508.806311][240:240] CHIP:DL: NVS set: chip-counters/reboot-count = 41 (0x29)
[1710663508.807354][240:240] CHIP:DL: Got Ethernet interface: end0
[1710663508.807933][240:240] CHIP:DL: Found the primary Ethernet interface:end0
[1710663508.808534][240:240] CHIP:DL: Got WiFi interface: wlan0
[1710663508.808586][240:240] CHIP:DL: Failed to reset WiFi statistic counts
2024-03-17 09:18:28 (MainThread) WARNING [PersistentStorage] Initializing persistent storage from file: /data/chip.json
2024-03-17 09:18:28 (MainThread) WARNING [PersistentStorage] Loading configuration from /data/chip.json...
[New Thread 0x7ff08181e0 (LWP 246)]
2024-03-17 09:18:29 (MainThread) WARNING [CertificateAuthorityManager] Loading certificate authorities from storage...
2024-03-17 09:18:29 (MainThread) WARNING [CertificateAuthority] New CertificateAuthority at index 1
2024-03-17 09:18:29 (MainThread) WARNING [CertificateAuthority] Loading fabric admins from storage...
2024-03-17 09:18:29 (MainThread) WARNING [FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2024-03-17 09:18:29 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2024-03-17 09:18:29 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
[New Thread 0x7fe3fff1e0 (LWP 247)]
2024-03-17 09:18:29 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetching the latest PAA root certificates from DCL.
2024-03-17 09:18:30 (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-17 09:18:41 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetched 129 PAA root certificates from DCL.
2024-03-17 09:18:41 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetching the latest PAA root certificates from Git.
2024-03-17 09:18:53 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetched 90 PAA root certificates from Git.
2024-03-17 09:18:53 (MainThread) WARNING [FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2024-03-17 09:18:54 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 546 ms, for event type 2
2024-03-17 09:18:54 (MainThread) INFO [matter_server.server.device_controller] Loaded 3 nodes from stored configuration
2024-03-17 09:18:54 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2024-03-17 09:18:54 (MainThread) INFO [matter_server.server.vendor_info] Loaded 179 vendors from storage.
2024-03-17 09:18:54 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2024-03-17 09:18:54 (MainThread) INFO [matter_server.server.vendor_info] Fetched 177 vendors from DCL.
2024-03-17 09:18:54 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
2024-03-17 09:18:56 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 3 discovered on MDNS
2024-03-17 09:18:56 (MainThread) INFO [matter_server.server.device_controller.node_3] Setting-up node...
2024-03-17 09:18:56 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 15 discovered on MDNS
2024-03-17 09:18:56 (MainThread) INFO [matter_server.server.device_controller.node_15] Setting-up node...
[New Thread 0x7fe2ec41e0 (LWP 248)]
2024-03-17 09:18:58 (MainThread) INFO [matter_server.server.device_controller.node_15] Setting up attributes and events subscription.
2024-03-17 09:18:59 (MainThread) INFO [matter_server.server.device_controller.node_15] Subscription succeeded
2024-03-17 09:19:01 (MainThread) INFO [matter_server.server.device_controller.node_3] Setting up attributes and events subscription.
2024-03-17 09:19:01 (MainThread) INFO [matter_server.server.device_controller.node_3] Subscription succeeded
2024-03-17 09:19:09 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 2 discovered on MDNS
2024-03-17 09:19:09 (MainThread) INFO [matter_server.server.device_controller.node_2] Setting-up node...
2024-03-17 09:19:11 (MainThread) INFO [matter_server.server.device_controller.node_2] Setting up attributes and events subscription.
2024-03-17 09:19:12 (MainThread) INFO [matter_server.server.device_controller.node_2] Subscription succeeded
1 Like

Solved the problem by adding the device via webSocket commands (without companion app) - directly with the BT adapter on the raspberry HA server.

First connect the OTBR to the matter server (command send by browser dev-tools):

var socket = new WebSocket("ws://10.0.0.54:5580/ws");
socket.addEventListener("message", (event) => {
    console.log("Message from server ", event.data);
});

socket.addEventListener("open", (event) => {
    console.log("WebSocket is open");
    var message = {
        "message_id": "1",
        "command": "set_thread_dataset",
        "args": {
            "dataset": "0e080000000000020000000300000b35060004001fffc00208e2c27b4173cafbed0708fd17bea5b1ae2d0a0510a45ff34823c7f536ded24c37a2d83bd0030e68612d7468726561642d633961360102c9a6041048bdf2923fc3ae9c3ba5b2911568137d0c0402a0f7f8"
        }
    };
    socket.send(JSON.stringify(message));
});

Second, pair e.g. eve energy with code:

var socket = new WebSocket("ws://10.0.0.54:5580/ws");
socket.addEventListener("message", (event) => {
    console.log("Message from server ", event.data);
});


socket.addEventListener("open", (event) => {
    console.log("WebSocket is open");
    var message = {
        "message_id": "2",
        "command": "commission_with_code",
        "args": {
            "code": "03626027046"
        }
    };
    socket.send(JSON.stringify(message));
});

Afterwards I could pair the eve door sensor - because the door sensor is only a child matter device and needs the eve energy first as a leader.

See also:
[("Thread border router required" with Eve and Matter)]