Did that (with 2.0.2) - got the newhidups driver to come up, but it had no
APC recognition of anything, it saw the UPS but upsc did not report any
status, just vendor, serial, description.
Then I tried the latest 2.0.3 on the site, had to add the libusb path for
newhidups to build (a clue I was on the same version as you were), and put
that in. However now, without any change to the config files that worked
for 2.0.2, it does not find the UPS at all.
Now it says:
# /usr/local/ups/bin/upsdrvctl start
Network UPS Tools - UPS driver controller 2.0.3-pre2
Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3-pre2)
No matching USB/HID UPS found
Driver failed to start (exit status=1)
#
Any idea how to get it going from here? As I said the config files are
untouched from what worked to get it to at least upsc seeing it in 2.0.2.
Peter Selinger writes:
Ted Bardusch wrote:
OK, I've installed libusb and gd (for the cgi stuff). I have the UPS
connected, and built NUT with newhidups. but now I need to know what
to set the ups.conf port to. Any ideas on that?
Please see the newhidups(8) man page, section IMPLEMENTATION.
IMPLEMENTATION
The driver ignores the "port" value in ups.conf. Unlike previous ver-
sions of this driver, it is now possible to control multiple UPS units
simultaneously with this driver. They can be distinguished by setting
some combination of the "vendor", "product", "serial", "vendorid", and
"productid" options. For instance:
[mge]
driver = newhidups
port = auto
vendorid = 0463
[tripplite]
driver = newhidups
port = auto
vendorid = 09ae
Arnaud: this is now a frequenly asked question. Should we add the info
on the newhidups "port" value to INSTALL, section 7?
Greetings to all from Hanoi (Vietnam). -- Peter
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
