[Nut-upsuser] New UPS Support: Eaton 5S 1000

Charles Lepple clepple at gmail.com
Wed May 4 13:49:01 UTC 2016

> On May 4, 2016, at 9:00 AM, Ken Marsh <ken.marsh at sparkpost.com> wrote:
>   24.578753	upsdrv_updateinfo...
>   24.831627	libusb_get_interrupt: Connection timed out
>   24.831647	Got 0 HID objects...
>   24.831661	Quick update...
>   24.881602	Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 32, Value: 0
>   24.931613	Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x09, Offset: 0, Size: 32, Value: 0
>   24.981610	Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x01, Offset: 0, Size: 1, Value: 1
>   24.981629	Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, ReportID: 0x01, Offset: 4, Size: 1, Value: 0
>   24.981639	Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x01, Offset: 2, Size: 1, Value: 1
>   24.981655	Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x01, Offset: 1, Size: 1, Value: 0

This part is normal, if the UPS doesn't have any updates. If you trust the battery, you could cut power (recommended that you keep the ground and neutral still connected - a power strip would work) or do a battery test.

Maybe there was another driver lingering in the background before?

You can add the "pollonly" flag under [eaton] in ups.conf to see if that works better, but before that, I'd kill the driver and start everything normally once.

(I didn't think the driver would get that far, but for future logs, please redirect to a text file and attach a gzip'd version.)

Charles Lepple
clepple at gmail

More information about the Nut-upsuser mailing list