search for: sweex2

...anks for your hint. sudo lsusb -v gives the correct output on virtual server too. Now, one UPS gives iProduct 2 USB to Serial iSerial 3 20100813 while the other iProduct 2 USB to Serial iSerial 0 So I modified ups.conf like this: [sweex2] driver = blazer_usb port = auto runtimecal = 1100,100,2200,50 bus = 002 serial = "20100813" [sweex3] driver = blazer_usb port = auto runtimecal = 1100,100,2200,50 bus = 002 serial = "" If I run (as root) blazer_usb -a sweex2 it works. I get th...

On Thu, Aug 14, 2014 at 3:55 AM, Marcello Vezzelli <m.vezzelli at e-works.it> wrote: > I've found another strange issue that prevented me to test this solution. > VMware ESXi is filtering out serial number information, together with > iManufacturer and iProduct. Is it a permissions issue? The NUT udev configuration file changes the ownership and permissions to allow the NUT

On 13/08/2014 16:27, Charles Lepple wrote: >> The blew one had the serial number, so I'm left with two different UPSes >> from the serial number point of view. >> I wonder if an empty serial number is a valid serial number! > I haven't tried it, but an empty string (that is, iSerial is not zero, > but the string has length zero) should match the regex "".

...one virtual USB controller. Unluckily, "serial" field is empty so I cannot use this to detect single UPS. This is my current configuration, but of course only one UPS is detected and running. [sweex1] driver = blazer_usb port = auto runtimecal = 1100,100,2200,50 bus = 002 [sweex2] driver = blazer_usb port = auto runtimecal = 1100,100,2200,50 bus = 002 [sweex3] driver = blazer_usb port = auto runtimecal = 1100,100,2200,50 bus = 002 It would be great if I could specify Device #id (taken from lsusb) in ups.conf file for each UPS. This way I can ident...