GPIO current value 'stuck' at 0.7 A ...

[ArjenR49]

I have two PiJuice HATs in use. Both on a Pi4B. One Pi runs 64-bit bookworm, the other 64-bit bullseye. Both PiJuice HATs have identical settings, but the bullseye one has two 3,5" BTRFS drives on their own powered USB hub in addition to the SSD with the OS. It is an off-site backup NAS of my own making.

All in all, these run OK. The software is 1.8 and the f/w 1.6 on both. They are powered from the PI4 USB-C power connector. The PiJuice HATs are only there to make the Pi's shut down gracefully in case there is a blackout.

A little while ago I decided to get spare (Cameron Sino) batteries for both. Perhaps in the course of 'installing'/trying those something happened. The PI running bullseye now shows a fixed current value in the PiJuice GUI under GPIO Power input of 0.7 A all the time, no matter what I try. In pijuice_cli the value is 0,690 A.

The other Pi running bookworm shows the typical varying current values. Sometimes positive, sometimes negative. The batteries. The GPIO voltage varies on both Pi's as usual.

I gathered from other discussions that the GPIO current value is an estimate made by software.
I have reset the HAT (20 sec SW1&SW2) and redone the settings. No change. I have stopped the Pi and removed the battery etc. No change. The current remains stuck at 0.7 A. (It happens to be the same value as in a screen shot in the documentation on GitHub ...) I have uninstalled the software and reinstalled it. No change.

It has been too short time to say that it doesn't make a difference for operation.

Normally these PiJuice HATs cycle between 100% battery charge and some lower value at which they decide to start charging the battery again until 100%. At least that is my observation.
Not yet sure now if the misbehaving Pi/PiJuice will keep functioning as intended. The scripts I use on both do seem to work as before and temperature stays within normal values.

Thanks for any and all comments.
Arjen
Bergen, Netherlands / Helsinki, Finland

P.S. Over the years I've been using or trying to use even 5 different types of UPS. I lost count. Two Greek products and one Chinese in addition to the PiJuice HATs. The PiJuice turned out the most reliable of them, but development and production apparently has stopped totally. The other UPS's I had to drop for one or the other reason, mostly too time consuming to get working right.
However, lately I have been using two WittyPi L3v7 HATs (half size) from UUgear on my PiHole DNS&timeservers (PiZero 2 and Pi4B, in two locations). They are available and actively supported.
I was able to buy a spare PiJuice earlier this year from a shop in my country, but that must have been sheer luck.

[ArjenR49]

I replaced the PiJuice HAT with a new spare one and the GPIO current value is OK now, fluctuating as it is meant to.

It proved the PiJuice board can be damaged w/o the smoke escaping... I tried to find a burnt component, but there are too many and most very small. I have no real clue how it happened, though. It was OK until I fiddled with the battery which I figured could do with replacing with a new one.

Changing the HAT was easier than expected. Most of my settings for the HAT were good by default. The User script settings are apparently stored on the OS drive, as they didn't need to be entered anew. Script name typing would have been most work.

User scripts are probably not actually necessary for my use case, as I only require a graceful shutdown at a blackout and automatic startup, but my user scripts keep a log of what happened and flash the LEDs for a nice effect and some feedback when one presses a button.