Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Plugin] NUT v2 - Network UPS Tools

Featured Replies

Need help

some one uses a UPS from EuroTech?

EuroTech UPS2000VA

 

[nutdev1]
driver = "nutdrv_qx"
port = "auto"
vendorid = "0001"
productid = "0000"
bus = "001"

 

May  4 15:19:59 PCPAI-HOME ool www[28452]: /usr/local/emhttp/plugins/nut-dw/scripts/start
May  4 15:20:00 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:20:02 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:20:02 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:20:02 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:20:09 PCPAI-HOME rc.nut: Device not supported!
May  4 15:20:09 PCPAI-HOME rc.nut: Device not supported!
May  4 15:20:09 PCPAI-HOME rc.nut: Network UPS Tools - Generic Q* USB/Serial driver 0.39 (2.7.4.1)
May  4 15:20:09 PCPAI-HOME rc.nut: USB communication driver 0.43
May  4 15:20:09 PCPAI-HOME rc.nut: Driver failed to start (exit status=1)
May  4 15:20:09 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1


May  4 15:28:54 PCPAI-HOME ool www[56806]: /usr/local/emhttp/plugins/nut-dw/scripts/stop
May  4 15:28:55 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:28:57 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:28:57 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:28:57 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:28:58 PCPAI-HOME rc.nut: Stopping the NUT services... 
May  4 15:29:00 PCPAI-HOME rc.nut: Can't open /var/run/nut/blazer_ser-ups.pid: No such file or directory
May  4 15:29:00 PCPAI-HOME rc.nut: Can't open /var/run/nut/blazer_ser-auto.pid either: No such file or directory
May  4 15:29:00 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:29:06 PCPAI-HOME ool www[57804]: /usr/local/emhttp/plugins/nut-dw/scripts/start
May  4 15:29:07 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:29:09 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:29:09 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:29:09 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:29:10 PCPAI-HOME rc.nut: Network UPS Tools - Megatec/Q1 protocol serial driver 1.58 (2.7.4.1)
May  4 15:29:10 PCPAI-HOME rc.nut: 
May  4 15:29:10 PCPAI-HOME rc.nut: Fatal error: 'vendorid' is not a valid variable name for this driver.
May  4 15:29:10 PCPAI-HOME rc.nut: 
May  4 15:29:10 PCPAI-HOME rc.nut: Look in the man page or call this driver with -h for a list of
May  4 15:29:10 PCPAI-HOME rc.nut: valid variable names and flags.
May  4 15:29:10 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:29:11 PCPAI-HOME rc.nut: fopen /var/run/nut/upsd.pid: No such file or directory
May  4 15:29:11 PCPAI-HOME rc.nut: listening on 0.0.0.0 port 3493
May  4 15:29:11 PCPAI-HOME upsd[58162]: listening on 0.0.0.0 port 3493
May  4 15:29:11 PCPAI-HOME upsd[58162]: Can't connect to UPS [ups] (blazer_ser-ups): No such file or directory
May  4 15:29:11 PCPAI-HOME rc.nut: Can't connect to UPS [ups] (blazer_ser-ups): No such file or directory
May  4 15:29:11 PCPAI-HOME upsd[58163]: Startup successful
May  4 15:29:12 PCPAI-HOME rc.nut: fopen /var/run/nut/upsmon.pid: No such file or directory
May  4 15:29:12 PCPAI-HOME rc.nut: UPS: [email protected] (master) (power value 1)
May  4 15:29:12 PCPAI-HOME rc.nut: Using power down flag file /etc/nut/no_killpower
May  4 15:29:12 PCPAI-HOME upsmon[58166]: Startup successful
May  4 15:29:12 PCPAI-HOME upsmon[58166]: Warning: running as one big root process by request (upsmon -p)
May  4 15:29:12 PCPAI-HOME upsd[58163]: User [email protected] logged into UPS [ups]
May  4 15:29:12 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:12 PCPAI-HOME upsmon[58166]: Communications with UPS [email protected] lost
May  4 15:29:17 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:17 PCPAI-HOME upsmon[58166]: UPS [email protected] is unavailable
May  4 15:29:22 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:27 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:32 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:37 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:42 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:47 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:52 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:57 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:30:02 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:30:07 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:30:07 PCPAI-HOME ool www[57807]: /usr/local/emhttp/plugins/nut-dw/scripts/restart
May  4 15:30:07 PCPAI-HOME rc.nut: Stopping the NUT services... 
May  4 15:30:07 PCPAI-HOME upsmon[58166]: Signal 15: exiting
May  4 15:30:07 PCPAI-HOME rc.nut: Network UPS Tools upsmon 2.7.4.1
May  4 15:30:07 PCPAI-HOME upsd[58163]: User [email protected] logged out from UPS [ups]
May  4 15:30:07 PCPAI-HOME upsd[58163]: mainloop: Interrupted system call
May  4 15:30:07 PCPAI-HOME upsd[58163]: Signal 15: exiting
May  4 15:30:07 PCPAI-HOME rc.nut: Network UPS Tools upsd 2.7.4.1
May  4 15:30:09 PCPAI-HOME rc.nut: Can't open /var/run/nut/blazer_ser-ups.pid: No such file or directory
May  4 15:30:09 PCPAI-HOME rc.nut: Can't open /var/run/nut/blazer_ser-auto.pid either: No such file or directory
May  4 15:30:09 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:30:13 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:30:16 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:30:16 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:30:16 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:30:17 PCPAI-HOME rc.nut: Fatal error: unusable configuration
May  4 15:30:17 PCPAI-HOME rc.nut: Network UPS Tools - Megatec/Q1 protocol serial driver 1.58 (2.7.4.1)
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut: Unable to open auto: No such file or directory
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut: Things to try:
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut:  - Check 'port=' in ups.conf
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut:  - Check owner/permissions of all parts of path
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut: Driver failed to start (exit status=1)
May  4 15:30:17 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:31:59 PCPAI-HOME ool www[63635]: /usr/local/emhttp/plugins/nut-dw/scripts/start
May  4 15:32:00 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:32:02 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:32:02 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:32:02 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:32:05 PCPAI-HOME rc.nut: No supported UPS detected
May  4 15:32:05 PCPAI-HOME rc.nut: Network UPS Tools - Megatec/Q1 protocol USB driver 0.20 (2.7.4.1)
May  4 15:32:05 PCPAI-HOME rc.nut: Driver failed to start (exit status=1)
May  4 15:32:05 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:32:12 PCPAI-HOME ool www[64160]: /usr/local/emhttp/plugins/nut-dw/scripts/start
May  4 15:32:13 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:32:15 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:32:15 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:32:15 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:32:18 PCPAI-HOME rc.nut: No supported UPS detected
May  4 15:32:18 PCPAI-HOME rc.nut: Network UPS Tools - Megatec/Q1 protocol USB driver 0.20 (2.7.4.1)
May  4 15:32:18 PCPAI-HOME rc.nut: Driver failed to start (exit status=1)
May  4 15:32:18 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1

dont know what to do

tried on legacy and 2.8.2

  • Replies 2.1k
  • Views 457.5k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • I am stopping updates for my version of the plugin. Update to the latest version 2023.09.17 and then you can remove my version and install Rysz's from CA and it will retain your configs.   T

  • Released 2023.07.26, @ich777 is creating a new package for me to use, and I want to look to move to 2.8 as the default version but will need to check upgrade path works ok.

  • 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:

Posted Images

19 hours ago, pcpai said:

Need help

some one uses a UPS from EuroTech?

EuroTech UPS2000VA

 

[nutdev1]
driver = "nutdrv_qx"
port = "auto"
vendorid = "0001"
productid = "0000"
bus = "001"

 

May  4 15:19:59 PCPAI-HOME ool www[28452]: /usr/local/emhttp/plugins/nut-dw/scripts/start
May  4 15:20:00 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:20:02 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:20:02 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:20:02 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:20:09 PCPAI-HOME rc.nut: Device not supported!
May  4 15:20:09 PCPAI-HOME rc.nut: Device not supported!
May  4 15:20:09 PCPAI-HOME rc.nut: Network UPS Tools - Generic Q* USB/Serial driver 0.39 (2.7.4.1)
May  4 15:20:09 PCPAI-HOME rc.nut: USB communication driver 0.43
May  4 15:20:09 PCPAI-HOME rc.nut: Driver failed to start (exit status=1)
May  4 15:20:09 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1


May  4 15:28:54 PCPAI-HOME ool www[56806]: /usr/local/emhttp/plugins/nut-dw/scripts/stop
May  4 15:28:55 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:28:57 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:28:57 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:28:57 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:28:58 PCPAI-HOME rc.nut: Stopping the NUT services... 
May  4 15:29:00 PCPAI-HOME rc.nut: Can't open /var/run/nut/blazer_ser-ups.pid: No such file or directory
May  4 15:29:00 PCPAI-HOME rc.nut: Can't open /var/run/nut/blazer_ser-auto.pid either: No such file or directory
May  4 15:29:00 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:29:06 PCPAI-HOME ool www[57804]: /usr/local/emhttp/plugins/nut-dw/scripts/start
May  4 15:29:07 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:29:09 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:29:09 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:29:09 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:29:10 PCPAI-HOME rc.nut: Network UPS Tools - Megatec/Q1 protocol serial driver 1.58 (2.7.4.1)
May  4 15:29:10 PCPAI-HOME rc.nut: 
May  4 15:29:10 PCPAI-HOME rc.nut: Fatal error: 'vendorid' is not a valid variable name for this driver.
May  4 15:29:10 PCPAI-HOME rc.nut: 
May  4 15:29:10 PCPAI-HOME rc.nut: Look in the man page or call this driver with -h for a list of
May  4 15:29:10 PCPAI-HOME rc.nut: valid variable names and flags.
May  4 15:29:10 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:29:11 PCPAI-HOME rc.nut: fopen /var/run/nut/upsd.pid: No such file or directory
May  4 15:29:11 PCPAI-HOME rc.nut: listening on 0.0.0.0 port 3493
May  4 15:29:11 PCPAI-HOME upsd[58162]: listening on 0.0.0.0 port 3493
May  4 15:29:11 PCPAI-HOME upsd[58162]: Can't connect to UPS [ups] (blazer_ser-ups): No such file or directory
May  4 15:29:11 PCPAI-HOME rc.nut: Can't connect to UPS [ups] (blazer_ser-ups): No such file or directory
May  4 15:29:11 PCPAI-HOME upsd[58163]: Startup successful
May  4 15:29:12 PCPAI-HOME rc.nut: fopen /var/run/nut/upsmon.pid: No such file or directory
May  4 15:29:12 PCPAI-HOME rc.nut: UPS: [email protected] (master) (power value 1)
May  4 15:29:12 PCPAI-HOME rc.nut: Using power down flag file /etc/nut/no_killpower
May  4 15:29:12 PCPAI-HOME upsmon[58166]: Startup successful
May  4 15:29:12 PCPAI-HOME upsmon[58166]: Warning: running as one big root process by request (upsmon -p)
May  4 15:29:12 PCPAI-HOME upsd[58163]: User [email protected] logged into UPS [ups]
May  4 15:29:12 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:12 PCPAI-HOME upsmon[58166]: Communications with UPS [email protected] lost
May  4 15:29:17 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:17 PCPAI-HOME upsmon[58166]: UPS [email protected] is unavailable
May  4 15:29:22 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:27 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:32 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:37 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:42 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:47 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:52 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:29:57 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:30:02 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:30:07 PCPAI-HOME upsmon[58166]: Poll UPS [[email protected]] failed - Driver not connected
May  4 15:30:07 PCPAI-HOME ool www[57807]: /usr/local/emhttp/plugins/nut-dw/scripts/restart
May  4 15:30:07 PCPAI-HOME rc.nut: Stopping the NUT services... 
May  4 15:30:07 PCPAI-HOME upsmon[58166]: Signal 15: exiting
May  4 15:30:07 PCPAI-HOME rc.nut: Network UPS Tools upsmon 2.7.4.1
May  4 15:30:07 PCPAI-HOME upsd[58163]: User [email protected] logged out from UPS [ups]
May  4 15:30:07 PCPAI-HOME upsd[58163]: mainloop: Interrupted system call
May  4 15:30:07 PCPAI-HOME upsd[58163]: Signal 15: exiting
May  4 15:30:07 PCPAI-HOME rc.nut: Network UPS Tools upsd 2.7.4.1
May  4 15:30:09 PCPAI-HOME rc.nut: Can't open /var/run/nut/blazer_ser-ups.pid: No such file or directory
May  4 15:30:09 PCPAI-HOME rc.nut: Can't open /var/run/nut/blazer_ser-auto.pid either: No such file or directory
May  4 15:30:09 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:30:13 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:30:16 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:30:16 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:30:16 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:30:17 PCPAI-HOME rc.nut: Fatal error: unusable configuration
May  4 15:30:17 PCPAI-HOME rc.nut: Network UPS Tools - Megatec/Q1 protocol serial driver 1.58 (2.7.4.1)
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut: Unable to open auto: No such file or directory
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut: Things to try:
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut:  - Check 'port=' in ups.conf
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut:  - Check owner/permissions of all parts of path
May  4 15:30:17 PCPAI-HOME rc.nut: 
May  4 15:30:17 PCPAI-HOME rc.nut: Driver failed to start (exit status=1)
May  4 15:30:17 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:31:59 PCPAI-HOME ool www[63635]: /usr/local/emhttp/plugins/nut-dw/scripts/start
May  4 15:32:00 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:32:02 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:32:02 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:32:02 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:32:05 PCPAI-HOME rc.nut: No supported UPS detected
May  4 15:32:05 PCPAI-HOME rc.nut: Network UPS Tools - Megatec/Q1 protocol USB driver 0.20 (2.7.4.1)
May  4 15:32:05 PCPAI-HOME rc.nut: Driver failed to start (exit status=1)
May  4 15:32:05 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1
May  4 15:32:12 PCPAI-HOME ool www[64160]: /usr/local/emhttp/plugins/nut-dw/scripts/start
May  4 15:32:13 PCPAI-HOME rc.nut: Writing NUT configuration...
May  4 15:32:15 PCPAI-HOME rc.nut: Updating permissions for NUT...
May  4 15:32:15 PCPAI-HOME rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May  4 15:32:15 PCPAI-HOME rc.nut: Disabling the NUT Runtime Statistics Module...
May  4 15:32:18 PCPAI-HOME rc.nut: No supported UPS detected
May  4 15:32:18 PCPAI-HOME rc.nut: Network UPS Tools - Megatec/Q1 protocol USB driver 0.20 (2.7.4.1)
May  4 15:32:18 PCPAI-HOME rc.nut: Driver failed to start (exit status=1)
May  4 15:32:18 PCPAI-HOME rc.nut: Network UPS Tools - UPS driver controller 2.7.4.1

dont know what to do

tried on legacy and 2.8.2

 

Sorry, it doesn't seem like this UPS manufacturer is supported by NUT at all.

It's also not listed in the hardware compatibility list: https://networkupstools.org/stable-hcl.html

On 5/4/2024 at 4:16 AM, Rysz said:

 

nut-2.8.2-x86_64-2debug.txz 4.94 MB · 1 download


Here we go - current master with debug symbols, same procedure as before.

Please do report back again with your findings - thanks in advance! 🙂 

 

 

@Rysz Thanks again for generating the new build from the NUT master branch. The NUT fixes for Gamatronic Driver worked, and it's finally the first time I've been able to get NUT to start on my UPS "Nobreak NHS Premium PDV Senoidal 1500 VA" from Brazillian brand "NHS Sistemas de Energia"



image.thumb.png.e2b190353a0e1c29bbf6c4bdcb8a22c5.png

 

1 hour ago, luzfcb said:

 

@Rysz Thanks again for generating the new build from the NUT master branch. The NUT fixes for Gamatronic Driver worked, and it's finally the first time I've been able to get NUT to start on my UPS "Nobreak NHS Premium PDV Senoidal 1500 VA" from Brazillian brand "NHS Sistemas de Energia"



image.thumb.png.e2b190353a0e1c29bbf6c4bdcb8a22c5.png

 


Hey, thanks for reporting back and glad it works for you now. I've just pushed an update to NUT where the "preview (latest build)" backend is now today's master including the fixes for your driver. So after updating NUT you just need to choose the "preview (latest build)" backend in NUT Settings and reboot your system afterwards, then you'll be on that driver natively (also surviving any system reboots).

 

Thanks again for your help and patience investigating this issue. 🙂 

 

Edited by Rysz

Hi Everyone,

I have question about Back-UPS XS 1300G Battery upgrades. My original batteries died and i replaced them with lead acid batteries different capacity ( much higher ) and same voltage. Is it possible to " explain" to UPS that need s to calculate estimated times for battery life time? It reports 1:15 minutes on 24V 130AH batteries. Also, what is the format of command in upc.conf that i can change battery manufacture date? i tried "battery.mfr.date : 2023/06/10" , battery.mfr.date = 2023/06/10 but that just disables plugin.

 

Sorry, im new in all this and my programming skils are limited with copy and paste. However, i would like to extend UPS backup time .

Any help is appreciated,

 

Best Regards,

Tim

itjtower-diagnostics-20240508-1107.zip

15 hours ago, Tim_J said:

Hi Everyone,

I have question about Back-UPS XS 1300G Battery upgrades. My original batteries died and i replaced them with lead acid batteries different capacity ( much higher ) and same voltage. Is it possible to " explain" to UPS that need s to calculate estimated times for battery life time? It reports 1:15 minutes on 24V 130AH batteries. Also, what is the format of command in upc.conf that i can change battery manufacture date? i tried "battery.mfr.date : 2023/06/10" , battery.mfr.date = 2023/06/10 but that just disables plugin.

 

Sorry, im new in all this and my programming skils are limited with copy and paste. However, i would like to extend UPS backup time .

Any help is appreciated,

 

Best Regards,

Tim

itjtower-diagnostics-20240508-1107.zip 162.07 kB · 0 downloads

 

Sorry, I can't provide support for usage cases outside of manufacturer's specifications. For safety reasons and from experience I'd also strongly advise against using any different battery capacity than those your UPS was rated for by the UPS manufacturer. The electrical mechanisms in the UPS may not safely be able to charge and/or discharge the higher capacity battery you are using, which may be hazardous for several reasons (fire, electrical shock, ...)

 

Edited by Rysz

Understood.

 

Thank you for responding,

Best Regards

20 hours ago, Tim_J said:

Is it possible to " explain" to UPS that need s to calculate estimated times for battery life time? It reports 1:15 minutes on 24V 130AH batteries.

Depending on how the UPS calculates level you might want to just go based on battery charge % instead of estimated time. Gonna need experimentation to find the right values obviously.

Also monitor your UPS' temperature, it might not have adequate cooling for operating that much longer than designed. Often unless it's designed to take additional external batteries the fact it can't be running longer than X time at Y load is kinda factored in the thermals. 

Edited by Kilrah

I've been trying to connect my Synology NAS to Unraid using this plugin without success. I have two options in Synology DSM to connect to a network UPS server, Synology NAS and SNMP. Obviously Unraid isn't a Synology NAS, so that doesn't work (I did try just in case). By default the NUT server doesn't seem to support SNMP either, anyone set this up?

12 minutes ago, Puntoboy said:

I've been trying to connect my Synology NAS to Unraid using this plugin without success. I have two options in Synology DSM to connect to a network UPS server, Synology NAS and SNMP. Obviously Unraid isn't a Synology NAS, so that doesn't work (I did try just in case). By default the NUT server doesn't seem to support SNMP either, anyone set this up?

 

Is your UPS physically connected to your UNRAID server or your Synology NAS?

What the right command for fsd (shutdown) the ups and server and all connected pc ,if i dont want to wait 10 min 

as i have in setting Time on Battery before Shutdown (Minutes): 10 ?

 

/etc/rc.d/rc.nut shutdown 2>&1 | logger -t "rc.nut"

 

3 minutes ago, Masterwishx said:

What the right command for fsd (shutdown) the ups and server and all connected pc ,if i dont want to wait 10 min 

as i have in setting Time on Battery before Shutdown (Minutes): 10 ?

 

/etc/rc.d/rc.nut shutdown 2>&1 | logger -t "rc.nut"

 

 

Use this command to start the NUT shutdown routine now:

upsmon -c fsd

 

The command you posted would result in an unclean shutdown because it would kill the power instantly.

1 minute ago, Rysz said:

 

Use this command to start the NUT shutdown routine now:

upsmon -c fsd

 

The command you posted would result in an unclean shutdown because it would kill the power instantly.

 

OK, i just tryed to find in code what command running in plugin for image.thumb.png.b4c76c7cba6dadd73dec4859ecbcdeda.png

is also good ?

upscmd shutdown.return - Turn off the load and return when power is back

3 minutes ago, Masterwishx said:

is also good ?

upscmd shutdown.return - Turn off the load and return when power is back

 

No, because this will also kill the power of the UPS instantly and result in an unclean shutdown on all your clients and server. Always use only this command to trigger the NUT shutdown routine: It ensures a clean shutdown of your clients and your server, will also disable the UPS power (if that is configured in the GUI) after the clean shutdown and start the UPS again when the power is back.

 

upsmon -c fsd

 

Edited by Rysz

On 5/5/2024 at 10:55 AM, Rysz said:

 

Sorry, it doesn't seem like this UPS manufacturer is supported by NUT at all.

It's also not listed in the hardware compatibility list: https://networkupstools.org/stable-hcl.html

And a internal vm, i have a install for it

4 hours ago, pcpai said:

And a internal vm, i have a install for it

 

What do you mean?

Hello guys,

Does anyone of you run NetworkUPS Tools with the PeaNUT Homepage integration?  I had it working in the past when i was trying out an ACP UPS. However, with my Cyberpower UPS (way lower idle draw from the UPS itself) I cannot get this widget to work. 

 

Any ideas what i might have configured wrong?

https://gethomepage.dev/latest/widgets/services/peanut/

 

      - tmoUPS:
            icon: https://cdn-icons-png.flaticon.com/512/2138/2138730.png
            description: tmo UPS
            siteMonitor: http://192.168.178.200:9990
            statusStyle: "dot"
            widget:
                type: peanut
                url: http://192.168.178.200:9990
                key: ups
                fields: ["battery_charge", "ups_load", "ups_status"]


grafik.png.39dae29a1fcaa1537a5357dc4b49d4ea.png

grafik.png

On 5/13/2024 at 2:07 PM, Rysz said:

 

What do you mean?

Install the drivers on a vm

And make it send the data to unraid ir Control it

IMG_20240515_223306.jpg

Edited by pcpai

I am using the Huawei UPS2000-A-2KTTS | 2KVA / 1600W with a built-in battery tower UPS, but when I use the NUT Device Scanner, it shows the following message:

usb3.thumb.png.1b1be493b38ebfef64caba01d087a003.png

NO DEVICES FOUND Please visit the 'Driver Guide' and manually choose the recommended driver for your UPS. In case of persisting problems please try another physical port, cable or the 'Support Thread'.

However, I checked the compatibility on the NUT Hardware Compatibility List and found that my UPS is supported. I am not sure what is wrong or if my settings are incorrect. I would appreciate any help with this issue.

ups1.png

ups2.png

ups4.png

2 minutes ago, dicry said:

I am using the Huawei UPS2000-A-2KTTS | 2KVA / 1600W with a built-in battery tower UPS, but when I use the NUT Device Scanner, it shows the following message:

usb3.thumb.png.1b1be493b38ebfef64caba01d087a003.png

NO DEVICES FOUND Please visit the 'Driver Guide' and manually choose the recommended driver for your UPS. In case of persisting problems please try another physical port, cable or the 'Support Thread'.

However, I checked the compatibility on the NUT Hardware Compatibility List and found that my UPS is supported. I am not sure what is wrong or if my settings are incorrect. I would appreciate any help with this issue.

ups1.png

ups2.png

ups4.png

 

Your settings are not correct, please try this configuration instead and let me know:

grafik.png.0de3732afc53ccebf86f5c8c24eb94ce.png

Thank you for your help, it is now working correctly. I have another question: I am currently using a 2303 to USB adapter, but I have an additional SNMP intelligent card. However, according to the Hardware Compatibility List, it seems that the UPS2000-A series does not support the SNMP intelligent card. I am not sure if it will still work properly if I switch to the SNMP card.

ups5.png

7 minutes ago, dicry said:

Thank you for your help, it is now working correctly. I have another question: I am currently using a 2303 to USB adapter, but I have an additional SNMP intelligent card. However, according to the Hardware Compatibility List, it seems that the UPS2000-A series does not support the SNMP intelligent card. I am not sure if it will still work properly if I switch to the SNMP card.

ups5.png

 

It can also work with SNMP, because for SNMP you would use another driver and not "huawei-ups2000" (that is only for a physical connection to the UPS). If you use SNMP, you would use the driver "snmp-ups" and set the UPS Port to the IP of your SNMP card (see where the red arrow is in the screenshot).

 

This would be an example SNMP configuration:

grafik.png.08b1cb70f2b5c346d5089e35018ec88b.png


But beware you need to make sure that the network connection to your UPS stays available in a power outage, so any switches also need to be connected to the UPS.

 

Edited by Rysz

22 minutes ago, Rysz said:

 

它还可以与 SNMP 一起使用,因为对于 SNMP,您将使用另一个驱动程序,而不是“huawei-ups2000”(仅用于与 UPS 的物理连接)。如果您使用 SNMP,则可以使用驱动程序“snmp-ups”并将 UPS 端口设置为 SNMP 卡的 IP(参见屏幕截图中红色箭头的位置)。这是 SNMP 配置示例:

 

图.png.08b1cb70f2b5c346d5089e35018ec88b.png


但请注意,您需要确保 UPS 的网络连接在停电时保持可用,因此任何交换机也需要连接到 UPS。

 

Thanks!!!

Any news for the APC Back-UP UPS?

image.png.99914ae42e0fdd3e774f21cade10be3e.png

After reboot it works for some time, then freeze

image.thumb.png.ab9a1396ae81de86d20818d872d38abd.png

Tried with usb power override without succes

EDIT: Saw the post about APC, resetted config, will see about freezing

 

nut-debug-20240520202951.zip

Edited by PilaScat

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.