When I then go to « Configuration » and switch the switch to « Enable Zigbee2mqtt », I have a red cross between Gladys and myqtt… (I specify that at each attempt, I wait for several tens of minutes as specified in the video)
I have to be disciplined, do as marked in the doc!
Enable Zigbee2Mqtt
Once your dongle is configured, Gladys needs to install two containers (MQTT and Zigbee2Mqtt) to use the dongle and communicate with all your devices. Don’t worry, all this has been automated.
As @VonOx says (who knows what he’s talking about and tries to explain it pedagogically), you’re mixing two integrations that have no connection to each other.
The MQTT integration is a dedicated MQTT integration that can be:
either configured on a broker external to Docker and/or Gladys hardware
or configured by Gladys in a dedicated eclipse-mosquitto Docker container.
This integration has no connection with zigbee2mqtt and allows, for example, to communicate with one or more Arduino(s) present on the network and connected to this MQTT server. It is also used by the Tasmota integration when the Tasmota devices are configured to communicate with this MQTT broker.
The zigbee2mqtt integration, which integrates a Docker container of the same name to communicate with Zigbee devices, as well as an « other » MQTT container (completely independent of the MQTT integration) that allows communication only between the zigbee2mqtt container and Gladys.
All of this is clearly explained in the documentation you normally refer to.
That’s all. Don’t hesitate if you need more information!
In that case, the documentation will need to be corrected, which is what I referred to in my response! I thought that both containers were necessary!
I understand that there is
a « gladys » container
an « mqtt » container that contains the Mosquitto broker
a « zigbee2mqtt » container that communicates with Zigbee devices
So a Zigbee device communicates to zigbee2mqtt, which communicates to mqtt, which transmits to gladys and Versailles High School! The two integrations mqtt and zigbee2mqtt may not be linked, but the mqtt integration is indeed necessary for the zigbee2mqtt integration to work!
However, in @Retlaw’s message, it seemed to me from his screenshot that the mqtt part was the issue… I have no doubt about the skills of @VonOx or his pedagogy, but when he says
I agree on the « two distinct services » and « influence » part, but nevertheless, if the « mqtt » integration does not need the « zigbee2mqtt » integration, the « zigbee2mqtt » integration does indeed need the « mqtt » integration to work???
This is not an issue of overbidding but of understanding, because I feel like I missed something!!
In the zigbee2mqtt integration, is there a dedicated mosquitto broker running or not? Or does it work with? Yes, I know the old ones have a hard time understanding!!!
