similar to: unexpected UPS status

On Wednesday 08 January 2020 06:44:03 Roger Price wrote: > On Tue, 7 Jan 2020, Eyal Lebedinsky wrote: > > On 2020-01-07 23:01, Roger Price wrote: > >> There is no report for variable "ups.delay.start" in your upsc > >> output. What does command "upsc <ups> ups.delay.start" report? > > > > $ upsc eaton ups.delay.start > > Init

This is part UPS and part nut question. I had a (intentional) power outage. The UPS/nut properly shut the system down when battery was down to 20%. It ran for only 18 minutes rather than the expected 40 (see later). After it charged to 37% I removed power from the UPS. After 4-5 minutes the system shut down. However, when I restored power to the UPS the machine powered up immediately (no delay).

On Wed, 8 Jan 2020, Gene Heskett wrote: > On Wednesday 08 January 2020 06:44:03 Roger Price wrote: >> I am surprised that there is no ups.delay.start for this UPS. > My new APC Smart-UPS_1500 doesn't have it either. Hello Gene, The NUT 2.7.2 "device dump library" entry for the APC Smart-UPS 1500 at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html shows an entry

Gene's posting: https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-January/011654.html contains a NUT 2.7.4 update for the APC Smart-UPS_1500 device dump at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html Please note the changes since the 2.7.2 report, e.g. ups.delay.start is no longer supported. Roger

Hi BACKGROUND INFO:I have a new Eaton 5E 1100i USB UPS which their website claims is supported on Linux. They don't provide software for it for Linux, only for Windows.Referring links: https://www.eaton.com/za/en-gb/catalog/backup-power-ups-surge-it-power-distribution/Eaton_5E_UPS.html https://www.eaton.com/za/en-gb/skuPage.5E1100IUSB.specifications.html It was manufactured in May 2020

Maybe a kernel USB issue, but people on this list may have encountered this issue. I am testing a new UPS (EATON 5E 1500iUSB) and am having a problem with the USB connection failing. My old UPS (EATON Ellipse MAX 1500) works just fine with the latest f30. Both devices identify as ID 0463:ffff MGE UPS Systems UPS To narrow the focus I booted recent live CDs on a PC that has no other USB devices

On Tue, 7 Jan 2020, Eyal Lebedinsky wrote: > I had a (intentional) power outage. The UPS/nut properly shut the system down > when battery was down to 20%. > It ran for only 18 minutes rather than the expected 40 (see later). > After it charged to 37% I removed power from the UPS. After 4-5 minutes the > system shut down. > However, when I restored power to the UPS the machine

On up-to-date f36, with latest kernel 6.1.7-100.fc36.x86_64. After receiving a few of these messages Broadcast message from nut at e7.eyal.emu.id.au (somewhere) UPS ups at ups is unavailable I noticed and ran sudo systemctl restart nut-driver at ups.service which triggered Broadcast message from nut at e7.eyal.emu.id.au (somewhere) Communications with UPS ups at ups established I now added

On 2020-08-19 17:36, Louis van Dyk wrote: > Hi > > BACKGROUND INFO: > I have a new Eaton 5E 1100i USB UPS which their website claims is supported on Linux.  They don't provide software for it for Linux, only for Windows. > Referring links: > https://www.eaton.com/za/en-gb/catalog/backup-power-ups-surge-it-power-distribution/Eaton_5E_UPS.html >

I got around to unplugging my UPS and I found it doesn't last nearly as long as estimated. Is the "upsmon[1446]: UPS desktop_ups at localhost battery is low" logged when "battery.runtime:" = "battery.runtime.low: 120"? Does any make better batteries that don't go down faster when they get old? battery.charge: 100 battery.charge.low: 10

On Monday 26 October 2020 09:01:31 Charles Lepple wrote: > On Oct 25, 2020, at 11:52 AM, Robert Stocker <kneadtoknow at gmail.com> 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

On Sep 6, 2019, at 6:28 PM, James wrote: > > I got around to unplugging my UPS and I found it doesn't last nearly as long as estimated. The estimates are typically less accurate when the load is light (output is showing 5%). Also, as Eyal mentioned, five years is getting old for a lead-acid battery. > > Is the "upsmon[1446]: UPS desktop_ups at localhost battery is

On 6/19/23 18:57, gene heskett wrote: > Greetings Jim & friends; > > Just installed nut 2.7.4 on a debian bullseye system.? ups is: > Bus 001 Device 006: ID 051d:0003 American Power Conversion UPS > Device Descriptor: > ? bLength??????????????? 18 > ? bDescriptorType???????? 1 > ? bcdUSB?????????????? 2.00 > ? bDeviceClass??????????? 0 > ?

Greetings Jim & friends; Just installed nut 2.7.4 on a debian bullseye system. ups is: Bus 001 Device 006: ID 051d:0003 American Power Conversion UPS Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor

On Sunday 08 December 2019 21:48:03 Charles Lepple wrote: > On Dec 7, 2019, at 7:01 PM, Gene Heskett <gheskett at shentel.net> wrote: > > What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't > > seem to want to talk to it, and the original name _(usbhid-ups) > > doesn't work from new mobo. Oh wait, I can't spell. But that didn't > >

Greetings Charles; I hope you had a nice Christmas, and will have a happy and prosperous new year in 2016. You mentioned upsrw in a message earlier, so I ran it, and found the shutdown timeout was only 20 seconds. gene at coyote:~$ upsrw myups [input.transfer.high] High voltage transfer point (V) Type: STRING Value: 140 [input.transfer.low] Low voltage transfer point (V) Type: STRING Value:

Thank you for the commands... Please find attached log... Im not sure if the Load.on worked, because in the end I had to manually start the UPS (with button). Anyway, let me know should I need to perform some steps again (probably yes, since I believe it was off). Jakub On 11.03.2015 20:11, hyouko at gmail.com wrote: > 2015-03-11 14:21 GMT+01:00 Jakub Scepka <jakub.scepka at

Hi Users NUT, I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a raspberry-pi. In compatibility list, is listed to use the blazer_ser driver. I use a USB adapter to RS-232 conected in to the No-Breake. Follow the comands e confs. root at rasp:/home/pi# lsusb *Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port* Bus 001 Device 003: ID 0424:ec00 Standard

On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> 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. > I tried setting override.battery.runtime.low = 60 in ups.conf, and waited for the UPS to reach 100% charge, and ups.status to report only

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