Mise a jour Sonoff DONGLE -E pour Zigbee2mqtt (EMBER) ( archive )

Sabjul33 · Mai 6, 2024, 4:04

Je n’ai pas eu besoin de le faire aussi. (renommé le fichier…)

WarC0zes · Mai 6, 2024, 4:28

C’est le monde…

Amigalxii · Mai 6, 2024, 5:07

la 7.4.3 +ember sur la V1.37.0 pour moi c’est OK. j’ai arreté ZigbeeMQTT modifié en ember dans la config puis flash du dongle, Redemarrage du system. j’ai un « mini PC » avec HA seul.

pascal_ha · Mai 6, 2024, 5:12

Je suis aussi dans ton cas, HAOS installé seul sur un mini PC.

« Dans la config », c’est-à-dire directement dans le fichier configuration.yaml du dossier zigbee2mqtt ?

ou dans le menu configuration du module complémentaire zigbee2mqtt ?
(il est quasi vide ce fichier et je n’ai rien dans serial)

Amigalxii · Mai 6, 2024, 5:18

oui dans serial

port: >-
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20231121095845-if00
adapter: ember

Amigalxii · Mai 6, 2024, 5:20

dans le menu configuration du module complémentaire zigbee2mqtt

WarC0zes · Mai 6, 2024, 5:37

Dans Z2M, puis paramètre / port serie

ou par file editor dans le configuration.yaml de Z2M.

ne pas faire de c’est endroit, ca risque de pas enregistrer.

janfi67 · Mai 6, 2024, 10:02

HA core_2024.5.1 puis core_2024.5.2, z2m 1.36.1-1 puis 1.37.0-1, Sonoff dongle-E flashé en 7.4.2 [GA] puis EmberZNet au lieu de ezsp et ça fonctionne sans rien renommer chez moi (à par quelques messages ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE.

Sabjul33 · Mai 7, 2024, 6:32

J’ai aussi ce type d’erreur, enfin maintenant moins, sauf il me semble quand j’essaye de faire une update d’n équipement. Est-ce qu’il faut passer la V7.4.3 du dongle ou attendre une update de Z2M.
That is the question !!!

ddfdom · Mai 7, 2024, 10:12

c’est une bonne idée de la faire, car ils travaillent activement sur le driver

pascal_ha · Mai 8, 2024, 8:48

Bonjour à tous

Mise a jour Dongle Type E avec Z2M depuis V1.37.0

J’ai procédé comme suit :

Arrêt du module complémentaire zigbee2mqtt (Z2M)
Modification du type adaptateur de « ezsp » en « ember » dans le fichier /zigbee2mqtt/configuration.yaml

Édit: 22/08/2024
!! La configuration de Z2M (ou modification de configuration) doit être faite dans le fichier de configuration.yaml de zigbee2mqtt

rappel:
Une fois Z2M installé, toutes les modifications de configuration doivent être faites dans le fichier de configuration.yaml, qui se trouve dans le dossier zigbee2mqtt !! .
Les modifications de configuration faites par UI du module complémentaire sont prises en compte uniquement lors de la premiere installation de Z2M.!!

**!! Il ne faut pas faire la configuration dans le module complémentaire de Z2M !! ** !!

Arrêt de HA et du NUC
Branchement de la clé sur mon PC pour mise à jour
Mise à jour avec le lien de @ddfdom : Silabs Firmware Flasher | Web based flasher for ZB-GW04 and ZBDongle-E. MultiPAN RCP firmware enables these devices to be used with Silabs Multiprotocol Addon in Home Assistant. Allow Zigbee and Thread to co-exist on the same dongle. Get ahead of the tech an experiment with Matter!

maj_dongle_E_21129×923 50.4 KB

Mise a jour Driver Windows :

Sous Windows, il peut arriver que le driver installé soit générique et votre dongle Sonoff pas reconnu.
aller dans le gestionnaire de périphériques de Windows pour vérifier son état.
effectuer un clic droit puis Mettre à jour le pilote.
vous devriez voir votre dongle sous les périphériques COM sous le nom Silicon Labs CP210x. Selectionner le driver silicon labs.

Selection Firmware :

J’ai utilisé le firmware_builds/zbdonglee/ncp-uart-hw-v7.4.3.0-zbdonglee-115200.gbl
à telecharger ici :
silabs-firmware-builder/firmware_builds/zbdonglee/ncp-uart-hw-v7.4.3.0-zbdonglee-115200.gbl at main · darkxst/silabs-firmware-builder · GitHub

Le Dernier Firmware 7.4.4.0 (22/08/2024) : ci dessous

maj_dongle_E_4

Cliquez sur change firmware pour installer le nouveau firmware (suivre la procedure)

maj_dongle_E_9_11

Pour cette premiere partie tous va bien.

La Suite …

Remise en place de la clé dans le NUC HA et redémarrage
Redémarrer le module complémentaire Z2M
1ᵉʳ démarrage échec

log1

[2024-05-08 10:09:46] info: 	zh:ember:uart:ash:   Out of sequence : RX=0
[2024-05-08 10:09:46] info: 	zh:ember:uart:ash:   ACK timeouts    : RX=0
[2024-05-08 10:09:46] error: 	z2m: Error while starting zigbee-herdsman
[2024-05-08 10:09:46] error: 	z2m: Failed to start zigbee
[2024-05-08 10:09:46] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-05-08 10:09:46] error: 	z2m: Exiting...
[2024-05-08 10:09:46] error: 	z2m: Error: 
    at Ezsp.ezspVersion (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:1301:19)
    at EmberAdapter.emberVersion (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1642:66)
    at EmberAdapter.initEzsp (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:802:9)
    at EmberAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:2660:24)
    at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:124:29)
    at Zigbee.start (/app/lib/zigbee.ts:62:27)
    at Controller.start (/app/lib/controller.ts:108:27)
    at start (/app/index.js:107:5)

Aller dans le dossier zigbee2mqtt et renommer coordinator_backup.json en coordinator_backup.json.bak

(Z2m va reconstruire le fichier avec les bons réglages)

Redémarrer Z2M (patienter quelques minutes) si c’est bon, vous avez ce log:

Log 2

[10:11:19] INFO: Preparing to start...
[10:11:19] INFO: Socat not enabled
[10:11:19] INFO: Starting Zigbee2MQTT...
[2024-05-08 10:11:20] info: 	z2m: Logging to console, file (filename: log.log)
[2024-05-08 10:11:21] info: 	z2m: Starting Zigbee2MQTT version 1.37.0 (commit #unknown)
[2024-05-08 10:11:21] info: 	z2m: Starting zigbee-herdsman (0.45.0)
[2024-05-08 10:11:21] info: 	zh:ember: ======== Ember Adapter Starting ========
[2024-05-08 10:11:21] info: 	zh:ember:ezsp: ======== EZSP starting ========
[2024-05-08 10:11:21] info: 	zh:ember:uart:ash: ======== ASH NCP reset ========
[2024-05-08 10:11:21] info: 	zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2024-05-08 10:11:21] info: 	zh:ember:uart:ash: Serial port opened
[2024-05-08 10:11:21] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2024-05-08 10:11:22] info: 	zh:ember:uart:ash: ======== ASH connected ========
[2024-05-08 10:11:22] info: 	zh:ember:uart:ash: ======== ASH started ========
[2024-05-08 10:11:22] info: 	zh:ember:ezsp: ======== EZSP started ========
[2024-05-08 10:11:22] info: 	zh:ember: [STACK STATUS] Network up.
[2024-05-08 10:11:22] info: 	zh:ember: [INIT TC] NCP network matches config.
[2024-05-08 10:11:22] info: 	zh:ember: [CONCENTRATOR] Started source route discovery. 1248ms until next broadcast.
[2024-05-08 10:11:22] info: 	z2m: zigbee-herdsman started (resumed)
[2024-05-08 10:11:22] info: 	z2m: Coordinator firmware version: '{"meta":{"build":0,"ezsp":13,"major":7,"minor":4,"patch":3,"revision":"7.4.3 [GA]","special":0,"type":170},"type":"EmberZNet"}'
[2024-05-08 10:11:22] info: 	z2m: Currently 39 devices are joined:
[2024-05-08 10:11:22] info: 	z2m: Plug zb 001 (0xa4c138606ee9d8d1): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 002 (0xa4c13892cedc4ea2): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 003 (0xa4c1386442433559): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 004 (0xa4c13897b38afa8d): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 005 (0xa4c138d21a4ada2a): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 006 (0xa4c1380fee2a7965): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 007 (0xa4c138505168542e): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 008 (0xa4c138b2b8cc9c0c): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 009 (0xa4c1389a6388b5b5): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 010 (0xa4c138aefffd1e8c): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 011 (0xa4c138b41955b770): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: Vanne motorise 1 (0xa4c138f4f5986e05): ZN231392 - TuYa Smart water/gas valve (Router)
[2024-05-08 10:11:22] info: 	z2m: VMC Pv Gv (0xa4c1389ce82b9071): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Fingerbot 1 (0xa4c1388f2d3731ce): TS0001_fingerbot - TuYa Zigbee fingerbot plus (EndDevice)
[2024-05-08 10:11:22] info: 	z2m: plug zb 012 (0xa4c138b54aa16f2b): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 013 (0xa4c138dbf840e272): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 014 (0xa4c13880d169e5db): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 015 (0xa4c1381d950548f0): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 016 (0xa4c138fd3f115316): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: Vanne motorise 2 (0xa4c13840975acd17): ZN231392 - TuYa Smart water/gas valve (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 017 (0xa4c13891190343c8): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 018 (0xa4c13812717db16f): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 019 (0xa4c138494117c6cd): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 020 (0xa4c1386edf7dbeb1): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: plug zb 021 (0xa4c138a48c43370c): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
[2024-05-08 10:11:22] info: 	z2m: perron (0xa4c138a076284caa): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Couloir rdc (0xa4c1380d42bfbc90): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Relais frisquet (0xa4c13822d6bc0e62): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Bureau (0xa4c13843562d31f4): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Garage (0xa4c1381990a367c2): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Buanderie (0xa4c138839a54b4e4): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Salle de douche (0xa4c138012848291e): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Couloir etage (0xa4c138782f37708a): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Salle de bain (0xa4c138dacecbb74c): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Miroir salle de bain (0xa4c1389d0591ea57): JR-ZDS01 - Girier 1 gang mini switch (Router)
[2024-05-08 10:11:22] info: 	z2m: Escalier etage (0xa4c13814bb92268a): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Grenier (0xa4c13830cb436749): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Cuisine (0xa4c13832d9a1fd54): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Facade avant (0xa4c13877a08f18c2): TS0001_switch_module - TuYa 1 gang switch module (Router)
[2024-05-08 10:11:22] info: 	z2m: Zigbee: disabling joining new devices.
[2024-05-08 10:11:22] info: 	z2m: Connecting to MQTT server at mqtt://core-mosquitto:1883
[2024-05-08 10:11:23] info: 	z2m: Connected to MQTT server
[2024-05-08 10:11:23] info: 	z2m: Started frontend on port 8099
[2024-05-08 10:11:23] info: 	z2m: Zigbee2MQTT started!

(Si c’est pas bon, redémarrer Z2M, j’ai du le faire 2 fois)

Activer un équipement Zigbee pour réactiver le réseau
Normalement après sa fonctionne )

Malgré tout j’ai ces message qui s’affiche dans les logs :

LOG Warning

[2024-05-08 10:11:26] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "35716".
[2024-05-08 10:12:07] warning: 	z2m: Failed to ping 'Vanne motorise 2' (attempt 1/1, ZCL command 0xa4c13840975acd17/1 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":0,"sourceEndpoint":1,"destinationEndpoint":1,"options":4160,"groupId":0,"sequence":253}))
[2024-05-08 10:12:17] warning: 	z2m: Failed to ping 'plug zb 017' (attempt 1/1, ZCL command 0xa4c13891190343c8/1 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":0,"sourceEndpoint":1,"destinationEndpoint":1,"options":4160,"groupId":0,"sequence":32}))

Edit: la mise a jour de z2m en version 1.37.1 apporte des corrections, notamment remplacement des messages de « warning » (rouge ou orange) par des messages « info » (vert).

Log Error

[2024-05-08 10:45:43] error: 	z2m: Publish 'set' 'state' to 'plug zb 020' failed: 'Error: ZCL command 0xa4c1386edf7dbeb1/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed ({"target":61859,"apsFrame":{"profileId":260,"clusterId":6,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":177},"zclSequence":186,"commandIdentifier":11} timed out after 10000ms)'

Tous fonctionne.

Voila si sa peut servir à d’autres…

ddfdom · Mai 8, 2024, 8:59

Rien de très grave dans tes log les 2 premiers sont sur des soucis de modules pas joignables (failed to ping) since sont des modules a piles tente de les réveiller manuellement

pascal_ha · Mai 8, 2024, 9:41

Le log error, vient bien de mon fingerbot, pourtant il fonctionne bien ??
Je l’ai actionné, mais il était bien visible dans HA

J’ai aussi remarqué que les warnings ou error se déclenche quand l’équipement met du temps à réagir.
(Je n’avais pas cela avant…)
exemple module lumière salle de bain

[2024-05-08 11:30:31] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "52460".
[2024-05-08 11:31:40] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "38485".
[2024-05-08 11:31:48] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "19414".
[2024-05-08 11:32:12] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "61966".
[2024-05-08 11:32:47] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "33903".
[2024-05-08 11:32:49] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "5612".
[2024-05-08 11:33:29] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "32585".
[2024-05-08 11:34:30] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "19414".
[2024-05-08 11:35:26] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "29819".
[2024-05-08 11:38:01] error: 	z2m: Publish 'set' 'state' to 'Salle de bain' failed: 'Error: ZCL command 0xa4c138dacecbb74c/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed ({"target":61966,"apsFrame":{"profileId":260,"clusterId":6,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":4},"zclSequence":66,"commandIdentifier":11} timed out after 10000ms)'
[2024-05-08 11:38:54] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "5612".
[2024-05-08 11:40:01] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "31066".
[2024-05-08 11:40:27] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "33903".
[2024-05-08 11:41:36] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "52460".

Idaho947 · Mai 8, 2024, 9:49

C’est une « nouveauté » de la maj.

pascal_ha · Mai 8, 2024, 9:51

c’est-à-dire ? la nouveauté, c’est d’être bombardé de warning

Idaho947 · Mai 8, 2024, 9:55

Faut voir ce que donneront les prochaines maj mais de nombreux utilisateurs remontent ce soucis. Pour le suivi : Issues · Koenkk/zigbee2mqtt · GitHub

didier02100 · Mai 8, 2024, 10:17

Bonjour a tous, je viens de faire également la mise à jours , avec redemarrage complet du system 2x
j’ai egalement des erreurs … pourtant tout fonctionne correctement pour l’instant

[12:15:31] INFO: Preparing to start...
[12:15:31] INFO: Socat not enabled
[12:15:32] INFO: Starting Zigbee2MQTT...
[2024-05-08 12:15:33] error: 	zh:ember:uart:ash: Received frame with CRC error
[2024-05-08 12:15:33] error: 	zh:ember:uart:ash: Received ERROR from NCP while connecting, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT.
[2024-05-08 12:15:33] error: 	zh:ember:uart:ash: ASH disconnected | NCP status: ASH_NCP_FATAL_ERROR
[2024-05-08 12:15:35] warning: 	zh:ember:uart:ash: Frame(s) in progress cancelled in [1ac1020b0a527e]
[2024-05-08 12:15:35] error: 	zh:ember:uart:ash: Received unexpected reset from NCP, with reason=RESET_SOFTWARE.
[2024-05-08 12:15:35] error: 	zh:ember:uart:ash: ASH disconnected: ASH_ERROR_NCP_RESET | NCP status: ASH_NCP_FATAL_ERROR
[2024-05-08 12:15:49] error: 	zh:ember:ezsp: ERROR Transaction failure; status=undefined. Last: [FRAME: ID=0:"VERSION" Seq=0 Len=4].
[2024-05-08 12:15:49] error: 	zh:ember: !!! NCP FATAL ERROR reason=undefined. ATTEMPTING RESET... !!!
[2024-05-08 12:15:49] error: 	z2m: Error while starting zigbee-herdsman
[2024-05-08 12:15:49] error: 	z2m: Failed to start zigbee
[2024-05-08 12:15:49] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-05-08 12:15:49] error: 	z2m: Exiting...
[2024-05-08 12:15:49] error: 	z2m: Error: 
    at Ezsp.ezspVersion (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:1301:19)
    at EmberAdapter.emberVersion (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1642:66)
    at EmberAdapter.initEzsp (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:802:9)
    at EmberAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:2660:24)
    at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:124:29)
    at Zigbee.start (/app/lib/zigbee.ts:62:27)
    at Controller.start (/app/lib/controller.ts:108:27)
    at start (/app/index.js:107:5)
[12:15:49] INFO: Preparing to start...
[12:15:50] INFO: Socat not enabled
[12:15:50] INFO: Starting Zigbee2MQTT...

ddfdom · Mai 8, 2024, 10:17

J’appel pas ça un problème si c’est réellement le cas
Mais faut croire que ça en perturbe certains
Faut pas s’inquiéter pour des warnings, le driver est peu être un peu trop verbeu

didier02100 · Mai 8, 2024, 10:26

Heu curieux … encore un autre redemarrage et presque tout fonctionne

[12:15:49] INFO: Preparing to start...
[12:15:50] INFO: Socat not enabled
[12:15:50] INFO: Starting Zigbee2MQTT...
[12:19:09] INFO: Preparing to start...
[12:19:09] INFO: Socat not enabled
[12:19:10] INFO: Starting Zigbee2MQTT...
[2024-05-08 12:22:22] info: 	z2m: Successfully changed options
[2024-05-08 12:22:56] info: 	z2m: Disconnecting from MQTT server
[2024-05-08 12:22:56] info: 	z2m: Stopping zigbee-herdsman...
[2024-05-08 12:22:56] info: 	zh:controller: Wrote coordinator backup to '/config/zigbee2mqtt/coordinator_backup.json'
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash: ASH COUNTERS since last clear:
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   Total frames: RX=241, TX=323
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   Cancelled   : RX=0, TX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   DATA frames : RX=236, TX=87
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   DATA bytes  : RX=5511, TX=1295
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   Retry frames: RX=4, TX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   ACK frames  : RX=0, TX=235
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   NAK frames  : RX=0, TX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   nRdy frames : RX=0, TX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   CRC errors      : RX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   Comm errors     : RX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   Length < minimum: RX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   Length > maximum: RX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   Bad controls    : RX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   Bad lengths     : RX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   Bad ACK numbers : RX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   Out of buffers  : RX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   Retry dupes     : RX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   Out of sequence : RX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash:   ACK timeouts    : RX=0
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash: Port closed. Error? no
[2024-05-08 12:22:56] info: 	zh:ember:uart:ash: ======== ASH stopped ========
[2024-05-08 12:22:56] info: 	zh:ember:ezsp: ======== EZSP stopped ========
[2024-05-08 12:22:56] info: 	zh:ember: ======== Ember Adapter Stopped ========
[2024-05-08 12:22:56] info: 	z2m: Stopped zigbee-herdsman
[2024-05-08 12:22:56] info: 	z2m: Stopped Zigbee2MQTT
[12:23:17] INFO: Preparing to start...
[12:23:18] INFO: Socat not enabled
[12:23:18] INFO: Starting Zigbee2MQTT...
[2024-05-08 12:23:19] info: 	z2m: Logging to console, file (filename: log.log)
[2024-05-08 12:23:20] info: 	z2m: Starting Zigbee2MQTT version 1.37.0 (commit #unknown)
[2024-05-08 12:23:20] info: 	z2m: Starting zigbee-herdsman (0.45.0)
[2024-05-08 12:23:20] info: 	zh:ember: ======== Ember Adapter Starting ========
[2024-05-08 12:23:20] info: 	zh:ember:ezsp: ======== EZSP starting ========
[2024-05-08 12:23:20] info: 	zh:ember:uart:ash: ======== ASH NCP reset ========
[2024-05-08 12:23:20] info: 	zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2024-05-08 12:23:20] info: 	zh:ember:uart:ash: Serial port opened
[2024-05-08 12:23:20] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2024-05-08 12:23:20] error: 	zh:ember:uart:ash: Received frame with CRC error
[2024-05-08 12:23:20] error: 	zh:ember:uart:ash: Received frame with CRC error
[2024-05-08 12:23:20] error: 	zh:ember:uart:ash: Received ERROR from NCP while connecting, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT.
[2024-05-08 12:23:20] error: 	zh:ember:uart:ash: ASH disconnected | NCP status: ASH_NCP_FATAL_ERROR
[2024-05-08 12:23:20] info: 	zh:ember:uart:ash: ======== ASH NCP reset ========
[2024-05-08 12:23:20] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2024-05-08 12:23:21] info: 	zh:ember:uart:ash: ======== ASH connected ========
[2024-05-08 12:23:21] info: 	zh:ember:uart:ash: ======== ASH started ========
[2024-05-08 12:23:21] info: 	zh:ember:ezsp: ======== EZSP started ========

reste plus que celles là :

[2024-05-08 12:23:20] error: 	zh:ember:uart:ash: Received frame with CRC error
[2024-05-08 12:23:20] error: 	zh:ember:uart:ash: Received frame with CRC error
[2024-05-08 12:23:20] error: 	zh:ember:uart:ash: Received ERROR from NCP while connecting, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT.
[2024-05-08 12:23:20] error: 	zh:ember:uart:ash: ASH disconnected | NCP status: ASH_NCP_FATAL_ERROR

.
.
.bon , ben ,il suffit d’attendre et tout rentre dans l’ordre … plus d’erreurs

didier02100 · Mai 8, 2024, 1:17

Je me sent vachement visé là … mais je suis pas « perturbé » , … jusque completement paniqué !! .

face_with_spiral_eyes

.
rofl
.
quand on sais pas trop ce qu’on fait … on suit à la lettre en espérant rien faire de mal !!
Et quand il y a un truc pas prévus … oupsss …

Mise a jour Sonoff DONGLE -E pour Zigbee2mqtt (EMBER) ( archive )

Pour cette premiere partie tous va bien.

** Tous fonctionne.**

Tous fonctionne.