similar to: release?

Seconding ... or firsting, considering the recent call to testing hidden somewhere in a recent mail post ;) Currently I'm aiming at cutting a NUT 2.8.1 release during October. As a bit of self-imposed retrospective: I did hope for a faster (quarterly or so) cadence when I made the 2.8.0 release, but then a few issues came up as regressions of 2.8.0 and it became a sort of crusade to fix

Seconding ... or firsting, considering the recent call to testing hidden somewhere in a recent mail post ;) Currently I'm aiming at cutting a NUT 2.8.1 release during October. As a bit of self-imposed retrospective: I did hope for a faster (quarterly or so) cadence when I made the 2.8.0 release, but then a few issues came up as regressions of 2.8.0 and it became a sort of crusade to fix

Hello, fellow NUTs! This October proved to be a rather productive month, with several developments wrapped up, as well as some issues with master codebase behavior created, reported, fixed and tested :) While we were not part of some official Hacktoberfest this year, it pretty much felt like one - great thanks to everyone involved! The month is also ending soon, so if we're to follow

Hello, fellow NUTs! This October proved to be a rather productive month, with several developments wrapped up, as well as some issues with master codebase behavior created, reported, fixed and tested :) While we were not part of some official Hacktoberfest this year, it pretty much felt like one - great thanks to everyone involved! The month is also ending soon, so if we're to follow

It looks like the CyberPower Cyber Power Systems CP685AVR supported by usbhid-ups has a favorable device dump linked to the Devices Dumps Library page here: http://networkupstools.org/ddl/Cyber_Power_Systems/CP685AVR.html However, it is not listed anywhere on the Hardware Compatibility List (HCL) page here: http://networkupstools.org/stable-hcl.html This appears to be an omission on the HCL

I am (belatedly) updating pkgsrc to 2.8.1 (+ bugfix). (FWIW, I think a 2.8.1.1 or 2.8.2 immediately with the fix is in order. >From a packaging viewpoint, the effort to update for a release is about 3 minutes plus time to adapt anythhing that has changed. So I'd much rather have releases more often.) In the pkgsrc build, nut finds tcp wrappers because they are part of the base system.

Hi I have just purchased a Cyberpower CP1300EPFCLCD UPS. It is not listed in your Compatibility List http://networkupstools.org/stable-hcl.html I am very new to all this but do have a background in IT. I have been retired for 18 years so am a bit out of touch so please excuse if I am a bit fuzzy. I will try my best to explain my issue below. When I plug my UPS into my Synology NAS

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

Hi, I installed apcupsd through pfsense and noticed some discrepancy with the NUT package. I'm not sure if this is a bug regarding the BATTDATE (apcupsd) and battery.date (NUT) but BATTDATE shows the correct date of 2016/05/11. While NUT shows the battery.date as 2001/09/25 which doesn't make sense. Any ideas? Pfsense 2.4.3-RELEASE-p1 (amd64) NUT 2.7.4_6 NUT installed through

Device Manufacturer: NHS Device Name: Expert C Online 6000 upsc output: battery.charge: 100 battery.current: 0.6 battery.date: 01012014 battery.runtime: 00000 battery.runtime.low: 59940 battery.temperature: 29 battery.voltage: 210.5 device.mfr: NHS Sistemas de Energia device.model: EXPERT GIII 8kVA device.type: ups driver.name: gamatronic driver.parameter.pollinterval: 20

I am wondering if there is a way to have Nut Server monitor a Minutemen UPS. https://minutemanups.com/uninterruptible-power-supply/pro-rt2u-line-interactive-uninterruptible-power-supply/ Thanks James -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20231213/254b1111/attachment.htm>

On 8/19/20 12:55 PM, Marc Franquesa wrote: > Thanks all for the quick responses on the question (always a good sign > of this mailing list). > > (Tim Dawson, Manuel Wolfshant): > Regarding root cause of my current problem pointing to a faulty > battery, this is not the first time that someone points to it. However > I made a simple test with the vendor tools (Windows) and

Below the answers: > This is the same as https://github.com/networkupstools/nut/issues/254 , right? Yes, this UPS is the same. > Does battery.runtime only get updated when on battery power, or is this with a different load? > battery.runtime.low: 59940 > battery.temperature: 00 Yes, this time time is updated on battery power, This is a dynamic counter that changes with a different

On Nov 12, 2014, at 5:46 AM, Thiago Wiezbicki <thiagowzb at gmail.com> wrote: > > > Device Manufacturer: NHS > Device Name: Expert C Online 6000 > > upsc output: > > battery.charge: 100 > battery.current: 0.6 > battery.date: 01012014 > battery.runtime: 00000 Quick question: does "battery.runtime" update when the device is on battery, or is this

The pieces should all be there, I think. NUT source iterations cooperate with the sister nut-website repo on github, as well as nut-ddl and some more, to produce an horde of static HTML pages, and PDF versions of some docs, tarballs, etc. which are pushed to a repo for "github pages" and with their magic (I guess GH spins up a container with a web server and many data files for each new

The Hardware Compatibility List page on our website said to report any omissions in the list to this address. I bought a CyberPower UPS Model *LX1500GU*. It looks similar to the *CP1500AVRLCD*. My intention is to configure it in FreeNAS (FreeBSD). The FreeNAS user guide says it uses NUT to provide UPS support an contains a link to your website for a list of drivers of supported UPS devices. I

My personal experience with a number of UPSes that are monitored via USB cable is that communications errors such as the ones referenced in the issue you linked to below are a result of USB hardware incompatibilities between the USB chipset and the USB port on the motherboard.*? This is NOT specific to the NUT project as it affects both apcupsd and in fact, has been reported as an issue with

We only have a few open items that I think should be resolved before releasing 2.7.3. The list grew a bit in the past week, but we'll cover that later. Here is the list: * #93: Devices Dumps Library improvements <https://github.com/networkupstools/nut/issues/93> * #158: Powerware BCMXCP advanced features <https://github.com/networkupstools/nut/pull/158> * #185: insecure storage

Also, which version of NUT is involved? There were recently PRs (merged to master-branch, eventually will be in 2.8.1) about more SNMP-UPS support including APCs e.g. 1674, 1679, 1113 (should be in 2.8.0)... Many distros still ship 2.7.4... Jim On Tue, Feb 28, 2023, 00:57 Greg Troxel <gdt at lexort.com> wrote: > mateuszx via Nut-upsdev <nut-upsdev at alioth-lists.debian.net>

mateuszx via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > At my workplace I have exact UPS config as stated in the subject (APC MGE > Galaxy 5500 + AP9635CH). > I have it set up to work with snmp-ups NUT driver. > Despite many readings from *upsc* command I am not receiving "On Line > Status" (ups.status OL) nor "On Battery Status"