Hello,
I just looked at
Mmm, normally no !
Maybe your mosquito was updated by Watchtower ?
Yes, restarting mosquito could be an option, but I’m not sure that will solve the issue
Restarting the container didn’t change anything…
And on the Gladys logs side, are there logs specific to MQTT?
If you have the same problem as @Terdious and me, the mosquitto update causes the password to be lost.
If that’s the case, just click on ‹ save the configuration › on the MQTT integration configuration page
Thanks for the suggestion,
Already tried, without success.
Same here, same problem, it doesn’t change anything.
Here’s what I found :
2022-12-12T10:39:58.860305140Z 2022-12-12T11:39:58+0100 \u003cinfo\u003e index.js:15 (Object.start) Starting Tasmota service
2022-12-12T10:39:58.894700138Z 2022-12-12T11:39:58+0100 \u003cinfo\u003e index.js:14 (Object.start) Starting Xiaomi service
2022-12-12T10:39:58.924930258Z 2022-12-12T11:39:58+0100 \u003cinfo\u003e index.js:13 (Object.start) Starting usb service
2022-12-12T10:39:58.958792714Z 2022-12-12T11:39:58+0100 \u003cinfo\u003e index.js:19 (Object.start) Starting Telegram service
2022-12-12T10:39:59.035089356Z 2022-12-12T11:39:59+0100 \u003cinfo\u003e index.js:16 (Object.start) Starting RTSP service
2022-12-12T10:39:59.068245209Z 2022-12-12T11:39:59+0100 \u003cinfo\u003e index.js:18 (Object.start) Starting Philips Hue service
2022-12-12T10:39:59.165395201Z 2022-12-12T11:39:59+0100 \u003cinfo\u003e index.js:16 (Object.start) Starting MQTT service
2022-12-12T10:39:59.216947465Z 2022-12-12T11:39:59+0100 \u003cinfo\u003e updateContainer.js:13 (MqttHandler.updateContainer) MQTT: checking for required changes...
2022-12-12T10:39:59.429263971Z 2022-12-12T11:39:59+0100 \u003cwarn\u003e connect.js:50 (MqttClient.\u003canonymous\u003e) Error while connecting to MQTT - Error: Connection refused: Not authorized
2022-12-12T10:39:59.477049736Z 2022-12-12T11:39:59+0100 \u003cinfo\u003e index.js:21 (Object.start) Starting example service
2022-12-12T10:39:59.995237697Z 2022-12-12T11:39:59+0100 \u003cinfo\u003e scene.dailyUpdate.js:58 () Sunrise today is at 8:45 today, in your timezone = Europe/Paris
2022-12-12T10:39:59.999922358Z 2022-12-12T11:39:59+0100 \u003cinfo\u003e scene.dailyUpdate.js:59 () Sunset today is at 16:55 today, in your timezone = Europe/Paris
2022-12-12T10:40:00.018914541Z 2022-12-12T11:40:00+0100 \u003cinfo\u003e scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2022-12-12T10:40:00.031318657Z 2022-12-12T11:40:00+0100 \u003cinfo\u003e scene.dailyUpdate.js:81 () Sunset is scheduled, in 5 hours.
@gaetanb76 I’m stumped ![]()
@AlexTrovato @VonOx any idea what might be happening?
It’s carnage right now!!!
I think it’s saving again from the front-end. It seems the credentials are not the same between mosquitto and gladys.
Recently there was a change to get docker-compose working. Could that be related?
But unfortunately I have little availability at the moment; I’ll do my best to try to reproduce the problem.
That happened to me too; I had to re-enter the MQTT password on all my Sonoff devices and everything started working again. Once I removed the Bluetooth test, I had Zigbee problems so I started from scratch, and again had to update the MQTT passwords on my Sonoff devices. Usually after a full restart from zero I only have to re-enter the password that I save in the MQTT integration. But the worst thing about this problem is that I copy-pasted the same password — I hope that’s clear.
For info, that happened to me a long time ago too, so I don’t think there’s any link with the latest devs (before moving the RPI to the Synology NAS) ![]()
Isn’t it related to that?
