Here it is, thanks!

nut-debug-20250405192327.zip

4 hours ago, jquery said:

I am trying to get an ecoflow delta 3 plus to work with NUT. It is on the compatibility list, so it should work. However, I can't even get the NUT service to start. Right after installing the NUT plugin, without any changes to the settings, I get this error: 

 

"NUT was not able to start successfully - please check the SYSLOG for more information."

 

Syslog says this:

Writing NUT configuration...
rc.nut: Updating permissions for NUT...
rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
rc.nut: Disabling the NUT Runtime Statistics Module...
rc.nut: Network UPS Tools - Generic HID driver 0.53 (2.8.2)
rc.nut: USB communication driver (libusb 1.0) 0.47
rc.nut: libusb1: Could not open any HID devices: insufficient permissions on everything
rc.nut: No matching HID UPS found
rc.nut: Driver failed to start (exit status=1)
rc.nut: Network UPS Tools - UPS driver controller 2.8.2

 

Any help is appreciated.

I believe this was actually added to the master branch a couple weeks ago for NUT so its possible that if the plugin is complied again with master this will be addressed as Generic HID driver 0.61 I believe has the fix.
Link to PR for adding ecoflow to NUT
https://github.com/networkupstools/nut/pull/2837

17 hours ago, Slimfat said:

I believe this was actually added to the master branch a couple weeks ago for NUT so its possible that if the plugin is complied again with master this will be addressed as Generic HID driver 0.61 I believe has the fix.
Link to PR for adding ecoflow to NUT
https://github.com/networkupstools/nut/pull/2837

It would be awesome if that was the solution! Any idea when the next version of NUT for unraid will be released, so I can try ecoflow support?

I actually also purchased an EcoFlow River 3 Plus and saw the PR that it was merged into NUT master.

 

I chose "preview (latest build)" in the backend switch. However, I can't tell from the version (nut-2.8.2-x86_64-7master.ssl31) about when it was actually refreshed or installed.

 

Is there a way to refresh how this preview build is chosen, so we can get the latest master build of NUT and get EcoFlow support?

I'll update the plugin today, but please don't create new accounts to bump your requests.

On 4/7/2025 at 8:29 AM, Rysz said:

I'll update the plugin today, but please don't create new accounts to bump your requests.

 

Just to follow up here, NUT 2.8.3 stable was just released and I am waiting for it to pass CI tests.

I'll hopefully be able to update the default and preview branches today or tomorrow at the latest. 🙂 

On 1/6/2022 at 7:04 PM, julzilla said:

G'Day,

 

New to NUT and having some issues with an older Eaton 5110 UPS  (http://powerquality.eaton.com/103004259-5591.aspx?cx=3&GUID=133F3D78-6347-45BB-95CB-FD97A6998A07)

Using Auto Detect I get:

        driver = "bcmxcp_usb"
        port = "auto"
        vendorid = "0592"
        productid = "0002"
        product = "Powerware UPS"
        vendor = "Powerware"
        bus = "002"

 

Services starts but reports almost every error under the sun for the UPS (ups.status = ALARM Online low battery) and won't report battery level, it will however report the correct line voltage and UPS load

. I connected the UPS to my Laptop and installed the proper 'Eaton Protection Software' where it shows the UPS functioning correctly and the battery having no problems at all (replaced both of them about 5 months back)

Read almost every post in regards to Eaton UPS's in NUT and tried finding additional info on https://networkupstools.org/ to no aval.

Attached screenshot of Nut Details below. Any help would be highly appreciated!

Kind Regards,
Julzilla

 

 

I am having this EXACT issue with this EXACT UPS. My 5110 is throwing a ton of critical errors despite Eaton software on my PC telling me that everything is in normal working order.

 

As Julzilla mentions in their edit, NUT is recognising this UPS as a Powerware 1500i instead of the Eaton 5110 that it is. bcmxcp_usb is the only driver that actually recognises that there is a device connected, but I am not able to get it to associate the correct model.

 

Grateful for any input on this! I have just paid for replacement batteries for the unit, so not super keen to replace the whole thing.

Edited April 9, 20251 yr by toast_ghost
Spelling/grammar

On 4/9/2025 at 9:00 AM, Rysz said:

 

Just to follow up here, NUT 2.8.3 stable was just released and I am waiting for it to pass CI tests.

I'll hopefully be able to update the default and preview branches today or tomorrow at the latest. 🙂 

Thank you so much for updating the plugin. Unfortunately, my Ecoflow is not being recognized. I also ran „Auto Config“ after resetting the configuration and it told me that no UPS devices were found. 
 

i feel like I am missing a very basic step or something.

nut-debug-20250410141028.zip

5 hours ago, jquery said:

Thank you so much for updating the plugin. Unfortunately, my Ecoflow is not being recognized. I also ran „Auto Config“ after resetting the configuration and it told me that no UPS devices were found. 
 

i feel like I am missing a very basic step or something.

nut-debug-20250410141028.zip 166.57 kB · 2 downloads

Is the ups running the latest firmware and is it plugged into the Unraid server? I ask this as i didn't see it listed in the lsusb log.

Also beware with Ecoflow as when you update the firmware it cuts the power to everything connected

Edited April 10, 20251 yr by Slimfat
added warning about ecoflow

3 hours ago, Slimfat said:

Is the ups running the latest firmware and is it plugged into the Unraid server? I ask this as i didn't see it listed in the lsusb log.

Also beware with Ecoflow as when you update the firmware it cuts the power to everything connected

Thanks for the warning. I found out that the connection works when I use a usb-c to usb-a cable and plug it into a usb-a port on my server. A usb-c to usb-c connection doesn’t work. Unfortunately I dont have a long enough cable laying around. I moved all the equipment around just to try this out 🤣
 

It may be the port, a configuration issue or the cable. I am not in the mood to troubleshoot further. I will simply buy a longer usb-c to usb-a cable and call it a win.

starting with the 7.1.0 betas, the NUT plugin seems to initiate a shutdown immediately after waking up from sleep mode. Does not happen under 7.0.1. or 7.0 with the same config. Is this a bug or do I need to adjust the NUT config because 7.1.0 may introduced something new?

Any help would be appreciated. Thanks!

Edit: Tried to export NUT debug package but ends up with the following error:
"ERROR: The NUT Debug Package Generation Script has failed - no response from the bash backend."

fuhlyserv01-diagnostics-20250412-1650.zip nut.log

Edited April 12, 20251 yr by T4ke

7 hours ago, T4ke said:

starting with the 7.1.0 betas, the NUT plugin seems to initiate a shutdown immediately after waking up from sleep mode. Does not happen under 7.0.1. or 7.0 with the same config. Is this a bug or do I need to adjust the NUT config because 7.1.0 may introduced something new?

Any help would be appreciated. Thanks!

Edit: Tried to export NUT debug package but ends up with the following error:
"ERROR: The NUT Debug Package Generation Script has failed - no response from the bash backend."

fuhlyserv01-diagnostics-20250412-1650.zip 294.5 kB · 1 download nut.log 44.52 kB · 0 downloads

I noted that too, mine is online, so there's always the alarm of 'UPS is in Converter Mode', and when it looses connection (very frequently) it initiate shutdown, if I 'sudo systemctl restart nut-server' where NUT server is running, my unraid will go down as well.

Apr 12 14:00:15 Tower upsmon[66261]: Communications with UPS [email protected] lost
Apr 12 14:00:15 Tower upsmon[66261]: UPS [[email protected]] was last known to be in an ALARM state and currently is not communicating, assuming dead.
Apr 12 14:00:15 Tower upsmon[66261]: Executing automatic power-fail shutdown

 

Quote

Because the UPS was in an alarm state + not communicating, and the default NUT behavior (ALARMCRITICAL) is enabled, the system initiated a shutdown to prevent possible data loss.

I tried adding ALARMCRITICAL 0 on upsmon.conf but didn't seem to do anything (after restarting nut-server).

On 4/10/2025 at 4:54 PM, jquery said:

Thanks for the warning. I found out that the connection works when I use a usb-c to usb-a cable and plug it into a usb-a port on my server. A usb-c to usb-c connection doesn’t work. Unfortunately I dont have a long enough cable laying around. I moved all the equipment around just to try this out 🤣
 

It may be the port, a configuration issue or the cable. I am not in the mood to troubleshoot further. I will simply buy a longer usb-c to usb-a cable and call it a win.

Good tip on the USB-C to USB-A cable. I have been trying to get NUT to work with the EcoFlow Delta 3 Plus without success with a USB-C to USB-C cable.

I got it to work with USB-C on the HID port on the EcoFlow and USB-A on the unRAID end.

• nut-2.8.3-x86_64-1stable.ssl31
• EcoFlow Delta 3 Plus with firmware V7.73.83.1

No UPS load metrics like I had with the Cyberpower though.

On 4/9/2025 at 10:42 AM, toast_ghost said:

 

I am having this EXACT issue with this EXACT UPS. My 5110 is throwing a ton of critical errors despite Eaton software on my PC telling me that everything is in normal working order.

 

As Julzilla mentions in their edit, NUT is recognising this UPS as a Powerware 1500i instead of the Eaton 5110 that it is. bcmxcp_usb is the only driver that actually recognises that there is a device connected, but I am not able to get it to associate the correct model.

 

Grateful for any input on this! I have just paid for replacement batteries for the unit, so not super keen to replace the whole thing.

 

Please post the NUT Debug Package found in the NUT Settings page.

 

18 hours ago, T4ke said:

starting with the 7.1.0 betas, the NUT plugin seems to initiate a shutdown immediately after waking up from sleep mode. Does not happen under 7.0.1. or 7.0 with the same config. Is this a bug or do I need to adjust the NUT config because 7.1.0 may introduced something new?

Any help would be appreciated. Thanks!

Edit: Tried to export NUT debug package but ends up with the following error:
"ERROR: The NUT Debug Package Generation Script has failed - no response from the bash backend."

fuhlyserv01-diagnostics-20250412-1650.zip 294.5 kB · 1 download nut.log 44.52 kB · 0 downloads

 

13 hours ago, Chriexpe said:

I noted that too, mine is online, so there's always the alarm of 'UPS is in Converter Mode', and when it looses connection (very frequently) it initiate shutdown, if I 'sudo systemctl restart nut-server' where NUT server is running, my unraid will go down as well.

Apr 12 14:00:15 Tower upsmon[66261]: Communications with UPS [email protected] lost
Apr 12 14:00:15 Tower upsmon[66261]: UPS [[email protected]] was last known to be in an ALARM state and currently is not communicating, assuming dead.
Apr 12 14:00:15 Tower upsmon[66261]: Executing automatic power-fail shutdown

 

I tried adding ALARMCRITICAL 0 on upsmon.conf but didn't seem to do anything (after restarting nut-server).

 

If it worked before, you might have better luck changing the backend to "previous" in the NUT Settings page and rebooting your system afterwards. In any case, sleep mode is highly dependent on the kernel and this may as well be a behavioural change between kernels. In general, the support for sleep mode in NUT is rudimentary at best, it's just not something the tool or any UPS really is designed to handle well (see various issues on the official project's GitHub).
 

12 hours ago, uberchuckie said:

Good tip on the USB-C to USB-A cable. I have been trying to get NUT to work with the EcoFlow Delta 3 Plus without success with a USB-C to USB-C cable.

I got it to work with USB-C on the HID port on the EcoFlow and USB-A on the unRAID end.

• nut-2.8.3-x86_64-1stable.ssl31
• EcoFlow Delta 3 Plus with firmware V7.73.83.1

No UPS load metrics like I had with the Cyberpower though.

 

Glad it works for you now. It seems the driver is still in its early stages and possibly that's why these values are still missing. In any case, UPS load is not a metric that is crucial for NUT, and all the really important metrics are there to safely shutdown your system in case of a power outage. The rest of the metrics are mostly for "eye-candy" in the dashboards.

54 minutes ago, Rysz said:

If it worked before, you might have better luck changing the backend to "previous" in the NUT Settings page and rebooting your system afterwards. In any case, sleep mode is highly dependent on the kernel and this may as well be a behavioural change between kernels. In general, the support for sleep mode in NUT is rudimentary at best, it's just not something the tool or any UPS really is designed to handle well (see various issues on the official project's GitHub).

I should have mentioned that I have already tried this but unfortunately it didn't make any difference.
In my case sleep mode is absolutely obliagorical for me which is why I'd rather live without NUT than sleep for the time being.
Thank you for your consideration though!

14 hours ago, Chriexpe said:

I noted that too, mine is online, so there's always the alarm of 'UPS is in Converter Mode', and when it looses connection (very frequently) it initiate shutdown, if I 'sudo systemctl restart nut-server' where NUT server is running, my unraid will go down as well.

Apr 12 14:00:15 Tower upsmon[66261]: Communications with UPS [email protected] lost
Apr 12 14:00:15 Tower upsmon[66261]: UPS [[email protected]] was last known to be in an ALARM state and currently is not communicating, assuming dead.
Apr 12 14:00:15 Tower upsmon[66261]: Executing automatic power-fail shutdown

 

I tried adding ALARMCRITICAL 0 on upsmon.conf but didn't seem to do anything (after restarting nut-server).

 

Did you put "ALARMCRITICAL 0" on line 9 or later in upsmon.conf?
The lines before that are overwritten by GUI settings (even if seeming empty).

Then you need to "Save" and "Restart NUT" for the setting to become effective.

The logs imply that the setting is not in effect there, so please double check that. 🙂 

 

10 minutes ago, T4ke said:

I should have mentioned that I have already tried this but unfortunately it didn't make any difference.
In my case sleep mode is absolutely obliagorical for me which is why I'd rather live without NUT than sleep for the time being.
Thank you for your consideration though!

 

Understandable, although if the previous backend does not restore that functionality for you, it's almost certainly a kernel-related behaviour change unrelated to the NUT plugin and/or underlying NUT software package (backend).

quick update on this, this doesn't seem to be related to NUT or any other plugin. It's still happening (at least to me) on 7.1.0-rc1 without any plugins installed. Something triggers the shutdown script right after waking up but I cannot identify what exactly. I would agree with the thesis that it is kernel related since we had a jump from 6.6.x to 6.12.x. Something changed in PM or whatever.

Meh. I could live without NUT for some time, but I cannot live without sleep. Going back to 7.0.1.

On 4/13/2025 at 7:20 PM, Rysz said:

 

Please post the NUT Debug Package found in the NUT Settings page.

 

Ahh apologies, of course. Thank you for following up!

nut-debug-20250414202327.zip

Hi all.  unRAID 6.4.13.  The NUT plugin has been working fine from what I can tell.  Now, it will not start.  I have removed and reinstalled all the versions on the dropdown, and none of them will start the pluging.  I am attaching the debug for the 2.8.3 version, but I can also reinstall and grab the others if needed (2.7.4, 2.8.1, 2.8.2).

 

Let me know if you need anything else.

nut-debug-20250414114828.zip

Is there a way to create an unraid notification (or some other kind of notification) if the NUT server fails to start on boot or crashes for any reason?

22 hours ago, J4bber said:

Hi all.  unRAID 6.4.13.  The NUT plugin has been working fine from what I can tell.  Now, it will not start.  I have removed and reinstalled all the versions on the dropdown, and none of them will start the pluging.  I am attaching the debug for the 2.8.3 version, but I can also reinstall and grab the others if needed (2.7.4, 2.8.1, 2.8.2).

 

Let me know if you need anything else.

nut-debug-20250414114828.zip 267.08 kB · 2 downloads

 

It doesn't seem to detect any UPS at all, maybe your USB cable or port is dead.

I'd try with another USB port or USB cable first, see if that does anything... 🙂 

I disconnected and reconnected the USB, and this did not help NUT find it, but it was in the lsusb output. I reinstalled NUT, and it is working now. I'm not sure what exactly happened, but it's working now.

 

Thanks for the help.

Edited April 15, 20251 yr by J4bber
typo

Hey there,

Is it possible to display more than 1 UPS in the GUI statistics panel and/or footer?

Reason is I have 2 UPSs and configured NUT correctly; it tracks both. 

However the UPS Name field, doesn't let me add commas to separate them.
If this is not possible, would this be a feature that would considered for this app?

Thanks in advance.

Not sure if I am doing something wrong but I am trying to connect NUT v2 on netserver to a Windows 11 machine with WinNUT-Client (which hasn't been updated in 2 years)

I have reset the settings on NUT, changed passwords and usernames but I have had zero luck getting it connected. I am always struck with the message " Connection to Nut Host IP ADDRESS Failed: No connection could be made because the target machine actively refused it" 
 
Now is this an issue with something I set up in NUT or is an issue with the client. And is there potentially an easier or newer version of a windows client that works with NUT?