sinclairpaul
commented
5 months ago I'm not sure there is a way to get NUT not to issue and FSD, the powervalue config is meant for multiple UPS devices.
As HA in my case runs inside a Proxmox VM, NUT can only shut down the VM itself which doesn't make any sense as this won't shutdown other VMs and the Proxmox host itself.
Why wouldn't you run NUT on the host, rather than in a container inside a VM?
The NUT add-on behaves weirdly when shutdown_host is deactivated: it goes into the shutdown/startup loop and the respective integration floods HA with events. This makes it impossible to build any meaningful automations.
The addon shouldn't restart unless the "Watchdog" functionality is enabled.
pspot2
starsoccer
gyp5y
Problem/Motivation
I'd like to be able to disable the FSD / auto-shutdown completely for 3 reasons:
shutdown_hostis deactivated: it goes into the shutdown/startup loop and the respective integration floods HA with events. This makes it impossible to build any meaningful automations.My goal is to manage the "low battery" situation myself with my own automations and notifications.
Expected behavior
If I understand the add-on documentation correctly, setting the
powervalueconfig option to0is supposed to do the trick.Actual behavior
When setting
powervalueto 0, the add-on refuses to start because of theMINSUPPLIESoption which is set to1inupsmon.conf. According to the error message,powervaluecannot be lower thanMINSUPPLIES.Steps to reproduce
Try setting
powervalueto0and restart the add-on.Proposed changes
Assuming that setting the
powervalueto0is the correct way to solve my problem (e.g. completely disable setting the FSD flag and shutting down the host/add-on), I suppose theMINSUPPLIESoption should be configurable as well.If that assumption is wrong, I'm open for better suggestions on how to achieve this.
Thanks