similar to: NetworkUPS tools Compatibility update

Hi Patrick, 2010/11/15 Patrick O'Malley > I've confirmed that the CyberPower CP1350AVRLCD works with nut using > the USB port and the usbhid-ups driver. It is not on your list. > Thanks! > have you checked all variables, and most of all that shutdown works as expected? ie http://new.networkupstools.org/user-manual.html#Testing_shutdowns please also send us an upsc output.

Hi list, I just recently installed Dovecot 2.0.15. Unfortunately, doveadm segfaults when I attempt to connect to the local dovecot instance. When this occurs, my logs show: 2011-10-19T12:31:23-07:00 mail02 dovecot: doveadm: Error: doveadm client not compatible with this server (mixed old and new binaries?) I am using the settings listed on the wiki page http://wiki2.dovecot.org/Director [root

We are interested in using Nut on our Federa 6.0 servers. However, our UPS systems are sold under the name "Geek Squad" (sold through the Best Buy chain of department stores). I'm pretty certain Geek Squad does not manufacture these units and they just rebrand them. Does anyone know who makes these units or what they are compatible with in terms of driver level protocol? The ones we

Got the: git clone git://github.com/networkupstools/nut.git To work. Had to all so do this: apt-get install autoconf apt-get install libtool Did put driver = usbhid-ups in the /etc/nut/ups.conf file like you said. Here is what I got for it all: root at odroid-u2:~/nut# ./autogen.sh Calling autoreconf... libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying

UNITEK Alpha650ipF and Alpha650ipE Build NUT v2.6.4 from sources http://www.networkupstools.org/source/2.6/nut-2.6.4.tar.gz System: RedHat Linux RHEL4 Kernel: 2.6.9-42.0.10.EL (upsc) command output : battery.charge: 100 battery.voltage: 14.30 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.mfr: UNITEK device.model: Alph650ipF device.type: ups

> On Dec 3, 2016, at 12:31 PM, Jack McGee <jack at greendesk.net> wrote: >> so this is progress. Thanks! Anything else to check to know it is working as it should? http://networkupstools.org/docs/user-manual.chunked/ar01s06.html#Testing_shutdowns The "FSD" test is more for the NUT logic, which isn't too complicated with only one UPS and one server. If you want to

Anyone familiar with Cyberpower's model numbers? I finally got sick of my Tripplite's USB port going south, all the time, so I'm looking to replace it. The HCL has an entry for a Cyberpower model CP1500AVRLCD. Not listed is the CP1500PFCLCD model, a newer, premium version of the unit; but the HCL does have an entry for the CP1000PFCLCD model. Pretty sure that the CP1500PFCLCD

I''ve the same problem as Alastair when running rspec command : http://lists.macromates.com/pipermail/textmate/2007-October/022585.html ../spec/mate/runner.rb:34:in `run'': undefined method `parse'' for Spec::Runner::OptionParser:Class I fixed this for me by changing the offending line to : ::Spec::Runner::CommandLine.run(argv, STDERR, stdout) (see

Hey guys, :) recently, I installed Cyberpower PR2200ELCDRT2U, however, I have not managed to get this UPS working with FreeNAS 11, yet. According to compatibility list, PR2200 should work fine, when using powerpanel driver: http://networkupstools.org/ddl/Cyber_Power_Systems/ http://networkupstools.org/ddl/Cyber_Power_Systems/PR2200.html However, when trying to establish a connection between

rPi3 running current Buster.  I get this far: # upsc networkups Init SSL without certificate database battery.charge: 100 battery.charge.warning: 30 battery.runtime: 2891 battery.type: PbAC device.mfr: Vertiv Co device.model: Liebert PST5 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid:

I have been using the Asium P700 for about 4 months, running Debian Wheezy 7.9,? and would like to submit the UPS for inclusion in your list of supported devices.? ASIUM P700 (650VA/360W) | ? | | ? | | ? | ? | ? | ? | ? | | ASIUM P700 (650VA/360W)Prices only valid for purchases within the US. No PO Box deliveries. | | | | View on www.asiumpower.com | Preview by Yahoo | | | | ? | Not sure

Hello All I have a MicroDowell ups (BBox BP 1000) connected to a Gentoo box by serial cable. If I try to start the driver , I see the following : Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. debug level is '13' ups_sync: send [\rP4\r] ups_sync: got ret 46 [#1000VA

I'm trying to get nut to work with a Cyberpower 900AVR. There are many different products known by this name, but this one has the extra name 'BC900D'. I am told by a cyberpower tech that this one should talk exactly the same USB protocol as the 685AVR, which was recently made to work with newhidups. Unfortunately, when I run the SVN checkout (trunk) of nut-2.1, I get: sstreet

On 3/21/24 14:00, Greg Oliver via Nut-upsuser wrote: > All I can say is definitely replace the batteries if you are going to > keep using it.? The CyberPower(s) I have had in the past all have the > battery check that cannot be turned off and when the batteries are > actually "dead" the unit will kill the load to everything every time it > runs the check.? Just FYI.

On 12/03/2016 10:35 AM, Charles Lepple wrote: > On Dec 3, 2016, at 11:16 AM, Jack McGee <jack at greendesk.net> wrote: >> Dec 3 08:38:16 amethi upsd[18234]: not listening on ::1 port 3493 >> Dec 3 08:38:16 amethi upsd[18234]: listening on 127.0.0.1 port 3493 >> Dec 3 08:38:16 amethi upsd[18234]: no listening interface available > I can't say I fully understand

Hi there First a big thank you to all nut developers. I tried the 2.0.4 as well as the 2.0.5-pre1 versions with my CyberPower OP1000E connected to a serial to USB converter. All I got was the following: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5-pre1 Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5-pre1) Warning: This is an

On Thu, Mar 21, 2024 at 12:23?PM Phil Stracchino via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote: > I have a CyberPower PR3000LCDRTXL2U with a BP48V75ART2U expansion > chassis, which I am monitoring using NUT 2.8.0 (on Gentoo Linux). TThe > UPS appears to be telling me that the batteries need replacement due to > age. CyberPower support has confirmed that for

So, a while back I got around to ordering replacement batteries for my CyberPower PR3000LCDRTXL2U. When they arrived, I went to swap them in. I was horrified at the flimsiness of CyberPower's battery "trays". I've seen heavier gauge plastic on "blister" packages in the store. I ALSO discovered that the expansion unit had been shipped to me with one of its two

So, regarding wildcards (globs) vs. regular expressions, the latter being used for such matches, I believe (did not check now) the config sections should look like this: [cp] driver = usbhid-ups port = auto desc = "CyberPower UPS CP" model = "CP685AVR-G" vendorid = "0764" product = "CP.*" Note the

Thank you, looks like the regex idiosyncracy might have been the issue. My current file: [sl] driver = usbhid-ups port = auto desc = "CyberPower UPS SL" product = "SL.*" productid = 0501 vendorid = 0764 #model = "SL Series" [ab] driver = usbhid-ups port = auto desc =