Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tripp Lite SMART1500RM2UL Support #2755

Open
scuppasteve opened this issue Jan 5, 2025 · 1 comment
Open

Tripp Lite SMART1500RM2UL Support #2755

scuppasteve opened this issue Jan 5, 2025 · 1 comment

Comments

@scuppasteve
Copy link


I am getting the error below when i try to startup nut.

TrippLite device (09ae:3018) is not (or perhaps not yet) supported

and it just spams the log with, any idea what i am doing wrong? Is it just about the device being different and not supported? Surprised its that different from all the other TRIPP LITE SMART1500's.

Jan  4 22:13:34 MovieServer kernel: hid-generic 0003:09AE:3018.0C45: hiddev97,hidraw1: USB HID v1.10 Device [Tripp Lite  TRIPP LITE SMART1500RM2UL ] on usb-0000:00:14.0-11.2/input0
Jan  4 22:13:49 MovieServer kernel: usb 1-11.2: USB disconnect, device number 95
Jan  4 22:13:49 MovieServer kernel: usb 1-11.2: new low-speed USB device number 96 using xhci_hcd
Jan  4 22:13:50 MovieServer kernel: hid-generic 0003:09AE:3018.0C46: hiddev97,hidraw1: USB HID v1.10 Device [Tripp Lite  TRIPP LITE SMART1500RM2UL ] on usb-0000:00:14.0-11.2/input0
Jan  4 22:14:04 MovieServer kernel: usb 1-11.2: USB disconnect, device number 96
Jan  4 22:14:04 MovieServer kernel: usb 1-11.2: new low-speed USB device number 97 using xhci_hcd
Jan  4 22:14:04 MovieServer kernel: hid-generic 0003:09AE:3018.0C47: hiddev97,hidraw1: USB HID v1.10 Device [Tripp Lite  TRIPP LITE SMART1500RM2UL ] on usb-0000:00:14.0-11.2/input0
Jan  4 22:14:19 MovieServer kernel: usb 1-11.2: USB disconnect, device number 97

@clepple
Copy link
Member

clepple commented Jan 7, 2025

Not terribly surprising; Tripp Lite has already used the SMART1500 name for two completely different protocol families (USB PID 0001 and more-or-less standard USB HID PDC.

You should be able to get further by specifying productid = 3018 in ups.conf - the driver normally doesn't need the PID for known models, but this is a sign that nobody has tested for any quirks in the protocol.

Also, do those disconnection times correspond to when you unplugged the USB cable? If not, you may be in for some amount of annoyance. The 3016 protocol UPSes were similar - they did not work well with modern USB controllers (even though they only use USB 1.1 low-speed) and would fall off of the bus when least convenient. I offloaded my 3016 UPS to someone who just needed battery backup, and didn't need monitoring support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants