Jim Klimov
2023-Feb-20 12:43 UTC
[Nut-upsuser] Issue with two UPS APC managed from a single PC.
Is that with both UPSes on same machine? A quick guess would be that insufficient data points to identify the device are configured (vendorid, productid, serial...) in ups.conf, so both drivers connect to the first match. I'd expect them to conflict and one would die or both loop reconnecting, if both are running at once, though. Also, which NUT version? Custom build from GitHub or an (older?) distro package? Jim On Mon, Feb 20, 2023, 12:28 Manuel Wolfshant via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote:> > > On February 20, 2023 12:01:46 PM GMT+02:00, Laurent Taieb via Nut-upsuser < > nut-upsuser at alioth-lists.debian.net> wrote: > >Hi mailing list, > >I looked at all FAQ and docs and can?t find a solution. > >I installed but on both Kali Linux and Ubuntu. > >(For comparison purposes) > >I?m trying to connect and monitor two UPS APC via usb. > >One is a back-ups bx1400 which I can see via via upsc. > >The second one is a more recent one smc 1500ic which when I poke it via > upsc returns the data of the bx1400 one. > >I tried by changing port and other tricks but no success. > >Would anyone have a clue of what the issue could be ? > > Hello > > Can you please share the configuration you have used, as well as the > output of lsusb ? > > wolfy > > > >Thanks > > > >Laurent > >_______________________________________________ > >Nut-upsuser mailing list > >Nut-upsuser at alioth-lists.debian.net > >https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20230220/8b190370/attachment.htm>
Laurent Taieb
2023-Feb-24 22:17 UTC
[Nut-upsuser] Issue with two UPS APC managed from a single PC.
Hi Jim, Yes both UPS are on the same machine. I moved away from Ubuntu and ?tried with Kali and got a slightly different issue as the driver even doesn?t start properly. I used the standard apt-get command to download nut and added libusb-dev which wasn?t by default on kali. I went to Kali nut web page and downloaded all packages ? hiddev0 and hiddev1 have been created in /dev/usb and changed the group to nut as they?ve been created with root group. I have attached the lsusb traces for the 2 UPS When starting the driver I got this message $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.8.0 Network UPS Tools - Generic HID driver 0.47 (2.8.0) USB communication driver (libusb 1.0) 0.43 interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of this message) libusb1: Could not open any HID devices: insufficient permissions on everything No matching HID UPS found Driver failed to start (exit status=1) Thanks for your help and guidance. Laurent De : Jim Klimov <jimklimov+nut at gmail.com> Date : lundi 20 f?vrier 2023 ? 13:43 ? : nut-upsuser Mailing List <nut-upsuser at lists.alioth.debian.org> Cc : "laurenttaieb at free.fr" <laurenttaieb at free.fr> Objet : Re: [Nut-upsuser] Issue with two UPS APC managed from a single PC. Is that with both UPSes on same machine? A quick guess would be that insufficient data points to identify the device are configured (vendorid, productid, serial...) in ups.conf, so both drivers connect to the first match. I'd expect them to conflict and one would die or both loop reconnecting, if both are running at once, though. Also, which NUT version? Custom build from GitHub or an (older?) distro package? Jim On Mon, Feb 20, 2023, 12:28 Manuel Wolfshant via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: On February 20, 2023 12:01:46 PM GMT+02:00, Laurent Taieb via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote:>Hi mailing list, >I looked at all FAQ and docs and can?t find a solution. >I installed but on both Kali Linux and Ubuntu. >(For comparison purposes) >I?m trying to connect and monitor two UPS APC via usb. >One is a back-ups bx1400 which I can see via via upsc. >The second one is a more recent one smc 1500ic which when I poke it via upsc returns the data of the bx1400 one. >I tried by changing port and other tricks but no success. >Would anyone have a clue of what the issue could be ?Hello Can you please share the configuration you have used, as well as the output of lsusb ? wolfy>Thanks > >Laurent >_______________________________________________ >Nut-upsuser mailing list >Nut-upsuser at alioth-lists.debian.net >https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser_______________________________________________ Nut-upsuser mailing list Nut-upsuser at alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20230224/c10a0bb0/attachment.htm> -------------- next part -------------- Bus 002 Device 005: ID 051d:0003 American Power Conversion UPS Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x051d American Power Conversion idProduct 0x0003 UPS bcdDevice 0.01 iManufacturer 1 American Power Conversion iProduct 2 Smart-UPS_1500 FW:UPS 04.6 / ID=1018 iSerial 3 AS2212262511 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0029 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 10mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 33 US bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 452 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 10 ------------ Bus 002 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x051d American Power Conversion idProduct 0x0002 Uninterruptible Power Supply bcdDevice 1.06 iManufacturer 3 American Power Conversion iProduct 1 Back-UPS XS 1400U FW:926.T2 .I USB FW:T2 iSerial 2 4B1835P44428 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0022 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 24mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 33 US bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 1028 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0006 1x 6 bytes bInterval 10