Hello everyone,
to continue with the MQTT momentum, with @VonOx, we have started working on the Zigbee2mqtt integration.
In order to cover as many cases as possible, I am calling on the community to find members already using this protocol. @VonOx already allows me to validate part of the development, but his network is limited to Aqara sensors. I thank him, by the way, for his indispensable participation.
I am therefore looking for the possibility to test other types of devices, if possible devices with actuators (on/offâŠ), not just sensors.
If you feel concerned, please contact me.
Otherwise, this integration will evolve over time, according to user feedback (which is not a bad thing either).
Iâm going to create my own, the components are ordered and I will have them by mid-November. But I think I will also have sensors, temperature, humidity, opening detector, etc. And if it has a long range, I will also install this system for a garage under construction that is 30 meters from my house.
@AlexTrovato, Iâm ready to help with the integration (dev and/or testing).
I set up a Rpi for this (gladys + mqtt broker + zigbee2mqtt with dongle).
I have an Ikea smart plug and its remote, an Osram plug, and Xiaomi sensors/buttons.
I can also contribute to Sonoff: I have an outdoor RGB spot flashed with Tasmota that I would like to integrate with GladysâŠ
I also think that the mqtt documentation should be detailed a bit more as it is difficult to access. I admit that I know a little about it and I had trouble using it. I will be able to propose improvements when I master the subject a little more.
Thanks @Reno,
For the zigbee2mqtt part, I could only do the sensors, so the actuator part is still to be done.
Same for sonoff, only the switch is developed as an actuator, the RGB is to be developed.
I will contact you in PM to see if we can organize ourselves.
For the documentation, we are not literary geniuses, but precisely, your feedback and remarks are important. We can all participate
Hello everyone, @Reno has completed the development on the Zigbee2mqtt service, he was able to test other sensors and actuators.
I also believe he is writing the documentation.
Are there other testers available on this protocol?
If it might interest some of you, I found this while searching for a ready-to-use Zigbee2mqtt key.
I havenât tested it, but it seems to have good feedback
It needs to be as plug-and-play as possible, working by default without the user having to understand whatâs happening under the hood.
What I see:
When the user wants to configure the zigbee2mqtt service (and only at that moment), the service automatically launches the right containers, without the user having to enter or understand anything. An « advanced » tab can allow the experienced user to get their hands dirty if itâs really useful. If itâs not useful, thereâs no need to display it. A small explanatory sentence about whatâs happening might be useful, without drowning the beginner.
Be sure to check that itâs a Docker installation, otherwise fall back to the current solution.
You can use the dockerode library that we already use in Gladys 4
Be careful not to interfere with the MQTT service. In my opinion, given the weight of an MQTT container (itâs negligible), it would be better to launch an MQTT container dedicated to zigbee2mqtt, otherwise you might run into hard-to-understand flow problems for the user (example: I launch zigbee2mqtt, then I configure MQTT with an external MQTT to use Owntracks for example â zigbee2mqtt broken??). It would be cool if these two services were not dependent.
Be sure to delete the zigbee2mqtt + MQTT container if the user no longer wants to use the service.
Be sure to manage the different architectures: the images must be different depending on whether the user is on an ARM system (Rasp) or x86 (Synology, home server, or development machine).
Iâm on the same page.
I can now create and launch the Zigbee2mqtt container via dockerode.
In the case of a non-Docker installation (I havenât handled this case), it will therefore not be possible to use Zigbee2mqtt.
For the MQTT part, wouldnât it be a good idea to modify this service to allow entering as many brokers as the user wants, via a + button?
In this case, Zigbee2mqtt could create its own in the list.
For the rest, itâs fine with me. I hope it will be functional for the release.
Well spotted, I think in this case we need to put a warning in the UI There is a backend API that returns this I believe.
I donât think so, it might confuse the user. After all, the end user doesnât care what your service uses to communicate with Gladys, the only thing they want: is that it works all the time!
Can you create a clean PR on the Gladys repo? Given the size of your modifications, I wouldnât be surprised if there are a lot of back and forth before the merge⊠The sooner I can review the code, the sooner it saves you from having to do big refactoring
