Zigbee2mqtt: Docker test image based on Gladys v4

VonOx · December 3, 2020, 10:03pm

You have to wait now that DockerHub has set limits.

I think it’s 6 hours

pierre-gilles · December 4, 2020, 7:48am

Yes, but the problem is that watchtower makes a request every 5 minutes… I’m not even sure it can do anything while waiting.

We might need to consider updating our Watchtower configuration from Gladys there ^^

Reno · December 4, 2020, 8:13pm

Thanks @Jean34.
I made a mistake in the code the day before yesterday.
I recreated the image last night and it should be good.
Looking forward to your feedback, testers!

Jean34 · December 9, 2020, 9:43pm

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 · December 9, 2020, 9:53pm

The log is clear (but it needs to be displayed in the 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 · December 11, 2020, 5:50pm

Hello,

I finally used my dongle + tested your service…

I must say I’m delighted!

The service works perfectly, no problem. Everything starts quickly, detects quickly, I’m happy.

It finds my little temperature sensor without any issues.

The logs are clean. Nothing to say about the service except good job! I’m waiting for it to be merged quickly

lmilcent · January 3, 2021, 7:55am

Hello @Reno

I think the builds for Raspberry Pi 4 (ARMv7 32bit) are not working correctly:

As you can see, it is tagged amd64 by the docker hub, generating an error when used on the 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 · January 3, 2021, 3:00pm

Hello. I was able to test with the Docker image and everything works perfectly

Thank you @Reno for the work and documentation.

For information:

Raspberry Pi 3B+
Texas Instruments CC2531 flashed
Xiaomi Aqora Sensors

lmilcent · January 4, 2021, 4:03pm

[EDIT]

Actually, it was the wrong application: « Zigbee » instead of « Zigbee2Mqtt ».

VonOx · January 4, 2021, 4:08pm

You’re going to have problems there
The Gladys image already has a Gladys container that uses this database

See my message above → Zigbee2mqtt : Image docker de test basée Gladys v4 - #30 par VonOx

Start clean and try again

lmilcent · January 4, 2021, 4:14pm

I thought I would stop the Gladys container and use yours instead, and therefore reuse the same data.
Isn’t that possible?

As you may have seen, you had to start by using the correct Zigbee2Mqtt application and not « Zigbee »…

lmilcent · January 4, 2021, 4:18pm

I still have an error (but this time the Zigbee key is correctly detected):

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

In the documentation for flashing my key, they indicate:

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!

There might be a connection?

lmilcent · January 4, 2021, 4:20pm

In the web interface:

It can be seen that ttyUSB0 is selected, but in reality, in the logs, it is ttyACM0 that is being used and causing the error.

VonOx · January 4, 2021, 4:21pm

Oh, that’s not it, you must have unplugged and replugged your key, right?

Edit: we’re responding at the same time, this is going to be hard to follow

lmilcent · January 4, 2021, 4:21pm

Nope, it’s on my raspberry pi in the electrical closet since yesterday

lmilcent · January 4, 2021, 4:22pm

And the system does detect it on ttyUSB0:

pi@gladys:~ $ ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 Jan  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 · January 4, 2021, 4:24pm

The zigbee2mqtt container config is not good and is not updated.

Either you modify it manually, or you wait for a fix from @Reno

lmilcent · January 4, 2021, 4:30pm

I’ll modify it in the meantime
I found the file /src/server # vi /var/lib/gladysassistant/zigbee2mqtt/mqtt/mosquitto.conf in the container, but nothing related to ttyACM0.

Any idea which file to modify?

lmilcent · January 4, 2021, 4:35pm

Found: it’s in /var/lib/gladysassistant/zigbee2mqtt/z2m/configuration.yaml:

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

VonOx · January 4, 2021, 4:38pm

Yes, that’s it, but there’s no need to go through the container. On your Raspberry Pi, everything is in /var/lib/gladysassistant

Topic		Replies	Views
Gladys Assistant 4.2 est disponible avec la compatibilité Zigbee2mqtt ! 🚀 Actualités	146	5671	May 17, 2021
Image Node 18 : Tests intégration Bluetooth Développement	41	1258	December 13, 2022
Zigbee2mqtt - services démarrés mais croix rouge pour le lien Configuration	60	1814	May 13, 2023
Gladys et docker mqtt+zigbee2mqtt existant Configuration	14	411	November 13, 2023
Pouvoir utiliser un Zigbee2mqtt externe dans Gladys [Archive] Demande de fonctionnalités zigbee2mqtt , feature-integration	67	791	May 6, 2024

Zigbee2mqtt: Docker test image based on Gladys v4

Related topics