Hi,
I’m evaluating Gladys for personal use. I like it a lot. But since I have mainly zigbee-devices the Zigbee2MQTT option is vital.
However I encounter an error.
MQTT and Zigbee2MQTT are running, but Gladys, MQTT and Zigbee2MQTT won’t connect to eachother. What can I do?
I’m running Gladys inside Pi OS on a Pi4B, with a native Pi-powersupply and a Sonoff ZBDongle-P plugged into the black USB-port.
EDIT: I restarted both mqtt and zigbee2mqtt in docker, but the problem remains.
Then I reviewed the logs. They show repeating patterns:
mqtt-logs:
zigbee2mqtt-logs:
Hi @alpha-rd and thanks for your message !
I’m happy you like Gladys.
The zigbee2mqtt integration is our most used integration so it’s supposed to work fine. It seems there was a very recent upgrade from Mosquitto (the MQTT broker we use), so it might be linked to that.
I’ll try to reproduce and come back to you
I confirm that I’m able to reproduce, it seems there is a bug with the 2.0.16 version of Mosquitto, there are many people complaining of the Github of similar issues ( Issues · eclipse/mosquitto · GitHub )
I’ll test again with a fixed 2.0.15 version to see if it mitigate the problem, and if yes I’ll push a Gladys upgrade.
Mosquitto 2.0.15 indeed fixes the issue.
I’ve published a fix:
GladysAssistant:master
← GladysAssistant:fix-mosquitto-version-2-0-15
opened 08:32AM - 21 Aug 23 UTC
### Pull Request check-list
To ensure your Pull Request can be accepted as fa… st as possible, make sure to review and check all of these items:
- [x] If your changes affects code, did your write the tests?
- [x] Are tests passing? (`npm test` on both front/server)
- [x] Is the linter passing? (`npm run eslint` on both front/server)
- [x] Did you run prettier? (`npm run prettier` on both front/server)
- [x] If you are adding a new features/services, did you run integration comparator? (`npm run compare-translations` on front)
- [x] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to [the community](https://community.gladysassistant.com/) for testing before merging.
- [x] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code)
- [x] If you are adding a new features/services which needs explanation, did you modify the user documentation? See [the GitHub repo](https://github.com/GladysAssistant/v4-website) and the [website](https://gladysassistant.com).
- [x] Did you add fake requests data for the demo mode (`front/src/config/demo.js`) so that the demo website is working without a backend? (if needed) See [https://demo.gladysassistant.com](https://demo.gladysassistant.com).
NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
### Description of change
Mosquitto 2.0.16 is buggy and doesn't work, so fixing the MQTT version to 2.0.15
I’ll tell you when it’s live in production
I just published Gladys Assistant v4.26.1, and it’ll automatically upgrade your container to Mosquitto 2.0.15 instead of 2.0.16 to mitigate this bug!
Note that you may need to re-save the configuration to fix the configuration file.
Don’t hesitate if you have any questions
Hi everyone!
I hope you had (or are having) a good summer vacation
On my side, I came back from holidays last Friday on Gladys and I’ve just published today an update with some fixes.
Mosquitto (MQTT) version fixed at 2.0.15
Mosquitto has released a new version of its MQTT broker, and this version suffers from a few bugs that for some of you prevent the use of MQTT and Zigbee2mqtt integration.
In Gladys, I’ve decided to freeze the version at 2.0.15 for the time being while t…
1 Like
I’ll check it and let you know. Thanks for the fast reply. I already started thinking I was doing things wrong. (And welcome back from your vacation).
1 Like