Ok, I’m not very familiar with MQTT Explorer (I was referring to MQTT X), I assume the topics shown on the left are those that have had a publication since you opened the software.
If you just opened the application, that means an MQTT message was sent from Node-RED to Mosquitto and then to Gladys.
If that’s the case, then there’s no issue on that side, but rather on the Node-RED side, right?
OK, no problem, but when I have fixed this MQTT issue.
I’ve also made an 8-day weather forecast screen (not finished yet but well advanced); I base it on the data from my weather station which are sent and retrieved via Weather Underground (API).
I’d like to integrate it one day into my Gladys dashboard.
Hi again,
I didn’t know mqttx, I’m in the process of installing it.
Regarding what I sent you, from your analysis, maybe a Node-RED problem but then why does it correctly feed its dashboard
No idea, you’re the one who programmed your Node-RED flow 
You need to debug on the Node-RED side to see if everything you’ve programmed is working properly.
Add logging to Node-RED, run manual tests, that sort of thing 
I’ll try to dig into Node-RED but I’m skeptical — MQTT has been updated and it’s Node-RED that would be buggy?
On my flows I already have control points at almost every node and no errors reported, with correct reporting of the data to the integrated Node-RED dashboard (the data are the same)
I’ll try to create another flow with MQTT and different data, we’ll see
That’s a suggestion! Keep us informed of the different tests you do, don’t forget to test all the cases I listed for you here: Problème connexion à MQTT après mise à jour de mosquitto par watchtower - #14 par pierre-gilles
I remember that I had this problem and I had to change the password on both sides, then revert to the original password on both sides, and afterwards it worked again — but is that the solution? Maybe default passwords were set following an update on the Gladys side or the MQTT side.
ok, no problem, but I’m going to take it slowly! Retired with a few minor health issues and lots of things keeping me busy, I no longer have the same level of productivity as in the past but my mind is still sharp…
Hello,
I just upgraded to MQTT 2.0.16 and it broke updates for some topics.
The messages are published from Node-RED and the problem concerns updating several topics simultaneously.
My mistake was in the MQTT publish settings in Node-RED; I had set the QoS to 2 even though I wasn’t using it. After changing the QoS to 0, it works again.
I’m not sure it’s the same problem as yours.
Hi everyone!
I’ve heard other reports that the Zigbee2mqtt / and MQTT integrations no longer worked during a new installation.
I tested it myself, and I get the same result — on a fresh installation, the installation no longer works:
configureContainer.js:26 (MqttHandler.configureContainer) MQTT broker Docker container is being configured...
configureContainer.js:43 (MqttHandler.configureContainer) Writting default eclipse-mosquitto configuration...
installContainer.js:35 (MqttHandler.installContainer) Creating container...
installContainer.js:43 (MqttHandler.installContainer) MQTT broker successfully installed as Docker container
installContainer.js:63 (MqttHandler.installContainer) MQTT saving configuration
installContainer.js:73 (MqttHandler.installContainer) MQTT installed
connect.js:50 (MqttClient.\u003canonymous\u003e) Error while connecting to MQTT - Error: Connection refused: Not authorized
From what I read online, there are indeed issues with Mosquitto 2.0.16.
I’m going to try pinning the image to 2.0.15 in Gladys to see if that actually fixes the issue.
Good news, 2.0.15 is working well 
I opened a PR:
I’ll let you know when it’s live in production
@PhilippeMA
hello,
I was indeed on my Node-RED MQTT node at QoS 2.
I also switched to 0, and additionally to MQTT 5 (whereas previously 3.1.1) (apparently the MQTT versions in the Node-RED node do not correspond to those of Mosquitto (why?)).
In the end, for now it’s working again, but I’ll wait a bit before finalizing the solution because I like to have some distance and try with new Node-RED scripts. The side effect of the MQTT-Mosquitto update on Node-RED and indirectly on Gladys seems odd to me. Maybe another MQTT update will come if too many issues are observed?
The Mosquitto version is now pinned to 2.0.15 in Gladys Assistant v4.26.1:
The container will be updated automatically; however, for new users, or those who have overwritten their configuration file, you may need to re-enter the MQTT password in Gladys so that Gladys overwrites the configuration file.
Thank you for your feedback 
MQTT had been broken for me since yesterday too.
Even though I’m on 4.26.1 it still didn’t work when I got home from work today.
I had to retype my MQTT password and save the configuration (as indicated by GBoulvin above) for it to work again.
Same here.
I needed a configuration backup on the MQTT integration side to get everything back in order
Same for me …
That doesn’t surprise me, version 2.0.16 clearly has a bug in generating the config file, it’s possible your previous file was overwritten and needs to be re-generated
We won’t have this issue going forward if we stick to « fixed » versions like this with a manual update process testing each version.
hello,
for my part, upgrading to 4.
Hello,
I also have a bug with the Gladys MQTT broker since August (last reading from a temperature sensor). I didn’t notice the connection stopping because I use Gladys mainly to manage Tempo days.
I therefore tested stopping the broker from Gladys but the MQTT configuration page always reverts to the configured settings: Switch, ID and password enabled.
I disabled the MQTT service in Gladys settings but the same result.
So I stopped the Mosquitto container, but the result was identical.
I restarted my Pi and the Gladys container but nothing works, it’s impossible to modify the MQTT, ID, or password settings in Gladys.
It’s as if Gladys’s MQTT configuration page is completely broken.
I haven’t tried launching a Mosquitto container because I find it very convenient to configure the MQTT broker from within Gladys.
All actions were performed on version 4.31.
We will need logs and screenshots to try to unblock you.