[Nut-upsuser] UPS is in OL+DISCHRG state, while charging, variable ignored?
Kit Gerrits
kitgerrits at gmail.com
Tue Jan 13 13:24:39 GMT 2026
Hello all,
I get the following warning in Logwatch:
--------------------- Network UPS Tools Begin ------------------------
**Unmatched Entries**
usbhid-ups: ups_status_set: seems that UPS [nutdev-usb1] is in
OL+DISCHRG state now. Battery charge is currently 99. Is it calibrating
(perhaps you want to set 'onlinedischarge_calibration' option)? Note that
some UPS models (e.g. CyberPower UT series) emit OL+DISCHRG when in fact
offline/on-battery (perhaps you want to set 'onlinedischarge_onbattery'
option).: 1 Time(s)
---------------------- Network UPS Tools End -------------------------
I have added the relevant configuration line to ups.conf according to what
I found here <https://github.com/networkupstools/nut/issues/3006>:
[root at gen8 ups]# grep -v '^#' ups.conf
maxretry = 3
[nutdev-usb1]
driver = "usbhid-ups"
port = "auto"
vendorid = "0463"
productid = "FFFF"
product = "Ellipse PRO"
serial = "G358P39040"
vendor = "EATON"
# bus = "001"
# device = "003"
# busport = "006"
onlinedischarge_calibration = 1
[root at gen8 ups]#
I have restarted the NUT service, but I still get this warning every time
the UPS does a calibration (I believe every month)
Here is my config:
[root at gen8 ups]# uname -a
Linux gen8.strike2.org 6.16.7-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Thu
Sep 11 17:46:54 UTC 2025 x86_64 GNU/Linux
[root at gen8 ups]# rpm -q nut
nut-2.8.4-1.fc42.x86_64
[root at gen8 ups]# /usr/libexec/nut-driver-enumerator.sh
Error reading the list of systemd service instances for UPS drivers, or
none are defined - before manipulations
Sun Dec 21 02:09:32 PM UTC 2025 : Detected changes in global section of
'/etc/ups/ups.conf', will restart all drivers
OK
Adding new systemd service instance for power device [nutdev-usb1]...
Created symlink
'/etc/systemd/system/nut-driver.target.wants/nut-driver at nutdev-usb1.service'
→ '/usr/lib/systemd/system/nut-driver at .service'.
Enabled instance: 'nut-driver at nutdev-usb1' for NUT configuration section
'nutdev-usb1'
Adding 'Wants'+After dependency for 'nutdev-usb1' on 'systemd-udevd.service
nut-udev-settle.service'...
OK
OK
OK
OK
Started instance: 'nut-driver at nutdev-usb1' for NUT configuration section
'nutdev-usb1'
=== The currently defined service instances are:
nutdev-usb1
=== The currently defined configurations in '/etc/ups/ups.conf' are:
nutdev-usb1
Sun Dec 21 02:09:35 PM UTC 2025 : OK: No more changes to reconcile between
systemd service instances and device configurations in '/etc/ups/ups.conf'
[root at gen8 ups]# nut-scanner
Scanning USB bus.
No IP range(s) requested, skipping SNMP
Scanning XML/HTTP bus.
No IP range(s) requested, skipping NUT bus (old libupsclient connect method)
Scanning NUT simulation devices.
Scanning NUT bus (avahi method).
Scanning IPMI bus.
[nutdev-usb1]
driver = "usbhid-ups"
port = "auto"
vendorid = "0463"
productid = "FFFF"
product = "Ellipse PRO"
serial = "G358P39040"
vendor = "EATON"
# bus = "003"
# device = "005"
# busport = "006"
Kind regards,
Kit
--
He attacked everything in life with a mix of extraordinary genius and naive
incompetence, and it was often difficult to tell which was which.
- Douglas Adams
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20260113/b2f64983/attachment.htm>
More information about the Nut-upsuser
mailing list