[Plugin] NUT v2 - Network UPS Tools


dmacias

Recommended Posts

Well, I've added the values for a 650va to the config file, reloaded NUT and it hasnt made any difference at all. 

 

Interestingly if I change the driver to  nutdrv.qx or nutdrv_atcl_usb it just shows the blazer driver.  The config will also not acept/update the input voltage parameters.

 

ups2.PNG.d0ac88d38d2a7f8aca89f1ee893da5dc.PNG

 

ups3.thumb.PNG.be810365a3ed123aae9cda749d6d891a.PNG

 

I have tried removing 'default' from the values but that doesnt do anything either.

Edited by MendipMan
Link to comment

Sorry, I should of said I have already put the new driver in.  Thank you very much btw @IGHOR

 

As you can see from the pics I have manual config enabled and It shows that the UPS is online and Load% is in green.

 

I just wanted to get the battery charge status working.  Oh well its not the end of the world as the UPS works and I only want it for immediate safe shutdown anyway.

Link to comment
  • 3 weeks later...

I recently swapped over from my trusty but now dead APC 650cs to an APC MODEL Back-UPS BX750MI.  NET detects it fine and starts monitoring.  After a few hours (twice in 24 hours), it disconnects with the following error:

 

Nov 22 03:41:15 tdm usbhid-ups[18835]: nut_libusb_get_report: Input/Output Error.
Nov 22 03:41:17 tdm usbhid-ups[18835]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Nov 22 03:41:17 tdm upsd[18990]: Data for UPS [ups] is stale - check driver
Nov 22 03:41:18 tdm upsmon[18994]: Poll UPS [ups@127.0.0.1] failed - Data stale
Nov 22 03:41:18 tdm upsmon[18994]: Communications with UPS ups@127.0.0.1 lost
Nov 22 03:41:19 tdm usbhid-ups[18835]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Nov 22 03:41:21 tdm usbhid-ups[18835]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Nov 22 03:41:23 tdm usbhid-ups[18835]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround

 

Repeating every second or so and spamming the syslog.  I pull out the USB cable and replug it in, and all works fine:

 

Nov 22 06:04:04 tdm kernel: usb 1-8: USB disconnect, device number 5
Nov 22 06:04:08 tdm upsmon[18994]: Poll UPS [ups@127.0.0.1] failed - Data stale
Nov 22 06:04:13 tdm upsmon[18994]: Poll UPS [ups@127.0.0.1] failed - Data stale
Nov 22 06:04:16 tdm kernel: usb 1-8: new full-speed USB device number 6 using xhci_hcd
Nov 22 06:04:16 tdm kernel: hid-generic 0003:051D:0002.0006: hiddev98,hidraw3: USB HID v1.10 Device [American Power Conversion Back-UPS BX750MI  FW:295201G -302201G ] on usb-0000:00:14.0-8/input0
Nov 22 06:04:17 tdm upsd[18990]: UPS [ups] data is no longer stale
Nov 22 06:04:18 tdm upsmon[18994]: Communications with UPS ups@127.0.0.1 established

 

Until it crashes again.

 

I moved over to the Unraid default UPS setting instead of NUT and it's now been solid without any disconnection.  While I don't *need* the Network feature, it was handy to have.  And I enjoyed the UPS status in the status bar.

 

Any ideas of what could be the issue, or what I can do to resolve it?  here's the UPS Details page for the UPS Settings tab

 

image.thumb.png.3a7b34266dd6a6e909c8ee2f73404a1e.png

Link to comment
  • 1 month later...
On 10/5/2021 at 12:31 AM, Acps said:

Swapped out and older apc for a new CyberPower CP1000PFCLCD, however i keep getting this error in the syslog:

 

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

I tried moving the cable to several different usb ports and it was the same thing,  do i have a cable or ups issue going on?

unraid-syslog-20211005-0126.zip 54.36 kB · 0 downloads

I have a CyberPower CP1500PFCLCD, very similar to yours, with the same issue. Log fills up with;

 

Dec 23 12:38:43 tmedia usbhid-ups[4122]: nut_libusb_get_report: Input/Output Error.

Dec 23 12:40:53 tmedia usbhid-ups[4122]: nut_libusb_get_report: Input/Output Error.

Dec 23 12:42:17 tmedia usbhid-ups[4122]: nut_libusb_get_report: Input/Output Error.

Dec 23 12:43:35 tmedia usbhid-ups[4122]: nut_libusb_get_report: Input/Output Error.      etc etc. 

Have you figured out how to stop it?

Link to comment
  • 2 weeks later...
I have a CyberPower CP1500PFCLCD, very similar to yours, with the same issue. Log fills up with;
 
Dec 23 12:38:43 tmedia usbhid-ups[4122]: nut_libusb_get_report: Input/Output Error.
Dec 23 12:40:53 tmedia usbhid-ups[4122]: nut_libusb_get_report: Input/Output Error.
Dec 23 12:42:17 tmedia usbhid-ups[4122]: nut_libusb_get_report: Input/Output Error.
Dec 23 12:43:35 tmedia usbhid-ups[4122]: nut_libusb_get_report: Input/Output Error.      etc etc. 

Have you figured out how to stop it?

Hey there, I did not find anything that helped. Other than filling up the system log though, I don't think it has any impact on the ups being able to do its job because it's still able to communicate with the ups and the gui shows it reporting the battery level, load and runtime left. I guess if you really wanted to be cautious you could disconnect most of your drives in your Nas and just boot unraid from the usb and unplug the ups from the wall and monitor the gui to see if it functions correctly and iniates shutdown at the proper % you have set.

Other than filling up the system log which is rather annoying, it's might be easier to keep it from reporting the errors to begin with, but isn't something that I have looked at yet. Which may or may not be a good idea!


-Acps


Sent from my iPhone using Tapatalk
Link to comment
9 hours ago, Acps said:

I guess if you really wanted to be cautious you could disconnect most of your drives in your Nas

No need to at all!

Just connect the Unraid power cord to the wall directly instead of the UPS.

Then plug in the USB into the UPS and initiate a UPS shutdown for example by yanking the UPS power cord.

Everything will behave as if the unraid computer is plugged into the UPS and unraid will still shutdown if all goes ok, besides that IF something goes wrong like UPS battery gets too low unraid still has power and will not shutoff from low battery.

Link to comment

hi guys, thank you very much for this plugin... i have installed it, and use it with my "GreenCell 600VA" UPS, it uses driver "blazer_usb"... i've got it mostly work...only thing that is still not working correctly is "ups load"... it is almost always on 10% (36watt), sometimes goes to 40 or 50 % but my server is behind shelly plug, and i am monitoring energy usage there... and it is around 88 watt (and this is more logic than 36watt for i7 with 5 HDD's etc...)... can i somewhere make correction for this ups load ? (because of this "runtime left" is also not correct of course)..

 

Hope to get some info about this...i am looking hours and hours for some option about this trough forum here and google...couldn't find anything.

 

Thank you in advance.

 

best regards,

 

Miki

Link to comment

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

 

nut 1.png

nut 2.png

Edited by julzilla
wrong model
Link to comment

I'm getting lots of this message in my syslog

    upsmon[24182]: UPS xs1200@127.0.0.1 battery is low

It seems to be at random intervals. I've run it as a standalone and netserver, the errors persist. Here are some grabs of the settings for both the built-in UPS settings and the NUT plugin.
image.thumb.png.6a9b5003d73999617bf51a755b778e66.png

image.thumb.png.6c90e411648711ad288ea67a42c7cb26.png

image.thumb.png.91c8295ef4ba4fe012f5a31f270a3862.png

 

My questions are these;

   Is this something others have seen? I couldn't find anything in the topic...

   How specifically can I really ramp up logging to debug this?
 

My next step is going to be to disable NUT and try the built-in UPS monitor and see if the errors turn up. I want to get NUT to work correctly so that I can shutdown other computers on my UPS when the power goes out.

 

Thanks in advance for the help!

 

Link to comment

Have you considered the battery might be shot?  They typically are good for 3-5 years and yours is almost 10 years old... And quality UPS's (ie: yours) will do a battery test every once in a while to alert you of this kind of stuff.

Link to comment
1 hour ago, blender50 said:

I want to get NUT to work correctly so that I can shutdown other computers on my UPS when the power goes out.

The built in tool (apcupsd) performs that function perfectly fine. I've been using it that way for years.

 

The server is the master, and when the power goes out for more than 3 minutes all the VM's and physical workstations shut down, followed by the server a few minutes later.

Link to comment
11 hours ago, medolino2009 said:

hi, anyone recognize problem i have ? (couple of posts up)...

 

Thanx in advance....

It is quite normal for large reading different between power factor aware SMART plug VS UPS, btw UPS usually dealing with VA rather then Watts, so you can't estimate the battery runtime by Watts, only electricity cost would apply by Watts.

Edited by Vr2Io
Link to comment
On 1/7/2022 at 11:38 AM, Vr2Io said:

It is quite normal for large reading different between power factor aware SMART plug VS UPS, btw UPS usually dealing with VA rather then Watts, so you can't estimate the battery runtime by Watts, only electricity cost would apply by Watts.

Hi, thank you for response, however, i don't think i explained good so you could understand what i mean...

If you look at photo up here in post of user "Blender50", you can see "UPS Load" is around 359watt, or UPS load around 46% (in percentage)... This is how it need to be ...in my case UPS load is 36watt (around 10%)... this is not correct... it should be around 90 watt (around 25% - 30%)... If this was correct, "Runtime Left" could be calculated better...

 

If i could change something to make wattage display correct, everything else would be correct as well.

 

Thanx in advace

 

Best regards

 

Miki

Link to comment

This is a follow-up to my post from last Thursday. I switched back to the built-in UPS plugin and the errors no longer show up in my syslog. So, that's the good news. 

As luck would have it we had a couple of power outages in the last couple of days, each long enough to get the ups to power down my server. Everything went fine but I had to manually power off my workstation since it is no longer monitoring the unRAID box.

 

This leaves me with either figuring out how to set up the built-in UPS plug so that it acts as a netserver or going back to the NUT plugin and tweaking the config to eliminate the bogus 'battery is low' messages. I have no reason to make NUT to work if the 'stock' plugin can be made to work. JonathanM, can you provide any further details on how to have the UPS plugin act as a master?

 

Squid, I see you mentioned I may have old batteries, but they were replaced a couple of years ago and I don't think the data is accurate. During the two powerboats this past weekend the UPS worked exactly as expected (thank goodness). 

 

Thanks again to all who have chimed in on this, I really appreciate the help.

 

Link to comment
  • 4 weeks later...
On 11/4/2021 at 3:31 PM, Jammy B said:

Have you updated NUT, go back. A couple pages in this thread. The legend recompiled nut with the driver you need. 
 

you also need to enable at the top to use custom config to make the text edited ups.conf work 

 

I made a thread on it as well. 

Hi did you get runtime working with changes to config? I have a Powercool 2000

 

image.thumb.png.9ceb3fb1e38e50578c684a4b59cab9e4.png

 

Have not added any manual config as yet.

 

image.thumb.png.47a6fef951fb2fdd93be6b5975275b28.png

Link to comment

Lost UPS after running for a while, NUT plugin shows running, but no UPS device shows
After re-plugging and unplugging the USB, restart the NUT plugin and enable it normally

Quote
Scanning for UPS...

[nutdev1]
driver = "usbhid-ups"
port = "auto"
vendorid = "051D"
productid = "0002"
product = "BK650M2-CH"
serial = "9B2019A13037"
vendor = "American Power Conversion"
bus = "001"

 

Feb 1 11:03:10 Tower upsmon[14759]: Poll UPS [ups@127.0.0.1] failed - Data stale
Feb 1 11:03:11 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:13 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:15 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:15 Tower upsmon[14759]: Poll UPS [ups@127.0.0.1] failed - Data stale
Feb 1 11:03:17 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:19 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:20 Tower upsmon[14759]: Poll UPS [ups@127.0.0.1] failed - Data stale
Feb 1 11:03:21 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:23 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:25 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:25 Tower upsmon[14759]: Poll UPS [ups@127.0.0.1] failed - Data stale
Feb 1 11:03:27 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:29 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:30 Tower upsmon[14759]: Poll UPS [ups@127.0.0.1] failed - Data stale
Feb 1 11:03:31 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:33 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:35 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:35 Tower upsmon[14759]: Poll UPS [ups@127.0.0.1] failed - Data stale
Feb 1 11:03:37 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:39 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:40 Tower upsmon[14759]: Poll UPS [ups@127.0.0.1] failed - Data stale
Feb 1 11:03:41 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:43 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:45 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:45 Tower upsmon[14759]: Poll UPS [ups@127.0.0.1] failed - Data stale
Feb 1 11:03:47 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:49 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:50 Tower upsmon[14759]: Poll UPS [ups@127.0.0.1] failed - Data stale
Feb 1 11:03:51 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:53 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:55 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:55 Tower upsmon[14759]: Poll UPS [ups@127.0.0.1] failed - Data stale
Feb 1 11:03:57 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround

 

Link to comment

Hi!

 

I'am using Eaton Ellipse PRO 1200 DIN along with NUT but for me it seems like the readed consume Watt is not calculated in the right way for the page footer.

 

I've set it to Manual (because Auto were more terrible values) with this settings:
 

UPS Output Volt Amp Capacity (VA): 1200

UPS Output Watt Capacity (Watts): 750

Showing at the bottom a consumption of: 135W

 

This value is not the value what the UPS is showing on Screen (95W) and double checked with power plug confirms the assumption.

 

I can see the ups.realpower = 95 which seems to me the right value but why is this value not displayed in the footer?

 

driver.version.dataMGE = HID 1.43

driver.version.internal = 0.55

driver.version.usb = libusb-1.0.23 (API: 0x1000107)

 

Have I set up something wrong or is that a bug within NUT?

 

Thanks

Link to comment
3 hours ago, Skylinar said:

Hi!

 

I'am using Eaton Ellipse PRO 1200 DIN along with NUT but for me it seems like the readed consume Watt is not calculated in the right way for the page footer.

 

I've set it to Manual (because Auto were more terrible values) with this settings:
 

UPS Output Volt Amp Capacity (VA): 1200

UPS Output Watt Capacity (Watts): 750

Showing at the bottom a consumption of: 135W

 

This value is not the value what the UPS is showing on Screen (95W) and double checked with power plug confirms the assumption.

 

I can see the ups.realpower = 95 which seems to me the right value but why is this value not displayed in the footer?

 

driver.version.dataMGE = HID 1.43

driver.version.internal = 0.55

driver.version.usb = libusb-1.0.23 (API: 0x1000107)

 

Have I set up something wrong or is that a bug within NUT?

 

Thanks

What value shows on the status in the nut settings.

 

If you change the power load value to Auto does it show 95?

 

image.thumb.png.37a986158b63ef4ecce8054d4fbd83fd.png

Edited by SimonF
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.