Bonsoir
Me voila de retour.
Avec vos conseils j’ai acheté :
SONOFF - Clé USB Zigbee 3.0 + antenne externe (V2) Réf: ZBDONGLE-E
Je me lance dans l’installation dans de HA sur mon Nas.
Je rencontre a nouveau un probleme, j’ai besoin de vous.
La config du NAS DSM 7.1
Dans le centre de paquet : Rien !!!
Pas de docker
Pas de Container Manager
Pas de Virtual Machine Manager
Comment faire ?
Bonjour
Tu as un DS215+ apparemment
Pour docker il faut un processeur intel ce qui n’est pas le cas de ton NAS
Edit: Je nuance, il y a maintenant quelques nas équipés de processeurs ARM compatibles, mais sur le DS215+ DDR3 1GB je ne le vois pas dans la liste mais de toute façon RAM 1GB c’est plus que juste
Liste des NAS compatibles
Je crois que je vais me tourner vers une box nabu casa afin d’être sur HA.
et donc finalement la clé ne va plus me servir.
Je vais donc prendre les produits suivants pour mon projet :
PS : J’ai une clé SONOFF a vendre 
Bonjour
J’ai tout reçu sauf mon Raspberry COM 4. 2 commandes avorter chez mouser 
Pensez vous qu’il soit judicieux de passer Raspberry com 5.
Es ce qu’il sera être supporter par la yellow ?
Bonjour
Vu ce matin justement
Je vais garder l’option CM4, car je suis newbie
Hello, c’est juste pour vous informer j’ai tout le matériel on dirait « y a plus k’a ».
Vous avez des recommandations avant que je commence l’installation ?
Bonsoir,
Installation matériel ok et logiciel Raspberry pi 
Démarrage de homeassistant
Par contre les ennuies semblent commencer :http://homeassistant.local:8123/
j’ai procéder à la désinstallation de ZHA pour mettre zigbee2mqtt
et la :
j’ai fait la mise a jour de l’adaptateur ember
découvertes j’ai ceci :
ai je raté une étape ?
euh la ça parle de multiprotocol
il faut installer un firmware 7.4.x en 115000 bauds pour ton dongle
tu p eux mettre le log aussi de Z2M par contre de tete rtscts doit etre sur false
par contre le multiprocol est abandonné ta video est obsolète
il faut flasher un firmware adéquat pour ember et configurer correctement
et faire un post dédié a ton problème
C’est bien dommage merci je m’en occupe demain.
Bonjour @franck1872,
L’add-on Silicon Labs Multiprotocol c’était simplement pour mettre à jour ton dongle ?
Si oui, je présume que tu peux le désinstaller une fois la MAJ faite.
Il te faudra également ignorer l’intégration découverte Zigbee Home Automation (la dernière dans ta liste) car elle fera conflit avec ton installation de Z2M.
Je te conseille le tuto du forum pour l’installation.
au contraire c’etait un très mauvaise idée
Le flash s’est bien passé ?
Ton serveur MQTT est bien actif ?
J’ai fait la procédure sur la yellow comme toi il y a 3 jours maintenant et tout s’est bien passé.
Pour le flash j’ai mis ca :
Après le flash tu as bien cette ligne à la fin des logs ?
`
INFO: universal-silabs-flasher-up script exited with code 0
`
Côté Z2M :
Et normalement avec ça, ca démarre.
ci dessous le journal de :
Silicon labs mulltiprotocol
Add-on: Silicon Labs Multiprotocol
Zigbee and OpenThread multiprotocol add-on
-----------------------------------------------------------
Add-on version: 2.4.5
You are running the latest version of this add-on.
System: Home Assistant OS 14.0 (aarch64 / yellow)
Home Assistant Core: 2024.12.1
Home Assistant Supervisor: 2024.11.4
-----------------------------------------------------------
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:11:45] INFO: Detected Home Assistant Yellow
[10:11:45] INFO: Starting universal-silabs-flasher with /dev/ttyAMA1
2024-12-08 10:11:47.130 homeassistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.3.1', ezsp_version='7.3.1.0', ot_rcp_version='SL-OPENTHREAD/2.3.1.0_GitHub-e6df00dd6' (2.3.1.0), cpc_version='4.3.1-4f7f9e99-dirty-e3b0c442' (4.3.1), fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>, baudrate=460800)
2024-12-08 10:11:47.131 homeassistant universal_silabs_flasher.flash INFO The '--yellow-gpio-reset' flag is deprecated. Use '--bootloader-reset' instead, see --help for details.
2024-12-08 10:11:47.131 homeassistant universal_silabs_flasher.flasher INFO Triggering yellow bootloader
2024-12-08 10:11:47.435 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-12-08 10:11:47.545 homeassistant universal_silabs_flasher.flasher INFO Launched application from bootloader
2024-12-08 10:11:48.548 homeassistant universal_silabs_flasher.flasher INFO Detected bootloader version '2.0.1'
2024-12-08 10:11:48.549 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2024-12-08 10:11:48.565 homeassistant universal_silabs_flasher.flasher INFO Detected ApplicationType.CPC, version '4.3.1-4f7f9e99-dirty-e3b0c442' (4.3.1) at 460800 baudrate (bootloader baudrate 115200)
2024-12-08 10:11:48.565 homeassistant universal_silabs_flasher.flash INFO Firmware version '4.3.1-4f7f9e99-dirty-e3b0c442' (4.3.1) is flashed, not re-installing
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service cpcd-config: starting
[10:11:49] INFO: Using known baudrate of 460800 for cpcd!
[10:11:49] INFO: Generating cpcd configuration.
s6-rc: info: service cpcd-config successfully started
s6-rc: info: service cpcd: starting
[10:11:50] INFO: Starting cpcd...
WARNING in function 'main' in file /usr/src/cpc-daemon/main.c at line #186 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
s6-rc: info: service cpcd successfully started
s6-rc: info: service zigbeed: starting
s6-rc: info: service otbr-agent: starting
s6-rc: info: service zigbeed successfully started
[10:11:51] INFO: Starting zigbeed...
[10:11:50:353219] Info : [CPCd v4.3.1.0] [Library API v3] [RCP Protocol v4]
[10:11:50:353335] Info : Git commit: 133b29678b3d0bc7578e098d2f46b4d5bcd2ebb4 / branch:
[10:11:50:353339] Info : Sources hash: ff8300587e7e4ab1def7a89a272c0baef32f9eb3bff9b0ba06b94e655d652367
[10:11:50:353354] WARNING : In function 'main' in file /usr/src/cpc-daemon/main.c at line #186 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
[10:11:50:353387] Info : Reading cli arguments
[10:11:50:353394] Info : /usr/local/bin/cpcd
[10:11:50:355376] Info : Reading configuration
[10:11:50:355396] Info : file_path = /usr/local/etc/cpcd.conf
[10:11:50:355400] Info : instance_name = cpcd_0
[10:11:50:355403] Info : socket_folder = /dev/shm
[10:11:50:355406] Info : operation_mode = MODE_NORMAL
[10:11:50:355409] Info : use_encryption = false
[10:11:50:355412] Info : binding_key_file = /etc/binding-key.key
[10:11:50:355415] Info : stdout_tracing = false
[10:11:50:355418] Info : file_tracing = false
[10:11:50:355420] Info : lttng_tracing = false
[10:11:50:355423] Info : enable_frame_trace = false
[10:11:50:355426] Info : traces_folder = /dev/shm/cpcd-traces
[10:11:50:355428] Info : bus = UART
[10:11:50:355431] Info : uart_baudrate = 460800
[10:11:50:355434] Info : uart_hardflow = true
[10:11:50:355437] Info : uart_file = /dev/ttyAMA1
[10:11:50:355440] Info : fu_recovery_pins_enabled = false
[10:11:50:355444] Info : fu_connect_to_bootloader = false
[10:11:50:355446] Info : fu_enter_bootloader = false
[10:11:50:355449] Info : restart_cpcd = false
[10:11:50:355452] Info : application_version_validation = false
[10:11:50:355455] Info : print_secondary_versions_and_exit = false
[10:11:50:355457] Info : use_noop_keep_alive = false
[10:11:50:355460] Info : reset_sequence = true
[10:11:50:355462] Info : stats_interval = 0
[10:11:50:355465] Info : rlimit_nofile = 2000
[10:11:50:355469] Info : ENCRYPTION IS DISABLED
[10:11:50:355471] Info : Starting daemon in normal mode
[10:11:50:366622] Info : Connecting to Secondary...
[10:11:50:440324] Info : RX capability is 256 bytes
[10:11:50:440353] Info : Connected to Secondary
[10:11:50:441437] Info : Secondary Protocol v4
[10:11:50:444015] Info : Secondary CPC v4.3.1
[10:11:50:445200] Info : Secondary bus bitrate is 460800
[10:11:50:448218] Info : Secondary APP v4.3.1-4f7f9e99-dirty-e3b0c442
[10:11:50:448509] Info : Daemon startup was successful. Waiting for client connections
[10:11:51] INFO: Setup OTBR firewall...
[10:11:51] INFO: Starting otbr-agent...
otbr-agent[306]: [NOTE]-AGENT---: Running 0.3.0
otbr-agent[306]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[306]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[306]: [NOTE]-AGENT---: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0
otbr-agent[306]: [NOTE]-ILS-----: Infra link selected: end0
otbr-agent[306]: 49d.17:46:12.329 [C] Platform------: mCpcBusSpeed = 115200
[10:11:51:720317] Info : New client connection using library v4.3.1.0
[10:11:51:722549] Info : Opened connection socket for ep#12
[10:11:51:722691] Info : Endpoint socket #12: Client connected. 1 connections
[10:11:52:118208] Info : New client connection using library v4.3.1.0
[10:11:52:120344] Info : Endpoint socket #12: Client connected. 2 connections
otbr-agent[306]: 00:00:00.044 [N] RoutingManager: BR ULA prefix: fd26:17e9:4887::/48 (loaded)
otbr-agent[306]: 00:00:00.044 [N] RoutingManager: Local on-link prefix: fdfa:7c13:f991:904a::/64
otbr-agent[306]: 00:00:00.083 [N] Mle-----------: Role disabled -> detached
otbr-agent[306]: 00:00:00.099 [N] Platform------: [netif] Changing interface state to up.
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
[10:11:54] 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
Listening on port 9999 for connection...
Accepting connection.
otbr-agent[306]: 00:00:26.288 [N] Mle-----------: RLOC16 c800 -> fffe
otbr-agent[306]: 00:00:26.290 [W] Platform------: [netif] Failed to process request#5: Unknown error -95
otbr-agent[306]: 00:00:26.710 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[306]: 00:00:33.213 [N] RouterTable---: Allocate router id 50
otbr-agent[306]: 00:00:33.213 [N] Mle-----------: RLOC16 fffe -> c800
otbr-agent[306]: 00:00:33.215 [N] Mle-----------: Role detached -> leader
otbr-agent[306]: 00:00:33.216 [N] Mle-----------: Partition ID 0x65fafa63
otbr-agent[306]: 00:00:33.246 [W] Platform------: [netif] Failed to process request#6: Unknown error -17
otbr-agent[306]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
pour zibbee2MQTT
[10:16:36] INFO: Preparing to start...
[10:16:37] INFO: Socat not enabled
[10:16:37] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-12-08 10:16:44] info: z2m: Logging to console, file (filename: log.log)
[2024-12-08 10:16:44] info: z2m: Starting Zigbee2MQTT version 1.42.0 (commit #unknown)
[2024-12-08 10:16:44] info: z2m: Starting zigbee-herdsman (2.1.9)
[2024-12-08 10:16:44] info: zh:ember: Using default stack config.
[2024-12-08 10:16:44] info: zh:ember: ======== Ember Adapter Starting ========
[2024-12-08 10:16:44] info: zh:ember:ezsp: ======== EZSP starting ========
[2024-12-08 10:16:44] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2024-12-08 10:16:44] info: zh:ember:uart:ash: ASH COUNTERS since last clear:
[2024-12-08 10:16:44] info: zh:ember:uart:ash: Total frames: RX=0, TX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: Cancelled : RX=0, TX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: DATA frames : RX=0, TX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: DATA bytes : RX=0, TX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: Retry frames: RX=0, TX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: ACK frames : RX=0, TX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: NAK frames : RX=0, TX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: CRC errors : RX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: Comm errors : RX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: Length < minimum: RX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: Length > maximum: RX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: Bad controls : RX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: Bad lengths : RX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: Bad ACK numbers : RX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: Out of buffers : RX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: Retry dupes : RX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: Out of sequence : RX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: ACK timeouts : RX=0
[2024-12-08 10:16:44] info: zh:ember:uart:ash: ======== ASH stopped ========
[2024-12-08 10:16:44] error: zh:ember:uart:ash: Failed to init port with error Error: Error Resource temporarily unavailable Cannot lock port
[2024-12-08 10:16:44] error: z2m: Error while starting zigbee-herdsman
[2024-12-08 10:16:44] error: z2m: Failed to start zigbee
[2024-12-08 10:16:44] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-12-08 10:16:44] error: z2m: Exiting...
[2024-12-08 10:16:44] error: z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.
at EmberAdapter.initEzsp (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:684:19)
at EmberAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1598:24)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:137:29)
at Zigbee.start (/app/lib/zigbee.ts:69:27)
at Controller.start (/app/lib/controller.ts:161:27)
at start (/app/index.js:154:5)
j’ai donc
je peux démarrer le module, mais message d’erreur au moment d’ouvrir l’interface utilisateur Web :
