Mise a jour fichier : devices.js

[ludoviclt]

bonjour

actuellement sur jeedom sur freebox delta, j’ai une clef zigbee2mqtt qui fonctionne tres bien
afin d’avoir a jour mon fichier devices, je pensais pouvoir telecharger celui ci afin de remplacer ma version actuel

pouvez vous me dire comment remplacer ou mettre a jour avec celui du site web mon fichier devices.js

voici comment je procède actuellement mais suite a cela je n’arrive plus a relancer le service zigbe2mqtt

1 - sudo systemctl stop zigbee2mqtt
2 - cd /opt/zigbee2mqtt/node_modules/zigbee-herdsman-converters
3 - wget -c https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/devices.js
4 - sudo systemctl start zigbee2mqtt

voic que que j’ai comme erreur

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
admin@Jeedom:~$ sudo journalctl -u zigbee2mqtt.service -f
-- Logs begin at Sat 2020-09-12 23:54:39 CEST. --
sept. 12 23:55:33 Jeedom systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
sept. 12 23:55:34 Jeedom systemd[1]: zigbee2mqtt.service: Service RestartSec=100ms expired, scheduling restart.
sept. 12 23:55:34 Jeedom systemd[1]: zigbee2mqtt.service: Scheduled restart job, restart counter is at 2.
sept. 12 23:55:34 Jeedom systemd[1]: Stopped zigbee2mqtt.
sept. 12 23:55:34 Jeedom systemd[1]: Started zigbee2mqtt.
sept. 12 23:55:34 Jeedom npm[1273]: > zigbee2mqtt@1.14.4 start /opt/zigbee2mqtt
sept. 12 23:55:34 Jeedom npm[1273]: > node index.js
sept. 12 23:55:35 Jeedom npm[1273]: Zigbee2MQTT:info  2020-09-12 23:55:35: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2020-09-12.23-55-35' filename: log.txt
sept. 12 23:55:36 Jeedom npm[1273]: Zigbee2MQTT:info  2020-09-12 23:55:36: Starting Zigbee2MQTT version 1.14.4 (commit #037d54a)
sept. 12 23:55:36 Jeedom npm[1273]: Zigbee2MQTT:info  2020-09-12 23:55:36: Starting zigbee-herdsman...
sept. 12 23:55:55 Jeedom npm[1273]: Zigbee2MQTT:error 2020-09-12 23:55:55: Error while starting zigbee-herdsman
sept. 12 23:55:55 Jeedom npm[1273]: Zigbee2MQTT:error 2020-09-12 23:55:55: Failed to start zigbee
sept. 12 23:55:55 Jeedom npm[1273]: Zigbee2MQTT:error 2020-09-12 23:55:55: Exiting...
sept. 12 23:55:55 Jeedom npm[1273]: Zigbee2MQTT:error 2020-09-12 23:55:55: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
sept. 12 23:55:55 Jeedom npm[1273]:     at ZStackAdapter.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:90:31)
sept. 12 23:55:55 Jeedom npm[1273]:     at Generator.throw (<anonymous>)
sept. 12 23:55:55 Jeedom npm[1273]:     at rejected (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)
sept. 12 23:55:55 Jeedom npm[1273]: npm ERR! code ELIFECYCLE
sept. 12 23:55:55 Jeedom npm[1273]: npm ERR! errno 1
sept. 12 23:55:55 Jeedom npm[1273]: npm ERR! zigbee2mqtt@1.14.4 start: `node index.js`
sept. 12 23:55:55 Jeedom npm[1273]: npm ERR! Exit status 1
sept. 12 23:55:55 Jeedom npm[1273]: npm ERR!
sept. 12 23:55:55 Jeedom npm[1273]: npm ERR! Failed at the zigbee2mqtt@1.14.4 start script.
sept. 12 23:55:55 Jeedom npm[1273]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
sept. 12 23:55:57 Jeedom npm[1273]: npm ERR! A complete log of this run can be found in:
sept. 12 23:55:57 Jeedom npm[1273]: npm ERR!     /home/admin/.npm/_logs/2020-09-12T21_55_55_830Z-debug.log
sept. 12 23:55:57 Jeedom systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=1/FAILURE
sept. 12 23:55:57 Jeedom systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
sept. 12 23:55:57 Jeedom systemd[1]: zigbee2mqtt.service: Service RestartSec=100ms expired, scheduling restart.
sept. 12 23:55:57 Jeedom systemd[1]: zigbee2mqtt.service: Scheduled restart job, restart counter is at 3.
sept. 12 23:55:57 Jeedom systemd[1]: Stopped zigbee2mqtt.
sept. 12 23:55:57 Jeedom systemd[1]: Started zigbee2mqtt.
sept. 12 23:55:58 Jeedom npm[1303]: > zigbee2mqtt@1.14.4 start /opt/zigbee2mqtt
sept. 12 23:55:58 Jeedom npm[1303]: > node index.js
sept. 12 23:55:58 Jeedom npm[1303]: Zigbee2MQTT:info  2020-09-12 23:55:58: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2020-09-12.23-55-58' filename: log.txt
sept. 12 23:55:59 Jeedom npm[1303]: Zigbee2MQTT:info  2020-09-12 23:55:59: Starting Zigbee2MQTT version 1.14.4 (commit #037d54a)
sept. 12 23:55:59 Jeedom npm[1303]: Zigbee2MQTT:info  2020-09-12 23:55:59: Starting zigbee-herdsman...
sept. 12 23:56:19 Jeedom npm[1303]: Zigbee2MQTT:error 2020-09-12 23:56:19: Error while starting zigbee-herdsman
sept. 12 23:56:19 Jeedom npm[1303]: Zigbee2MQTT:error 2020-09-12 23:56:19: Failed to start zigbee
sept. 12 23:56:19 Jeedom npm[1303]: Zigbee2MQTT:error 2020-09-12 23:56:19: Exiting...
sept. 12 23:56:19 Jeedom npm[1303]: Zigbee2MQTT:error 2020-09-12 23:56:19: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
sept. 12 23:56:19 Jeedom npm[1303]:     at ZStackAdapter.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:90:31)
sept. 12 23:56:19 Jeedom npm[1303]:     at Generator.throw (<anonymous>)
sept. 12 23:56:19 Jeedom npm[1303]:     at rejected (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)
sept. 12 23:56:19 Jeedom npm[1303]: npm ERR! code ELIFECYCLE
sept. 12 23:56:19 Jeedom npm[1303]: npm ERR! errno 1
sept. 12 23:56:19 Jeedom npm[1303]: npm ERR! zigbee2mqtt@1.14.4 start: `node index.js`
sept. 12 23:56:19 Jeedom npm[1303]: npm ERR! Exit status 1
sept. 12 23:56:19 Jeedom npm[1303]: npm ERR!
sept. 12 23:56:19 Jeedom npm[1303]: npm ERR! Failed at the zigbee2mqtt@1.14.4 start script.
sept. 12 23:56:19 Jeedom npm[1303]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
sept. 12 23:56:19 Jeedom npm[1303]: npm ERR! A complete log of this run can be found in:
sept. 12 23:56:19 Jeedom npm[1303]: npm ERR!     /home/admin/.npm/_logs/2020-09-12T21_56_19_125Z-debug.log
sept. 12 23:56:19 Jeedom systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=1/FAILURE
sept. 12 23:56:19 Jeedom systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
sept. 12 23:56:19 Jeedom systemd[1]: zigbee2mqtt.service: Service RestartSec=100ms expired, scheduling restart.
sept. 12 23:56:19 Jeedom systemd[1]: zigbee2mqtt.service: Scheduled restart job, restart counter is at 4.
sept. 12 23:56:19 Jeedom systemd[1]: Stopped zigbee2mqtt.
sept. 12 23:56:19 Jeedom systemd[1]: Started zigbee2mqtt.
sept. 12 23:56:20 Jeedom npm[1629]: > zigbee2mqtt@1.14.4 start /opt/zigbee2mqtt
sept. 12 23:56:20 Jeedom npm[1629]: > node index.js
sept. 12 23:56:21 Jeedom npm[1629]: Zigbee2MQTT:info  2020-09-12 23:56:21: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2020-09-12.23-56-21' filename: log.txt
sept. 12 23:56:22 Jeedom npm[1629]: Zigbee2MQTT:info  2020-09-12 23:56:22: Starting Zigbee2MQTT version 1.14.4 (commit #037d54a)
sept. 12 23:56:22 Jeedom npm[1629]: Zigbee2MQTT:info  2020-09-12 23:56:22: Starting zigbee-herdsman...
sept. 12 23:56:42 Jeedom npm[1629]: Zigbee2MQTT:error 2020-09-12 23:56:42: Error while starting zigbee-herdsman
sept. 12 23:56:42 Jeedom npm[1629]: Zigbee2MQTT:error 2020-09-12 23:56:42: Failed to start zigbee
sept. 12 23:56:42 Jeedom npm[1629]: Zigbee2MQTT:error 2020-09-12 23:56:42: Exiting...
sept. 12 23:56:42 Jeedom npm[1629]: Zigbee2MQTT:error 2020-09-12 23:56:42: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
sept. 12 23:56:42 Jeedom npm[1629]:     at ZStackAdapter.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:90:31)
sept. 12 23:56:42 Jeedom npm[1629]:     at Generator.throw (<anonymous>)
sept. 12 23:56:42 Jeedom npm[1629]:     at rejected (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)
sept. 12 23:56:42 Jeedom npm[1629]: npm ERR! code ELIFECYCLE
sept. 12 23:56:42 Jeedom npm[1629]: npm ERR! errno 1
sept. 12 23:56:42 Jeedom npm[1629]: npm ERR! zigbee2mqtt@1.14.4 start: `node index.js`
sept. 12 23:56:42 Jeedom npm[1629]: npm ERR! Exit status 1
sept. 12 23:56:42 Jeedom npm[1629]: npm ERR!
sept. 12 23:56:42 Jeedom npm[1629]: npm ERR! Failed at the zigbee2mqtt@1.14.4 start script.
sept. 12 23:56:42 Jeedom npm[1629]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
sept. 12 23:56:42 Jeedom npm[1629]: npm ERR! A complete log of this run can be found in:
sept. 12 23:56:42 Jeedom npm[1629]: npm ERR!     /home/admin/.npm/_logs/2020-09-12T21_56_42_479Z-debug.log
sept. 12 23:56:42 Jeedom systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=1/FAILURE
sept. 12 23:56:42 Jeedom systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
sept. 12 23:56:43 Jeedom systemd[1]: zigbee2mqtt.service: Service RestartSec=100ms expired, scheduling restart.
sept. 12 23:56:43 Jeedom systemd[1]: zigbee2mqtt.service: Scheduled restart job, restart counter is at 5.
sept. 12 23:56:43 Jeedom systemd[1]: Stopped zigbee2mqtt.
sept. 12 23:56:43 Jeedom systemd[1]: Started zigbee2mqtt.
sept. 12 23:56:43 Jeedom npm[1766]: > zigbee2mqtt@1.14.4 start /opt/zigbee2mqtt
sept. 12 23:56:43 Jeedom npm[1766]: > node index.js

actuellement pour m’en sortir je récupère ma vm complète et cela fonctionne

merci pour votre aide

[PanoLyon]

Bonsoir, je ne pense pas qu’il suffise de de remplacer le device.js, il faut faire la mise à jour complète …

[ludoviclt]

bonsoir @PanoLyon, tu fais cela comment la mise a jour complète

merci

[BMW09]

Voici un lien vers les instruction.

Merci

https://www.zigbee2mqtt.io/getting_started/running_zigbee2mqtt.html

[PanoLyon]

en bas de la page du lien envoyé par @BMW09

[ludoviclt]

@BMW09

| Zigbee2MQTT

merci a vous deux

donc si je comprends le fait de mettre a jour la clef va mettre aussi a jour le fichier devices

j’avais fait cette manip il y a peux, mais comment savoir si le fichier devices est a jour par rapport a celle du serveur

il y a une commande pour cela

merci

[BMW09]

Bonjour Ludoviclt. Petit point, c’est pas la clé qu’il faut mettre a jour mais le logiciel zigbee2mqtt. La clé c’est juste l’antenne zigbee. Sur gitub le concepteur fait des mise a jour tout les 20 jours à 1 mois environ. Donc si tout fonctionne bien pas besoin de faire de mise a jour. Si tu ajoute des nouveaux périphériques, là tu peut faire une petite mise a jour avant, mais sans plus.

Au plaisir

[ludoviclt]

merci en fait je voulais mettre a jour le logiciel oui afin de voir pourquoi j’ai un équipement inconnu

sept. 14 21:33:24 Jeedom npm[2336]: Zigbee2MQTT:warn  2020-09-14 21:33:24: Received message from unsupported device with Zigbee model 'undefined'
sept. 14 21:33:24 Jeedom npm[2336]: Zigbee2MQTT:warn  2020-09-14 21:33:24: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

je pense que j’ai cette alerte depuis que j’ai programmé une autre clef zigbee2mqtt mais avec le firmware routeur sur une autre clef cc2531

je pense que j’ai bien un capteur qui remonte via ce routeur mais pas sur a 100%

je vais voir comment fonctionne le fait d’avoir le maillage que j’ai sur mes deux clefs avec graphviz

[BMW09]

Ok. oui c’est probablement ça. J’ai pas encore compris comment mapper le maillage avec graphviz. J’utilise mqtt explorer pour remonté le topic mais rien ne remonte. Si tu y arrive j’aimerais bien avoir un petit tuto pour voir comment faire.

Tien moi informer

Merci