We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I find when using the below config, the particle device is:
However, the downside appears to be very delayed (or lost messages) from subscriptions.
Is there a way to separate out receiving any publish events from the other activities that might be 'blocking' OTA capabilities in the below?
Code
MQTT client("xxxxxxxx.iot.ap-southeast-2.amazonaws.com", 8883, 360, callback); //The below code is run every 120 seconds if (client.isConnected()) { client.loop(); } else { if(awsDisconnect == 0) { connectToAwsMqtt("connect"); } }
The text was updated successfully, but these errors were encountered:
check your firmware source code about the OTA(0.6.x/0.7.x/0.8.x) and network packet with WireShark.
Sorry, something went wrong.
No branches or pull requests
I find when using the below config, the particle device is:
However, the downside appears to be very delayed (or lost messages) from subscriptions.
Is there a way to separate out receiving any publish events from the other activities that might be 'blocking' OTA capabilities in the below?
Code
The text was updated successfully, but these errors were encountered: