# How to uninstall the LiPo shim battery monitor

**URL:** <https://forums.pimoroni.com/t/how-to-uninstall-the-lipo-shim-battery-monitor/10337>\
**Category:** Raspberry Pi\
**Created:** [April 8, 2019, 7:27am UTC](https://forums.pimoroni.com/t/how-to-uninstall-the-lipo-shim-battery-monitor/10337 "2019-04-08T07:27:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![akzidenzgrotesk9](https://avatars.discourse-cdn.com/v4/letter/a/838e76/32.png) [@akzidenzgrotesk9](https://forums.pimoroni.com/u/akzidenzgrotesk9)\
**Post date:** [April 8, 2019, 7:27am UTC](https://forums.pimoroni.com/t/how-to-uninstall-the-lipo-shim-battery-monitor/10337/1 "2019-04-08T07:27:03Z")

</div>

Hi there,

I installed Pimoroni’s battery monitoring software with this command:

`curl https://get.pimoroni.com/zerolipo | bash`

But whenever I try to power on with usb instead of lipo and ssh into my pi, the terminal will constantly broadcast a shutdown message, rendering it impossible to work. I need to uninstall this software, but the `sudo systemctl disable gpio-poweroff` line that seemed to work [in this thread](https://forums.pimoroni.com/t/zero-lipo-software-causes-failed-to-authenticate-error/5246/55) returns an error of “No such file or directory”.

How do I uninstall this script? Thanks so much!

---

<div class="post-metadata">

**Author:** ![monglet](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.pimoroni.com/monglet/32/1113_2.png) [@monglet](https://forums.pimoroni.com/u/monglet)\
**Post date:** [April 8, 2019, 8:04am UTC](https://forums.pimoroni.com/t/how-to-uninstall-the-lipo-shim-battery-monitor/10337/2 "2019-04-08T08:04:02Z")

</div>

From [GitHub - pimoroni/clean-shutdown: Python daemon to watch a GPIO pin and trigger a clean shutdown.](https://github.com/pimoroni/clean-shutdown)

> Parasitic Shutdowns
> 
> Be aware that altering the state of trigger\_pin can throw you in a scenario where your Pi shuts down right away upon boot, if a process, dtoverlay, or HAT EEPROM, just to name a few possibilities, pulls it low on boot (or set it as an output, which implies it being driven low initially).
> 
> If this occurs right after you plugged a HAT, then try booting without it attached, and disable the cleatshutd service with:
> 
> sudo systemctl disable cleanshutd  
> There is another way, which is provided as an emergency solution for scenarios where reaching the bash prompt is not possible (because the Pi shuts down before you get a chance to do so).
> 
> In such cases, or as an alternative to the above, you may add the following to your /boot/config.txt file from another computer:
> 
> disable\_cleanshutd=1