I have a Raspberry Pi 2B with Witty Pi 3 that has been working since 2020. I decided to update to the latest Raspbian Trixie and reinstall the Witty software. The PI 2B boots fine and the witty daemon.sh appears in the list of processes. The problem is no shutdown happens. Also, pushing the button to shutdown has no effect - system stays on. I noticed this message:
[ 29.692268] systemd-sysv-generator[803]: SysV service '/etc/init.d/wittypi' lacks a native systemd unit file, automatically generating a unit file for compatibility.
[ 29.692536] systemd-sysv-generator[803]: Please update package to include a native systemd unit file.
[ 29.693612] systemd-sysv-generator[803]: ! This compatibility logic is deprecated, expect removal soon. !
---
I moved the following to /boot/firmware/config.txt
dtparam=i2c1=on
dtparam=i2c_arm=on
dtoverlay=pi3-miniuart-bt
dtoverlay=miniuart-bt
core_freq=250
---
I check that the following is OK: gpio readall
---
Any ideas on how to fix this would be great. Or do I have to buy the Witty Pi 4?
Thanks.
Despite the warning message from the SysV service, the daemon.sh process started. However, this does not mean it is functioning as expected. You may check the content of /home/pi/wittypi/wittyPi.log file and it usually tells what went wrong.
Witty Pi 3 software includes an old compatibility wrapper named gpio-util.sh. It was added when the wiringPi was no longer available on some Raspberry Pi OS releases. On newer Raspberry Pi OS versions this wrapper may no longer work correctly, especially for waiting for GPIO events. Since your system already has a working gpio command, you can try disabling this wrapper so the Witty Pi scripts use the real wiringPi gpio utility instead.
For example, you may rename the gpio-util.sh and reboot:
cd /home/pi/wittypi sudo mv gpio-util.sh gpio-util.sh.disabled sudo reboot
The system has been running continuously since 2020. I think some pins lost contact. Once I removed and reseated the Witty Pi, the button now turns the system on and off. But the system did not appear to follow the programmed schedule, so I also did your recommended change about gpio-util.sh. All works fine now. Thanks for the quick response.