Pasi Salenius

Thanks. I already briefly tried changing a few things but it went nowhere. It might require a more thorough understanding of what is going on between all the different parts....

Hi Luis, did you find a way to fix Ubuntu support?

I have not seen this type of behaviour in my usage of the library. You could try to debug reception of data and find the cause of the lag, perhaps...

I committed quite a big update to the client today. You might want to check if it fixes the issues you were seeing.

@luisdelarosa Should the package be updated with a new version, now that I committed an update that changed sending packets from a synchronous operation to async? Would, for example, version...

This is not supported at the moment. The client library is best at simple use case of subscribing to topics and receiving messages, this is what I use it for....

@df1gr The default ping interval is 10 seconds, you can try reducing that and see if it helps. I've also seen similar behaviour with one MQTT server, and could not...

The pingInterval parameter of the LightMQTT.Options struct defines the interval at which the server expects to receive ping MQTT messages, and LightMQTT will send pings at half of that interval....

I don't think this is what causes your disconnection issues, but thanks for pointing that out. I already commited a fix for it in https://github.com/PasiSalenius/LightMQTT/commit/6074529387618f0395017347db7aa77344314429.

I'm very glad to hear that. That got me thinking I also need to make sure I wasn't accidentally using the same clientId repeatedly during one development phase.