Zigbee2mqtt: Docker test image based on Gladys v4

[Albenss]

And when you deleted your devices via the Z2M interface, did you check the two boxes in the pop-up, including the one that could be the cause of the issue named « Block from joining again »?

[guim31]

No, I actually paid attention to that.

[Albenss]

Look in your configuration.yml file (normally here: /var/lib/gladysassistant/zigbee2mqtt/z2m/configuration.yml) on your host if you don’t have your devices in a blocking element, I don’t exactly remember the syntax of the blocks on Z2M.

[guim31]

I only see my 3 already added devices in this file

[Albenss]

Strange, I just tested on my side, the simple deletion does not work, but the deletion with force mode works well and the re-association afterwards works well for my Xiaomi/Aqara switches…

[guim31]

I’m unlucky…!

[VonOx]

@valerimarcel

Download the Gladys v4 image with zigbee2mqtt.

Hello, this is not a Raspbian image but a Docker image.

You have an example command to test this container in the discussion

Zigbee2mqtt : Image docker de test basée Gladys v4

Tu peux changer le port et le nom de la DB Par exemple 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

[pineapple_bnj]

Hello everyone,

@Reno I’m giving you my little feedback on the module .

I had a bit of trouble at first to get everything working correctly.
I had the same issues mentioned earlier.

I had to do a clean reinstall from the gladys v4 image.
Then stop the classic GladysV4 container and its Always restart.

Then install your docker image.

Only then did I go to the gladys configuration interface.

At the first activation of Zigbee2mqtt, I let it time to install everything and refresh.
Same, I had no connection between gladys => mqtt and zigbee2mqtt.

I had to deactivate zigbee2mqtt, wait a bit and reactivate it and then everything worked correctly.

I paired 2 Tradfri - Smart Plug from IKEA.

So well done great job

[guim31]

After too many manipulations I broke everything…! Haha

So I noticed something strange:

zigbee2mqtt is « running » but stopped…

[VonOx]

Is the container running?

docker ps -a

[guim31]

No, it’s not… That’s exactly why it seems strange to me.

[guim31]

Well, I ended up removing everything / restarting everything.
I’m back with my double switch that only reports battery information, but not the switch function.

[guim31]

The good news is that my water leak detector is perfectly recognized right away!!

[pineapple_bnj]

I have a question, I admit that even as a dev I have never looked into docker.
I have understood the concept and I have roughly skimmed over it, that’s all.
I know that docker is quite powerful, however, I just want to make sure @Reno.
Your docker image gladys zigbee2mqtt cannot logically be updated by watchtower to version 4.0.2 since this zigbee2mqtt image is =/= the base Gladys image, we agree on that, right?
And if the answer is no, when will there be a definitive integration of Zigbee2mqtt into the future version of gladys?

[VonOx]

@pineapple_bnj

Your Docker image for gladys zigbee2mqtt cannot logically be updated by watchtower to version 4.0.2 since this zigbee2mqtt image is not the same as the base Gladys image, right?

No, because it’s not the same image

gladysassistant/gladys vs r6n0/gladys-zigbee2mqtt

@pineapple_bnj

And if the answer is no, when will there be a final integration of Zigbee2mqtt in the future version of gladys?

We hope that @Reno will give us a nice Christmas gift

[pineapple_bnj]

@VonOx Thanks for the clarification, that makes sense but it’s good to be sure

And yes haha :D!

[guim31]

@VonOx

We hope @Reno will give us a nice Christmas present

@Reno the present! The present! The present!

[Reno]

I just updated the test image based on v4.0.2.
The images for RPi will be available within 30 minutes (build in progress).
I fixed a few bugs, including the connection issue after service installation.

I also created the PR (#996). You can leave your bug comments and suggestions there. @VonOx

Now I need to start coding the tests…

PS: the image must be updated manually:

docker pull r6n0/gladys-zigbee2mqtt:latest
docker restart gladys-zigbee2mqtt

[Jean34]

I will test this tonight and file a bug report if there are any…

[Jean34]

Hello, I installed it yesterday but the connection is not working

I tried disabling/enabling Zigbee2mqtt, but there was no change. Here are the logs:

> 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-03T21:48:53+0100 <info> connect.js:38 (MqttClient.<anonymous>) Connected to MQTT server mqtt://localhost
2020-12-03T21:48:54+0100 <info> subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic gladys/master/#
2020-12-03T21:48:54+0100 <info> index.js:20 (Object.start) Starting Open Weather service
2020-12-03T21:48:54+0100 <info> service.start.js:40 (Service.start) Service openweather is not configured, so it was not started.
2020-12-03T21:48:55+0100 <info> init.js:49 () Zigbee2mqtt USB dongle attached to /dev/ttyACM0
2020-12-03T21:48:55+0100 <info> index.js:15 (Object.start) Starting Bluetooth service
2020-12-03T21:48:56+0100 <info> subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic stat/+/+
2020-12-03T21:48:56+0100 <info> subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic tele/+/+
2020-12-03T21:48:56+0100 <info> index.js:16 (Object.start) Starting zwave service
2020-12-03T21:48:56+0100 <info> service.start.js:40 (Service.start) Service zwave is not configured, so it was not started.
2020-12-03T21:48:56+0100 <info> index.js:13 (Object.start) Starting usb service
2020-12-03T21:48:56+0100 <info> index.js:19 (Object.start) Starting telegram service
2020-12-03T21:48:56+0100 <info> service.start.js:40 (Service.start) Service telegram is not configured, so it was not started.
2020-12-03T21:48:56+0100 <info> index.js:63 (Server.<anonymous>) Server listening on port 1080
2020-12-03T21:53:46+0100 <info> init.js:49 () Zigbee2mqtt USB dongle attached to /dev/ttyACM0
2020-12-03T21:53:46+0100 <info> installMqttContainer.js:91 (Zigbee2mqttManager.installMqttContainer) Zigbee2MQTT MQTT broker is starting...
2020-12-03T21:53:46+0100 <info> installMqttContainer.js:103 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started
2020-12-03T21:53:46+0100 <info> installZ2mContainer.js:55 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is starting...
2020-12-03T21:53:46+0100 <info> installZ2mContainer.js:67 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt successfully started
2020-12-03T21:53:47+0100 <warn> connect.js:33 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-12-03T21:53:47+0100 <warn> connect.js:42 (MqttClient.<anonymous>) Disconnected from MQTT server
2020-12-03T21:53:52+0100 <warn> connect.js:33 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized
2020-12-03T21:53:57+0100 <warn> connect.js:33 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: Connection refused: Not authorized

I also tried a docker pull r6n0/gladys-zigbee2mqtt:latest, but I received this error

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit