[Nut-upsuser] Old thread on belkin

[Charles Lepple]

On Dec 27, 2009, at 9:49 AM, Gene Heskett wrote:

> Greetings all;
>
> Back to a thread I started back in May of 2008 I think.  I never did  
> get this
> belkin and nut to talking, so I thought I'd make another run at it.
>
> Trying to run the driver as the user gene, I'm getting this:
> ---------------------------
> [root at coyote ups]# su gene -c "/sbin/belkin -D -a myups"
> Network UPS Tools - Belkin Smart protocol driver 0.21 (2.2.2)
> debug level is '1'
>
> Unable to open /dev/hidraw0: Permission denied

Hey Gene,

At the moment (this applies to both 2.2.2 and 2.4.1), none of our  
drivers will use /dev/hidraw* devices. Serial port drivers use /dev/ 
ttyS* and /dev/ttyUSB*, and the USB drivers use a matching scheme  
based on vendor and product IDs.

> /dev/hidraw0 was _not_ created during boot time discovery, and was  
> only
> created when I momentarily unplugged the data cable, which when I  
> plugged it
> back in, which returned this in the messages log:

Not sure why it didn't appear at boot time, but since our drivers  
don't use that interface, it is soon to become a moot point. One of  
the side effects of the usbhid-ups driver is that it will tell the  
kernel HID driver to release the /dev/hid* device when it connects, so  
that /dev entry will disappear.

> -----------------------------
> Dec 27 08:52:39 coyote kernel: [77690.153405] usb 1-10.1: new low  
> speed USB
> device using ehci_hcd and address 16
> Dec 27 08:52:39 coyote kernel: [77690.368022] usb 1-10.1: New USB  
> device
> found, idVendor=050d, idProduct=0751

Looking in the Hardware Compatibility List under Belkin, we can see  
that a number of devices mention Vendor ID 050d:

http://new.networkupstools.org/stable-hcl.html

They are all listed next to the "usbhid-ups" driver.

You should be able to run with the following entry in ups.conf:

[myups]
	driver = usbhid-ups
	port = auto
	vendorid = 050d

If not, please send us the error you get when starting the driver, and  
remind us which distribution of Linux you are running.

> The user & passwd in the .conf files is me, not root.

We're starting to make a bigger distinction in the documentation, but  
there are two types of "users" in NUT configuration files: system  
(login) usernames, which tell NUT which non-root user to run as, and  
upsd user/password pairs, which do not have to match any other login  
name (they are used to prevent a random network user from logging in  
and shutting down a system).

You never have to put a system login password into a configuration  
file - the startup scripts run as root, so they can change to the non- 
root user without a password.

- Charles