Replies: 1 comment 3 replies
-
Which version are you using? The latest release or main branch? If you're using the latest release, your code would have the client create its own task and stay out of the way of any user tasks (like the Arduino loop). So yes, the client's loop does block but it shouldn't hinder you. PS Blocking is practically only when creating the TCP (and TLS!) connection. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello Bert,
maybe you can help me with a comprehension question?
I am using an ESP32 for a project and your library for the WiFi MQTT part.
It is important for me that the loop with the control parts always goes through undisturbed and does not block.
Therefore I thought if I initialize the espMqttClient(1, 0) the WiFi and MQTT part would be executed on core 0 and in case of connection problems the main loop would not be blocked.
I'm not 100% sure yet, but in serial debug it looks like in case of problems, before MQTT disconnect, the loop is blocked.
I'm trying to collect more detailed info.
Beta Was this translation helpful? Give feedback.
All reactions