Hello everyone.
After installing a new instance for testing (Finish the integration of the OWON PIR313-E detector), I restarted the main Gladys instance.
But the MQTT services are not working. In the zigbee2mqtt integration section, there are two red crosses among the 3 services (Gladys to MQTT and MQTT to z2m).
From the logs it seems the problem comes from MQTT.
When I run docker logs gladys-z2m-mqtt after restarting my Raspberry Pi I get:
1701943433: Saving in-memory database to /mosquitto/config//mosquitto.db.
1701943477: mosquitto version 2.0.15 starting
1701943477: Config loaded from /mosquitto/config/mosquitto.conf.
1701943477: Opening ipv4 listen socket on port 1884.
1701943477: Opening ipv6 listen socket on port 1884.
1701943477: mosquitto version 2.0.15 running
1701943493: New connection from ::1:57750 on port 1884.
1701943493: New client connected from ::1:57750 as mqttjs_290a8e33 (p2, c1, k60, u’gladys’).
1701943508: New connection from ::1:57752 on port 1884.
1701943508: Client gladys-main-instance-403308 disconnected, not authorised.
1701943510: New connection from ::1:57754 on port 1884.
1701943510: New client connected from ::1:57754 as gladys-main-instance-793152 (p2, c1, k60, u’gladys’).
1701943513: New connection from ::1:57760 on port 1884.
1701943513: Client gladys-main-instance-403308 disconnected, not authorised.
1701943518: New connection from ::1:57762 on port 1884.
1701943518: Client gladys-main-instance-403308 disconnected, not authorised.
The last 4 lines repeat indefinitely.
When I go to the zigbee2mqtt interface I have the 3 devices I used during the test, but not those from my main instance.
To restart the main instance I had first run a full docker run as in the docs. It told me the instance already existed . I then did docker stop gladys, then docker start gladys. Is there something else to do, for example to indicate which MQTT instance to target?
Try with another browser, it’s probably the password for the MQTT container configuration in Gladys that’s no longer valid but if you try to change it with Firefox it doesn’t work, the password displayed by Gladys is not injected into the configuration file but is replaced on the fly by the one in Firefox’s cache
I’ve done all that, but it doesn’t help.
I removed the container gladys-OWON-test (docker rm), I restarted Gladys, rebooted the Raspberry Pi, still no luck. I still have the red crosses, and the z2m interface still shows the 3 test devices.
After that, I don’t know if that’s normal for the z2m interface or not. I don’t know what happens when you create a test instance. Is a completely new environment recreated in the folder you specify during creation, or are there shared elements between the different instances?
Try unplugging it for 30s and plugging your USB dongle back in; if that isn’t conclusive, try another port while checking if that changes anything on the zigbee2mqtt container side.
But the Zigbee key works fine because in the z2m interface the states of my sensors change correctly when something happens.
It’s as if there were a path issue: my gladys instance is trying to connect to the MQTT and z2m instances that were generated for my gladys-OWON-test instance. I’m certainly not using the right words, but I have the feeling it’s something like that.
It seems to be a path issue, because on the Raspberry Pi I deleted the folder gladysassistant_OWON_test that had been created when I set up my test instance and now I can no longer access the z2m interface (http:adresse_ip:8080 returns: unable to access this page).
I need to be able to say somewhere that they should go look in /var/lib/gladysassistant
. I then did docker stop gladys, then docker start gladys. Is there something else to do, for example to indicate which MQTT instance to target?