OTBR configuration + aqara u200

Configuration Matter/Thread
1

Hello,
I brought an aqara U200 smart lock. I correctly configured it using Bluetooth using the aqara home app. I would like to connect it to my home assistant installation using matter over thread. I didn’t have a thread and matter network, so I brought a ZBT-1 stick this month. But I can’t connect aqara U200 as a Matter device using the android companion app. More on this later. I suspect a misconfiguration of the OpenThread Border Router add-on.

I had some difficulties to make ZBT-1 recognized by home assistant. But now, it appears on the Settings > System > Hardware tab.

Configuration of the Home Assistant Connect ZBT-1

I think this section is unrelated to my problem, but it might help someone with this issue : the configure button of Home Assistant Connect ZBT-1 in Settings > System > Hardware did not appear.

I had trouble configure it (it did appear in the Settings > System > Hardware > All hardware as /dev/serial/by-id/usb-Nabu_Casa_Home_Assistant_Connect_ZBT-1_*, but not Settings > System > Hardware with the configure button)

  • I manually installed the OpenThread Border Router add-on, but the configuration failed with this error message:

    The radio firmware on your Home Assistant Connect ZBT-1 could not be determined. Make sure that no other integration or add-on is currently trying to communicate with the device. If you are running Home Assistant OS in a virtual machine or in Docker, please make sure that permissions are set correctly for the device.

  • I removed the OpenThread Border Router add-on
  • I manually installed the Silicon Labs Multiprotocol add-on. After this step, the configure button did appear in Hardware tab.
  • I removed the Silicon Labs Multiprotocol add-on (I don’t want multiprotocol).

Step to add aqara as matter device

  1. Now that the configure button appears in Hardware tab, I removed those to get a fresh start:
    • Integrations:
      • Thread
      • Open Thread Border Router
      • Matter
    • Add-ons:
      • Matter Server
      • OpenThread Border Router
      • Silicon Labs Multiprotocol
  2. OS reboot
  3. in Settings > System > Hardware > Home Assistant Connect ZBT-1 “configure” > Thread
    It installs and configure automatically
    • Matter Server (add-on)
    • OpenThread Border Router (add-on)
    • Matter (integration)
    • Thread (integration)
  4. in Thread integration > configure > Preferred network, there is a thread ha-thread-702f with only one border router Home Assistant OpenThread Border Router #1C16.
    I clicked on ... > Used for Android + iOS credentials
  5. on the companion app (android 14):
    Settings > Companion app > Troubleshooting > Sync Thread credentials.
    • first time popup: ✅ Added network from Home Assistant to this device
    • second time popup: ✅ Home Assistant and this device use the same network
  6. on the companion app:
    1. Settings > Devices & services > Add integration > Add Matter device > No. it’s new > Set up without qr code
    2. enter pairing code (the qr code doesn’t work) > Get Ready for setup
    3. on the aqara u200 lock, I press the Set button. the light start blinking (time 0)
    4. On the companion app: I'm ready
      1. Connecting to device… (time 5 seconds)
      2. Generating Matter credentials (time 30 seconds)
      3. Checking network connectivity to “my Wi-Fi 5G network” (time 35 seconds). Why does my Wi-Fi network is involved instead of the thread network ?
        Note: I tried with a Wi-Fi 2.4G with the same result. My android device is a tablet, without sim card, so no internet access outside the Wi-Fi.
      4. on the aqara u200 lock, the light stop blinking (time 170 seconds). Timeout ?
      5. On the companion app: (time 220 seconds)

        Can’t reach device. Make sure your phone is connected to Wi-Fi.

Logs

Matter Server (add-on) 
s6-rc: info: service matter-server successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
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: 7.0.0
 You are running the latest version of this add-on.
 System: Debian GNU/Linux 12 (bookworm)  (amd64 / qemux86-64)
 Home Assistant Core: 2025.3.3
 Home Assistant Supervisor: 2025.03.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 matter-server: starting
s6-rc: info: service matter-server successfully started
s6-rc: info: service legacy-services: starting
[10:33:51] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[10:33:51] INFO: Using 'enp172s0' as primary network interface.
[10:33:51] INFO: Successfully send discovery information to Home Assistant.
2025-03-19 10:33:53.430 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2025-03-19 10:33:53.430 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1742376833.472921][117:117] CHIP:CTL: Setting attestation nonce to random value
[1742376833.473162][117:117] CHIP:CTL: Setting CSR nonce to random value
[1742376833.474293][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1742376833.476533][117:117] CHIP:DL: Wrote settings to /tmp/chip_kvs
[1742376833.476754][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1742376833.476858][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1742376833.476906][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1742376833.479010][117:117] CHIP:DL: Wrote settings to /data/chip_counters.ini
[1742376833.479021][117:117] CHIP:DL: NVS set: chip-counters/reboot-count = 2 (0x2)
[1742376833.480300][117:117] CHIP:DL: Got Ethernet interface: enp172s0
[1742376833.481365][117:117] CHIP:DL: Found the primary Ethernet interface:enp172s0
[1742376833.483205][117:117] CHIP:DL: Failed to get WiFi interface
[1742376833.483212][117:117] CHIP:DL: Failed to reset WiFi statistic counts
2025-03-19 10:33:53.483 (MainThread) INFO [chip.storage] Initializing persistent storage from file: /data/chip.json
2025-03-19 10:33:53.483 (MainThread) INFO [chip.storage] Loading configuration from /data/chip.json...
2025-03-19 10:33:53.540 (MainThread) INFO [chip.CertificateAuthority] Loading certificate authorities from storage...
2025-03-19 10:33:53.541 (MainThread) INFO [chip.CertificateAuthority] New CertificateAuthority at index 1
2025-03-19 10:33:53.541 (MainThread) INFO [chip.CertificateAuthority] Loading fabric admins from storage...
2025-03-19 10:33:53.541 (MainThread) INFO [chip.FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2025-03-19 10:33:53.541 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2025-03-19 10:33:53.542 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2025-03-19 10:33:53.543 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).
2025-03-19 10:33:53.544 (MainThread) INFO [chip.FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2025-03-19 10:33:53.594 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to advertise records: src/inet/UDPEndPointImplSockets.cpp:421: OS Error 0x02000065: Network is unreachable
2025-03-19 10:33:53.596 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to advertise records: src/inet/UDPEndPointImplSockets.cpp:421: OS Error 0x02000065: Network is unreachable
2025-03-19 10:33:53.598 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to advertise records: src/lib/dnssd/minimal_mdns/Server.cpp:344: CHIP Error 0x00000046: No endpoint was available to send the message
Same message in loop, removed as I reached the maximum post size on the forum.
2025-03-19 10:33:53.610 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to advertise records: src/lib/dnssd/minimal_mdns/Server.cpp:344: CHIP Error 0x00000046: No endpoint was available to send the message
2025-03-19 10:33:53.615 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2025-03-19 10:33:53.618 (MainThread) INFO [matter_server.server.vendor_info] Loaded 297 vendors from storage.
2025-03-19 10:33:53.618 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2025-03-19 10:33:53.871 (MainThread) INFO [matter_server.server.vendor_info] Fetched 296 vendors from DCL.
2025-03-19 10:33:53.872 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
2025-03-19 10:33:53.875 (MainThread) INFO [matter_server.server.device_controller] Loaded 0 nodes from stored configuration
2025-03-19 10:33:53.898 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.
OpenThread Border Router (add-on) 
s6-rc: info: service mdns successfully stopped
[10:33:50] 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
[10:33:50] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Jan 14 2025 21:04:03) starting

-----------------------------------------------------------
 Add-on: OpenThread Border Router
 OpenThread Border Router add-on
-----------------------------------------------------------
 Add-on version: 2.13.0
 You are running the latest version of this add-on.
 System: Debian GNU/Linux 12 (bookworm)  (amd64 / qemux86-64)
 Home Assistant Core: 2025.3.3
 Home Assistant Supervisor: 2025.03.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
[10:33:51] INFO: Checking /dev/ttyUSB1 identifying Home Assistant Connect ZBT-1 from Nabu Casa.
[10:33:51] INFO: Starting universal-silabs-flasher with /dev/ttyUSB1
2025-03-19 10:33:51.716 debian universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=2, sdk_version='4.4.4', ezsp_version=None, ot_rcp_version='SL-OPENTHREAD/2.4.4.0_GitHub-7074a43e4' (2.4.4.0), cpc_version=None, fw_type=<FirmwareImageType.OPENTHREAD_RCP: 'openthread_rcp'>, fw_variant=None, baudrate=460800)
2025-03-19 10:33:51.716 debian universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2025-03-19 10:33:53.727 debian universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
2025-03-19 10:33:54.842 debian universal_silabs_flasher.flasher INFO Detected ApplicationType.SPINEL, version 'SL-OPENTHREAD/2.4.4.0_GitHub-7074a43e4' (2.4.4.0) at 460800 baudrate (bootloader baudrate None)
2025-03-19 10:33:54.842 debian universal_silabs_flasher.flash INFO Firmware version 'SL-OPENTHREAD/2.4.4.0_GitHub-7074a43e4' (2.4.4.0) is flashed, not re-installing
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[10:33:55] INFO: Setup OTBR firewall...
[10:33:55] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-b067e5ac-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://enp172s0
[NOTE]-ILS-----: Infra link selected: enp172s0
49d.17:03:24.744 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.046 [N] RoutingManager: BR ULA prefix: fd85:2627:3722::/48 (loaded)
00:00:00.046 [N] RoutingManager: Local on-link prefix: fdf9:4a52:3e41:f373::/64
00:00:00.093 [N] Mle-----------: Role disabled -> detached
00:00:00.238 [N] P-Netif-------: Changing interface state to up.
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-configure: starting
Done
s6-rc: info: service otbr-agent-configure successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
00:00:00.333 [W] P-Netif-------: Failed to process request#2: No such process
00:00:00.334 [W] P-Netif-------: Failed to process request#6: No such process
[10:33:55] 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: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8807:fbff:feaa:8c1a/veth4116e44/101
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8807:fbff:feaa:8c1a/veth4116e44/101
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::18e9:6ff:fedd:84a6/veth49b2ec6/102
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8807:fbff:feaa:8c1a/veth4116e44/101
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::18e9:6ff:fedd:84a6/veth49b2ec6/102
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8807:fbff:feaa:8c1a/veth4116e44/101
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8807:fbff:feaa:8c1a/veth4116e44/101
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8807:fbff:feaa:8c1a/veth4116e44/101
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::18e9:6ff:fedd:84a6/veth49b2ec6/102
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8807:fbff:feaa:8c1a/veth4116e44/101
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8807:fbff:feaa:8c1a/veth4116e44/101
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::18e9:6ff:fedd:84a6/veth49b2ec6/102
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8807:fbff:feaa:8c1a/veth4116e44/101
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::18e9:6ff:fedd:84a6/veth49b2ec6/102
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::18e9:6ff:fedd:84a6/veth49b2ec6/102
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::18e9:6ff:fedd:84a6/veth49b2ec6/102
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::18e9:6ff:fedd:84a6/veth49b2ec6/102
00:00:27.111 [N] Mle-----------: RLOC16 b400 -> fffe
00:00:27.793 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:34.293 [N] RouterTable---: Allocate router id 45
00:00:34.293 [N] Mle-----------: RLOC16 fffe -> b400
00:00:34.296 [N] Mle-----------: Role detached -> leader
00:00:34.296 [N] Mle-----------: Partition ID 0xc1051bc
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:00:38.052 [W] DuaManager----: Failed to perform next registration: NotFound
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c80d:efff:fe50:60f3/veth6fbef33/104
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c80d:efff:fe50:60f3/veth6fbef33/104
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c80d:efff:fe50:60f3/veth6fbef33/104
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c80d:efff:fe50:60f3/veth6fbef33/104
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c80d:efff:fe50:60f3/veth6fbef33/104
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c80d:efff:fe50:60f3/veth6fbef33/104
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c80d:efff:fe50:60f3/veth6fbef33/104
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::6c86:63ff:fe70:1b1b/veth7ad57b4/106
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::6c86:63ff:fe70:1b1b/veth7ad57b4/106
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::6c86:63ff:fe70:1b1b/veth7ad57b4/106
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::6c86:63ff:fe70:1b1b/veth7ad57b4/106
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::6c86:63ff:fe70:1b1b/veth7ad57b4/106
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::6c86:63ff:fe70:1b1b/veth7ad57b4/106
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7003:dff:fedf:46d9/veth2ee7602/108
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7003:dff:fedf:46d9/veth2ee7602/108
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7003:dff:fedf:46d9/veth2ee7602/108
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7003:dff:fedf:46d9/veth2ee7602/108
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7003:dff:fedf:46d9/veth2ee7602/108
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7003:dff:fedf:46d9/veth2ee7602/108
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7003:dff:fedf:46d9/veth2ee7602/108
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7003:dff:fedf:46d9/veth2ee7602/108
00:44:34.251 [W] P-RadioSpinel-: Unexpected Spinel transaction message: 3
00:44:34.251 [W] P-RadioSpinel-: Error processing response: Drop
00:56:53.173 [W] P-RadioSpinel-: Error processing result: NoAddress
00:56:53.173 [W] P-RadioSpinel-: Error waiting response: NoAddress
01:09:25.899 [W] P-RadioSpinel-: Error processing result: NoAddress
01:09:25.899 [W] P-RadioSpinel-: Error waiting response: NoAddress
01:34:20.813 [W] P-RadioSpinel-: Error processing result: NoAddress
01:34:20.813 [W] P-RadioSpinel-: Error waiting response: NoAddress

Hardware

  • ttyUSB0 /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
    ttyUSB0 is used by zigbee2mqtt. I tried to stop the add-on and disconnect ttyUSB0, but same result for my matter pairing problem.
  • ttyUSB1 /dev/serial/by-id/usb-Nabu_Casa_Home_Assistant_Connect_ZBT-1_*-if00-port0 I replaced a hexadecimal number by *. I don’t know if it is sensitive or pertinent.

Both antennas are away from my computer using USB extension cords (both antennas and computer are one meter apart).
In first pairings there was no direct line of sigh between ttyUSB1 and aqara u200.
In the last pairing attempt in the log (timestamp 01:34:20 in OpenThread Border Router logs), I moved the aqara u200 at two meters of the ttyUSB1, with a direct line of sigh. Same result.

Home assistant

What version
Core 2025.3.3
Supervisor 2025.03.3
Operating System Linux debian 6.1.0-31-amd64 x86_64 GNU/Linux
Frontend 20250306.0

Matter Server (add-on)

log_level: info
log_level_sdk: error
beta: false
enable_test_net_dcl: false

OpenThread Border Router (add-on)

device: >-
  /dev/serial/by-id/usb-Nabu_Casa_Home_Assistant_Connect_ZBT-1_*-if00-port0
baudrate: 460800
flow_control: true
autoflash_firmware: true
otbr_log_level: notice
firewall: true
nat64: false

Remarque

related links

2

Hey,
I have the same issue.
I installed HASS on a proxmox VM and get the same 'NoAddress" error after pairing.

Do you have more information in the meantime?

3

To pair any Matter device to any Matter over Thread or Matter over WiFi hub:
a) Factory reset the device
b) Add as Matter device immediately after factory reset AND before pairing with manufacturer’s app.

If these steps are not followed, adding as Matter device will fail/malfunction. Once device works with Matter, then add the device to their manufacturer’s apps. This has been my experience based on Aqara and Govee devices.

To pair Aqara lock, factory reset the lock. Open HA app on Android phone (I don’t have iPhone). Go to Devices and Add device → Matter device. Scan QR code on lock and device should be added as Matter device if OTBR is working correctly and OTBR Thread network is your preferred network. Please keep your phone near the lock during device add process. Once added as a Matter device, feel free to add to Aqara app.

If you have already programmed users/passwords/fingerprints for the lock, you will lose them.

I did this only yesterday using SLZB-06 dongle setup as OTBR in HA and Aqara U300. Worked fine. Hope this helps.

4

Hello,
Same problem here. It’s driving me crazy…
HAOS/HomeAssistant/OTBR/SLZB-06 connected over LAN.
I’m trying to find out what’s happening, I’ll keep you posted

EDIT1: I tried to factory reset the U200, it changed nothing.

5

I finally did it, but with so many steps that I don’t know which one has been useful.
Last things I did:

  • move the SLZB06 to USB
  • reconfigure OTBR to use the USB device
  • it created a new thread network !? I set it as preferred
  • I refreshed thread credentials on my phone, it didn’t work
  • I took my tablet (which I never synced cred with before), synced the creds, and adding the u200 worked.

EDIT1: I readded the U200 to aqara app, and I moved the SLZB back to ethernet, it still works