Impossible d'ajouter des appareils Matter/Thread à mon réseau Thread

Tidjy · Janvier 10, 2026, 5:27

Bonjour,

Mon problème

J’ai acquis des capteurs de porte de Ikea (MYGGBETT) qui sont Matter/Thread. J’ai donc décidé d’acquérir par la même occaz une clé Sonoff Dongle-E pour y flasher le dernier firmware OpenThread (2.4.4). Jusque là tout va bien.

Après avoir lu quelques tuto je me suis assuré que les addons Mater Server et Open Thread Border Router étaient bien installés et configurés tout comme l’intégration Thread. J’ai donc un réseau nommé ha-thread-a455 qui s’est ajouté dans l’intégration Thread. Il est ajouté en tant que réseau favoris. J’ai tenté de faire rejoindre mon capteur de porte au réseau Thread mais après avoir scanné le qr code de l’appareil, les étapes suivantes sont effectuées :

Recherche de l’appareil
Connexion à l’appareil
Création des identifiants Matter
et enfin je tombe sur l’erreur suivante :

J’ai lu sur divers fil de discussions qu’il fallait passer par l’app companon Home Assistant pour le comissioning afin de synchroniser les identifiants Thread entre le téléphone et le Home Assistant. Ce que j’ai fais en prenant le soin de supprimer les données des services Google Play pour faire les choses proprement. Après ça lorsque je tente donc la synchronisation des identifiants ça me dit bien que mon téléphone et Home Assistant sont sur le même réseau.

Cela n’a pas empêché que je ne puisse toujours pas ajouté mes capteurs de porte à mon réseau Thread avec la même précédente. J’ai même tenté de supprimer et réinstaller toutes les modules complémentaires et intégrations liées à Matter, réinitialisé mon réseau Thread mais rien n’y fait. Je suis à cours de solution.

Pour info l’IPV6 est bien activé en mode automatique dans les paramètres réseaux de Home Assistant.

Logs du module Open Thread Border Router :

-----------------------------------------------------------
 Add-on: OpenThread Border Router
 OpenThread Border Router add-on
-----------------------------------------------------------
 Add-on version: 2.15.3
 You are running the latest version of this add-on.
 System: Ubuntu 24.10  (aarch64 / raspberrypi5-64)
 Home Assistant Core: 2026.1.0
 Home Assistant Supervisor: 2026.01.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 otbr-agent: starting
[17:43:53] INFO: Setup OTBR firewall...
[17:43:54] INFO: Migrating OTBR settings if needed...
2026-01-10 17:43:54 tidjydev asyncio[226] DEBUG Using selector: EpollSelector
2026-01-10 17:43:54 tidjydev zigpy.serial[226] DEBUG Opening a serial connection to '/dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_8641d1a8bf49ef11a11bd68cff00cc63-if00-port0' (baudrate=460800, xonxoff=False, rtscts=False)
2026-01-10 17:43:54 tidjydev serialx.platforms.serial_posix[226] DEBUG Configuring serial port '/dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_8641d1a8bf49ef11a11bd68cff00cc63-if00-port0'
2026-01-10 17:43:54 tidjydev serialx.platforms.serial_posix[226] DEBUG Configuring serial port: [0, 0, 3248, 0, 4100, 4100, [b'\x03', b'\x1c', b'\x7f', b'\x15', b'\x04', 0, 0, b'\x00', b'\x11', b'\x13', b'\x1a', b'\x00', b'\x12', b'\x0f', b'\x17', b'\x16', b'\x00', b'\x00', b'\x00', b'\x00', b'\x00', b'\x00', b'\x00', b'\x00', b'\x00', b'\x00', b'\x00', b'\x00', b'\x00', b'\x00', b'\x00', b'\x00']]
2026-01-10 17:43:54 tidjydev serialx.platforms.serial_posix[226] DEBUG Setting low latency mode: True
2026-01-10 17:43:54 tidjydev serialx.platforms.serial_posix[226] DEBUG Setting modem pins: ModemPins[!dtr !rts]
2026-01-10 17:43:54 tidjydev serialx.platforms.serial_posix[226] DEBUG TIOCMBIC: 0x00000006
2026-01-10 17:43:54 tidjydev zigpy.serial[226] DEBUG Connection made: <serialx.platforms.serial_posix.PosixSerialTransport object at 0xffff97e07a10>
2026-01-10 17:43:54 tidjydev universal_silabs_flasher.spinel[226] DEBUG Sending frame SpinelFrame(header=SpinelHeader(transaction_id=0, network_link_id=0, flag=2), command_id=<CommandID.RESET: 1>, data=b'\x02')
2026-01-10 17:43:54 tidjydev universal_silabs_flasher.spinel[226] DEBUG Sending data b'~\x80\x01\x02\xea\xf0~'
2026-01-10 17:43:54 tidjydev serialx.descriptor_transport[226] DEBUG Immediately writing b'~\x80\x01\x02\xea\xf0~'
2026-01-10 17:43:54 tidjydev serialx.descriptor_transport[226] DEBUG Sent 7 of 7 bytes
2026-01-10 17:43:54 tidjydev serialx.descriptor_transport[226] DEBUG Event loop woke up reader
2026-01-10 17:43:54 tidjydev serialx.descriptor_transport[226] DEBUG Received b'~\x80\x06\x00p\xeet~'
2026-01-10 17:43:54 tidjydev universal_silabs_flasher.spinel[226] DEBUG Decoded HDLC frame: HDLCLiteFrame(data=b'\x80\x06\x00p')
2026-01-10 17:43:54 tidjydev universal_silabs_flasher.spinel[226] DEBUG Parsed frame SpinelFrame(header=SpinelHeader(transaction_id=0, network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_IS: 6>, data=b'\x00p')
2026-01-10 17:43:54 tidjydev universal_silabs_flasher.spinel[226] DEBUG Sending frame SpinelFrame(header=SpinelHeader(transaction_id=3, network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_GET: 2>, data=b'\x08')
2026-01-10 17:43:54 tidjydev universal_silabs_flasher.spinel[226] DEBUG Sending data b'~\x83\x02\x08\xbc\x9a~'
2026-01-10 17:43:54 tidjydev serialx.descriptor_transport[226] DEBUG Immediately writing b'~\x83\x02\x08\xbc\x9a~'
2026-01-10 17:43:54 tidjydev serialx.descriptor_transport[226] DEBUG Sent 7 of 7 bytes
2026-01-10 17:43:54 tidjydev serialx.descriptor_transport[226] DEBUG Event loop woke up reader
2026-01-10 17:43:54 tidjydev serialx.descriptor_transport[226] DEBUG Received b'~\x83\x06\x08\x08\xb9_\xff\xfeYD\xc6\xac\x04~'
2026-01-10 17:43:54 tidjydev universal_silabs_flasher.spinel[226] DEBUG Decoded HDLC frame: HDLCLiteFrame(data=b'\x83\x06\x08\x08\xb9_\xff\xfeYD\xc6')
2026-01-10 17:43:54 tidjydev universal_silabs_flasher.spinel[226] DEBUG Parsed frame SpinelFrame(header=SpinelHeader(transaction_id=3, network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_IS: 6>, data=b'\x08\x08\xb9_\xff\xfeYD\xc6')
2026-01-10 17:43:54 tidjydev serialx.descriptor_transport[226] DEBUG Closing at the request of the application
2026-01-10 17:43:54 tidjydev zigpy.serial[226] DEBUG Waiting for serial port to close
2026-01-10 17:43:54 tidjydev serialx.descriptor_transport[226] DEBUG Closing connection: None
2026-01-10 17:43:54 tidjydev serialx.descriptor_transport[226] DEBUG Closing file descriptor 7
2026-01-10 17:43:54 tidjydev serialx.descriptor_transport[226] DEBUG Calling protocol `connection_lost` with exc=None
2026-01-10 17:43:54 tidjydev zigpy.serial[226] DEBUG Connection lost: None
No existing settings files found, skipping
[17:43:54] 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/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_8641d1a8bf49ef11a11bd68cff00cc63-if00-port0?uart-baudrate=460800&uart-init-deassert
[NOTE]-AGENT---: Radio URL: trel://eth0
[NOTE]-ILS-----: Infra link selected: eth0
50d.09:06:46.904 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.034 [N] RoutingManager: No valid /48 BR ULA prefix found in settings, generating new one
00:00:00.038 [N] RoutingManager: BR ULA prefix: fd50:8554:fb08::/48 (generated)
00:00:00.038 [N] RoutingManager: Local on-link prefix: fdde:ad00:beef:cafe::/64
00:00:00.058 [W] P-Netif-------: Failed to process request#2: No such process
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.845 [N] RoutingManager: Local on-link prefix: fd77:fc24:d56e:daa9::/64
00:00:00.858 [N] Mle-----------: Role disabled -> detached
00:00:00.888 [N] P-Netif-------: Changing interface state to up.
00:00:00.920 [W] P-Netif-------: Failed to process request#5: No such process
[17:43: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
00:00:01.100 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
Default: mDNSCoreReceiveResponse: Received from fe80::64fd:9ff:fe00:3bcf:5353   20 f.c.b.3.0.0.e.f.f.f.9.0.d.f.4.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 F.C.B.3.0.0.E.F.F.F.9.0.D.F.4.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from fe80::2448:61ff:fe97:d057:5353   20 7.5.0.d.7.9.e.f.f.f.1.6.8.4.4.2.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 7.5.0.D.7.9.E.F.F.F.1.6.8.4.4.2.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from fe80::74d2:3ff:fe73:44cf:5353   20 f.c.4.4.3.7.e.f.f.f.3.0.2.d.4.7.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 F.C.4.4.3.7.E.F.F.F.3.0.2.D.4.7.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from fe80::442:6bff:fe8a:f826:5353   20 6.2.8.f.a.8.e.f.f.f.b.6.2.4.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 6.2.8.F.A.8.E.F.F.F.B.6.2.4.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from fe80::30ca:ddff:feeb:4962:5353   20 2.6.9.4.b.e.e.f.f.f.d.d.a.c.0.3.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 2.6.9.4.B.E.E.F.F.F.D.D.A.C.0.3.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from fe80::5083:2aff:fedc:d9d1:5353   20 1.d.9.d.c.d.e.f.f.f.a.2.3.8.0.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 1.D.9.D.C.D.E.F.F.F.A.2.3.8.0.5.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from fe80::c98:b7ff:fe0e:7fbd:5353   20 d.b.f.7.e.0.e.f.f.f.7.b.8.9.c.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 D.B.F.7.E.0.E.F.F.F.7.B.8.9.C.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from fe80::80d7:80ff:fe05:a006:5353   20 6.0.0.a.5.0.e.f.f.f.0.8.7.d.0.8.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 6.0.0.A.5.0.E.F.F.F.0.8.7.D.0.8.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from fe80::e8e8:f2ff:fed1:d220:5353   20 0.2.2.d.1.d.e.f.f.f.2.f.8.e.8.e.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 0.2.2.D.1.D.E.F.F.F.2.F.8.E.8.E.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from fe80::2455:bcff:feed:ba4c:5353   20 c.4.a.b.d.e.e.f.f.f.c.b.5.5.4.2.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 C.4.A.B.D.E.E.F.F.F.C.B.5.5.4.2.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from fe80::7cd0:20ff:feda:3815:5353   20 5.1.8.3.a.d.e.f.f.f.0.2.0.d.c.7.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 5.1.8.3.A.D.E.F.F.F.0.2.0.D.C.7.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from 172.30.32.1:5353   20 5.8.e.2.9.d.e.f.f.f.4.9.6.a.4.3.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 5.8.E.2.9.D.E.F.F.F.4.9.6.A.4.3.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from 172.30.32.1:5353   20 1.32.30.172.in-addr.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 1.32.30.172.in-addr.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from 172.17.0.1:5353   20 e.0.9.3.8.5.e.f.f.f.e.5.e.7.4.7.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 E.0.9.3.8.5.E.F.F.F.E.5.E.7.4.7.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from 172.17.0.1:5353   20 1.0.17.172.in-addr.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 1.0.17.172.in-addr.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from 2001:861:2412:4110:2760:8c28:ea75:4384:5353   20 b.0.8.1.5.b.8.b.0.7.4.8.1.d.d.6.0.1.1.4.2.1.4.2.1.6.8.0.1.0.0.2.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 B.0.8.1.5.B.8.B.0.7.4.8.1.D.D.6.0.1.1.4.2.1.4.2.1.6.8.0.1.0.0.2.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from 2001:861:2412:4110:2760:8c28:ea75:4384:5353   20 4.8.3.4.5.7.a.e.8.2.c.8.0.6.7.2.0.1.1.4.2.1.4.2.1.6.8.0.1.0.0.2.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 4.8.3.4.5.7.A.E.8.2.C.8.0.6.7.2.0.1.1.4.2.1.4.2.1.6.8.0.1.0.0.2.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from 2001:861:2412:4110:2760:8c28:ea75:4384:5353   20 0.5.6.3.e.1.8.6.5.2.4.3.4.f.4.f.0.1.1.4.2.1.4.2.1.6.8.0.1.0.0.2.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 0.5.6.3.E.1.8.6.5.2.4.3.4.F.4.F.0.1.1.4.2.1.4.2.1.6.8.0.1.0.0.2.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from 192.168.1.102:5353   20 102.1.168.192.in-addr.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 102.1.168.192.in-addr.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from 192.168.1.101:5353   20 7.7.4.c.5.4.a.7.6.7.e.8.a.d.8.1.0.1.1.4.2.1.4.2.1.6.8.0.1.0.0.2.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 7.7.4.C.5.4.A.7.6.7.E.8.A.D.8.1.0.1.1.4.2.1.4.2.1.6.8.0.1.0.0.2.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from 192.168.1.101:5353   20 101.1.168.192.in-addr.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 101.1.168.192.in-addr.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from 192.168.1.101:5353   20 6.f.3.d.9.4.b.0.f.7.0.f.3.f.e.c.0.1.1.4.2.1.4.2.1.6.8.0.1.0.0.2.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 6.F.3.D.9.4.B.0.F.7.0.F.3.F.E.C.0.1.1.4.2.1.4.2.1.6.8.0.1.0.0.2.ip6.arpa. PTR tidjydev.local.
Default: mDNSCoreReceiveResponse: Received from 192.168.1.101:5353   20 0.0.4.a.7.3.9.4.7.8.b.d.9.2.e.b.0.1.1.4.2.1.4.2.1.6.8.0.1.0.0.2.ip6.arpa. PTR tidjydev-536.local.
Default: mDNSCoreReceiveResponse: Unexpected conflict discarding   16 0.0.4.A.7.3.9.4.7.8.B.D.9.2.E.B.0.1.1.4.2.1.4.2.1.6.8.0.1.0.0.2.ip6.arpa. PTR tidjydev.local.
00:00:07.600 [N] RouterTable---: Allocate router id 58
00:00:07.600 [N] Mle-----------: RLOC16 fffe -> e800
00:00:07.602 [N] Mle-----------: Role detached -> leader
00:00:07.603 [N] Mle-----------: Partition ID 0x139b369d
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:00:09.052 [W] DuaManager----: Failed to perform next registration: NotFound

Côté Matter Server :

-----------------------------------------------------------
 Add-on: Matter Server
 Matter WebSocket Server for Home Assistant Matter support.
-----------------------------------------------------------
 Add-on version: 8.1.2
 You are running the latest version of this add-on.
 System: Ubuntu 24.10  (aarch64 / raspberrypi5-64)
 Home Assistant Core: 2026.1.0
 Home Assistant Supervisor: 2026.01.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
[17:28:41] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[17:28:43] INFO: Using 'eth0' as primary network interface.
[17:28:43] INFO: Successfully send discovery information to Home Assistant.
2026-01-10 17:28:46.188 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2026-01-10 17:28:46.188 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1768062526.231556][117:117] CHIP:CTL: Setting attestation nonce to random value
[1768062526.231921][117:117] CHIP:CTL: Setting CSR nonce to random value
[1768062526.233442][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1768062526.240044][117:117] CHIP:DL: Wrote settings to /tmp/chip_kvs
[1768062526.240283][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1768062526.241460][117:117] CHIP:DL: Wrote settings to /data/chip_factory.ini
[1768062526.241510][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1768062526.242707][117:117] CHIP:DL: Wrote settings to /data/chip_config.ini
[1768062526.242759][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1768062526.243813][117:117] CHIP:DL: Wrote settings to /data/chip_counters.ini
[1768062526.245344][117:117] CHIP:DL: Wrote settings to /data/chip_factory.ini
[1768062526.245368][117:117] CHIP:DL: NVS set: chip-factory/unique-id = "8966CE26A3CA4576"
[1768062526.246465][117:117] CHIP:DL: Wrote settings to /data/chip_factory.ini
[1768062526.246491][117:117] CHIP:DL: NVS set: chip-factory/vendor-id = 65521 (0xFFF1)
[1768062526.247700][117:117] CHIP:DL: Wrote settings to /data/chip_factory.ini
[1768062526.247723][117:117] CHIP:DL: NVS set: chip-factory/product-id = 32769 (0x8001)
[1768062526.249335][117:117] CHIP:DL: Wrote settings to /data/chip_counters.ini
[1768062526.249359][117:117] CHIP:DL: NVS set: chip-counters/reboot-count = 1 (0x1)
[1768062526.251003][117:117] CHIP:DL: Wrote settings to /data/chip_counters.ini
[1768062526.251026][117:117] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1768062526.252128][117:117] CHIP:DL: Wrote settings to /data/chip_counters.ini
[1768062526.252147][117:117] CHIP:DL: NVS set: chip-counters/boot-reason = 0 (0x0)
[1768062526.253625][117:117] CHIP:DL: Wrote settings to /data/chip_config.ini
[1768062526.253647][117:117] CHIP:DL: NVS set: chip-config/regulatory-location = 0 (0x0)
[1768062526.255179][117:117] CHIP:DL: Wrote settings to /data/chip_config.ini
[1768062526.255202][117:117] CHIP:DL: NVS set: chip-config/location-capability = 2 (0x2)
[1768062526.256277][117:117] CHIP:DL: Wrote settings to /data/chip_config.ini
[1768062526.256299][117:117] CHIP:DL: NVS set: chip-config/configuration-version = 1 (0x1)
[1768062526.256709][117:117] CHIP:DL: Got Ethernet interface: eth0
[1768062526.256973][117:117] CHIP:DL: Found the primary Ethernet interface:eth0
[1768062526.257220][117:117] CHIP:DL: Got WiFi interface: wlan0
[1768062526.261754][117:117] CHIP:DL: Found the primary WiFi interface:wlan0
[1768062526.261768][117:117] CHIP:PAF: WiFiPAF: WiFiPAFLayer::Init()
2026-01-10 17:28:46.262 (MainThread) INFO [chip.storage] Initializing persistent storage from file: /data/chip.json
2026-01-10 17:28:46.262 (MainThread) ERROR [chip.storage] [Errno 2] No such file or directory: '/data/chip.json'
2026-01-10 17:28:46.262 (MainThread) CRITICAL [chip.storage] Could not load configuration from /data/chip.json - resetting configuration...
2026-01-10 17:28:46.262 (MainThread) WARNING [chip.storage] No valid SDK configuration present - clearing out configuration
2026-01-10 17:28:46.262 (MainThread) WARNING [chip.storage] No valid REPL configuration present - clearing out configuration
2026-01-10 17:28:46.368 (MainThread) INFO [chip.CertificateAuthority] Loading certificate authorities from storage...
2026-01-10 17:28:46.369 (MainThread) INFO [chip.CertificateAuthority] New CertificateAuthority at index 1
2026-01-10 17:28:46.375 (MainThread) INFO [chip.FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2026-01-10 17:28:46.376 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2026-01-10 17:28:46.376 (MainThread) INFO [matter_server.server.server] Matter Server initialized
2026-01-10 17:28:46.376 (MainThread) INFO [matter_server.server.server] Using 'eth0' as primary interface (for link-local addresses)
2026-01-10 17:28:46.377 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2026-01-10 17:28:46.380 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetching the latest PAA root certificates from DCL.
2026-01-10 17:28:48.157 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetched 72 PAA root certificates from DCL.
2026-01-10 17:28:48.157 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetching the latest PAA root certificates from Git.
2026-01-10 17:28:48.494 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetched 2 PAA root certificates from Git.
2026-01-10 17:28:48.495 (MainThread) INFO [chip.FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2026-01-10 17:28:48.626 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 130 ms, for event type 2
2026-01-10 17:28:48.634 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2026-01-10 17:28:48.634 (MainThread) INFO [matter_server.server.vendor_info] Loaded 0 vendors from storage.
2026-01-10 17:28:48.634 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2026-01-10 17:28:48.803 (MainThread) INFO [matter_server.server.vendor_info] Fetched 385 vendors from DCL.
2026-01-10 17:28:48.803 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
2026-01-10 17:28:48.805 (MainThread) INFO [matter_server.server.device_controller] Loaded 0 nodes from stored configuration
2026-01-10 17:28:48.812 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.

Tidjy · Janvier 11, 2026, 7:28

J’etais sur une installation Home Assistant Supervised. J’ai testé sur une installation Home Assistant OS et toujours le même problème. Si quelqu’un a des idées je suis preneur

Popoff · Janvier 11, 2026, 8:14

Tu suis cette procédure ?

Tidjy · Janvier 11, 2026, 9:33

Ouis, j’ai effectué toutes ses étapes mais quelque chose bloque lors de la dernière étape. Le capteur de porte Ikea est bien détecté mais pas le border router visiblement. Pourtant il apparaît bien dans l’intégration Thread.

Tidjy · Janvier 13, 2026, 5:40

J’ai résolu mon problème avec ces capteurs de contact MYGGBETT d’Ikea. Le problème était vraiment tout bête à résoudre : Réinitialiser les capteurs. Sauf que même dans la doc d’Ikea c’était marqué nulle part comment faire. Et de toutes façons j’étais même pas sûr que le problème provenait de l’appareil en lui même. Je pensais à un problème au niveau du border router. Au final pour réinitialiser ses capteurs il faut rester appuyer sur le bouton de réveille une bonne dizaine de seconde jusqu’à ce que la led clignote 3 ou 4 fois en rouge et ensuite la led repassera en clignotement orange régulier. Auquel cas cela veut dire qu’il est repassé en mode association… C’était tout bête. Bien qu’au final, lorsque l’appareil sort de son mode d’association, on a aucun moyen de le savoir car par défaut, tant que le capteur n’est pas associé, il continue à clignoter en orange. J’appelle ça un problème de design.

A force de trop chercher les problèmes, on creuse loin pour rien alors que la solution est juste sous nos yeux.

system · Janvier 15, 2026, 5:40

Ce sujet a été automatiquement fermé après 2 jours. Aucune réponse n’est permise dorénavant.