Project Jean-Jacques M

Even though it’s not recommended, it generally works (I had one a long time ago and I got rid of it after accidentally breaking the antenna ^^).

To get a clearer view you should go to the zigbee2mqtt dashboard:
the IP address of your Gladys with port 8080 at the end.

For example : http://192.168.1.12:8080

There you’ll find in the settings the button that allows you to enable pairing:

See if it works from that button :wink:

Hello and Thank you
The IP address is not responding …however I have [file:///home/jean-jacques/Images/Capture%20d%E2%80%99%C3%A9cran%20du%202024-06-14%2006-44-57.png](file:///home/jean-jacques/Images/Capture%20d%E2%80%99%C3%A9cran%20du%202024-06-14%2006-44-57.png)

I’m not sure I attached the screenshot?? I really have a lot of gaps in my knowledge.

We all have them! :wink:
Indeed, we can’t see your screenshots.

1 Like

Since I haven’t yet found the solution from the screenshot, I’ll describe it , In Settings / System / Container … /gladys-z2m-zigbee2mqtt it has been stopped for 3 days
Stopped …

Did you go and configure your dongle here:


Do you have the green arrows here:

For screenshots, you can try a simple copy-paste…

I followed this procedure… (thanks to the training). But I never got the green arrows… However, from what I

Don’t worry, I don’t think you broke anything, but we’ll need to investigate a bit.

It seems you installed Gladys on Ubuntu.
I assume you therefore have SSH access to your machine?
If that’s the case, we’ll need to take a look at the logs.

To do that, can you first show us the output of the command:

sudo docker ps -a

Keep us posted!

@MABILLE ,

I think you must be confusing some things.
When you talk about « Allow association » are you talking about this button below in the Zigbee Discovery tab?

![image|689x128](upload://lOO8KMxZnoKM2Aow9MIzr

1 Like

Hello and thank you for your availability

gladys@gladys:~$ sudo docker ps -a
[sudo] password for gladys: 
CONTAINER ID   IMAGE                       COMMAND                  CREATED        STATUS                         PORTS      NAMES
51492d9c5744   eclipse-mosquitto:2.0.15    \"/docker-entrypoint.…\"   47 hours ago   Up 44 hours                               eclipse-mosquitto
a093ba5f900d   koenkk/zigbee2mqtt:latest   \"docker-entrypoint.s…\"   3 days ago     Restarting (1) 6 seconds ago              gladys-z2m-zigbee2mqtt
56c5a37c99b2   eclipse-mosquitto:2.0.15    \"/docker-entrypoint.…\"   3 days ago     Up 41 hours                               gladys-z2m-mqtt
2edf2a2092d3   containrrr/watchtower       \"/watchtower --clean…\"   4 days ago     Up 44 hours (healthy)          8080/tcp   watchtower
a649a774e1b9   gladysassistant/gladys:v4   \"docker-entrypoint.s…\"   4 days ago     Up 44 hours                               gladys
gladys@gladys:~$

Hello … so as not to bother you any longer, I’ll put the dongle installation on hold until the Sonoff dongle is received … Thank you very much

Don’t be afraid to bother us!
We’re here to help and make sure everyone can get it working…
It looks like your ZigBee2MQTT container is restarting in a loop.
Most of the time, it’s just a configuration issue that went wrong.
We can help you investigate if you want…
Can you give us the output of the command ‹ docker logs gladys-z2m-zigbee2mqtt ›

ladys@gladys:~$ sudo docker logs gladys-z2m-zigbee2mqtt
[sudo] password for gladys: 
Using '/app/data' as data directory
[2024-06-11 08:05:11] info: 	z2m: Logging to console, file (filename: log.log)
[2024-06-11 08:05:11] info: 	z2m: Starting Zigbee2MQTT version 1.38.0 (commit #fe048e6)
[2024-06-11 08:05:11] info: 	z2m: Starting zigbee-herdsman (0.49.2)
[2024-06-11 08:05:11] info: 	zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyACM0","baudRate":115200,"rtscts":false,"autoOpen":false}
[2024-06-11 08:05:11] info: 	zh:zstack:znp: Serialport opened
[2024-06-11 08:05:12] info: 	z2m: zigbee-herdsman started (resumed)
[2024-06-11 08:05:12] info: 	z2m: Coordinator firmware version: '{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20211115,"transportrev":2},"type":"zStack12"}'
[2024-06-11 08:05:12] info: 	z2m: Currently 0 devices are joined:
[2024-06-11 08:05:12] info: 	z2m: Zigbee: disabling joining new devices.
[2024-06-11 08:05:12] info: 	z2m:mqtt: Connecting to MQTT server at mqtt://localhost:1884
[2024-06-11 08:05:12] error: 	z2m:mqtt: MQTT error: Connection refused: Not authorized
[2024-06-11 08:05:12] error: 	z2m: MQTT failed to connect, exiting...
[2024-06-11 08:05:12] info: 	z2m: Stopping zigbee-herdsman...
[2024-06-11 08:05:12] info: 	zh:controller: Wrote coordinator backup to '/app/data/coordinator_backup.json'
[2024-06-11 08:05:12] info: 	zh:zstack:znp: closing
[2024-06-11 08:05:12] info: 	zh:zstack:znp: Port closed
[2024-06-11 08:05:12] info: 	z2m: Stopped zigbee-herdsman
Using '/app/data' as data directory
[2024-06-11 08:05:14] info: 	z2m: Logging to console, file (filename: log.log)
[2024-06-11 08:05:14] info: 	z2m: Starting Zigbee2MQTT version 1.38.0 (commit #fe048e6)
[2024-06-11 08:05:14] info: 	z2m: Starting zigbee-herdsman (0.49.2)
[2024-06-11 08:05:15] info: 	zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyACM0","baudRate":115200,"rtscts":false,"autoOpen":false}
[2024-06-11 08:05:15] info: 	zh:zstack:znp: Serialport opened
[2024-06-11 08:05:15] info: 	z2m: zigbee-herdsman started (resumed)
[2024-06-11 08:05:15] info: 	z2m: Coordinator firmware version: '{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20211115,"transportrev":2},"type":"zStack12"}'
[2024-06-11 08:05:15] info: 	z2m: Currently 0 devices are joined:
[2024-06-11 08:05:15] info: 	z2m: Zigbee: disabling joining new devices.
[2024-06-11 08:05:15] info: 	z2m:mqtt: Connecting to MQTT server at mqtt://localhost:1884
[2024-06-11 08:05:15] error: 	z2m:mqtt: MQTT error: Connection refused: Not authorized
[2024-06-11 08:05:15] error: 	z2m: MQTT failed to connect, exiting...
[2024-06-11 08:05:15] info: 	z2m: Stopping zigbee-herdsman...
[2024-06-11 08:05:16] info: 	zh:controller: Wrote coordinator backup to '/app/data/coordinator_backup.json'
[2024-06-11 08:05:16] info: 	zh:zstack:znp: closing
[2024-06-11 08:05:16] info: 	zh:zstack:znp: Port closed
[2024-06-11 08:05:16] info: 	z2m: Stopped zigbee-herdsman

There are still 15 pages or even more like this one… Should I attach them??

No need to post the 15 pages, they’re messages that repeat in a loop.

The 2 lines that interest us are

Indeed: I have a password for the Gladys account… and another, a bit stronger, for the SSH connection… Should I unify them??

It’s your ZigBee2MQTT container that can’t connect to the MQTT container.
This configuration is supposed to be automatic and you shouldn’t have to do anything about it…

The simplest thing, in my opinion, would be to do the following:

  1. Disable the ZigBee2MQTT integration in Gladys.
  2. Over SSH, remove everything related to this integration: sudo rm -r /var/lib/gladysassistant/zigbee2mqtt
  3. Take a breath
  4. Re-enable the integration and redo the basic setup, making sure to select the correct dongle.
  5. Wait long enough for the configuration to complete (this can take several long minutes)…
  6. Get back to us!
1 Like

In the meantime I tried to make the two passwords the same… After that I followed the instructions and after a few minutes I ran the command docker logs gladys…

gladys@gladys:~$ sudo rm -r /var/lib/gladysassistant/zigbee2mqtt
gladys@gladys:~$ docker logs gladys-z2m-zigbee2mqtt
permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.45/containers/gladys-z2m-zigbee2mqtt/json": dial unix /var/run/docker.sock: connect: permission denied
gladys@gladys:~$

Sorry but I’m getting a bit lost in the messages (and not just that) …

Zigbee2mqtt service configuration

  • Install from Gladys

Edit

  • Configuration
USB Port /dev/ttyACM0
Dongle Texas Instruments CC2531
TCP Port 12000

Edit

  • Enable or disable the service

On the next restart of Gladys, the service will start again. Depending on the power of your machine and the speed of your network, starting this service in « Install from Gladys » can take between 2 minutes and 1 hour. It is possible to permanently disable the service from this page: Settings \u003e Services.

GLADYS

Gladys

Started



MQTT

MQTT

Started



ZIGBEE2MQTT

Zigbee2mqtt

To be honest Jean-Jacques it’s difficult to help you because the messages you send are not exactly crystal clear :wink:

First of all, remember to use the preformatted text option on the forum when you copy something that comes from your SSH commands. That makes the formatting readable (I’ve edited your previous messages accordingly).

It’s that thing, in the toolbar when you write a message :
image

Next you need to learn how to take screenshots.
For that I invite you to look on the internet, otherwise depending on the device from which you access your Gladys dashboard, you can simply use the key on your keyboard: prt sc or print screen, it copies your screen, you just have to paste it here with ctrl+v directly.

If you haven’t configured anything in Gladys yet, I think the wisest thing for you, before getting too tangled up, would be to wait for the arrival of your « final » SONOFF dongle and I’ll reinstall everything cleanly from the beginning. You can keep your Ubuntu Server install, but everything that concerns the Docker containers you’ll have to remove and recreate.

Tell us what you think :slight_smile:

No, you shouldn’t have touched the password! The SSH password has nothing to do with the Gladys password. And @guim31, by mentioning a password issue, was referring to the password for the MQTT broker of the zigbee2mqtt integration but it’s totally transparent — you can’t change it yourself from Gladys.

By the way, do you know how to take screenshots? Because you just did a copy/paste so we can’t see the images…

After running the command suggested by @GBoulvin sudo rm -r /var/lib/gladysassistant/zigbee2mqtt did you enable the zigbee2mqtt service in Gladys before checking the logs?

Otherwise, are you sure about the USB port where the dongle is connected?

You should also show us with a screenshot the USB port configuration to see the option you have.

And run the command lsusb so we can check if the chosen USB port is correct.