@dnpwwo Thanks, i now understand much more things: the timeout flag is just a way to set the red banner to the sensor and it is my plugin responsability to set this value according to a specific timeout ... is there a way (from my plugin) to access to the value of the Domoticz's data timeout (used ...

@dnpww0 Hello, i noticed that whenever i create sensors through my plugin (see previous post), these sensors won't ever turn in red if data does not arrive during the specified amount of time (as in settings). On the other hand, it works perfectly for sensors that have been added via others ways ...

@dnpwwo ... it was the 'Hey' in your code that lead me to think that this 'Test' message was yours ... while it was an old greetings no one remembered ;) Thank you for the debug codes, the connack and suback ways to manage. The plugin is now working and automatically create sensors upon MQTT message ...

@Dnpwwo ah ok, thanks for your explanation ... anyway, i've not been able to find this 'TestHey' in your code ... and it occurs every time i subscribe to a topic (and it features a retain=True field!!). I'm running the latest git version in a docker. Now if you look at the onConnect, this is where ...

@Dnpwwo Ok thanks for your answer. What was a bit strange for me is that we usually let the client set a random clientID. However, this kind of <<double connect>> (i.e you connect via MQTT AND you use Connect.send ??) I also noticed a 'testHey' ... probably for you to check that we've successfully ...

Hello, One related question regarding your new MQTT Subscribe/Publish sample codes: def onConnect(self, Connection, Status, Description): Domoticz.Debug("onConnect called ...") if self._shutdown is True: return if (Status == 0): Domoticz.Debug("MQTT connected successfully ...") sendData = { 'Verb ...