Tearing my hair out w NUT server on RPi - APC CS650/HA integration

Not technically a HA question quite YET, but Im WASTING so much time configuring a NUT server on a RPi connected to a APC CS650 UPS (I need to remotely control the UPS away from my HA instance) but will be integrated into HA once I gat the NUT server working (was the original end goal)

Ive gone thru all the NUT configs I can find on the web, as well as Techno Tims YT video (like 10x) and have followed meticulously everything I can absorb and yet I cannot get the NUT server to connect to my UPS (even tho the pi can see it and reports the right values)

All the CLI responses suggest that the driver is not connected or No matching HID UPS found. I can only guess that theres a part of Debian Bullseye that doesnt allow me to get thru the USB port without modified permissions to the USB port???. Any ideas would be really appreciated because Ive wasted 3 days screwing around with this.

heres my configs:

nut.conf

MODE=netserver

ups.conf

[ups]
        driver = "usbhid-ups"
        port = "auto"
        vendorid = "051d"
        productid = "0002"
        product = "Back-UPS"
       bus = "001"

upsd.conf

LISTEN 192.168.1.22 3493
LISTEN 127.0.0.1 3493

upsd.users

[upsmaster]
        password = apassword
     	admin master

upsmon.conf

RUN_AS_USER root
MONITOR ups@localhost 1 admin apassword master

Outputs are as follows:

The Nut Server says that the usbhid-usb generic driver is the correct one - plus what is being reported back from the CLI

nut-scanner shows:

[nutdev1]
        driver = "usbhid-ups"
        port = "auto"
        vendorid = "051D"
        productid = "0002"
        bus = "001"

upscmd -l ups

Error: Driver not connected

upsc upsc@localhost

error: driver not connected

journalctl -xe

admin@nutserver:/ $ journalctl -xe
A start job for unit nut-server.service has finished successfully.
The job identifier is 1233.
Nov 06 12:29:15 nutserver sudo[2159]: pam_unix(sudo:session): session closed fo>
Nov 06 12:29:17 nutserver upsmon[529]: Poll UPS [ups@localhost] failed - Write >
Nov 06 12:29:22 nutserver upsmon[529]: Login on UPS [ups@localhost] failed - go>
Nov 06 12:29:26 nutserver sudo[2169]:    admin : TTY=pts/0 ; PWD=/ ; USER=root >
Nov 06 12:29:26 nutserver sudo[2169]: pam_unix(sudo:session): session opened fo>
Nov 06 12:29:26 nutserver systemd[1]: Starting Network UPS Tools - power device>
Subject: A start job for unit nut-driver.service has begun execution
Defined-By: systemd
Support: https://www.debian.org/support
A start job for unit nut-driver.service has begun execution.

The job identifier is 1303.
Nov 06 12:29:26 nutserver upsdrvctl[2173]: Network UPS Tools - Generic HID driv>
Nov 06 12:29:26 nutserver upsdrvctl[2173]: USB communication driver 0.33
Nov 06 12:29:26 nutserver upsdrvctl[2173]: No matching HID UPS found
Nov 06 12:29:26 nutserver upsdrvctl[2172]: Driver failed to start (exit status=>
Nov 06 12:29:26 nutserver upsdrvctl[2172]: Network UPS Tools - UPS driver contr>
Nov 06 12:29:26 nutserver systemd[1]: nut-driver.service: Control process exite>
Subject: Unit process exited
Defined-By: systemd
Support: https://www.debian.org/support

An ExecStart= process belonging to unit nut-driver.service has exited.

The process' exit code is 'exited' and its exit status is 1.
Nov 06 12:29:26 nutserver systemd[1]: nut-driver.service: Failed with result 'e>``1

and using

sudo service nut-server status

admin@nutserver:~ $ sudo service nut-server status
● nut-server.service - Network UPS Tools - power devices information server
     Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2022-11-06 12:56:18 +08; 14min ago
    Process: 531 ExecStart=/sbin/upsd (code=exited, status=0/SUCCESS)
   Main PID: 537 (upsd)
      Tasks: 1 (limit: 1596)
        CPU: 195ms
     CGroup: /system.slice/nut-server.service
             └─537 /lib/nut/upsd

Nov 06 12:56:18 nutserver upsd[531]: not listening on 10.27.27.47 port 3493
Nov 06 12:56:18 nutserver upsd[531]: listening on 0.0.0.0 port 3493
Nov 06 12:56:18 nutserver upsd[531]: not listening on 127.0.0.1 port 3493
Nov 06 12:56:18 nutserver upsd[531]: Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 06 12:56:18 nutserver upsd[531]: not listening on 10.27.27.47 port 3493
Nov 06 12:56:18 nutserver upsd[531]: Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 06 12:56:18 nutserver upsd[537]: Startup successful
Nov 06 12:56:18 nutserver systemd[1]: Started Network UPS Tools - power devices information server.
Nov 06 13:01:19 nutserver upsd[537]: Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 06 13:06:19 nutserver upsd[537]: Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory

Anything that anyone can suggest would be muchly appreciated.

SOLVED:

To anyone who is attempting this on a RPi - DO NOT USE ANY OTHER VERSION OTHER THAN BUSTER - it will not work

I used this guide to initially get things up and working

at this point (Nov 2022) newer versions of debian dont work

2 Likes

I know the post is very old, but I am having some problems similar to yours with a SALICRU HOME 650w, it is not recognized by the system and I cannot use it with NUT, any solution at this point and with current versions of Raspbian.

I have another salicru, in this case a 700w ONE that the system recognizes without problems.

Thanks for the help