esp-mdf mqtt cannot subscribe topic

[sapparatus]

Using the example in esp-mdf mqtt, the publish topic works fine but when you try to subscribe a topic, the payload does not come to the mesh, the root node seems no knowledge about there is a topic it subscribed, e.g. "mesh/ffffffffffff/toDevice" topic but none of the mesh node receives anything?

[PeterR]

in esp-mdf mqtt, the publish topic works fine

What makes you think that publish worked fine? Guess you are QoS0?

but when you try to subscribe a topic, the payload does not come to the mesh

What return code did you get from esp_mqtt_client_subscribe()?

You have not told us anything about your MQTT server. Do you have an MQTT server & if so which one & where?

[sapparatus]

I have an internal mqtt server that receives all mesh messages from all nodes

on the root node, I put some lines so i see it is subscribing topics:


I (13052) [MESH_MQTT, 241]: =============== mymesh/b4e62db8661d/toDevice subscribed ==============================
I (13060) [MESH_MQTT, 246]: =============== mymesh/ffffffffffff/toDevice subscribed ==============================
I (13071) [MESH_MQTT, 251]: =============== mymesh/ff0000010000/toDevice subscribed ==============================
I (13081) [MYMESH, 331]: MQTT Topic subscribed

but when you send message to these topics, none is responding with "Node receives:"

[PeterR]

It is not clear what you mean. The new line without full stop makes the two first lines unclear. Are you saying that your root node is the MQTT server? Which MQTT server did you use?

Also produce a log of one of the ESP MQTT client's setup & return status codes.

Did you esp_mqtt_client_register_event()?

[clif123]

I'm interested in knowing if anyone has gotten the ESP-MDF MQTT example to work out of the box. I tried both the 1.0 and master from a few days ago with no success. Specifically, the root node obtained an IP address on the router but no MQTT traffic ever flowed over the router's network. I posted all my details here: viewtopic.php?f=2&t=18176

TL;DR I monitored all network traffic for an AP dedicated to this test and only observed DHCP and ARP traffic from the ESP32 that was the root node. I've had better luck with the IDF for network routing and mesh seems to work fine on MDF framework but I cannot get MESH + WLAN gateway scenarios to work.

[PeterR]

I did over WS.
There were/are issues, check my posts, as I recall does not like fragmentation. ESP were very helpful & offered some patches.
In the end I cut the local ESP client out as was also quite laggy over WS so moved past the ESP32 MQTT client thing.

But, I am still not sure where/what you're mqtt server is? Try the HiveMq client. If you cannot get that the publish/subscribe then chances are its your server (or lack of).

[PeterR]

Ok, seen you're other post. I am guessing that you have a managed switch & you have enabled port mirroring?
You have actual transport errors logged so it should be possible (probably painful) to debug those clues.

[clif123]

My test fixture was simply a high-speed hub connected to a simple access point. I monitored it there after not seeing anything but DHCP and ARPs over the main WiFi AP with a monitor point at the MQTT server. You would think that the example would just work out of the box right?

[clif123]

I did over WS.
There were/are issues, check my posts, as I recall does not like fragmentation. ESP were very helpful & offered some patches.
In the end I cut the local ESP client out as was also quite laggy over WS so moved past the ESP32 MQTT client thing.

But, I am still not sure where/what you're mqtt server is? Try the HiveMq client. If you cannot get that the publish/subscribe then chances are its your server (or lack of).

Peter, you said that you cut out the MQTT client. What alternative did you use. I'm finding that I have good success using just the IDF and MQTT but I have not performed any long-term performance tests yet. Most of my existing projects have used the ESP8266, which appears more mature after wide adoption. I was excited about the possibility of using the mesh framework to offload the main WiFi network but this may just be too immature to rely on. To your other comment, I will dig around in the code and see if I can find the root cause to my network errors as ESP has not responded to my posts yet. I found the patch you referred to and will see if those changes could affect my success. Thanks for help!

[PeterR]

I was using the ESP client (WS) to talk to my ESP WS MQTT server. Both client & server were on the same ESP. Other computers could also access the server. There were a range of issues in the local transport and the local ESP client. Also the client was laggy. I stripped the client out as I could just expose procedural calls within my server. This ran faster and with less ram & I did not have to debug as much!
I don't think that above helps you much. The WS server & client transport were sensitive to fragmentation as I recall & the patches in the post seem to resolve. There was also an issue with WS subprotocols (Chrome) which again seems to have a working patch.