similar to: LiebertPSP

On Jun 10, 2019, at 2:32 PM, Marc Finns wrote: > > Hello, I read all FAQ and other sources but I could not find this situation, so I thought of asking the experts. > I successfully configured a Raspberry NUT server to control my UPS that powers several devices (NUC with ESXI VMs, Synology NAS etc). > All works well in principle, but I have the following behaviours that I could not

Hi, I posted about this to the list earlier this week, but it seems to have got combined with a previous thread and lost, at least that's what it looks like in the archive (and I didn't receive a copy as I would have expected). So forgive me if you've already seen this, but: I've got a couple of LiebertPSP's connected to my equipment and I'd like to use NUT to keep an

Hi, I posted about this to the list earlier this week, but it seems to have got combined with a previous thread and lost, at least that's what it looks like in the archive (and I didn't receive a copy as I would have expected). So forgive me if you've already seen this, but: I've got a couple of LiebertPSP's connected to my equipment and I'd like to use NUT to keep an

Hi Guys Having trouble getting my LiebertPSP UPS to work. $ upsc upsname battery.charge.low: 38 battery.charge.warning: 38 battery.type: PbAc device.mfr: Emerson Network Power device.model: LiebertPSP device.serial: device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.vendorid: 10af driver.version:

I took the log. Here's what happened. Broadcast Message from nut at rasp (somewhere) at 16:18 ... UPS BNT500AP at localhost battery needs to be replaced occurred when for the first time value "1" was read as "UPS.PowerSummary.PresentStatus.NeedReplacement", on this line: 6409.240690 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x0a,

Hello Nutters, I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) with an APC Back-UPS CS 350 connected via USB. I get persistent (every few minutes) messages logged "battery is low" but I don't understand why. I don't think it's for the reason described in the FAQ (but I'm not 100% sure). In the trace output I can see that

I have a Tripp-Lite BCPERS450, connected to a system running Ubuntu 16.04.3 LTS and NUT 2.7.2-4ubuntu1.2. I had to make my own /lib/systemd/system-shutdown/nutshutdown, but now everything is working except for powering on and off the UPS. Regardless of the settings of offdelay and ondelay in upsconf, and regardless of whether the AC power is on, when I say "upsdrvctl shutdown" the UPS

Hello all, About a month ago Peter and Charles were kind enough to try to help me with getting a Tripp Lite USB UPS to work with NUT. I reported quite a bit of initial success, and then other things here fell apart. Between work, fence building and a week-long out of town business trip, I have had to drop this from my list of things to do lately. I am back at it, and I believe I will have

Hello, I am having difficulty using NUT to shut down my Netgate SG-1100 (a pfSense router) when the power level of the UPS gets critically low. Here is some relevant information: - OS: pfSense 2.4.5-RELEASE-p1 (FreeBSD 11.3-STABLE) - NUT version: 2.7.4 - Installed from: pfSense package 2.7.4_7 - UPS: AVR750U (Device release number 2) - I have included my config files, output from `upsc`, and

[I am CC'ing Alexey from Powercom in case he has seen any of these issues with the Raspberry Pi hardware.] On Jun 10, 2013, at 1:05 PM, M?rti?? Pu??tis wrote: > I took the log. Here's what happened. > Broadcast Message from nut at rasp > (somewhere) at 16:18 ... > UPS BNT500AP at localhost battery needs to be replaced > > occurred when for the first time value

Charles, It starts out good, then goes into a Connection timed out loop. If I can provide any information to fix a driver I'll do my best. Here's the output: # /usr/local/ups/bin/usbhid-ups -DD -a eaton Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 0.000000 debug level is '2' 0.002550 upsdrv_initups... 0.288229 Checking device

Hi, Folks, I'm new to this admin game, and one of the hardest parts for me is figuring out where files/programs/data are stored in the file system. I think this is one of these situations. I've installed NUT on my Mac OS X 10.5 server, using the macports build. The machine is a dual processor G4 tower, connected to an APC UPS via USB. usbhid-ups seems to be working, see output

I've acquired and installed NUT 2.4.1 on a D-Link DNS323 NAS. With exception of Load and Battery Temp readings all works well. A upsc ups at localhost command returns; battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2008/06/05 battery.runtime: 2122 battery.runtime.low: 120 battery.temperature: 3022999999999998800 battery.type:

Hi, I have an MGE Ellipse UPS connected to a FreeBSD 7.0 system and it works OK to begin with but after an hour or so it dies, eg.. Starts out OK.. debug level is '2' upsdrv_initups... Checking device (0463/FFFF) (/dev/usb2//dev/ugen0) - VendorID: 0463 - ProductID: ffff - Manufacturer: MGE UPS SYSTEMS - Product: ELLIPSE - Serial Number: 000000000 - Bus: /dev/usb2 Trying to match device

Hello. Not listed as supported, so here is some info, [root at vhost ~]# /usr/sbin/usbhid-ups -DD -a powercom Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 0.000000 debug level is '2' 0.001318 upsdrv_initups... 0.074753 Checking device (0529/0001) (003/002) 0.074835 Failed to open device, skipping. (Permission denied)

It's been a while since I tried to use NUT, so I thought I would give it another try. Big trouble. The UPS is a Tripp-Lite AVR 550U. It has only a USB connector. The computer is running Red Hat Enterprise Linux 4. I just installed NUT version 2.2.0. I'm going through the steps in the INSTALL document. # cat ups.conf [igor] driver = usbhid-ups port = auto

Thanks Charles, On Saturday 05 Apr 2014 12:53:06 Charles Lepple wrote: > On Apr 5, 2014, at 7:18 AM, Mick wrote: > > $ upsrw -s "ups.delay.shutdown"="30" iDowell at localhost > > Username (suzy): admin > > Password: > > OK > > This command is sending the value to the UPS (via the usbhid-ups driver). > > > $ upsc iDowell at localhost

Hi all, I've recently obtained a couple of LiebertPSP UPS and I set about hooking them up to NUT. The out-of-the-box functionality is almost, but not quite correct and I'd like to help fix that. I've done some research, starting here: http://www.mail-archive.com/nut-upsuser at lists.alioth.debian.org/msg05612.html and having just ended with me trying to write a new sub-driver for

On 10/01/2015 00:45, Charles Lepple wrote: > On Jan 8, 2015, at 11:43 PM, Graham Menhennitt > <graham at menhennitt.com.au <mailto:graham at menhennitt.com.au>> wrote: > >> Hello Nutters, >> >> I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) >> with an APC Back-UPS CS 350 connected via USB. I get persistent >> (every few

Hi all, I attached a driver for MiniBox openUPS device ( http://www.mini-box.com/OpenUPS) and a dump of the hid usages. I had the possibility to make a few adjustments to the device firmware for HID usages, and although I haven't managed to produce a good structure many issues from previous firmware were at least fixed and new information added. ATM the driver only shows pertaining