Same ups, same problem.

Same ups, same problem.

Sometimes during these last updates, not sure exactly which one, load in watts is not displayed anymore, UPS is an APC Back-UPS Pro 900:

 

76% load and 0 watts sounds about right. Should be fixed now.

 

Thanks.

540    108 Watts    20%

 

1 hour ago, dmacias said:

Should be fixed now.

?

Updated to the latest. Nominal Power is empty and UPS Load is `-` with an Eaton 5E 650i.

Edited January 15, 20188 yr by realies

2 hours ago, realies said:

Updated to the latest. Nominal Power is empty and UPS Load is `-` with an Eaton 5E 650i.

I thought the nut commit for the eaton driver in your pull request computed an approximation of ups.realpower.nominal. Do you not get a ups.realpower.nominal variable? Upon further inspection I believe that was for higher end Eaton UPS.  The 0.80 powerfactor is also too high for your UPS. You'll have to use the manual option in the Display Settings and enter 650VA and 360W.

 

Edit: I saw your original nut repo issue. And I see he extrapolated the 0.80 from your Eaton companion readings. But 140W @ 27% on a 650VA/360W rated UPS doesn't seem right. That would add up to over 500W at 100%. Is there any way you could measure the actual watts used with a killawatt adapter or similar.

Edited January 15, 20188 yr by dmacias

Hey All

 

Just some info if any one knows why?

I have a Mecer ME-2000-VU 2000VA/1200W Line Interactive UPS

I upgraded to unRAID 6.4 from the version before and then when i rebooted NUT would not start.

Tried all sorts uninstalled reinstalled and nothing.

Then read a post here and set all to default and port to auto and manually ran the nut start.

Now working again.

I have made no changes to the config before the upgrade is there something I need to do to keep it from happening again

 

here are my settings

 

 

 

does nut have a conf file that I can backup if this happens again or should the autodetect just work as from my log file I was getting this before it started

 

Jan 19 08:01:49 Terok-Nor kernel: usb 2-1.2: USB disconnect, device number 19
Jan 19 08:01:51 Terok-Nor kernel: usb 2-1.2: new low-speed USB device number 20 using ehci-pci
Jan 19 08:01:51 Terok-Nor kernel: hid-generic 0003:0665:5161.1753: hiddev96,hidraw1: USB HID v1.00 Device [INNO TECH USB to Serial] on usb-0000:00:1d.0-1.2/input0
Jan 19 08:01:59 Terok-Nor ool www[28682]: /usr/local/emhttp/plugins/nut/scripts/start
Jan 19 08:02:01 Terok-Nor kernel: usb 2-1.2: USB disconnect, device number 20
Jan 19 08:02:02 Terok-Nor kernel: usb 2-1.2: new low-speed USB device number 21 using ehci-pci
Jan 19 08:02:03 Terok-Nor kernel: hid-generic 0003:0665:5161.1754: hiddev96,hidraw1: USB HID v1.00 Device [INNO TECH USB to Serial] on usb-0000:00:1d.0-1.2/input0
Jan 19 08:02:12 Terok-Nor kernel: usb 2-1.2: USB disconnect, device number 21
Jan 19 08:02:14 Terok-Nor kernel: usb 2-1.2: new low-speed USB device number 22 using ehci-pci
Jan 19 08:02:14 Terok-Nor kernel: hid-generic 0003:0665:5161.1755: hiddev96,hidraw1: USB HID v1.00 Device [INNO TECH USB to Serial] on usb-0000:00:1d.0-1.2/input0
Jan 19 08:02:23 Terok-Nor kernel: usb 2-1.2: USB disconnect, device number 22
Jan 19 08:02:25 Terok-Nor kernel: usb 2-1.2: new low-speed USB device number 23 using ehci-pci
Jan 19 08:02:25 Terok-Nor kernel: hid-generic 0003:0665:5161.1756: hiddev96,hidraw1: USB HID v1.00 Device [INNO TECH USB to Serial] on usb-0000:00:1d.0-1.2/input0

 

thanks for any words of wisdom ....

Hey All
 
Just some info if any one knows why?
I have a Mecer ME-2000-VU 2000VA/1200W Line Interactive UPS
I upgraded to unRAID 6.4 from the version before and then when i rebooted NUT would not start.
Tried all sorts uninstalled reinstalled and nothing.
Then read a post here and set all to default and port to auto and manually ran the nut start.
Now working again.
I have made no changes to the config before the upgrade is there something I need to do to keep it from happening again

 
here are my settings
 

 

 
does nut have a conf file that I can backup if this happens again or should the autodetect just work as from my log file I was getting this before it started
 
Jan 19 08:01:49 Terok-Nor kernel: usb 2-1.2: USB disconnect, device number 19
Jan 19 08:01:51 Terok-Nor kernel: usb 2-1.2: new low-speed USB device number 20 using ehci-pci
Jan 19 08:01:51 Terok-Nor kernel: hid-generic 0003:0665:5161.1753: hiddev96,hidraw1: USB HID v1.00 Device [iNNO TECH USB to Serial] on usb-0000:00:1d.0-1.2/input0
Jan 19 08:01:59 Terok-Nor ool www[28682]: /usr/local/emhttp/plugins/nut/scripts/start
Jan 19 08:02:01 Terok-Nor kernel: usb 2-1.2: USB disconnect, device number 20
Jan 19 08:02:02 Terok-Nor kernel: usb 2-1.2: new low-speed USB device number 21 using ehci-pci
Jan 19 08:02:03 Terok-Nor kernel: hid-generic 0003:0665:5161.1754: hiddev96,hidraw1: USB HID v1.00 Device [iNNO TECH USB to Serial] on usb-0000:00:1d.0-1.2/input0
Jan 19 08:02:12 Terok-Nor kernel: usb 2-1.2: USB disconnect, device number 21
Jan 19 08:02:14 Terok-Nor kernel: usb 2-1.2: new low-speed USB device number 22 using ehci-pci
Jan 19 08:02:14 Terok-Nor kernel: hid-generic 0003:0665:5161.1755: hiddev96,hidraw1: USB HID v1.00 Device [iNNO TECH USB to Serial] on usb-0000:00:1d.0-1.2/input0
Jan 19 08:02:23 Terok-Nor kernel: usb 2-1.2: USB disconnect, device number 22
Jan 19 08:02:25 Terok-Nor kernel: usb 2-1.2: new low-speed USB device number 23 using ehci-pci
Jan 19 08:02:25 Terok-Nor kernel: hid-generic 0003:0665:5161.1756: hiddev96,hidraw1: USB HID v1.00 Device [iNNO TECH USB to Serial] on usb-0000:00:1d.0-1.2/input0
 
thanks for any words of wisdom ....

Unless using complete manual mode the conf files are overwritten using info from /boot/config/plugins/nut/nut.cfg. To me it looks like there was something wrong with your nut.cfg, possibly edited with notepad or another editor that isn't compatible with Linux. I'm not sure why moving to 6.4 broke it though. The disconnects are kernel related and I get them to, even on a fresh reboot with no nut. I even had to disable usb3/xhci in the bios. But they should stop after the nut driver connects. You can also set the display settings at the bottom to manual and enter in your UPS values to get an estimation of power used.

I just got a replacement UPS as my previous one just died when the power went out. With this new one I can't get NUT to start.

 

Both the new and the old are a PowerWalker BlueWalker VI 2200 SH.

 

Unraid detects it when I plug it in:

Feb 1 22:09:18 UnRaid kernel: hid-generic 0003:06DA:FFFF.0001: hiddev0,hidraw0: USB HID v1.00 Device [PPC Offline UPS] on usb-0000:05:00.0-1/input0

 

The driver is set to Blazer_usb and the port to auto. This worked fine with the old one.

 

If I try to start it from SSH this is what happens:

root@UnRaid:/# /etc/rc.d/rc.nut start
Writing nut config
Updating permissions...
Network UPS Tools - UPS driver controller 2.7.4.1
Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4.1)
No supported devices found. Please check your device availability with 'lsusb'
and make sure you have an up-to-date version of NUT. If this does not help,
try running the driver with at least 'subdriver', 'vendorid' and 'productid'
options specified. Please refer to the man page for details about these options
(man 8 blazer_usb).

Driver failed to start (exit status=1)

 

But if I try to stop it (even when it's not running) this happens:

 

root@UnRaid:/# /etc/rc.d/rc.nut stop
Writing nut config
Updating permissions...
Stopping the UPS services...
Network UPS Tools - UPS driver controller 2.7.4.1
Can't open /var/run/nut/blazer_usb-auto.pid: No such file or directory

 

I've tried to switch around the drivers and every time it can't find the .pid file under /var/run/nut/.

 

I've tried to reinstall the plugin without any luck as well.

Ok what the hell...

 

Just for the hell of it I tried to start the APC UPS Daemon that comes with Unraid and it detects my UPS

 

Now I'm even more confused. These PowerWalkers has never worked with apcupsd...

But if I try to stop it (even when it's not running) this happens:
 

root@UnRaid:/# /etc/rc.d/rc.nut stopWriting nut configUpdating permissions...Stopping the UPS services...Network UPS Tools - UPS driver controller 2.7.4.1Can't open /var/run/nut/blazer_usb-auto.pid: No such file or directory

 
I've tried to switch around the drivers and every time it can't find the .pid file under /var/run/nut/.
 
I've tried to reinstall the plugin without any luck as well.

Not sure why it wouldn't work on the new UPS. The can't find pid is normal since you couldn't get it running.

hi guys, need you help!

I recently bought cheap UPS Cyberpower EX850E usb,

I connected it, unraid detected it using APCUPSD and using NUT, everything is fine except one thing

I can not make him turn off after server shutdown, so I want when power is applied again the server is turned on

Bios settings after power loss set to "always on"

here is Nut output: (upsc ups@localhost)

battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
battery.runtime: 1241
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 13.8
battery.voltage.nominal: 12
device.mfr: CPS
device.model: EX850E
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4.1
driver.version.data: CyberPower HID 0.5
driver.version.internal: 0.42
input.transfer.high: 0
input.transfer.low: 0
input.voltage: 224.0
input.voltage.nominal: 230
output.voltage: 223.0
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 23
ups.mfr: CPS
ups.model: EX850E
ups.productid: 0501
ups.realpower.nominal: 490
ups.status: OL
ups.test.result: No test initiated
ups.timer.shutdown: -60
ups.timer.start: -60
ups.vendorid: 0764

Instant commands supported on UPS (upscmd -l)

beeper.disable - Disable the UPS beeper
beeper.enable - Enable the UPS beeper
beeper.mute - Temporarily mute the UPS beeper
beeper.off - Obsolete (use beeper.disable or beeper.mute)
beeper.on - Obsolete (use beeper.enable)
load.off - Turn off the load immediately
load.off.delay - Turn off the load with a delay (seconds)
load.on - Turn on the load immediately
load.on.delay - Turn on the load with a delay (seconds)
shutdown.return - Turn off the load and return when power is back
shutdown.stayoff - Turn off the load and remain off
shutdown.stop - Stop a shutdown in progress
test.battery.start.deep - Start a deep battery test
test.battery.start.quick - Start a quick battery test
test.battery.stop - Stop the battery test

upsrw ups
[battery.charge.low]
Remaining battery level when UPS switches to LB (percent)
Type: STRING
Maximum length: 10
Value: 10

[battery.runtime.low]
Remaining battery runtime when UPS switches to LB (seconds)
Type: STRING
Maximum length: 10
Value: 300

[input.transfer.high]
High voltage transfer point (V)
Type: STRING
Maximum length: 10
Value: 0

[input.transfer.low]
Low voltage transfer point (V)
Type: STRING
Maximum length: 10
Value: 0

[ups.delay.shutdown]
Interval to wait after shutdown with delay command (seconds)
Type: STRING
Maximum length: 10
Value: 20

[ups.delay.start]
Interval to wait before (re)starting the load (seconds)
Type: STRING
Maximum length: 10
Value: 30

please help =)

 

UPD: my friend use such UPS whith synology nas, that use NUT, and everything works perfect. Power cut > shutdown > ups-off, and when power retained it starts

Edited March 16, 20188 yr by vanes

I cant get "Turn off UPS after shutdown" to work as it should!

Its my first UPS, guys, point out the direction to move please =))

Does your friend's UPS parameter also -60 ? ( not sure relate to this problem or not )

As I remember some member also report same issue for Cyberpower UPS

 

ups.timer.shutdown: -60
ups.timer.start: -60

 

I use APC and running in Network slave mode. I haven't enable shutdown UPS feature, below is my output

 

ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.timer.start: -1
 

 

Edited March 16, 20188 yr by Benson

This is friends output

/volume1/homes/***$ upsc ups
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
battery.runtime: 908
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 9.2
battery.voltage.nominal: 12
device.mfr: CPS
device.model: EX650E
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 5
driver.parameter.port: auto
driver.version: DSM6-1-15205-171017-1-gf424baa
driver.version.data: CyberPower HID 0.3
driver.version.internal: 0.38
input.transfer.high: 0
input.transfer.low: 0
input.voltage: 218.0
input.voltage.nominal: 230
output.voltage: 217.0
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 31
ups.mfr: CPS
ups.model: EX650E
ups.productid: 0501
ups.realpower.nominal: 360
ups.status: OL
ups.test.result: No test initiated
ups.timer.shutdown: -60
ups.timer.start: -60
ups.vendorid: 0764

i tried:

 upsmon -c fsd  (from here http://networkupstools.org/docs/man/usbhid-ups.html)

 upsrw shutdown.stayoff ups

tried APCPSD test (apctest  kilpower test)

No reaction.....

Edited March 16, 20188 yr by vanes

So, no idea. Seems unRAID missing poweroff Cyberpower UPS feature.

 

Your friend's UPS battery should be abnormal, only 9.2v but charge 100%.

Edited March 16, 20188 yr by Benson

i see that unraid drivers and nut are newer than syno. can i test older drivers somehow?

i see that unraid drivers and nut are newer than syno. can i test older drivers somehow?

I may be able to point you to some older version. I'll have to check if it's compatible with the plugin now

@dmacias i tested v1 plugin! v1 works, but not as v2 

after power loss UPS begins shutdown of server and after 20-30 sec  turns off itself (not completed shutdown), then after 20-30 sec. turns on himself regardless of the power plug...

 

Edited March 19, 20188 yr by vanes

v1 info

root@unRaid:~# upsc ups
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
battery.runtime: 1191
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 13.8
battery.voltage.nominal: 12
device.mfr: CPS
device.model: EX850E
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.3
driver.version.data: CyberPower HID 0.4
driver.version.internal: 0.39
input.transfer.high: 0
input.transfer.low: 0
input.voltage: 227.0
input.voltage.nominal: 230
output.voltage: 225.0
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 24
ups.mfr: CPS
ups.model: EX850E
ups.productid: 0501
ups.realpower.nominal: 490
ups.status: OL
ups.test.result: No test initiated
ups.timer.shutdown: -60
ups.timer.start: -60
ups.vendorid: 0764

 

root@unRaid:~# upscmd -l ups
Instant commands supported on UPS [ups]:

beeper.disable - Disable the UPS beeper
beeper.enable - Enable the UPS beeper
beeper.mute - Temporarily mute the UPS beeper
beeper.off - Obsolete (use beeper.disable or beeper.mute)
beeper.on - Obsolete (use beeper.enable)
load.off - Turn off the load immediately
load.off.delay - Turn off the load with a delay (seconds)
load.on - Turn on the load immediately
load.on.delay - Turn on the load with a delay (seconds)
shutdown.return - Turn off the load and return when power is back
shutdown.stayoff - Turn off the load and remain off
shutdown.stop - Stop a shutdown in progress
test.battery.start.deep - Start a deep battery test
test.battery.start.quick - Start a quick battery test
test.battery.stop - Stop the battery test

 

root@unRaid:~# upsrw ups
[battery.charge.low]
Remaining battery level when UPS switches to LB (percent)
Type: STRING
Maximum length: 10
Value: 10

[battery.runtime.low]
Remaining battery runtime when UPS switches to LB (seconds)
Type: STRING
Maximum length: 10
Value: 300

[input.transfer.high]
High voltage transfer point (V)
Type: STRING
Maximum length: 10
Value: 0

[input.transfer.low]
Low voltage transfer point (V)
Type: STRING
Maximum length: 10
Value: 0

[ups.delay.shutdown]
Interval to wait after shutdown with delay command (seconds)
Type: STRING
Maximum length: 10
Value: 20

[ups.delay.start]
Interval to wait before (re)starting the load (seconds)
Type: STRING
Maximum length: 10
Value: 30

 

Edited March 19, 20188 yr by vanes

[mention=11874]dmacias[/mention] i tested v1 plugin! v1 works, but not as v2 
after power loss UPS begins shutdown of server and after 20-30 sec  turns off itself (not completed shutdown), then after 20-30 sec. turns on himself regardless of the power plug...
 

Here's the previous driver.https://github.com/dmacias72/NUT-unRAID/raw/master/packages/nut-2.7.4-x86_64-2_slonly.txz
Try installing v2 plugin. Make sure it's stopped. Then install this nut version. Then try it out.

Also what settings are you using to shutdown (your Nut settings from the settings page)? What method are you using to shutdown? Battery level, runtime left or Time on Battery?

3 minutes ago, dmacias said:

Also what settings are you using to shutdown (your Nut settings from the settings page)? What method are you using to shutdown? Battery level, runtime left or Time on Battery?

i use Time on Battery method.

 

4 minutes ago, dmacias said:

Then install this nut version. Then try it out.

I do not know how to install this file =)) I'm new to Linux =)) I ask, if not difficult, to write a short algorithm step by step

Thanks

I do not know how to install this file =)) I'm new to Linux =)) I ask, if not difficult, to write a short algorithm step by step
Thanks

If you put it in the root of your flash drive then run upgradepkg /boot/nut-2.7.4-x86_64-2_slonly.txz from the command line

Sorry guys, cant test this anymore! I changed UPS to APC back ups 700 and everething is perfect now! I think anybody alse can test it...

Hey guys, 

 

I think i found an issue with the rc script.

 

If you have cups installed and running, the pgrep in start_upsd (in /etc/rc.d/rc.nut) will get a hit for cupsd and not start upsd.    pgrep -x should probably work for this case

 

Thanks!