Issues with ZigBee2Mqtt

Hello, I have a ZigBee2Mqtt issue. I am currently using two Gladys instances, one V3 and one V4, on two Raspberry Pi devices. The V4 was installed from version 4.1.0 and is regularly updated. I am now on version 4.3.0. I decided to use Sonoff devices from the MiniR2 Wi-Fi or ZBMini ZigBee range, all with the goal of replacing the Gladys V3, which operates with RF433Mhz interfaces.

Initially, I wanted to use ZigBee2Mqtt. I purchased a ZigBee USB key, which I installed. The configuration was validated in the settings and enabled in the configuration, but there was no green checkmark between Gladys MQTT and ZigBee2Mqtt, although it started. During the ZigBee scan in discovery, I received a response « Gladys is not accessible. Â» Then, I lost the ZigBee2Mqtt icon in the ZigBee service status.

I asked if it was possible to integrate ZBmini into the Hue service, as it is not currently recognized. On the other hand, the MiniR2 works very well with eWelink, so I would go down that path if ZigBee2Mqtt does not work. Thank you for your help.

The zigbee2mqtt service status shows that all services are operational or not?

You can easily check by accessing the Gladys URL, but on port 8080.
For example: http://192.168.1.10:8080

You should see a web interface, which is not Gladys but corresponds to the module used by the Zigbee2Mqtt service.

Hello Imilcent, :blush:I just tried to log in to the Gladys URL without success (site inaccessible)

At my place, Gladys is accessible on the IP 192.168.1.53 and the « Zigbee2Mqtt Â» project is accessible on 192.168.1.53:8080.

If you don’t have any web page loading, it seems nothing is launched or started.
Have you tried restarting your Raspberry Pi?

Hello. You should check the Docker container logs.
Do you know how to SSH into the Raspberry Pi?

docker logs gladys
docker logs gladys-z2m-zigbee2mqtt
docker logs gladys-z2m-mqtt

Hello cicoub13, yes I know how to connect via SSH, but I’m not so good at writing commands :lying_face: I assume I need to type these commands as you wrote them with sudo in front.

Yes, that’s right.

docker logs gladys
docker logs gladys-z2m-zigbee2mqtt
docker logs gladys-z2m-mqtt

You can copy and paste the logs into a code block:

```
logs
```

Ok..!! I’ll do that, just one more small question, how do I transfer the data to the forum?

Thank you.

Copy / paste :sweat_smile:

ah..!! alright, there must be a big piece of toast.

@lmilcent I edited your post, no need to be root, we’ll avoid any mischief :wink:

Try to see if you notice any errors or interesting things

If the user « pi Â» has been added to the docker group, then yes, it is not necessary.

I tried to send everything but the copied file is too large, I’ll see if I can’t send it to you in image format, but even then, it’s split into 301 image files :sob: if you can tell me what you’re interested in finding, I’ll look for it. :hot_face:

Otherwise, I suggest you restart the containers and then display the logs from the last few minutes.

# Restarting the 3 containers
docker restart gladys gladys-z2m-mqtt gladys-z2m-zigbee2mqtt

# Displaying logs from the 3 containers
docker logs -f --since 1m gladys
docker logs -f --since 1m gladys-z2m-mqtt
docker logs -f --since 1m gladys-z2m-zigbee2mqtt

You can adjust the --since 1m (number of minutes) according to the time you want, of course :wink:
There will be far fewer logs displayed!

Ok, I’ll do that, in the meantime I’ll send you the first 10 images!










Yes, that’s standard on the Gladys image.

It’s weird these logs, it doesn’t look at all like the ones I have. Had you just restarted Gladys?

How did you install it (Gladys)?

These logs correspond to connection errors to Gladys Plus, which is normal since you canceled your subscription in July 2020 :slight_smile:

I would advise you to remove the connection to Gladys Plus in your settings, otherwise you will have a lot of logs since your instance tries to reconnect to an account that no longer exists

By the way, it’s you who’s been constantly trying to connect to Gladys Plus and getting 403 Forbidden errors for months :joy: I’ve seen connection attempts for a while now and was wondering who it was! ^^