Roger Light

I also tested and did not see incorrect behaviour. Please bear in mind that the important behaviour is whether the messages are delivered to the client or not, whether mosquitto...

I'm looking into this now. Just for your information though, you can also do this, which I personally find more convenient: ``` mosquitto_sub -p 1883 -v -t '$SYS/broker/clients/connected' -t '$SYS/broker/clients/total'...

This behaviour isn't supported in 2.0.x, but is possible with the upcoming 2.1 release. It expects to load a config file from a path based on the name of the...

Hmmm, I can see what is happening here but I'm not sure what the correct response is. I'm still thinking about the correct response. One way of looking at it...

Thanks for the analysis @ptjm, I'm not sure I agree about your final point though. dummypthread.h is only included in the mosquitto code, so it only affects the mosquitto code...

If this is still a problem for you, I'm afraid I can't do much about the version on ubuntu 20.04 directly. I would suggest looking at the mosquitto project ppa:...

You used the `-l` option to mosquitto_pub - did you provide any input to mosquitto_pub on stdin? I would suggest a simpler command for initial testing: ``` mosquitto_pub --url mqtt://testuser:[email protected](mailto:[email protected]):9530/test_topic/dada...

This sounds like a sensible addition to me, I'd be happy to have a PR for it. Given the nature of the SAN, I agree that the more flexible approach...

@kaisBou mosquitto is compliant with MQTT v5.0 and v3.x. I'm afraid if your client has problems connecting it's likely there is a problem with the client. Note there are also...

@karlp I've checked, and it's been like this forever. I'm mostly inclined to say that we should just change the behaviour (and for QoS 2) without an option. For people...