I have an issue with the Zigbee module configuration.
My installation (freshly reinstalled a few minutes ago):
An Intel NUC running Ubuntu 22.04.2 LTS
A Sonoff Zigbee Dongle (ZBDongle-P)
Gladys on Docker following Pierre Gilles’ tutorial
In the Zigbee2mqtt integration module, when I enable the service, the mosquitto folders and configuration files are not created in the gladys assistant directory
When I run docker ps, the status of the gladys-z2m-mqtt container is Restarting (13).
anthony@NUC-Anthony:/var/lib/gladysassistant$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
9445326db9de eclipse-mosquitto:2 \"/docker-entrypoint.…\" 12 seconds ago Restarting (13) 1 second ago gladys-z2m-mqtt
d7e3301030ba gladysassistant/gladys:v4 \"docker-entrypoint.s…\" 7 minutes ago Up 7 minutes gladys
I tried to force the permissions of the /var/lib/gladysassistant directory to 775, but it doesn’t help: the folders and files are not created:
anthony@NUC-Anthony:/var/lib/gladysassistant$ ls -lh
total 2,8M
-rwxrwxr-x 1 root root 4,0K avril 25 22:08 gladys-production.db
-rwxrwxr-x 1 root root 32K avril 25 22:14 gladys-production.db-shm
-rwxrwxr-x 1 root root 2,7M avril 25 22:14 gladys-production.db-wal
drwxrwxr-x 2 root root 4,0K avril 25 22:08 homekit
drwxr-xr-x 3 root root 4,0K avril 25 22:14 zigbee2mqtt
Well, I’m at the limit of my knowledge (not very extensive), so I won’t be able to help you beyond that..
Have you tried restarting Gladys?
Or even restarting your NUC?
I’m in exactly the same situation. After a power cut my Raspberry Pi would power on but reboot immediately — I tried to start from a clean configuration when in the end it was the power supply that had taken a hit.
I’m in the same boat as you and honestly I’m tearing my hair out. Whether it’s a fresh setup or a restore via Gladys Plus.
And Node-RED with the serial port problem — don’t get me started.
If there are any solutions I’m open to them as well.
Out of curiosity, have you tried doing a clean install of a new OS, then reinstalling Docker / Gladys afterwards?
Because what’s surprising is that it’s a completely fresh install… Everything should be running smoothly
Which docker run command did you run? Exactly the same as on the site or did you make modifications to that command?
The folder you show looks fine, there is indeed a « zigbee2mqtt » folder that was created. Can you go into that folder and show its contents? If it contains a « mqtt » folder, can you go into the « mqtt » folder and show its contents to us?
This « path » is the internal path inside the container; in Gladys these folders will be placed on the volume /var/lib/gladysassistant/zigbee2mqtt/mqtt.
However, the logs you show do contain an error:
MQTT broker container failed to start:
Error: (HTTP code 409) container stopped/paused - Container 9445326db9de3007d75ba1408e7004302a0d15e8994d0647f4abb7fa68b7c7d9 is restarting, wait until the container is running
Nonetheless this error is not necessarily the first error you had; you find yourself in a bit of a messy situation where you have a container that keeps restarting and therefore Gladys may not necessarily see it.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
61f274b22beb koenkk/zigbee2mqtt:latest \"docker-entrypoint.s…\" 15 seconds ago Up 10 seconds gladys-z2m-zigbee2mqtt
89c67dfdb09f eclipse-mosquitto:2 \"/docker-entrypoint.…\" 50 seconds ago Up 38 seconds gladys-z2m-mqtt
d7e3301030ba gladysassistant/gladys:v4 \"docker-entrypoint.s…\" 12 hours ago Up About a minute gladys
)