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.

Sign up for GitHub

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

Jump to bottom

better solution for AWS interruption - errorcode 5134 and 1051 #75

Open
nibi79 opened this issue Mar 6, 2023 · 0 comments
Open

better solution for AWS interruption - errorcode 5134 and 1051 #75

nibi79 opened this issue Mar 6, 2023 · 0 comments
Assignees
@nibi79
Labels
improvement Improvement

Comments

@nibi79
Copy link
Owner

nibi79 commented Mar 6, 2023

The AWS connection is being interrupted every 15-20 minutes, but is automatically resumed

Errors in log:

  • [DEBUG] [worxlandroid.internal.mqtt.AWSClient] - connection interrupted errorcode: 5134
  • [DEBUG] [worxlandroid.internal.mqtt.AWSClient] - connection interrupted errorcode: 1051

To prevent the devices from going offline, I have implemented a scheduled job to check if the connection was really interrupted or if it has already resumed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nibi79 nibi79

Labels
improvement Improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nibi79