similar to: FW: Unable to use the TCP network interface

* Rasbian Buster Lite: latest * NUT version: latest * NUT installed from package manager * CyberPower CP1000PFCLCD via USB Followed this article: https://loganmarchione.com/2017/02/raspberry-pi-ups-monitor-with-nginx-web-m onitoring/ "upsc" command works and outputs UPS data correctly. My question regards the TCP network interface:

On March 23, 2020 1:43:01 PM UTC, Tyler Montney <montneytyler at gmail.com> wrote: >Compiling against >http://www.networkupstools.org/source/2.7/nut-2.7.4.tar.gz. >I also have libusb-0.1-4 installed but no joy. > >On Mon, Mar 23, 2020 at 2:45 AM Jim Klimov <jimklimov at cos.ru> wrote: > >> On March 23, 2020 12:50:11 AM UTC, Tyler Montney ><montneytyler at

On Mar 22, 2020, at 8:50 PM, Tyler Montney <montneytyler at gmail.com> wrote: > > Came across this in the process of troubleshooting: https://alioth-lists.debian.net/pipermail/nut-upsuser/2011-November/007249.html <https://alioth-lists.debian.net/pipermail/nut-upsuser/2011-November/007249.html> Take everything that guy says with a grain of salt ;-) > > My whole reason for

On March 23, 2020 12:50:11 AM UTC, Tyler Montney <montneytyler at gmail.com> wrote: >Came across this in the process of troubleshooting: >https://alioth-lists.debian.net/pipermail/nut-upsuser/2011-November/007249.html > >My whole reason for compiling from source is to add SSL support (as it >doesn't seem available through the package manager). Apt list shows >these

Compiling against http://www.networkupstools.org/source/2.7/nut-2.7.4.tar.gz. I also have libusb-0.1-4 installed but no joy. On Mon, Mar 23, 2020 at 2:45 AM Jim Klimov <jimklimov at cos.ru> wrote: > On March 23, 2020 12:50:11 AM UTC, Tyler Montney <montneytyler at gmail.com> > wrote: > >Came across this in the process of troubleshooting: > > >

On Mar 23, 2020, at 9:43 AM, Tyler Montney <montneytyler at gmail.com> wrote: > > Compiling against http://www.networkupstools.org/source/2.7/nut-2.7.4.tar.gz <http://www.networkupstools.org/source/2.7/nut-2.7.4.tar.gz>. I also have libusb-0.1-4 installed but no joy. > The 2.7.4 tarball predates the work towards supporting libusb-1.0, so libusb-0.1 should work. Check the

Came across this in the process of troubleshooting: https://alioth-lists.debian.net/pipermail/nut-upsuser/2011-November/007249.html My whole reason for compiling from source is to add SSL support (as it doesn't seem available through the package manager). Apt list shows these installed: libusb-1.0-0-dev/stable,now 2:1.0.22-2 armhf [installed] libusb-1.0-0/stable,now 2:1.0.22-2 armhf

Hi! I just installed a new CP1000PFCLCD (Cyber Power PFC Sinewave UPS) and everything appears to be working correctly, except that I have an oddly high output voltage reading from nut. All of the other values seem consistent with what the front-panel LCD says except for this one. Is this something that needs a correction factor, or perhaps the value the driver is reading has been remapped? BTW,

Charles Lepple writes: > On Nov 12, 2017, at 10:08 AM, Sam Varshavchik wrote: > > > > 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 will work; but figure I ask if anyone

Cyber Power Systems CP1000PFCLCD = upsc output = attached = Shutdown results = I experienced a genuine power outage shortly after setup. The 1 master system and the 1 slave system both shutdown successfully. The master shutdown before the slave (*not* a bug report; I may not have this configured correctly yet). The UPS was not powered off by the master. I don't know if the UPS

On Nov 12, 2017, at 10:08 AM, Sam Varshavchik wrote: > > 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 will work; but figure I ask if anyone knows for sure. > We have a bit of a backlog of HCL/DDL

I have the same issue of incorrect output voltage being reported by usbhid-ups, as run on NAS4Free (FreeBSD). UPS is as shown below. There is a thread on this list from 2014 that has these same issues, apparently never addressed by any of the later usbhid-ups releases. I?m using 2.7.3. The value I am especially concerned with is the output voltage; if ANY thing should be right on the report, it?s

On 11/12/2017 10:08 AM, Sam Varshavchik wrote: > 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

Attached is the first 32 seconds of the driver output after applying the patch which fixes the battery scaling problem for this UPS. Matthew Stapleton Email: matthew4196 at gmail.com On 10/08/14 01:27, Charles Lepple wrote: > On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote: > >> On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com>

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

On Sep 10, 2015, at 10:23 AM, d tbsky <tbskyd at gmail.com> wrote: > > Hi: > I found I can setup password for uspmon. but upsc can connect to > any upsd without authentication. although the ups data is not very > confidential, but I would like not to expose it to anyone who can > connect to server. > > is there any method to harden upsd? thanks for hint.

On May 31, 2019, at 11:19 AM, Gene Heskett wrote: > > On Friday 31 May 2019 10:08:02 am Charles Lepple wrote: >> >> To be honest, I thought we had fixed this a while ago (NUT 2.7.1), but >> I guess it popped back up again: >> https://github.com/networkupstools/nut/issues/30 > > nut 2.7.2. Built from the tarball. Some option I should have configured > it

If you don't use 'CERTVERIFY 1', then this will at least make sure that nobody can sniff your sessions without a large effort (...) > So, do I misunderstand CERTVERIFY directive ? Or is there a bug ? >> Can you reproduce such behaviour ? >> > > I'm not sure what is going on. Can you try running 'upsmon' with debugging > enabled? The following are