Eaton Ellipse Eco 650USB - connection refused

networkupstools / nut

The Network UPS Tools repository. UPS management protocol Informational RFC 9271 published by IETF at https://www.rfc-editor.org/info/rfc9271 Please star NUT on GitHub, this helps with sponsorships!

https://networkupstools.org/

Other

1.99k stars 349 forks source link

Eaton Ellipse Eco 650USB - connection refused #1412

Closed binderth closed 2 years ago

binderth commented 2 years ago

I'm using the Eaton Ellipse Eco 650USB, which is connected to a Raspbian Bullseye (Linux 11) - Raspberry Pi 3.

I just installed nut:

sudo apt-get install nut-client nut-server usbutils

which gave me v2.7.4-13

My /etc/nut/ups.conf:

maxretry = 3

[eaton]
        driver = usbhid-ups
        port = auto
        productid = ffff
        desc = "Eaton Ellipse Eco 650USB"

sudo upsdrvctl start gives me this:

Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
Using subdriver: MGE HID 1.40

but: upsc eaton (or sudo upsc eaton) leads to:

Error: Connection failure: Connection refused

lsusb:

Bus 001 Device 004: ID 0463:ffff MGE UPS Systems UPS
Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

` What is causing this?

jimklimov commented 2 years ago

I think it also needs vendorid (0x0463) to match.

Regarding rights, did you set up udev rules so the devfs node would be handed by kernel to nut runtime user?

On Sun, May 1, 2022, 14:35 Thomas B. @.***> wrote:

I'm using the Eaton Ellipse Eco 650USB, which is connected to a Raspbian Bullseye (Linux 11) - Raspberry Pi 3.

I just installed nut:

sudo apt-get install nut-client nut-server usbutils

which gave me v2.7.4-13

My /etc/nut/ups.conf:

maxretry = 3

[eaton] driver = usbhid-ups port = auto productid = ffff desc = "Eaton Ellipse Eco 650USB"

sudo upsdrvctl start gives me this:

Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 Using subdriver: MGE HID 1.40

but: upsc eaton (or sudo upsc eaton) leads to:

Error: Connection failure: Connection refused

lsusb:

Bus 001 Device 004: ID 0463:ffff MGE UPS Systems UPS Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

` What is causing this?

— Reply to this email directly, view it on GitHub https://github.com/networkupstools/nut/issues/1412, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMPTFBM36OOTL7FQEDE4GDVHZ3CHANCNFSM5UZ2LBVQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

jimklimov commented 2 years ago

Also you may need "usb quirks" set up in certain Linux kernel versions, see https://wiki.archlinux.org/title/Network_UPS_Tools#CyberPower_UPS_keeps_disconnecting/reconnecting

On Sun, May 1, 2022, 23:14 Jim Klimov @.***> wrote:

I think it also needs vendorid (0x0463) to match.

Regarding rights, did you set up udev rules so the devfs node would be handed by kernel to nut runtime user?

On Sun, May 1, 2022, 14:35 Thomas B. @.***> wrote:

I'm using the Eaton Ellipse Eco 650USB, which is connected to a Raspbian Bullseye (Linux 11) - Raspberry Pi 3.

I just installed nut:

sudo apt-get install nut-client nut-server usbutils

which gave me v2.7.4-13

My /etc/nut/ups.conf:

maxretry = 3

[eaton] driver = usbhid-ups port = auto productid = ffff desc = "Eaton Ellipse Eco 650USB"

sudo upsdrvctl start gives me this:

Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 Using subdriver: MGE HID 1.40

but: upsc eaton (or sudo upsc eaton) leads to:

Error: Connection failure: Connection refused

lsusb:

Bus 001 Device 004: ID 0463:ffff MGE UPS Systems UPS Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

` What is causing this?

— Reply to this email directly, view it on GitHub https://github.com/networkupstools/nut/issues/1412, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMPTFBM36OOTL7FQEDE4GDVHZ3CHANCNFSM5UZ2LBVQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

binderth commented 2 years ago

I did screw up and edited the wrong config file for upsd.users, so of course, there wasn't any users present for upsmon.conf.

So, now it's running smoothly! ;)

Regarding rights, did you set up udev rules so the devfs node would be handed by kernel to nut runtime user?

I did not. Apparently, this is optional for some LINUX flavours? Raspi OS 'Bullseye' handles the USB for a understandable way for nut, I guess?