But I can’t pair the sensors. I have allowed the association, I keep the sensor button pressed and the LED blinks, I click on Scan and nothing appears. Here are the logs:
Yes, that’s what I thought. I had connected it to ttyACM0 in the interface.
I changed it last night to ttyUSB0 but it didn’t make any difference.
I just unplugged it, saved the config with ----- as the adapter so that Glagys recognizes that the dongle is no longer there (if you don’t save, it still indicates that the adapter is present even after refreshing the USB device list).
I plug it back in and choose ttyUSB0, I activate Zigbee2mqtt
I have the red cross between MQTT and ZIGBEE2MQTT, even after a few minutes…
I go to Zigbee Discovery, I start a scan and I go back to Configuration so that the cross becomes a green tick (it’s the only way I’ve found to make the tick green)
I have the same logs.
I have a question: should I use the Gladys v4.6.0 installation or is this a test image?
I did the manipulations with Gladys v4.6.0
Your USB dongle change in the interface was not taken into account (you should have ttyUSB0 in the second command). I will try to reproduce (and fix if there is an issue). In the meantime, you can:
delete the gladys-z2m-zigbee2mqtt container
properly select ttyUSB0 in the integration
disable/enable the service in the Configuration page
I will first stop the container before deleting it.
Should I also delete the gladys-z2m-mqtt container?
I unplugged the dongle and plugged it back in.
The only adapter found in Gladys is ttyAMA0…
No, there is no name, and I only have AMA0 now, even after refreshing the USB adapter list.
I changed the dongle port on the powered hub connected to the rpi, but that didn’t change anything.