[Plugin] NUT v2 - Network UPS Tools

[JimmyGerms 3]

Hi there! I posted a bit on another tread about a CyberPower CP1500PFCLCD UPS and some issues I was running into and wanted to post here on what I found. The goal is to edit my shutdown and start times for the CyberPower UPS because it does not play nice with "Turn off UPS after shutdown".

Problem:

 

This is what I just tried:

• ups.conf:

[CP1500]
	driver = usbhid-ups
	port = auto
	offdelay = 300
	ondelay = 0
	ignorelb
	override.battery.charge.low = 50
	override.battery.charge.warning = 60

• "Start Network UPS Tools service"=No (Because Yes would not start on reboot)
• "Enable Manual Config Only"=Yes
• Edited "/boot/config/go" to contain:
  • bash /etc/rc.d/rc.nut start

 

Upon a power outage the server will shutdown cleanly and the CP1500PFCLCD will count down from 5 min and remain off when done. When power is restored I see it counting down from 10 seconds and then it turns itself back on. Exactly what I want...EXCEPT...NUT will reset ups.delay.shutdown and ups.delay.start to their default values of 20 and 30 blowing the whole setup randomly.

 

When I noticed the reset I saw this in the logs:

usbhid-ups[16281]: nut_libusb_get_string: Pipe error.
usbhid-ups[16281]: nut_libusb_get_report: Input/Output Error.

Any help would be much appreciated. I would love to get my CyberPower UPS to shutdown and restart upon power loss/restore if possible!

Thanks!

 

EDIT:

After watching and reading the logs the reset is caused by whatever this error is doing:

usbhid-ups[3459]: nut_libusb_get_report: Input/Output Error.

Google is coming up with this thread and not much else around this error.

Edited January 8 by JimmyGerms

[seanzhang43 1]

Hi, dmacias.

 

I love this plugin, thank you very much!! 

 

BTW, any plan for supporting multi-language?  

[CS01-HS 34]

On 1/8/2021 at 12:33 AM, JimmyGerms said:

NUT will reset ups.delay.shutdown and ups.delay.start to their default values of 20 and 30 blowing the whole setup randomly.

 

Are you sure it's random? If e.g. it's reset on startup you can save the good version to your boot drive and copy it over in config/go (which I'm pretty sure runs after plugins are installed)

[JimmyGerms 3]

I don't believe it's as random as I'm thinking. It seems to reset every time this error pops up in the logs:

usbhid-ups[3459]: nut_libusb_get_report: Input/Output Error.

I cannot find much on google about this.

 

What I've done for now is setup a raspberry pie to be the netserver and I've had no issues so far. Thanks for the tutorial. It helped me get to where I needed to go!

Edited January 23 by JimmyGerms

[CS01-HS 34]

13 hours ago, JimmyGerms said:

Thanks for the tutorial. It helped me get to where I needed to go!

 

Glad it was helpful.

 

Actually I've updated it with misc reliability tweaks and a shift from battery level-based shutdown to timer-based shutdown. I was holding off until I had a few natural power outage/shutdowns to test with but I'm reasonably confident it's an improvement.

Edited January 23 by CS01-HS

[j5428 0]

Has anyone tried to get a Liebert GXT3 1500 UPS connected with a USB cable to work?  When I try to start the Nut plugin I get the following:

 

Writing nut config
Updating permissions...
Network UPS Tools - UPS driver controller 2.7.4.1
Network UPS Tools - Generic HID driver 0.55 (2.7.4.1)
USB communication driver 0.43
This Liebert device (10af:0000) is not (or perhaps not yet) supported
by usbhid-ups. Please make sure you have an up-to-date version of NUT. If
this does not fix the problem, try running the driver with the
'-x productid=0000' option. Please report your results to the NUT user's
mailing list <nut-upsuser@lists.alioth.debian.org>.

No matching HID UPS found
Driver failed to start (exit status=1)

 

Here is the ups.conf file I tried to add the suggestion in the error log to and it did not help.

 

[ups]
driver = Usbhid-ups
-x productid=0000
port = 10af:0000

 

 

Thank you in advance for any help.

 

 

 

 

Edited February 7 by j5428

[Surgikill 0]

Hi all,

 

I have a Tripp Lite SMART1500LCD UPS, and I'm having an issue getting the current wattage to show up correctly. I have a Kill-A-Watt connected between the UPS and the wall. It seems that no matter what I do, I cannot get an accurate reading. Currently, these are my settings for the UPS. The only driver that will work is usbhid, although I believe that the tripplite-usb driver should work.

 

 

Currently, NUT is showing around 520 watts of power being consumed, while the kill-a-watt is only showing 350.

 

This gets exacerbated when I try to import the data into grafana with nut-influxdb-exporter. The ups.power value shows nothing when selected, however when I select "watts" it shows the erroneously high value. Do I need to change username/password and select tripplite-usb to fix this? It's very frustrating.

 

[Vr2Io 181]

2 hours ago, Surgikill said:

Do I need to change username/password and select tripplite-usb to fix this? It's very frustrating.

No.

 

Most UPS won't provide power usage figure, plugin will calculate base on ups.load / output.current / other. You can setting "UPS Power and Load Display Settings" to tune that. And you should know UPS / Kill-A-Watt would provide very different figure is normal, accurate power measurement not a easy job.

 

[Surgikill 0]

4 hours ago, Vr2Io said:

No.

 

Most UPS won't provide power usage figure, plugin will calculate base on ups.load / output.current / other. You can setting "UPS Power and Load Display Settings" to tune that. And you should know UPS / Kill-A-Watt would provide very different figure is normal, accurate power measurement not a easy job.

 

This only fixes the display in unraid. It does not change the value that gets sent to influx db.

 

I would not expect the UPS to report a figure higher than the kill-a-watt. Currently, I have on-board power monitoring for all of my servers. The only non power monitored items in my rack are a non-poe switch, and a modem. If I am to take the power reported from each server and subtract it from the power reported by the UPS, I am left with around 100-150 watts of overhead, which is much more than my switch and modem pull.

 

Power factor correction is also enabled on all of the machines.

[david_w 0]

I am trying to get my Tripp Lite SMART1500LCDT to work with the NUT plugin. I am able to pass through the UPS's USB and get it to work on a Mint VM using NUT installed on the VM. But I cannot get it to work directly within Unraid with the NUT plugin.  On the VM I have to change the /lib/udev/rules.d/62-nut-usbups.rules to just contain the following:

 

SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end"

# TrippLite
#  e.g. TrippLite SMART1500LCD - usbhid-ups
ACTION=="add|change", SUBSYSTEM=="usb|usb_device", SUBSYSTEMS=="usb|usb_device", ATTR{idVendor}=="09ae", ATTR{idProduct}=="3016", MODE="664", GROUP="nut", RUN+="/sbin/upsdrvctl stop; /sbin/upsdrvctl start"

LABEL="nut-usbups_rules_end"

However, unraid overwrites the udev folder on boot. So this is not an option. Is there some way for me to update this file and not have it overwritten? The plugin adds this file somehow (it's not in the udev folder when the plugin is uninstalled), how is the file added by the plugin?

[CS01-HS 34]

16 hours ago, david_w said:

However, unraid overwrites the udev folder on boot. So this is not an option.

 

I don't know enough about the plugin to know if that's the best solution but you can overwrite the rules file on boot by saving your custom version on the flash drive (I created the directory /boot/extras/ for custom scripts) then adding something like the following to your /boot/config/go file:

 

# Custom autofan
cp /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/autofan /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/autofan.orig
cp /boot/extras/autofan /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/autofan

 

[SimonF 77]

17 hours ago, david_w said:

udev folder

The running files are not persistent.  Plugins get reloaded at boot so they can copy/create the file, as @CS01-HSsaid you can use the go file to make changes.

 

This is part of my plugin install which is just a bash script.

# move the rules file

cp /usr/local/emhttp/plugins/&name;/99_persistent_usb.rules /etc/udev/rules.d/

chmod 644 -R /etc/udev/rules.d/99_persistent_usb.rules 2>/dev/null



# reload udev rules

udevadm control --reload-rules

So create a udev rules file on you boot drive, in the go file copy to udev rules and then run udevadm to update with your rules. My location is from the plugin which gets restored at boot.

Edited Saturday at 01:49 PM by SimonF