-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Latest system update to 6.1.21-v8+broke the RPi Reporter #94
Comments
Ok, I can confirm its related to some system update. I just ran updates on my second RPi ( 2 of 3 down. I guess I won't update my 3rd RPi... ahhh :) |
another thing I would like to mention is that if I stop the service and run the RPi Reporter manually, it actually works and updates every 2 minutes, for example:
|
Given I tested. .21 for RPL and it is the SenseHAT fix, mine are still working fine and have been for a eek or so. |
interesting. Maybe its not related to .21 but something else to .21. Having 2 RPi down, something changed for sure. |
@Anto79-ops I have updated a number of RPi 4's here and am not seeing any issues. Since the errors you show appear to be access to temps can you please recheck that your daemon account has the correct permissions? (Since you can run interactively, it seems to be an issue with the Daemon account.) |
hey! that was it. Problem is fixed after repeating those steps. I wonder how that got reset? thank you for your help. Closing |
I updated my RPi4 today (April 14) using
sudo apt-get update/upgrade
, then restarted the RPi and it seems something has broke with the reporterbullseye 6.1.21-v8+
my other two RPis are running 6.1.19-v8+ and working fine
here's what I see:
Checklist:
Release with the issue:
ISP-RPi-mqtt-daemon v1.8.4
Last working release (if known):
Hardware, Operating System, Python version:
Description of problem:
Run our report script 'genBugInfo' on your failing device and include the output here:
Python errors shown in the logs (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: