On Jan 2, 2024, at 1:49 PM, Kelly Byrd wrote:
>
> My question for you all is what units ups.powersummary.runtimetoempty is
> supposed to be in? This doc from USB.org:
> https://www.usb.org/sites/default/files/hut1_4.pdf (Section 31.2) says
> minutes,
Do you mean the Power Device Class
Heh, ya. It does smell of copy-pasta.
I've got a consumer APC UPS. When I get time, I'll connect it to my NUT dev
server and sit what it reports with usbhid-ups vs what the display shows.
I'll also confirm with what Windows or MacOS think (but I don't know how
their drivers work)
On Tue, Jan
Kelly Byrd writes:
> Thanks for the reply, it looks to me (based on various existing HID-based
> drivers in the NUT source tree) that everyone is just mapping it directly
> with a line like this in a hid_info_t:
> { "battery.runtime", 0, 0, "UPS.PowerSummary.RunTimeToEmpty", NULL,
> "%.0f",
Thanks for the reply, it looks to me (based on various existing HID-based
drivers in the NUT source tree) that everyone is just mapping it directly
with a line like this in a hid_info_t:
{ "battery.runtime", 0, 0, "UPS.PowerSummary.RunTimeToEmpty", NULL,
"%.0f", 0, NULL }
I found that in
Kelly Byrd writes:
> Looking through a bunch of the code for drivers using HID, It looks like
> everyone is using "ups.powersummary.runtimetoempty" to map to NUT's
> "battery.runtime" variable.
>
> My question for you all is what units ups.powersummary.runtimetoempty is
> supposed to be in? This
Looking through a bunch of the code for drivers using HID, It looks like
everyone is using "ups.powersummary.runtimetoempty" to map to NUT's
"battery.runtime" variable.
My question for you all is what units ups.powersummary.runtimetoempty is
supposed to be in? This doc from USB.org:
