-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
RaspberryPi 5 - notes #113
Comments
I forgot to add some, install isn't much different a few tweaks (simpler) iirc. We can now also show if a 5V 5A PSU is being used (or 3A is being overridden) |
Yep, I'm learning venv setup and will adjust my instructions when I figure out a good approach. Which would you see using more? a per-user setup for venv or a per project setup? |
I created a venv under /opt/RPi-Reporter-MQTT2HA-Daemon, activated the venv, installed requirements, and set isp-rpi-reporter.service as such:
Has been working great. I prefer having it in a virtual environment. |
@sholdee I can easily make that change and update the docs. Thank you for finding, testing, and reporting this working pattern! |
Gonna expand on @sholdee 's comment. This has become more important with Bookworm, since Python 3.11 defaults to failing pip installs without a "--break-system-packages" argument, and that's kinda (intentionally) scary for someone running the install. I've just got this working in a venv, here's my instruction updates: First, I'd probably remove the duplicate packages entirely and use entirely env local packages. I had a couple conflicts between my own apps and this daemon due to system packages. So put all the requirements into the Python venv, and reduce the OS system instruction to Add the others to requirements.txt. Pip install should take care of dependencies. This is actually pretty easy, since the virtual environment gets baked in when launched from the venv symlinks. Create the venv as root: I like to put the actual python application into a subfolder to keep the venv clean, "app" in this case: This is just what I'm using, you might prefer a different pattern. Install the requirements: (This worked fine on my systems as-is, it's possible there's some additional system packages needed for pip to do it's thing. Sometimes it can't auto-resolve dependencies, or the wheels need to compile, etc.) Modify the .service file to execute under the virtualenv. (Ideally this gets updated if you decide to use venvs for future versions.) Edit the config.ini as appropriate and set permissions, since it contains the mqtt password. (The default service file runs this as the daemon user.)
Install the service file and kick it off:
Since the service runs as daemon, I had errors with files in /dev on one or two systems. In my case, I added daemon to the video group, but you can also just set the service file to run as root. w/e works in your env. |
[ Awaiting the update regarding btw, on |
thanks for the instructions - worked perfect for me 🙏 |
For anyone reading this, blank pi zero 2w -> Bookworm RPI OS Light 64bit - actual install commands that worked for me below. They might work in a single script if you remove sudo and run the script as sudo.
Might help someone update the actual install guide... sudo apt-get update |
Ok less a bug release, just a place I'm going to put any note when I test it on the Pi5 in a little bit
I do know we can add more detail, voltages, fan speed etc.
Bookworm may cause a problem due to the way we need to set it up ( venv and python.) but that's Pi independent.
The text was updated successfully, but these errors were encountered: