Hello community,
I developed quite a few things between Gladys and Node-Red using MQTT before the integration was developed, and everything worked perfectly.
I have a process in Docker (gladys-node-red) that starts. I suppose it’s that integration I must have configured at some point, but I don’t use it because I go through MQTT.
The problem is that I’ve had a lot of errors for a few days which don’t affect the overall Gladys/Node-Red operation but produce many messages:
These messages disappear when I « stop » the process in Docker. So it is indeed the one causing these messages.
I don’t want this process to start automatically at machine reboot.
Can anyone provide a solution, please?
Unless it’s possible to configure everything properly so as to no longer have these rather resource-hungry errors.
Thanks ![]()
