similar to: Keep on losing communication: Raspberry Pi, CyberPower PR1500LCD

On Aug 12, 2017, at 12:00 PM, Rory Jaffe <rsjaffe at gmail.com> wrote: > > OS Version: Linux piaware 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux > Nut Version: 2.7.2-4 > Nut Installation Method: apt > Device: CyberPower PR1500LCD > Uses? ?Generic HID driver 0.38 (2.7.2) Is this stock Raspbian or another variant? If it is Raspbian, I think it might

I've not been able to connect to my ups using NUT 2.7.4 or NUT 2.8.0. 2.7.4 was installed as a package, 2.8.O was compiled from source. I've messed with permissons, everything is root:root and has the approprate read/execute permissons. I've tried two differnt UPS(es) APC & CyperPower. I'm running PI OS (Raspbian) on a Raspberry Pi3 model B. The port 3493 is open (UFW). I can

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

Now that upsstats.cgi works, I've noticed that dummy-ups changes state every 5 minutes between OL and OB (probably when the 300 second timer expires). The UPS state stays online. Also "online" and "onbatt" are broadcast to the console probably via WALL. (The state changes don't seem to be form the ups as upsshed-cmd doesn't run). Upssched-cmd does run when the UPS

Hi all, So I was on the phone with their tech support, and I was able to get a copy of their protocols, see attached. >From reading it, it looks like the hex code in the debug area is key. Thanks, Mike On Wed, Jun 6, 2018 at 1:41 PM, Michael <fax12345 at gmail.com> wrote: > Hi Charles, > > Here's a screen grab of what I ran: > > ubuntu at intranet:~/upsmonitor/nut$

Hi Charles, Here's a screen grab of what I ran: ubuntu at intranet:~/upsmonitor/nut$ git checkout tripplite_0005 Already on 'tripplite_0005' Your branch is up to date with 'origin/tripplite_0005'. ubuntu at intranet:~/upsmonitor/nut$ git status On branch tripplite_0005 Your branch is up to date with 'origin/tripplite_0005'. nothing to commit, working tree clean

I've built NUT 2.8.0 from source. When the nut-monitor runs: fopen upsmon.pid fails. I'm running as root, upsmon has root:root permissions as well as the other daemons and .conf files. I've tried configuring with and without --prefixpath --prefixaltpath. Is there something I am missing? Please see attached. Dan -------------- next part -------------- An HTML attachment was

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a little patch for the drivers.list The "Cyber Power Systems Intelligent Series CP1500EAVRLCD" ups http://eu.cyberpowersystems.com/products/ups_systems/intelligent/cp1500eavrlcd.htm Got one here running (see: https://nut.stillbilde.net/cgi-bin/nut/upsstats.cgi?host=CyberPower at upsmonitor) Works flawlessly. Patch as follows:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've set up my ups solution with a dedicated box (laptop with its own powersupply) connected to the ups, and have set up upsmon.conf to use a customized script (SHUTDOWNCMD "/usr/local/upsmonitor-files/shutdown.sh") that shuts down my ESXi boxes properly. However when ups power reaches the shutdown point, it seems that NUT promptly

Hey all! I'm sure you've all been missing my webcam stream, so I decided to start it up again (also, I wanted to do it for my family overseas). However, this time, I'm doing things a little bit differently. For starters, the encoder is the current (as of about an hour ago) ptalarbvorm branch which is destined to become libtheora 1.2. Another difference is that I'm using

Hy list, first of all - yes I have read the docs, but obvious I must have missed something. The user/password setting in upsd.users seems to be ignored and I can monitor the ups with some arbitrary password. The following setup is working: Server A has nut installed and has the following config: upsd.conf: ACL localnets 192.168.101.0/255.255.255.0 ACL localhost 127.0.0.1/32 ACL all

Hi I have a GE Digital Energy Match UPS 1500 where i previously successfully used the victronups driver. However after i upgraded from debian woody to debian sarge and thus from 1.4.2 to 2.0.1, then upsstats.cgi says Model not supportet, status online My syslog says Jul 25 11:12:28 localhost upsmon[6220]: Startup successful Jul 25 11:12:28 localhost upsd[6218]: Connection from 127.0.0.1

OK, I am running CentOS 6 on my Laptop and Desktop, presently kernel version 2.6.32-696.20.1.el6.x86_64 (yes, a version or so out of date -- I'll probably do an update soon -- non-trivial since my Internet connection is via dialup). I recently bought a couple of Adafruit Arduino compatibles, a Flora and a Metro 328. Hooking up the Flora and the Metro to a Raspberry Pi running Raspbian

Roger, I get 4.3.8(1)-release There was good reason, BTW, for the script to NOT fine the journal script on my machine. I had not downloaded it yet. On 7/14/2019 9:06 AM, Roger Price wrote: > On Sun, 14 Jul 2019, David White wrote: > >> ... I saw nothing that looked like a problem with the report save the >> sections <scriptname> "Cannot access <scriptname>.

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120104/34be491b/attachment.html>

Hi, - The device never re-connects to the system, i have to physically remove the USB plug and insert it again for the device to come back. - This does not happen when running the driver from the supplier. (java process) - When i poll every 60s it works for about 3 days, anything lower or higher causes it to disconnect faster - The big log i sent is not the output of the driver? if not how can i

Hi, I have a Liebert UPS which I have connected to a FreeNAS Box. I had all sorts of issues making FreeNAS (FreeBSD based) talk to the UPS over USB. My solution seemed to be to buy a Raspberry Pi then connect it to the UPS (works fine), then make my NAS read the UPS status from the Pi over a TCP/IP connection. Convoluted I know, but it works well...for about a month, then it just loses

On Sep 3, 2014, at 9:38 AM, Heiko L. <HL at fh-lausitz.de> wrote: > Howto force shutdown if nut-snmp Communications lost? > > My 1. suggestion was option DEADTIME, but seem to be information only. (s. below) DEADTIME expiration is a critical condition if the UPS is on battery when comms are lost, otherwise you are correct, it is only informative. What about a NOTIFYCMD script

Hallo, I have one ups with snmp and any ups without snmp. Shutdown works while network online. But some batteries are empty, so that the communication break early. Howto force shutdown if nut-snmp Communications lost? My 1. suggestion was option DEADTIME, but seem to be information only. (s. below) Any suggestions? The last way would be a ugly cronjob (like: ping || shutdown). regards Heiko

On Feb 9, 2015, at 6:48 AM, PERE (yahoo.es) <pererivers at yahoo.es> wrote: > 0.028188 Can't set USB configuration: could not set config 1: Device or resource busy > 0.029246 detached kernel driver from USB device... > 0.030559 USB device [0001:0000] opened > 0.866216 read: (8 bytes) => 03 00 00 00 00 00 00 00 > 0.866413 reply[0] = 0x03