similar to: NUT on Raspberry PI 3b+

I was able to make NUT and my Powercom SPIDER UPS (USB port) work under the Raspberry Pi Desktop (Debian). Everything works in VMware Workstation 15 Player. But my Raspberry Pi 3b + (with raspbian) doesn’t work with the same UPS, and with same NUT configuration. Raspberry sees the UPS, but the driver does not cling. Here is the response of Raspberry 3b + to some commands. pi at raspberrypi:~

I installed the NUT under the latest Ubuntu Mate for Raspberry. The driver immediately earned with my UPS (Powercom SPD-850U). But my happiness was not long. After the first restart of Raspberry, the NUT did not start. It is treated by reconnecting the USB connector. Reconnection has to be performed after each reboot of Raspberry. The USB permissions for the "nut" group and priority

please subscribe to the nut user mailing list ( http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser) and post the output of "/path/to/usbhid-ups -DDDDD -a <your_ups_name_in_ups.conf>" cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

On May 2, 2019, at 6:22 PM, Vladimir Zaitchikov wrote: > > pi at raspberrypi:~ $ lsusb -v > > Bus 001 Device 004: ID 0d9f:0004 Powercom Co., Ltd What are the permissions on /dev/bus/usb/001/004? If the group is not "nut", and you installed NUT after plugging in the UPS USB cable, you may need to run udevadm as mentioned here:

I have a Powercom SPD-850U UPS. I try to connect this UPS with my Raspberry PI 3B + via NUT, I came to the conclusion - all works nice with Raspbian (2018-03-13), the first one that supports 3B +, but does not work with the latest version of Raspbian (2019-04-08). I think, the algorithm for working with the USB bus has changed in the latest versions of the kernel. And this is bad, because it

My UPS Powercom WOW-1000U does greatly work with NUT, but not auto-cofigurable... This UPS is not usb-hid ups, and works well with this settings in NUT: [powercom] desc = "powercom" driver = powercom port = "/dev/serial/by-id/usb-POWERCOM_CO.__LTD._USB_to_Serial-if00-port0" type = IMP lsusb -v fragment attached. Unlike other UPSes, gnome-power-manager does

Hi, Sometime ago I asked the question about getting nut to run on my iMac as I was having trouble getting the USB driver to behave with OS X. The same driver under LINUX is fine. It was suggested that the better option might be to run nut on a Rasberry PI instead and monitor the nut daemon from the iMac. Well I have bought a Rasberry PI, I have other things planned for it. I have installed nut

Hi, I know it's been a topic many times here, but I've searched the archives, googled for days, and I simply don't believe, that there is still no solution to this. I'm using a PowerCom BNT-600AP ups with usb port. I've downloaded the latest version from svn, compiled it, and tried to use it: * megatec(_usb) - no luck, it did not find the UPS (I?ve read in this list, that

I have a Powercom SPD-850U UPS. I try to connect this UPS with my Raspberry PI 3B + via NUT, I came to the conclusion - all works nice with Raspbian (2018-03-13), the first one that supports 3B +, but does not work with the latest version of Raspbian (2019-04-08). I think, the algorithm for working with the USB bus has changed in the latest versions of the kernel. And this is bad, because it

Hello In case anyone is interested and for the sake of updating the documentation from http://networkupstools.org/stable-hcl.html , I would like to report that nut v2.7.4 talks successfully ( at least partially ) with the UPS from $topic, which is part of the product line from http://www.informups.com/guardian_guardian_lcd600va_2000va.html ( Inform is a Turkish manufacturer that was

Hi all, I've bought UPS FSP EP 850 because I have similar UPS, FSP EP 1000. It is working on my other server with with Fedora 14, kernel 2.6.35.14-106.fc14.x86_64 and installed nut-2.6.2-1. My new UPS is detected by kernel (see below lsusb output) and is partially detected by blazer_usb driver also. But it doesn't communicate with driver (see below blazer_usb output). I run all

Hi all, just landed here so apologize. I've googled a lot but I can't find a way to get my UPS working with NUT. here my ( relevant ) details: lsusb ... ... Bus 001 Device 027: ID 0001:0000 Fry's Electronics ... ... lsusb -v -d 0001:0000 Bus 001 Device 027: ID 0001:0000 Fry's Electronics Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB

Hi All, I bought a USB Bluetooth dongle. However, it's not working for me. Please help, how to debug and get more information as I can not see any error or warning message from system log message. I checked http://thread.gmane.org/gmane.linux.bluez.kernel/22183/focus=22211, however, also find another page

Hello list, ? ?Cannot make Evolution 850 to be recognized, maybe the problem is "Warning: incomplete endpoint descriptor" in lsusb? Details are as follows. NUT installed by download of debian package. Any ideas/suggestions are highly welcome, thanks in advance! --ValenteM = ? ?= ? ? = ? ? = Ubuntu server 12.04.1 LTS (GNU/Linux 3.2.0-35-generic x86_64) sudo dpkg -i

Hi, just try the Unitek Self Protek Mistral 1000ipF with nut and I doesn't work. How can I correctly configure it (if the driver support it). Best regards, In my dmesg: [42953293.620000] usb 1-2: new low speed USB device using uhci_hcd and address 7 [42953293.760000] usb 1-2: no configurations [42953293.760000] usb 1-2: can't read configurations, error -22 [42953293.880000] usb 1-2: new

Apologies for the long post. I'm trying to include what I hope are the relevant bits (output of lsusb -v and usbhid-ups) Long term goal: I've got a DIY UPS that I would like to get working with my QNAP NAS (which uses Linux and NUT underneath the hood) Immediate short-term problem: I can't get past running usbhid-ups on Ubuntu 23.10 with an Arduino Leonardo. I have an Arduino Micro

Hi, I have a powermust with a usb connector. I searched the archive and found this post: http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-April/000816.html Must I abandon hope of controlling this UPS via USB with NUT? Added this line to /etc/udev/rules.d/70-nut-usbups.rules: # OMRON - usbhid-ups SYSFS{idVendor}=="06da", SYSFS{idProduct}=="0003",

Hello I have two completely different UPS that turn out to use the same driver. Both work with blazer_usb my LSUSB says: Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial Bus 001 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial my lsusb -vd 0665: says: pi at elektra:~ $ lsusb -vd 0665: Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial

Hi all! FYI, after some research in your list I think that blazer_usb is the best driver for my Soyntec Sekury A600 UPS (which is not in the hardware supported lists). I connected it with my system using USB port (it also has serial RS-232) This is the report I have: battery.voltage: 13.60 battery.voltage.nominal: 12.0 beeper.status: enabled device.type: ups driver.name: blazer_usb

folks, the following is lsusb -v for my 250gb usb hard drive. I note the Protocol line mentions zip: ie bInterfaceProtocol 80 Bulk (Zip) does that mean its one of those USB-ZIP devices ? If so, to the parameters below say anything about the CHS settings needed ? tia, PS - HPA, you were correct wrt what I missed :-} Bus 001 Device 002: ID 1058:0401 Western Digital Technologies,