Bonjour,
Mon problème
Bonjour,
Je n’arrive pas à connecter ma serrure Aqara.
Il y a des messages d’erreur dans mes logs Matter et Open Thread Border Router
Et à l’ajout de l’appareil, l’appairage échoue…
L’ipv6 a été activé sur ma box
Merci d’avance pour l’aide que vous pourrez m’apporter 
Ma configuration
System Information
| version | core-2024.10.0 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.12.4 |
| os_name | Linux |
| os_version | 6.6.46-haos |
| arch | aarch64 |
| timezone | Europe/Paris |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| HACS Data | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 2.0.1 |
| Stage | running |
| Available Repositories | 1429 |
| Downloaded Repositories | 9 |
Home Assistant Cloud
| logged_in | false |
|---|---|
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 13.1 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2024.09.1 |
| agent_version | 1.6.0 |
| docker_version | 26.1.4 |
| disk_total | 117.4 GB |
| disk_used | 15.9 GB |
| healthy | true |
| supported | true |
| host_connectivity | true |
| supervisor_connectivity | true |
| ntp_synchronized | true |
| virtualization | kvm |
| board | generic-aarch64 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Terminal & SSH (9.15.0), Mosquitto broker (6.4.1), Zigbee2MQTT (1.40.1-1), File editor (5.8.0), ESPHome (2024.9.1), Matter Server (6.5.1), OpenThread Border Router (2.11.0) |
Logs Matter Server
Add-on: Matter Server
Matter WebSocket Server for Home Assistant Matter support.
Add-on version: 6.5.1
You are running the latest version of this add-on.
System: Home Assistant OS 13.1 (aarch64 / qemuarm-64)
Home Assistant Core: 2024.10.0
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 matter-server: starting
s6-rc: info: service matter-server successfully started
s6-rc: info: service legacy-services: starting
[18:50:17] INFO: Starting Matter Server…
s6-rc: info: service legacy-services successfully started
[18:50:19] INFO: Using ‹ enp0s3 › as primary network interface.
[18:50:19] INFO: Successfully send discovery information to Home Assistant.
2024-10-03 18:50:23.852 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging…
2024-10-03 18:50:23.853 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack…
[1727974223.934863][127:127] CHIP:CTL: Setting attestation nonce to random value
[1727974223.935311][127:127] CHIP:CTL: Setting CSR nonce to random value
[1727974223.936999][127:127] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1727974223.937269][127:127] CHIP:DL: writing settings to file (/tmp/chip_kvs-IwhBPL)
[1727974223.937462][127:127] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1727974223.937866][127:127] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1727974223.938276][127:127] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1727974223.938499][127:127] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1727974223.939006][127:127] CHIP:DL: writing settings to file (/data/chip_counters.ini-sV6aBM)
[1727974223.939403][127:127] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1727974223.939537][127:127] CHIP:DL: NVS set: chip-counters/reboot-count = 9 (0x9)
[1727974223.940225][127:127] CHIP:DL: Got Ethernet interface: enp0s3
[1727974223.940650][127:127] CHIP:DL: Found the primary Ethernet interface:enp0s3
[1727974223.941740][127:127] CHIP:DL: Failed to get WiFi interface
[1727974223.941784][127:127] CHIP:DL: Failed to reset WiFi statistic counts
2024-10-03 18:50:23.942 (MainThread) INFO [chip.storage] Initializing persistent storage from file: /data/chip.json
2024-10-03 18:50:23.943 (MainThread) INFO [chip.storage] Loading configuration from /data/chip.json…
2024-10-03 18:50:24.205 (MainThread) INFO [chip.CertificateAuthority] Loading certificate authorities from storage…
2024-10-03 18:50:24.205 (MainThread) INFO [chip.CertificateAuthority] New CertificateAuthority at index 1
2024-10-03 18:50:24.207 (MainThread) INFO [chip.CertificateAuthority] Loading fabric admins from storage…
2024-10-03 18:50:24.207 (MainThread) INFO [chip.FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2024-10-03 18:50:24.208 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2024-10-03 18:50:24.210 (MainThread) INFO [matter_server.server.server] Starting the Matter Server…
2024-10-03 18:50:24.218 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).
2024-10-03 18:50:24.218 (MainThread) INFO [chip.FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags:
2024-10-03 18:50:24.440 (Dummy-2) CHIP_ERROR [chip.native.DL] [size=4][size=4][size=4]Long dispatch time: 219 ms, for event type 2
2024-10-03 18:50:24.461 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2024-10-03 18:50:24.473 (MainThread) INFO [matter_server.server.vendor_info] Loaded 248 vendors from storage.
2024-10-03 18:50:24.474 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2024-10-03 18:50:24.660 (MainThread) INFO [matter_server.server.vendor_info] Fetched 247 vendors from DCL.
2024-10-03 18:50:24.662 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
2024-10-03 18:50:24.677 (MainThread) INFO [matter_server.server.device_controller] Loaded 0 nodes from stored configuration
2024-10-03 18:50:24.695 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.
Logs OTBR
Add-on: OpenThread Border Router
OpenThread Border Router add-on
Add-on version: 2.11.0
You are running the latest version of this add-on.
System: Home Assistant OS 13.1 (aarch64 / qemuarm-64)
Home Assistant Core: 2024.10.0
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
[18:49:25] INFO: Checking /dev/ttyUSB0 identifying Home Assistant Connect ZBT-1 from Nabu Casa.
[18:49:25] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
2024-10-03 18:49:26.901 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-10-03 18:49:26.901 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-10-03 18:49:28.910 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
2024-10-03 18:49:30.030 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-10-03 18:49:30.031 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
[18:49:31] INFO: Setup OTBR firewall…
[18:49:31] INFO: Starting otbr-agent…
[NOTE]-AGENT—: Running 0.3.0-ff7227e-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://enp0s3
[NOTE]-ILS-----: Infra link selected: enp0s3
49d.18:13:44.917 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.058 [N] RoutingManager: BR ULA prefix: fdf7:293d:7341::/48 (loaded)
00:00:00.059 [N] RoutingManager: Local on-link prefix: fd5c:2ecf:7d41:14c5::/64
00:00:00.093 [N] Mle-----------: Role disabled → detached
00:00:00.109 [N] P-Netif-------: Changing interface state to up.
00:00:00.126 [W] P-Netif-------: Failed to process request#2: No such process
00:00:00.127 [W] P-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
Done
s6-rc: info: service otbr-agent-configure successfully started
[18:49:32] 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
00:00:25.453 [N] Mle-----------: RLOC16 8c00 → fffe
00:00:25.701 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:32.201 [N] RouterTable—: Allocate router id 35
00:00:32.201 [N] Mle-----------: RLOC16 fffe → 8c00
00:00:32.206 [N] Mle-----------: Role detached → leader
00:00:32.206 [N] Mle-----------: Partition ID 0xac7b4a5
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:00:34.904 [W] DuaManager----: Failed to perform next registration: NotFound