Does this plugin work with the Smart-UPS SC620 UPS connected via a serial port (RS232)?

 

 

I have a CyberPower LX1500GU3

 

It reports 0 Load with my unraid plugged into it, and 7 min 30 for remaining batter , I know this is not correct

 

here is my config , any thoughts

 

 

[upsunraid]
driver = usbhid-ups
port = auto
vendorid = "0764"
productid = "0601"
bus = "009"
 

Hi!

I have a GreenCell Micropower 1500VA UPS and it was working great with for quite some time with the blaze usb driver. However something happened and the battery charge percentage no longer updates. This results in my system not shutting down gracefully upon power outage.

I can see the UPS load and the battery voltage indicator still updating.

 

If someone can look on it please do. Thank you.

nut-debug-20241219105328.zip nut-ups.dev

I noticed my NUT has been stopped for a while, and tried to investigate.
It has run for months without issue, I have updated everything (unraid, plugin) and cannot get it to start.

my log is as follows
 

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

the scanner button next to the driver selector shows it is recognized

 

-----------------------------------------------------
INFO: The NUT Scanner is also available from the terminal with more advanced settings.
INFO: You can use 'nut-scanner -h' to see all available options for searching UPS devices.
-----------------------------------------------------

Reading the system network configuration...

NUT Scanner is now searching for UPS devices...
#####################################################

[nutdev-usb1]
driver = "usbhid-ups"
port = "auto"
vendorid = "0463"
productid = "FFFF"
product = "Ellipse ECO"
serial = "000000000"
vendor = "EATON"
# bus = "001"
# device = "004"
# busport = "007"

#####################################################

Apart from regular updates I have not touched any plugin settings or the usb port it is connected to since I put it into operation, and it has worked there for a long time before I ran into this issue.

On 12/5/2024 at 10:11 AM, Rysz said:

 

That APC BX series is known to suffer from this (what we believe to be) firmware issue and we've put patches in place to suppress this unwanted behaviour on the UPS side. Here's how you can set it up:

• Go to NUT Settings.
• Set Network UPS Tools Backend Switch to preview (latest build).
• Apply settings and either reinstall NUT or reboot the machine.
• Confirm the Network UPS Tools Backend now has "master" in the name.
• Using the NUT Configuration Editor (in NUT Settings) put at the end of ups.conf (after line 8 or later):

  pollonly
  lbrb_log_delay_sec = 3
  lbrb_log_delay_without_calibrating

• Save the configuration file and restart NUT.
• After reloading the NUT Settings page, confirm the made changes are still present in ups.conf.

Please let us know if the process worked out for you or if you have any additional questions. 🙂 

 

I'm having same problem with a BX1200MI.

 

In my case it always shows 99% and charging.

 

I'm following this post too. There, reference is made to other possible solutions in the configuration.

 

For now, given that your suggestions here are more recent, I'll try what you suggest and see what the result is.

 

THANK YOU VERY MUCH for your great plugin. I think that should be included in the new UnRAID v7.0 and replace the old one.

 

Edited December 25, 20241 yr by JAnguita

I have a Cyberpower CP1350PFCLCD set up with the Nutv2 plugin.  The plugin can start and read a lot of static information, but it does not show any output or load metrics.  I'm using the usb-hid driver and everything else seems to work.  Amy I missing something?  Output is one of the more important metrics behind time remaining.

I am getting the error below when i try to startup nut.

 

TrippLite device (09ae:3018) is not (or perhaps not yet) supported

 

and it just spams the log with, any idea what i am doing wrong?

 

Jan  4 22:13:34 MovieServer kernel: hid-generic 0003:09AE:3018.0C45: hiddev97,hidraw1: USB HID v1.10 Device [Tripp Lite  TRIPP LITE SMART1500RM2UL ] on usb-0000:00:14.0-11.2/input0
Jan  4 22:13:49 MovieServer kernel: usb 1-11.2: USB disconnect, device number 95
Jan  4 22:13:49 MovieServer kernel: usb 1-11.2: new low-speed USB device number 96 using xhci_hcd
Jan  4 22:13:50 MovieServer kernel: hid-generic 0003:09AE:3018.0C46: hiddev97,hidraw1: USB HID v1.10 Device [Tripp Lite  TRIPP LITE SMART1500RM2UL ] on usb-0000:00:14.0-11.2/input0
Jan  4 22:14:04 MovieServer kernel: usb 1-11.2: USB disconnect, device number 96
Jan  4 22:14:04 MovieServer kernel: usb 1-11.2: new low-speed USB device number 97 using xhci_hcd
Jan  4 22:14:04 MovieServer kernel: hid-generic 0003:09AE:3018.0C47: hiddev97,hidraw1: USB HID v1.10 Device [Tripp Lite  TRIPP LITE SMART1500RM2UL ] on usb-0000:00:14.0-11.2/input0
Jan  4 22:14:19 MovieServer kernel: usb 1-11.2: USB disconnect, device number 97

 

Apologies for the late reply on the recent posts as I've been more caught up with daily life. Unfortunately most if not all of these issues are (backend) driver and not plugin related, so they are essentially out of my control as the plugin (and not backend) developer - I can only suggest reading up more on connection issues and possible fixes here:

... or take your issue to the NUT developers on GitHub: https://github.com/networkupstools/nut/issues

Somehow the runtime shown here:

 

is different from battery.runtime number:

 

 

10392 sec = 2 hr 53 mins (this is the accurate runtime left shown from UPS itself.)

 

Thanks!

nut-debug-20250111173435.zip

On 2/24/2024 at 10:57 PM, teufelhunden said:

I have a American Power Conversion  Smart-UPS C 1500. This device is recoginzed when connecting it to my unraid server via USB. When trying to set up the plugin though I keep getting these errors in the logs. 
Feb 24 22:34:16 Hermes root: Using subdriver: APC HID 0.100
Feb 24 22:34:16 Hermes root: Network UPS Tools - Generic HID driver 0.52 (2.8.1.1)
Feb 24 22:34:16 Hermes root: USB communication driver (libusb 1.0) 0.46
Feb 24 22:34:16 Hermes root: nut_libusb_get_report: Input/Output Error
Feb 24 22:34:16 Hermes root: Can't initialize data from HID UPS
Feb 24 22:34:16 Hermes root: Driver failed to start (exit status=1)

 

I'm trying to use this as a network server so I can also shut down my pfsense box with it. I tried looking around and this is a brand new USB cable and connected to a  USB 2.0 port on this X13SAE-F motherboard. 

 

Any ideas. 

Having the same issue with the same model UPS. Was curious which settings you were using for your Driver and Driver port. Cheers!

On 5/2/2024 at 4:07 PM, VodkaPump said:

I've seen a fair few people report issues with PowerWalker/BlueWalker UPS' stopping working and needing a server reboot (or just a replug) both here and on reddit.
I've been struggling with the same, usually it'll wok great for 3-4 days (sometimes a full week!) without needing to be replugged.

 

I've found a solution to this, adding: pollonly = "enabled" to your ups.conf. My UPS has not disconnected for over a full month now since doing this.
Just posting this here as this hread shows up when googling issues with NUT and PowerWalker/BlueWalker.

Hi there,

 

Do you have a screenshot of your NUT settings of your PowerWalker/BlueWalker you are using. You like to share?
I do have PowerWalker/BlueWalker but stop using it on unraid since mine stops after som days.
Hopefully I can try again, but i don't remember the settings I was using.

Like to share your settings?

Appologies if this is a basic question. I have installed the NUT plugin and this is running on my Unraid server. I want to connect to the UPS status from home assistant. I have automations based on the UPS status. 

 

My Unraid server is on 192.168.1.3 

My Homeassistant Server is running on 192.168.1.57 as a VM

 

I simply cant connect to the NUT Server on Unraid. Here is the configuration screen on Home Assistant

 

 

 

NUT settings 

 

 

 

Is the default port correct. Or do I need to change something for Home Assistant to be able to connect to 192.168.1.3 Unraid IP.  New to Unraid so apologies if this is a basic question.

 

Thanks

 

Andy 

 

 

1 hour ago, Andyzzzz1 said:

Or do I need to change something for Home Assistant to be able to connect to 192.168.1.3 Unraid IP.

No.

 

Also ensure they are in same network bridge, i.e. br0 br1 etc.

Hey, I am running a vertiv gxt5 UPS and with some messing I got it working, but it isn't showing all stats. is there anything I can do to get the UPS load to show? I am using a USB connection 

Hello,

 

I have a Cyberpower UPS and it works fine with NUT. However after migrating to a new server and upgrading to Unraid 7.0 my syslog is filling up with this message:

Jan 26 13:22:09 Green usbhid-ups[713416]: nut_libusb_get_report: Input/Output Error
Jan 26 13:22:11 Green usbhid-ups[713416]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Jan 26 13:22:11 Green usbhid-ups[713416]: nut_libusb_get_string: Input/Output Error
Jan 26 13:25:36 Green usbhid-ups[713416]: nut_libusb_get_report: Input/Output Error
Jan 26 13:25:38 Green usbhid-ups[713416]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Jan 26 13:32:53 Green monitor_nchan: Stop running nchan processes
Jan 26 13:36:52 Green usbhid-ups[713416]: nut_libusb_get_string: Input/Output Error
Jan 26 13:39:32 Green usbhid-ups[713416]: nut_libusb_get_report: Input/Output Error
Jan 26 13:39:34 Green usbhid-ups[713416]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Jan 26 13:39:34 Green usbhid-ups[713416]: nut_libusb_get_string: Pipe error
Jan 26 13:40:38 Green usbhid-ups[713416]: nut_libusb_get_report: Input/Output Error
Jan 26 13:40:40 Green usbhid-ups[713416]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Jan 26 13:45:27 Green usbhid-ups[713416]: nut_libusb_get_report: Input/Output Error
Jan 26 13:45:29 Green usbhid-ups[713416]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!

This never used to happen with my old server. I found some old advice of adding "pollonly" to line 8 of the ups.conf, but when I did that NUT refused to start stating that:

Jan 26 13:18:01 Green rc.nut: Can't open /var/run/nut/usbhid-ups-ups.pid: No such file or directory
Jan 26 13:18:01 Green rc.nut: Can't open /var/run/nut/usbhid-ups-auto.pid either: No such file or directory

 

So I reset the config and restarted it, and now it's working again, albeit with the above Input/Output errors. This never used to happen on my old server, and I'm using the same USB cable as before. Any ideas? 

We experienced a power outage yesterday and the NUT plugin failed to execute a safe shutdown sequence but fortunately I was home to take care of it. I've attached syslog notifications showing the sequence of events, but to provide some context we initially had the power go out for a few seconds, come back on for 3-4 seconds, then finally going off again continuously for about 2 hours.

 

The nut plugin showed the system was on battery power and even gave an alert twice that it was going to start the shutdown sequence in 360 seconds (I have unraid set to shutdown 6 minutes after going on battery, NUT settings shown below). There was notification that the initial shutdown sequence would be cancelled, but you can see that a secondary sequence was started immediately afterwards. I'm wondering if there was some timing issue where both shutdown sequences were cancelled while still on battery power. Ultimately NUT did not start start a shutdown sequence and I had to safely shutdown everything manually.

 

Any thoughts on a more robust method for ensuring this doesn't happen?

 

Regarding the attached images (specifically syslog), the initial power loss was on the 26th at the start of the log shown. The shutdown sequence at the end of the log on the 27th was me testing to make sure NUT was behaving as expected with a "normal" power loss scenario - I just pulled the UPS plug and NUT shut everything down safely as expected.

5 hours ago, cinsun42 said:

We experienced a power outage yesterday and the NUT plugin failed to execute a safe shutdown sequence but fortunately I was home to take care of it. I've attached syslog notifications showing the sequence of events, but to provide some context we initially had the power go out for a few seconds, come back on for 3-4 seconds, then finally going off again continuously for about 2 hours.

 

The nut plugin showed the system was on battery power and even gave an alert twice that it was going to start the shutdown sequence in 360 seconds (I have unraid set to shutdown 6 minutes after going on battery, NUT settings shown below). There was notification that the initial shutdown sequence would be cancelled, but you can see that a secondary sequence was started immediately afterwards. I'm wondering if there was some timing issue where both shutdown sequences were cancelled while still on battery power. Ultimately NUT did not start start a shutdown sequence and I had to safely shutdown everything manually.

 

Any thoughts on a more robust method for ensuring this doesn't happen?

 

Regarding the attached images (specifically syslog), the initial power loss was on the 26th at the start of the log shown. The shutdown sequence at the end of the log on the 27th was me testing to make sure NUT was behaving as expected with a "normal" power loss scenario - I just pulled the UPS plug and NUT shut everything down safely as expected.

 

It's hard to trace a problem from these logs, everything seemed to work as expected (except for it actually shutting down). Interestingly, it also doesn't seem like some kind of race condition has occurred. The logic of the notification-handling shutdown script has been largely unchanged for the past 8 years and I've not had a significant number of other reports of this happening, so I'd consider it more of a random occurrence (especially as it seems to work in your later test). I'll still look some more into what could possibly lead to (?) race conditions and how to make the notification handling more resilient - thanks. 🙂 

 

On 1/23/2025 at 12:49 PM, mayberts said:

Hey, I am running a vertiv gxt5 UPS and with some messing I got it working, but it isn't showing all stats. is there anything I can do to get the UPS load to show? I am using a USB connection 

 

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

 

On 1/26/2025 at 8:52 PM, mattalat said:

Hello,

 

I have a Cyberpower UPS and it works fine with NUT. However after migrating to a new server and upgrading to Unraid 7.0 my syslog is filling up with this message:

Jan 26 13:22:09 Green usbhid-ups[713416]: nut_libusb_get_report: Input/Output Error
Jan 26 13:22:11 Green usbhid-ups[713416]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Jan 26 13:22:11 Green usbhid-ups[713416]: nut_libusb_get_string: Input/Output Error
Jan 26 13:25:36 Green usbhid-ups[713416]: nut_libusb_get_report: Input/Output Error
Jan 26 13:25:38 Green usbhid-ups[713416]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Jan 26 13:32:53 Green monitor_nchan: Stop running nchan processes
Jan 26 13:36:52 Green usbhid-ups[713416]: nut_libusb_get_string: Input/Output Error
Jan 26 13:39:32 Green usbhid-ups[713416]: nut_libusb_get_report: Input/Output Error
Jan 26 13:39:34 Green usbhid-ups[713416]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Jan 26 13:39:34 Green usbhid-ups[713416]: nut_libusb_get_string: Pipe error
Jan 26 13:40:38 Green usbhid-ups[713416]: nut_libusb_get_report: Input/Output Error
Jan 26 13:40:40 Green usbhid-ups[713416]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Jan 26 13:45:27 Green usbhid-ups[713416]: nut_libusb_get_report: Input/Output Error
Jan 26 13:45:29 Green usbhid-ups[713416]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!

This never used to happen with my old server. I found some old advice of adding "pollonly" to line 8 of the ups.conf, but when I did that NUT refused to start stating that:

Jan 26 13:18:01 Green rc.nut: Can't open /var/run/nut/usbhid-ups-ups.pid: No such file or directory
Jan 26 13:18:01 Green rc.nut: Can't open /var/run/nut/usbhid-ups-auto.pid either: No such file or directory

 

So I reset the config and restarted it, and now it's working again, albeit with the above Input/Output errors. This never used to happen on my old server, and I'm using the same USB cable as before. Any ideas? 

 

Most likely a change in the kernel's USB handling that affects your specific device, you can try on another USB port or with another USB cable and see if that does anything. Please also post your NUT Debug Package that can be found on NUT Settings page.

7 minutes ago, Rysz said:

 

It's hard to trace a problem from these logs, everything seemed to work as expected (except for it actually shutting down). Interestingly, it also doesn't seem like some kind of race condition has occurred. The logic of the notification-handling shutdown script has been largely unchanged for the past 8 years and I've not had a significant number of other reports of this happening, so I'd consider it more of a random occurrence (especially as it seems to work in your later test). I'll still look some more into what could possibly lead to (?) race conditions and how to make the notification handling more resilient - thanks. 🙂 

 

 

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

 

 

Most likely a change in the kernel's USB handling that affects your specific device, you can try on another USB port or with another USB cable and see if that does anything. Please also post your NUT Debug Package that can be found on NUT Settings page.

I have tried switching from a USB 3.0 to USB 2.0 port with no improvement. In the meantime I've set my NUT server to run on my old (now backup) server and all seems to be working fine. Debug package attached.

nut-debug-20250127235828.zip

22 minutes ago, mattalat said:

I have tried switching from a USB 3.0 to USB 2.0 port with no improvement. In the meantime I've set my NUT server to run on my old (now backup) server and all seems to be working fine. Debug package attached.

nut-debug-20250127235828.zip 151.62 kB · 0 downloads

 

It does seem like something on the USB-side of things has changed (in the kernel/OS), so I'm afraid at this point all you can do is keep it as it is now (running on the older server) or filter out these logs if it generally works despite the spamming (using the "Enable Rule-Based Syslog Filters" or "Redirection for NUT Service Logs" in NUT Settings). Hopefully a future kernel update (in the next OS versions) will resolve the issue. You can also play around with the different NUT backends (in NUT Settings) and see if using another NUT backend resolves the problem for you.

 

I'm going rackmount now and need a new UPS. I'm thinking of going with Eaton this time, but when I look at the supported models it doesn't list all of them on this page: https://networkupstools.org/ddl/Eaton/index.html

I was thinking of something from the Eaton 5P or Eaton 5PX G2 series, but I don't see many listed there.

Any thoughts on that? Should it still work as the protocol is the same?

13 hours ago, talonserver said:

I'm going rackmount now and need a new UPS. I'm thinking of going with Eaton this time, but when I look at the supported models it doesn't list all of them on this page: https://networkupstools.org/ddl/Eaton/index.html

I was thinking of something from the Eaton 5P or Eaton 5PX G2 series, but I don't see many listed there.

Any thoughts on that? Should it still work as the protocol is the same?

 

Eaton is by far the best supported vendor for NUT (and was a long time sponsor of the project).

I use an Eaton 5P series myself and I'm extremely happy with it. 🙂 

 

Usually you just need to look if the series, rather than the specific model, is supported.

Anyway, for Eaton they all use the same HID, so most if not all are compatible one way or another.

 

17 hours ago, Rysz said:

 

Eaton is by far the best supported vendor for NUT (and was a long time sponsor of the project).

I use an Eaton 5P series myself and I'm extremely happy with it. 🙂 

 

Usually you just need to look if the series, rather than the specific model, is supported.

Anyway, for Eaton they all use the same HID, so most if not all are compatible one way or another.

 

K thanks!

On 10/1/2023 at 3:51 PM, Rysz said:

Please install Network UPS Tools (NUT) for UNRAID by Rysz from Community Applications. The older plugins (including the one in the first post of this topic) are deprecated/now unsupported.

For the life of me, I cant find  Network UPS Tools (NUT) for UNRAID from you. The one I can only see is by dessertwitch? How do I get this?

1 minute ago, japurillo said:

For the life of me, I cant find  Network UPS Tools (NUT) for UNRAID from you. The one I can only see is by dessertwitch? How do I get this?

 

Mine is the "desertwitch" one, seems the display was recently changed to the GitHub repository name. Thanks, I'll update it in the post so it's less confusing.

@RyszI’ve searched around a bit but only found one similar posted question that was never answered. Does the plug-in allow for UPS event triggers to run an external script? I have it all running as a Netserver and slave for two Unraid servers, but I also need to run a script to gracefully shutdown a Ubiquiti UDM Pro router and my understanding is that I have to use a script to do that until Ubiquiti builds NUT into their software (if they ever do). Anyone else with a similar issue that can comment on how they solved this? Need both the method for executing a script and preferable another UDM Pro user that has a script that works. Thank you!