similar to: No subject

So, this is the result of upsc Inform@localhost with the UPS connected to the mains: battery.charge: 97.7 driver.name: powercom driver.parameter.linevoltage: 220 driver.parameter.port: /dev/ttyS0 driver.parameter.type: KIN1500AP driver.version: 2.0.4 driver.version.internal: $ Revision: 0.5 $ input.frequency: 49.61 input.voltage: 236.3 input.voltage.nominal: 220 output.frequency: 49.10

On Monday 03 April 2017 14:13:08 Stuart D. Gathman wrote: Back on the mailing list, where such belongs. > On Mon, 3 Apr 2017, Gene Heskett wrote: > > Nut, IIRC, can do a periodic battery test by putting it offline, > > using the battery, for a predetermined length of time, weekly, > > monthly etc, > > We definitely don't want that in this instance either! Why not?

'belkin-hid.c' and 'tripplite-hid.c' subdrivers, the only thing that happens when the shutdown functions are run is sending DelayBeforeShutdow= n (if that's available, which it probably always is). According to the HID Power Devices specification, it will do just that and is effectively the same as 'shutdown.stayoff'. If there is mains power at that time, the output

Hi, [ There is also a github issue about this here: https://github.com/networkupstools/nut/issues/2347 ] I have an APC Back-UPS BX1600MI purchased in January, attached by its supplied USB cable to a Debian 10 machine. Initially using the nut packaged in Debian 10 (2.7.4-8) this was unusable as the usbhid-ups driver kept disconnecting every few seconds. I upgraded to the git HEAD of nut and

Hi Andy, trying to catch my late here and there, keep in mind that my below comments may be missing things... 2016-04-24 23:30 GMT+02:00 Andy R <spinner+NUTlist at delphinidae.org.uk>: > On 17/04/2016 21:49, Charles Lepple wrote: > >> On Apr 16, 2016, at 9:08 PM, Andy R - (NUT-List) >> <spinner+NUTlist at delphinidae.org.uk> wrote: >> >>>

Dear Mr Claesson, prepare for quite a long letter from me. I hope you will have time to read it. I bestowed a whole morning on trying to identify the correct upstype. Here are the results: root@marto:/home/marto# /usr/local/ups/bin/powercom -DD -u root -a Inform -x type=KP625AP Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision: 0.5 $ (2.0.4) debug level is '2'

>> Over the last couple months, we have had a couple incidents (luckily a= ll >> on weekends) where all 15 UPSs will mysteriously shut off, and we had = to >> manually power them back up. To top it off, there was nothing in syslo= g >> about any UPS going onto battery power and staying there - just a coup= le >> curious low-battery warnings from one of the UPSs. You

I'd like to submit a patch to the 'hidups' driver. I'm a bit new to open-source development model, so I hope I'm not committing a faux paus by just posting it here. I did verify that the problem still exists (by source code inspection) in the latest dev snapshot, which is nut-2.0.3-pre2. I'm using nut-2.0.2 myself. The problem is when I'm connecting to my APC

Hello, I have been using NUT for a short period of time and have some questions regarding the UPS reboot signal that I can't figure out. Have tried some googling and reading the DOCs but I am struggling to understand how some variables / things are supposed to work, so would appreciate any help with any of the following questions. I am running NUT on standalone mode on a linux machine

BTW: I am acutally started to implement the ogg skeleton handling ... - Yorn > Hi everybody, > > I posted here about two years ago about the initial release. This is a > release that fixes many bugs, and has enhancements that make it possible > to support a multi-stream format, ALingA, which I will mention briefly > later. It also supports a PCM format, Neuro, both as part of

Hi! I've recently come into to the possesion of a couple of Belkin Omniguard 3200 UPS's. Given the horrible apache/java based software they come with, I decided to see if I cannot get them to work with NUT. To cut a long story short, they work out to be SEC -based, and extensively modifying the nut-1.4 driver code to come up with the attached two files. I've marked them

Thanks again, Great to see confirmations of more and more things working! > I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). > is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? At least by intent of this new feature -- yes.

Thanks again, Great to see confirmations of more and more things working! > I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). > is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? At least by intent of this new feature -- yes.

cmd test.battery.start.deep was not tested yet. cmd test.battery.start.quick works as expected. cmd test.battery.start 120 works as expected. cmd test.battery.stop works as expected. cmd beeper.toggle works as expected. cmd shutdown.return works as expected. cmd shutdown.reboot does not work entirely. After a minute, UPS is shut down but didn't come back. (Issuing shutdown.stop power up it

On Tue, 2013-07-16 at 23:09 -0400, Charles Lepple wrote: > On Jul 16, 2013, at 11:30 AM, Matt Ivie wrote: > > > I'm sure this has been asked before and I did search the list archives > > but anything I did find looked to be older. > > > > I'm looking at buying some UPS and I'm not sure how to tell which > > currently sold models are supported by

Jim Klimov <jimklimov+nut at gmail.com> > > I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Hi: I got another ups for testing. so I test the new commit for both APC SRT3000XL and SMT2200RM2U. the results below: 1. I get the new attribute "ups.test.result" for

Jim Klimov <jimklimov+nut at gmail.com> > > I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Hi: I got another ups for testing. so I test the new commit for both APC SRT3000XL and SMT2200RM2U. the results below: 1. I get the new attribute "ups.test.result" for

On Mar 13, 2015, at 6:30 PM, cinowell <cinowell at gmail.com> wrote: > Hello, > > I had running OpenMediaVault server with NUT 2.4.3 megatec_usb driver. After the OMV upgrade, NUT also upgraded to 2.6.4. I realised that megatec_usb removed in this version. So I have configured to use blazer_usb driver. However NUT behaves incorrectly after switching blazer_usb. System is being

Hello list, I have been trying to figure out the whole day how I can connect our old Trust UPS Energy Protector 400VA with nut. But I have not made any progress yet and the worst is: I have no idea where to start although I read the documentation and search the web. My first problem is how to find out which driver I should take because this UPS is not in the compatibility list. The second issue

On Sun, 16 Aug 2020, James Fischl wrote: > Thank you Roger, I appreciate the response. I'll have to check my commands, I > believe I started it with those systemctl commands you provided. What I can > say is that oddly enough after completing the server config and after two more > reboots a reboot of the Pi doesn't seem to be causing the UPS to reboot > anymore. I have