It’s available in the latest dev build! ![]()
Hello, I would like to test some things with zigbee2mqtt from Node-red, is there a « simple » way to know the id / password of the Mqtt container created by Zigbee2mqtt?
Well, I don’t know if this is a « simple » way, but it seems that the username/password pair is stored in a file in /var/lib/gladysassistant on your machine ![]()
Hello
Sorry for the delayed response! It’s summer ![]()
I just looked at the topic and bad news, the password is hashed (stored in an unreadable way) in the file /var/lib/gladysassistant/zigbee2mqtt/mqtt/mosquitto_passwd.
We would need to check directly in the container if we can retrieve the password in plain text. If I find it, I’ll let you know @Albenss!
As @pierre-gilles says, it is in the database, it’s the only way for the moment.
At my place, the z2m account doesn’t seem to have a password. This account is used by zigbee2mqtt to communicate with the MQTT server.
I don’t know if it’s allowed to communicate locally only or not. If so, you won’t be able to use this account to interconnect because you will send requests from outside.
Maybe @cicoub13 will have more information to provide?
Hello, from my side the only « easy » way to make the connection via NodeRed is to create a new identifier on the MQTT container via ssh
I indeed think that this is the simplest and most effective way.
There are two accounts created with the zigbee2mqtt service in Gladys.
The account z2m (which allows the zigbee2mqtt container to connect to Mqtt). You will find the login/password under the variables Z2M_MQTT_USERNAME/Z2M_MQTT_PASSWORD in the t_variable table.
The account gladys (which allows the gladys container to connect to Mqtt). You will find the login/password under the variables GLADYS_MQTT_USERNAME/GLADYS_MQTT_PASSWORD in the t_variable table.
I think the best is indeed to create a new user.
@VonOx asked me to be able to use the zigbee2mqtt service with an already existing Mqtt container (which would meet your need). I need to get to it ![]()
I made a PR that adds a few devices.
I think the priority for this integration will be feature detection or a way to be in sync with the devices on the z2m repo.
The exposes is the solution to our issues