similar to: Power failure and NUT not shutting down

Can anyone give me insight into upsrw? I have a cyberpower PR2200 UPS (running an experimental version of the powerpanel driver hot off the presses by Arjen (thanks Arjen!!)). When I try to run "upsrw -s xyz=abc" to set any available variable, I get "Set variable failed: Access denied". What user name and password is it looking for here? My upsd.users file has 2 users

Hi all, first message to the list. :-) I've got an iBox made by iDowell: http://store.apple.com/uk/product/TR423ZM/A This seems to be similar to the smaller Microdowell UPS: http://idowell.eu/ I cannot get it recognised by the drivers. This is what I get when I plug in the USB connector: Jan 3 19:27:26 compaq kernel: usb 3-2: new low speed USB device using uhci_hcd and address 47

Hello! I got my hands on a CyberPower 1500AVRT, and i'm trying to get it connected to my Gentoo machine. I've followed all the basic guides on setting up NUT and UPS' but have had no luck. My current ups.conf is: [cyberpower-gentoo] driver = cyberpower port = /dev/ttyS0 desc = Workstation Upon running /etc/init.d/upsd start or upsdrv start I get: * Starting

Hi, Nut version 2.2.2, Opensuse 11.0 using serial connection using Cyberpower cable. Have 2 servers connected directly using serial. Looking for a way to get this ups and nut to work together. Have tried with powerpanel and cyberpower and they both do not like to talk to the ups. The upsd fails to start. Can somebody guide me to what I do wrong or how I can find the issue. The port is

I have three APC SmartUPS 5000s. Two of them are AP9617 and one is AP9619. I have a RS-232 connections from my monitor host to all three. All three report status and give information. One of the two AP9617 - ups3-1 - does not shut down when FSD is sent. It did when I first set this system up a year or two ago but it's stopped doing so since then. Resetting the management interface does not

Ok, so just a follow-up to my last email; still following that guide, which is great…. Just stuck on getting the nut-server service starting automatically.  Got everything else working.  I’ve been able to get the nut-client starting up automatically at boot up (I had a missing “1” in upsmon.conf.  Oooops!)  However, I cannot get nut-server service to start-up automatically still. proton at

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

Dear Charles, thanks for your quick answer and your information! I didn't know there is a difference in the PR-series between old and new. So thanks for this valuable information! usbconfig dump_device_desc shows: ugen0.2: <CyberPower Systems product 0x0601> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (50mA)

I recently purchased a Cyber Power 700 AVR UPS. I installed it just fine and wanted to install NUT to monitor the unit. I searched the mailing list and found a similar post. However, the distro used in that post was different and the unit was slightly different (900 AVR). My server is running Debian Lenny. The Cyber Power UPS is connect to one of the serial ports using the cable that came with

For directory permissions, the "x" priv determines if you can access the directory, so going from 555 (r-x,r-x,r-x) to 640 (rw-,r--,---) pretty much locks out access to the dir. Myself, I'd go back to 555. 640 essentially locks the group "nut" out . . . - Tim On August 11, 2020 11:11:22 PM CDT, Todd Benivegna <todd at benivegna.com> wrote: >Ok, so just a

On Aug 12, 2020, at 5:32 PM, Todd Benivegna <todd at benivegna.com> wrote: > >> Those LISTEN lines were appropriate pre-systemd when NUT's startup script was launched after networking was fully enabled. I would recommend "LISTEN 0.0.0.0 3493" instead, and use firewall rules if you are trying to exclude an interface (which is likely not the case on a Pi). > Ok, so

Hello All, I'm trying to establish a MASTER SLAVE configuration of UPS using NUT Driver. I'm able to shutdown the master after UPS is on BATTERY ( POWER BLACKOUT) .However I'm trying to shutdown the other SLAVE MACHINES BEFORE MASTER. But at the remote side ( Slaves ) shutdown after UPS blackout does not happen. My configuration in Master are /usr/etc/upsd.users

On Fri, 7 Aug 2020, Todd Benivegna wrote: Hello Todd, sorry for the delay replying, I was away for a while. It's ok to post configuration files in this list if blank lines and comments are removed. > On the Synology (I didn’t edit any of these files): > ups.conf:  https://hastebin.com/dedereqizi.shell pollinterval = 5 [ups] driver = usbhid-ups port = auto >

This fixed everything! Everything appears to be working ok now and all clients are connected. Thank you! Going to test everything out now. -- Todd Benivegna // todd at benivegna.com On Aug 12, 2020, 6:16 PM -0400, Charles Lepple <clepple at gmail.com>, wrote: > On Aug 12, 2020, at 5:32 PM, Todd Benivegna <todd at benivegna.com> wrote: > > > > > Those LISTEN lines

It seems the `libmodbus` library or headers were not found, or something similar - so the driver against it was not built. Did you install `libmodbus-dev` before the build? What does `config.log` in the build root say (and.or the summary shown after you run the `configure` script)? On Sat, Sep 16, 2023 at 7:46?PM FatGear <fatgear1 at free.fr> wrote: > Hi, > > I don't know what

This unit works fine with the "cyberpower" driver (which reports it as "Unknown model - 15"). It reads this much from it: battery.charge : 100 driver.name : cyberpower driver.parameter.pollinterval : 2 driver.parameter.port : /dev/ttyS0 driver.version : 2.2.0- driver.version.internal : 1.00 input.frequency : 60.2 input.voltage : 121 ups.firmware : 5.100

I am having some problems getting NUT to run with my cyberpower avr1200 (brandnew). I have a straight through serial cable, and I am getting this: /usr/local/etc/rc.d/nut.sh start Starting nut. Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools - CyberPower driver 1.00 (2.0.2) Giving up on hardware detection after 3 tries Unable to get initial hardware info string Driver failed

I am having some problems getting NUT to run with my cyberpower avr1200 (brandnew). I have a straight through serial cable, and I am getting this: /usr/local/etc/rc.d/nut.sh start Starting nut. Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools - CyberPower driver 1.00 (2.0.2) Giving up on hardware detection after 3 tries Unable to get initial hardware info string Driver failed

Hello there, I don't think that's working,? I have done all your repo but i don't know how it's supposed to work. I have a idea, change vendor id and product id? to make the driver try to connect to the ups, what do you think of that ? With this driver maybe : usbhid-ups FatGear Le 16/09/2023 ? 20:40, Jim Klimov a ?crit?: > It seems the `libmodbus` library or headers were

I'm looking for people that are using the 'cyberpower' driver that has been available for some years now. It seems the overhauled 'powerpanel' driver could support your UPS too. The commands and status bytes used are identical, the only difference being the way the values read for battery charge, temperature and frequency are interpreted. If we can find a way to detect when to