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

Seems to be the busy light API was offline #36

Open
pmartello opened this issue Jan 24, 2023 · 1 comment
Open

Seems to be the busy light API was offline #36

pmartello opened this issue Jan 24, 2023 · 1 comment

Comments

@pmartello
Copy link

I recently upgraded the RPi to Bullseye and started receiving the message "Seems to be the busy light API was offline" which I understand is a catch-all message (I believe it's coming from busyLightService.ts) when trying to retrieve the busy status from the API.

Not sure why I'm getting this message and so I'm looking for the logs to see if there is anything in particular that might be causing this issue but I'm having trouble finding this detail. I have switched on Debug to get more verbose logging but this has not given me the desired result.

Any suggestions?

@pmartello
Copy link
Author

Following the upgrade to Bullseye, Python is upgraded to v3.9. As a result, the following modules need to be reinstalled using the "pip install" command:

  • gpiozero
  • spidev
  • unicornhat
  • unicornhatmini
  • flask
  • flask_cors
  • jsmin

I can now run the busylight service for testing purposes, just need to get the busylight service starting on reboot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant