Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

On Aug 15, 2017, at 5:24 AM, Song Teck 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

Re: [Nut-upsuser] NUT Client Shuts Down After Brief Power Loss

On Aug 8, 2017, at 6:34 PM, Todd Benivegna wrote: > > OS name and version: MacOS 10.9.5 on 2011 Mac mini > NUT version: 2.7.4-1 > NUT installation method: Package installed via FINK and FinkCommander > Exact device name: APC Back-UPS NS 650M1 (brand new) > > Issue: >

Re: [Nut-upsuser] I have a question in use CyberPower UPS.

On Aug 8, 2017, at 4:01 AM, Andy Jan <andy163...@gmail.com> wrote: > > Hi Charles, > > The attachment(gzip) is the CyberPower UPS USB HID data. > It is worked! Thanks a lot. That's from a different UPS, right? Committed to master (as b898bc652). Thanks for testing! -- -

Re: [Nut-upsuser] I have a question in use CyberPower UPS.

On Aug 7, 2017, at 7:33 AM, Andy Jan wrote: > > [root@andy nut-2.7.4]# yum install libusb > Loaded plugins: langpacks, presto, refresh-packagekit > Package 1:libusb-0.1.3-11.fc18.i686 already installed and latest version That is the runtime library. To rebuild nut, you

Re: [Nut-upsuser] I have a question in use CyberPower UPS.

On Aug 4, 2017, at 4:56 AM, Andy Jan wrote: > > Is the modification will be released? Let me know if it works, and I will merge that onto the master branch that will be used for the next release. ___ Nut-upsuser mailing list

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

On Aug 3, 2017, at 5:35 AM, Song Teck wrote: > > That package is supposed to install both server and client (according to the > description at https://packages.debian.org/stretch/nut anyway). I'll try both > server and client individually later and see if that helps. >

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

On Aug 2, 2017, at 12:09 PM, Song Teck wrote: > > 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

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

On Aug 1, 2017, at 12:01 PM, Song Teck 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

Re: [Nut-upsuser] I have a question in use CyberPower UPS.

On Aug 1, 2017, at 5:47 AM, Andy Jan wrote: > > But I want to see the frequency in NUT by connecting CPS UPS. I have traced > the NUT source code and find that the CPS HID table doesn't build the > frequency. > > Due to I know less about Linux and NUT. Could you help to

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

On Aug 1, 2017, at 7:56 AM, Song Teck Ng wrote: > > Hi Charles, > > Thanks for your reply. So the Jessie or stretch versions will work then since > those are 2.7.2 and 2.7.4... > > I will have to update my sources.list and follow this? > >

Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2

On Aug 1, 2017, at 3:14 AM, Song Teck Ng wrote: > 4) Have edited the ups.conf and nut.conf files with the necessary entries but > trying to start the driver with upsdrvctl start gives: > "Network UPS Tools - UPS driver controller 2.6.4 > > Network UPS Tools -

Re: [Nut-upsuser] Compaq R3000h support

[please don't use HTML email unless needed.] sorry for the delay. > On Jul 22, 2017, at 11:33 AM, Tomas Larsson wrote: > > Now I have some access problems. > This is what ends up un messages > Hosts.allow is set to accept anyone on the local net. > Username and

Re: [Nut-upsdev] Openups patch proposal

On Jul 22, 2017, at 9:13 AM, Alphonse wrote: > > Note that there is still a 'libusb_get_string: Invalid argument' message into > the log, but only when starting or resuming the system. I should mention that this is now in the master branch as commit e6d77c87d0b0 I added

Re: [Nut-upsdev] Openups patch proposal (KDE, etc.)

On Jul 23, 2017, at 4:50 AM, Alphonse wrote: > > Another point is bugging me: the ups is not repported as a battery in kde nor > in the output of 'solid-hardware list'. > Do you have an idea for this problem? > Thanks! > To be honest, most of the NUT development effort

Re: [Nut-upsdev] Openups patch proposal

On Jul 22, 2017, at 9:40 AM, Alphonse wrote: > > This is weird (for me): I have added the 'explore' option into the ups > configuration, and restarted the driver, but now it tells that the device is > offline! It is back to normal without this option. > I have attached

Re: [Nut-upsuser] Compaq R3000h support

On Jul 22, 2017, at 4:13 AM, Tomas Larsson wrote: > > I am planning to install NUT (master) on a headless CENTOS 6.8 system. > Connect the UPS with seral cable. It looks like this might be using the upscode2 driver (UPScode-II protocol), right? > Now my main question

Re: [Nut-upsdev] Openups patch proposal

On Jul 21, 2017, at 3:21 PM, Alphonse 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 >

Re: [Nut-upsuser] Device not supported?

> On Jul 5, 2017, at 7:45 PM, Manuel Wolfshant wrote: > > udevadm control --reload ||: from the man page: --reload Signal systemd-udevd to reload the rules files and other databases like the kernel module index. Reloading rules and databases does not

Re: [Nut-upsuser] Device not supported?

On Jul 5, 2017, at 7:23 PM, Manuel Wolfshant wrote: > >> Manuel: did you happen to regenerate the udev files, or use one of the >> Buildbot tarballs? We typically don't bother to do that until "make dist" >> before a release (since the rules files are generated from *.in files based >> on

Re: [Nut-upsuser] Device not supported?

On Jul 5, 2017, at 5:34 PM, Ambrogio Coletti wrote: > > From section 4.23 of the Developer Guide: > > "There are a few USB UPS devices that are not HID devices. These devices > typically implement some version of the manufacturer’s serial protocol over > USB (which is a

Re: [Nut-upsuser] Help with Elite 800VA usb UPS

On Jul 5, 2017, at 7:05 AM, Andrea de Lutti wrote: > > Which are the ups.status I can use with ups in dummy mode? > I have seen only OB, LB, OL... > Those are the ones that upsmon will respond to. The dummy-ups driver accepts any string, AFAIK. Others:

Re: [Nut-upsuser] Help with Elite 800VA usb UPS

On Jul 3, 2017, at 11:06 AM, Andrea de Lutti wrote: > > ​I would like that NOTIFYCMD points to upssched​. > If I understand correctly, Roger is pointing out that your configuration is confusing upssched and upssched-script. Since you are using Ubuntu, upsmon.conf should

Re: [Nut-upsuser] SU2200RTXLCD2U and protocol 4006

On Jul 3, 2017, at 12:48 PM, Ambrogio Coletti wrote: > > I wouldn't use the NUT at this point because I don't think I will be able to > write a software update to adapt the NUT to my needs. > > My idea was first to test the protocol via a serial terminal client directly > connected to the UPS,

Re: [Nut-upsuser] Help with Elite 800VA usb UPS

On Jun 29, 2017, at 6:52 AM, Andrea de Lutti wrote: >>> Anyway I still not receive any email on any test (power cord disconnected >>> and/or reconnected for example) >> >> Oh, I misinterpreted "working script" as a script that was sending email, >> rather than work-in-progress. Does that same

Re: [Nut-upsuser] Help with Elite 800VA usb UPS

On Jun 27, 2017, at 9:23 AM, Andrea de Lutti wrote: > > Sorry, I didn't received it... You should be subscribed to the list now. > I don't have any REPLBATT message Right, you would only get REPLBATT messages when the UPS reports that the battery *needs to be replaced*

Re: [Nut-upsuser] Help with Elite 800VA usb UPS

On Jun 26, 2017, at 7:03 AM, Andrea de Lutti wrote: > > Are there no warnings for battery test? not sure if you saw my reply on 2016-06-17: Do you mean a notification that a test is in progress, or something for the results? There is the REPLBATT message in upsmon when

Re: [Nut-upsuser] Why are LAN ports not standard on UPSs these days?

On Jun 25, 2017, at 8:53 AM, Philip Rhoades wrote: > I don't understand why most of the UPS offerings available do not come > standard with a LAN port? Why is this? As others have mentioned, it probably comes down to cost for a port that is not frequently used. Something to consider is that

Re: [Nut-upsuser] NUT supporting Modbus TCP

On Jun 24, 2017, at 10:57 AM, Sergei Naumov wrote: > I was wonering if there is a driver that supports communicating with a Modbus > aware device over IP. I have a solar/wind invertor that can broadcast its > state and I would like to monitor the batteries. If they discarge to a > certain

Re: [Nut-upsuser] man pages and asciidoc (was: Device not supported?)

On Jun 23, 2017, at 10:28 PM, Manuel Wolfshant wrote: > > Unfortunately they do not include any man pages, I did not have time to find > a workaround for the hard requirement of newer versions for the tools used by > the build process to create the man pages. You have mentioned the man pages

Re: [Nut-upsuser] Device not supported?

On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti wrote: > > "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by > usbhid-ups. [...]" > but my device (SU2200RTXLCD2U) is supported, as clearly state here. No, the HCL also mentions "protocol 4001". For

Re: [Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB

On Jun 20, 2017, at 6:00 AM, Manuel Wolfshant wrote: > >On 06/20/2017 04:08 AM, Charles Lepple wrote: >> [...] >> It does not get a length for method 1, so it moves on to method 2, which >> gets a length, but fails to get the rest of the descriptor. This is what i

Re: [Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB

On Jun 19, 2017, at 7:56 PM, Manuel Wolfshant wrote: > > On 06/20/2017 02:27 AM, Charles Lepple wrote: >> On Jun 19, 2017, at 10:45 AM, Manuel Wolfshant wrote: >> >>> #lsusb -vvv -d 0463: >>> >>> Bus 002 Device 012: ID 0463: MGE UPS Sys

Re: [Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB

On Jun 19, 2017, at 10:45 AM, Manuel Wolfshant wrote: > > #lsusb -vvv -d 0463: > > Bus 002 Device 012: ID 0463: MGE UPS Systems UPS ... > HID Device Descriptor: > bLength 9 > bDescriptorType33 > bcdHID 1.10 >

Re: [Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB

On Jun 19, 2017, at 4:27 AM, Manuel Wolfshant wrote: > > 1.014501 [D2] Unable to get HID descriptor (Pipe error) > 1.014511 [D3] HID descriptor length (method 1) -1 So at this point in the logs, the kernel USB HID driver is detached from the UPS HID interface (until the UPS USB

Re: [Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB

On Jun 19, 2017, at 4:02 AM, Manuel Wolfshant wrote: > On 06/18/2017 05:42 PM, Charles Lepple wrote: >> On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant wrote: >>> >>> running autogen.sh was triggered automatically. but even if I do it >>> explicit

Re: [Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB

On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant wrote: > > running autogen.sh was triggered automatically. but even if I do it > explicitly, I still get: > + autoreconf -i > >

Re: [Nut-upsuser] Help with Elite 800VA usb UPS

On Jun 16, 2017, at 9:19 AM, Andrea de Lutti wrote: > > Thanks mates, > as suggested I have added > > runtimecal = 240,100,720,50 > default.battery.voltage.low = 10.4 > default.battery.voltage.high = 13.8 (the actual charging voltage) > > In ups.conf > > I

Re: [Nut-upsuser] Help with Elite 800VA usb UPS (/var/run/nut on Ubuntu 16.04)

On Jun 11, 2017, at 8:10 AM, Andrea de Lutti wrote: > > What's the right procedure for loading driver/daemon at boot? > I have read a lot about /var/run/nut missing, but haven't find any > solution Your copy of /etc/init.d/nut-server should have the following lines: #

Re: [Nut-upsuser] Help with Elite 800VA usb UPS

On Jun 16, 2017, at 2:20 AM, Andrea de Lutti wrote: > Using 'guestimation' (low: -0.87, high: -1.08)! > Initial battery charge undetermined > Driver failed to start (exit status=1) The "low" and "high" voltages should correspond to the battery voltage when it is

Re: [Nut-upsuser] Apple Mac slave

On Jun 15, 2017, at 4:09 PM, Robbie van der Walle wrote: > What is the purpose of Boolean: SuccessfulExit? > All I remember is the comment on the next line: I did have to fiddle with permissions of config files - Fink currently builds NUT to run as user

Re: [Nut-upsuser] Apple Mac slave

On Jun 15, 2017, at 10:31 AM, Robbie van der Walle wrote: > > Did you change anything in the plist or used mine ? > Copied and pasted from yours. If you run "sudo /sw/sbin/upsmon -D" from the command line, does it exit immediately? I did have to fiddle with

Re: [Nut-upsuser] Apple Mac slave

On Jun 14, 2017, at 1:54 PM, Robbie van der Walle wrote: > > > "http://www.apple.com/DTDs/PropertyList-1.0.dtd > "> > > > Label > org.networkupstools.upsmon > RunAtLoad > >

Re: [Nut-upsuser] Apple Mac slave

On Jun 14, 2017, at 9:12 AM, Robbie van der Walle wrote: > > But I cannot load it with the command: > > $ sudo launchctl load /Library/LaunchAgents/com.networkupstools.upsmon.plist > > /Library/LaunchAgents/com.networkupstools.upsmon.plist: Invalid property list > I

Re: [Nut-upsdev] Proposed new documentation "Configuration Examples"

On Jun 9, 2017, at 10:16 AM, Roger Price wrote: > > Most of the questions asked in the nut-user mailing list seem to me to be > either erudite technical discussion of new and exotic UPS units, or n00b > questions of the style "I have this old UPS so I installed NUT but it didn't > work". > >

Re: [Nut-upsuser] Apple Mac slave

On Jun 11, 2017, at 7:15 AM, Robbie van der Walle wrote: > > I see only a reboot. Not a shutdown. But is this normal because shutdown -u > -h +0 is used? > To be honest, I haven't experimented much with this, but I saw a normal shutdown/reboot when I just tried this

Re: [Nut-upsuser] Apple Mac slave

On Jun 9, 2017, at 4:47 AM, Robbie van der Walle wrote: > >> Under System Preferences, Energy Saver, there is a setting Start up >> automatically after a power failure. >> Running sudo pmset -a autorestart 1 does the same trick. > > But unfortunately Mac stays . Step

Re: [Nut-upsuser] Apple Mac slave

On Jun 8, 2017, at 4:06 PM, Robbie van der Walle wrote: > > 7. No they didn’t restart. I know there is a setting on the NAS to activate > this. I will check and try again. Not sure for the NAS, but for the Mac, it is probably something like this: sudo pmset -a

Re: [Nut-upsuser] Help with Elite 800VA usb UPS

On Jun 8, 2017, at 9:15 AM, Andrea de Lutti wrote: > > Thank you for your reply Charles, > this is the "upsc" result: > > root@artu:~# upsc ups@localhost > Init SSL without certificate database > Error: Unknown UPS > Use the name from ups.conf in front of "@localhost". >

Re: [Nut-upsuser] Apple Mac slave

On Jun 7, 2017, at 1:14 PM, Roger Price wrote: > > 2. On the NAS, use command > > upsrw -s battery.charge.low=80 -u upsmaster -s sekret UPS Robbie, The "upsrw" command contacts upsd, so it sounds like you should be able to add a user to upsd.users on the NAS, and then run something like

Re: [Nut-upsuser] Help with Elite 800VA usb UPS

On Jun 7, 2017, at 12:54 AM, Andrea de Lutti wrote: > > > Hi, I have tried several drivers for make my Elite UPS working. > With blazer_usb I can contact it, but I have no informations. This is the > best result. > > OS: Ubuntu Xenial 16.04.2 LTS > NUT Version: Nut

Re: [Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB

On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant 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 front and one in the

[Nut-upsdev] new driver- or vendor-specific variable prefix?

Not to pick on anyone in particular, but for the sake of organization, I think we might need to address the need for variables beyond the standard ones defined here: http://networkupstools.org/docs/developer-guide.chunked/apas01.html From

Re: [Nut-upsuser] Emerson Liebert GXT4

On Jun 5, 2017, at 1:05 AM, zefanjas wrote: >> I think the Logical Min/Max are responsible for the battery voltages, since >> there are larger values in the log: >> >> 0.240091 Report[buf]: (5 bytes) => 05 51 00 48 00 >> 0.240097 Path: UPS.PowerSummary.Voltage, Type:

Re: [Nut-upsuser] [HCL] Cyber Power Systems CP1500AVRLCDa supported by usbhid-ups

On Jun 5, 2017, at 11:21 AM, Mike wrote: > > Result of the command, where "n" is incremented in a loop: > > # usbconfig -u 1 -a 2 dump_string n > STRING_0x00 = 0x04, 0x03, 0x09, 0x04 > STRING_0x01 = > STRING_0x02 = > STRING_0x03 = >

Re: [Nut-upsuser] Fwd: Emerson Liebert GXT4

On Jun 4, 2017, at 8:32 PM, zefanjas wrote: > > Hi, > > thanks for your helpful reply. I've added the productid in the ups.conf > and it seems to work (better) now. > > >> After starting the driver and upsd, what does "upsc ups" return? If you can >> also include "upsrw

Re: [Nut-upsuser] [HCL] Cyber Power Systems CP1500AVRLCDa supported by usbhid-ups

On Jun 3, 2017, at 2:21 PM, Mike <the.li...@mgm51.com> wrote: > > On 5/30/2017 10:47 PM, Charles Lepple wrote: >> On May 22, 2017, at 11:13 AM, Mike <the.li...@mgm51.com> wrote: >>> >>> On 5/21/2017 10:39 AM, Charles Lepple wrote: > [snip] > &g

Re: [Nut-upsuser] Fwd: Emerson Liebert GXT4

On Jun 2, 2017, at 8:28 AM, zefanjas wrote: > I couldn't get the GXT4 working with usbhid-ups driver. So I need some > advise to continue to get this device working. The GXT3 seems to be > working ok with NUT (http://networkupstools.org/ddl/Liebert/GXT3.html). > > Here is my

Re: [Nut-upsuser] [HCL] Cyber Power Systems CP1500AVRLCDa supported by usbhid-ups

On May 22, 2017, at 11:13 AM, Mike <the.li...@mgm51.com> wrote: > > On 5/21/2017 10:39 AM, Charles Lepple wrote: >> >> Let me know if you're interested in figuring out if the battery.mfr.date >> value is stored somewhere else. > > Of course. The

Re: [Nut-upsuser] File nut.conf, does mode=netserver means no upsmon?

cerns. # - netclient: this mode only requires upsmon. So netserver seems to be a superset of standalone, but it's not clear that it has to be different. (Tying in firewalls and so forth seems ambitious to me.) -- Charles Lepple clepple@gmail

Re: [Nut-upsdev] NUT namespace: RFC for new variable addition

On May 24, 2017, at 7:56 AM, Jim Klimov <jimkli...@cos.ru> wrote: > > On May 24, 2017 1:08:09 PM GMT+02:00, Charles Lepple <clep...@gmail.com> > wrote: >> I don't think "dephasing" is common usage, but "phase shift" should >> suffice

Re: [Nut-upsdev] NUT namespace: RFC for new variable addition

On May 24, 2017, at 5:11 AM, Arnaud Quette 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), I'd like to > add a new variable: "input.phase.shift" > >

Re: [Nut-upsuser] [HCL] Cyber Power Systems CP1500AVRLCDa supported by usbhid-ups

tput voltages match the values on the LCD? > Results of upscmd -l Thanks, I'll add the timer info to the documentation: https://github.com/networkupstools/nut/issues/432 Also, what about the output of "upsrw"? -- Charles Lepple clepple@gmail __

Re: [Nut-upsuser] [Nut-upsdev] POWERCOM-UPS-USB : UPS Shutdown

On May 17, 2017, at 4:53 AM, Dinow Hsieh wrote: > > ==> I tried below set-command but it react fail > > dinow-All-Series:~# upsrw -s "ups.delay.shutdown"="30" -u pcmups > pcmups@localhost > Password: > Unexpected response from upsd: ERR ACCESS-DENIED > This error is

Re: [Nut-upsuser] TrippLite HID 0.82: libusb_get_interrupt: Function not implemented [3016]

On May 12, 2017, at 10:06 AM, Mike wrote: > > > OpenBSD 6.1/amd64 > nut-2.7.4p0 (from OpenBSD package) > UPS: Tripp-Lite OMNI1500LCDT > > I cannot get the driver for the UPS to load without error. > > Here are the commands, with the output, and the config files: > >

Re: [Nut-upsuser] Message body is too big: 247741 bytes with a limit of 40 KB

On May 12, 2017, at 10:13 AM, Matus UHLAR - fantomas wrote: > > On 11.05.17 17:35, Jesse Molina wrote: >> A 40KB limitation on messages is probably inappropriate in the year 2017. > > sending mail >40KB is inapropriate in this kind of mailing list. > If you have attachment,

Re: [Nut-upsuser] APC Back-UPS XS 1500G says "No battery"

On May 11, 2017, at 1:51 PM, Jesse Molina 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

Re: [Nut-upsdev] Many open green PRs in NUT, wanna merge?

uration/compilation side that seems to be the result of rushing to add features initially. I suspect that there will be a few issues that crop up during packaging, and given the time it takes to rebuild and check .debs for the PPA on other branches, this is not something I look forward to doing in my

Re: [Nut-upsdev] [nut-upsuser] Copeland Engineering Dockmaster

On Mar 19, 2017, at 6:49 PM, Charles Lepple wrote: > > I started modifying one of the drivers to do the reads, but it may not be of > much use until we understand what needs to be written, as you mentioned here: > >> but commenting-out the writing portion makes the data c

Re: [Nut-upsuser] Two UPS via SNMP at one ubunut box

On Apr 18, 2017, at 11:05 AM, Karsten Kortenhorn <karstenkortenh...@gmail.com> wrote: > > OK, it works now. I noticed that I also have to start nut-client over > systemctl and that /etc/default/nut is obsolate. > > > Thanks > > > >> Am 18.04.2017 um 1

Re: [Nut-upsuser] Two UPS via SNMP at one ubunut box

[please use Reply-All to keep the list CC'd. Thanks!] > On Apr 18, 2017, at 3:27 AM, Karsten Kortenhorn > wrote: > > Hi, > > I use upsd 2.7.2 on ubuntu 16.04.2 LTS. "ps aux" don't display upsmon! That's the first thing to troubleshoot. The flow of information

Re: [Nut-upsuser] Two UPS via SNMP at one ubunut box

On Apr 17, 2017, at 3:43 AM, Karsten Kortenhorn wrote: > > I would like to check two UPS in two different buildings with an ubuntu > server. I use SNMP on both UPS. The cgi-page displayed all information as > expected, but if I pull the fuse for one UPS in

Re: [Nut-upsdev] New UPS information - Liebert GXT4 via US

On Apr 17, 2017, at 5:54 AM, Christo Simeonoff wrote: > > Hi UPS List members, > > I have purchased a number of Emerson Power / Liebert GXT4 UPS units. > I have these working correctly under nut, but limited detsils are being > reported. What is reported (upsc

Re: [Nut-upsuser] HP R1500 G2 USB on Ubuntu [HCL]

On Apr 12, 2017, at 3:23 AM, m...@electronico.nc wrote: > > Hello, > > Control HP R1500 G2 with nut via USB. > > Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-72-generic x86_64) > nut V2.7.1 installed from repository > > /etc/nut/ups.conf > [HPR1500] > driver=usbhid-ups > port=auto > > After dealing

Re: [Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error

On Apr 11, 2017, at 2:18 AM, Jon Bendtsen wrote: > > ps: in my new UPS Eaton 5SC I could not see a battery manufacture date in the > extended tree data from nut-cgi :-/ so I wrote the install date on a sticker > and put it on it. You could also do something like this in ups.conf:

Re: [Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error

On Apr 10, 2017, at 10:42 AM, Jon Bendtsen wrote: > > Actually maybe it is within NUT's control. Maybe NUT should only claim that a > UPS is ONLINE if ONLINE is the only thing it is? The problem is that a lot of the UPS status values are more of a de-facto standard, but they have been

Re: [Nut-upsuser] [Eaton 5S 1500] overvoltage shut down?

the NUT website, but I haven't had a chance to poke around the Eaton website. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] usbhid-ups: Failed to open device, skipping. (Permission denied)

e UPS still generates a lot of disconnect/timeout/reconnect traffic in the kernel logs, you might be up against this issue. Full gory details here: https://github.com/networkupstools/nut/pull/122 -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@l

Re: [Nut-upsuser] upsd/upsc, LISTEN and hostname resolution in master/slave

Somewhat related: has anyone used nss-myhostname to ensure that the local hostname can be looked up even without DNS? Seems like this is the intended use case. Also, assuming NUT has been built against glibc (more than likely, for most desktop/server Linux distributions), you can use "getent

Re: [us...@bb.net] Grid and Transposed Grid Views in buildbot nine?

On Mar 28, 2017, at 4:05 PM, Pierre Tardy wrote: > > For buildbot 8, the grid view is a very commonly used view that users set up. > Do you have numbers to back up that idea? > I would go further and say that the beauty of the views provided in 0.8 is that there is so little

Re: [Nut-upsuser] contineously receiving the same values

On Mar 22, 2017, at 9:29 AM, Marc Kessels wrote: > > Hi Charles, > > > Upsmart version is 1.5, copyright says 2012-2014 Do you have a direct link? I found UPSmart-DryContact-V3-4.zip and UPSmart-Networking-V2-4.zip via web search, but the dates for the Linux components

Re: [Nut-upsuser] contineously receiving the same values

On Mar 22, 2017, at 6:27 AM, Marc Kessels wrote: > > with NUT, I am able to connect to the UPS using the blazer_usb and > nutdrv_qx. However, the reported values are constant, and only change if I > run the UPSmart tool (It can run in parallel). What can I do to get NUT to

Re: [Nut-upsdev] [nut-upsuser] Copeland Engineering Dockmaster

Drew, Another thing to consider is the NUT driver documentation. This is the template, but since it originally predated the USB drivers, feel free to draw on the other man pages for inspiration: https://github.com/networkupstools/nut/blob/master/docs/man/skel.txt - Charles

Re: [Nut-upsdev] [nut-upsuser] Copeland Engineering Dockmaster

On Mar 19, 2017, at 10:56 AM, Drew from Zhrodague wrote: > > [] I've spoken with one of the developers, and he's offered to share > some technical documentation with me. I'll report here with whatever I can. > He's on vacation in China. Hopefully this

Re: [Nut-upsdev] modbus driver for phoenix contact industrial UPS

On Mar 14, 2017, at 5:28 AM, Spiros Ioannou wrote: > > Is there any indication on the usual time it takes for a driver to be > checked/included on the master? > (We are planning on setting up hundreds of those UPS boxes and it would be > great to have an estimate) > As an

Re: [Nut-upsdev] [nut-upsuser] Copeland Engineering Dockmaster

[moved to nut-upsdev while we figure out the protocol] > On Mar 9, 2017, at 11:22 AM, Drew from Zhrodague > wrote: > > I'm able to cat /dev/usb/hiddev0 and /dev/hidraw0 - I pipe this through > hexdump and I get different types of data from each: > > > hiddev: >

Re: [Nut-upsuser] MGE ESV+ and Power Trim

On Mar 3, 2017, at 8:21 AM, Charles Lepple <clep...@gmail.com> wrote: > > On Mar 2, 2017, at 3:38 PM, David Baker <da...@baker.im> wrote: >> >> I’ve read the documentation, and it would appear that this can be set by the >> U-Talk protocol (page 34 of >

Re: [Nut-upsuser] MGE ESV+ and Power Trim

On Mar 2, 2017, at 3:38 PM, David Baker wrote: > > I’ve read the documentation, and it would appear that this can be set by the > U-Talk protocol (page 34 of > http://networkupstools.org/protocols/mge/9261zwfa.pdf) but I can’t seem to > figure out how to send the device the

Re: [Nut-upsuser] NUT - General Concept Question

figuration files (including setup of the RPi nodes), and just change the host list when it is time to deploy to the production system. Let us know how it goes. (opinions are my own - I do not speak for my employer, etc, etc.) -- - Charles Lepple https://ghz.cc/charles/ __

Re: [Nut-upsuser] Copeland Engineering Dockmaster

ill provide the output to guide that decision. Could you please also provide the output of "lsusb -vvv -d 04d8:0500" run as root? > > On 2/22/17 11:19 PM, Charles Lepple wrote: >> On Feb 21, 2017, at 10:21 AM, Drew from Zhrodague >> <drewzhroda...@zhrodague.net> wro

Re: [Nut-upsuser] [HCL] Cyber Power Systems EC750G supported by usbhid-ups [UPS.Output.DelayBeforeShutdown]

On Dec 9, 2016, at 11:14 AM, Mike <the.li...@mgm51.com> wrote: > > On 12/8/2016 10:37 PM, Charles Lepple wrote: >> On Dec 8, 2016, at 1:34 PM, Mike wrote: >>> The result of the command >>> >>> upscmd -u user -p password myups load.off.delay 300

Re: [Nut-upsuser] [HCL] Powerware PW5125 with driver bcmxcp

On Feb 21, 2017, at 10:14 AM, Mike wrote: > > I'm attaching a text file with the requested info. Thanks, committed: https://github.com/networkupstools/nut-ddl/commit/179280daad0ea045efeeb417a3e0f437b62d0744 Digging up the other thread...

Re: [Nut-upsuser] Copeland Engineering Dockmaster

On Feb 21, 2017, at 10:21 AM, Drew from Zhrodague wrote: > > > Hello! I have a Dockmaster from Copeland Engineering. This is a battery > saver used for a laptop docking station in a police car, which has a USB port > for relaying its internal timers and

Re: [Nut-upsuser] [HCL] Powerware PW5125 with driver bcmxcp

On Feb 20, 2017, at 11:19 AM, Mike wrote: > > This UPS is already listed in the compatibility list. But I wanted to > add the instant commands supported by upscmd: > ... > and note that a delayed shutoff command is not available. > > (NUT 2.7.4 on OpenBSD 6.0) > > imo,

Re: [Nut-upsuser] NUT configuration complicated by Stonith/Fencing cabling

On Feb 13, 2017, at 8:08 AM, Tim Richards wrote: > > Feb 13 23:11:42 systemd[1] Starting LSB: UPS monitoring software (deprecated, > remote/local)... > Feb 13 23:11:43 usbhid-ups[2093] Startup successful > Feb 13 23:11:43 upsd[1 932] Starting NUT UPS drivers ..done > Feb

Re: [Nut-upsuser] NUT configuration complicated by Stonith/Fencing cabling

perhaps from the fencing software lists or forums, feel free to post that here was well.) -- - Charles Lepple https://ghz.cc/charles/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [libhid-discuss] Can libhid be used to create a "virtual" Bluetooth device?

f step-by-step guides if you do a web search for "emulate Bluetooth Linux". -- - Charles Lepple https://ghz.cc/charles/ ___ libhid-discuss mailing list libhid-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman

Re: [Nut-upsuser] Frys Electronic / ATCL FOR UPS / Debian Jessie

[please use Reply-All to include the list - the list server does not modify the headers] > On Jan 11, 2017, at 1:49 PM, london jak wrote: > > Hi folks, > > Can’t seem to get this working with Frys Electronic / ATCL FOR UPS device > connect direct via USB. > > > This post suggests it should

Re: [Nut-upsuser] NUT Client shuts down when performing runtime calibration on APC UPS

On Jan 9, 2017, at 9:46 AM, Merk - Oliver wrote: > > I then connected to my QNAP and set the UPS settings on the web interface to > "Shutdown server if power loss is 5 min", the UPS is configured to an > SNMP-Connection with its IP-address. Started runtime calibration

[Bug 1540008] Re: USB permissions not set at install time (udevd name changed?)

Patch for xenial: https://launchpadlibrarian.net/300873279/nut_2.7.4-0ubuntu6~xenial~libusb1~gb0e1758_2.7.4-0ubuntu7~xenial~libusb1~gb0e1758.diff.gz I haven't tested the patch for trusty, but I assume it would be similar since the udevd binary has the same name. Uploaded to PPA:

Re: [Nut-upsuser] NUT 2.7.2.3 on CentOS 7.2 doesn't cut power to the host after shutdown

On Dec 25, 2016, at 5:14 PM, Mark Hansen wrote: > > 2. The host does its own power-off before the FSB command is sent to the UPS. Hopefully a CentOS expert can chime in, but this sounds similar to an Ubuntu bug that was discussed earlier:

<    1   2   3   4   5   6   7   8   9   10   >