Re: [Nut-upsuser] Permissions error

On Jun 10, 2024, at 7:22 PM, Jack McGee wrote: > > mythuser@amethi:~$ upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.4 > Can't open /etc/nut/ups.conf: Can't open /etc/nut/ups.conf: Permission denied If you are sure the driver is not running (unclear from "eliminating the no

Re: [Nut-upsuser] UPS not Shutting Down

On Jun 2, 2024, at 12:14 PM, Roger Price wrote: > >> Is the comment about offdelay (in red) correct / can this line be >> eliminated?. > > My understanding is "yes", but others may have deeper knowledge. I don't have a ton of direct experience with this post-v2.7.4, but someone else wrote

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

On Apr 24, 2024, at 3:45 PM, tim.o via Nut-upsuser wrote: >> Have you tried any other values? 3600 is hex 0xe10, and 16 is 0x10, so it is >> quite possible the UPS is using an 8-bit field to store battery.runtime.low. >> I'm guessing the maximum is going to be 255. >> > I am not sure I

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

> On Apr 23, 2024, at 3:51 PM, tim.o via Nut-upsuser > wrote: > > The value changed to battery.runtime.low: 16, instead of 3600. I don't > understand why, because executing the command resulted in SUCCESS. Unfortunately, the SUCCESS response is just saying that upsrw was able to send that

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

On Mar 14, 2024, at 11:09 AM, Alan via Nut-upsuser wrote: > > Hi, > > I am studying (in a few months I might go on a TV quiz show :-) > Rodger's excelent guide and wanted to confirm that all measurements in > NUT are in seconds. all timing measurements are in seconds, yes. > For example, the

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

On Mar 14, 2024, at 11:41 AM, Alan via Nut-upsuser wrote: > Hi, > > My Cyber Power reports these two values. Each pair has the same value. > > Would they normally be the same thing? Without any intervening `upsrw` changes, yes. `driver.parameter.*` corresponds to the initial value from

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 override.*: > Use 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

On Mar 8, 2024, at 8:22 AM, Dan Grostick via Nut-upsuser wrote: > > I've installed 2.8.1 on a Raspberry PI 5 using Pi OS bookworm 64 bit (Debian > 12) with success. > > When I take that same configuration to a PI 3B running bookworm 32 bit, > compile from source, use the same files from

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

On Mar 8, 2024, at 7:07 AM, Roger Price wrote: > > Perhaps setting lowbatt = 50 in ups.conf would help. Roger, good point. That option is missing in the usbhid-ups man page, so I logged an issue to remind us to fix that: https://github.com/networkupstools/nut/issues/2356 Since I am used to

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

On Mar 4, 2024, at 3:23 PM, Alan C. Bonnici via Nut-upsuser wrote: > > I would like to push up the shutdown process to initiate when the ups is at > 50% rather than 10% mainly because there is a need to down other servers. > Some UPSes have a limited range for adjusting the LB threshold, or

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

On Feb 17, 2024, at 11:17 AM, Greg Troxel wrote: > > I would guess that reply-to is getting added because of header munging. > Turn off munging and this all goes away. Please re-read my email that explains the current setup of the list:

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 ?

On Feb 17, 2024, at 3:29 AM, Roger Price wrote: > > Note that the Reply-To goes back to the original poster, not the list. > Many mailing lists encourage the subscribers to "keep the list traffic on the > list", rather than wandering off into private discussions. The nut-upsuser > setup has

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

On Jan 9, 2024, at 8:19 PM, Claudio Zanetta Penna via Nut-upsuser wrote: > > My problem is that I want to connect a second Raspberry to the first one with > NUT server on it, so the information obtained by the second can be sent to > the server > and be presented in only one web GUI. > If

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

On Dec 21, 2023, at 1:13 PM, Tim Reimers KA4LFP wrote: > Yet, a "file" command shows it to be an 32-bit ELF executable. > Although you mentioned that they are both running Debian bullseye, Pi2 is 64-bit capable, and it looks like the Raspbian image is 64-bit (aarch64 in the /lib pathnames).

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-upsuser] usbhid-ups not loading with Arduino Leonardo on Ubuntu 23.10

> On Oct 29, 2023, at 9:25 PM, Kelly Byrd wrote: > > I have seen reports of folks claiming this just worked for them out of the > box, Here you're referring to just making things work on Windows or macOS, right? I don't think it will be quite as simple with NUT, mostly because the NUT drivers

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...

> On Feb 19, 2023, at 8:18 AM, Tom via Nut-upsuser > wrote: > > Good Morning, > > I am working on setting up a 12V DC UPS that will power a NAS and a router > for a few hours. It contains some lithium-ion batteries, and a BMS to > control charging. Since it is just a dumb box with

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

On Jan 14, 2023, at 6:51 PM, Bruce Pleat via Nut-upsuser wrote: > > (Any clue how to get 2.8 included in the package provider for my Raspberry Pi > is presumably beyond the scope of this list, but if someone knows and wants > to let me know, I wouldn't complain...) Raspbian (assuming that's

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

Hi Josh, I'm not finding this Microchip firmware example online at the moment, but there was once a PIC sample project that implemented USB HID PDC, which is the protocol the NUT usbhid-ups driver speaks. I think the OpenUPS product (somewhat misleadingly named IMHO; the firmware is not open

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?

> On Aug 11, 2022, at 8:03 AM, z.kevino--- via Nut-upsuser wrote: > > So even with Buster I get the same results - no nut-scanner. I was under the > impression that it was needed to get the serial # of an APC device. I have > two of the same type of devices (APC UPS) and the vendor code and

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-upsuser] Info on Cyber Power CP1500AVRLCDa

On Jun 5, 2022, at 5:54 AM, Greg Troxel wrote: > > So having documentation per model that enables buying something that > works seems key, and I don't find that. [...] > Sorry, I did find the compat list > > https://networkupstools.org/stable-hcl.html > > but I'm not really clear where the sort

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-upsuser] finding a common abstraction for reporting

On Mar 17, 2022, at 7:26 PM, Greg Troxel wrote: > > My script is in the process of being extended to also deal with apcupsd > and that seems to have different variables, like timeleft in minutes > instead of runtime in seconds. It seems obvious to me that I should > bring things into a common

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

The patch has been merged into the main Git branch, as mentioned here: https://github.com/networkupstools/nut/issues/439 (also suggests why the CP1500... doesn't exhibit the problem) but a new release is still in the works:

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

On Jan 25, 2022, at 2:51 PM, William Cole via Nut-upsuser wrote: > > I hope that this is an appropriate post for this group. Please let me know > if it should go elsewhere. Yes, this is a good place to ask general questions. However, you may want to subscribe to the list, at least

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-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 ?

On Jun 19, 2021, at 10:55 AM, Roger Price wrote: > > During the ISE review of the proposed RFC, the IETF editor has asked for > clarification of the output of command LIST RANGE . > > The Developer Guide Chapter 9 > https://networkupstools.org/docs/developer-guide.chunked/ar01s09.html >

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

On Mar 8, 2021, at 5:38 PM, Lee Damon via Nut-upsuser wrote: > > On 3/8/21 2:05 PM, Manuel Wolfshant wrote: >> calibrating should not trigger nut > > I agree, it shouldn't. > The behavior is going to depend slightly on which version of NUT you are running. v2.7.4:

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

On Feb 28, 2021, at 7:02 PM, Matthew Rivett via Nut-upsuser wrote: > > I'm new to this project. What would the next steps be to get the values > working correctly? I will help where I have the necessary skills. I can't promise if/when I will have time to look at the results, but to debug

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 >> config 'startup' with 'before' is

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

On Jan 22, 2021, at 5:38 PM, David White via Nut-upsuser wrote: > > 4. lsusb shows the UPS on Bus 001, Device 003 (cypress USB to Serial) > Bus 002 Device 002: ID 05e3:0612 Genesys Logic, Inc. > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 005: ID 046d:c52b

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?

On Jan 10, 2021, at 4:37 AM, Roger Price wrote: > > I am trying to understand the specification of subcommand ENUM in > https://networkupstools.org/docs/developer-guide.chunked/ar01s09.html ... > What exactly does command LIST ENUM call for? Is it a list of those > variables for which there is

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