Access of Supla MQTT from other docker instances (Homeassistant)

[pzygmunt]

If you already have a broker, set the following in the SUPLA .env:

SUPLA_MQTT_BROKER_ENABLED=true
SUPLA_MQTT_BROKER_HOST=broker.ip.address
SUPLA_MQTT_BROKER_TLS=false (you can change this to true if you enable SSL in your broker)
SUPLA_MQTT_BROKER_USERNAME=your_broker's_username
SUPLA_MQTT_BROKER_PASSWORD=user_password
SUPLA_MQTT_BROKER_PORT=1883 (8883 if you have SSL)

The instructions you found online refer to cloud.supla.org where the broker is automatically available.

[PeterP]

Ok, thanks.

this is now what I did (as described).

The variable names are misleading if (as I wrongly assumed) they are not fur supla mqtt broker function.

Better naming would be just
MQTT_Server_IP
MQTT_Client_User_Name
….

the Supla_MQTT_Broker….was a clear indication (at least to me) to set up an internal Broker… and that was also requested and answered in the German section as such. So I went to a completely different path thinking I set up the Broker within my self hosted environment.


But anyway : I really do not know why this is not part of Supla (in case Supla Cloud has got the feature options.) Ok, if the MQTT on public supla cloud is always the same like a separate MQTT broker as mosquitto, so some descriptions stating Supla internal MQTT were misleading too …

Now, I set this up, but I do not see a client connect in mosquitto ….

Is it only after having devices in Supla?

From Homeassistant and from my other external devoce I‘ve got a client connect in mosquitto log,
But not from Supla..

I‘m not using TLS currently because of missing certification - which seems not to have a value or being necessary on a local private network…. All instances run as containers on the same only one raspberry pi..

So I just need now to find out how I could get the connect to the mosquitto with Supla.


Sorry that I sound a little frustrated from having waisted some time on my faulty assumptions- your help is really appreciated!!

[lesny8]

https://your_domain/integrations/mqtt-broker

IMG_20260521_231501.jpg

[PeterP]

Yes I activated - and could add ‚virtual channels‘
(polish energy prices) - however the channel / virtual devices stay disconnected AND still no connect in mosquitto log from Supla….

I just want now to find out where to configure eg. the weather channel, as it does not work without city which is greyed out in the dialog.

And still need Supla connect to mosquitto.

[PeterP]

I disabled in frontend the MQTT and tried to enable/activate again but now get a message that I change settings to fast and have to wait…

This is now persistent, even after restarting the containers and starting a new session, the message is coming so MQTT isn‘t possible to activate again.

That‘s a bit strange to me….

Now after some dozen minutes I could activate again.

[PeterP]

For MQTT Broker IP address setting I use the IP address of the computer and not internal docker network IP-adresses.

For homeassistant an my external device this workd well for mosquitto but seems not working to add Supla to that.

I checked all over and over and waisting more time trying to connect my Supla to mosquitto, no success at all. I also checked all the logs. With starting/activation absolutely nothing happens. No single attempt to send via tcp anything to mosquitto. even no client registration. Supla sends nothing on activation of MQTT.

I set up a device in Supla and see all data in Supla, history etc. But useless if I could not use MQTT to use data somewhere else. Maybe I should give up the Supla MQTT ? I do not get why it‘s not getting to my mosquitto server. All others can do: Homesssistand and DTU etc… only Supla does it not.

[PeterP]

I think the main problem is partially similar to this:

https://en-forum.supla.org/viewtopic.php?t=13311

But:

I already use the mosquitto - and moreover in HA only ONE mqtt broker can be set up - AND: I learned here that the MQTT setting within Supla does NOT setup a broker but a client.

So the hint to create a bridge between 2 brokers is not possible as SUPLA (docker) doesn‘t provide any MQTT broker function if I got it right here in the forum.

So at the end I feel that an integration to HA isn‘t possible with SUPLA docker….?

Maybe I‘m wrong - but maybe you can make proposal how to proceed?

[[email protected]]

You need to have:
Supla container
Mosquitto container
Home assistant, in any way
Now Supla needs to talk to Mosquitto
HA needs to use the same mosquitto
You need to check what's on Mosquitto container logs once you connect IT in Supla.
Probably problem lies in TLS or any other security topic.

Or just they dont see each other on docker network
Paste here the logs od Mosquitto so we can evaluate

[pzygmunt]

The sula-server is always a client. At cloud.supla.org, we simply provide an additional broker due to the nature of the MQTT architecture.

In your case, you install a single MQTT broker (one mosqitto). Home Assistant connects to the broker as a client, and supla-server as a client. You don't need bridges or additional brokers. For simplicity, I suggest starting everything without TLS, especially since everything communicates locally.

[PeterP]

Hello,
yes - I observe the logs since days:
Here the log - no attempt from SUPLA to connect
Integration from HA and OpenDTU-123 as it's best - no problems: do see all data devices from OpenDTU in HA.

It's a mystery.



1779542607: mosquitto version 2.1.2 starting
1779542607: Config loaded from /mosquitto/config/mosquitto.conf.
1779542607: Bridge support available.
1779542607: Persistence support available.
1779542607: TLS support available.
1779542607: TLS-PSK support available.
1779542607: Websockets support available.
1779542607: Plugin builtin-security has registered to receive 'basic-auth' events.
1779542607: Opening ipv4 listen socket on port 1883.
1779542607: Opening ipv6 listen socket on port 1883.
1779542607: Opening ipv4 listen socket on port 8883.
1779542607: Opening ipv6 listen socket on port 8883.
1779542607: Opening ipv4 listen socket on port 9001.
1779542607: Opening ipv6 listen socket on port 9001.
1779542607: mosquitto version 2.1.2 running
1779542608: New connection from 192.168.1.88:49704 on port 1883.
1779542608: New client connected from 192.168.1.88:49704 as OpenDTU-123 (p4, c1, k15, u'myMOsquitto').
1779542616: New connection from 192.168.1.115:59299 on port 1883.
1779542616: New client connected from 192.168.1.115:59299 as Home-Assistant (p4, c1, k60, u'myMOsquitto').




Supla container => yes!
Mosquitto container => yes!
Home assistant, in any way =>yes!
Now Supla needs to talk to Mosquitto => this is what I aim for
HA needs to use the same mosquitto => yes! (works)
You need to check what's on Mosquitto container logs once you connect IT in Supla.
Probably problem lies in TLS or any other security topic. => no TLS activated - not in mosquitto not in HA not in DTU, not in SUPLA!

Connected IT in SUPLA:
One channel in SUPLA active: supla-device-linux temperature sensor of CPU (Raspberry) => works fine in SUPLA

HA <=> mosquitto <=> DTU works perfectly together where HA & mosquitto are both inside their own docker on machine 192.168.1.115
Supla is also in docker on machine 192.16.8.1.115

all join the docker network webproxy though I use that network without certificates / without https, also nginx has his docker container and is responsible for inbound traffic from webclients in my home networks.

Supla docker image as of 05/26, (latest).