similar to: [HCL] Cyber Power Systems CP600LCD supported by usbhid-ups

Greetings: I'm evaluating two replacements for UPS upgrades to my dept. Because the CyberPower OP650 has been retired, we are evaluating the CyberPower600VA and the CyperPower 1000AVRLCD. We will be evaluating others. Initial configuration and communications are established via the usbhid-ups driver, the gambit of tests are all passed with the exception of one. I seem to be failing

Hello, I've been trying to set this UPS up on a Synology NAS DS218+ which uses NUT, and even though they are using NUT, they don't have all drivers available as NUT has them at NUT's website. Please see that below: root at DSAltaCloud:/usr/syno/etc/ups# upsdrvctl start Network UPS Tools - UPS driver controller DSM6-2-1-newmodel-repack-23796-180722 Network UPS Tools - Generic HID

Hi, Context of my question: * OS name and version, Synology's distributed Linux: Linux DS 3.10.102 #15152 SMP Fri Sep 1 11:15:03 CST 2017 x86_64 GNU/Linux * exact NUT version, Tricky... the installed tools display: $ /usr/sbin/upsd -V Network UPS Tools upsd DSM6-1-15114-170518 while the one I've compiled, and its not running, displays: $ /opt/sbin/upsd -V Network UPS Tools upsd

Greetings; I have been trying to set Samba on the latest release of Fedora to share some files on my office network. Here is my smbd.conf file: #======================= Global Settings ===================================== [global] workgroup = Maison server string = Linux netbios name = Linux encrypt passwords = yes wins support = yes [data] path = /data browseable = yes

Ok guys, So we just had a storm roll through and of course we lost power for just a split second.  This time I was actually home for it.  Sure enough, the servers shutdown and wouldn’t boot all the way up until I restarted my Synology.  I grep’d the syslog and here’s the results: > proton at proton:~$ sudo grep upsmon /var/log/syslog > Aug  6 19:19:09 proton upsmon[1552]: UPS ups at

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

Hi all, Am setting up a internet cyber cafe of roughly 50 or so boxes running on CentOS 5.0. Now the question is. Does someone on the list know of a open source cyber timer/cybermanager which runs on CentOS(LINUX) and where i can download it? All that am getting are M$ based.(grrrh). Thanks. ------------------------------------------------- David Maina. Systems/Network Administrator. PdE-Kenya.

I'm currnetly using NUT 2.4.3 to monitor a Cyber Power 1000AVRLCD UPS. I found the following in the mailing list archive: http://lists.alioth.debian.org/pipermail/nut-upsdev/2010-March/004673.html and I want to inform the list that I had to apply the same patch to libhid.c in order to monitor that UPS. -spc

CyberPower Battery Backup with Surge Protection, model LE825G Appears to function properly with the driver listed on the HCL for the Cyber Power Systems ups 2 685AVR USB (usbhid-ups). Tested with shutdown mode "UPS Goes On Battery" with a 5 second timer and the system successfully shutdown as expected. upsc output: upsc ups battery.charge: 100 battery.charge.low: 10

[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: > >

Cyber Power UPS Model LX1500GU *upsc output:* root at freenas:~ # upsc ups at localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 5670 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 24.0 battery.voltage.nominal: 24 device.mfr: CPS device.model: LX1500GU device.serial: QAKGP2000252 device.type: ups driver.name:

On Dec 8, 2016, at 1:34 PM, Mike wrote: > > I didn't want to sign up for the nut-devs list or create a git account > just to provide this information, so I hope posting this info here is OK... Not a problem. (Both lists go into the same mailbox on my end.) The important part is the "HCL" subject so I can find it later. For anyone else who runs across this: you don't

Mike, Thanks for the info. I have enough to add an entry to the DDL, but I have a few more questions inline. On May 14, 2017, at 1:21 PM, Mike wrote: > > [updated] > > OpenBSD 6.1/amd64 > NUT 2.7.4p0 (from OpenBSD package) > > > Results of upsc: > > battery.charge: 100 > battery.charge.low: 10 > battery.charge.warning: 20 > battery.mfr.date: CPS Let

On Jun 5, 2017, at 11:21 AM, Mike <the.lists at mgm51.com> wrote: > > Result of the command, where "n" is incremented in a loop: > > # usbconfig -u 1 -a 2 dump_string n > STRING_0x00 = 0x04, 0x03, 0x09, 0x04 > STRING_0x01 = <CP1500AVRLCDa> > STRING_0x02 = <CTHGN200xxxx> > STRING_0x03 = <CPS> > STRING_0x04 = <PbAcid> >

On Mon, 4 Mar 2024, Alan C. Bonnici via Nut-upsuser wrote: > Platform: Proxmox VE 8.1.4 > NUT version: Network UPS Tools upsstats 2.8.0 > > I configured Proxmox and I can pull up the UPS stats. > Typing in `upsrw -l cyberpower at localhost` I get the following: > > [battery.charge.low] > Remaining battery level when UPS switches to LB (percent) > Type: STRING >

Thanks Charles for the clarification. If NUT cannot control it then removing it would, IMO add value. On Sun, 10 Mar 2024 at 00:14, Charles Lepple < clepple_at_gmail.com_chribonn at duck.com> wrote: > On Mar 9, 2024, at 5:16?PM, chribonn at duck.com wrote: > > > > The posting at > https://github.com/networkupstools/nut/issues/432#issuecomment-405371395 > references

Very good point. I hope to write a beginners guide -- more like adopting my notes --on NUT. I could summarise your point that technically one should only override settings that NUT can act upon (like those settings that control Low Battery or, as stated in the documentation if the reported value is known to be incorrect. Overriding a variable that is out of scope for NUT (as with

Wow :-) I'll have a read through it. On Sun, 10 Mar 2024 at 15:54, Roger Price < roger_at_rogerprice.org_chribonn at duck.com> wrote: > On Sun, 10 Mar 2024, Alan via Nut-upsuser wrote: > > > Very good point. I hope to write a beginners guide -- more like > adopting my > > notes --on NUT. > > I did the same thing, 131 pages, at >

On Dec 9, 2016, at 11:14 AM, Mike <the.lists at mgm51.com> wrote: > > On 12/8/2016 10:37 PM, Charles Lepple wrote: >> On Dec 8, 2016, at 1:34 PM, Mike wrote: >>> The result of the command >>> >>> upscmd -u user -p password myups load.off.delay 300 >>> >>> is an immediate power-off, no delay. >> >> Hmm. Certainly

On Mar 9, 2024, at 5:16?PM, chribonn at duck.com wrote: > > The posting at https://github.com/networkupstools/nut/issues/432#issuecomment-405371395 references ups.delay.start and suggests setting it to -1. > > upsrw -l pve1 at localhost listed this as modifiable but any attempt at modifying the value failed. I used the override.ups.delay.start = -1 in nut.conf and this is now being