similar to: NUT namespace: RFC for new variable addition

Hi all, here is another variable addition, related to iPDU, that I'd like to make: outlet.n.name | Outlet name (opaque string) | A1 For the sake of completion, we already have "outlet.n.desc" which is more of a description, as per its name. At Eaton, we implement: * outlet.n.name as the physical name of the outlet, related to the group of the outlet. For example,

(hmmm, finally hitting the Sent button...) 2017-05-24 13:56 GMT+02:00 Jim Klimov <jimklimov at cos.ru>: > On May 24, 2017 1:08:09 PM GMT+02:00, Charles Lepple <clepple at gmail.com> > wrote: > >On May 24, 2017, at 5:11 AM, Arnaud Quette <arnaud.quette at gmail.com> > >wrote: > >> > >> Hi all, > >> > >> here is another one,

Hi all, here is another one, related to ATS (automatic transfer switch) this time. in order to track "dephasing" between input sources (1 and 2), I'd like to add a new variable: "input.phase.shift" Details and implementation can be found on: https://github.com/networkupstools/nut/pull/433 Comments and feedback warmly welcome. cheers, Arno -- Eaton Data Center

Hi all, here is another variable addition, related to iPDU, that I'd like to make: outlet.group.n.color | Color of outlet group (hex code) | #daa520 For the sake of completion, Eaton ePDU outlet groups are identified with a color code on the device itself: http://powerquality.eaton.com/images/product-images/ePDU/more-images/EMA324-10DaisyChainWith2.jpg Here the first group

On Aug 4, 2017, at 3:00 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote: > > Comments and feedback warmly welcome. > Please however note that I'll be pushing the related commit, since it seem trivial. It does sound trivial, but do we have that sort of information for other PDUs, and if not, how should names be represented in a GUI if outlet.n.name isn't present?

Hi Manuel 2017-06-07 14:40 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> > wrote: > > > > If that matters, the OS is a fully updated CentOS 6.9 and this > (latest stable ) version of nut was packaged by me. The problem appears on > any of the USB ports ( well, I tried the 2 in

I've recently been working a bit on adding PDU (http://en.wikipedia.org/wiki/Power_distribution_unit) support in NUT. Some of you might have seen the Powerman thread, which also deals with adding more PDUs support: http://powerman.sourceforge.net/supported.html The result is that we now have support for 2 Eaton | Powerware ePDUs (Managed and Monitored iirc, check http://www.epdu.com). I plan

Hi, the diff inline below adds a new subdriver for snmp-ups to support Huawei UPS, based on an observed walk from a UPS5000-E with a few bits filled in from the MIBs (copy at http://junkpile.org/HUAWEI_UPS_MIB/). Sample output from upsc follows the diff. cheers, Stuart diff --git a/data/driver.list.in b/data/driver.list.in index a0e82fb..fac3d5a 100644 --- a/data/driver.list.in +++

Hi! Have a similar issue with one of our customers having HP R12000/3 UPS with AF430A card. Upsmon shows the UPS as Online, on Battery and Battery discharging at the same time: [root at smrsrvslv06 lib64]# upsc hpups at localhost ambient.temperature: 19.0 ambient.temperature.high: 0.00 ambient.temperature.low: 0.00 battery.charge: 94.00 battery.current: 0.00 battery.runtime: 4620.00

On May 24, 2017 1:08:09 PM GMT+02:00, Charles Lepple <clepple at gmail.com> wrote: >On May 24, 2017, at 5:11 AM, Arnaud Quette <arnaud.quette at gmail.com> >wrote: >> >> Hi all, >> >> here is another one, related to ATS (automatic transfer switch) this >time. >> >> in order to track "dephasing" between input sources (1 and 2),

Hi Roger 2017-03-21 19:34 GMT+01:00 Roger Price <roger at rogerprice.org>: > On Tue, 21 Mar 2017, Arnaud Quette wrote: > > Hi Roger, >> >> reviving this discussion, since we have a Github ticket for 2.7.5: >> https://github.com/networkupstools/nut/issues/293 >> > ... > >> I've made some additions to clarify things on the timer, and complete

Arno, thanks for taking the time to write back and no worries about lag, we're all busy and I'm grateful there is a community to interact with to begin with. You're right - the problem went away once I actually configured nut. I guess I was too "cautious" and when I saw the errors I thought something was wrong with the usb connection and didn't try to get nut going

Hi Powermen ;-) I recently came across the Powerman project (http://sourceforge.net/projects/powerman/), pointed by Tony Merenda, from Opengear (thanks Tony). Congrats for your work in this area! I've thought a bit about Powerman and NUT since then... NUT currently supports hosts of UPSs and few PDUs (RPCs), and provides tons of features: http://test.networkupstools.org

Hello Arno, FreeNAS doesn't come with a compiler and I had to compile with the patch on FreebBSD-9.3 and then copy the produced mge-shut. Unfortunately it didn't work out. For every try I was getting "Connection Refused" and when I tried /usr/local/libexec/nut/mge-shut -D -a <ups_name> I was always getting 'No matching HID UPS found'. I returned back to the

Hello all, As some of you may already know from comments in the GitHub pull requests and other media, due to pre-emption by real life our long-term leader and main maintainer, Arnaud Quette, had to step down from this role and from intensive involvement in the NUT project (we hope he would still be able to help on occasion, time permitting). He asked the members of the core team to take over,

Hello all, As some of you may already know from comments in the GitHub pull requests and other media, due to pre-emption by real life our long-term leader and main maintainer, Arnaud Quette, had to step down from this role and from intensive involvement in the NUT project (we hope he would still be able to help on occasion, time permitting). He asked the members of the core team to take over,

Hi David, 2017-03-21 20:06 GMT+01:00 David Baker <david at baker.im>: > Hi, > > > Thanks for checking in ? I managed to re-compile it but was getting the > same error ? I then had other things to do so didn?t get further in my > investigation. > same error being "Can't chdir to /var/state/ups: No such file or directory"? if so, ensure that you use

Hi Panagiotis 2015-04-06 9:13 GMT+02:00 Panagiotis Kritikakos < panagiotis.kritikakos at nikitec.gr>: > Hello Arno, > > Can apply the patch directly or should I recompile nut? > not sure to fully understand your comment, but... this is a source code patch, so you indeed have to apply it to the NUT source code (from within the source tree, "patch -p1 <

Hi Roger, reviving this discussion, since we have a Github ticket for 2.7.5: https://github.com/networkupstools/nut/issues/293 2016-06-05 12:34 GMT+02:00 Roger Price <roger at rogerprice.org>: > On Sat, 4 Jun 2016, Charles Lepple wrote: > > On Jun 3, 2016, at 6:48 AM, Roger Price <roger at rogerprice.org> wrote: >> >>> ... the timer. I don't see it in

2017-03-23 14:29 GMT+01:00 Sonic <sonicsmith at gmail.com>: > Hello > Hi Chris > Sorry if any of this is obvious - I'm new to NUT. > > NUT via upsc is displaying (edited for length): > > device.model: Eaton 5P 2200 > device.type: ups > driver.name: usbhid-ups > ups.alarm: Fatal EEPROM fault! > ups.status: ALARM OL CHRG > ups.test.interval: 604800