Re: [Nut-upsuser] Protocol for an Arduino based UPS

On Aug 19, 2018, at 3:31 PM, Glenn Ramsey wrote: > > Hi, > > I'm building a DIY UPS for a Raspberry Pi using a 12V SLA battery, charger, > and > an off the shelf 5V regulator. To monitor the battery level I'd like to use an > Arduino or similar type device. Since the Arduino can have a serial

Re: [Nut-upsuser] TrippLite SMX1500LCDT FreeBSD 11.2 trouble

On Aug 19, 2018, at 3:03 PM, Valentin Merkulov wrote: > > Here is what I get: > > # usbconfig -u 1 -a 3 dump_curr_config_desc > ugen1.3: at usbus1, cfg=0 md=HOST spd=LOW > (1.5Mbps) pwr=ON (100mA) > [...] Hmm, that may be an issue on the NUT side, then. (You might see issues if you run

Re: [Nut-upsuser] TrippLite SMX1500LCDT FreeBSD 11.2 trouble

On Aug 19, 2018, at 2:04 AM, Valentin Merkulov wrote: > > Hi Everyone, > > I'm having trouble getting TrippLite SMX1500LCDT to work on FreeBSD > 11.2, nut 2.7.4 installed from FreeBSD port. > > The debug output is rather big when I'm starting usbhid-ups initially, > Please find that attached

Re: [Nut-upsuser] Wrong battery.date variable value

On Aug 12, 2018, at 11:03 PM, Kevin Mychal M. Ong wrote: > > Hi, > > I installed apcupsd through pfsense and noticed some discrepancy with the NUT > package. I'm not sure if this is a bug regarding the BATTDATE (apcupsd) and > battery.date (NUT) but BATTDATE shows the correct date of

Re: [Nut-upsuser] Query NUT via SNMP on Linux?

On Aug 8, 2018, at 5:36 PM, Garrett Michael Hayes wrote: > > I guess I wasn't as clear as I thought I was. > > I am NOT asking about how to monitor a UPS using SNMP. > NUT is already configured and monitoring the UPS just fine on a USB > connection. > > I'm asking if it is possible to query

Re: [Nut-upsuser] Can Not Get UPS to Turn Off After System Shutdown

Denny, Thanks for providing some Gentoo-specific insight! Rich, Did you fix the root cause for this log message? Jul 26 19:08:57 run-public upsmon[4897]: FSD set on UPS Eaton5SC1500@127.0.0.1 failed: ERR ACCESS-DENIED If not, it is probably related to matching up the NUT master user/password

Re: [Nut-upsuser] Invalid directive CERTFILE /etc/nut/keys/gold.pem on Debian stretch

On Jul 7, 2018, at 6:47 AM, Roger Price wrote: > > * The User Manual section 9.5 should include a « Not on Debian » warning. The section nesting is a bit deep, but further down in Section 9.5 is the following, which should work (at least, NSS appears to be linked in on Debian jessie, and the

Re: [Nut-upsuser] No run cmd /usbhid-ups -k !

On Jul 2, 2018, at 9:02 AM, icin...@gmail.com wrote: > > ioctl(12, USBDEVFS_CLAIMINTERFACE, 0xbecf910c) = -1 EBUSY (Resource busy) > ioctl(12, USBDEVFS_GETDRIVER, 0xbecf9024) = 0 > writev(2, [{"Can't claim USB device [0463:fff"..., 62}, {NULL, 0}], 2Can't > claim USB device [0463:]: No such

Re: [Nut-upsuser] No run cmd /usbhid-ups -k !

On Jul 1, 2018, at 7:58 AM, Jon Bendtsen wrote: > >> Now I'm ordering to shut down UPS: >> /lib/nut/usbhid-ups -a qnapups -k >> Network UPS Tools - Generic HID driver 0.41 (3.10-76-gd2caa7d) >> USB communication driver 0.33 >> Can not claim USB device [0463: ]: No such file or directory > >

Re: [Nut-upsuser] Tripp Lite SU5000RT3U

On Jun 6, 2018, at 5:18 PM, Michael wrote: > > From reading it, it looks like the hex code in the debug area is key. > Agreed - the code that I added to the tripplite_0005 branch parses those same bytes that are shown in the debug output. (All of the Tripp-Lite protocols are similar, with

Re: [Nut-upsuser] Tripp Lite SU5000RT3U

". > > Thanks, > Mike > > On Fri, May 25, 2018 at 5:01 PM, Charles Lepple <mailto:clep...@gmail.com>> wrote: > On May 25, 2018, at 5:20 PM, Michael <mailto:fax12...@gmail.com>> wrote: > > > > driver.version: 2.7.4-480-g14301bdb > > &g

Re: [Nut-upsuser] Tripp Lite SU5000RT3U

On May 25, 2018, at 5:20 PM, Michael wrote: > > driver.version: 2.7.4-480-g14301bdb > I might not have provided enough information on the branch. 14301bdb corresponds to a commit on the master branch, rather than the tripplite_0005 branch that has the new code. What does

Re: [Nut-upsdev] IBM 1500VA/1000W Tower HV UPS supported by usbhid-ups

On May 25, 2018, at 3:00 AM, smage wurgold wrote: > > Hi I would like to be able to use this UPS with NUT please ? > > Product id = 53962KX > > > Network UPS Tools - Generic HID driver 0.38 (2.7.2) > USB communication driver 0.32 >0.00 debug level is '2' >

Re: [Nut-upsuser] Using NUT to signal an appliance

On May 14, 2018, at 4:47 PM, matthew.koundakj...@engility.com wrote: > > Charles, thank you for the thoughtful and helpful reply! > > The ACNC box uses an RS232 serial interface for UPS connection. Whoops, I thought I saw something about USB in your original email. A null-modem serial cable

Re: [Nut-upsuser] Using NUT to signal an appliance

> I have a disk box from ACNC (Jetstor 416is) that has an UPS port. The manual > describes an UPS port: “2. Uninterrupted Power Supply (UPS) Port (APC Smart > UPS only) The subsystem may come with an optional UPS port allowing you to > connect APC Smart UPS device. Connect the cable from the

Re: [Nut-upsuser] Tripp Lite SU5000RT3U

own before, you should be okay. You can try building this week, but I'd still wait until the weekend to test the new driver. - Charles > > Thanks, > Mike > > On Tue, May 8, 2018 at 8:06 AM, Charles Lepple <clep...@gmail.com> wrote: >> Hi, I ported the serial tripplite.

Re: [Nut-upsuser] Tripp Lite SU5000RT3U

Hi, I ported the serial tripplite.c driver to support the non-PDC USB models. It's a bit of a mess, but this is partially due to not getting any public documentation from Tripp Lite regarding these models. What you see below is an attempt to parse the debug variables based on what we know from

Re: [Nut-upsuser] List of connected slaves

On Apr 13, 2018, at 8:21 AM, Larry Fahnoe wrote: > > Umm, the ups -c option "Lists each client connected on ups, one name per > line." according to the man page and it has worked for me for a long time. > You're right, and I have no idea how I missed that the first time.

Re: [Nut-upsuser] List of connected slaves

On Apr 13, 2018, at 3:55 AM, Jon Bendtsen wrote: > > On 13/04/2018 07.56, zefanjas wrote: >> Hi, >> is there a command to get a list of connected slaves you can run on the >> nutserver? I want to monitor the slaves and if their are actually >> connected to server. > > if

Re: [Nut-upsuser] Trying to update the official docs for nut on FreeNAS - help needed to ensure it's written correctly

On Mar 30, 2018, at 2:46 AM, Stilez Stilezy wrote: > GENERAL NUT + ETHERNET CONNECTIONS: > > 1. Is "ethernet" likely to be synonymous with "snmp" for UPS network cards? It is the most likely, but there are definitely Ethernet network cards for MGE models that support SNMP as

Re: [Nut-upsuser] problem with nut APC BackUPS RS 1500 (white)

On Mar 27, 2018, at 5:47 PM, wrote: > > if somebody has same problem with APC BackUPS (SmartUPS works correctly in > same USB) > USE FASTEST USB that U have on board, (if you have USB 2.0 and USB 3.0 > onboard use one 3.0 port for UPS), > sounds like nonsense, but it works,

Re: [Nut-upsuser] Best Power FE700VA?

On Mar 22, 2018, at 10:22 PM, David Melik wrote: > > I assume if I just go through the setup instructions on the NUT website, > that'll make the server automatically load this driver on boot. If the Slackware startup scripts call "upsdrvctl start", and the UPS is listed in

Re: [Nut-upsuser] Best Power FE700VA?

On Mar 20, 2018, at 6:06 PM, David Melik wrote: > > On 03/19/2018 04:49 AM, Charles Lepple wrote: >> The rc-style init systems typically want programs like the drivers to go >> into the background on their own (as the driver does without "-D", or when >> lau

Re: [Nut-upsuser] Tripp-Lite BCPERS450 shutdown/restart problems

ark usually collapses all of the elements of the report descriptor, it is often easier to find report IDs in the usbhid-ups debug output. -- - 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: [Nut-upsuser] Best Power FE700VA?

On Mar 19, 2018, at 4:00 AM, David Melik wrote: > >> Then you can launch the driver with at least one "-D" flag: >> >> /usr/libexec/nut/bestfcom -a ups -D > > I thought there was a lot more to it than that, but after I ran that stuff, > the driver outputs. However, /etc/rc.d/rc.ups

Re: [Nut-upsuser] Interfacing with Siemens SITOP UPS500S

On Mar 14, 2018, at 7:26 AM, Berge, Matthijs ten wrote: > > Can anyone point me in the right direction where I should start? I already > found http://networkupstools.org/docs/developer-guide.chunked/ar01s04.html, > but it doesn't give any specific tips for serial communication. For example, >

Re: [Nut-upsdev] UPS CYBERPOWER CP1300EPFCLCD MISSING FROMCOMPATIBILITY LIST

On Mar 10, 2018, at 4:57 PM, Ron J Taylor wrote: > > Hello Charles, > Nice to make your acquaintance. J > Thanks for your detailed reply. I appreciate it greatly. I want to learn. You're welcome! > > I have read and tried to get my head around the information you

Re: [Nut-upsdev] UPS CYBERPOWER CP1300EPFCLCD MISSING FROMCOMPATIBILITY LIST

On Mar 10, 2018, at 12:40 AM, Ron J Taylor wrote: > > Hi > I have just purchased a Cyberpower CP1300EPFCLCD UPS. > > It is not listed in your Compatibility List > http://networkupstools.org/stable-hcl.html Thanks, we'll add that to the list. We have a few updates queued up for when we cut

Re: [Nut-upsdev] [networkupstools/nut] Riello IDG400 wrong values & not powering off (#530)

On Feb 26, 2018, at 12:06 PM, Elio Parisi wrote: > - the second problem I think is related to the first because the > shutdown command that I sent to UPS by NUT monitor works without problems; Can you please weigh in on the discussion on GitHub?

Re: [Nut-upsuser] APC UPS wrong input voltage

On Mar 5, 2018, at 4:41 PM, Crispin Proctor wrote: > > The UPS functions as it should - it works when there is no power but cannot > test brownout or anything else. Okay. > > I ran the command you put but it fails to log anything to file. Not sure why. I'm assuming

Re: [Nut-upsdev] [PATCH 2/3] Add generic facility to override HID report descriptor in usbhid-ups

On Feb 3, 2018, at 7:19 PM, Russell King wrote: > > + addvar(VAR_VALUE, "hid_descriptor", "Replacement HID descriptor file"); Hi Russell, I was adding a quick note to the usbhid-ups man page about this parameter, and I had a few thoughts: * Maybe we should call it

Re: [Nut-upsuser] APC UPS wrong input voltage

[please use reply-all to CC the list, thanks!] On Mar 3, 2018, at 11:42 AM, Crispin Proctor wrote: > > Folks, > > I've asked this question on the FreeNAS forum but there are no ideas there as > it looks like it's a NUT issue. > > Original question: >

Re: [us...@bb.net] debian packages?

On Feb 27, 2018, at 3:03 PM, Bill Deegan wrote: > > Any one else have this concern with installing buildbot from pypi? > Yes. For some projects (especially those where the continuous integration tool is a means to an end, rather than the product), the

Re: [Nut-upsdev] [networkupstools/nut] Riello IDG400 wrong values & not powering off (#530)

On Feb 26, 2018, at 4:58 AM, Elio Parisi wrote: > > Hi Charles, > this type of UPS doesn't support realtime autonomy calculation, instead a > fixed countdown must be used. > > How we can fix non supported values? If a value is not supported, the driver should not

[Nut-upsdev] Fwd: [networkupstools/nut] Riello IDG400 wrong values & not powering off (#530)

Elio or others at Riello, can you please check out the following issue on Github? https://github.com/networkupstools/nut/issues/530 Begin forwarded message: > > From: latimeria > Subject: [networkupstools/nut] Riello IDG400 wrong values & not powering off > (#530) > Date: February 25, 2018 at

Re: [Nut-upsuser] Best Power FE700VA?

On Feb 19, 2018, at 3:44 PM, David Melik wrote: > > Minicom listed a blank modem init string, and 'f' did nothing. Do you have a pinout for that cable? I forget if it is the default, but you might need to turn off the hardware and software flow control (minicom: Ctrl-A then letter O, "Serial

Re: [Nut-upsdev] [PATCH 1/3] Skip non-feature HID reports

On Feb 16, 2018, at 6:55 AM, Russell King wrote: > > Hence, libusb_get_report() always requests the report ID as a feature > report, and never uses the report type that was stored. > My apologies. I saw the HIDData_t pointer (with its report type field) getting passed down to HIDGetItemData(),

Re: [Nut-upsdev] [PATCH 1/3] Skip non-feature HID reports

have both Input and Feature entries for the same Usage IDs). -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsuser] Best Power FE700VA?

On Feb 12, 2018, at 11:53 PM, David Melik wrote: > > On 01/21/2018 05:53 AM, Charles Lepple wrote: >> If you hook up a terminal emulator to the comms port (1200 baud, 8/N/1 >> unless stickers and/or configuration DIP switches indicate otherwise), and >> type "f&quo

Re: [Nut-upsuser] CentOS 7, systemd, nut-monitor, and failing to shut down the UPS

On Feb 2, 2018, at 8:07 AM, Roger Price wrote: > >> # check to see if we need to actually shutdown the UPS then do it >> /usr/sbin/upsmon -K >/dev/null 2>&1 && /usr/sbin/upsdrvctl shutdown > > I don't have NUT + systemd + CentOS/RHEL, but I'm confused by your script. > "upsdrvctl" is

Re: [Nut-upsuser] testing shutdown: pc not restarting; and "ups unavailable" messages

On Feb 1, 2018, at 10:58 AM, nut.user.u...@neverbox.com wrote: > > According to the theory above, this should have caused the computer to detect > a power loss and turn itself back on. Instead it remained off (as I expected). I have an older box set up this way for continuous integration, and

Re: [Nut-upsuser] Tripp-Lite BCPERS450 shutdown/restart problems

On Jan 22, 2018, at 3:00 PM, Ken Olum wrote: > > I tested the effect of setting UPS.OutletSystem.Outlet.DelayBeforeShutdown > using Tripp Lite's software, which appears to be as follows: > Theoretically, this should be the same as running the command "upscmd

Re: [Nut-upsuser] Best Power FE700VA?

ools/nut/blob/v2.7.4/drivers/bestfcom.c#L226-L244 Let us know how it goes, and we can update the various compatibility lists: http://buildbot.networkupstools.org/~buildbot/docker-debian-jessie/docs/latest/stable-hcl.html#footnotes -- Charles Lepple clepple@gmail ___

Re: [Nut-upsuser] Eaton 5PX after battery replacement still says "replace battery" in NUT [HCL]

On Jan 16, 2018, at 6:07 PM, James Whitwell wrote: > > This might be a simple thing to fix, but I can’t figure it out. We replaced > the battery for the first time in our Eaton 5PX a couple of weeks ago, but we > haven’t been able to clear the “ups.alarm: replace

Re: [Nut-upsuser] Tripp-Lite BCPERS450 shutdown/restart problems

On Jan 11, 2018, at 3:14 PM, Ken Olum wrote: > > So I monitored the USB port with wireshark (an interesting endeavor > since I didn't start out with any knowledge of USB protocols). But I > have managed to discover that when I ask Tripp Lite's poweralert > software to schedule a UPS shutdown, it

Re: [Nut-upsuser] Tripp-Lite BCPERS450 shutdown/restart problems

On Dec 20, 2017, at 10:32 AM, Ken Olum wrote: > > 0.090564find_nut_info: unknown info type: load.on.delay > 0.090577find_nut_info: unknown info type: load.on.delay > 0.090585Initiating UPS shutdown > 0.090593upsdrv_shutdown... > 0.090601instcmd(shutdown.return,

Re: [Nut-upsdev] No answer from upsrw command

.battery.start.quick, [NULL]) > > 2232.749549send: T > > 2233.136727read: > > 2233.136780instcmd: command [test.battery.start.quick] handled Not all UPSes support the standard commands, especially with a de facto standard like the Qx protocol. For testing

Re: [Nut-upsuser] Debian 9.3 nut-client.service reports itself as nut-monitor.service

On Dec 28, 2017, at 6:35 AM, Roger Price wrote: > > It would be clearer to users if the service unit file was also called > > /lib/systemd/service/nut-monitor.service > >From what I can tell, the "nut-client.service" name comes from this >Debian-specific symlink:

Re: [Nut-upsuser] Tripp-Lite BCPERS450 shutdown/restart problems

[please use reply-all to post to the list - the mailing list does not add a reply-to header. thanks!] On Dec 18, 2017, at 11:37 AM, Ken Olum wrote: > > I have a Tripp-Lite BCPERS450, connected to a system running Ubuntu > 16.04.3 LTS and NUT 2.7.2-4ubuntu1.2. I had to make my own >

Re: [Nut-upsuser] Debian 9 : Can't open /etc/nut/upsd.users: Permission denied

On Dec 10, 2017, at 6:10 AM, Roger Price wrote: > > The nut:nut ownership seems to me to be more natural, and the root:nut > ownership looks like a bug in the Debian package. I would argue it slightly differently: upsd has no need to write to upsd.users (or change

Re: [Nut-upsuser] SNMPv3 fails when more than one UPS is configured in ups.conf

On Dec 4, 2017, at 2:43 PM, Lee Damon wrote: > > I have it "working" with the following settings changes from the default > in the RPM. By "working" I mean it starts after reboot and after issuing > 'sudo systemctl restart nut-driver' but, as expected, it takes quite a >

Re: [Nut-upsuser] SNMPv3 fails when more than one UPS is configured in ups.conf

On Nov 30, 2017, at 6:31 PM, Lee Damon wrote: > > SNMPv3 works fine when I have any one of the three configured in > ups.conf while the other two are configured with SNMPv1. It doesn't > matter which _one_ UPS is configured for SNMPv3 in ups.conf, they all > work

Re: [Nut-upsuser] Have any FreeBSD users tried the new libusb-1.0 branch?

> >> # nut-scanner >> Cannot load USB library (/usr/lib64/libusb-1.0.so.0.1.0) : >> /usr/lib64/libusb-1.0.so.0.1.0: undefined symbol: usb_get_string_simple. USB >> search disabled. > > Although I suspect that the USB portion of nut-scanner could probably be > replaced with a small shell

Re: [Nut-upsuser] Have any FreeBSD users tried the new libusb-1.0 branch?

On Nov 26, 2017, at 3:15 PM, Sam Varshavchik wrote: > > Charles Lepple writes: > >> still looking for volunteers to test the libusb-1.0 code on FreeBSD and >> other systems. > > On Fedora 27, running commit 2999c95f0: Thanks for checking this. I should have been mor

Re: [Nut-upsuser] How to disable hal-addon-hid-ups

On Wed, Nov 16, 2016 at 11:28 PM, Stuart Gathman wrote: > On 11/13/2016 10:08 AM, Charles Lepple wrote: >>> Here is one of recipes I googled: >>> https://github.com/sdgathman/trippfix/blob/master/halpolicy.fdi >> What if you convert th

Re: [Nut-upsuser] Have any FreeBSD users tried the new libusb-1.0 branch?

On Nov 22, 2017, at 7:39 PM, Charles Lepple <clep...@gmail.com> wrote: > > The new branch will only attach to the device if I pass the '-u root' flag to > usbhid-ups. fixed: https://github.com/networkupstools/nut/compare/dfd514e...80bc452 still looking for volunteers to test

[Nut-upsuser] Have any FreeBSD users tried the new libusb-1.0 branch?

. -- Thanks, - 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: [Nut-upsdev] [HCL] Riello IPG 600 supported by riello_usb / incorrect battery.charge and ups.temperature values

[when responding, please use Reply-All to include the list. Thanks!] On Nov 16, 2017, at 6:30 AM, Andrés Valdaliso wrote: > > Hello everyone, > > I recently bought a Riello IPG 600 UPS > (http://www.riello-ups.com/products/1-ups/39-iplug) to prevent hardware > damage to

Re: [Nut-upsuser] Cyberpower PR2200ELCDRT2U [HCL]

On Nov 10, 2017, at 5:31 PM, Christoph Lampl wrote: > > Dear Charles, > > thanks for your quick answer and your information! I didn't know there is a > difference in the PR-series between old and new. So thanks for this valuable > information! Just a lucky guess :-) We tend

Re: [Nut-upsuser] Cyberpower model numbers in the HCL

On Nov 12, 2017, at 12:09 PM, Sam Varshavchik wrote: > > http://buildbot.networkupstools.org/~buildbot/docker-debian-jessie/docs/latest//ddl/Cyber_Power_Systems/CP1500EPFCLCD.html > > So, you have the entry for the CP1500EPFCLCD already. I'll grab the > CP1500PFCLCD model, and hope for the

Re: [Nut-upsuser] Cyberpower model numbers in the HCL

On Nov 12, 2017, at 10:08 AM, Sam Varshavchik wrote: > > The HCL has an entry for a Cyberpower model CP1500AVRLCD. Not listed is the > CP1500PFCLCD model, a newer, premium version of the unit; but the HCL does > have an entry for the CP1000PFCLCD model. > > Pretty sure that the CP1500PFCLCD

Re: [Nut-upsuser] Cyberpower PR2200ELCDRT2U

[please use reply-all to include the list. thanks!] > On Nov 9, 2017, at 9:19 PM, Christoph Lampl wrote: > > Hey guys, :) > > recently, I installed Cyberpower PR2200ELCDRT2U, however, I have not managed > to get this UPS working with FreeNAS 11, yet. > > According to

Re: [Nut-upsuser] nut-server service fails to start at boot

On Oct 22, 2017, at 2:39 AM, Daniel Shields wrote: > > Oct 22 05:57:37 nut.tklapp.com upsd[341]: not listening on 192.168.213.189 > port 3493 > Oct 22 05:57:37 nut.tklapp.com upsd[341]: not listening on 192.168.213.189 > port 3493 > Oct 22 05:57:37 nut.tklapp.com

Re: [Nut-upsuser] Junda-tech

On Oct 17, 2017, at 8:48 AM, LLSJ Krüger wrote: > Results of 'lsusb -vvv -d 3344:' [...] > wDescriptorLength 136 > Report Descriptors: >** UNAVAILABLE ** > Can you please re-run lsusb, possibly as root, to grab the contents of the

Re: [Nut-upsuser] Junda-tech

[please use Reply-All to include the list, thanks!] > On Oct 11, 2017, at 12:20 PM, Louis LSJ Krüger wrote: > > Hi, > > I have an UPS with only the marking D1000 on it and it came with > Junda-Tech's UpsMate. Not sure we have had any reports of Junda-Tech before. Is there a

[Bug 1617810] Re: buildbot not start on ubuntu 16 lts

I did a quick check on Ubuntu 16.04, but I don't have that box in front of me at the moment. Pretty sure it was up-to-date, so using version 0.8.12-3. Notes just added to Debian bug #867588: "So far, I have not observed any failures after removing the offending lines ("sqlalchemy >= 0.6, <=

Bug#867588: buildbot: application fails at runtime requiring sqlalchemy-migrate==0.7.2

So far, I have not observed any failures after removing the offending lines ("sqlalchemy >= 0.6, <= 0.7.10" and "sqlalchemy-migrate==0.7.2") from /usr/lib/python2.7/dist-packages/buildbot-0.8.12.egg-info/requires.txt Tested with buildbot 0.8.12-3.2 on stretch, with python-sqlalchemy 1.0.15+ds1-1

Bug#867588: buildbot: application fails at runtime requiring sqlalchemy-migrate==0.7.2

So far, I have not observed any failures after removing the offending lines ("sqlalchemy >= 0.6, <= 0.7.10" and "sqlalchemy-migrate==0.7.2") from /usr/lib/python2.7/dist-packages/buildbot-0.8.12.egg-info/requires.txt Tested with buildbot 0.8.12-3.2 on stretch, with python-sqlalchemy 1.0.15+ds1-1

Re: [Nut-upsdev] Tripplite Smart Int 1000 - wrong numbers

On Oct 10, 2017, at 11:50 AM, Thomas Charron wrote: > > I do have some of the more modern protocol documentation for Tripplite from > the tripplite engineers, if someone is working on updating the Tripplite > drivers. Is this something we can publish on the protocol

Re: [Nut-upsdev] Tripplite Smart Int 1000 - wrong numbers

On Oct 10, 2017, at 1:37 AM, tuhar...@misbb.sk wrote: > > Charles, maybe we are getting closer :-) >> The tripplite_serial_protocol branch has some debug statements that will >> show up if you run "sudo drivers/tripplite -D -a name-of-ups" from the nut >> directory. > Network UPS Tools -

Re: [Nut-upsdev] Tripplite Smart Int 1000 - wrong numbers

My apologies, I forgot a step. See below. > On Oct 9, 2017, at 1:59 PM, tuhar...@misbb.sk wrote: > > Hi, Charles > > I'm trying compilation but there is no configure command in the cloned git > directory of nut. > > > Dňa 08.10.2017 o 23:47 Charles Lepple napísal(

Re: [Nut-upsdev] Tripplite Smart Int 1000 - wrong numbers

On Oct 8, 2017, at 4:34 PM, tuhar...@misbb.sk wrote: > > Thank You for You reply, Charles > > > Dňa 07.10.2017 o 14:30 Charles Lepple napísal(a): >> Is the "lan4.1" cable different from this one? >> http://networkupstools.org/cables.html#_tripp_lite &

Re: [Nut-upsdev] Tripplite Smart Int 1000 - wrong numbers

On Oct 7, 2017, at 8:30 AM, Charles Lepple <clep...@gmail.com> wrote: > >> I also miss values such as output.voltage, battery.runtime etc, but maybe >> this model simply dosen't have the numbers reported. > > We have to calculate an estimate of battery.runtime in tri

Re: [Nut-upsdev] Tripplite Smart Int 1000 - wrong numbers

[please use reply-all to keep the list CC'd, thanks!] On Oct 6, 2017, at 1:29 PM, tuhar...@misbb.sk wrote: > > Hello, > > I've got Tripplite Smart Int 1000 UPS with lan4.1 serial interface. Quite > sympathetic UPS, I must say from first glance. I have made a proper serial > cable (btw i hate

Re: [us...@bb.net] Master-Webserver Bind Address

On Oct 2, 2017, at 9:01 AM, Sebastian wrote: > > can someone tell me how to bind the Web Server Process (twistd) on an > Specific IP Address? I haven't verified this, but would this work? port="tcp:8080:interface=x.x.x.x" Ref:

Re: [Nut-upsdev] [HCL] CyberPower EC350G supported by usbhid-ups

On Sep 28, 2017, at 7:23 PM, Matt Beisser wrote: > > [shutdown sequence] > I have tested and verified the shutdown sequence works. > > [manufacturor] > https://www.cyberpowersystems.com/product/ups/ec350g/ > Thanks.

Re: [Nut-upsdev] Patch for phoenixcontact modbus driver

On Sep 19, 2017, at 3:21 AM, Spiros Ioannou wrote: > > I attach a patch for phoenixcontact_modbus.c > > This patch does the following: > > * Marks driver as DRV_BETA > * Fixes stale data detection when cable is disconnected > > I can open a pull request if needed. Looks

Re: [Nut-upsuser] Bug or feature? polling frequency = (pollfreq + pollinterval)

On Sep 19, 2017, at 9:50 PM, René Berber <rber...@fastmail.fm> wrote: > > On 9/19/2017 6:45 PM, Charles Lepple wrote: > >> On Sep 19, 2017, at 1:36 PM, René Berber wrote: > >>> My guess is that they are the same version (Synology keeps it updated). >> &

Re: [Nut-upsuser] Bug or feature? polling frequency = (pollfreq + pollinterval)

On Sep 19, 2017, at 1:36 PM, René Berber wrote: > My guess is that they are the same version (Synology keeps it updated). Is there a way to check which version they are using? (Just curious - probably will not affect the problem you described.) > Read about pollfreq, and

Re: [Nut-upsuser] building on Solus

On Sep 17, 2017, at 9:39 PM, MTS wrote: > > I am looking at the readme in /scripts/python but am unsure how to proceed. To be honest, the install process for the GUI is pretty much "install the distro package", due to the additional dependencies. (I have been trying to

Re: [Nut-upsuser] building on Solus

On Sep 17, 2017, at 6:33 PM, MTS wrote: > > I am using the same configs as I have in Linux Mint. What do I need to change > here? Sounds like this worked itself out, but if you change upsd.users in the future, you will need to reload (sudo upsd -c reload) or restart upsd.

Re: [Nut-upsuser] building on Solus (was: Flatpak request)

On Sep 15, 2017, at 11:15 PM, MTS wrote: > > Hi, > > I thought it might be problematic. I am really frustrated I cannot get it > working on Solus. > I use Solus way more than Mint these days and it would be nice to have NUT > working. If you describe the problems you

Re: [Nut-upsuser] Flatpak request

On Sep 15, 2017, at 9:51 PM, MTS wrote: > > Is there a possibility of NUT being built into a Flatpak so all distributions > can use it. > If it was available on Flathub it would be a simple and foolproof way of > installing it. >From http://flatpak.org/faq.html : "Can

Re: [Nut-upsdev] CyberPower UPS Omission

On Sep 11, 2017, at 10:09 PM, Jason Berg wrote: > I am happy to provide you the output of "upsc" but I do not know what that > is. "Does it mean UPS console"? Basically - "UPS client" was the original author's intent, I think.

Re: [Nut-upsdev] CyberPower UPS Omission

On Sep 11, 2017, at 5:40 PM, Jason Berg wrote: > > The Hardware Compatibility List page on our website said to report any > omissions in the list to this address. I bought a CyberPower UPS Model > LX1500GU. It looks similar to the CP1500AVRLCD. My intention is to configure

Re: [Nut-upsuser] new NUT release please!

On 11/9/17 1:56 am, Dutchman01 wrote: > > I request a new NUT release as current dates back to March 9, 2016: NUT 2.7.4 > > > The fact stays that not all distro’s use latest snapshots/commits from github > dev tree. > Not all of the distros have moved to 2.7.4, either... As Sam alluded to

Re: [Nut-upsuser] Problem with upsmon?

On Sep 2, 2017, at 1:55 PM, Michele Alzetta wrote: > > the brand is Vultech, but lsusb gives me this: > > Bus 003 Device 006: ID 0925:1234 Lakeview Research It is likely that someone just copied the USB device descriptor from the example in Jan Axelson's book. Whether

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

I uninstalled NUT on xenial, rebooted, confirmed that ownership was root:root, enabled xenial-proposed, and installed nut-server 2.7.2-4ubuntu1.2. The ownership was successfully changed to root:nut. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You

Re: [Nut-upsuser] Can not inialize SSL connection

On Aug 31, 2017, at 5:33 PM, Gareth Williams wrote: > > I'm trying to get upsd (version 2.7.2 running on Debian) to work with an SSL > certificate. >From https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1576584 : "Please see

[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver

Simon, can you check whether the SYSFS/ATTR comment from the Debian bug applies? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721600#10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947

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

Chris and Christian, thanks for working on this! For xenial, looks like this debian/ patch might have gotten dropped (other half of the 52--nut-usbups.rules renaming), which might be causing the build failure: https://anonscm.debian.org/cgit/collab-

Re: [Nut-upsuser] Windows Binary for 2.7.4

On Aug 13, 2017, at 10:29 PM, Jeff Silberberg wrote: > Looking at the project site the latest Windows Binary is a few back - 2.6.5.6 > > Has any one built a more recent version that they can upload and update the > Project site ? > > Looking for Windows 7 / Windows 8, not

Re: [Nut-upsuser] TrippLite SMART1500LCD no delay before ups shutdown.

On Aug 21, 2017, at 1:35 PM, Whiteshell Tech wrote: > > I ran it again on battery and upsd running, set upsrw ok and then > shutdown.return gave an "ERR CMD-NOT-SUPPORTED" Odd thing is after running > that I am getting random timed ups powering off for one or two

Re: [Nut-upsuser] TrippLite SMART1500LCD no delay before ups shutdown.

On Aug 21, 2017, at 8:33 AM, Charles Lepple <clep...@gmail.com> wrote: > > That said, it looks like the TrippLite HID mappings (in v2.7.4 as well as > master) are missing the "shutdown.return" command. I'd look into it further, > but ironically, the local power compa

Re: [Nut-upsuser] TrippLite SMART1500LCD no delay before ups shutdown.

[when responding, please use reply-all - the list does not mangle the reply-to header] > On Aug 21, 2017, at 12:45 AM, Whiteshell Tech > wrote: > > I have attempted to set the delay higher using "upsrw -s > ups.delay.shutdown=120 TrippLiteUPS@localhost" and

Re: [Nut-upsuser] New powercom device?

On Aug 16, 2017, at 8:36 PM, Harlan Stenn wrote: > >> >> Is it possible that you just need to load the usbserial kernel >> module, and bind it to the UPS' 0d9f:0002 ID? Then the /dev/ttyUSB* >> port can be passed to the "powercom" driver. (This is suggested by >>

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

On Aug 16, 2017, at 3:27 AM, Song Teck wrote: > > How do I go about capturing the log? You might want to discharge the battery most of the way to battery.charge.low (5%, if it is similar to the other unit listed in the DDL) before switching to debug mode, because it is

Re: [Nut-upsuser] New powercom device?

On Aug 10, 2017, at 12:19 AM, Harlan Stenn wrote: > > 0.447497HID descriptor length 37 > 0.450449Report Descriptor size = 37 > 0.451062Using subdriver: PowerCOM HID 0.5 > 0.4519963 HID objects found > 0.453502Path: ffa1.ffa1, Type: Input, ReportID: 0x00, >

Re: [Nut-upsuser] CyberPower ol2000ertxl2u

On Aug 8, 2017, at 4:57 AM, Greg Vickers wrote: > > I'm picking up a CyberPower OL2000ERTXL2U tomorrow (needs new batteries), > should that be supported via the powerpanel driver? Unfortunately, the author of the powerpanel driver has not had time to contribute to NUT for some time now, but if

Re: [Nut-upsuser] Keep on losing communication: Raspberry Pi, CyberPower PR1500LCD

On Aug 12, 2017, at 12:00 PM, Rory Jaffe wrote: > > OS Version: Linux piaware 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 > armv7l GNU/Linux > Nut Version: 2.7.2-4 > Nut Installation Method: apt > Device: CyberPower PR1500LCD > Uses​ ​Generic HID driver 0.38 (2.7.2) Is

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