The Network UPS Tools repository. UPS management protocol Informational RFC 9271 published by IETF at https://www.rfc-editor.org/info/rfc9271 Please star NUT on GitHub, this helps with sponsorships!
The following variables were listed but could not be changed with upsrw:
battery.charge.low
battery.runtime.low
input.transfer.low
input.transfer.high
upsmon did a shutdown when OB+LB was reported (11.6V)
shutdown|start timers have a granularity of 60 seconds round down.
If UPS is off when line power is restored, output comes on, regardless of battery state.
If line power never goes down during a upscmd shutdown.restore, the load is power cycled.
If line power is restored during the shutdown timer and the battery is low. The output is not turned back on when the start timer expires. Hopefully it turns back on when the battery is charged. (TBC)
The battery.charge and battery.runtime values do not update during discharge, only during charging
ups-scanner suggested blazer_usb driver, however usbhid-ups works instead
/etc/nut/ups.conf
[nutdev1]
driver = usbhid-ups
port = auto
vendorid = 0764
productid = 0601
user = "root"
group = _ups
desc = "The PowerWalker"
pollonly
override.battery.voltage.nominal = 12
offdelay = 120
ondelay = 180
Thank you all to the project maintainers.
upsrw
:battery.charge.low
battery.runtime.low
input.transfer.low
input.transfer.high
upsmon
did a shutdown when OB+LB was reported (11.6V)upscmd shutdown.restore
, the load is power cycled.battery.charge
andbattery.runtime
values do not update during discharge, only during chargingups-scanner
suggestedblazer_usb
driver, howeverusbhid-ups
works instead/etc/nut/ups.conf
/etc/nut/upsd.conf
is empty/etc/rc.shutdown
Output of
upsc nutdev1
Output of
upsrw -l nutdev1 | grep ^[[V] | paste - - | column -t
Output of
uname -a
OpenBSD proliant.henryandlizzy.uk 7.5 GENERIC.MP#82 amd64