New version 4.7: Graphical display and major Zigbee2mqtt integration update!

After installing Gladys on another Raspberry Pi, I plug in the key and it is correctly recognized, and I can save to the new Raspberry Pi.

It must therefore be a Docker configuration issue.

Just keep on scratching…

Which Raspberry image are you using, which Docker command did you run?

I used Bulleye as indicated below:

PRETTY_NAME=« Debian GNU/Linux 11 (bullseye) »
NAME=« Debian GNU/Linux »
VERSION_ID=« 11 »
VERSION=« 11 (bullseye) »
VERSION_CODENAME=bullseye
ID=debian
HOME_URL=« https://www.debian.org/ »
SUPPORT_URL=« Debian -- Assistance aux utilisateurs »
BUG_REPORT_URL=« https://bugs.debian.org/ »

And the commands used to create the container are those from Pierre-gilles’ tutorial.

OK so it’s not the Gladys image but the official Raspberry Pi image.

The tutoring? The documentation?

All commands used are as follows: Installation avec Docker | Gladys Assistant

Strangely, I have the same issue as @gsr_oyo with the Gladys configuration on Docker. What’s surprising is that I had done tests with the beta and I had no problems (always with Docker). What’s different in my main configuration is that the system is on an SSD, whereas all the tests I did on the beta were with an SD card. The SSD consumed too much power and as a result the SONOFF key didn’t work well. In this case, I’m using a powered USB hub. But whether I plug the key into the hub or directly into the Raspberry Pi, it appears, but I can’t save the configuration. I haven’t yet looked in detail at how to analyze the issue, but for now I’m stuck on the deployment of Zigbee2mqtt.

UPDATE: I just reinstalled the dev version of the Docker container and this time it works on its own. There’s something with the production version I think.

Do you have a specific error in the logs?

It’s resolved, the problem was me!

To start Gladys, I was using an old version of the Docker command line without the cgroupns parameter (just the important thing to manage cgroups v2 I guess).

I noticed that the documentation had been updated. I restarted with the correct command line and everything seems to work perfectly. I’ll finally be able to set up the complete configuration of my office with all the sensors I bought.

Sorry for being a fool.