tripplite_usb -a UPS_NAME [OPTIONS]
This driver should work with older Tripp Lite UPSes which are detected as USB HID-class devices, but are not true HID Power-Device Class devices. So far, the devices supported by tripplite_usb have product ID 0001, and the newer units (such as those with "LCD" in the model name) with product ID 2001 require the usbhid-ups(8) driver instead. Please report success or failure to the nut-upsuser mailing list. A key piece of information is the protocol number, returned in ups.debug.0. Also, be sure to turn on debugging (-DDD) for more informative log messages. If your Tripp Lite UPS uses a serial port, you may wish to investigate the tripplite(8) or tripplite_su(8) driver.
This driver has been tested with the following models:
If you have used Tripp Lite's PowerAlert software to connect to your UPS, there is a good chance that tripplite_usb will work if it uses one of the following protocols:
On the other hand, if the web page for your UPS on the Tripp-Lite website says "HID-compliant USB port also enables direct integration with built-in power management and auto-shutdown features of Windows and MAC OS X", then you should use the usbhid-ups(8) driver instead.
This driver supports the following optional settings in the ups.conf(5) file (or with -x on the command line):
This regex is matched against the full USB product string as seen in lsusb(8). The ups.model in the upsc(1) output only lists the name after TRIPP LITE, so to match a SMART2200RMXL2U, you could use the regex .*SMART2200.*.
For more information on regular expressions, see regex(7)
The driver was not developed with any official documentation from Tripp Lite, so certain events may confuse the driver. If you observe any strange behavior, please re-run the driver with -DDD to increase the verbosity.
So far, the Tripp Lite UPSes do not seem to have a serial number or other globally unique identifier accessible through USB. Thus, when monitoring several Tripp Lite USB UPSes, you should use either the bus or product configuration options to uniquely specify which UPS a given driver instance should control.
For instance, you can easily monitor an OMNIVS1000 and a SMART1500RM2U at the same time, since they have different USB Product ID strings. If you have two SMART1500RM2U units, you would have to find which USB bus number each unit is on (via lsusb(8)), which may result in ambiguities if the available USB ports are on the same bus.
Some of the SMART*2U models have an ID number, but because this ID is not exposed as a USB string descriptor, there is no easy way to use this ID to distinguish between multiple UPS units on a single machine. The UPS would need to be claimed by the driver in order to read this ID.
Written by Charles Lepple, based on the tripplite(8) driver by Rickard E. (Rik) Faith and Nicholas Kain. Please do not email the authors directly - use the nut-upsdev mailing list.
A Tripp Lite OMNIVS1000 was graciously donated to the NUT project by Bradley Feldman (http://www.bradleyloritheo.com)
tripplite(8), tripplitesu(8), usbhid-ups(8)
The NUT (Network UPS Tools) home page: http://www.networkupstools.org/