Are you saying that when using a different commit from https://github.com/espressif/esp-mqtt than the one specified in idf, then mqtt connection worked and with the default one did not? Can you please share the exact commit id's of esp-idf and esp-mqtt which you used for the version with worked and ...

ok, so there no issue with dns resolution and iot.eclipse.org is accessible from your network, so the only issue I can think of might be a blocked port 1883. can you please check there's no firewall involved and/or this port is enabled in your network? another option is to check out the ws example w...

Hi George, The error `Error transport connect` means that a connection to a broker cannot be established and since it's a tcp connection it could be caused by: - not resolving the dns name - socket connection error Which broker are you connecting to, is it the default iot.eclipse.org:1883? Is this s...

Thank you Doug. Yes, the fix should be available in few weeks time.

As for the bug fixes / features per releases: https://github.com/espressif/esp-idf/releases

For the stable 3.3 release I cannot really say, as there's still 3.2 which should come before.

Hi Dough,

This actually is a bug -- wrong total_data_len in data event when multiple mqtt messages packed into a read buffer.

Will be fixed soon, or I can provide a quick patch if needed.

Hi Doug, I believe that what you describe is an intended behaviour. Message can be broken down to more 'data-received' events. Can you please check that the message id is the same for both parts? There's also some more info such as total/remaining message length within the data event to help you tra...

Hi Doug, Which bug are you referring to? AFAIK there are/were currently 3 limitations of the library: 1) Wrong reception of retained messages (e.g. when one TCP packet contain multiple MQTT messages) 2) Library is not thread safe 3) Messages (with qos>0) sent while client went off-line are not being...

Hi, Please make sure you have typed the host name correctly. I see some underscores between address bytes in your post, it should be <menuconfig-name>_XXYYZZ, where XXYYZZ are last 3 numbers from MAC in hex. Please try to locate this line in the log? I (239) mdns-test: mdns hostname set to: [esp32-m...

Hello Are you running the mdns example from release3.1? No modification, default configuration (besides the wifi credentials)? This should work normally and indeed it does in my environment. I can browse for advertised services (checked with avahi on linux and dns-sd on macos) as well as resolve pub...