similar to: NUT website update, and plans for 2.7.5 release

Hi, > Since NUT is guessing, is there a way to make it list likely drivers back to the user when they are a close match and check validity for each one until it gets a good connection? Part of auto select? What NUT currently does in `usbhid-ups` (some other drivers may handle similar stuff differently), is it goes through a list of subdrivers built into the binary and calls those

[please use Reply-All - this list does not modify the reply-to header] > On Nov 23, 2016, at 10:30 AM, Craig STCR <craig.stcr1 at gmail.com> wrote: > > 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: > >

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

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

> Is this the current layout? > > nut-website (branch: dll-hll) > \__ nut submodule (branch: master) > \__ ddl submodule (branch unknown?) nut-website (branch: dll-hll) \__ nut submodule (branch: master @ abc0006 [not updated to avoid conflicts when merging back to master]) \__ ddl submodule (branch: master @ bbfd79f; now updated to ab6166c) > The "ddl" branch

Hi Daniele and Arnaud, While tracking down the Cyber Power voltage scaling issue, I found the DDL repository extremely helpful. Instead of searching across all of the old mailing list posts, I was able to run 'git grep' in the Cyber Power directory, and the consistency of the data made it an easy task. I had a motherboard failure on my main computer, and I was trying to recreate the

On Aug 19, 2020, at 6:22 AM, Manuel Wolfshant wrote: > > 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.

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

On Aug 12, 2018, at 11:03 PM, Kevin Mychal M. Ong <kevindd992002 at yahoo.com> wrote: > > 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

On Jun 8, 2016, at 7:47 PM, hyouko at gmail.com wrote: > >> However, this was not an error I was expecting to see when rebuilding: >> >> http://buildbot.networkupstools.org/public/nut/builders/Debian-website/builds/55/steps/shell/logs/stdio >> [...] >> Makefile:796: *** target pattern contains no '%'. Stop. >> >> Any ideas? > >

> The only thing we need to watch out for is when the parameters to printf have '%' embedded in them. Probably not a problem for the DDL, since '%' has special meaning in URLs, but using 'printf %s' should avoid problems down the road. mmh.. if we want to add support for '%'s we could do something like this (not sure if it's worth doing):

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

No, the Battery Temp does not change. It is always 25C. I don't know why the ups.delay.start is that high. Is that user configurable? Yes, I have tested the automatic shutdown. Works well. Yes, the instant commands work, at least those I feel comfortable testing. Battery test work fine. I have not enable the write to variables. Did not know that it might be necessary. John Hart -----

> However, this was not an error I was expecting to see when rebuilding: > > http://buildbot.networkupstools.org/public/nut/builders/Debian-website/builds/55/steps/shell/logs/stdio > [...] > Makefile:796: *** target pattern contains no '%'. Stop. > > Any ideas? I think we don't support colons in names of files and dirs: -

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

On 06/18/2017 05:42 PM, Charles Lepple wrote: > On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant > <wolfy at nobugconsulting.ro <mailto:wolfy at nobugconsulting.ro>> wrote: >> >> running autogen.sh was triggered automatically. but even if I do it >> explicitly, I still get: >> + autoreconf -i >> configure.ac:887: warning: AC_LANG_CONFTEST: no

On Dec 28, 2014, at 4:38 PM, hyouko at gmail.com wrote: > So, I think this can be solved replacing all the occurrences (3) of > 'echo -e' with 'printf' in Makefile.am, see: > https://github.com/zykh/nut-website/tree/issue7 > Does it solve the problem? Are there other hiccups? As expected, printf works for me on OS X 10.9 (Mavericks) as well. The only thing we need to

On 06/19/2017 11:02 AM, Manuel Wolfshant wrote: > Thank a lot ! > Now, conclusions after attempting builds ( with no docs included since > attempting to enable them triggers the errors related to missing or > too old tools mentioned by me in an earlier message ) > - building against libsub 1.0 triggers the following 2 errors : > nutdrv_qx-nutdrv_qx.o: In function