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

Error always received on startup #539

Closed
harleyg321 opened this issue Apr 2, 2020 · 0 comments · Fixed by #540
Closed

Error always received on startup #539

harleyg321 opened this issue Apr 2, 2020 · 0 comments · Fixed by #540
Assignees
Labels
bug Something isn't working

Comments

@harleyg321
Copy link
Contributor

Describe the bug
Every time I turn on my raspberry pi, I get a "Can't retrieve printer status" error before it goes into standby.

Expected behavior
Errors shouldn't be shown on startup while we are still waiting for OctoPrint to launch.

General Information:

  • OctoDash v1.4.1
  • OctoPrint v1.4.0
  • Klipper v0.8.0

Additional context
I think what is happening is OctoDash starts before OctoPrint has finished starting, so it is unable to contact OctoPrint, and displays an error. OctoPrint then starts up, at which point OctoDash is able to get the printer status and see that the serial connection has not been opened yet and goes into standby, but not before an error has already been shown (which persists onto the standby screen).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants