On 11/1/2025 at 8:11 AM, Rysz said:

The latest update allows adding the port to the IP address in GUI settings, please try and report back if it works.

Confirming all is good for me with this update

Both UnRAID servers able to select any of the UPS devices

thanks @Rysz for the very fast turnaround.

1 hour ago, dam_j said:

Hello,

Sadly even after the update (thanks for that) my Unifi ups still doesn´t work.

Anything else i can try?

Are you sure this is not some firewall rule blocking the connection?

Please show a screenshot of the NUT server configuration on the UniFi side.

Here you go.

The unifi log doesnt show anything blocked.

I'm able to connect to my Unifi UPS now. There was a firmware update that dropped today and the plugin update, and it will only work (for me) with credentials disabled in Unifi. You still need to provide dummy username/password in Unraid though, but it finally works.

There's a thread on the unifi community about mishandling of strings on the NUT server. Kind of over my head, but related to quotes getting passed when they shouldn't or vice versa.

11 hours ago, dam_j said:

Here you go.

The unifi log doesnt show anything blocked.

Well it seems you got "UPS Name" in Unraid configured to "Tower" but to "UPS-Tower" within UniFi.

Also you should try disabling "Login Credential" as other people had problems with that (see above).

If that doesn't work, try changing as follows:

• Name to "unifi" (without quotes, in UniFi settings)

• ID to "unifi" (without quotes, in UniFi settings)

• "Login Credential" to disabled (in UniFi settings)

• UPS Name to "unifi" (without quotes, in Unraid settings)

I didnt get the part with "no credentials" in ubi...

Sorry and thanks now it works!!

Just for feedback.

Without credentials it is working, but I have to insert something in username and password (NUT Settings). Otherwise I get an error.

But it is toggling and sometimes not shows all data for like 30s or so.

I have 2 UPS 2U but this is all new to me.

Longshot probably, but is there a way for a slaved UPS connected to NUT to be emulated as a local, USB UPS through unraid's native UPS module? I have a mobile app that uses the unraid API to report on UPS status (among other things). With the native functionality disabled in lieu of NUT, nothing UPS comes through the API and the app assumes no UPS at all.

On 11/4/2025 at 4:47 PM, Marino said:

Just for feedback.

Without credentials it is working, but I have to insert something in username and password (NUT Settings). Otherwise I get an error.

But it is toggling and sometimes not shows all data for like 30s or so.

I have 2 UPS 2U but this is all new to me.

It seems it's cycling between regular polling and fallback mode, I'll have to see what could cause this.

Usually it goes into fallback mode only if the device does not respond to a regular variable dump query, odd.

3 hours ago, airtower said:

Longshot probably, but is there a way for a slaved UPS connected to NUT to be emulated as a local, USB UPS through unraid's native UPS module? I have a mobile app that uses the unraid API to report on UPS status (among other things). With the native functionality disabled in lieu of NUT, nothing UPS comes through the API and the app assumes no UPS at all.

Sorry that's not possible as far as I know, I think only the other direction is possible (bridge a apcupsd UPS into to NUT).

On 10/19/2025 at 9:03 PM, Rysz said:

Thank you for the detailed debug package with debug level increased.

I'm not sure what to make of your issue, although Eaton devices are usually well supported in NUT.

I've logged an upstream issue with the NUT software package developers, and will investigate myself also:
https://github.com/networkupstools/nut/issues/3136

I'll let you know if I have any news, hopefully we'll get this resolved for you, as soon as possible.

Legend!

I've tested https://github.com/networkupstools/nut/pull/3149 from https://github.com/networkupstools/nut/issues/3136 and can see my UPS.

battery.capacity: 9.00

battery.charger.type: Constant Charge (CC)

device.mfr: EATON

device.model: Eaton 9PX

device.serial: REMOVED

device.type: ups

driver.debug: 6

driver.flag.allow_killpower: 0

driver.name: usbhid-ups

driver.parameter.interrupt_pipe_no_events_tolerance: -1

driver.parameter.pollfreq: 30

driver.parameter.pollinterval: 2

driver.parameter.port: auto

driver.parameter.synchronous: yes

driver.state: quiet

driver.version: 2.8.4.690.6-696+g7715f839b

driver.version.data: MGE HID 1.57

driver.version.internal: 0.71

driver.version.usb: libusb-1.0.25 (API: 0x01000109)

input.frequency.nominal: 50

input.voltage.nominal: 240

ups.beeper.status: enabled

ups.mfr: EATON

ups.model: Eaton 9PX

ups.productid: ffff

ups.serial: REMOVED

ups.status:

ups.test.result: Done and passed

ups.vendorid: 0463

1 minute ago, lowsanity said:

Legend!

I've tested https://github.com/networkupstools/nut/pull/3149 from https://github.com/networkupstools/nut/issues/3136 and can see my UPS.

battery.capacity: 9.00

battery.charger.type: Constant Charge (CC)

device.mfr: EATON

device.model: Eaton 9PX

device.serial: REMOVED

device.type: ups

driver.debug: 6

driver.flag.allow_killpower: 0

driver.name: usbhid-ups

driver.parameter.interrupt_pipe_no_events_tolerance: -1

driver.parameter.pollfreq: 30

driver.parameter.pollinterval: 2

driver.parameter.port: auto

driver.parameter.synchronous: yes

driver.state: quiet

driver.version: 2.8.4.690.6-696+g7715f839b

driver.version.data: MGE HID 1.57

driver.version.internal: 0.71

driver.version.usb: libusb-1.0.25 (API: 0x01000109)

input.frequency.nominal: 50

input.voltage.nominal: 240

ups.beeper.status: enabled

ups.mfr: EATON

ups.model: Eaton 9PX

ups.productid: ffff

ups.serial: REMOVED

ups.status:

ups.test.result: Done and passed

ups.vendorid: 0463

Perfect, thanks for reporting back. I'll get the changes baked into the next update and will let you know. 😁

53 minutes ago, lowsanity said:

Legend!

I've tested https://github.com/networkupstools/nut/pull/3149 from https://github.com/networkupstools/nut/issues/3136 and can see my UPS.

battery.capacity: 9.00

battery.charger.type: Constant Charge (CC)

device.mfr: EATON

device.model: Eaton 9PX

device.serial: REMOVED

device.type: ups

driver.debug: 6

driver.flag.allow_killpower: 0

driver.name: usbhid-ups

driver.parameter.interrupt_pipe_no_events_tolerance: -1

driver.parameter.pollfreq: 30

driver.parameter.pollinterval: 2

driver.parameter.port: auto

driver.parameter.synchronous: yes

driver.state: quiet

driver.version: 2.8.4.690.6-696+g7715f839b

driver.version.data: MGE HID 1.57

driver.version.internal: 0.71

driver.version.usb: libusb-1.0.25 (API: 0x01000109)

input.frequency.nominal: 50

input.voltage.nominal: 240

ups.beeper.status: enabled

ups.mfr: EATON

ups.model: Eaton 9PX

ups.productid: ffff

ups.serial: REMOVED

ups.status:

ups.test.result: Done and passed

ups.vendorid: 0463

Any chance you could post a log with "UPS Driver Debug Level" set to 6?

Just to see if it's doing what we want it to do...

On 11/6/2025 at 9:09 PM, Rysz said:

Any chance you could post a log with "UPS Driver Debug Level" set to 6?

Just to see if it's doing what we want it to do...

Sure. Attached and below snip where it tried one HID descriptor, then another.

0.140182 [D2] Checking device 3 of 8 (0463/FFFF)

0.141095 [D2] - VendorID: 0463

0.141096 [D2] - ProductID: ffff

0.141097 [D2] - Manufacturer: EATON

0.141098 [D2] - Product: Eaton 9PX

0.141098 [D2] - Serial Number: REMOVED

0.141099 [D2] - Bus: 001

0.141099 [D2] - Bus Port: 003

0.141100 [D2] - Device: 003

0.141100 [D2] - Device release number: 0202

0.141101 [D2] Trying to match device

0.141102 [D2] match_function_subdriver (non-SHUT mode): matching a device...

0.141103 [D3] match_function_regex: matching a device...

0.141104 [D2] Device matches

0.141105 [D2] Reading configuration descriptor 1 of 1

0.141107 [D3] libusb_kernel_driver_active() returned 0: Success

0.141113 [D2] Claimed interface 0 successfully

0.141114 [D3] nut_libusb_set_altinterface: skipped libusb_set_interface_alt_setting(udev, 0, 0)

0.141255 [D2] Retrieved HID descriptor (expected 9, got 9)

0.141257 [D3] HID descriptor, method 1: (9 bytes) => 09 21 10 01 21 01 22 5f 12

0.141258 [D3] HID descriptor length (method 1) 4703

0.141258 [D4] i=0, extra[i]=09, extra[i+1]=21

0.141259 [D3] HID descriptor, method 2: (9 bytes) => 09 21 10 01 21 01 22 84 04

0.141260 [D3] HID descriptor length (method 2) 1156

0.141261 [D1] Eaton device v2.02. Using full report descriptor

0.141261 [D2] Warning: two different HID descriptors retrieved (Reportlen = 4703 vs. 1156)

0.141262 [D2] Trying HID descriptor length 4703

0.141269 [D2] Unable to get Report descriptor: Resource temporarily unavailable

0.141269 [D2] Trying HID descriptor length 1156

0.147121 [D2] Report Descriptor size = 1156

usbhid-debug.log

Edited November 7, 2025Nov 7 by lowsanity

Ubiquiti UPS 2U

Unraid 7.0.1

NUT 2025.11.01b

I have turned on the NUT Server on my 2U UPS and i have NUT Tools plugin installed on my unraid server but when I start NUT tools on my unraid server it does not report any UPS statuses.

• Unifi Setting-

ID / Port: UPS2UServer:3493

Username: test

Password: password

• Unraid NUT Tools settings-

Network UPS Tools Backend:

nut-2.8.4-x86_64-1stable.ssl31 nut-actions-2025.02.25

Start Network UPS Tools Service: Yes   

NUT Mode: Slave

NUT Master IP Address[:Port]: (UPS IP):3493

NUT Monitor Username: username in UPS settings

NUT Monitor Password: password in UPS settings

UPS Name: UPS

UPS Battery Runtime Attribute:              

battery.runtime

Shutdown Mode:            

Battery Level

1 minute ago, MrDrux said:

Ubiquiti UPS 2U

Unraid 7.0.1

NUT 2025.11.01b

I have turned on the NUT Server on my 2U UPS and i have NUT Tools plugin installed on my unraid server but when I start NUT tools on my unraid server it does not report any UPS statuses.

• Unifi Setting-

ID / Port: UPS2UServer:3493

Username: test

Password: password

• Unraid NUT Tools settings-

Network UPS Tools Backend:

nut-2.8.4-x86_64-1stable.ssl31 nut-actions-2025.02.25

Start Network UPS Tools Service: Yes   

NUT Mode: Slave

NUT Master IP Address[:Port]: (UPS IP):3493

NUT Monitor Username: username in UPS settings

NUT Monitor Password: password in UPS settings

UPS Name: UPS

UPS Battery Runtime Attribute:              

battery.runtime

Shutdown Mode:            

Battery Level

You need to set the UPS Name to the UniFi NUT server ID and disable authentication on the UniFi NUT server.

15 minutes ago, Rysz said:

You need to set the UPS Name to the UniFi NUT server ID and disable authentication on the UniFi NUT server.

This didn't work. it gave me this error in the log and failed to start.

"rc.nut: Fatal error: insufficient power configured!"

with authentication it starts but doesn't give me ups status

EDIT

Figured it out. you do need the name to match the ID but you need authentication enabled too

Edited November 8, 2025Nov 8 by MrDrux
additional info

Hello everyone, wondering if a fix has been found for an issue with one of those new GoldenMate UPS units.

Everything appears to be working correctly save for an annoying tendency to sporadically (but consistently) send a "UPS is on battery. The system will shutdown in 600 seconds." notification, followed shortly (within a minute) by a "UPS is online, any planned shutdowns were cancelled." notification.

Have seen at least one other person with this issue though I'm unsure if a solution has been found. It is the new upgraded '2025' version with the USB port, which so far seems to be a nice unit otherwise so I'm hoping we can figure out a fix. Happy to post logs if anyone is kind enough to detail the best way for me to provide them.

For clarity it is being monitored via NUT as the built-in UPS settings don't seem to detect this model. Any help is appreciated!

On 11/7/2025 at 12:44 PM, lowsanity said:

Sure. Attached and below snip where it tried one HID descriptor, then another.

0.140182 [D2] Checking device 3 of 8 (0463/FFFF)

0.141095 [D2] - VendorID: 0463

0.141096 [D2] - ProductID: ffff

0.141097 [D2] - Manufacturer: EATON

0.141098 [D2] - Product: Eaton 9PX

0.141098 [D2] - Serial Number: REMOVED

0.141099 [D2] - Bus: 001

0.141099 [D2] - Bus Port: 003

0.141100 [D2] - Device: 003

0.141100 [D2] - Device release number: 0202

0.141101 [D2] Trying to match device

0.141102 [D2] match_function_subdriver (non-SHUT mode): matching a device...

0.141103 [D3] match_function_regex: matching a device...

0.141104 [D2] Device matches

0.141105 [D2] Reading configuration descriptor 1 of 1

0.141107 [D3] libusb_kernel_driver_active() returned 0: Success

0.141113 [D2] Claimed interface 0 successfully

0.141114 [D3] nut_libusb_set_altinterface: skipped libusb_set_interface_alt_setting(udev, 0, 0)

0.141255 [D2] Retrieved HID descriptor (expected 9, got 9)

0.141257 [D3] HID descriptor, method 1: (9 bytes) => 09 21 10 01 21 01 22 5f 12

0.141258 [D3] HID descriptor length (method 1) 4703

0.141258 [D4] i=0, extra[i]=09, extra[i+1]=21

0.141259 [D3] HID descriptor, method 2: (9 bytes) => 09 21 10 01 21 01 22 84 04

0.141260 [D3] HID descriptor length (method 2) 1156

0.141261 [D1] Eaton device v2.02. Using full report descriptor

0.141261 [D2] Warning: two different HID descriptors retrieved (Reportlen = 4703 vs. 1156)

0.141262 [D2] Trying HID descriptor length 4703

0.141269 [D2] Unable to get Report descriptor: Resource temporarily unavailable

0.141269 [D2] Trying HID descriptor length 1156

0.147121 [D2] Report Descriptor size = 1156

usbhid-debug.log

Thanks, you can now switch the NUT backend to "preview (latest build)" before updating.

After the update you'll be on the version that has this change baked in, backend should say something including "master".

If you saw this after updating already, switch the NUT backend to "preview (latest build)" and reinstall the plugin or just reboot.

Hi !

I installed the NUT plugin today but I cannot find my UPS.

On my other linux server I have the following config:

maxretry = 3

[eaton]

driver = "usbhid-ups"

port = "/dev/bus/usb/001/015"

vendorid = "0463"

productid = "FFFF"

product = "Ellipse ECO"

serial = "000000000"

vendor = "EATON"

on my linux server I have upsc v 2.7.4 which is older than then version shipped by the plugin (v 2.8.4). any idea why it is not finding the device ?

1 hour ago, ChristianHahn said:

Hi !

I installed the NUT plugin today but I cannot find my UPS.

On my other linux server I have the following config:

maxretry = 3

[eaton]

driver = "usbhid-ups"

port = "/dev/bus/usb/001/015"

vendorid = "0463"

productid = "FFFF"

product = "Ellipse ECO"

serial = "000000000"

vendor = "EATON"

on my linux server I have upsc v 2.7.4 which is older than then version shipped by the plugin (v 2.8.4). any idea why it is not finding the device ?

Please post the NUT debug package that you can find in NUT settings.

Just to clarify, you want to connect to a remote NUT server, or the UPS is connected to your Unraid server?

I want to connect to a UPS connected via USB to Unraid.

nut-debug-20251110132545.zip

Edited November 10, 2025Nov 10 by ChristianHahn

1 hour ago, ChristianHahn said:

I want to connect to a UPS connected via USB to Unraid.

nut-debug-20251110132545.zip

And this was with the UPS connected via USB?

Nothing is detected at all... which leads me to think USB port, USB cable...?

I'd start with trying a USB 2.0 port, if you have one, or any other USB port really...

Especially as Eaton are among the best supported and most used devices with NUT.

strange - I reconnected now the USB cabel and now it work

Thanks anyways for helping out

Just commenting to say that my Unifi UPS Tower connected perfectly when I disabled the credentials on the UPS but used dummy credentials. Thank you!

20 minutes ago, mcreekmore said:

Just commenting to say that my Unifi UPS Tower connected perfectly when I disabled the credentials on the UPS but used dummy credentials. Thank you!

I case anyone else is having trouble with their Unifi UPS, here are my settings