Thanks got a bit further now the log shows this:

 

Nov 6 22:02:48 UNRAID ool www[15543]: /usr/local/emhttp/plugins/nut-dw/scripts/start

Nov 6 22:02:49 UNRAID rc.nut: Writing NUT configuration...

Nov 6 22:02:51 UNRAID rc.nut: Updating permissions for NUT...

Nov 6 22:02:51 UNRAID rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...

Nov 6 22:02:51 UNRAID rc.nut: Disabling the NUT Runtime Statistics Module...

Nov 6 22:02:52 UNRAID rc.nut: Fatal error: unusable configuration

Nov 6 22:02:52 UNRAID rc.nut: Network UPS Tools - PowerCom protocol UPS driver 0.22 (2.8.2)

Nov 6 22:02:52 UNRAID rc.nut: Nov 6 22:02:52 UNRAID rc.nut: Unable to open auto: No such file or directory

Nov 6 22:02:52 UNRAID rc.nut: Nov 6 22:02:52 UNRAID rc.nut: Things to try:

Nov 6 22:02:52 UNRAID rc.nut:

Nov 6 22:02:52 UNRAID rc.nut: - Check 'port=' in ups.conf

Nov 6 22:02:52 UNRAID rc.nut:

Nov 6 22:02:52 UNRAID rc.nut: - Check owner/permissions of all parts of path

Nov 6 22:02:52 UNRAID rc.nut:

Nov 6 22:02:52 UNRAID rc.nut: Driver failed to start (exit status=1)

Nov 6 22:02:52 UNRAID rc.nut: Network UPS Tools - UPS driver controller 2.8.2

 

Where do I go looking for this file and what should be in it?

 

1 minute ago, Dwarfboysim said:

Thanks got a bit further now the log shows this:

 

Nov 6 22:02:48 UNRAID ool www[15543]: /usr/local/emhttp/plugins/nut-dw/scripts/start

Nov 6 22:02:49 UNRAID rc.nut: Writing NUT configuration...

Nov 6 22:02:51 UNRAID rc.nut: Updating permissions for NUT...

Nov 6 22:02:51 UNRAID rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...

Nov 6 22:02:51 UNRAID rc.nut: Disabling the NUT Runtime Statistics Module...

Nov 6 22:02:52 UNRAID rc.nut: Fatal error: unusable configuration

Nov 6 22:02:52 UNRAID rc.nut: Network UPS Tools - PowerCom protocol UPS driver 0.22 (2.8.2)

Nov 6 22:02:52 UNRAID rc.nut: Nov 6 22:02:52 UNRAID rc.nut: Unable to open auto: No such file or directory

Nov 6 22:02:52 UNRAID rc.nut: Nov 6 22:02:52 UNRAID rc.nut: Things to try:

Nov 6 22:02:52 UNRAID rc.nut:

Nov 6 22:02:52 UNRAID rc.nut: - Check 'port=' in ups.conf

Nov 6 22:02:52 UNRAID rc.nut:

Nov 6 22:02:52 UNRAID rc.nut: - Check owner/permissions of all parts of path

Nov 6 22:02:52 UNRAID rc.nut:

Nov 6 22:02:52 UNRAID rc.nut: Driver failed to start (exit status=1)

Nov 6 22:02:52 UNRAID rc.nut: Network UPS Tools - UPS driver controller 2.8.2

 

Where do I go looking for this file and what should be in it?

 

 

Please post the NUT Debug Package that can be found inside NUT Settings page.

Here it is

nut-debug-20241106221449.zip

1 hour ago, Dwarfboysim said:

Here it is

nut-debug-20241106221449.zip 259.38 kB · 0 downloads

 

There's nothing I can see here that indicates your USB-connected UPS is detected by NUT.

You can try the "optiups" driver with "UPS Driver Port" set to "/dev/ttyUSB0" (without the quotes).

 

If that doesn't work you can still try these drivers:

• "usbhid-ups" driver with "UPS Driver Port" set to "auto".
• "nutdrv_qx" driver with "UPS Driver Port" set to "auto".
• "blazer_usb" driver with "UPS Driver Port" set to "auto".

It's not really a common UPS, so apart from that I'm not sure what else you could try.

I think your best bet is the "optiups" driver with either "/dev/ttyUSB0" or an actual serial cable.

which NUT details tell us how long our battery can last?

 

I do not see `battery.runtime` / `battery.runtime.low` information

nut-ups.dev

16 hours ago, shawnngtq said:

which NUT details tell us how long our battery can last?

 

I do not see `battery.runtime` / `battery.runtime.low` information

nut-ups.dev 877 B · 0 downloads

 

If your UPS or the UPS driver doesn't report it, there's no real way to do it - I'm afraid.

On 11/17/2024 at 9:21 AM, shawnngtq said:

how long our battery can last

Set the shutdown to occur 3 or so minutes after power is lost. If the UPS is appropriately sized and the battery is in good condition that should allow for delays in shutdown, and keep the battery above 50% charge for best life. You should never run a UPS until the last possible moment, it's hard on equipment, and doesn't gain you anything.

Sorry to bug again, but I had issues a few months ago with a Lievert/Vertiv GXT5 UPS that I ended up moving to SNMP since it was more "enterprise" and the USB drivers didnt work for it. I can get all sorts of great readings from it, but I noticed my syslog was filling up. When watching it when NUT is on, I get this error repeatedly. I'm guessing it's the SNMP connection since it references the OID, but I'm not sure what to test. I'm using SNMP v2c at your request. Should I bump that down to v1 or is v3 working any better? Thanks!

 

Nov 23 23:13:31 NAS01 snmp-ups[9618]: [ups] Warning: type error exception (OID = .1.3.6.1.2.1.33.1.7.7.1)

Hi there,

 

do someone got an SC450RMI1U working? I was missing the origin cable so I bought that one (Link).

It worked on my windows server with the PowerChute and the CP210x USB to UART Bridge Virtual COM Port (VCP) drivers (link).

 

Refer to this Network UPS Tools - Smart-UPS SC450 RM I should be able to set the apcsmart as driver. But I missing it in the dropdown menu. Is there a way to get the CP210x USB to UART Bridge Virtual COM Port on NUT?

 

Or should I use another cable?

1 minute ago, kitharo said:

Hi there,

 

do someone got an SC450RMI1U working? I was missing the origin cable so I bought that one (Link).

It worked on my windows server with the PowerChute and the CP210x USB to UART Bridge Virtual COM Port (VCP) drivers (link).

 

Refer to this Network UPS Tools - Smart-UPS SC450 RM I should be able to set the apcsmart as driver. But I missing it in the dropdown menu. Is there a way to get the CP210x USB to UART Bridge Virtual COM Port on NUT?

 

Or should I use another cable?

 

Choose "custom (not listed)" for UPS Driver and put "apcsmart" in the textbox appearing to the right. For UPS Port, put the path to the serial device. By clicking on the magnifying glass icon next to UPS Driver you can scan for devices.

15 minutes ago, Rysz said:

For UPS Port, put the path to the serial device.

I'm not sure about how can I do this. How do I know the path (sorry for that dumb question).

I installed the USB Manager Plugin with the USB Manager Serial Options addon but there is also no option to show the path.

Can you help me out?

 

 

From the log of the device:

 

USB to Serial cable are always confusing

Edited November 24, 20241 yr by kitharo
additional info

1 minute ago, kitharo said:

I'm not sure about how can I do this. How do I know the path (sorry for that dumb question).

I installed the USB Manager Plugin with the USB Manager Serial Options addon but there is also no option to show the path.

Can you help me out?

 

 

 

Please post the NUT Debug Package that can be found in NUT Settings.

2 minutes ago, Rysz said:

Please post the NUT Debug Package that can be found in NUT Settings.

Here it is. Thank you in advance!

nut-debug-20241124111031.zip

4 minutes ago, kitharo said:

Here it is. Thank you in advance!

nut-debug-20241124111031.zip 134.26 kB · 0 downloads

 

NUT didn't detect the UPS, but you can try setting "UPS Port" to "/dev/ttyUSB0" (without quotes).

Please let me know if you had any luck with that, if not - please also post the logs again. 🙂 

 

4 minutes ago, Rysz said:

 

NUT didn't detect the UPS, but you can try setting "UPS Port" to "/dev/ttyUSB0".

Please let me know if you had any luck with that. 🙂 

Hi Rysz,

 

you saved my sunday! Thank you very much!

 

If other looking for an solution in the future with the SC450RMI1U and an usb to serial cable that comes with an CP210x USB to UART Bridge Virtual COM Port:

 

Edited November 24, 20241 yr by kitharo

5 minutes ago, kitharo said:

Hi Rysz,

 

you saved my sunday! Thank you very much!

 

No problem, I'm glad that it works for you - can you do me a favour and post a screenshot of the GUI dashboard? I mean this part, at least how it looks for you:

 

 

I just saw your UPS reports some values as floating point, so I might need to fix the display for the next NUT version. Ideally, if you can - please also attach the NUT Debug Package (fetch a new one from the NUT Settings). 🙂 

 

2 minutes ago, Rysz said:

 

No problem, I'm glad that it works for you - can you do me a favour and post a screenshot of the GUI dashboard?

 

This part, at least how it looks for you:

 

I just saw your UPS reports some values as floating point, so I might need to fix the display for the next NUT version.

Ideally, if you can - please also attach the NUT Debug Package (fetch a new one from the NUT Settings).

 

Here it is:

 

1 minute ago, kitharo said:

Here it is:

 

 

Great, I can help you fill the missing variables - set your settings like this:

Please let me know if that worked for you and filled in the rest of the fields 🙂 

6 minutes ago, Rysz said:

please also attach the NUT Debug Package (fetch a new one from the NUT Settings).

Missed reading that! Here it is

 

2 minutes ago, Rysz said:

Please let me know if that worked for you and filled in the rest of the fields 🙂 

It does! Thank you very much!

 

 

nut-debug-20241124112740.zip

16 hours ago, jholman76 said:

Sorry to bug again, but I had issues a few months ago with a Lievert/Vertiv GXT5 UPS that I ended up moving to SNMP since it was more "enterprise" and the USB drivers didnt work for it. I can get all sorts of great readings from it, but I noticed my syslog was filling up. When watching it when NUT is on, I get this error repeatedly. I'm guessing it's the SNMP connection since it references the OID, but I'm not sure what to test. I'm using SNMP v2c at your request. Should I bump that down to v1 or is v3 working any better? Thanks!

 

Nov 23 23:13:31 NAS01 snmp-ups[9618]: [ups] Warning: type error exception (OID = .1.3.6.1.2.1.33.1.7.7.1)

 

Attaching my debug logs, if you have a moment to look. The UNRAID syslog is just that above error over and over, but it seems like the UPS is working fine. It shows footer information and the UPS being online, etc. 

 

I had it in bypass mode for a while and changed it to not be. I'm not 100% sure what this brand of UPS wants to be in as the NUT plugin shows green when not in bypass, but the UPS GUI shows a warning... when I go on bypass, they are opposite. UNRAID shows the yellow/amber warning and the UPS shows all green. go figure. 

 

nut-debug-20241124160132.zipnut-ups.dev

I'm getting this error randomly and can't figure out what's wrong.

```

zeus usbhid-ups[1012]: nut_libusb_get_string: Pipe error

```

nut-debug-20241124205841.zip

I've been getting these errors since I started using NUT:

 

Nov 25 21:56:50 MegaHub usbhid-ups[18724]: nut_libusb_get_string: Input/Output Error

Nov 25 21:56:50 MegaHub usbhid-ups[18724]: nut_libusb_get_string: Pipe error

Nov 25 21:56:50 MegaHub usbhid-ups[18724]: nut_libusb_get_report: Input/Output Error

 

 

I finally went out and bought a new USB cable because I was mostly confident that was the issue.

 

It apparently was not. 

 

My configuration editor contains this (last time I tried to fix it I adjusted this):

 

driver = usbhid-ups
port = auto
pollonly

 

Do you happen to have any other recommendations?

 

Realistically, it seems to work as intended minus randomly giving a bunch of those errors, so I'm not extraordinarily concerned, but still would like to fix it if I could

On 11/26/2024 at 12:00 AM, PartyingChair said:

I've been getting these errors since I started using NUT:

 

Nov 25 21:56:50 MegaHub usbhid-ups[18724]: nut_libusb_get_string: Input/Output Error

Nov 25 21:56:50 MegaHub usbhid-ups[18724]: nut_libusb_get_string: Pipe error

Nov 25 21:56:50 MegaHub usbhid-ups[18724]: nut_libusb_get_report: Input/Output Error

 

 

I finally went out and bought a new USB cable because I was mostly confident that was the issue.

 

It apparently was not. 

 

My configuration editor contains this (last time I tried to fix it I adjusted this):

 

driver = usbhid-ups
port = auto
pollonly

 

Do you happen to have any other recommendations?

 

Realistically, it seems to work as intended minus randomly giving a bunch of those errors, so I'm not extraordinarily concerned, but still would like to fix it if I could

I get the same errors with a CyberPower CP1500AVRLCD3. I've tried forcing the ports to USB2, switching ports, setting kernel boot flags, using both chatgpt and claude 3.5 sonnet. Nothing can seem to stop them.

On 11/24/2024 at 11:05 PM, jholman76 said:

 

Attaching my debug logs, if you have a moment to look. The UNRAID syslog is just that above error over and over, but it seems like the UPS is working fine. It shows footer information and the UPS being online, etc. 

 

I had it in bypass mode for a while and changed it to not be. I'm not 100% sure what this brand of UPS wants to be in as the NUT plugin shows green when not in bypass, but the UPS GUI shows a warning... when I go on bypass, they are opposite. UNRAID shows the yellow/amber warning and the UPS shows all green. go figure. 

 

nut-debug-20241124160132.zip 180.88 kB · 0 downloads nut-ups.dev 1.37 kB · 0 downloads

 

On 11/25/2024 at 3:02 AM, bozzio said:

I'm getting this error randomly and can't figure out what's wrong.

```

zeus usbhid-ups[1012]: nut_libusb_get_string: Pipe error

```

nut-debug-20241124205841.zip 223.11 kB · 0 downloads

 

On 11/26/2024 at 6:00 AM, PartyingChair said:

I've been getting these errors since I started using NUT:

 

Nov 25 21:56:50 MegaHub usbhid-ups[18724]: nut_libusb_get_string: Input/Output Error

Nov 25 21:56:50 MegaHub usbhid-ups[18724]: nut_libusb_get_string: Pipe error

Nov 25 21:56:50 MegaHub usbhid-ups[18724]: nut_libusb_get_report: Input/Output Error

 

 

I finally went out and bought a new USB cable because I was mostly confident that was the issue.

 

It apparently was not. 

 

My configuration editor contains this (last time I tried to fix it I adjusted this):

 

driver = usbhid-ups
port = auto
pollonly

 

Do you happen to have any other recommendations?

 

Realistically, it seems to work as intended minus randomly giving a bunch of those errors, so I'm not extraordinarily concerned, but still would like to fix it if I could

 

3 hours ago, robbiered said:

I get the same errors with a CyberPower CP1500AVRLCD3. I've tried forcing the ports to USB2, switching ports, setting kernel boot flags, using both chatgpt and claude 3.5 sonnet. Nothing can seem to stop them.

 

Sorry for the late replies, I've been a bit tied up with real life. If the UPS are working fine aside from the log spamming, I suggest using the "Enable Rule-Based Syslog Filters" setting in "NUT Settings" to define which messages need filtering out. There's no other way around this, as these connection instabilities usually stem not from NUT itself, but a combination of factors of hardware and OS/kernel-side USB implementation.

 

Users suffering from the I/O and pipe-related errors can add to their xnut-nospam.conf (in GUI configuration editor):

:msg, regex, "nut_libusb.*rror" -/var/log/nut-spam
:msg, regex, "nut_libusb.*rror" stop

 

Users suffering from the SNMP type errors can add to their xnut-nospam.conf (in GUI configuration editor):

:msg, regex, "type error.*OID" -/var/log/nut-spam
:msg, regex, "type error.*OID" stop

 

Afterwards, make sure to "Restart NUT" to have these changes applied to your SYSLOG configuration.

 

5 hours ago, Rysz said:

 

 

 

 

Sorry for the late replies, I've been a bit tied up with real life. If the UPS are working fine aside from the log spamming, I suggest using the "Enable Rule-Based Syslog Filters" setting in "NUT Settings" to define which messages need filtering out. There's no other way around this, as these connection instabilities usually stem not from NUT itself, but a combination of factors of hardware and OS/kernel-side USB implementation.

 

Users suffering from the I/O and pipe-related errors can add to their xnut-nospam.conf (in GUI configuration editor):

:msg, regex, "nut_libusb.*rror" -/var/log/nut-spam
:msg, regex, "nut_libusb.*rror" stop

 

Users suffering from the SNMP type errors can add to their xnut-nospam.conf (in GUI configuration editor):

:msg, regex, "type error.*OID" -/var/log/nut-spam
:msg, regex, "type error.*OID" stop

 

Afterwards, make sure to "Restart NUT" to have these changes applied to your SYSLOG configuration.

 

Thanks!