Nut upsuser - Jun 2014 - Anyone successfully used NUT with the Eaton "5E Essential UPS"

Hi,


Wondering whether anyone has managed to get NUT working with the Eaton
5E Essential UPS, or has any tips as to what I might try to get it
working, or whether I'm just out of luck?


My config is:
OS name and version: Kubuntu 14.04
exact NUT version: 2.7.1-1ubuntu1
NUT installation method: sudo apt-get install nut
exact device name: 5E2000iUSB-AU
ups.conf entry:
[Eaton5E2000]
driver = usbhid-ups -DD
port = auto
desc = "Eaton 5E2000 UPS"
Output of "sudo /lib/nut/usbhid-ups -DD -a Eaton5E2000":
Network UPS Tools - Generic HID driver 0.38 (2.7.1)
USB communication driver 0.32
0.000000 debug level is '2'
0.000272 upsdrv_initups...
0.011069 Checking device (1D6B/0003) (004/001)
0.022373 - VendorID: 1d6b
0.022388 - ProductID: 0003
0.022394 - Manufacturer: unknown
0.022399 - Product: unknown
0.022405 - Serial Number: unknown
0.022410 - Bus: 004
0.022415 Trying to match device
0.022438 Device does not match - skipping
0.022796 Checking device (0463/FFFF) (003/006)
0.023496 - VendorID: 0463
0.023511 - ProductID: ffff
0.023517 - Manufacturer: unknown
0.023522 - Product: unknown
0.023528 - Serial Number: unknown
0.023533 - Bus: 003
0.023538 Trying to match device
0.023546 Device matches
0.024498 Unable to get HID descriptor (error sending control message:
Broken pipe)
0.024518 HID descriptor length 549
0.024861 Unable to get Report descriptor: Broken pipe
0.024894 Checking device (046D/08C5) (003/005)
0.024921 - VendorID: 046d
0.024927 - ProductID: 08c5
0.024932 - Manufacturer: unknown
0.024937 - Product: unknown
0.024943 - Serial Number: unknown
0.024948 - Bus: 003
0.024953 Trying to match device
0.024961 Device does not match - skipping
0.024972 Checking device (1199/68A3) (003/002)
0.024991 - VendorID: 1199
0.024996 - ProductID: 68a3
0.025001 - Manufacturer: unknown
0.025007 - Product: unknown
0.025012 - Serial Number: unknown
0.025017 - Bus: 003
0.025022 Trying to match device
0.025028 Device does not match - skipping
0.025037 Checking device (1D6B/0002) (003/001)
0.025053 - VendorID: 1d6b
0.025059 - ProductID: 0002
0.025064 - Manufacturer: unknown
0.025069 - Product: unknown
0.025074 - Serial Number: unknown
0.025080 - Bus: 003
0.025084 Trying to match device
0.025090 Device does not match - skipping
0.025099 Checking device (045E/00CB) (002/004)
0.025117 - VendorID: 045e
0.025122 - ProductID: 00cb
0.025127 - Manufacturer: unknown
0.025132 - Product: unknown
0.025138 - Serial Number: unknown
0.025143 - Bus: 002
0.025148 Trying to match device
0.025153 Device does not match - skipping
0.025162 Checking device (03F0/0324) (002/003)
0.025179 - VendorID: 03f0
0.025185 - ProductID: 0324
0.025190 - Manufacturer: unknown
0.025195 - Product: unknown
0.025200 - Serial Number: unknown
0.025205 - Bus: 002
0.025210 Trying to match device
0.025217 Device does not match - skipping
0.025225 Checking device (8087/8000) (002/002)
0.025238 - VendorID: 8087
0.025243 - ProductID: 8000
0.025248 - Manufacturer: unknown
0.025253 - Product: unknown
0.025259 - Serial Number: unknown
0.025264 - Bus: 002
0.025269 Trying to match device
0.025274 Device does not match - skipping
0.025283 Checking device (1D6B/0002) (002/001)
0.025299 - VendorID: 1d6b
0.025305 - ProductID: 0002
0.025310 - Manufacturer: unknown
0.025315 - Product: unknown
0.025320 - Serial Number: unknown
0.025325 - Bus: 002
0.025330 Trying to match device
0.025336 Device does not match - skipping
0.025345 Checking device (058F/6362) (001/004)
0.025364 - VendorID: 058f
0.025369 - ProductID: 6362
0.025374 - Manufacturer: unknown
0.025379 - Product: unknown
0.025384 - Serial Number: unknown
0.025390 - Bus: 001
0.025394 Trying to match device
0.025400 Device does not match - skipping
0.025408 Checking device (046D/0A29) (001/003)
0.025426 - VendorID: 046d
0.025432 - ProductID: 0a29
0.025437 - Manufacturer: unknown
0.025442 - Product: unknown
0.025447 - Serial Number: unknown
0.025452 - Bus: 001
0.025457 Trying to match device
0.025463 Device does not match - skipping
0.025471 Checking device (8087/8008) (001/002)
0.025484 - VendorID: 8087
0.025489 - ProductID: 8008
0.025494 - Manufacturer: unknown
0.025499 - Product: unknown
0.025504 - Serial Number: unknown
0.025509 - Bus: 001
0.025514 Trying to match device
0.025520 Device does not match - skipping
0.025529 Checking device (1D6B/0002) (001/001)
0.025545 - VendorID: 1d6b
0.025550 - ProductID: 0002
0.025555 - Manufacturer: unknown
0.025561 - Product: unknown
0.025566 - Serial Number: unknown
0.025571 - Bus: 001
0.025576 Trying to match device
0.025581 Device does not match - skipping
0.025590 No appropriate HID device found
0.025597 No matching HID UPS found


Many thanks in advance for any suggestions, advice or pointers.


Regards,
Shane
-------------- next part --------------
An embedded message was scrubbed...
From: unknown sender
Subject: no subject
Date: no date
Size: 13322
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140620/fc16f8af/attachment-0003.eml>

On Thu, Jun 19, 2014 at 12:16 PM, Shane Alderton
<shane at northlandease.com.au> wrote:
> Hi,
>
>
> Wondering whether anyone has managed to get NUT working with the Eaton
> 5E Essential UPS, or has any tips as to what I might try to get it
> working, or whether I'm just out of luck?
>
>
> My config is:
> OS name and version: Kubuntu 14.04
> exact NUT version: 2.7.1-1ubuntu1
> NUT installation method: sudo apt-get install nut
> exact device name: 5E2000iUSB-AU
> ups.conf entry:
> [Eaton5E2000]
> driver = usbhid-ups -DD
> port = auto
> desc = "Eaton 5E2000 UPS"
> Output of "sudo /lib/nut/usbhid-ups -DD -a Eaton5E2000":
> Network UPS Tools - Generic HID driver 0.38 (2.7.1)
> USB communication driver 0.32
[...]
> 0.022796 Checking device (0463/FFFF) (003/006)
> 0.023496 - VendorID: 0463
> 0.023511 - ProductID: ffff
> 0.023517 - Manufacturer: unknown
> 0.023522 - Product: unknown
> 0.023528 - Serial Number: unknown
> 0.023533 - Bus: 003
> 0.023538 Trying to match device
> 0.023546 Device matches
> 0.024498 Unable to get HID descriptor (error sending control message:
> Broken pipe)
> 0.024518 HID descriptor length 549
> 0.024861 Unable to get Report descriptor: Broken pipe
Hi Shane,

Going through old list posts, and I noticed the similarity to Leith's email:

http://lists.alioth.debian.org/pipermail/nut-upsuser/2014-August/009128.html

The "Broken pipe" error message might also show up in dmesg output as
"error -32".

What kind of motherboard do you have, and what version of the kernel
are you running?

Hi Shane,

Sounds like the same error I am getting.

Have you tried rebooting the UPS? (turn it off with the power button
then back on and reboot your computer)

I find that fixes it for a the current session, until I reboot the
computer a few times then it stops again.
Thanks,
Leith Bade
leith at leithalweapon.geek.nz


On 10 August 2014 10:54, Charles Lepple <clepple at gmail.com>
wrote:
> On Thu, Jun 19, 2014 at 12:16 PM, Shane Alderton
> <shane at northlandease.com.au> wrote:
>> Hi,
>>
>>
>> Wondering whether anyone has managed to get NUT working with the Eaton
>> 5E Essential UPS, or has any tips as to what I might try to get it
>> working, or whether I'm just out of luck?
>>
>>
>> My config is:
>> OS name and version: Kubuntu 14.04
>> exact NUT version: 2.7.1-1ubuntu1
>> NUT installation method: sudo apt-get install nut
>> exact device name: 5E2000iUSB-AU
>> ups.conf entry:
>> [Eaton5E2000]
>> driver = usbhid-ups -DD
>> port = auto
>> desc = "Eaton 5E2000 UPS"
>> Output of "sudo /lib/nut/usbhid-ups -DD -a Eaton5E2000":
>> Network UPS Tools - Generic HID driver 0.38 (2.7.1)
>> USB communication driver 0.32
> [...]
>> 0.022796 Checking device (0463/FFFF) (003/006)
>> 0.023496 - VendorID: 0463
>> 0.023511 - ProductID: ffff
>> 0.023517 - Manufacturer: unknown
>> 0.023522 - Product: unknown
>> 0.023528 - Serial Number: unknown
>> 0.023533 - Bus: 003
>> 0.023538 Trying to match device
>> 0.023546 Device matches
>> 0.024498 Unable to get HID descriptor (error sending control message:
>> Broken pipe)
>> 0.024518 HID descriptor length 549
>> 0.024861 Unable to get Report descriptor: Broken pipe
>
> Hi Shane,
>
> Going through old list posts, and I noticed the similarity to Leith's
email:
>
>
http://lists.alioth.debian.org/pipermail/nut-upsuser/2014-August/009128.html
>
> The "Broken pipe" error message might also show up in dmesg
output as
> "error -32".
>
> What kind of motherboard do you have, and what version of the kernel
> are you running?
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser