Re: [Nut-upsuser] CyberPower CST150UC: Question re: battery.runtime.low configuration settings

UPS, but this will probably hold true for other values) My guess is that if you sent 520, upsc would return 8 (for a revised maximum of 511 seconds). If not, the UPS is even weirder than most :-) As you found, the ignorelb option is available to work around limitations in the UPS shutdown l

Re: [Nut-upsuser] CyberPower CST150UC: Question re: battery.runtime.low configuration settings

. I'm guessing the maximum is going to be 255. This is not entirely surprising - we have a GitHub issue label specific to CPS for issues with their USB HID protocol implementation. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut

Re: [Nut-upsuser] Are all measurements are in seconds?

of back-and-forth to poll USB HID values that aren't sent automatically whenever the USB interrupt pipe is polled. That said, if you are observing the same value 14x in a row, then changing and holding for another 14x-15x, it is certainly possible that the UPS is not updating its values as freque

Re: [Nut-upsuser] driver.parameter.offdelay vs ups.delay.shutdown / driver.parameter.ondelay vs ups.delay.start

tial value from ups.conf or `-x` command-line flags. For usbhid-ups (and a few other drivers), the offdelay parameter sets ups.delay.shutdown when the driver starts: https://github.com/networkupstools/nut/blob/v2.8.1/drivers/usbhid-ups.c#L1300-L1306 and likewise for ondelay and ups.delay.start. --

Re: [Nut-upsuser] Cyber Power System CP1500 AVR UPS: changing battery.charge.low value [ups.delay.start sidebar]

On Mar 9, 2024, at 6:14 PM, Charles Lepple wrote: > > On Mar 9, 2024, at 5:16 PM, chrib...@duck.com wrote: >> I used the override.ups.delay.start = -1 in nut.conf and this is now being >> reported. The ups.conf man page describes the direction that the data flows with

Re: [Nut-upsuser] Cyber Power System CP1500 AVR UPS: changing battery.charge.low value [ups.delay.start sidebar]

On Mar 9, 2024, at 5:16 PM, chrib...@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@localhost listed this as modifiable but any attempt at > modifying

Re: [Nut-upsuser] NUT 2.8.1 (source build) Pi OS bookworm 32 bit - nut-monitor trying to connect to UPS - Connection Refused

, then monitoring ups-name@localhost will likely not work. You may want to listen on the wildcard 0.0.0.0 address instead of a specific address (helps if the IP is dynamic), or just add "LISTEN 127.0.0.1". -- Charles Lepple clepple@gmail _

Re: [Nut-upsuser] Cyber Power System CP1500 AVR UPS: changing battery.charge.low value

tively), and that might not even be enough. Discussion: https://github.com/networkupstools/nut/issues/432#issuecomment-405371395 and https://github.com/networkupstools/nut/issues/625 -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@

Re: [Nut-upsuser] Cyber Power System CP1500 AVR UPS: changing battery.charge.low value

docs/man/ups.conf.html#_ups_fields -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Keeping the traffis on or off the list ?

server, so I am not volunteering for this job.) [please use Reply-All as we get this all sorted out, thanks. No intentional asides to me; I will instinctively add back the list address as I have been doing manually for years when people email me directly about

Re: [Nut-upsuser] Keeping the traffis on or off the list ?

On Feb 17, 2024, at 7:57 AM, Jim Klimov wrote: > > Other than that, I think the mailing list service we get from alioth comes > "as is", not sure we can configure much about it. Can check, but not really > inclined to - let humans decide how to best post and what is correct for each > case :)

Re: [Nut-upsuser] Keeping the traffis on or off the list ?

ple email me directly about NUT issues.] -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsdev] Cyber Power LE1000DG UPS

things differently, but I don't think I have run across this particular issue (my CPS UPS is currently on a Mac, so I don't see connect/disconnect logs). The usual hardware suggestions are to swap out the USB cable, and try a powered USB hub. -- Charles Lepple clepple@gmail > _

Re: [Nut-upsuser] NUT server with multiple raspberry pi

nly one web GUI. > If you are referring to this tutorial: https://technotim.live/posts/NUT-server-guide/ then on the first Raspberry Pi with the web interface, you should be able to replace "localhost" in "MONITOR upsname@localhost" with the hostname of the second

Re: [Nut-upsdev] RunTimeToEmpty is in minutes or seconds?

On Jan 2, 2024, at 1:49 PM, Kelly Byrd wrote: > > My question for you all is what units ups.powersummary.runtimetoempty is > supposed to be in? This doc from USB.org: > https://www.usb.org/sites/default/files/hut1_4.pdf (Section 31.2) says > minutes, Do you mean the Power Device Class

Re: [Nut-upsuser] Help with CGI upsstats.cgi giving "file not found"

find/load the 32-bit libc on a 64-bit system. - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Help with CGI upsstats.cgi giving "file not found"

On Dec 20, 2023, at 5:17 PM, Tim Reimers KA4LFP via Nut-upsuser wrote: > > First, a summary: > - I have a RasPI (hereafter referred to as Pi1) running Bullseye in which > this all WORKS FINE -- the upsd/upsc/ monitor services, etc > - I have a SECOND RasPI (hereafter referred to as Pi2)

Re: [Nut-upsdev] Minutemen UPS Driver

I think the problem is that there were some communication errors, as noted here: https://github.com/networkupstools/nut/issues/555 I would want to test thoroughly before relying on it for automated shutdowns. -- Charles Lepple clepple@gmail > On Dec 14, 2023, at 8:35 AM, Jim Klimov via

Re: [Nut-upsuser] usbhid-ups not loading with Arduino Leonardo on Ubuntu 23.10

riptors" is likely a result of the driver dropping root privileges, then not having enough permissions to write to the /dev/bus/usb node to request the HID descriptor. I don't know how your VID/PID got into the udev rules file - VID 2341 doesn't show up in the NUT Git source tree.

Re: [Nut-upsuser] had to reinstall on new drive, lost all nut related .conf's

> On Jun 19, 2023, at 8:33 PM, gene heskett wrote: > >>> However, any attempt to add it to the [myups] stanza in ups.conf is a >>> showstopper error. No mention of this "flag" in the rest of the file's >>> comments. >> >> So how does that syntax actually look like? > In ups.conf, you should

Re: [Nut-upsuser] Monitoring a remote UPS

On Jun 9, 2023, at 5:25 AM, Nichole Kaligian via Nut-upsuser wrote: > > Hi, > > Every guide I'm finding is connecting their NUT server to the UPS directly. > Is there no option to monitor a network-attached UPS? On its IP or hostname? > This was my first assumption when looking at a product

Re: [Nut-upsuser] Using 'dummy.ups' for a real application, not just testing...

of this file to the NAS. I think the NAS is probably only looking at ups.status (OL/OB/LB) to trigger shutdown (barring any custom "shut down when variable X gets below a threshold), but it certainly can't hurt to publish the other values if you have something to log them. -- Charles

Re: [Nut-upsuser] Init SSL without certificate database

> On Jan 28, 2023, at 6:14 PM, Jim Klimov via Nut-upsuser > wrote: > > and I have a hard time guessing what distro might ship a "driver.version: > DSM7-1-1-42930-workplus-version2-repack-42930-220712". Ask them what NUT > version (release or snapshot) they use, and if they would consider

Re: [Nut-upsuser] Problem with Multiple USB UPSs, including multiple apparent CyberPower

building from Git sources, which will include the more recent PRs that Jim mentioned: https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu <https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu> -- Char

Re: [Nut-upsuser] battery.voltage Powercom Macan MRT-3000

Please email nut-upsuser@alioth-lists rather than nut-upsuser-owner, thanks! > On Jan 10, 2023, at 12:58 PM, Alex Rydzewski wrote: > > Yes, You right) battery.voltage > > I found these data among other > >0.522942 [D5] hid_lookup_path: 00840004 -> UPS >0.522950 [D5]

Re: [Nut-upsdev] Can we just import apcupsd code?

On Jan 4, 2023, at 5:02 PM, Ted Mittelstaedt via Nut-upsdev wrote: > > But instead of that NUT elected to write a shim that spawns apcuspd. > Technically, it doesn't launch apcupsd, the driver connects to an existing apcupsd instance. And the shim (apcupsd-ups) was contributed by a user.

Re: [Nut-upsuser] confusion about shutdown

On Dec 30, 2022, at 7:42 PM, Greg Troxel wrote: > > maybe me, maybe docs. > > I have never had auto shutdown set up on netbsd. Mostly I monitor to > mqtt. But now I'm trying and have multiple confusions. > > 1) 'upsdrvctl shutdown' vs 'upscmd shutdown.return' > > upsdrvctl is about stopping

Re: [Nut-upsuser] Shutdown variables

On Nov 27, 2022, at 8:21 PM, Simon Wilson via Nut-upsuser wrote: > > "[replbatt] The UPS needs to have its battery replaced. Not all UPS's can > indicate this." > > Can anyone advise whether the Eaton USB UPSs support that? Specifically mine > is a 5SX 1750. I don't know for the 5SX line in

Re: [Nut-upsuser] Building a Custom UPS with NUT Compatibility

"upside" project in a while, so not sure if it will provide a good starting point. If nothing else, there might be some good UPS engineering information in the wiki: https://gitlab.com/esr/upside -- Charles Lepple clepple@gmail > On Sep 16, 2022, at 3:34 PM, Joshua Quesenberry vi

Re: [Nut-upsuser] dual cyberpower 2200 on windows

On Aug 11, 2022, at 10:46 PM, Richard Ward wrote: > > Thanks Charles, > > The devices are the same make and model, bought at the same time. both return > the following when running upsc, and I cant see any way to distiguish the 2 > apart. Any suggestions, other than to connect them to

Re: [Nut-upsuser] dual cyberpower 2200 on windows

On Aug 11, 2022, at 10:06 AM, Richard Ward wrote: > > I need to specify the usb port in the ups.conf file, but I cannot work out > how to find the path for each ups to fill in the port = section. If I leave > it as port = auto, then only 1 unit can be monitored at a time. > as the

Re: [Nut-upsuser] Where is nut-scanner on raspberry pi?

;lsusb -d 51d:" flag filters for APC's vendor ID.) # ups.conf [apc] driver = usbhid-ups port = auto serial = "3S1746X05384" desc = "Basement" -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing l

Re: [Nut-upsuser] NUT can't connect to USB UPS on OpenBSD

On Aug 10, 2022, at 9:15 PM, Marc-André Harbec via Nut-upsuser wrote: > # These are all the USB devices on my machine > ❯ doas ls -l /dev/usb* > crw-r- 1 root usb 61, 0 Jun 24 16:21 /dev/usb0 > crw-r- 1 root usb 61, 1 Jun 24 16:21 /dev/usb1 > crw-r- 1 root usb 61, 2

Re: [Nut-upsuser] Where is nut-scanner on raspberry pi?

On Aug 10, 2022, at 9:05 PM, z.kevino--- via Nut-upsuser wrote: > > VERSION="9 (stretch)" > VERSION_CODENAME=stretch > stretch is getting pretty old now - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921379 appears to have been fixed in 2019. The output of nut-scanner should mostly be

Re: [Nut-upsdev] Compatibility question

On Jul 17, 2022, at 4:09 PM, Al M via Nut-upsdev wrote: > > Should this APC UPS be compatible with NUT? Could not find it on the > compatible list. > > This description from Amazon: > APC UPS Battery Backup and Surge Protector, 600VA Backup Battery Power > Supply, BE600M1 Back-UPS It would

Re: [Nut-upsuser] Info on Cyber Power CP1500AVRLCDa

_Systems/CP1500AVRLCDa.html and if I understand Phil's post correctly, he is referring to this firmware issue regarding ups.delay.start: https://github.com/networkupstools/nut/issues/625 Updates to the DDL can be requested here: https://github.com/networkupstools/nut-ddl/issues -- C

Re: [Nut-upsuser] Debian Bullseye Package

> On May 31, 2022, at 10:57 AM, Brandon Wright via Nut-upsuser > wrote: > > Hello, > > I have my 2.7.4 server running, but wanting to update to the 2.8 version to > make use of the many updates and hard work that has been done. Curious if > there has been any updates or a timeframe for the

Re: [Nut-upsdev] a few build nits

On Mar 31, 2022, at 9:18 AM, Greg Troxel wrote: > > I see your point about distcheck. I tend to build tarballs from source > to then use in pkgsrc (not that I publish those tarballs and packages), > to be able to debug the combination of upstream and pkgsrc to be ready > for a release. I can

Re: [Nut-upsuser] finding a common abstraction for reporting

org/docs/user-manual.chunked/apcs02.html -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsdev] On retiring some terminology

On Mar 12, 2022, at 11:51 AM, Ted Mittelstaedt via Nut-upsdev wrote: > > 11 post over the last year on this topic. Lots of effort expended on a WOKE > problem far more than effort expended on real issues that actually affect > code functionality. My condolences. > Ted, this project doesn't

Re: [Nut-upsuser] Incorrect output.voltage readings : CyberPower AVRG900LCD UPS

pen+label%3A%22CyberPower+%28CPS%29%22 <https://github.com/networkupstools/nut/issues?q=is:issue+is:open+label:%22CyberPower+(CPS)%22> -- Charles Lepple clepple@gmail > On Mar 8, 2022, at 7:04 PM, James N. Grace via Nut-upsuser > wrote: > > nut 2.7.4 > Ubuntu Linux 21.10 >

Re: [Nut-upsuser] NUT Client Not Working, Server OK

[please keep the list CC'd - probably easiest via Reply-All] On Jan 28, 2022, at 10:20 AM, William Cole wrote: > However, when executing sudo service nut-client on the Client PC, still > getting a Connection refused message: > > upsmon[491] UPS [APCES750Client@192.168.1.101]:connect failed:

Re: [Nut-upsuser] NUT Client Not Working, Server OK

On Jan 26, 2022, at 3:01 PM, William Cole via Nut-upsuser wrote: > > Thank you for your reply and help. > > I admit to still learning how to use NUT. > > My general NUT-use plan is as follows: the NUT server Pi controls a number of > network devices; router, VoIP, mesh pod, fiber connection,

Re: [Nut-upsuser] NUT Client Not Working, Server OK

aiting for everyone else to get on the life rafts safely (or the captain goes down with the ship). If you do not want to create extra dependencies between the two Pis, each can have a "master" entry in its upsmon.conf that points to the directly-connected UPS. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Can NUT handle a laptop battery?

On Jan 8, 2022, at 12:38 PM, Goran Vukoman wrote: > > The Pine64 ARM boards have a battery connector, not quite a laptop, but AFAIK > the board will charge and use the battery as fallback if lights go out. It looks like the Pinebook Pro has a /sys/class/power_supply driver:

Re: [Nut-upsuser] issue SHUTDOWNCMD from a slave

On Nov 29, 2021, at 11:58 AM, Ken Brubacher wrote: > > Is it possible to issue a SHUTDOWNCMD command from a slave or only from a > master? > > The scenario is a Dell R740 hypervisor, and I’d like NUT server to run as a > virtual machine on it, and shut down the host from the virtual machine

Re: [Nut-upsuser] UPS Monitor Won't Start: invalid directive monitor

On Nov 21, 2021, at 9:28 PM, Jarrod Coombes via Nut-upsuser wrote: > > When I try to start the UPS monitor service I get: > > Starting Network UPS Tools - power device monitor and shutdown controller... > fopen /run/nut/upsmon.pid: No such file or directory > /etc/nut/upsmon.conf line 86:

Re: [Nut-upsdev] Cross-compiling for OpenWRT on Debian - neon libraries error

On Sep 16, 2021, at 6:30 AM, Seb Belcher via Nut-upsdev wrote: > > Bit of a noob question I'm sure but would appreciate the help. The nut > package maintained for OpenWRT does not include the netxml drivers that I > need for my UPS, so I'm embarking on something a little outside my comfort

Re: [Nut-upsuser] Empty readings from sensors (MEC0003)

On Aug 13, 2021, at 7:32 AM, Manuel Wolfshant wrote: > >> [...] 2.135215 read: (000.0 000.0 000.0 000 00.0 0.00 00.0 > As far as I can see, the UPS is sending exclusively zeroes so there isn't > much that the drivers could do. > I agree that the logs seem to be showing that the

Re: [Nut-upsuser] permanently setting "battery.charge.low" on APC Back-UPS RS 550G

On Jun 29, 2021, at 12:27 PM, Roger Price wrote: > > On Tue, 29 Jun 2021, Ralf Fassel via Nut-upsuser wrote: > >> OS Ubuntu 20.04.2 LTS >> Network UPS Tools 2.7.4 (Debian Package nut-client 2.7.4-11ubuntu4) >> >> device.mfr: American Power Conversion >> device.model: Back-UPS RS 550G >> >>

Re: [Nut-upsuser] Random output of a LIST ENUM command ?

On Jun 19, 2021, at 10:25 AM, Roger Price wrote: > > The ENUM entries are not in ascending order. Does this mean that the output > is in random order?, or is there some other logic? Similar to the LIST RANGE email, I don't have a good citation for this, but my understanding is that this was

Re: [Nut-upsuser] Discontinuous output of a LIST RANGE command ?

nput.transfer.low > Roger > > _______ > Nut-upsuser mailing list > Nut-upsuser@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Tripp Lite model number AVR900U didn't change, but USB product ID did

On May 8, 2021, at 11:46 PM, Paul Nickerson via Nut-upsuser wrote: > > I'm running Raspbian GNU/Linux 10 (buster) on a Raspberry Pi 4. > I have nut-client and nut-server version 2.7.4-8 armhf installed from the > Raspbian Buster main apt repository. > I have a Tripp Lite AVR900U series AG-0309

Re: [Nut-upsuser] How to reset "Shutting Down" Status in Tray-App without re-Starting the monitoring (WIN 7) Computer?

On May 4, 2021, at 12:50 PM, Jürgen Wege via Nut-upsuser wrote: > > It also keeps the old date for "STARTTIME". You mentioned apcupsd earlier. STARTTIME is not a NUT variable, and I don't think NUT ever had a system tray application (though maybe one of the third-party Windows ports did), so

Re: [Nut-upsuser] ONLINE + LOWBATT shutdown

se VMs with dummy-ups drivers to test some of these potential solutions. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Liebert GXT4

On Mar 3, 2021, at 7:43 AM, Matthew Rivett via Nut-upsuser wrote: > > Charles, > > Being me I'd love to have all the data but that shouldn't be necessary. :) That's fair :-) > What got me interested is that the frequency is shown on the UPS and I was > curious what was going on when the

Re: [Nut-upsuser] Liebert GXT4

to debug the 0.0 values, it would be useful to increase the driver debug output level from -D2 to -D3. That includes the raw bytes from the UPS. Also, what other variables are you looking for? (Previous Liebert GXT units have not provided as many measurements as other UPSes.) -- Charles Leppl

Re: [Nut-upsuser] Overriding battery.runtime.low

On Feb 24, 2021, at 4:02 AM, Peter Bishop via Nut-upsuser wrote: > > I have an APC BR1500GI and want to run my devices for the longest possible > period. Consequently I want to use the battery.runtime.low setting, > sufficient to allow my devices to shutdown. The APC has a setting of 5 >

Re: [Nut-upsuser] warning in hasss.io

On Feb 20, 2021, at 2:02 PM, Charles Lepple wrote: > > On Feb 20, 2021, at 8:54 AM, enzo fn via Nut-upsuser > wrote: [...] >> on rasberry pi4 >> this is in my supervisor log: >> 21-02-20 11:38:31 WARNING (MainThread) [supervisor.addons.validate] Add-on >&

Re: [Nut-upsuser] warning in hasss.io

On Feb 20, 2021, at 8:54 AM, enzo fn via Nut-upsuser wrote: > > hassio vers.core-2021.2.3 > Nut vers. 0.6.2 That is an unfortunate choice of names, but you are probably referring to this hassio add-on that uses Network UPS Tools: https://www.home-assistant.io/integrations/nut You probably

Re: [Nut-upsuser] Why do ondelay and offdelay parameters break the NUT driver?

On Feb 12, 2021, at 1:25 PM, Shilov via Nut-upsuser wrote: > > Ok, what needs to be done to make this parameter fit for this driver? Someone would need to add the necessary command to send the ondelay value, if it is implemented by the UPS. Protocols are posted here:

Re: [Nut-upsuser] Why do ondelay and offdelay parameters break the NUT driver?

On Feb 11, 2021, at 10:45 AM, Shilov via Nut-upsuser wrote: > > └─557 /lib/nut/powercom -a myserver > ... > фев 11 17:23:48 myserver upsdrvctl[531]: Network UPS Tools - PowerCom > protocol UPS driver 0.17 (2.7.4) > фев 11 17:23:48 myserver upsdrvctl[531]: Fatal error: 'ondelay' is

Re: [Nut-upsuser] New User Questions (again) - With Belkin USB

On Jan 23, 2021, at 1:07 PM, David White via Nut-upsuser wrote: > > I did the chmod myself thinking that there might be some odd > access/permission problem and will change it back since that hasn't changed > diddly. > > ls -l /dev/bus/usb/001/003 shows: > crw-rw. 1 root aid_usb 189, 2

Re: [Nut-upsuser] An RFC for the NUT project

On Jan 23, 2021, at 8:18 AM, Roger Price wrote: > > IETF and IANA require that protocols on ports assigned by IANA be documented > with RFC's. We do not currently have an RFC for port nut/3493. To solve > this IANA port administration issue, I propose the text >

Re: [Nut-upsuser] New User Questions (again) - With Belkin USB

is in newer versions of NUT, but with 2.7.1 and an Ubuntu-like filesystem layout, it would be something like this (assuming the UPS name is still belkinusb in /etc/nut/ups.conf): /lib/nut/blazer_usb -a belkinusb -DD -- Charles Lepple clepple@gmail __

Re: [Nut-upsuser] New stable release of NUT after 2.7.4?

On Jan 10, 2021, at 8:29 AM, Dan Langille via Nut-upsuser wrote: > > On Sun, Jan 10, 2021, at 8:12 AM, Jim Klimov wrote: >> On January 10, 2021 11:12:48 AM UTC, Victor Hooi via Nut-upsuser >> wrote: >>> Hi, >>> >>> The last release of NUT seems to be 2.7.4, from 2016. >>> >>> However, from

Re: [Nut-upsuser] What does ENUM mean?

case for usbhid-ups: https://github.com/networkupstools/nut/issues/134 -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] How to handle flags as status?

On Dec 29, 2020, at 9:54 AM, Shakil Shaikh via Nut-upsuser wrote: > > Are clients therefore supposed to list all possibilities, or split on space > to get the flags back? > Clients should split on space. I remember we had a better description of this from the protocol perspective, but that

Re: [Nut-upsdev] Does Cyberpower BR1000ELCD work?

On Dec 28, 2020, at 10:01 AM, Mike Ricketts wrote: > > Hi > > I am considering buying a Cyberpower BR1000ELCD UPS. > > https://www.cyberpower.com/uk/en/product/series/brics_lcd > > It does not appear on the HCL, but other Cyberpower USB models do. > > The specs claim it has a HID-compliant

Re: [Nut-upsuser] APC Back-UPS 1500 RS - looking for help with strange behaviour

On Oct 31, 2020, at 5:40 PM, David Butler wrote: > > Hi All, > > hoping someone might have some insights to what is going wrong with my NUT > setup and my APC Back - UPS RS 1500 (specifically a BR1500GI) using the > usbhid driver. > >

Re: [Nut-upsuser] upsd "events"

On Nov 7, 2020, at 11:18 AM, Jason Antman wrote: > > Hello, > > I'm quite new to NUT, currently setting it up on a few machines in my home > lab because I switched from an APC UPS to a CyberPower unit. This is running > in a home lab, and I'm trying to implement some apparently unusual logic

Re: [Nut-upsuser] ups.test.result meaning

On Oct 31, 2020, at 10:53 PM, Charles Lepple wrote: > > On Oct 31, 2020, at 8:30 PM, Gene Heskett wrote: >> >>> battery.voltage: 16.0 >> At that voltage, 5 of the 12 cells are shorted >>> battery.voltage.nominal: 24 > > The 16.0 is a scaled version of

Re: [Nut-upsuser] ups.test.result meaning

On Oct 31, 2020, at 8:13 PM, Rick Dicaire wrote: > > On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson > wrote: > I'm going to guess that since your test runtime of 305 is very close to the > low limit of 300, that's the warning. Not yet a fail, but very, very close. >

Re: [Nut-upsuser] ups.test.result meaning

On Oct 31, 2020, at 8:30 PM, Gene Heskett wrote: > >> battery.voltage: 16.0 > At that voltage, 5 of the 12 cells are shorted >> battery.voltage.nominal: 24 The 16.0 is a scaled version of the fixed (bogus) 24.0 V reading, similar to this unit:

Re: [Nut-upsuser] NUT Installation Issue

On Oct 31, 2020, at 5:36 PM, bobby wrote: > > Fatal error: 'maxretry' is not a valid variable name for this driver. https://networkupstools.org/docs/man/ups.conf.html 'maxretry' is in the global section, which needs to come before the UPS/driver-specific sections

Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

On Oct 30, 2020, at 12:22 AM, Gene Heskett wrote: > > On Thursday 29 October 2020 22:12:00 Charles Lepple wrote: > >> On Oct 28, 2020, at 9:56 PM, Gene Heskett wrote: >>> Which looks very incomplete to me. OTOH, its not a very big UPS but >>>

Re: [Nut-upsuser] NUT Installation Issue

On Oct 30, 2020, at 3:00 PM, bobby wrote: > > I installed NUT on my raspberry pi. I've been following this tutorial: > https://melgrubb.com/2016/12/11/rphs-v2-ups/. I am trying to use NUT to > monitor my cyberpower UPS. I seem to have this problem though: upsc > cyberpower@localhost Init

Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

On Oct 31, 2020, at 8:42 AM, Robert Stocker wrote: > > I successfully changed my UPS name and after a reboot, things seems to be > well on their way. Do I need to worry about this line in the upsc results: > > Init SSL without certificate database

Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

On Oct 29, 2020, at 2:44 PM, Robert Stocker wrote: > > Sorry for the delay. Here are my outputs, but first a quick question: am I > right in thinking I can change the name of my ups simply by editing ups.conf? > That script I ran from the Pi forum used that name, and I don't care for it. >

Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

On Oct 28, 2020, at 9:56 PM, Gene Heskett wrote: > > Which looks very incomplete to me. OTOH, its not a very big UPS but > neither is the pi. I have tested that, and it shuts off long before it > outouts a LB signal. Which part looks incomplete, the variables or the commands? Even the

Re: [Nut-upsuser] NUT uses port 3493 for everything

On Oct 24, 2020, at 3:20 PM, Roger Price wrote: > > The NUT project uses port 3493 to receive traffic to the upsd server. Unlike > the protocols http (80) and https (443), NUT has no specific port for > encrypted traffic. For the upsdTLS.py daemon. I squatted port 563, but it > would be much

Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

On Oct 27, 2020, at 2:45 PM, Robert Stocker wrote: > > Thanks so much for all the help! It looks like at present I've at least got a > working configuration that I need to test and fine-tune, am I interpreting > this correctly? Yes. If you're good with the default NUT behavior of shutting

Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

On Oct 26, 2020, at 9:38 AM, Gene Heskett wrote: > >>> battery.voltage: 24.0 >>> battery.voltage.nominal: 24 >> >> I don't have the citation handy, but I think another user reported >> that the battery.voltage returned by the UPS is a constant 24.0 V, >> regardless of the actual battery

Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

On Oct 26, 2020, at 9:01 AM, I wrote: > >> battery.voltage.nominal: 24 > > I don't have the citation handy, but I think another user reported that the > battery.voltage returned by the UPS is a constant 24.0 V, regardless of the > actual battery voltage. Here's what I was thinking of:

Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

On Oct 26, 2020, at 9:01 AM, I wrote: > >> battery.voltage: 24.0 >> battery.voltage.nominal: 24 > > I don't have the citation handy, but I think another user reported that the > battery.voltage returned by the UPS is a constant 24.0 V *another user reported that CyberPower support said the

Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

On Oct 25, 2020, at 11:52 AM, Robert Stocker wrote: > > Init SSL without certificate database > battery.charge: 100 > battery.charge.low: 10 > battery.charge.warning: 20 > battery.mfr.date: CPS > battery.runtime: 15690 > battery.runtime.low: 300 > battery.type: PbAcid > battery.voltage: 24.0 >

Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

On Oct 23, 2020, at 11:06 AM, Robert Stocker wrote: > > Thanks again for your patience. I'm still learning how to deal with systemctl > myself (and starting from, I'm sure, a much lower level of understanding), so > if I've neglected to restart or start something, please let me know. > > I

Re: [Nut-upsuser] Can't get CyberPower UPS to work with Raspberry Pi 4

On Oct 21, 2020, at 3:27 PM, Robert Stocker wrote: > > Operating System: Raspbian GNU/Linux 10 (buster) > Kernel name & release: Linux 5.4.51-v7l+ > Kernel version:#1333 SMP Mon Aug 10 16:51:40 BST 2020 > > exact NUT version: > Network UPS Tools 2.7.3, according to

Re: [Nut-upsuser] [EXTERNAL] Is there a new way to search the listserv archives?

On Oct 20, 2020, at 3:44 PM, David Zomaya wrote: > I see the link here, but clicking it results in a 404. Before I waste everyone's time posting my question, I really wanted to search to see if it's been solved already. > > I don't know of a baked-in official method, but the

Re: [Nut-upsuser] Multi UPS Monitoring

On Oct 9, 2020, at 8:07 PM, Rusty Bower wrote: > > Hey all, > > I've read through as many relevant mailing list posts and public blog posts > as I could, but I can't seem to find an answer to my issue. > > I currently have 2x Tripp Lite SMART1500LCDXLs, and I am attempting to > monitor both

Re: [Nut-upsuser] ups not being started sat reboot

On Sep 5, 2020, at 5:23 AM, Roger Price wrote: > > On Sat, 5 Sep 2020, Gene Heskett wrote: > >> But runs normally if started. On a rpi4 running an uptodate raspbian >> buster, how do I set it to auto start at boot time? > > Hello Gene, By "auto start" I assume you mean the automatic power on

Re: [Nut-upsuser] Device recommendation Salicru

On Aug 19, 2020, at 8:20 AM, Charles Lepple wrote: > > Getting back to Marc's original question, this is all we have collected for > Salicru: https://github.com/networkupstools/nut-ddl/tree/master/Salicru > > That is not to say that other models don't work, but that information w

Re: [Nut-upsuser] Device recommendation Salicru

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

Re: [Nut-upsuser] Eaton 5E 1100i USB UPS - failed to claim USB device error

On Aug 19, 2020, at 6:00 AM, Louis van Dyk wrote: > > @DEVS: Could you please re-add the code for using this UPS? It's > still being sold fast and furious in our region, and I'm sure more > people are having the same problem. Kernel quirks need to be added back by the kernel developers.

Re: [Nut-upsuser] Synology NAS is shutting down Ubuntu servers after very brief power outage (fwd)

On Aug 12, 2020, at 5:32 PM, Todd Benivegna wrote: > >> Those LISTEN lines were appropriate pre-systemd when NUT's startup script >> was launched after networking was fully enabled. I would recommend "LISTEN >> 0.0.0.0 3493" instead, and use firewall rules if you are trying to exclude >> an

Re: [Nut-upsuser] Synology NAS is shutting down Ubuntu servers after very brief power outage (fwd)

On Aug 12, 2020, at 12:11 AM, Todd Benivegna wrote: > > Here is my upsd.conf: > > LISTEN 127.0.0.1 3493 > LISTEN 192.168.1.31 3493 > Those LISTEN lines were appropriate pre-systemd when NUT's startup script was launched after networking was fully enabled. I would recommend "LISTEN 0.0.0.0

Re: [Nut-upsuser] Synology NAS is shutting down Ubuntu servers after very brief power outage (fwd)

On Aug 9, 2020, at 3:18 PM, Todd Benivegna wrote: > > Now they will spin-up on their own, but it takes 5-10 seconds. My thought > was if they can’t communicate initially, they assume the server is dead and > shut down. Would that make sense at all? Sorry to jump in the middle here, but

Re: [Nut-upsuser] Low Battery Problems

On Jun 22, 2020, at 3:42 PM, Gene Heskett wrote: > > pi@rpi4:~ $ sudo nano /etc/nut/upsd.users > pi@rpi4:~ $ upscmd myups test.battery.start.deep You'll need a "sudo upsd -c reload" in between editing the users file and trying a new command. https://networkupstools.org/docs/man/upsd.html

Re: [Nut-upsuser] Low Battery Problems

On Jun 22, 2020, at 3:36 PM, Charles Lepple wrote: > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: >> >> So I just edited /etc/nut/upsd.users to add both the commands it claims >> to have but get this response to either: > > In your original example, you

Re: [Nut-upsuser] Low Battery Problems

On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: > > So I just edited /etc/nut/upsd.users to add both the commands it claims > to have but get this response to either: In your original example, you had multiple “instcmd =“ lines for one user- I think the allowed commands all need to be listed

  1   2   3   4   5   6   7   8   9   10   >