similar to: Openups patch proposal

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

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:

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,

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

On Jul 21, 2017, at 3:21 PM, Alphonse <alphsteiner at gmail.com> wrote: > > 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

On Nov 6, 2014, at 1:44 PM, Toomas Suurmets (Priv) <toomas at suurmets.com> wrote: > Hi, > > Debug output of driver is attached, started with OpenUPS2 input feed online @ 12V and going offline at 15th second of debug run. Thanks, the voltages seem to only be off by a factor of 10: Path: UPS.PowerSummary.Output.Voltage, Type: Feature, ReportID: 0x21, Offset: 0, Size: 16, Value:

On Nov 4, 2014, at 4:36 PM, Toomas Suurmets (Priv) <toomas at suurmets.com> wrote: > Hi Charles, > > I tried your suggestion with OpenUPS2 (on Raspberry PI, Debian Jessie), it works. Thanks for the update. We can add the ID to the driver, but I noticed a few inconsistencies (indicated below). > OpenUPS2 Configuartion variables modification would be very welcome.... I'm

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

>> I don't think that the firmware supported commands when this sub-driver was written. It is certainly something we can check for, using the "explore" mode mentioned in the driver man page: http://networkupstools.org/docs/man/usbhid-ups.html (please stop after 30-60 seconds, and gzip the output) This is weird (for me): I have added the 'explore' option into the ups

On Aug 15, 2017, at 5:24 AM, Song Teck <songteck at gmail.com> wrote: > > Hi Charles, > > Have managed to make some progress after a fashion. Got the unit to work on the jessie version of NUT (2.7.2). upsc does output the unit parameters, along with the mis-scaled voltage readings described at http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html. Am now trying to get the

Hi Charles, Tim, Ah, thanks for bit about the dependencies. Would have thought them to be version specific. Tried with the client and server debs but it seems too many dependency differences between wheezy and jessie. I also tried upgrading from wheezy to jessie wholesale to see if that worked and it did solve nut but in the process broke something else that's more critical so I'll give

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

Hi Charles, Ok, I missed the absence from the backports as well. Again, some unfamiliarity here, so 1) I presume I cannot use a metapackage meant for jessie or stretch on wheezy? Or if I can, is there a way to deploy it from console? 2) If not and I use the 2.7.4 tar found at http://networkupstools.org/download.html, do i just run the classical process? i.e. ./configure make sudo make install

[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

> Right, I forgot to mention that the explore mode is not meant to send data to upsd - it just generates debug output. And it is written in the man page... that I do had read! > There are a few extra variables that might be read/write, but I don't see the usual ones that translate into commands (such as UPS.BatterySystem.Battery.Test or UPS.PowerSummary.DelayBeforeShutdown). > >

Hi Charles, thanks for the clarification on the libusb. that indeed does work to get the value in ./configure. I've tried installing a .deb sudo dpkg -i nut_2.7.4-5_all.deb (Reading database ... 103447 files and directories currently installed.) Preparing to replace nut 2.6.4-2.3+deb7u1 (using nut_2.7.4-5_all.deb) ... Unpacking replacement nut ... Setting up nut (2.7.4-5) ... which

Hello, Would like to see if I could get some help with this UPS on a debian set-up. Am not the best with linux and have tried what I managed to find elsewhere on the list so am just trying here. 1) Device seems supported: http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html 2) lsusb -v -d 04d8: seems to give the right parameters including product name, max power etc from the unit 3)

Hi Charles, Ok, will try the ignore lb flag later. How do I go about capturing the log? I might as well do it while testing the flag... Cheers, ST On 15 August 2017 at 20:42, Charles Lepple <clepple at gmail.com> wrote: > On Aug 15, 2017, at 5:24 AM, Song Teck <songteck at gmail.com> wrote: > > > > Hi Charles, > > > > Have managed to make some progress

On Aug 1, 2017, at 12:01 PM, Song Teck <songteck at gmail.com> wrote: > > Hi Charles, > > Ok, I missed the absence from the backports as well. Again, some unfamiliarity here, so > > 1) I presume I cannot use a metapackage meant for jessie or stretch on wheezy? Or if I can, is there a way to deploy it from console? The "nut" metapackage just depends on