I had the same issue as this poster, and the new firmware v1.3 resolved it. However, when I then use the wp5 tool to change the 'Default state when powered' to 0 (should power on the Pi immediately when the WittyPi5 gets powered), it doesn't seem to do anything. I still need to press the WP5's power button to turn on the Pi. I have had this setting work properly with older firmware versions on other WP5s.
We did not change this behavior recently.
How did you test it? If you just pulled out the wall plug and quickly plug it back, it probably will not work because the power adapter has big capacitor inside and it keeps some voltage. When your Raspberry Pi is off, the load is rather small and it will take some time to fully discharge that capacitor. The actual voltage applied on Witty Pi 5 may not drop low enough to be considered "power cut".
I may not have unplugged it for long enough. I will try again with that later today. Thanks for the quick reply.
Still doesn't seem to be working, unfortunately. I unplugged the power supply from the wall for a few minutes & plugged it back in. I just see the white LED blink for a few seconds, then it blinks once every 10 seconds. It powers on the Pi if I push the power button.
I believe I've configured it properly:
➜ ~ wp5 ================================================================================ | | | Witty Pi - Realtime Clock + Power Management for Raspberry Pi | | | | < Version 5.0.0 > by Dun Cat B.V. (UUGear) | | | ================================================================================ -------------------------------------------------------------------------------- Model: Witty Pi 5 Temperature: 23.688°C / 74.637°F V-IN: 11.964V V-OUT: 5.264V I-OUT: 0.833A SYS Time: 2026-05-11 08:22:01 RTC Time: 2026-05-11 08:22:01 -------------------------------------------------------------------------------- 1. Write system time to RTC 2. Write RTC time to system 3. Synchronize with network time 4. Schedule next shutdown 5. Schedule next startup 6. Choose schedule script 7. Set low voltage threshold 8. Set recovery voltage threshold 9. Set over temperature action 10. Set below temperature action 11. Other settings... 12. Reset data... 13. Administrate... 14. Exit Please input 1~14: 11 Other Settings: [ 1] Default state when powered [default OFF] [ 2] Power cut delay after shutdown [15 Seconds] [ 3] Pulsing interval during sleep [10 Seconds] [ 4] White LED pulse length [100 ms] [ 5] Dummy load pulse length [0 ms] [ 6] V-USB adjustment [+0.00V] [ 7] V-IN adjustment [+0.00V] [ 8] V-OUT adjustment [+0.00V] [ 9] I-OUT adjustment [+0.000A] [10] Power source priority [V-USB first] [11] Watchdog [Disabled] [12] Log to file on Witty Pi [Yes] [13] Return to main menu Please input 1~13: 1 Input the delay (in second) to turn on Raspberry Pi after getting powered (255=off): 0 Auto power-on delay is set to 0 seconds! -------------------------------------------------------------------------------- Model: Witty Pi 5 Temperature: 23.812°C / 74.863°F V-IN: 11.902V V-OUT: 5.281V I-OUT: 0.786A SYS Time: 2026-05-11 17:58:32 RTC Time: 2026-05-11 08:22:30 -------------------------------------------------------------------------------- 1. Write system time to RTC 2. Write RTC time to system 3. Synchronize with network time 4. Schedule next shutdown 5. Schedule next startup 6. Choose schedule script 7. Set low voltage threshold 8. Set recovery voltage threshold 9. Set over temperature action 10. Set below temperature action 11. Other settings... 12. Reset data... 13. Administrate... 14. Exit Please input 1~14: 14 Exit now.
It looks like the register settings aren't being persisted to the config file properly. After configuring things as above with wp5, I checked the register values via i2cget, and it seemed to be OK:
➜ ~ sudo i2cget -y 1 0x51 17 0x00
But then after I power cycle everything, register 17 is back to the default:
➜ ~ sudo i2cget -y 1 0x51 17 0xff
Not sure if this is relevant, but while troubleshooting this, I have been unable to get the WP5 to show up as an external drive. I've tried plugging it in via USB to my MacBook, as well as to a RPi (with the WP5 not connected via the 40-pin connector). It only shows up when I put it into firmware installation mode via holding down the BOOTSEL button as I connect the USB cable.
@josh since you mentioned the external drive ("Witty Pi 5" USB drive) is missing and the configuration is not persisted to config file, the FAT filesystem seems corrupted. Firmware v1.3 fixed a bug that may cause such kind of corruption, but if the filesystem is already corrupted, it can not fix the filesystem directly.
Please follow the "Erase the corrupted FAT filesystem" section on this page to recover your device first:
https://github.com/uugear/Witty-Pi-5-Firmware/releases/tag/v1.3
Yep, I started with that FAT erasing FW update first, when I saw that it was part of the 1.3 updating process. Still have the problem.
@josh we provided the wp5-fat-full-eraser.uf2 file with the v1.3 firmware together, how comes you did the FAT erasing FW update before seeing v1.3 firmware?
Anyway, after recovering the device, you should see the "Witty Pi 5" USB drive when connect it to PC. Otherwise it is not in normal state yet.
Yes, I saw they were provided together. As I wrote above, I did the FAT erasing as part of the 1.3 upgrade process, loading that code first.
@josh Have you followed all the 11 steps listed in the "Erase the corrupted FAT filesystem" section?
It is more than dragging two .uf2 files into RP2350 disk, there are quite some interactions.
I had gone through those 11 steps many many times. One step that may need some clarification: Step 9 says to 'Tap on the button on Witty Pi 5 before the blinking stops.' Is that the BOOTSEL button again, or the power button this time? I had been tapping the BOOTSEL button, so I don't know if that was the problem.
I just did it again, but tapped the power button this time and it seems like everything is now working properly.
Thanks for the support.