Domoticz

Running on latest Beta on a RPi 3 (uodating basically daily), I run into the following issue since June 23rd (currently on 16097). I try to setup a MQTT connection from a python plugin (legacy framework) using the Domoticz Connection object, and Iget now a 'connection refused' status with code 111.

Code to setup the connection: Then the onConnect method has the following log line: Producing this output:
2024-06-25 11:40:29.485 fan slaapkamer: onConnect called: Connection 'Name: '192.168.86.23', Transport: 'TCP/IP', Protocol: 'MQTT', Address: '192.168.86.23', Port: '1883', Baud: -1, Timeout: 0, Bytes: 0, Connected: False, Last Seen: 1970-01-01 01:00:00, Parent: 'None'', Status: '111', Description: 'Connection refused'

Obviously I checked: the address is reachable from the Pi. Nothing changed on the MQTT server side.

Did anything change on the implementation of the Connection object?

Did this every work?

I always use 'paho mqtt' when I want to work with MQTT

Yes, it used to work like a charm for many years (oldest files in the repo already 5 years old). Interesting suggestion. Still question remains for me: did anything change to the Domoticz Connection object?

Also a bit more background info: the MQTT server is running on a remote device, a Dyson fan. So I need to setup and maintain a network connection to this remote device. Does paho do this for me? When checking their docs, they have some looping in there. I guess this is already taken care of by the onHeartbeat callbacks in the plugin framework? But can I just create those callbacks or do I need to do something with these loops? As the callbacks are not Domoticz connection regular callbacks?

Do you have an example implementation of a plugin using paho?

You can check how they done it with the mqtt mapper plugin

https://www.domoticz.com/forum/viewtopic.php?t=39279

Could it be that you need a username/password?

The MQTT mapper plugin also uses

self.mqttConn = Domoticz.Connection(Name=self.Address, Transport="TCP/IP", Protocol="MQTT", Address=self.Address, Port=self.Port)
self.mqttConn.Connect()

Yes it does need a password but that is handled via the Parameters list. I remember something about you fixing that for me in the past because I fetch the password for machine access from a connected cloud account and write that into the Parameter object from the plugin. And the Connection object doesn't take user/pwd as input:
So I guess I'll have to dive into the multithreading topic. Nice challenge I remember trying it in the past when it wasn't supported yet (so it failed).

Question: Do I need to upgrade to the extended framework to get multithreading to work or is that also supported in legacy framework? Or should I just move to extended anyway?

OK, played around a bit with paho client. Still no luck. Tried ultimately with telnet sessions: also no luck. So apparently something wrong on the transport level......

ok, final update: German reset (off course....) solved it