Replies: 2 comments
-
Moving
To the end of the function makes it work. This suggests that something is clearing the gpio interrupts in the process of setting up the mqtt server, but I have no idea what it could be. WiFi communication continues happily after this change, so nothing is obviously depending on these IRQs besides my code. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Rephrased this as issue #2577. Closing the discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Friends, I have a sketch where I want to listen for some interrupts and increment counters when they fire. Then, some computation is done on these counters periodically and the results are sent off to an MQTT server.
What I've found is that something about starting up the MQTT client disables my interrupts. I've not been able to drill down into the exact source of the problem, but what I can tell you is that until I see the "connected" message in this sketch, I can click my button and see "interrupted!" on Serial1. After the mqtt client is connected, no joy.
My build flags:
I'm going to keep debugging but I'm wondering if this rings a bell for anyone? I can try to put together a more minimal example if this one is too long.
Beta Was this translation helpful? Give feedback.
All reactions