Lorsque j’essaie d’ajouter mon 1er capteur Thread, j’ai un message sur mon iPhone qui me dit : « Routeur de bordure Thread requis ». Pourtant dans Home Assistant j’ai bien un Open Thread Border router en Favori.
Comment faire ?
Pistes possibles :
Le fait que j’utilise le firmware Thread only, je n’ai pas pu suivre un tuto complet, la plupart montrant la version Multiprotocol. Il me manque peut-être un truc…
Le module complémentaire OpenThread Border Router est bien démarré mais les logs semblent dire qu’il y a des choses à corriger (voir ci-desous). J’ai du mal à les interpréter.
J’ai suivi les indications ici pour ajouter le capteur : Matter (BETA) - Home Assistant, qui est bien compatible Matter / Thread. Voici le message obtenu sur mon téléphone.
Vous pouvez voir dans ma configuration :
Matter Server (6.0.0), OpenThread Border Router (2.6.0)
Configuration de mon réseau Thread
J’ai un réseau Zigbee qui fonctionne bien depuis plusieurs années. Je ne souhaitais donc pas le modifier. J’ai acheté une clé Sonoff Zigbee 3.0 avec une puce EFR32MG21 que j’ai flashé avec firwmare Thread only. La plupart des tutos utilisent un firmware Zigbee + Thread, j’ai préféré la dédiée à du Thread, ce qui est aussi recommandé ici : About firmware options – Home Assistant Yellow.
Dans Paramètres / Appareils et Services / Thread / Configurer, j’ai bien un réseau Favori
-----------------------------------------------------------
Add-on: OpenThread Border Router
OpenThread Border Router add-on
-----------------------------------------------------------
Add-on version: 2.6.0
You are running the latest version of this add-on.
System: Debian GNU/Linux 11 (bullseye) (amd64 / qemux86-64)
Home Assistant Core: 2024.5.5
Home Assistant Supervisor: 2024.05.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
[15:40:59] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[15:40:59] INFO: Setup OTBR firewall...
[15:41:00] INFO: Starting otbr-agent...
otbr-agent[168]: [NOTE]-AGENT---: Running 0.3.0-2279c02-dirty
otbr-agent[168]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[168]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[168]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=460800
otbr-agent[168]: [NOTE]-AGENT---: Radio URL: trel://enp5s0
otbr-agent[168]: [NOTE]-ILS-----: Infra link selected: enp5s0
otbr-agent[168]: 50d.19:13:40.009 [W] P-RadioSpinel-: Wait for response timeout
otbr-agent[168]: 50d.19:13:42.011 [W] P-RadioSpinel-: Wait for response timeout
otbr-agent[168]: 50d.19:13:42.011 [C] P-RadioSpinel-: Failed to communicate with RCP - no response from RCP during initialization
otbr-agent[168]: 50d.19:13:42.011 [C] P-RadioSpinel-: This is not a bug and typically due a config error (wrong URL parameters) or bad RCP image:
otbr-agent[168]: 50d.19:13:42.011 [C] P-RadioSpinel-: - Make sure RCP is running the correct firmware
otbr-agent[168]: 50d.19:13:42.011 [C] P-RadioSpinel-: - Double check the config parameters passed as `RadioURL` input
otbr-agent[168]: 50d.19:13:42.011 [C] Platform------: HandleRcpTimeout() at radio_spinel.cpp:2092: RadioSpinelNoResponse
[15:41:04] WARNING: otbr-agent exited with code 6 (by signal 0).
Chain OTBR_FORWARD_INGRESS (0 references)
target prot opt source destination
DROP all -- anywhere anywhere PKTTYPE = unicast
DROP all -- anywhere anywhere match-set otbr-ingress-deny-src src
ACCEPT all -- anywhere anywhere match-set otbr-ingress-allow-dst dst
DROP all -- anywhere anywhere PKTTYPE = unicast
ACCEPT all -- anywhere anywhere
otbr-ingress-deny-src
ipset v7.17: Set cannot be destroyed: it is in use by a kernel component
otbr-ingress-deny-src
ipset v7.17: Set cannot be destroyed: it is in use by a kernel component
otbr-ingress-deny-src
ipset v7.17: Set cannot be destroyed: it is in use by a kernel component
otbr-ingress-deny-src
ipset v7.17: Set cannot be destroyed: it is in use by a kernel component
otbr-ingress-deny-src
ipset v7.17: Set cannot be destroyed: it is in use by a kernel component
otbr-ingress-deny-src
ipset v7.17: Set cannot be destroyed: it is in use by a kernel component
otbr-ingress-deny-src
ipset v7.17: Set cannot be destroyed: it is in use by a kernel component
otbr-ingress-deny-src
ipset v7.17: Set cannot be destroyed: it is in use by a kernel component
otbr-ingress-deny-src
ipset v7.17: Set cannot be destroyed: it is in use by a kernel component
otbr-ingress-deny-src
ipset v7.17: Set cannot be destroyed: it is in use by a kernel component
otbr-ingress-deny-src
ipset v7.17: Set cannot be destroyed: it is in use by a kernel component
otbr-ingress-deny-src
ipset v7.17: Set cannot be destroyed: it is in use by a kernel component
otbr-ingress-deny-src
ipset v7.17: Set cannot be destroyed: it is in use by a kernel component
otbr-ingress-deny-src
otbr-ingress-deny-src-swap
otbr-ingress-allow-dst
otbr-ingress-allow-dst-swap
Chain OTBR_FORWARD_EGRESS (0 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
[15:41:04] INFO: OTBR firewall teardown completed.
s6-svlisten1: fatal: /run/s6-rc/servicedirs/otbr-agent failed permanently or its supervisor died
s6-rc: warning: unable to start service otbr-agent: command exited 1
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service universal-silabs-flasher: stopping
s6-rc: info: service mdns: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service universal-silabs-flasher successfully stopped
s6-rc: info: service banner: stopping
Default: mDNSResponder (Engineering Build) (Apr 26 2024 10:02:08) stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
[15:41:04] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped
je n’ai pas ma même config HW que toi, je suis en Raspberry 5 avec HAOS avec Thread seul sur une clef skyconnect; et zigbee est sur une clef sonoff à part.
mais déjà voila les logs de mon otbr quand il démarre…
[16:13:23] 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
[16:13:23] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Apr 26 2024 10:06:25) starting
-----------------------------------------------------------
Add-on: OpenThread Border Router
OpenThread Border Router add-on
-----------------------------------------------------------
Add-on version: 2.6.0
You are running the latest version of this add-on.
System: Home Assistant OS 12.3 (aarch64 / raspberrypi5-64)
Home Assistant Core: 2024.5.5
Home Assistant Supervisor: 2024.05.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
[16:13:24] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[16:13:24] INFO: Setup OTBR firewall...
[16:13:24] INFO: Starting otbr-agent...
otbr-agent[172]: [NOTE]-AGENT---: Running 0.3.0-2279c02-dirty
otbr-agent[172]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[172]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[172]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB1?uart-baudrate=460800
otbr-agent[172]: [NOTE]-AGENT---: Radio URL: trel://end0
otbr-agent[172]: [NOTE]-ILS-----: Infra link selected: end0
otbr-agent[172]: 00:00:00.046 [N] RoutingManager: BR ULA prefix: fdfb:e674:9b42::/48 (loaded)
otbr-agent[172]: 00:00:00.046 [N] RoutingManager: Local on-link prefix: fdf8:91e9:2bf8:2b4d::/64
otbr-agent[172]: 00:00:00.066 [N] Mle-----------: Role disabled -> detached
otbr-agent[172]: 00:00:00.074 [N] Platform------: [netif] Changing interface state to up.
otbr-agent[172]: 00:00:00.084 [W] Platform------: [netif] Failed to process request#2: No such process
otbr-agent[172]: 00:00:00.084 [W] Platform------: [netif] ADD [U] fe80:0:0:0:d8bc:6828:6a3:7464 failed (InvalidArgs)
otbr-agent[172]: 00:00:00.084 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[172]: 00:00:00.084 [W] Platform------: [netif] ADD [U] fd9b:f987:dca7:0:3707:8524:9c5c:ae7 failed (InvalidArgs)
otbr-agent[172]: 00:00:00.084 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[172]: 00:00:00.084 [W] Platform------: [netif] ADD [U] fd9b:f987:dca7:0:0:ff:fe00:8c00 failed (InvalidArgs)
otbr-agent[172]: 00:00:00.084 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[172]: 00:00:00.084 [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
[16:13:25] INFO: Starting otbr-web...
otbr-web[260]: [INFO]-WEB-----: Running 0.3.0-2279c02-dirty
otbr-web[260]: [INFO]-WEB-----: Border router web started on wpan0
Done
s6-rc: info: service otbr-agent-configure successfully started
[16:13:25] 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[172]: 00:00:05.271 [N] Mle-----------: Role detached -> router
otbr-agent[172]: 00:00:05.271 [N] Mle-----------: Partition ID 0x6f7cf9b3
otbr-agent[172]: 00:00:05.381 [W] Platform------: [netif] Successfully added an external route ::/0 in kernel
otbr-agent[172]: 00:00:05.405 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:62, chksum:9190, ecn:no, sec:yes, error:NoRoute, prio:net, radio:all
otbr-agent[172]: 00:00:05.405 [N] MeshForwarder-: src:[fd9b:f987:dca7:0:0:ff:fe00:8c00]:61631
otbr-agent[172]: 00:00:05.405 [N] MeshForwarder-: dst:[fd9b:f987:dca7:0:0:ff:fe00:fc00]:61631
otbr-agent[172]: 00:00:05.405 [W] Platform------: [netif] ADD [U] fd9b:f987:dca7:0:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[172]: 00:00:05.405 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[172]: 00:00:05.405 [W] Platform------: [netif] ADD [U] fdbd:4ebb:da68:1:1730:56db:262e:7f25 failed (InvalidArgs)
otbr-agent[172]: 00:00:05.405 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[172]: 00:00:07.938 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:173, chksum:24b1, ecn:no, sec:yes, prio:net, radio:all
otbr-agent[172]: 00:00:07.938 [N] MeshForwarder-: src:[fe80:0:0:0:d8bc:6828:6a3:7464]:19788
otbr-agent[172]: 00:00:07.938 [N] MeshForwarder-: dst:[ff02:0:0:0:0:0:0:1]:19788
Merci pour vos réponses. Déjà j’ai changé la clé USB Thread de port et je n’ai plus les erreurs dans les logs de démarrage (exit l’erreur no response from RCP). Cela ressemble désormais davantage aux logs de Bentou.
Je n’ai toujours pas réussi à ajouter le périphérique avec mon iPhone, j’ai l’erreur qu’il ne trouve pas le routeur de bordure.
-----------------------------------------------------------
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
[13:17:21] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[13:17:21] INFO: Setup OTBR firewall...
[13:17:21] INFO: Starting otbr-agent...
otbr-agent[173]: [NOTE]-AGENT---: Running 0.3.0-2279c02-dirty
otbr-agent[173]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[173]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[173]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=460800
otbr-agent[173]: [NOTE]-AGENT---: Radio URL: trel://enp5s0
otbr-agent[173]: [NOTE]-ILS-----: Infra link selected: enp5s0
otbr-agent[173]: 00:00:00.021 [N] RoutingManager: BR ULA prefix: fd61:44:b5e6::/48 (loaded)
otbr-agent[173]: 00:00:00.021 [N] RoutingManager: Local on-link prefix: fdda:10d8:41fe:51bc::/64
otbr-agent[173]: 00:00:00.032 [N] Mle-----------: Role disabled -> detached
otbr-agent[173]: 00:00:00.045 [N] Platform------: [netif] Changing interface state to up.
otbr-agent[173]: 00:00:00.053 [W] Platform------: [netif] Failed to process request#2: No such process
otbr-agent[173]: 00:00:00.054 [W] Platform------: [netif] ADD [U] fe80:0:0:0:89d:6189:d124:f1e3 failed (InvalidArgs)
otbr-agent[173]: 00:00:00.054 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[173]: 00:00:00.054 [W] Platform------: [netif] ADD [U] fdb7:913d:e74b:4e46:a66e:c44c:8c74:eb23 failed (InvalidArgs)
otbr-agent[173]: 00:00:00.054 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[173]: 00:00:00.054 [W] Platform------: [netif] ADD [U] fdb7:913d:e74b:4e46:0:ff:fe00:f400 failed (InvalidArgs)
otbr-agent[173]: 00:00:00.054 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[173]: 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
s6-rc: info: service otbr-web: starting
s6-rc: info: service otbr-web successfully started
[13:17:21] 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
Done
s6-rc: info: service otbr-agent-configure successfully started
[13:17:22] 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
Mon Matter serveur est bien démarré sans erreurs dans les logs.
Par contre c’est vrai que dans les logs il me met radio URL = /dev/ttyACM0
alors que j’ai choisi /dev/serial/by-id/usb… dans la config. Je ne sais pas si ça a un lien mais l’erreur ne semble plus avec le device.
Si vous voyez une erreur potentielle (comme l’option du firewall je ne sais pas l’impact) :
# Pour vérifier les logs du service OTBR
sudo journalctl -u otbr-agent
-- Journal begins at Fri 2024-06-07 18:56:31 CEST, ends at Fri 2024-06-07 19:03:43 CEST. --
-- No entries --
Je n’ai pas non plus de logs sur le Matter Server.
Quelqu’un a déjà rencontré ce type d’erreur ?
Je peux essayer de tout supprimer et reprendre la config de 0.
Bonjour,
J’ai eu le même problème a part que j’étais sous android.
J’ai trouvé sur un forum qu’il fallait aller dans l’application Companion, puis paramètres, puis Application Companion, Dépannage et cliquer su Synchroniser les identifiants Thread.
Merci pour ton retour. Il me semble avoir lu ça aussi quelque part mais malheureusement sur mon iPhone quand je vais sur cette page elle est vide.
J’ai essayé de réinstaller l’app mais même comportement.
J’ai fait le test avec Home Assistant OS sur une VM, en installant uniquement les addons Thread et Matter mais j’ai le même problème, impossible d’ajouter le périphérique j’ai une erreur « Routeur de bordure Thread requis » alors qu’il me semble pourtant bien qu’il est présent :
Bonjour,
Avez vous eu une avancée depuis ?
Je viens d’ajouter une clé sonoff avec de dernier firmware Thread, suivi toutes les procédures et même soucis, impossible d’ajouter mon périphérique via mon iphone…
Bonjour @ncdgtl ,
Malheureusement non je ne me suis pas repenché sur le sujet.
Vu que j’ai déjà pas mal de trucs sur mon HA je reste dans l’idée de mettre ça sur une VM « propre » pour voir si c’est lié à un quelconque conflit.
Je posterai ici si j’ai du nouveau.
Bonjour à tous, et un grand merci @DavidElbe pour le tuto de dépannage. J’ai pu sans problème installer ma prise Eve energy et mon bulb Nanoleaf sur une VM syr Syno et Androïd.
