search for: acpresent

...tStatus.NeedReplacement, Type: Input, ReportID: 0x0a, Offset: 6, Size: 1, Value: 1 It happened for 9 times, but the message appeared only on first. Broadcast Message from nut at rasp (somewhere) at 17:33 ... UPS BNT500AP at localhost on battery occurred when UPS.PowerSummary.PresentStatus.ACPresent turned to 0 on this line: 10921.069403 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x0a, Offset: 2, Size: 1, Value: 0 Broadcast Message from nut at rasp (somewhere) at 17:33 ... UPS BNT500AP at localhost on line power There were 3 more "on battery" ev...

...ect, upsmon throttles the REPLBATT event: http://www.networkupstools.org/docs/man/upsmon.conf.html (search for RBWARNTIME) > Broadcast Message from nut at rasp > (somewhere) at 17:33 ... > > UPS BNT500AP at localhost on battery > occurred when UPS.PowerSummary.PresentStatus.ACPresent turned to 0 on this line: > 10921.069403 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x0a, Offset: 2, Size: 1, Value: 0 If you turn up the debugging level from 2 to 3, the driver will do a hex dump of the report buffer. Offset and size are bits, so if the ACPresent bi...

...built. With the changes from that thread (I had a PR merged), I was able to get usbhid-ups to recognize my device and could setup NUT the rest of the way. My intended configuration is to run NUT on a Raspberry Pi, have that device be master and then have clients of that NUT install take action when ACPresent goes from true to false. The problem I ran into is `upsc diyups at locahost` was always showing ups.status as "OB". I ran tests and confirmed the raw reports included "UPS.PowerSummary.PresentStatus.ACPresent correctly showing 1 and 0 as appropriate as well as correctly reporting t...

...ges from that thread (I had a > PR merged), I was able to get usbhid-ups to recognize my device and could > setup NUT the rest of the way. My intended configuration is to run NUT on a > Raspberry Pi, have that device be master and then have clients of that NUT > install take action when ACPresent goes from true to false. > > The problem I ran into is `upsc diyups at locahost` was always showing > ups.status as "OB". I ran tests and confirmed the raw reports > included "UPS.PowerSummary.PresentStatus.ACPresent correctly showing 1 and > 0 as appropriate as well...

...started this topic. I've finally tested it on Linux desktop PC. Nut version 2.6.4-2.3 Basically the behavior is the same as on raspberry pi. It reports "battery needs to be replaced" regularly and I got "on battery" message 114107.780504 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x0a, Offset: 2, Size: 1, Value: 0 (on line nr. 1044540 in log) after ~ 31 hours of testing along with immediate "low battery (critical)" not sure, but probably because of 114107.780620 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input...

...read (I had a >> PR merged), I was able to get usbhid-ups to recognize my device and could >> setup NUT the rest of the way. My intended configuration is to run NUT on a >> Raspberry Pi, have that device be master and then have clients of that NUT >> install take action when ACPresent goes from true to false. >> >> The problem I ran into is `upsc diyups at locahost` was always showing >> ups.status as "OB". I ran tests and confirmed the raw reports >> included "UPS.PowerSummary.PresentStatus.ACPresent correctly showing 1 and >> 0 as...

On Jun 8, 2013, at 12:57 PM, M?rti?? Pu??tis wrote: > I'll take a longer driver log. This page (http://www.networkupstools.org/support.html) says that to take a driver log NUT should be stopped, so I won't be able to tell when these events occurred within a driver log. Hmm, I didn't realize it said that, but I think that's to prevent having two copies of the same driver

...t; "UPS.PowerSummary.DesignCapacity", NULL, "%.0f", 0, NULL }, > { "unmapped.ups.powersummary.fullchargecapacity", 0, 0, > "UPS.PowerSummary.FullChargeCapacity", NULL, "%.0f", 0, NULL }, > { "unmapped.ups.powersummary.presentstatus.acpresent", 0, 0, > "UPS.PowerSummary.PresentStatus.ACPresent", NULL, "%.0f", 0, NULL }, > { "unmapped.ups.powersummary.presentstatus.charging", 0, 0, > "UPS.PowerSummary.PresentStatus.Charging", NULL, "%.0f", 0, NULL }, > { "unmappe...

Thanks for the support. Here's list of when transition to battery with return to utility power within a few seconds occurred in last few days: Wednesday 1:41 11:48 11:54 12:59 13:42 14:42 18:13 18:14 Thursday 5:23 Friday 5:12 7:39 7:43 Saturday 7:34 Here's list of when messages that battery needs replacement occurred: Wednesday 20:34 Thursday 9:07 23:09 Friday 18:25 Saturday 7:32 19:47

...xed too. 0.417897 Report[get]: (3 bytes) => 1f 18 00 0.417916 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x1f, Offset: 0, Size: 16, Value: 0.000000 > > > 0.350081 Report[buf]: (2 bytes) => 07 0d > > 0.350095 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: > > Feature, ReportID: 0x07, Offset: 2, Size: 1, Value: 0.000000 > > 0.350106 Report[buf]: (2 bytes) => 07 0d > > 0.350120 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: > > Input, ReportID: 0x07, Offset: 2, Size: 1, Value: 0.000000 > > Al...

...612 Path: UPS.PowerSummary.PresentStatus.Voltage, Type: Feature, ReportID: 0x31, Offset: 0, Size: 16, Value: 1138 0.142600 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x32, Offset: 0, Size: 1, Value: 0 0.142760 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x32, Offset: 1, Size: 1, Value: 1 0.142906 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x32, Offset: 2, Size: 1, Value: 1 0.143052 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x32, Offset: 3, Size: 1, Valu...

On Jan 8, 2015, at 11:43 PM, Graham Menhennitt <graham at menhennitt.com.au> wrote: > Hello Nutters, > > I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) with an APC Back-UPS CS 350 connected via USB. I get persistent (every few minutes) messages logged "battery is low" but I don't understand why. I don't think it's for the reason

...: 0, Size: 8, Value: 2 771.853725 Path: UPS.ManufacturerDate, Type: Feature, ReportID: 0x35, Offset: 0, Size: 16, Value: 12935 771.864707 Path: UPS.Output.ConfigActivePower, Type: Feature, ReportID: 0x52, Offset: 0, Size: 16, Value: 210 771.873644 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x07, Offset: 2, Size: 1, Value: 1 771.873720 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, ReportID: 0x07, Offset: 1, Size: 1, Value: 0 771.873751 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x07, Offset: 0, Size: 1...

...63.201247 Path: UPS.PowerSummary.DelayBeforeReboot, Type: Feature, ReportID: 0x13, Offset: 0, Size: 24, Value: 0 163.210345 Path: UPS.Output.DelayBeforeStartup, Type: Feature, ReportID: 0x28, Offset: 0, Size: 16, Value: 0 163.221472 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x07, Offset: 2, Size: 1, Value: 1 163.221585 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, ReportID: 0x07, Offset: 1, Size: 1, Value: 0 163.221614 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x07...

...Offset: 40, Size: 8, Value: 6 5.727946 Path: UPS.PowerSummary.PercentLoad, Type: Feature, ReportID: 0x07, Offset: 0, Size: 8, Value: 0 5.727964 Path: UPS.PowerSummary.PowerSummaryID, Type: Feature, ReportID: 0x0b, Offset: 104, Size: 8, Value: 1 5.777970 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x01, Offset: 0, Size: 1, Value: 1 5.777987 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x01, Offset: 0, Size: 1, Value: 1 5.777997 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x01, Offset: 1,...

...t;>> PR merged), I was able to get usbhid-ups to recognize my device and could >>> setup NUT the rest of the way. My intended configuration is to run NUT on a >>> Raspberry Pi, have that device be master and then have clients of that NUT >>> install take action when ACPresent goes from true to false. >>> >>> The problem I ran into is `upsc diyups at locahost` was always showing >>> ups.status as "OB". I ran tests and confirmed the raw reports >>> included "UPS.PowerSummary.PresentStatus.ACPresent correctly showing 1 an...

Hi, I have an UPS with only the marking D1000 on it and it came with Junda-Tech's UpsMate. Its USB id is 3344:0025, which is apparently a microprocessor. I've could get some of the HID interactions as described on the website, but there are some outstanding. Junda-Tech does not respond to any queries. Does anybody else have the same or a similar UPS with more information? What is the

..., Offset: 24, Size: 16, Value: 300 0.037734 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x09, Offset: 0, Size: 8, Value: 24 0.038485 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 8, Value: 24 0.039229 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x0b, Offset: 0, Size: 1, Value: 1 0.039344 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x0b, Offset: 1, Size: 1, Value: 0 0.039448 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x0b, Offset: 2, Size: 1, Value: 0...

Oops... changing that to --with-user=nut solved one problem. I have the driver, upsd and upsmon running now. Thank you! Now I'm back to another issue, every 2 seconds I get in the logs: May 3 13:45:23 myhost upsd[2587]: Connected to UPS [eaton]: usbhid-ups-eaton It seems happy to do this forever. On Tue, May 3, 2016 at 8:17 AM, Charles Lepple <clepple at gmail.com> wrote: > On

...Size: 16, Value: 300 0.132561 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x09, Offset: 0, Size: 8, Value: 24 0.132643 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 8, Value: 24 0.132765 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x0b, Offset: 0, Size: 1, Value: 1 0.132770 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x0b, Offset: 1, Size: 1, Value: 0 0.132774 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x0b, Offset: 2, Size: 1, V...