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.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

[Plugin] NUT v2 - Network UPS Tools

dmacias
in Plugin Support

Featured Replies

2 minutes ago, Dwsomers said:

Appreciate it if developers could respond. Will this hardware be included in an upcoming version update of NUT?
Also, is there any way I can assist with troubleshooting?

Please post the NUT debug package which can be found in "NUT Settings", so I can take a look.

  • Quote
    • Replies 2.1k
    • Views 460.9k
    • Created
    • Last Reply

    Top Posters In This Topic

    Popular Days

    Most Popular Posts

    • SimonF
      SimonF

      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

    • SimonF
      SimonF

      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.

    • Rysz
      Rysz

      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

    Just now, Dwsomers said:

    Thank you for taking a look, much appreciated.
    Please find package attached.

    nut-debug-20251019160603.zip

    Thank you, any chance you could also post the drivers you were given?
    I may be able to take a look if we can derive a driver for NUT from them.

  • Quote

    ugreen_ups_firmware_V3.3.bin
    No problem, UGreen directed me to their website and to the driver download (see attached png screenshot)
    I've also attached the actual driver bin file that you get from the download.

    US3000.png

  • Quote
    6 minutes ago, Dwsomers said:

    Thank you for taking a look, much appreciated.
    Please find package attached.

    nut-debug-20251019160603.zip

    I'm confident we can get this to work with NUT as it reports as:
    Bus 003 Device 002: ID 2b89:ffff UGREEN US3000

    And this type of UPS is reported to work with NUT after some tweaking of settings:
    https://github.com/networkupstools/nut/issues/2987

    First stop NUT, then set this setting:
    grafik.png

    Then apply the setting and on the same page go to the NUT Configuration Editor.

    Put into UPS.CONF the following settings:

    grafik.png
    Save the settings and then change this setting as follows:

    grafik.png

    Then apply the setting and start NUT again, report back if it works.

    If it doesn't work, produce another debug package and post it again here.

  • Quote
    • Thanks 1

    Ok, thank you. )I will follow your instructions and provide feedback shortly.

  • Quote

    Unfortunately, it failed to start again after the config changes.
    Please find the debug package attached.

    Kind regards

    nut-debug-20251019163338.zip

  • Quote
    4 minutes ago, Dwsomers said:

    Unfortunately, it failed to start again after the config changes.
    Please find the debug package attached.

    Kind regards

    nut-debug-20251019163338.zip

    Please add to UPS.CONF: debug_min = 6 and try starting again, then post the debug package again.

  • Quote

    Yes!!!
    It didn't crash this time, and I am getting info from the device now.
    Please find attached nut debug package.
    Thank you so much, I didn't think I'd ever get it working!!

    nut-debug-20251019164515.zip

  • Quote
    3 minutes ago, Dwsomers said:

    Yes!!!
    It didn't crash this time, and I am getting info from the device now.
    Please find attached nut debug package.
    Thank you so much, I didn't think I'd ever get it working!!

    nut-debug-20251019164515.zip

    Thank you, that's great to hear - please make sure to remove the debug line from the configuration again and restart NUT after. Otherwise the debug information will fill up your logs.

  • Quote
    4 minutes ago, Rysz said:

    Thank you, that's great to hear - please make sure to remove the debug line from the configuration again and restart NUT after. Otherwise the debug information will fill up your logs.

    All done and restarted with no issues.
    Thanks again )

  • Quote
    • Like 1
    On 10/19/2025 at 3:35 AM, lowsanity said:

    Hello,

    Just purchased an Eaton 9PX and the driver doesn't seem to load when connected via USB. I've tried different USB ports, cables, motherboards (2nd Unraid server), 2.82 through to preview builds of NUT. Attached debug file.

    I wanted to check if there's anything I can or should do to get this working before I get a network card for this unit.

    nut-debug-20251019122507.zip

    Can you try putting in your UPS.CONF on line 9 or later: synchronous

    Then save and (re-)start NUT?

  • Quote
    On 10/13/2025 at 7:56 PM, gundamguy said:

    Just wanted to let you know that I was able to get the Unfi Tower UPS NUT server working with this plugin.

    1) The Unifi interface is confusing.
    2) I had to do manual setup of the upsmon.conf file.

    MONITOR "Unifi_Id"@[Tower_IP_Addess]:[Tower_Port] 1 user userpass slave
    Example
    MONITOR [email protected]:3493 1 nutuser nutpass slave

    Additionally I had to uncheck the box labeled "login credential" in Unifi because even though it says non UI devices will need to log in with a credential, it seems like unchecking the box make it not require a password at all. Additionally I wasn't able to get it to accept my user / password even if I checked the box and set it in this plugin and the unfi the same, probly because of an issue with the upsd.users file on the tower. (Was not able to trouble shoot this further.) So the user ans userpass part of the monitor line might not be required... not sure.

    Anyway doing the manual setup + unchecking the box allowed me to get a connection with the remote Unifi Tower UPS established.

    Also I'm new to this plugin so I'm not sure how to configure the NUT plugin to shutdown the server when the UPS Tower signals a power loss or whatever... but hey step one solved right?

    Is there any chance you could post your full config (minus the credentials.)
    I'm trying to get this setup. It was rather painless on TrueNAS, which was the only thing that was painless over on that. I'm trying to get it working on unraid and I am having an impossible time with it.

  • Quote
    7 hours ago, Rysz said:

    Can you try putting in your UPS.CONF on line 9 or later: synchronous

    Then save and (re-)start NUT?

    Thanks for looking into this.

    The service starts, but no data is retrieved from the UPS.

    I can see this in syslog-

    Fatal error: 'synchronous' is not a valid flag for this driver.

    Followed by many lines of -

    Poll UPS [[email protected]] failed - Driver not connected

    I also tried synchronous = yes but received the same as before: 2 different HID descriptors Unable to get Report descriptor: Resource temporarily unavailable

    nut-debug-20251021055120.zip

  • Quote

    Hey,

    I´m trying to get the new Ubuiqiti Tower UPS connected.

    Only configuration it has is enabling the internal NUT-Server and config a user which i have done.

    In the NUT Plugin i configure it as slave and give the Ip, user, password.

    After i start the plugin i don´t get any errors in the log but i also get no read from the ups.

    I can ping the UPS just fine from the unraid server.

    LOG says:

    Oct 21 14:10:44 TEST rc.nut: Writing NUT configuration...

    Oct 21 14:10:45 TEST rc.nut: Updating permissions for NUT...

    Oct 21 14:10:45 TEST rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...

    Oct 21 14:10:45 TEST rc.nut: Disabling the NUT Runtime Statistics Module...

    Oct 21 14:10:46 TEST rc.nut: Network UPS Tools upsmon 2.8.4 release

    Oct 21 14:10:46 TEST rc.nut: UPS: [email protected] (secondary) (power value 1)

    Oct 21 14:10:46 TEST rc.nut: Using power down flag file /etc/nut/no_killpower

    Oct 21 14:10:46 TEST upsmon[608694]: Startup successful

    Oct 21 14:10:46 TEST upsmon[608694]: Warning: running as one big root process by request (upsmon -p)

    And thats it. Anything more that i can try?

    Thanks in advance

    Edited by dam_j

  • Quote
    11 hours ago, dam_j said:

    Hey,

    I´m trying to get the new Ubuiqiti Tower UPS connected.

    Only configuration it has is enabling the internal NUT-Server and config a user which i have done.

    In the NUT Plugin i configure it as slave and give the Ip, user, password.

    After i start the plugin i don´t get any errors in the log but i also get no read from the ups.

    I can ping the UPS just fine from the unraid server.

    LOG says:

    Oct 21 14:10:44 TEST rc.nut: Writing NUT configuration...

    Oct 21 14:10:45 TEST rc.nut: Updating permissions for NUT...

    Oct 21 14:10:45 TEST rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...

    Oct 21 14:10:45 TEST rc.nut: Disabling the NUT Runtime Statistics Module...

    Oct 21 14:10:46 TEST rc.nut: Network UPS Tools upsmon 2.8.4 release

    Oct 21 14:10:46 TEST rc.nut: UPS: [email protected] (secondary) (power value 1)

    Oct 21 14:10:46 TEST rc.nut: Using power down flag file /etc/nut/no_killpower

    Oct 21 14:10:46 TEST upsmon[608694]: Startup successful

    Oct 21 14:10:46 TEST upsmon[608694]: Warning: running as one big root process by request (upsmon -p)

    And thats it. Anything more that i can try?

    Thanks in advance

    I'm also having this issue. I have the log level turned up and I'm seeing:

    Oct 21 19:14:19 namehere upsmon[128611]: [D4:128611] 5-sec delay between main loop cycles finished, took 5.000064
Oct 21 19:14:19 namehere upsmon[128611]: [D2:128611] pollups: [email protected]
Oct 21 19:14:19 namehere upsmon[128611]: [D3:128611] get_var: [email protected] / status
Oct 21 19:14:19 namehere upsmon[128611]: [D3:128611] get_var: [email protected] / buzzword
Oct 21 19:14:19 namehere upsmon[128611]: [D3:128611] get_var: [email protected] / X-buzzword
Oct 21 19:14:20 namehere upsmon[128611]: [D2:128611] parse_status: [OL CHRG]
Oct 21 19:14:20 namehere upsmon[128611]: [D3:128611] parsing: [OL]
Oct 21 19:14:20 namehere upsmon[128611]: [D4:128611] ups_on_line: [email protected] (no change)
Oct 21 19:14:20 namehere upsmon[128611]: [D3:128611] parsing: [CHRG]
Oct 21 19:14:20 namehere upsmon[128611]: [D4:128611] Known and ignored status token: [CHRG]
Oct 21 19:14:20 namehere upsmon[128611]: [D3:128611] Handled 2 status tokens
Oct 21 19:14:20 namehere upsmon[128611]: [D3:128611] Current power value: 1
Oct 21 19:14:20 namehere upsmon[128611]: [D3:128611] Minimum power value: 1
Oct 21 19:14:20 namehere upsmon[128611]: [D4:128611] Beginning 5-sec delay between main loop cycles

    I can also confirm that via WinNUT the UPS is reading out correctly with the same configurations:
    image.png

    Edited by asceticism

  • Quote
    15 hours ago, dam_j said:

    Hey,

    I´m trying to get the new Ubuiqiti Tower UPS connected.

    Only configuration it has is enabling the internal NUT-Server and config a user which i have done.

    In the NUT Plugin i configure it as slave and give the Ip, user, password.

    After i start the plugin i don´t get any errors in the log but i also get no read from the ups.

    I can ping the UPS just fine from the unraid server.

    LOG says:

    Oct 21 14:10:44 TEST rc.nut: Writing NUT configuration...

    Oct 21 14:10:45 TEST rc.nut: Updating permissions for NUT...

    Oct 21 14:10:45 TEST rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...

    Oct 21 14:10:45 TEST rc.nut: Disabling the NUT Runtime Statistics Module...

    Oct 21 14:10:46 TEST rc.nut: Network UPS Tools upsmon 2.8.4 release

    Oct 21 14:10:46 TEST rc.nut: UPS: [email protected] (secondary) (power value 1)

    Oct 21 14:10:46 TEST rc.nut: Using power down flag file /etc/nut/no_killpower

    Oct 21 14:10:46 TEST upsmon[608694]: Startup successful

    Oct 21 14:10:46 TEST upsmon[608694]: Warning: running as one big root process by request (upsmon -p)

    And thats it. Anything more that i can try?

    Thanks in advance

    4 hours ago, asceticism said:

    I'm also having this issue. I have the log level turned up and I'm seeing:

    Oct 21 19:14:19 namehere upsmon[128611]: [D4:128611] 5-sec delay between main loop cycles finished, took 5.000064
Oct 21 19:14:19 namehere upsmon[128611]: [D2:128611] pollups: [email protected]
Oct 21 19:14:19 namehere upsmon[128611]: [D3:128611] get_var: [email protected] / status
Oct 21 19:14:19 namehere upsmon[128611]: [D3:128611] get_var: [email protected] / buzzword
Oct 21 19:14:19 namehere upsmon[128611]: [D3:128611] get_var: [email protected] / X-buzzword
Oct 21 19:14:20 namehere upsmon[128611]: [D2:128611] parse_status: [OL CHRG]
Oct 21 19:14:20 namehere upsmon[128611]: [D3:128611] parsing: [OL]
Oct 21 19:14:20 namehere upsmon[128611]: [D4:128611] ups_on_line: [email protected] (no change)
Oct 21 19:14:20 namehere upsmon[128611]: [D3:128611] parsing: [CHRG]
Oct 21 19:14:20 namehere upsmon[128611]: [D4:128611] Known and ignored status token: [CHRG]
Oct 21 19:14:20 namehere upsmon[128611]: [D3:128611] Handled 2 status tokens
Oct 21 19:14:20 namehere upsmon[128611]: [D3:128611] Current power value: 1
Oct 21 19:14:20 namehere upsmon[128611]: [D3:128611] Minimum power value: 1
Oct 21 19:14:20 namehere upsmon[128611]: [D4:128611] Beginning 5-sec delay between main loop cycles

    I can also confirm that via WinNUT the UPS is reading out correctly with the same configurations:
    image.png

    Please post the NUT Debug Package found in NUT Settings.

  • Quote
    9 hours ago, Rysz said:

    Please post the NUT Debug Package found in NUT Settings.

    Here it is!nut-debug-20251022084513.zip

    Thanks for any and all help, much appreciated.

  • Quote
    12 minutes ago, asceticism said:

    Here it is!nut-debug-20251022084513.zip

    Thanks for any and all help, much appreciated.

    Nothing unusual sticks out, but it says access denied and looks like a credentials issue.

    Although that is weird, because even with wrong credentials it should show information (just not register as "slave"/secondary).

    It does look like they perhaps baked in some stricter authentication on their own; other UniFi UPS users do report:
    Still no dice connecting to the NUT server while using authentication. Unauthenticated seems OK, just when setting a username/password the NUT server is returning a mix of "ERR ACCESS-DENIED" and "ECONNRESET" when attempting to connect from any 3rd-party NUT client.

    https://community.ui.com/releases/UniFi-UPS-1-4-13/fdd23b70-1191-4bc1-8485-d85c41a3a510

    Maybe this is even some kind of "fake" NUT server (just speaking NUT protocol) that just isn't fully bug-free yet (just a guess).

    In any case, I'd also try maybe using credentials that don't have any special characters, that could be a factor also... not sure...

  • Quote
    1 minute ago, Rysz said:

    Also I'd try maybe using credentials that don't have any special characters, that could be a factor also.

    Haha at one point, I had user: nut, password: nut. Thanks for the look, surprised to see auth issues in the zip. According to the logs, it's connecting: Trying to connect to UPS [[email protected]] and Logged into UPS [email protected]

    Oct 22 09:18:21 namehere ool www[586085]: /usr/local/emhttp/plugins/nut-dw/scripts/start
Oct 22 09:18:22 namehere rc.nut: Writing NUT configuration...
Oct 22 09:18:23 namehere rc.nut: Updating permissions for NUT...
Oct 22 09:18:23 namehere rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Oct 22 09:18:23 namehere rc.nut: Enabling the NUT Runtime Statistics Module...
Oct 22 09:18:24 namehere rc.nut: Network UPS Tools upsmon 2.8.4.39-39+g009fbbd1b (development iteration after 2.8.4)
Oct 22 09:18:24 namehere rc.nut: UPS: [email protected] (secondary) (power value 1)
Oct 22 09:18:24 namehere rc.nut: Using power down flag file /etc/nut/no_killpower
Oct 22 09:18:24 namehere rc.nut:    0.000018     [D1:691416] debug level is '6'
Oct 22 09:18:24 namehere rc.nut:    0.000023     [D1:691416] will use a shutdown command (SHUTDOWNCMD): '/sbin/poweroff'
Oct 22 09:18:24 namehere rc.nut:    0.000025     [D1:691416] will use custom notification command (NOTIFYCMD): '/usr/sbin/nut-notify'
Oct 22 09:18:24 namehere upsmon[691417]: Startup successful
Oct 22 09:18:24 namehere upsmon[691417]: Warning: running as one big root process by request (upsmon -p)
Oct 22 09:18:24 namehere upsmon[691417]: [D1:691417] Saving PID 691417 into /var/run/nut/upsmon.pid
Oct 22 09:18:24 namehere upsmon[691417]: [D1:691417] upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it
Oct 22 09:18:24 namehere upsmon[691417]: [D1:691417] Trying to connect to UPS [[email protected]]
Oct 22 09:18:25 namehere upsmon[691417]: [D1:691417] Logged into UPS [email protected]
Oct 22 09:18:25 namehere upsmon[691417]: [D2:691417] pollups: [email protected]
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] get_var: [email protected] / status
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] get_var: [email protected] / buzzword
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] get_var: [email protected] / X-buzzword
Oct 22 09:18:25 namehere upsmon[691417]: [D2:691417] parse_status: [OL CHRG]
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] parsing: [OL]
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] ups_on_line: [email protected] (first time)
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] parsing: [CHRG]
Oct 22 09:18:25 namehere upsmon[691417]: [D4:691417] Known and ignored status token: [CHRG]
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] Handled 2 status tokens
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] Current power value: 1
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] Minimum power value: 1
Oct 22 09:18:25 namehere upsmon[691417]: [D4:691417] Beginning 5-sec delay between main loop cycles
Oct 22 09:18:30 namehere upsmon[691417]: [D4:691417] 5-sec delay between main loop cycles finished, took 5.000099
Oct 22 09:18:30 namehere upsmon[691417]: [D2:691417] pollups: [email protected]
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] get_var: [email protected] / status
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] get_var: [email protected] / buzzword
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] get_var: [email protected] / X-buzzword
Oct 22 09:18:30 namehere upsmon[691417]: [D2:691417] parse_status: [OL CHRG]
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] parsing: [OL]
Oct 22 09:18:30 namehere upsmon[691417]: [D4:691417] ups_on_line: [email protected] (no change)
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] parsing: [CHRG]
Oct 22 09:18:30 namehere upsmon[691417]: [D4:691417] Known and ignored status token: [CHRG]
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] Handled 2 status tokens
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] Current power value: 1
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] Minimum power value: 1
Oct 22 09:18:30 namehere upsmon[691417]: [D4:691417] Beginning 5-sec delay between main loop cycles

    Edited by asceticism
    I can't spell

  • Quote
    20 minutes ago, asceticism said:

    Haha at one point, I had user: nut, password: nut. Thanks for the look, surprised to see auth issues in the zip. According to the logs, it's connecting: Trying to connect to UPS [[email protected]] and Logged into UPS [email protected]

    Oct 22 09:18:21 namehere ool www[586085]: /usr/local/emhttp/plugins/nut-dw/scripts/start
Oct 22 09:18:22 namehere rc.nut: Writing NUT configuration...
Oct 22 09:18:23 namehere rc.nut: Updating permissions for NUT...
Oct 22 09:18:23 namehere rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Oct 22 09:18:23 namehere rc.nut: Enabling the NUT Runtime Statistics Module...
Oct 22 09:18:24 namehere rc.nut: Network UPS Tools upsmon 2.8.4.39-39+g009fbbd1b (development iteration after 2.8.4)
Oct 22 09:18:24 namehere rc.nut: UPS: [email protected] (secondary) (power value 1)
Oct 22 09:18:24 namehere rc.nut: Using power down flag file /etc/nut/no_killpower
Oct 22 09:18:24 namehere rc.nut:    0.000018     [D1:691416] debug level is '6'
Oct 22 09:18:24 namehere rc.nut:    0.000023     [D1:691416] will use a shutdown command (SHUTDOWNCMD): '/sbin/poweroff'
Oct 22 09:18:24 namehere rc.nut:    0.000025     [D1:691416] will use custom notification command (NOTIFYCMD): '/usr/sbin/nut-notify'
Oct 22 09:18:24 namehere upsmon[691417]: Startup successful
Oct 22 09:18:24 namehere upsmon[691417]: Warning: running as one big root process by request (upsmon -p)
Oct 22 09:18:24 namehere upsmon[691417]: [D1:691417] Saving PID 691417 into /var/run/nut/upsmon.pid
Oct 22 09:18:24 namehere upsmon[691417]: [D1:691417] upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it
Oct 22 09:18:24 namehere upsmon[691417]: [D1:691417] Trying to connect to UPS [[email protected]]
Oct 22 09:18:25 namehere upsmon[691417]: [D1:691417] Logged into UPS [email protected]
Oct 22 09:18:25 namehere upsmon[691417]: [D2:691417] pollups: [email protected]
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] get_var: [email protected] / status
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] get_var: [email protected] / buzzword
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] get_var: [email protected] / X-buzzword
Oct 22 09:18:25 namehere upsmon[691417]: [D2:691417] parse_status: [OL CHRG]
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] parsing: [OL]
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] ups_on_line: [email protected] (first time)
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] parsing: [CHRG]
Oct 22 09:18:25 namehere upsmon[691417]: [D4:691417] Known and ignored status token: [CHRG]
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] Handled 2 status tokens
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] Current power value: 1
Oct 22 09:18:25 namehere upsmon[691417]: [D3:691417] Minimum power value: 1
Oct 22 09:18:25 namehere upsmon[691417]: [D4:691417] Beginning 5-sec delay between main loop cycles
Oct 22 09:18:30 namehere upsmon[691417]: [D4:691417] 5-sec delay between main loop cycles finished, took 5.000099
Oct 22 09:18:30 namehere upsmon[691417]: [D2:691417] pollups: [email protected]
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] get_var: [email protected] / status
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] get_var: [email protected] / buzzword
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] get_var: [email protected] / X-buzzword
Oct 22 09:18:30 namehere upsmon[691417]: [D2:691417] parse_status: [OL CHRG]
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] parsing: [OL]
Oct 22 09:18:30 namehere upsmon[691417]: [D4:691417] ups_on_line: [email protected] (no change)
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] parsing: [CHRG]
Oct 22 09:18:30 namehere upsmon[691417]: [D4:691417] Known and ignored status token: [CHRG]
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] Handled 2 status tokens
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] Current power value: 1
Oct 22 09:18:30 namehere upsmon[691417]: [D3:691417] Minimum power value: 1
Oct 22 09:18:30 namehere upsmon[691417]: [D4:691417] Beginning 5-sec delay between main loop cycles

    Can you try running in command line:

    upsc [email protected]

    upsc [email protected] ups.status

  • Quote
    6 hours ago, Rysz said:

    Can you try running in command line:

    upsc [email protected]

    upsc [email protected] ups.status

    I'm having issues with my UniFi UPS as well. I ran that command and I couldn't get it to connect unless I added the port I used as a socket at the end of the IP, so I'd have to do something like upsc [email protected]:123 otherwise I got a connection refused. It only works if I have the credentials disabled.
    Is there a way in the manual config to point to a hostname or at least add the socket on the end of the IP?

  • Quote

    Hello guys !

    I recently bought one Wöhrle UPS in quite good condition and I am trying to integrate it into Unraid.

    The manufacturer's Windows application works perfectly and displays all information correctly, such as remaining runtime, charge level, and other details.

    However, when using NUT only a very limited set of data is being reported, and runtime left on battery is missing + the battery charge stays at 100%..

    image.png

    Is there a known driver or a specific configuration within NUT for Wöhrle UPS devices that allows access to the full range of device information?

    Thank you in advance for your help and suggestions.

    EDIT : I have a licence key written on the UPS if its needed.

    EDIT2: This manual seems be really helpfull, unfortunately I hate no idea what Im doing o

    https://generex.de/media/pages/packages/documents/manuals/4e7a06ffcc-1755789504/manual_UPSMAN_en.pdf

    Wöhrle Convert 3000/4N2
    https://generex.de/partners/oem/45/software/upsman/update (Link to the driver)

    nut-debug-20251024182714.zip

    Edited by Furlings

  • Quote

    Is this plugin compatible with Unraid 7.2 RC2?

    I recently had to update my NAS to 7.2 so I could mount an NTFS drive.

    I want to monitor my UPS from this machine, however I can't turn on NUT.

    The syslog shows a bunch of errors.

    UPS = CyberPower CP1500AVRLCD3 Intelligent LCD UPS System, 1500VA/900W

  • Quote

    • 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...
    Go to topic listing

    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.