-
Notifications
You must be signed in to change notification settings - Fork 12
Read Subscribe message #48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @PhilC66 , I think this is probably a timeout issue? First up, it looks like you posted the same serial console messages twice? "with empty message" and "with message" are the same - both show a 5 second delay. But I understand the issue. In So, I think this is expected. If the topic is 'empty', it will take Closing. Please reopen if you need more help with this. Best wishes, |
0K, I understand. |
Hi Philippe, Looking at the SARA-R5 AT commands manual, the You will need to modify Example17: Modify the callback Keep calling Only call I hope this helps, |
High Paul, |
Subject of the issue
command readMQTT() take 5 seconds to give answer if no message,
take 1second if message present
Your workbench
with empty message
17:18:26.007 -> debut:59236
17:18:26.007 -> sendCommandWithResponse: Command: +UMQTTC=6,1
17:18:26.007 -> sendCommandWithResponse: Response:
17:18:26.007 -> OK
17:18:31.006 ->
17:18:31.006 -> readMQTT: sendCommandWithResponse err 4
17:18:31.006 -> fin:64236
with message
17:18:26.007 -> debut:59236
17:18:26.007 -> sendCommandWithResponse: Command: +UMQTTC=6,1
17:18:26.007 -> sendCommandWithResponse: Response:
17:18:26.007 -> OK
17:18:31.006 ->
17:18:31.006 -> readMQTT: sendCommandWithResponse err 4
17:18:31.006 -> fin:64236
Steps to reproduce
Tell us how to reproduce this issue. Please post stripped down example code demonstrating your issue to a gist.
Expected behaviour
Tell us what should happen
Actual behaviour
Tell us what happens instead
The text was updated successfully, but these errors were encountered: