Raymond
Raymond
Yes, I know it does not depend on the MQTT connection. It is the connected status of the specific implementation of the communication channel (espMqttClientInternals::Transport* _transport). The issue is independent...
yes, I am using the regular version.
> But please keep in mind, that OpenDTU uses the AsyncTCP approach Yes, you are right. But to drill down the problem, I used my own small little test. I...
Hi! I guess you mean **_transport**->disconnected() instead of **_client-**>disconnected()
For a swift response, I've integrated your code changes into my OpenDTU setup and have started and killed my ioBroker Docker many times. So far, your solution seems to be...
"Mind that in the Transport implementation client.disconnected() is implemented as !client.connected(). simple as that." I hope I’m not misunderstanding your concerns. Indeed, that’s why I suggested adding an extra time...
The behavior heavily depends on the implementation of the Transport interface class. In the Async version, future code changes could lead to a situation where connected() is equivalent to !disconnected(),...
Hello, For your information, OpenDTU runs stable with the current modifications until now. It always reconnects to ioBroker without any problem. Regards!