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

Withings token input timeout? #179

Open
leaskovski opened this issue Oct 22, 2024 · 0 comments
Open

Withings token input timeout? #179

leaskovski opened this issue Oct 22, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@leaskovski
Copy link

leaskovski commented Oct 22, 2024

So I have this running fine. I do a "docker run" and get the token for withings sorted, the first sync runs and completes, and then I have a crontab that runs "docker start" every night to sync the latest data. All good! Eventually there is an authorisation issue, and that then requires me to sort out by starting the container in interactive mode. The problem is, I have no idea this is the case until my mrs moans at me that her weight isn't updating.

Now, I would be able to know if things went south by the "docker start" not hanging around after 30 seconds. i.e. if the input that the tool waits for (the auth token), didn't just sit there. The input says that there is a 30 second window to do it, so if after 30 seconds the tool could effectively exit with an error code (maybe the auth error?), then any docker monitoring software could report on this. That way, my zabbix server would report back that a container isn't exiting successfully, and I could action it before the mrs has a moan 🥇

Is that possible?

@leaskovski leaskovski changed the title Garmin token input timeout? Withings token input timeout? Oct 22, 2024
@longstone longstone added the enhancement New feature or request label Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants