<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On Oct 9, 2020, at 8:07 PM, Rusty Bower wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hey all,<div class=""><br class=""></div><div class="">I've read through as many relevant mailing list posts and public blog posts as I could, but I can't seem to find an answer to my issue.</div><div class=""><br class=""></div><div class="">I currently have 2x Tripp Lite SMART1500LCDXLs, and I am attempting to monitor both of them with the same Raspberry Pi using NUT. The problem I have is there doesn't seem to be any way in the nut.conf to differentiate between the two UPS via USB other than Vendor/Product/Serial. Unfortunately, I cannot leverage Vendor/Product filtering, because they are the exact same model, and the serial number is returning "unknown"</div></div></div></blockquote><div><br class=""></div>The unknown serial number does seem to be the case for other 2012 protocol models, yes.</div><div><br class=""></div><div>(I'm 99% certain this isn't going to yield different results in your case, but if you ever want to rule out NUT as part of the problem in retrieving the serial number, you can run "lsusb -vvv" as root, or check dmesg/journalctl to see if other parts of the system were able to retrieve a serial number.)</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">Does anyone know how to get these Tripp Lite models to return an actual serial number? Or is there a way to differentiate between the two devices on the same USB bus?</div></div></div></blockquote><div><br class=""></div>I forget if adding a USB hub ends up creating a second logical bus as far as the kernel is concerned, but if you have a spare hub on hand, it's an easy thing to try.</div><div><br class=""></div><div>It is possible that a future version of NUT could use the kernel's USB topology information: <a href="http://libusb.sourceforge.net/api-1.0/group__libusb__dev.html#ga14879a0ea7daccdcddb68852d86c00c4" class="">http://libusb.sourceforge.net/api-1.0/group__libusb__dev.html#ga14879a0ea7daccdcddb68852d86c00c4</a></div><div><br class=""></div><div>but we are still working out issues in the libusb-0.1/1.0 transition: <a href="https://github.com/networkupstools/nut/issues/300" class="">https://github.com/networkupstools/nut/issues/300</a></div><div><br class=""></div><div>If it were me, I'd probably just find a spare Raspberry Pi and have a 1:1 UPS-to-Pi mapping, just to hedge against the Pi and its power supply being a single point of failure in the monitoring system.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">Raspbian GNU/Linux 10</div><div class="">Nut Version 2.7.4-8</div></div></div></blockquote><div><br class=""></div>Thanks for the NUT and OS version info!<br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class=""> 0.056938 Checking device (09AE/2012) (001/113)<br class=""> 0.062961 - VendorID: 09ae<br class=""> 0.063011 - ProductID: 2012<br class=""> 0.063055 - Manufacturer: Tripp Lite<br class=""> 0.063094 - Product: Tripp Lite UPS<br class=""> 0.063136 - Serial Number: unknown<br class=""> 0.063189 - Bus: 001<br class=""> 0.063259 - Device release number: 0009<br class=""></div><div class=""><br class=""></div><div class="">Rusty</div></div>
_______________________________________________<br class="">Nut-upsuser mailing list<br class=""><a href="mailto:Nut-upsuser@alioth-lists.debian.net" class="">Nut-upsuser@alioth-lists.debian.net</a><br class="">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</div></blockquote></div><br class=""></body></html>