Skip to content
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

Meadow.Cloud - Commands (MQTT messages) are not guaranteed to arrive #809

Open
alexischr opened this issue Jan 10, 2025 · 0 comments
Open
Assignees

Comments

@alexischr
Copy link
Contributor

Describe the bug
In practice, Meadow.Cloud cloud-to-device commands (OTA, 'Command & Control') are evident to not be guaranteed to arrive.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy a Meadow.Cloud-enabled app, such as Cultivar, configured to a network you can easily disable (I like using the iPhone's Personal Hotspot in Compatibility Mode)
  2. While device is operating normally, confirm that OTA/C&C work for your app by sending a request and watching it go through
  3. Disable the network
  4. Send another OTA/C&C command
  5. Enable the network and allow time for the device to fully reconnect to it and Meadow.Cloud/MQTT
  6. Observe that the command (which is the payload of a missing MQTT message under the hood) never arrives.

Expected behavior
The user's command should execute shortly after the network is brought back up.

@alexischr alexischr changed the title Meadow.Cloud - Commands (MQTT messaging) is not guaranteed to arrive Meadow.Cloud - Commands (MQTT messages) are not guaranteed to arrive Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants