Assistance in Communicating UPS NHS Prime Sinusoidal

TrueNAS General
1

I’m having trouble with this NHS UPS; I’ve already tested all the generic drivers, and only one seems to work, but it doesn’t read correctly.

Driver: Various ups 1 (various) Generic RUPS 2000 (Megatec M2501 cable) (genericups)
UPS: NHS Prime Senoidal

root@truenas[~]# upsc “NHS_Prime_Senoidal_3200VA@localhost”

Init SSL without certificate database

device.mfr: Generic

device.model: Generic RUPS 2000

device.type: ups

driver.name: genericups

driver.parameter.pollinterval: 2

driver.parameter.port: /dev/ttyACM0

driver.parameter.synchronous: auto

driver.parameter.upstype: 21

driver.version: 2.8.0

driver.version.internal: 1.38

ups.mfr: Generic

ups.model: Generic RUPS 2000

ups.status: LB OL

root@truenas[~]# upsc “NHS_Prime_Senoidal_3200VA@localhost”

Init SSL without certificate database

device.mfr: Generic

device.model: Generic RUPS 2000

device.type: ups

driver.name: genericups

driver.parameter.pollinterval: 2

driver.parameter.port: /dev/ttyACM0

driver.parameter.synchronous: auto

driver.parameter.upstype: 21

driver.version: 2.8.0

driver.version.internal: 1.38

ups.mfr: Generic

ups.model: Generic RUPS 2000

ups.status: LB OL

The battery is full, and I unplugged it.
It doesn’t update via USB.

Message on the manufacturer’s website:

Note: For the Linux operating system and its derivatives, the driver is already included in the kernel through the cdc_acm driver class.

2

Die you check from shell with nut-scanner -U which driver the ups expect?

3

root@truenas[~]# nut-scanner -U
Scanning USB bus.
root@truenas[~]#

It stayed like this

4

That’s not good… it should look like this

lars@truenas[~]# nut-scanner -U
Scanning USB bus.
[nutdev1]
        driver = "usbhid-ups"
        port = "auto"
        vendorid = "0764"
        productid = "0601"
        product = "2200R"
        serial = "000000000000"
        vendor = "1"
        bus = "005"
lars@truenas[~]#

It may be that your ups is not fully supported by the nut version truenas uses and you may have to wait for a truenas update that also updates the nut version.

5

Tense….
Welcome to TrueNAS
Last login: Fri Jan 23 08:18:35 -03 2026 on pts/50
root@truenas[~]# nut-scanner
Scanning USB bus.
No start IP, skipping SNMP
No start IP, skipping NUT bus (old connect method)
Scanning NUT bus (avahi method).
Scanning IPMI bus.
root@truenas[~]# nut-scanner -U
Scanning USB bus.
root@truenas[~]#

He can’t see the UPS, from what I’ve researched it must be because he’s using a USB serial card.
Is it not possible to install that Linux driver that the manufacturer claims is compatible?

Note: For the Linux operating system and its derivatives, the driver is already included in the kernel through the cdc_acm driver class.

6

It’s not officially supported or recommended to install any additional packages on truenas.
However, if you know the risks you can enable the developer mode and install them.
You will have to re-install them after every truenas update because they get wiped during the update.
As always the warning: If you enable developer mode you’re in unsupported territory, so “here be dragons”

7

Another approach is not to use TrueNAS to manage the UPS. I have a whole bunch of servers (a Proxmox cluster) hanging off my UPS in addition to the NAS. I found a Raspberry Pi to be a better solution. The UPS talks to the Pi which manages shutting down both Proxmox and the NAS in an orderly manner once the power has been gone for more than three minutes. No problems with getting the very latest NUT if you do it that way.

8

I’ll try that Raspberry Pi solution.