Yes yes I know, I’m not in a hurry 
(the login doesn’t change anything)
I had to improvise to get the 3 containers running, impossible to have the zigbee2mqtt container (I had to remove the passwords from the mqtt config to use my old container, etc.)
So normally it’s fine as the status side
However, in the logs:
Edit: it finally worked
Well done @Reno, I’ve never been so happy to see my sensors on the dashboard
2 Likes
I’m receiving my key tomorrow, can’t wait to test all this
Nice that you like it.
I hope it will work on the first try with standard installations.
I need to make a PR for the atmospheric pressure which should display in hPa.
Hello @Reno and congrats on this monstrous work!
Indeed, this is an integration that is highly anticipated and will make many people happy.
Awesome, everything needed. Great job.
Clearly. This will avoid future problems, and above all, it allows supporting people who have an external broker for MQTT but do not necessarily want to use it for Zigbee2mqtt (it wouldn’t make sense).
Small question: what do you call the mosquitto container? Its name must be clearly distinct from that of the MQTT service.
I’ll take the liberty of answering:
z2m-mqtt for mqtt
zigbee2mqtt for z2m
I think we need to establish a rule for the gladys containers, a prefix ga- for example (for gladys assistant)
I also changed the port for the broker (1884) to have both running in parallel.
For the Zigbee2mqtt container, I was thinking of using z2m-z2m but it’s not very nice! 
No, actually, I forgot, I was in such a hurry to publish the image…
Indeed, good idea. Then we need to see how to manage the existing ones because we can’t migrate like that ^^
Yes, important! Very well.
Thanks @Reno for all your work!
I can’t wait to test this quickly!
Just a quick question, I have a RPi running with the official Gladys image (v4)
Can I use your image in parallel on the same RPi without creating conflicts (by changing the ports for the UI of course)? Or would it be wise to do tests on a dedicated card for this?
You can change the port and the name of the DB
For example
docker run -d \
--log-opt max-size=10m \
--restart=always \
--privileged \
--network=host \
--name gladys-zigbee2mqtt \
-e NODE_ENV=production \
-e SERVER_PORT=1080 \
-e TZ=Europe/Paris \
-e SQLITE_FILE_PATH=/var/lib/gladysassistant/gladys-zigbee2mqtt.db \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /var/lib/gladysassistant:/var/lib/gladysassistant \
-v /dev:/dev \
-v /run/udev:/run/udev:ro \
r6n0/gladys-zigbee2mqtt:latest
1 Like
At the top @VonOx! I’ll do that and I’ll give you some feedback quickly with my Xiaomi equipment (door opening, vibration, brightness, push button, etc..)
docker logs gladys-zigbee2mqtt
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-11-16T11:59:39+0100 <info> service.start.js:53 (Service.start) Service mqtt is not configured, so it was not started.
2020-11-16T11:59:39+0100 <info> index.js:20 (Object.start) Starting Open Weather service
2020-11-16T11:59:39+0100 <info> service.start.js:53 (Service.start) Service openweather is not configured, so it was not started.
2020-11-16T11:59:39+0100 <info> init.js:38 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle not attached
2020-11-16T11:59:39+0100 <info> index.js:15 (Object.start) Starting Bluetooth service
2020-11-16T11:59:40+0100 <info> index.js:16 (Object.start) Starting zwave service
2020-11-16T11:59:40+0100 <info> service.start.js:53 (Service.start) Service zwave is not configured, so it was not started.
2020-11-16T11:59:40+0100 <info> index.js:13 (Object.start) Starting usb service
2020-11-16T11:59:40+0100 <info> index.js:19 (Object.start) Starting telegram service
2020-11-16T11:59:40+0100 <info> service.start.js:53 (Service.start) Service telegram is not configured, so it was not started.
2020-11-16T11:59:40+0100 <info> index.js:63 (Server.<anonymous>) Server listening on port 1080
2020-11-16T12:02:59+0100 <info> init.js:49 () Zigbee2mqtt USB dongle attached to /dev/ttyACM0
2020-11-16T12:03:10+0100 <info> init.js:49 () Zigbee2mqtt USB dongle attached to /dev/ttyACM0
2020-11-16T12:03:10+0100 <info> installMqttContainer.js:30 (Zigbee2mqttManager.installMqttContainer) MQTT broker is being installed as Docker container...
2020-11-16T12:03:10+0100 <info> installMqttContainer.js:31 (Zigbee2mqttManager.installMqttContainer) Pulling eclipse-mosquitto:latest image...
2020-11-16T12:03:21+0100 <info> installMqttContainer.js:34 (Zigbee2mqttManager.installMqttContainer) Preparing broker environment...
2020-11-16T12:03:21+0100 <info> installMqttContainer.js:38 (Zigbee2mqttManager.installMqttContainer) Creating container...
2020-11-16T12:03:21+0100 <info> installMqttContainer.js:52 (Zigbee2mqttManager.installMqttContainer) Zigbee2MQTT MQTT broker is starting...
2020-11-16T12:03:27+0100 <info> installMqttContainer.js:58 (Zigbee2mqttManager.installMqttContainer) Creating user/pass...
2020-11-16T12:03:27+0100 <info> installMqttContainer.js:69 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started
2020-11-16T12:03:27+0100 <info> installZ2mContainer.js:29 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is being installed as Docker container...
2020-11-16T12:03:27+0100 <info> installZ2mContainer.js:30 (Zigbee2mqttManager.installZ2mContainer) Pulling koenkk/zigbee2mqtt:latest image...
2020-11-16T12:04:10+0100 <info> installZ2mContainer.js:33 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment...
2020-11-16T12:04:10+0100 <info> installZ2mContainer.js:39 (Zigbee2mqttManager.installZ2mContainer) Creating container...
2020-11-16T12:04:14+0100 <info> installZ2mContainer.js:47 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt successfully installed as Docker container
2020-11-16T12:04:14+0100 <info> installZ2mContainer.js:59 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is starting...
2020-11-16T12:04:20+0100 <info> installZ2mContainer.js:71 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt successfully started
2020-11-16T12:04:20+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:04:20+0100 <warn> connect.js:41 (MqttClient.<anonymous>) Disconnected from MQTT server
2020-11-16T12:04:25+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:04:30+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:04:35+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:04:40+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:04:45+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:04:50+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:04:55+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:05:00+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:05:05+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:05:10+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:05:15+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:05:20+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:05:25+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:05:30+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:05:35+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:05:40+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:05:45+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:05:50+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:05:55+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:06:00+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:06:05+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:06:10+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:06:15+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:06:21+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:06:26+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:06:31+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:06:36+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:06:41+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:06:46+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:06:51+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:06:56+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:07:01+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:07:06+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:07:11+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:07:16+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:07:21+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:07:26+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:07:31+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:07:36+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:07:41+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:07:46+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:07:51+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:07:56+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:08:01+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:08:06+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:08:11+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:08:16+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:08:21+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:08:26+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:08:31+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:08:36+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:08:41+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:08:46+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:08:51+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:08:56+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:09:01+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:09:06+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:09:11+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:09:16+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:09:21+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:09:26+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-11-16T12:09:31+0100 <warn> connect.js:32 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorizedI know why
Execute these 2 commands:
docker restart z2m-mqtt
docker restart zigbee2mqtt
Then check again in Gladys
Everything is green! Thanks @VonOx!
I hope this feedback will help create a more « simple » install that doesn’t require this kind of manipulation haha
The goal is indeed that one!
However, I thought I had solved the problem because it no longer happened to me.
Another solution is to disable the service and then reactivate it from the interface.
1 Like
From what I’ve seen, the MQTT configuration is not being applied and requires a container restart.
@Reno I suggest you check what has been done on the MQTT service, have you looked at the recent changes? Some small details have been implemented to prevent this kind of bug from happening. Notably, timeouts and checks to only launch the container when it’s ready.
After a few quick tests, the tests are conclusive for the moment!!
I found four sensors:
- Door opening: OK
- 1-button switch: OK
- Vibration sensor: OK
- Light sensor: NOT OK (but I think the battery is dead actually…)
Everything is great so far! I will continue my tests a bit later.
Thanks A LOT @Reno!