Zigbee2mqtt : Image docker de test basée Gladys v4

VonOx · Décembre 3, 2020, 10:03

T’es obligé d’attendre dockerhub à mis des limites maintenant.

C’est 6h je crois

pierre-gilles · Décembre 4, 2020, 7:48

Oui sauf que le problème est que watchtower fait une requête toutes les 5 minutes… je suis même pas sûr qu’il arrive à faire quelque chose en attendant.

Va falloir peut-être envisager de mettre à jour notre configuration Watchtower depuis Gladys là ^^

Reno · Décembre 4, 2020, 8:13

Merci @Jean34.
J’avais fait une bourde dans le code avant hier.
J’ai recréé l’image hier soir et ça doit être bon.
J’attends vos retours, les testeur !

Jean34 · Décembre 9, 2020, 9:43

Salut, alors pour ma part, cette fois tout est au vert sur une installation fraiche à partir de la doc

Mais j’ai les logs qui crient un peu je crois alors je te les joints :

> gladys-server@ start:prod /src/server
> cross-env NODE_ENV=production node index.js

Initialising OpenZWave 1.6.1051 binary addon for Node.JS.
        OpenZWave Security API is ENABLED
        ZWave device db    : /usr/local/etc/openzwave
        User settings path : /src/server/services/zwave/node_modules/openzwave-shared/build/Release/../../
        Option Overrides : --Logging false --ConsoleOutput false --SaveConfiguration true
2020-12-09T22:22:12+0100 <info> index.js:16 (Object.start) Starting zwave service
2020-12-09T22:22:12+0100 <info> service.start.js:40 (Service.start) Service zwave is not configured, so it was not started.
2020-12-09T22:22:12+0100 <info> index.js:13 (Object.start) Starting usb service
2020-12-09T22:22:12+0100 <info> init.js:38 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle not attached
2020-12-09T22:22:12+0100 <info> index.js:15 (Object.start) Starting Bluetooth service
2020-12-09T22:22:13+0100 <info> index.js:19 (Object.start) Starting telegram service
2020-12-09T22:22:13+0100 <info> service.start.js:40 (Service.start) Service telegram is not configured, so it was not started.
2020-12-09T22:22:13+0100 <info> service.start.js:40 (Service.start) Service mqtt is not configured, so it was not started.
2020-12-09T22:22:13+0100 <info> index.js:20 (Object.start) Starting Open Weather service
2020-12-09T22:22:13+0100 <info> service.start.js:40 (Service.start) Service openweather is not configured, so it was not started.
2020-12-09T22:22:14+0100 <info> index.js:63 (Server.<anonymous>) Server listening on port 1080
2020-12-09T22:23:54+0100 <info> init.js:49 () Zigbee2mqtt USB dongle attached to /dev/ttyACM0
2020-12-09T22:24:11+0100 <info> init.js:49 () Zigbee2mqtt USB dongle attached to /dev/ttyACM0
2020-12-09T22:24:11+0100 <info> installMqttContainer.js:32 (Zigbee2mqttManager.installMqttContainer) MQTT broker is being installed as Docker container...
2020-12-09T22:24:11+0100 <info> installMqttContainer.js:33 (Zigbee2mqttManager.installMqttContainer) Pulling eclipse-mosquitto:latest image...
2020-12-09T22:24:19+0100 <info> installMqttContainer.js:37 (Zigbee2mqttManager.installMqttContainer) Preparing broker environment...
2020-12-09T22:24:19+0100 <info> installMqttContainer.js:41 (Zigbee2mqttManager.installMqttContainer) Creating container...
2020-12-09T22:24:32+0100 <info> installMqttContainer.js:55 (Zigbee2mqttManager.installMqttContainer) Zigbee2MQTT MQTT broker is starting...
2020-12-09T22:24:43+0100 <info> installMqttContainer.js:61 (Zigbee2mqttManager.installMqttContainer) Creating user/pass...
2020-12-09T22:24:45+0100 <info> installMqttContainer.js:73 (Zigbee2mqttManager.installMqttContainer) Zigbee2MQTT MQTT broker is starting...
2020-12-09T22:24:52+0100 <info> installMqttContainer.js:77 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started
2020-12-09T22:24:52+0100 <info> installZ2mContainer.js:25 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is being installed as Docker container...
2020-12-09T22:24:52+0100 <info> installZ2mContainer.js:26 (Zigbee2mqttManager.installZ2mContainer) Pulling koenkk/zigbee2mqtt:latest image...
2020-12-09T22:26:11+0100 <info> init.js:49 () Zigbee2mqtt USB dongle attached to /dev/ttyACM0
2020-12-09T22:26:11+0100 <info> installMqttContainer.js:91 (Zigbee2mqttManager.installMqttContainer) Zigbee2MQTT MQTT broker is starting...
2020-12-09T22:26:11+0100 <info> installMqttContainer.js:103 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started
2020-12-09T22:26:11+0100 <info> installZ2mContainer.js:25 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is being installed as Docker container...
2020-12-09T22:26:11+0100 <info> installZ2mContainer.js:26 (Zigbee2mqttManager.installZ2mContainer) Pulling koenkk/zigbee2mqtt:latest image...
2020-12-09T22:26:13+0100 <info> installZ2mContainer.js:29 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment...
2020-12-09T22:26:13+0100 <info> installZ2mContainer.js:35 (Zigbee2mqttManager.installZ2mContainer) Creating container...
2020-12-09T22:26:13+0100 <info> installZ2mContainer.js:29 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment...
2020-12-09T22:26:13+0100 <info> installZ2mContainer.js:35 (Zigbee2mqttManager.installZ2mContainer) Creating container...
2020-12-09T22:26:20+0100 <error> installZ2mContainer.js:46 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt failed to install as Docker container: Error: (HTTP code 409) unexpected - Conflict. The container name "/zigbee2mqtt" is already in use by container "8a9b6c463fc6d86c6d54911504b73ce1aa95b49a54e39cda80822982fabed3d3". You have to remove (or rename) that container to be able to reuse that name.
    at /src/server/node_modules/docker-modem/lib/modem.js:257:17
    at getCause (/src/server/node_modules/docker-modem/lib/modem.js:287:7)
    at Modem.buildPayload (/src/server/node_modules/docker-modem/lib/modem.js:256:5)
    at IncomingMessage.<anonymous> (/src/server/node_modules/docker-modem/lib/modem.js:232:14)
    at IncomingMessage.emit (events.js:326:22)
    at endReadableNT (_stream_readable.js:1241:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  reason: undefined,
  statusCode: 409,
  json: {
    message: 'Conflict. The container name "/zigbee2mqtt" is already in use by container "8a9b6c463fc6d86c6d54911504b73ce1aa95b49a54e39cda80822982fabed3d3". You have to remove (or rename) that container to be able to reuse that name.'
  }
}
2020-12-09T22:26:21+0100 <error> index.js:14 (process.<anonymous>) unhandledRejection catched: Promise {
  <rejected> Error: (HTTP code 409) unexpected - Conflict. The container name "/zigbee2mqtt" is already in use by container "8a9b6c463fc6d86c6d54911504b73ce1aa95b49a54e39cda80822982fabed3d3". You have to remove (or rename) that container to be able to reuse that name.
      at /src/server/node_modules/docker-modem/lib/modem.js:257:17
      at getCause (/src/server/node_modules/docker-modem/lib/modem.js:287:7)
      at Modem.buildPayload (/src/server/node_modules/docker-modem/lib/modem.js:256:5)
      at IncomingMessage.<anonymous> (/src/server/node_modules/docker-modem/lib/modem.js:232:14)
      at IncomingMessage.emit (events.js:326:22)
      at endReadableNT (_stream_readable.js:1241:12)
      at processTicksAndRejections (internal/process/task_queues.js:84:21) {
    reason: undefined,
    statusCode: 409,
    json: {
      message: 'Conflict. The container name "/zigbee2mqtt" is already in use by container "8a9b6c463fc6d86c6d54911504b73ce1aa95b49a54e39cda80822982fabed3d3". You have to remove (or rename) that container to be able to reuse that name.'
    }
  }
}
2020-12-09T22:26:21+0100 <error> index.js:15 (process.<anonymous>) Error: (HTTP code 409) unexpected - Conflict. The container name "/zigbee2mqtt" is already in use by container "8a9b6c463fc6d86c6d54911504b73ce1aa95b49a54e39cda80822982fabed3d3". You have to remove (or rename) that container to be able to reuse that name.
    at /src/server/node_modules/docker-modem/lib/modem.js:257:17
    at getCause (/src/server/node_modules/docker-modem/lib/modem.js:287:7)
    at Modem.buildPayload (/src/server/node_modules/docker-modem/lib/modem.js:256:5)
    at IncomingMessage.<anonymous> (/src/server/node_modules/docker-modem/lib/modem.js:232:14)
    at IncomingMessage.emit (events.js:326:22)
    at endReadableNT (_stream_readable.js:1241:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  reason: undefined,
  statusCode: 409,
  json: {
    message: 'Conflict. The container name "/zigbee2mqtt" is already in use by container "8a9b6c463fc6d86c6d54911504b73ce1aa95b49a54e39cda80822982fabed3d3". You have to remove (or rename) that container to be able to reuse that name.'
  }
}
2020-12-09T22:26:31+0100 <info> installZ2mContainer.js:43 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt successfully installed as Docker container
2020-12-09T22:26:31+0100 <info> installZ2mContainer.js:55 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is starting...
pi@gladys:~ $ docker logs gladys-zigbee2mqtt

> gladys-server@ start:prod /src/server
> cross-env NODE_ENV=production node index.js

Initialising OpenZWave 1.6.1051 binary addon for Node.JS.
        OpenZWave Security API is ENABLED
        ZWave device db    : /usr/local/etc/openzwave
        User settings path : /src/server/services/zwave/node_modules/openzwave-shared/build/Release/../../
        Option Overrides : --Logging false --ConsoleOutput false --SaveConfiguration true
2020-12-09T22:22:12+0100 <info> index.js:16 (Object.start) Starting zwave service
2020-12-09T22:22:12+0100 <info> service.start.js:40 (Service.start) Service zwave is not configured, so it was not started.
2020-12-09T22:22:12+0100 <info> index.js:13 (Object.start) Starting usb service
2020-12-09T22:22:12+0100 <info> init.js:38 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle not attached
2020-12-09T22:22:12+0100 <info> index.js:15 (Object.start) Starting Bluetooth service
2020-12-09T22:22:13+0100 <info> index.js:19 (Object.start) Starting telegram service
2020-12-09T22:22:13+0100 <info> service.start.js:40 (Service.start) Service telegram is not configured, so it was not started.
2020-12-09T22:22:13+0100 <info> service.start.js:40 (Service.start) Service mqtt is not configured, so it was not started.
2020-12-09T22:22:13+0100 <info> index.js:20 (Object.start) Starting Open Weather service
2020-12-09T22:22:13+0100 <info> service.start.js:40 (Service.start) Service openweather is not configured, so it was not started.
2020-12-09T22:22:14+0100 <info> index.js:63 (Server.<anonymous>) Server listening on port 1080
2020-12-09T22:23:54+0100 <info> init.js:49 () Zigbee2mqtt USB dongle attached to /dev/ttyACM0
2020-12-09T22:24:11+0100 <info> init.js:49 () Zigbee2mqtt USB dongle attached to /dev/ttyACM0
2020-12-09T22:24:11+0100 <info> installMqttContainer.js:32 (Zigbee2mqttManager.installMqttContainer) MQTT broker is being installed as Docker container...
2020-12-09T22:24:11+0100 <info> installMqttContainer.js:33 (Zigbee2mqttManager.installMqttContainer) Pulling eclipse-mosquitto:latest image...
2020-12-09T22:24:19+0100 <info> installMqttContainer.js:37 (Zigbee2mqttManager.installMqttContainer) Preparing broker environment...
2020-12-09T22:24:19+0100 <info> installMqttContainer.js:41 (Zigbee2mqttManager.installMqttContainer) Creating container...
2020-12-09T22:24:32+0100 <info> installMqttContainer.js:55 (Zigbee2mqttManager.installMqttContainer) Zigbee2MQTT MQTT broker is starting...
2020-12-09T22:24:43+0100 <info> installMqttContainer.js:61 (Zigbee2mqttManager.installMqttContainer) Creating user/pass...
2020-12-09T22:24:45+0100 <info> installMqttContainer.js:73 (Zigbee2mqttManager.installMqttContainer) Zigbee2MQTT MQTT broker is starting...
2020-12-09T22:24:52+0100 <info> installMqttContainer.js:77 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started
2020-12-09T22:24:52+0100 <info> installZ2mContainer.js:25 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is being installed as Docker container...
2020-12-09T22:24:52+0100 <info> installZ2mContainer.js:26 (Zigbee2mqttManager.installZ2mContainer) Pulling koenkk/zigbee2mqtt:latest image...
2020-12-09T22:26:11+0100 <info> init.js:49 () Zigbee2mqtt USB dongle attached to /dev/ttyACM0
2020-12-09T22:26:11+0100 <info> installMqttContainer.js:91 (Zigbee2mqttManager.installMqttContainer) Zigbee2MQTT MQTT broker is starting...
2020-12-09T22:26:11+0100 <info> installMqttContainer.js:103 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started
2020-12-09T22:26:11+0100 <info> installZ2mContainer.js:25 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is being installed as Docker container...
2020-12-09T22:26:11+0100 <info> installZ2mContainer.js:26 (Zigbee2mqttManager.installZ2mContainer) Pulling koenkk/zigbee2mqtt:latest image...
2020-12-09T22:26:13+0100 <info> installZ2mContainer.js:29 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment...
2020-12-09T22:26:13+0100 <info> installZ2mContainer.js:35 (Zigbee2mqttManager.installZ2mContainer) Creating container...
2020-12-09T22:26:13+0100 <info> installZ2mContainer.js:29 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment...
2020-12-09T22:26:13+0100 <info> installZ2mContainer.js:35 (Zigbee2mqttManager.installZ2mContainer) Creating container...
2020-12-09T22:26:20+0100 <error> installZ2mContainer.js:46 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt failed to install as Docker container: Error: (HTTP code 409) unexpected - Conflict. The container name "/zigbee2mqtt" is already in use by container "8a9b6c463fc6d86c6d54911504b73ce1aa95b49a54e39cda80822982fabed3d3". You have to remove (or rename) that container to be able to reuse that name.
    at /src/server/node_modules/docker-modem/lib/modem.js:257:17
    at getCause (/src/server/node_modules/docker-modem/lib/modem.js:287:7)
    at Modem.buildPayload (/src/server/node_modules/docker-modem/lib/modem.js:256:5)
    at IncomingMessage.<anonymous> (/src/server/node_modules/docker-modem/lib/modem.js:232:14)
    at IncomingMessage.emit (events.js:326:22)
    at endReadableNT (_stream_readable.js:1241:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  reason: undefined,
  statusCode: 409,
  json: {
    message: 'Conflict. The container name "/zigbee2mqtt" is already in use by container "8a9b6c463fc6d86c6d54911504b73ce1aa95b49a54e39cda80822982fabed3d3". You have to remove (or rename) that container to be able to reuse that name.'
  }
}
2020-12-09T22:26:21+0100 <error> index.js:14 (process.<anonymous>) unhandledRejection catched: Promise {
  <rejected> Error: (HTTP code 409) unexpected - Conflict. The container name "/zigbee2mqtt" is already in use by container "8a9b6c463fc6d86c6d54911504b73ce1aa95b49a54e39cda80822982fabed3d3". You have to remove (or rename) that container to be able to reuse that name.
      at /src/server/node_modules/docker-modem/lib/modem.js:257:17
      at getCause (/src/server/node_modules/docker-modem/lib/modem.js:287:7)
      at Modem.buildPayload (/src/server/node_modules/docker-modem/lib/modem.js:256:5)
      at IncomingMessage.<anonymous> (/src/server/node_modules/docker-modem/lib/modem.js:232:14)
      at IncomingMessage.emit (events.js:326:22)
      at endReadableNT (_stream_readable.js:1241:12)
      at processTicksAndRejections (internal/process/task_queues.js:84:21) {
    reason: undefined,
    statusCode: 409,
    json: {
      message: 'Conflict. The container name "/zigbee2mqtt" is already in use by container "8a9b6c463fc6d86c6d54911504b73ce1aa95b49a54e39cda80822982fabed3d3". You have to remove (or rename) that container to be able to reuse that name.'
    }
  }
}
2020-12-09T22:26:21+0100 <error> index.js:15 (process.<anonymous>) Error: (HTTP code 409) unexpected - Conflict. The container name "/zigbee2mqtt" is already in use by container "8a9b6c463fc6d86c6d54911504b73ce1aa95b49a54e39cda80822982fabed3d3". You have to remove (or rename) that container to be able to reuse that name.
    at /src/server/node_modules/docker-modem/lib/modem.js:257:17
    at getCause (/src/server/node_modules/docker-modem/lib/modem.js:287:7)
    at Modem.buildPayload (/src/server/node_modules/docker-modem/lib/modem.js:256:5)
    at IncomingMessage.<anonymous> (/src/server/node_modules/docker-modem/lib/modem.js:232:14)
    at IncomingMessage.emit (events.js:326:22)
    at endReadableNT (_stream_readable.js:1241:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  reason: undefined,
  statusCode: 409,
  json: {
    message: 'Conflict. The container name "/zigbee2mqtt" is already in use by container "8a9b6c463fc6d86c6d54911504b73ce1aa95b49a54e39cda80822982fabed3d3". You have to remove (or rename) that container to be able to reuse that name.'
  }
}
2020-12-09T22:26:31+0100 <info> installZ2mContainer.js:43 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt successfully installed as Docker container
2020-12-09T22:26:31+0100 <info> installZ2mContainer.js:55 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is starting...
2020-12-09T22:26:42+0100 <info> installZ2mContainer.js:67 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt successfully started
2020-12-09T22:26:43+0100 <info> connect.js:23 (MqttClient.<anonymous>) Connected to MQTT container mqtt://localhost:1884
2020-12-09T22:26:43+0100 <info> subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/#
2020-12-09T22:26:45+0100 <info> handleMqttMessage.js:91 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt topic zigbee2mqtt/bridge/logging not handled.
2020-12-09T22:26:45+0100 <info> handleMqttMessage.js:91 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt topic zigbee2mqtt/bridge/logging not handled.
2020-12-09T22:26:45+0100 <info> handleMqttMessage.js:91 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt topic zigbee2mqtt/bridge/state not handled.
2020-12-09T22:26:45+0100 <info> handleMqttMessage.js:91 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt topic zigbee2mqtt/bridge/logging not handled.
2020-12-09T22:26:45+0100 <info> handleMqttMessage.js:91 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt topic zigbee2mqtt/bridge/info not handled.
2020-12-09T22:26:45+0100 <info> handleMqttMessage.js:91 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt topic zigbee2mqtt/bridge/logging not handled.
2020-12-09T22:26:45+0100 <info> handleMqttMessage.js:91 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt topic zigbee2mqtt/bridge/devices not handled.
2020-12-09T22:26:45+0100 <info> handleMqttMessage.js:91 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt topic zigbee2mqtt/bridge/logging not handled.
2020-12-09T22:26:45+0100 <info> handleMqttMessage.js:91 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt topic zigbee2mqtt/bridge/groups not handled.
2020-12-09T22:26:45+0100 <info> handleMqttMessage.js:91 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt topic zigbee2mqtt/bridge/logging not handled.

Intégration de mon capteur en 10 secondes, franchement c’est excellent !
Par contre si je l’intègre sur l’écran d’accueil, je vois “le nom de mon capteur - opening-sensor” qui je pense est la catégorie du périphérique.

Très beau service.

VonOx · Décembre 9, 2020, 9:53

Le log est clair ( mais faut que ça remonte dans l’UI )

message: 'Conflict. The container name "/zigbee2mqtt" is already in use by container "8a9b6c463fc6d86c6d54911504b73ce1aa95b49a54e39cda80822982fabed3d3". You have to remove (or rename) that container to be able to reuse that name.'

damalgos · Décembre 11, 2020, 5:50

Hello,

J’ai enfin utilisé mon dongle + testé du coup ton service …

Je dois le dire je suis ravi !

Le service fonctionne au poil niquel sans problème. Tout démarre rapidement, se détecte rapidement je suis content.

Il trouve mon petit capteur de température sans soucis.

Les logs sont clean. Rien à redire sur le service à part good job ! J’attend vite que ca soit merge

lmilcent · Janvier 3, 2021, 7:55

Salut @Reno

J’ai l’impression que les build pour Raspberry Pi 4 (ARMv7 32bit) ne fonctionnent pas correctement :

Docker

Comme tu peux le constater, il est taggé amd64 par le docker hub, générant une erreur lors de son utilisation sur le raspberry pi.

WARNING: The requested image’s platform (linux/amd64) does not match the detected host platform (linux/arm/v7) and no specific platform was requested 62b998e4d72215b5eb9a7cf4413df649445e0592eb8616b281691ebf1c8bc617

cicoub13 · Janvier 3, 2021, 3:00

Hello. J’ai pu tester avec l’image Docker et tout fonctionne parfaitement
Merci @Reno pour le travail et la documentation.

Pour info :

Raspberry Pi 3B+
Texas Instruments CC2531 flashé
Xiaomi Aqora Sensors

lmilcent · Janvier 4, 2021, 4:03

[EDIT]

En fait, c’était pas la bonne application : “Zigbee” au lieu de “Zigbee2Mqtt”.

VonOx · Janvier 4, 2021, 4:08

Tu va avoir des problèmes toi
L’image Gladys a déjà un conteneur Gladys qui utilise cette base de données

Voir mon message plus haut => Zigbee2mqtt : Image docker de test basée Gladys v4 - #30 par VonOx

Repart propre et refait l’essai

lmilcent · Janvier 4, 2021, 4:14

Je pensais stopper le conteneur Gladys et utiliser le tiens à la place, et donc en réutilisant les mêmes données.
C’est possible non ?

Comme tu l’as peut être vu, il fallait déjà commencer par utiliser la bonne application Zigbee2Mqtt et pas « Zigbee »…

lmilcent · Janvier 4, 2021, 4:18

J’ai cependant bien une erreur (mais cette fois la clé Zigbee est bien détectée) :

Zigbee2mqtt container failed to start: Error: (HTTP code 500) server error - Cannot restart container b4e181c1c2c85eea5ba156fc7fcddb3707cfc10d1b25d12016b942380200aa35: error gathering device information while adding custom device "/dev/ttyACM0": no such file or directory
    at /src/server/node_modules/docker-modem/lib/modem.js:257:17
    at getCause (/src/server/node_modules/docker-modem/lib/modem.js:287:7)
    at Modem.buildPayload (/src/server/node_modules/docker-modem/lib/modem.js:256:5)
    at IncomingMessage.<anonymous> (/src/server/node_modules/docker-modem/lib/modem.js:232:14)
    at IncomingMessage.emit (events.js:326:22)
    at endReadableNT (_stream_readable.js:1241:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  reason: 'server error',
  statusCode: 500,
  json: {
    message: 'Cannot restart container b4e181c1c2c85eea5ba156fc7fcddb3707cfc10d1b25d12016b942380200aa35: error gathering device information while adding custom device "/dev/ttyACM0": no such file or directory'
  }
}
2021-01-04T17:15:17+0100 <warn> service.start.js:44 (Service.start) Unable to start service zigbee2mqtt Error: (HTTP code 500) server error - Cannot restart container b4e181c1c2c85eea5ba156fc7fcddb3707cfc10d1b25d12016b942380200aa35: error gathering device information while adding custom device "/dev/ttyACM0": no such file or directory
    at /src/server/node_modules/docker-modem/lib/modem.js:257:17
    at getCause (/src/server/node_modules/docker-modem/lib/modem.js:287:7)
    at Modem.buildPayload (/src/server/node_modules/docker-modem/lib/modem.js:256:5)
    at IncomingMessage.<anonymous> (/src/server/node_modules/docker-modem/lib/modem.js:232:14)
    at IncomingMessage.emit (events.js:326:22)
    at endReadableNT (_stream_readable.js:1241:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  reason: 'server error',
  statusCode: 500,
  json: {
    message: 'Cannot restart container b4e181c1c2c85eea5ba156fc7fcddb3707cfc10d1b25d12016b942380200aa35: error gathering device information while adding custom device "/dev/ttyACM0": no such file or directory'
  }
}
2021-01-04T17:15:17+0100 <info> index.js:15 (Object.start) Starting Bluetooth service
2021-01-04T17:15:17+0100 <info> index.js:13 (Object.start) Starting usb service
2021-01-04T17:15:17+0100 <info> index.js:63 (Server.<anonymous>) Server listening on port 80

Dans la doc pour flasher ma clé, ils indiquent :

Another thing we need to take care of, is to use the « long » serial-port names!
Do NOT use the syntax like /dev/ttyUSBx.

Instead use the one like /dev/serial/by-id/usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_A8_E3_95-if00-port0!

Why should we do this?
Cause the serial-port using the enumerated-syntax can (and may will) change!
Using the /dev/serial/by-id/.... syntax will never change.
And docker, or the running linux, will find the correct associated serial-port for our device!

Il y a peut être un lien ?

lmilcent · Janvier 4, 2021, 4:20

Dans l’interface web :

On voit que ttyUSB0 est sélectionné, mais en réalité dans les logs, c’est ttyACM0 qui est utilisé et génère l’erreur.

VonOx · Janvier 4, 2021, 4:21

Nan c’est pas ça, tu as dû débrancher et rebrancher ta clé non ?

Edit: on se répond en même temps ça va être dur à suivre

lmilcent · Janvier 4, 2021, 4:21

Nope, elle est sur mon raspberry pi dans le placard électrique depuis hier

lmilcent · Janvier 4, 2021, 4:22

Et le système la détecte bien sur ttyUSB0 :

pi@gladys:~ $ ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 janv.  2 18:42 usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CC_41_DF-if00-port0 -> ../../ttyUSB0

VonOx · Janvier 4, 2021, 4:24

La conf du conteneur zigbee2mqtt n’est pas bonne et n’est pas mise à jour.

Soit tu modifie à la main, soit tu attends un Fix de @Reno

lmilcent · Janvier 4, 2021, 4:30

Je vais le modifier en attendant
J’ai trouvé le fichier /src/server # vi /var/lib/gladysassistant/zigbee2mqtt/mqtt/mosquitto.conf dans le conteneur, mais rien de relatif à ttyACM0.

Une idée du fichier à modifier ?

lmilcent · Janvier 4, 2021, 4:35

Trouvé : c’est dans /var/lib/gladysassistant/zigbee2mqtt/z2m/configuration.yaml :

serial:
#  port: /dev/ttyACM0
  port: /dev/ttyUSB0

VonOx · Janvier 4, 2021, 4:38

Oui c’est ça, par contre pas besoin de passer par le conteneur. Sur ton rpi tout est dans /var/lib/gladysassistant

Sujet		Réponses	Vues
Gladys Assistant 4.2 est disponible avec la compatibilité Zigbee2mqtt ! 🚀 Actualités	146	5684	Mai 17, 2021
Image Node 18 : Tests intégration Bluetooth Développement	41	1260	Décembre 13, 2022
Zigbee2mqtt - services démarrés mais croix rouge pour le lien Configuration	60	1832	Mai 13, 2023
Gladys et docker mqtt+zigbee2mqtt existant Configuration	14	414	Novembre 13, 2023
Pouvoir utiliser un Zigbee2mqtt externe dans Gladys [Archive] Demande de fonctionnalités zigbee2mqtt , feature-integration	67	795	Mai 6, 2024

Zigbee2mqtt : Image docker de test basée Gladys v4

Sujets connexes