I tried installing everything from scratch. After some time I got to the same point as you. I had "SUPLA_MQTT_..." entries in .env, but it wasn't connecting to the broker. No logs, nothing.PeterP wrote: Sun May 24, 2026 5:02 pm With manual editing the supla.cfg file in /etc/supla-server/ and adding the correct MQTT values
and using docker kill —-signal=SIGHUP to restart the app without recreation of the container the connect works and also the HA discovery.
So the task is now on developer side. This workaround is not stable —- any tecreation/restart of containers revoke the connection.
There is a bug in latest release. supla-docker /cloud assume that the entries in .env should be SUPLA_MQTT_, but supla-server is still expecting the old names starting from MQTT_
So I removed "SUPLA_" in .env from MQTT entries and it started to work.
So thanks for reporting this problem and for your patience. We'll fix it.
