[HCL] nJoy Keen 2000 supported by driver usbhid-ups #2650
Labels
CyberPower (CPS)
DDL
HCL
impacts-release-2.8.2
Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)
USB
This is an FYI issue, mostly for tracking the info.
OS: Arch Linux (rolling), nut v2.8.2
Manufacturer: nJoy
Device: Keen 2000 USB
P/N: UPLI-LI200KU-CG01B
Manufacturing date: on or around July 2024 (see here why this might be important)
Website: https://www.njoy.global/product/keen-2000/UPLI-LI200KU-CG01B?variants%5B53%5D=1
Unlike the nJoy Keen 600 (issue) or nJoy Keen 1500 (issue) which use serial connection and work with
blazer_ser
ornutdrv_qx
drivers, this one usesusbhid-ups
driver instead.The device itself seems to be manufactured by Cyberpower. Visually it is identical to Cyberpower's UT2200E, except for the front panel. This is further corroborated by the fact that the UT2200E, according to Cyberpower's website, is rated at 1320 W - which is coincidentally the same value reported by my unit via
ups.realpower.nominal
lsusb:
I suspect that they've just reused the device ID and maybe some of the components of this CyberPower UPS. I haven't opened my unit, so I can't state this with complete certainty.
/etc/nut/ups.conf:
journalctl -b:
upsc nutdev-usb1
battery.voltage
value is a bit higher than expected, can't really tell whether it's an issue of the unit or just an incorrect value is being reported (EDIT: seems to be normal when battery is partially charged and is actively charging).output_voltage
readout does not seem to be correct. Usually it is dead set at 6 volts, and jumps to 24 volts when UPS is on battery power. I assume that this just reports input voltage on DC-AC converter, right out of buck convertor - instead of actual AC output voltage.ups.status
:Mains power, charging batteries:
OL CHRG
Mains power, batteries charged:
OL
On battery, discharging:
OB DISCHRG
On battery, low battery:
OB LB
battery.voltage.high
andbattery.voltage.low
and unit's temperature are not reported by the device.The text was updated successfully, but these errors were encountered: