similar to: Udev rules troubles: incorrect ACTION expression?

G'day, all! I installed latest stable nut-2.6.1.tar.gz from source on Xenserver 5.6 SP2 (Linux xen-home 2.6.32.12-0.7.1.xs5.6.100.323.170596xen #1 SMP Fri Apr 8 07:25:07 EDT 2011 i686 athlon i386 GNU/Linux), my UPS is Powercom WOW--500U FW3.A4. All works almost fine but here are some troubles: when I pull the plug then upsd immediately starts (after FINALDELAY delaying) the procedure of

Hi all, Here's a brief history of my adventure: I purchased a CyberPower 685 AVR and decided to connect it through USB to my Gentoo linux machine running kernel 2.6.22. While the device was detected properly and added to /dev, it was added with the wrong permissions (gid was set to 'usb' instead of 'nut', as it was expected to be according to the rules under

Can anyone point me to information for getting the Tripplite SMART3000RM2U to work with NUT? Our newer Tripplite units seem to work with the usbhid-ups driver, but these older ones seem to need something different. So far I have had little success getting tripplite_usb to work. [root at banyan ~]# tripplite_usb -a tripplite Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.1)

Hi. I'm using nut with debian squeeze. When the computer boots and nut is loaded, I get the following messages: "Starting the hotplug events dispatcher: udevdudevd [451]: BUS= will be removed in a future udev version. please use SUBSYSTEM= to match the event device. or SUBSYSTEMS= to match a parent device. in /lib/udev/rules.d/52-nut-usb.rules:6 . Synthesizing the initial hotplug

Hi, seems there is one missing change in /trunk/scripts/udev/nut-usbups.rules.in BUS -> SUBSYSTEMS previous change [1] missed this. Now, the latest udev started to complain: > ... udevd[31526]: BUS= will be removed in a future udev version ... 098 udev version (from 2006) is required for this [2], but this is the same version as required for previous SYSFS -> ATTR change. I've

Hello. I have this UPS: Krauler UP-D1200VA Megatec USB protocol Vendor ID: 0x0001, Device ID: 0x0000 #KRAULER UP-D1200VA VER6.00 #220.0 004 23.50 50.0 Currently I have nut 2.2.0 installed from sources. Installation was successful except that I had to change a string in 52-nut-usbups.rules from: SUBSYSTEM!="usb_device", GOTO="nut-usbups_rules_end" to:

In a separate discussion, on 6/26/17 4:04 AM, Arnaud Quette wrote: > Hi > > If you're sure it's a HID device, add an entry in drivers/powercom-hid.c > { USB_DEVICE(POWERCOM_VENDORID, 0x0002), NULL }, > > Then autogen.sh + configure... > Please also report back so that I can update the code > > Cheers > Arno Thanks! I don't *know* whether or not

Thought I'd follow up in case someone else runs into this issue. In the end what worked for me was tweaking the udev rules. I have had no USB disconnects or stale data warnings so far. I only used one rule for my UPS: # /etc/udev/rules.d/62-nut-usbups.rules SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end" # TrippLite # e.g. TrippLite SMART1500LCD - usbhid-ups

I wouldn't be surprised if they both use the same driver. I think they are essentially the same model, but with one having a slightly larger battery. My issue is primarily with the UPS turning back on after having shut off like it should. @Scott Colby if you take a look at the config files I posted in the github issue I created, perhaps that will give you some hints on your issue. Maybe

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 last version) 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

Hi ALL, Powercom Imperial IMP-525AP seems to be fully compatible with NUT. Unfortunately, I can not disable beeper. upscmd -u {NUT_USER} -p {NUT_PASSWORD} powercom beeper.toggle returns *OK*, however, ups.beeper.status=enabled Thank you, Sergey ========== Additional info: 1) $ upsc powercom battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.date: 2010/01/01

I've read through the archives http://lists.alioth.debian.org/pipermail/nut-upsuser/2006-August/001550.htmland http://lists.alioth.debian.org/pipermail/nut-upsuser/2006-August/001558.html. Going through the readme, http://eu1.networkupstools.org/doc/2.2.0/INSTALL.html, I made it to step 8 before the problems started. Originally I had used the usb program supplied with the ups from powercom,

I have an FC5 system with a powerware 5110 usb ups. The system seems to find the UPS ------------------------------ [root@b1 src]# lsusb Bus 004 Device 001: ID 0000:0000 Bus 003 Device 002: ID 0592:0002 Powerware Corp. Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 ------------------------------- [root@b1

Hello, I've compiled and installed nut-2.7.2 on a Xen server (Actually XCP 1.6/Centos 5.7) to manage a Dell UPS 2700W. Here is my ups.conf : [SU27003U-08] driver = usbhid-ups port = auto desc = "SU27003U-08" 52-nut-usbups.rules have well been installed in /lib/udev/rules.d/. I've put it in /etc/udev/rules.d/ too. I've rebooted the machine.

On Apr 23, 2014, at 3:47 AM, Frantz de Germain wrote: > I've compiled and installed nut-2.7.2 on a Xen server (Actually XCP > 1.6/Centos 5.7) to manage a Dell UPS 2700W. > > Here is my ups.conf : > > [SU27003U-08] > driver = usbhid-ups > port = auto > desc = "SU27003U-08" > > 52-nut-usbups.rules have well been installed in

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 -

Hello list, I am configuring NUT on a Dell workstation that is connected to an APC Back UPS Pro 1300, and I am running into an issue where starting everything manually seems to be successful, but fails when using the init.d scripts. The short story is that I get the following error when trying to check the status of the UPS: [root at mypc:/etc/nut]# upsc apc_pro1300 at localhost Error:

On Sat, Jun 27, 2020, at 23:11, Manuel Wolfshant wrote: > On 6/28/20 5:54 AM, Scott Colby wrote: >> >> I'm not convinced this is the problem; I think that pfSense has an alternative way of running the NUT components: # ps aux | grep ups root 45456 0.0 0.1 6796 884 - Is 02:22 0:00.01 /usr/local/sbin/upsmon uucp 45751 0.0 0.1 6796 772 - S 02:22

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

Hi. Sorry for the English. Use online translator. Trying to configure Powercom Smart KING Pro 1250A and Debian Jessie. OS name and version: Debian Jessie 8.8, kernel 4.9.25-1~bpo8+1 exact NUT version: 2.7.2-4 NUT installation method: package exact device name and related information: Powercom Smart KING Pro 1250A (connect via usb; leads changed) complete problem description, with any relevant