similar to: No matching HID UPS found

Changed the driver as you suggest ... # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Generic Q* USB/Serial driver 0.06 (2.7.2) USB communication driver 0.32 Using protocol: Q1 0.02 Can't autodetect number of battery packs [-1/13.50] Battery runtime will not be calculated (runtimecal not set) ... looks like it's connected to something, although maybe

Thanks for the response. No /dev/ttyUSB0. /dev/tty and /dev/tty1 ... /dev/tty63 /dev/ttyS0 ... /dev/ttyS3 but no /dev/ttyUSB0 How can I get one? Just make one? All the rest are 4,0-67 plus one 5,0 What ought the major number be? On 2016-10-20 07:33, Charles Lepple wrote: > [please use reply-all to include the list - the headers are not > mangled] > >> On Oct 18, 2016, at

Hello, I am trying to make my UPS system working with NUT but with no success. I got "No supported UPS detected" message. I use the blazer_usb driver since it was proposed to me by the web site. My NUT version is : 2.7.1 (installed from standard RPM), release 2.41 The UPS identification: INFOSEC X4 RM PLUS linux-2qya:~ # /usr/lib/ups/driver/blazer_usb -a infosec Network UPS Tools -

Ok - before stale data: After stale data: $ lsusb -d 0665: Bus 002 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial After stale data: And the gzipped log attached: On 2 January 2015 at 21:56, Charles Lepple <clepple at gmail.com> wrote: > On Jan 2, 2015, at 2:43 PM, Mike Raath <raathm at gmail.com> wrote: > > Not sure what other logs I can provide to try

Sorry, I messed up my reply a bit. The output of the lsusb command is the same before and after the data goes stale. $ lsusb -d 0665: Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial And the output of the /lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 command is the same as in the previous attachment. I truncated the "before" log because it just carried on with

Hello, Replaced UPS Kstar Micropower Micro 1200 (managed via blazer_usb) with https://www.njoy.ro/UPS/horus-plus-2000. The latter doesn't seem to be supported. 1. I tried blazer_usb and usbhid-ups. Any other suggestions? 2. What would be needed to get it supported by NUT? ======== HW ======== HP Microserver Gen 8 ======== UPS ======== Working:Kstar Micropower Micro

Hi Having followed this guide: http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/and seeing support for Apollo UPSes mentioned on the compatibility list (genericups, type=4) I tried to set up Nut as follows. OS: Ubuntu Server 12.04 Nut: 2.6.3 (I believe - from Ubuntu repos) ups.conf: > [apollo] > driver = genericups > upstype = 4 > port = /dev/ttyUSB0

> On Oct 20, 2016, at 8:25 AM, jfmxl at sdf.org wrote: > > Using protocol: Q1 0.02 > Can't autodetect number of battery packs [-1/13.50] > Battery runtime will not be calculated (runtimecal not set) > > ... looks like it's connected to something, although maybe the driver is not quite right? That looks reasonable. Not all UPSes provide enough information to

[please use reply-all to include the list - the headers are not mangled] > On Oct 18, 2016, at 9:02 PM, jfmxl at sdf.org wrote: > > So, apparently, my Eaton is sending > > Bus 002 Device 010: ID 0665:5161 Cypress Semiconductor USB to Serial Do you get a device named "/dev/ttyUSB0" when you plug in the UPS? We do have an entry for 0665:5161 in the nutdrv_qx driver (and

> Hello everyone. I try to connect four PowerMust 2000 ups's via usb to one > computer using megatec_usb driver. But megatec_usb completly ignores port > directive in ups.conf, I even try port = /dev/null and megatec_usb founds > ups and it works. The 'port' is not used for USB connected devices, it's only needed for compatibility reasons. > Problem is that

On Jan 2, 2015, at 3:33 PM, Mike Raath <raathm at gmail.com> wrote: > Sorry, I messed up my reply a bit. > > The output of the lsusb command is the same before and after the data goes stale. > > $ lsusb -d 0665: > Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial > OK. That usually means that the VM kernel doesn't see that the device is

hi, i own a aeg protect home (think it is a 600 VA) which has a serial and an usb port. using this hack in ups.conf: [bestupsname] driver = bestups port = /dev/ttyUSB0 ID = FOR,750,230,230,11.0,13.5 desc = "home-server" i start the driver with: ./bestups -a bestupsname -D -q and after adding some debugging it seems to work (not yet in

Hi Sergey, 2011/7/15 Sergey Talchuk <tals1975 at gmail.com> > Hi Arnaud, > > both configurations are ok :). Please find the file attached. > logic since the 2nd is automatically guessed from the first using USB Vendor and Product ID ;-) can you please send in upsc, upscmd and upsrw output. and also report the shutdown testing as described here:

A fragment of dmesg output (here idVendor=0665, idProduct=5161 is the UPS; the webcam is idVendor=17a1, idProduct=0128): [ 1.317085] usb 4-1: new high-speed USB device number 2 using ehci-pci [ 1.405223] tsc: Refined TSC clocksource calibration: 3395.557 MHz [ 1.405228] Switching to clocksource tsc [ 1.449642] usb 4-1: New USB device found, idVendor=8087, idProduct=0024 [ 1.449648]

Well, also below in dmesg: [ 190.249219] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 26.11.2014, 03:05, "Victor Porton" <porton at narod.ru>: > A fragment of dmesg output (here idVendor=0665, idProduct=5161 is the UPS; the webcam is idVendor=17a1, idProduct=0128): > > [ ???1.317085] usb 4-1: new high-speed USB device number 2

Hi Thank you very much for the feedback. I will download and try to get it working on the Raspberry Pi. Regards Tom On Sun, Feb 14, 2016 at 1:49 AM, hyouko at gmail.com <hyouko at gmail.com> wrote: > > I have the RCT 3KVA Axpert solar hybrid inverter. It is also known as > the > > MPP Solar PIP-MS series, the IPS-4000WM and the Voltronic Axpert MKS. I > am > >

Hello i need your help regarding the following issue : i have a hero touch ups from infosec. it is connected via USB to a raspberry pi 3. i?ve configure ups.conf file as below [HERO] driver = blazer_usb vendorid = 0665 productid = 5161 either with port = auto or port = /dev/hidraw0 or port = /dev/ttySo the connection never works i get the

Hi Users NUT, I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a raspberry-pi. In compatibility list, is listed to use the blazer_ser driver. I use a USB adapter to RS-232 conected in to the No-Breake. Follow the comands e confs. root at rasp:/home/pi# lsusb *Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port* Bus 001 Device 003: ID 0424:ec00 Standard

On Feb 18, 2014, at 10:15 PM, Charles Lepple wrote: > On Feb 18, 2014, at 5:55 PM, Thiago Tiedtke dos Reis wrote: > >> Hi, >> >> Recently I got three units of this nobreak [0]: > ... >> [0] http://www.sms.com.br/produtos/Nobreak-SMS/Manager-III-Senoidal > > According to the HCL, for the Manager III, you might want to try the blazer_ser (or in 2.7.1,

I use Debian jessie with nut-server 2.7.2-1+b3. Yesterday I've configured it for my new Advice PRS850 (a UPS with USB interface). I also have an USB webcam (and also USB mouse and keyboard, but that doesn't matter). When I start the program Cheese (a program which uses the webcam), I receive the following broadcast message: "Communications with UPS advice at localhost lost"