similar to: Problems with NUT 2.7.2 on CentOS 7 and using the Mini-Box OpenUPS

[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 Mar 17, 2015, at 11:46 AM, Philip Taylor <philip at kelsotowers.co.uk> wrote: > Charles, > > Did you get chance to look at the data I sent you, please? > > I?ve done some more work myself and the conclusion I?ve reached is that if the minibus OpenUPS doesn?t support instant commands, then sending ?upsdrvctl shutdown? won?t ever work, as it would need to send instant

Charles, Did you get chance to look at the data I sent you, please? I?ve done some more work myself and the conclusion I?ve reached is that if the minibus OpenUPS doesn?t support instant commands, then sending ?upsdrvctl shutdown? won?t ever work, as it would need to send instant commands! Also from the trace I sent you, it appears that after the ?RunTimeToEmpty? query, the interface tries to

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:

Charles, Thanks again for your help, and sorry I didn?t :cc - noted for the future! I?m suspicious that the OpenUPS doesn?t behave properly in a number of ways, of which the USB traffic is the one of immediate concern. It seems to me that NUT can read from it but probably not write to it: and the OpenUPS doesn?t flag ?low battery? conditions correctly either. It does shut itself down at a

Hi, I'm trying to generate a skeleton driver with usbhid-ups and gen-usbhid-subdriver but the output seems to be incorrect. Same behavior with stable 2.6.5, so I guess there is something wrong with data coming out of device. I attached the output of usbhid-ups and gen-usbhid-subdriver from the commands: drivers/usbhid-ups -DD -u root -x explore -x vendorid=04d8 -a openups >&

Hi all, I attached a driver for MiniBox openUPS device ( http://www.mini-box.com/OpenUPS) and a dump of the hid usages. I had the possibility to make a few adjustments to the device firmware for HID usages, and although I haven't managed to produce a good structure many issues from previous firmware were at least fixed and new information added. ATM the driver only shows pertaining

Hi, Debug output of driver is attached, started with OpenUPS2 input feed online @ 12V and going offline at 15th second of debug run. Second attached file is debug output of unsuccessful UPS shutdown captured with command: /lib/nut/usbhid-ups -a openups -x productid=d005 -u root -DDD *-k* 2>&1 |tee openups-d005-shut.log I believe input voltage on my earlier upsc run was around 16V,

Hello, I have an openups2 ups. It works very well with nut, except two things: 1) It keeps sending a 'libusb_get_string: invalid argument' message to the log; 2) It does not report any command. Following http://nut-upsdev.alioth.debian.narkive.com/bmJyFFkO/libusb-get-string-invalid-argument, I was able to fix the error message using the attached patch. I do not know how ot fix the

Charles, to your specific points : > The other HID drivers seem to trigger shutdown by writing to the various timers (e.g. UPS.PowerSummary.DelayBeforeReboot). Your firmware seems to have UPS.PowerSummary.PresentStatus.ShutdownRequested, which according to the HID PDC spec, is read/write. I wonder if the firmware responds to this? So are you suggesting if I modify openups-hid.c to include

On Mar 13, 2015, at 8:21 AM, Philip Taylor <philip at kelsotowers.co.uk> wrote: > 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

I bought a very nice little, self contained, UPS from mini-box: http://www.mini-box.com/OpenUPS2 thinking it would be handled by NUT. I think I misread or misinterpreted the HCL http://www.networkupstools.org/stable-hcl.html The OpenUPS UPS is listed as supported under usbhid-ups, and I had assumed that OpenUPS2 would be as well. Bzzzzt. I get a unknown device ID for d005 Is adding (or

On Sep 8, 2014, at 5:46 PM, John Thurston <john.thurston at alaska.gov> wrote: > I bought a very nice little, self contained, UPS from mini-box: > http://www.mini-box.com/OpenUPS2 > thinking it would be handled by NUT. > I think I misread or misinterpreted the HCL > http://www.networkupstools.org/stable-hcl.html Correct, we only knew about the original openUPS (USB ID

Hi, I've been checking out NUT with an OpenUPS board over the last couple of weekends, and have noticed that it doesn't seem to report sensible values. This lead me to investigate usbhid-ups and delve into various issues. As mentioned in a github issue, one of the problems is with the report descriptor - dumping this from the usbhid-ups debug output and picking through it reveals that

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

On Jun 8, 2015, at 8:23 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > Hi Charles. I patched, reconfigured, remake'd, remake install'd - but > no change. however, some more likely helpful information below for > you. Thank you Odd. Are you sure that the new version of usbhid-ups got installed to the same path you are running? Also, there is no protection against

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 Mine is a different brand: "Kanji" which appears to be the argentinian dealler for some generic chinese manufacturer. My model is also 800VA and identified in the same way, so maybe is the same UPS under a different brand:

Charles Lepple a ?crit : > Thanks for the patch. For reference, what does the rest of the "upsc" > output look like for this device? Here it is: $ upsc openups2 Init SSL without certificate database battery.capacity: 100 battery.charge: 100 battery.charge.low: 5 battery.charge.warning: 20 battery.current: 0.000 battery.mfr.date: battery.runtime: 3932100 battery.temperature:

* Ubuntu 12.04 Precise * NUT 2.6 * From Ubuntu terminal ---> sudo apt-get install nut * Openups from mini-box.com (http://www.mini-box.com/OpenUPS) * - Intelligent UPS, USB interface - SMBUS slave and I2C master - Input 6-34V - Programable output 6-24V - Default output is 12V - Input/Output current 6A/10A peak - Charge between 6-30V, 3A - Voltage and current limits - Li-Ion, Li-Po,

Hello! First time posting to this list. I recently purchased a Tripp-Lite OMNIPLUS1000LCD from Costco (USA). I have it attached via USB to a Dell computer with Ubuntu 8.04 server (all updates on it). I've gone through a lot of research on google and this list and can't figure out why my UPS will not connect using nut/usbhid-ups. My setup in ups.conf is: ------- [OMNI1000LCD]