david-cermak

@garudaonekh Could you please provide a simple project that would exhibit his problem?

Closing for short of feedback. Please reopen if needed with more details.

Closing as MQTTv5 was merged in https://github.com/espressif/esp-idf/commit/5a7b17ff7d39e3768a1ee5a7fe6b04f8dca7f3be and the examples are available in https://github.com/espressif/esp-idf/tree/release/v5.0/examples/protocols/mqtt5

@liang-zhu-zi Good point, thanks for noticing! Please feel free to file a PR with this update of documentation. will be happy to accept it and merge. (otherwise, will fix later)

Hi @egnor We have already branched-off of the `v4.x` support, just to keep the code simple(-er), with less `#ifdef`'s. There's a branch [`idf_v4.x`](https://github.com/espressif/esp-mqtt/tree/idf_v4.x) for IDF

Sorry for the delay and thanks for updating the PR. I agree that in certain places we can (and should!) treat the timeouts as errors. Also please update the docs...

Hi @michaelgaehwiler and @someburner Thanks for reporting this problem and elaborating on a potential solution. I think the two options (separate locks, external mqtt task) you suggested make sense and...

Hi @michaelgaehwiler Thanks! Just wanted to hear the feedback to see if the proposed user-event would help and fix your issues. About the handler's arguments, it uses the standard type,...

@someburner As said above, using separate outbox locks would be my preferred choice, so yes, please, create a new issue for this. > I still need a way to ensure...

@someburner Thanks for explaining! If I understand correctly, you're trying to implement some kind of streaming with mqtt messages. Would some platform which inherently supports steaming help in your use-case?...