Hello again all,
I just wanted to put this out there in case it helps anyone else. I found
the answer to this yesterday in another scour of Google.
https://nmaggioni.xyz/2017/03/14/NUT-CyberPower-UPS/
[cyber1]
driver = "usbhid-ups"
port = "auto"
desc = "CyberPower CP900EPFCLCD"
pollinterval = 15
The pollinterval key may or may not be a needed change, but since in this
configuration it works I see no harm in leaving it where it is.
/etc/nut/upsmon.conf
1
2
DEADTIME 25
MAXAGE 25
I’ve had nut up and running for over 12 hours now and still going strong.
Previously couldn’t get past 4 hours without stale data. Will keep an eye on
it and post back. Thanks!
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
From: Daniel Shields<mailto:grungeliza...@hotmail.com>
Sent: Friday, September 22, 2017 11:18 AM
To:
nut-upsuser@lists.alioth.debian.org<mailto:nut-upsuser@lists.alioth.debian.org>
Subject: Data stale at random intervals on Raspberry Pi Model B
Hello all. I have installed Nut on a Raspberry PI and all looks to be
configured correctly, but I get stale data and communications lost at random
intervals. I tried running nut-driver in gcc to see if I could find any clues
there, but it ran for about 24 hours with no sign of an issue. However, when I
let Nut run normally, it seems to be anywhere from 2 to 8 hours and the data
goes stale and communications are lost. Charles helped me compile Nut with
libusb-1.0 for my Debian server and Nut was solid for about a year, so I was
wondering if Nut for armhf could be compiled with libusb-1.0 as well. Thanks!
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
