aaronsss / rh-setup Goto Github PK

The RH devs have updated the installation instructions.

Now they’re creating the venv in ~/.venv, instead of ~/RotorHazard/src/server/venv

see: https://github.com/RotorHazard/RotorHazard/blob/main/doc/Software%20Setup.md#5-install-python

The automatic install doesn't seem to work on bookworm (Pi OS 12). You can install manually without any issues

Automatic install does still work on bullseye (PI OS 11)

RH-Install downloads the latest Release.
https://api.github.com/repos/RotorHazard/RotorHazard/releases/latest

For me, it's also useful to download the latest Main branch, even though it's a dev version.

What do you think about this @Aaronsss ? I guess a fully automated install shouldn't have any options, but it would be useful to choose the version, especially when instigating RH-Setup manually.

Hi Aaron,

I've just across your RH-Setup repo and tried it out.

I ' M V E R Y I M P R E S S E D !

I wish I had come across it earlier. I'm testing RH out on the new RPi v5 board, and your RH-Setup script runs sooooo fast (partly because rebooting on RPi 5 is damn quick, compared to before).

RH-Setup first stage completed in 2-4 minutes and second stage seemed to flash by, maybe a further 1 minute, 2 minutes max!

Here's my first time experience and feedback, in case it's any use.

1. I couldn't edit the firstrun.sh file using my Mac, due to user permissions. I chose the manual installation method (see 4. below)
   cd ~
   wget https://github.com/Aaronsss/RH-Setup/archive/refs/heads/main.zip
   unzip main.zip
   sudo chmod 744 ~/RH-Setup-main/rh-pi-setup.sh
   ~/RH-Setup-main/rh-pi-setup.sh

2. The first stage paused (when initiating raspi-config), and it asked the user to confirm Serial options (Login Shell = No, Serial Port Hardware Enabled = Yes, confirm = Enter).
   A first time user wouldn't know the correct responses here, perhaps it's worth mentioning this in your README.md

3. The RH-Setup installation first stage completed ok, but at the end I got these messages and then the process failed to continue (see error log below)

To get round this, I manually created the folder ("sudo mkdir /boot/RH") and re-ran the rh-pi-setup.sh script. The process continued and completed satisfactorily.

ERROR LOG
sh: 1: cannot create /boot/RH/RHInstalProgress.txt: Directory nonexistent
Sun 19 Nov 09:48:50 GMT 2023 RotorHazard first stage install completed in: 156 Seconds
Rebooting to complete install

Broadcast message from root@raspberrypi5 on pts/1 (Sun 2023-11-19 09:48:50 GMT):

The system will reboot now!

Connection to raspberrypi5.local closed by remote host.
Connection to raspberrypi5.local closed.

4. Running it manually, to initiate the 2nd Stage, after first reboot, I needed to manually re-enter the command "~/RH-Setup-main/rh-pi-setup.sh"

5. pi-fan-control.service failed to start up in systemctl
   Running the script manually, the following log is returned:
   Traceback (most recent call last):
   File "/home/martin/Raspberry-Pi-Fan-Control/run-fan.py", line 43, in
   setup()
   File "/home/martin/Raspberry-Pi-Fan-Control/run-fan.py", line 13, in setup
   GPIO.setup(pin, GPIO.OUT)
   RuntimeError: No access to /dev/mem. Try running as root!

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/home/martin/Raspberry-Pi-Fan-Control/run-fan.py", line 48, in
fan_on()
File "/home/martin/Raspberry-Pi-Fan-Control/run-fan.py", line 25, in fan_on
GPIO.output(pin, True)
RuntimeError: The GPIO channel has not been set up as an OUTPUT

6. In pi-config-update.sh ...
   sudo -- bash -c 'echo "core_freq=250" >> /boot/config.txt' is not needed for Pi 4 and Pi 5.

7. rh-install.sh doesn't use the venv python virtual environment method.