similar to: PowerCOM BNT-1000AP HID instant commands patch

[please keep the list CC'd. thanks!] On Mar 13, 2015, at 10:53 AM, Philip Taylor <philip at kelsotowers.co.uk> wrote: > I?ve set up UPSMON to simply execute ?shutdown -h now? and my system shuts down when I type ?upsmon -c fsd?. The problem is that the OpenUPS doesn?t shut down as a result; and therefore when the power comes back on, unless the battery has totally run out, the

On May 11, 2017, at 1:51 PM, Jesse Molina <jmolina at swoncology.net> wrote: > > I suspect this is a driver problem because while NUT claims the battery isn't plugged in, it's giving me battery runtime/charge info. Both can't be valid at the same time. > > I am at a remote location from the computer and UPS, so I can't physically go over and check. I asked a

Windows 7 Pro x64, NUT 2.6.5-4 (interim release) Product: Back-UPS RS 1200 FW:8.g3 .D USB FW:g3 Setting UPS values can be confusing. For example, battery.charge.low and battery.runtime.low. Using upsrw, the values will be retained after restarting the OS, but not if the UPS is turned off/restarted. In the driver log (below), it looks like the values are obtained from the UPS, but if I set

Hello all, I think I've found the "regression" in Belkin/Liebert USB HID support which worked for NUT v2.7.4 and reports zero voltages in 2.8.0 -- it was actually caused by a bug fix: practically the only functional difference per `git diff v2.7.4..v2.8.0 drivers/belkin-hid.c` is a change from `abs()` to `fabs()` in order-of-magnitude comparisons like `if( abs(value - 1e-7) <

Hello all, I think I've found the "regression" in Belkin/Liebert USB HID support which worked for NUT v2.7.4 and reports zero voltages in 2.8.0 -- it was actually caused by a bug fix: practically the only functional difference per `git diff v2.7.4..v2.8.0 drivers/belkin-hid.c` is a change from `abs()` to `fabs()` in order-of-magnitude comparisons like `if( abs(value - 1e-7) <

Hi, I've been using NUT for many years to look after the UPS on my home servers. Originally I was using a Compaq R3000 but that was replaced with an MGE Pulsar Evolution 3000 about a couple of years ago because the Compaq one was just too noisy! I'm just setting up a replacement server and would like to connect it using a serial cable as I've found that the USB connection

Hi On 10/06/2014 03:04 PM, Charles Lepple wrote:> I think I see what is going on. > >???? 0.368670??? Report[buf]: (5 bytes) => 05 4e 00 48 00 >???? 0.368698??? PhyMax = 0, PhyMin = 0, LogMax = 1, LogMin = 0 >???? 0.368723??? Unit = 00000000, UnitExp = 0 >???? 0.368747??? Exponent = 0 >???? 0.368776??? Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset:

Have recently purchased a MGE Nova 1100 UPS and am trying to get running on netBSD. Configuration netBSD 3.0 amd64 libusb 0.1.10a nut 2.0.3 Built & installed libusb Built kernel with ugen device and uhid removed Build & install nut-2.0.3 with usb Chmod /dev/ugen1 etc to allow access by nut user. Ups.conf [MGENova] driver = newhidups port = auto

tags 439055 upstream thanks Hi Joey, interesting setup! Do you use it (the arm) to monitor the UPS and send notifications... I've sadly not much time to investigate, but have you tested the latest trunk? also, you mention that it was working before: which nut version? what has changed since? 2007/8/21, Joey Hess <joeyh at debian.org>: > Package: nut > Version: 2.0.5-3+b1 >

On May 28, 2014, at 8:59 PM, Daniel O'Connor wrote: > On 28 May 2014, at 21:59, Charles Lepple <clepple at gmail.com> wrote: >>> What would log it? >> >> The driver. > > OK. > >>> I could try running the driver with debugging and see if that shows anything of interest. >> >> That should help. Unfortunately for non-debug

I've acquired and installed NUT 2.4.1 on a D-Link DNS323 NAS. With exception of Load and Battery Temp readings all works well. A upsc ups at localhost command returns; battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2008/06/05 battery.runtime: 2122 battery.runtime.low: 120 battery.temperature: 3022999999999998800 battery.type:

Hello! I left this line uncommented in powercom-hid.c for battery voltage: { "battery.voltage", 0, 0, "UPS.Battery.Voltage", NULL, "%.2f", 0, NULL }, and got some data different from the input voltage values The Powercom support staff gave the following response to my question: Dear Alex, First of all , thank you for purchasing PCM MRT-3000 ups. Regarding of your

Hello. So as my english is not so good, i'll try to write my story in bash commands :o) miwa@zork3$ uname -mrs FreeBSD 5.5-STABLE i386 miwa@zork3$ su root@zork3# cd /usr/ports/sysutils/nat root@zork3# make && make install root@zork3# cd ../nut-usb root@zork3# make && make install root@zork3# cd /usr/local/etc/nut root@zork3# cat ups.conf user=root [MGE-Ellipse]

On Dec 20, 2013, at 5:31 PM, Ariel Wainer wrote: > Hi, I just bought a cheap UPS and apparently I'm hitting the same issue > that's described here: > http://comments.gmane.org/gmane.comp.monitoring.nut.user/6146 Maybe I'm getting old, but I wish Gmane hadn't gone with such an unreadable layout for their blog format. (Not your fault, I'm just venting. I suppose I

I have a new-ish APC Back-UPS XS 1500G connected via USB. It's giving me a "ups.alarm: No battery installed!" error. I also installed and configured apcupsd to give that a try and it's giving me the same error. I suspect this is a driver problem because while NUT claims the battery isn't plugged in, it's giving me battery runtime/charge info. Both can't be valid

Hi all, I have problem with UPS from PowerWalker model VFI 2000 RT LCD over USB (didn't try serial yet). UPS should work via HID driver but ups.status is not rendered properly. Specification of UPS says USB HID compatible. HID driver is the only one which talks with UPS as i try a few from /lib/nut. I use driver usbhid-ups (which communicate with ups), but subdriver resolving is

Hi I Bought a cheap Plexus 800VA UPS from ebuyer : http://www.ebuyer.com/product/240319 to use with my Netgear ReadyNAS duo. Initial version of NUT was very old and NAS didn't detect it although in the NAS log it said "UPS Disconnected". Syslog did send the following : Jan 25 12:46:36 nas-27lfc kernel: usb 1-1: new low speed USB device using uhci_hcd and address 2 Jan 25 12:46:37

I?m a new user of NUT and the OpenUPS - in the past I?ve used APC hardware and apcupsd on Centos 6. I?ve built NUT 2.7.2 from source but used the OpenUPS HID driver v0.4 that?s in github. I?m using firmware version 1.5 on the openups which is the latest published version; I?ve also tried 1.7 which Mini-box sent to me but reverted to the published version. Their support seems a bit slow! I?ve got

Peter, I have been doing some more testing and I find that if I modify the libusb.c file to set a report size in libusb_get_report to 16 the error messages go away. This is the code as it currently stands: static int libusb_get_report(usb_dev_handle *udev, int ReportId, unsigned char *raw_buf, int ReportSize ) { int ReportSize_test = 16; unsigned char raw_buf_test[ReportSize_test +

I purchased a TrippLite ECO550UPS from Amazon a few days ago thinking I was going to use it for my Windows Media Center HTPC. I've since changed my mind and decided to use Mythbuntu but it I can't get my UPS working with nut. I've tried all of the tripplite drivers and the usbhid-ups driver. The tripplite_usb and usbhid_ups output is listed below. The tripplite and tripplitesu drivers