[Solved / Archived] WittyPi 3 mini on Pi Zero 2W and WittyPi 4 on Pi 4

@admin I don't have access to the device right now so I can't check the kernel version. Other than that it's December 5th 2023 bookworm release, Lite edition (no desktop), 64 bit on Pi Zero 2 W for me.

@admin I'm not sure of the release date, are there any commands you want me to run?

My pi 4 is running bookworm 12, 6.1.0 64bit, full OS

My pi zero 2 is bookworm 12, 6.1.0 32bit, full OS

Both running raspberry pi OS fresh installs from the raspberry pi writer. 

As I think I said in an earlier post it initially worked, then I guess an update broke it, there is a chance that update has been "fixed" and it isn't a problem any longer. I can try uncommenting the changes at some point, but it might not be this week.

Could you advise what the commented out bit of the script actually does? Thanks

@msage I guess you mean this code block:

# delay until GPIO pin state gets stable
counter=0
while [ $counter -lt 5 ]; do  # increase this value if it needs more time
  if [ $(gpio -g read $HALT_PIN) == '1' ] ; then
    counter=$(($counter+1))
  else
    counter=0
  fi
  sleep 1
done

This code repeatly reads GPIO-4 for every second, and will not stop until GPIO-4 has the same status for 5 readings in a row.

It may also be helpful if you can paste the complete error message you have saw.

@admin So the error was being generated by the systemctl this is all the errors I could find:

On the pi zero 2 (witty pi 3 mini), I'm getting this every second:
Dec 13 10:03:18 livingroompi wittypi[801]: /home/pi/wittypi/daemon.sh: line 119: [: too many arguments

On the pi 4 (witty pi 4) I'm getting this every second:
Dec 13 10:03:51 studykioskpi wittypi[589]: /home/pi/wittypi/daemon.sh: line 155: [: too many arguments

@msage since you are using Witty Pi 3 Mini, the line that referred by the error message is this one.

It is exactly the same part of code as I previously mentioned. The error most probably comes from gpio function, which is provided by gpio-util.sh and is a wrapper of raspi-gpio. The change from raspi-gpio may indeed cause issue like this, but I can not reproduce it yet.

I checked the OS details on my device, here it is:

uname -a
Linux pi-zero2 6.1.0-rpi7-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) aarch64 GNU/Linux

Posted by: @msage

↑

As I think I said in an earlier post it initially worked, then I guess an update broke it, there is a chance that update has been "fixed" and it isn't a problem any longer. I can try uncommenting the changes at some point, but it might not be this week.

Unfortunately it's still happening, I just did an `apt update && apt upgrade`, uncommented the lines and it doesn't work (same error) 🙁

I've just set up a pi zero wh with a mini 4, fresh install and I am still getting the issue, so I can't explain why your test version is working!

Hello everyone,

Is there already a solution for this problem in connection with bookworm?
I'm using 20 Rapis, which are supposed to go into the field in the next few days but don't shut down when the power button on the WittyPi is pressed.

Many thanks in advance.

@dobby The fix I posted earlier about commenting out the GPIO section is still working...

We managed to reproduce this issue after running "sudo apt upgrade" on bookworm system.

We confirm the issue is due to the change of raspi-gpio, which newly appended this text to the output of every command call:

[ raspi-gpio is deprecated - try `pinctrl` instead ]

We will have to modify the gpio-utils.sh to have this output properly processed.

The software for Witty Pi currently does not support Raspberry Pi 5, because raspi-gpio will not get updated to have RPi 5 supported. We will have to modify the gpio-utils.sh to use pinctrl to replace raspi-gpio, and this work is not that small.

@admin I did say earlier in the thread I thought the extra output was causing the issue, but I couldn't work out how to fix.

With regard to the pi 5 I think that's probably a separate issue that needs it's own thread update?

@msage Supporting RPi 5 and this issue is somehow related, because they all request to modify the gpio-utils.sh.

We can either make a minor update on gpio-utils.sh first, to fix the output of raspi-gpio; or maybe we directly update gpio-utils.sh and use pinctrl instead -- which should also fixed this issue.

We will evaluate both ways and decide what to do. At the time being I think it is better to make minor update first, to make sure RPi4 can work. Updating to pinctl needs more time.

After further investigation, we realize that the culprit is actually not that appended text message, but the change of output format for raspi-gpio. The newer version of raspi-gpio removed the "fsel=" (function selection) from the output, which causes the error of result parsing. We checked the repository of raspi-gpio and surprisely found that this change had been made about 3 years ago! It turns out that Raspberry Pi OS includes a very old version of raspi-gpio until the recent change.

We have modified gpio-util.sh and made it work with both old and new versions of raspi-gpio. We also added some messages to tell users that the current software version doesn't support Raspberry Pi 5. The software is now officially upgraded to V4.14, and you can view the changes here.

@admin Will the witty pi 3 (and mini) get this update or should I manually make the changes?