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] 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] 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

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] 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-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] 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] 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] 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] 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] APC Back-UPS CS 650 offdelay and startdelay

On Aug 22, 2018, at 1:20 PM, Karol Olszewski wrote: > > W dniu 22.08.2018 o 14:41, Charles Lepple pisze: >> /lib/nut/usbhid-ups -a apc -DDD -k > Please see attachement. 1.872180 Report[buf]: (2 bytes) => 40 00 1.872196 Path: UPS.Output.APCDelayBeforeReboot, Type:

Re: [Nut-upsuser] APC Back-UPS CS 650 offdelay and startdelay

On Aug 26, 2018, at 1:19 PM, Karol Olszewski wrote: > > W dniu 24.08.2018 o 23:13, Karol Olszewski pisze: >> Hi >> I'm bit closer :) >> Acctually change "UPS.Output.APCDelayBeforeReboot" to >> >> { "shutdown.return", 0, 0, "UPS.Output.APCShutdownAfterDelay", NULL, >> "90", HU_TYPE_CMD, NULL

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] 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 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] TrippLite SMX1500LCDT FreeBSD 11.2 trouble

On Aug 20, 2018, at 1:03 AM, Valentin Merkulov wrote: > > 0.033412 [D3] nut_usb_claim_interface: failed to claim USB > device (Other error). > 0.033417 [D3] nut_usb_claim_interface: failed to detach kernel > driver from USB device (Other error). I am not as familiar with this branch

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

new /dev node? Do the usbconfig commands return any data? > On Mon, Aug 20, 2018 at 1:42 PM, Charles Lepple wrote: >> On Aug 20, 2018, at 1:03 AM, Valentin Merkulov wrote: >>> >>> 0.033412 [D3] nut_usb_claim_interface: failed to claim USB &

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

Understood about unplugging USB - others with the 3016 devices have proposed various methods with USB hubs that have per-port power switching, etc. to simulate unplugging. I am not a fan of the concept, but I recognize that others have made more significant investments than the single UPS that

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

On Aug 22, 2018, at 2:03 PM, Valentin Merkulov wrote: > > With interruptonly the driver output goes into a loop (is it an > expected behavior?) Yes, this is what the driver does in the background if you do not pass any "-D" flags. If you were to start `upsd` at that point, it should be able to

Re: [Nut-upsuser] APC Back-UPS CS 650 offdelay and startdelay

On Aug 23, 2018, at 10:46 AM, Karol Olszewski wrote: > > W dniu 23.08.2018 o 02:16, Charles Lepple pisze: >> >> For some reason, this is being hardcoded to 1: >> >> drivers/apc-hid.c- /* used by APC BackUPS CS */ >> drivers/a

Re: [Nut-upsuser] upsmon fails to start

On Sep 1, 2018, at 2:44 PM, Mick wrote: > > On Saturday, 1 September 2018 17:50:13 BST Charles Lepple wrote: >> I don’t have the code in front of me at the moment, but my guess is that the >> config parser stopped parsing at the “#” character. > > I suspected a r

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] after power outage and proper shutdown, UPS turns on before power returns

On Sep 27, 2018, at 6:59 PM, Gabriel wrote: > > Hi, > > I'm struggling with a peculiar issue with my UPS. After a power > outage, the devices powered by it properly shut down via nut. > Eventually, the UPS also goes down. Power is still out, however, > roughly 40 seconds after the UPS shut

Re: [Nut-upsuser] Wrong battery.date variable value [APC, usbhid-ups]

On Aug 30, 2018, at 10:05 AM, Ong, Kevin wrote: > > The battery.mfr.date is actually the correct value I'm looking for. That is > the exact date the battery was last replaced. And yes, it is the correct > value displayed in apcupsd. I think we're on the same page for the battery date. What

Re: [Nut-upsuser] Wrong battery.date variable value [APC, usbhid-ups]

On Aug 30, 2018, at 6:54 AM, Ong, Kevin wrote: > > I'm very sorry for the delay here, I've been very swamped with work. Here's > the relevant information you guys need: > > "upsc APC_BR1500GI" output: https://pastebin.com/rH3W0dbz > "upsrw APC_BR1500GI" output: https://pastebin.com/tEWv8a3d >

Re: [Nut-upsuser] APC Back UPS?

> >> Maybe it's not a standard ethernet-to-UPS cable? > > That's Ben's point - either it is actual Ethernet (usually found on an add-on > UPS SNMP monitoring card, where the jack typically has two status LEDs, one > on either side of the notch for the modular plug tab) that needs to go to >

Re: [Nut-upsuser] APC Back UPS?

On Dec 26, 2018, at 8:59 PM, David Melik wrote: > > root@0.darwinheim :~# lsusb -d 051d: > root@0.darwinheim :~# If you leave off the "-d 051d:" part, do you see anything in the listing that looks like it could be the UPS? (The 051d vendor ID

Re: [Nut-upsuser] Newbie - SNMP-UPS Driver Issue

On Jan 22, 2019, at 5:29 PM, NutList wrote: > > Hello all, > I have exhausted my research and need a little help with some basic concepts. > First time configuration working with NUT and putting into a OS X > environment. Was able to install the package using Brew. Have read the >

Re: [Nut-upsuser] CpberPower PR3000LCDRTXL2UN support

On Jan 22, 2019, at 4:37 PM, Phil Stracchino wrote: > Is there any practical benefit to getting the SNMP network card for it > unless I plan to monitor it via SNMP, or can any monitoring and > management I need to do be done perfectly well via serial, as on my APCs? For CyberPower, a SNMP card

Re: [Nut-upsuser] APC Back UPS and Best Power FERRUPS?

On Dec 25, 2018, at 4:07 AM, David Melik wrote: > > Lately I got (used) an APC Back UPS Pro 1000 and Back UPS NS 1080. I got an > [8P8C]-to-USB cable from another UPS, but the Pro isn't detected (with > usbhid-ups.) I haven't tried the NS yet but it seems to not be on the list > though looks

Re: [Nut-upsuser] detailed ups.test.result

On Dec 15, 2018, at 10:32 PM, James wrote: > > My UPS has an LCD that says the battery is 100% and the estimated run time is > 12min. > The uspc has similar results. > The problem is when line power is lost the UPS batter goes to 0% very quickly > (seconds). > > It charged to 85% when power

Re: [Nut-upsuser] Can not match USB UPS

On Dec 13, 2018, at 9:47 PM, André Hänsel wrote: > > Hi list, I seem to need another pair of eyes. > > Here's my ups.conf: > > [myups] > driver = usbhid-ups > port = auto > vendor = 051d > product = 0002 > serial = 4B1717P25055 It's subtle, but "vendor" matches

Re: [Nut-upsuser] detailed ups.test.result

On Dec 16, 2018, at 6:07 PM, James wrote: >> Which driver is this? > ... > device.mfr: CPS > device.model: UPS CP850AVRLCD > device.type: ups > driver.name: usbhid-ups For a USB HID PDC (Power Device Class) UPS like this, "ups.test.result" comes straight from the spec:

Re: [Nut-upsuser] battery.runtime

On Dec 4, 2018, at 10:12 AM, Danny Siminiuk wrote: > > First time poster but I've been using NUT periodically for a long time. > > I was looking for a way to initiate a shutdown on servers when UPS battery > runtime drops to a certain threshold. I never found a published way after > much

Re: [Nut-upsuser] MGE EllipseMAX 1500 shuts down after a few hours

On Dec 2, 2018, at 3:21 PM, Manuel Wolfshant wrote: > > On December 2, 2018 7:29:38 PM GMT+02:00, raul wrote: >> I have restored original configuration and enabled the ignorelb flag. I >> >> didn't point out in the original e-mail that after every poweroff the >> battery percentage is

Re: [Nut-upsuser] NUT reporting wrong voltage

On Dec 5, 2018, at 5:17 PM, Crispin Proctor wrote: > > Hi folks, > > > I have an APC Back-UPS XS 1400U which is reporting the wrong input and output > voltages. > I am in the UK where our nominal voltage is 240 - not 110 :) You're doing somewhat better than the XS 1200, and not quite as good

Re: [Nut-upsuser] battery.runtime

On Dec 4, 2018, at 1:38 PM, Danny Siminiuk wrote: > > I don't think "ignorelb" will work in my case because that is set on the > master. I am using the nut package in pfSense as the master and I want > pfSense to shutdown on LOWBATT as designed. > Ah, the multiple thresholds weren't clear

Re: [Nut-upsuser] Just an interesting data point [CyberPower SNMP/USB]

On Jan 27, 2019, at 9:31 PM, Phil Stracchino wrote: > > On 1/27/19 9:13 PM, Charles Lepple wrote: >> I forget, is your copy of NUT built from an RPM? If so, it shouldn't be >> too hard to add that patch to get load, charge, input voltage/frequency >> and output vol

Re: [Nut-upsuser] Just an interesting data point [CyberPower SNMP]

On Jan 27, 2019, at 2:36 PM, Phil Stracchino wrote: > > SO, my full load on my core UPS is two Dell R610s, one Sun X4540, one HP > DL360p gen8, two six-core Thuban-II workstations plua their monitors, > and the network stack and KVM. > > The APC SU3000RM (3KVA) that blew up last week considered

Re: [Nut-upsuser] Just an interesting data point [CyberPower SNMP/USB]

On Jan 27, 2019, at 10:56 PM, Phil Stracchino wrote: > > I'm not 100% certain I'm tracking what you mean by 'scaled to the > transfer voltage range' though. Could you clarify? > The "output.voltage" column in the quoted portion at the link is clipped/scaled to the range 136.0 to 142.0, which

Re: [Nut-upsuser] variables between manufacturers

On Apr 2, 2019, at 9:42 PM, James wrote: > > I switched my desktop with my raspberry pi because I thought my desktop ups > had a larger capacity. > Now the ups.load of each is not what it was (it should be). Note that ups.load is a percentage of "full load", which is up to each UPS vendor to

Re: [Nut-upsuser] nut vs ups fail

On May 12, 2019, at 5:56 PM, Gene Heskett wrote: > > So I believe I'm in business if systemctl starts it on a reboot. Cool! > > However I get this at the top of a upsc report: > > Init SSL without certificate database > > Which I've not recalled seeing in wheezy. > And the common certs are

Re: [Nut-upsuser] odd msg at top of upsc output

On May 31, 2019, at 11:19 AM, Gene Heskett wrote: > > On Friday 31 May 2019 10:08:02 am Charles Lepple wrote: >> >> To be honest, I thought we had fixed this a while ago (NUT 2.7.1), but >> I guess it popped back up again: >> https://github.com/networkupstool

Re: [Nut-upsuser] odd msg at top of upsc output

On May 31, 2019, at 1:29 AM, Manuel Wolfshant wrote: > > On 5/31/19 6:54 AM, Gene Heskett wrote: >> Greetings all; >> >> gene@coyote:~$ upsc myups >> Init SSL without certificate database >> battery.charge: 100 >> battery.charge.low: 30 >> [yadda yadda] >> >> Is there a certificate package I

Re: [Nut-upsuser] How to shutdown macOS / mac OSX from Network UPS Tools client - NUT

vaguely remember them not using the NUT LB state. (That might have been covered in one of your links, but I haven't had a chance to look through all of them.) -- - Charles Lepple https://ghz.cc/charles/ ___ Nut-upsuser mailing list Nut-upsuser@alioth-

Re: [Nut-upsuser] How to shutdown macOS / mac OSX from Network UPS Tools client - NUT

On Jun 10, 2019, at 5:50 PM, Joe Gervasio wrote: > > The only thing I can see in the system.log that may be relevant is :- > Jun 10 22:06:36 Joes-iMac com.apple.xpc.launchd[1] > (com.apple.xpc.launchd.domain.system): Session adoption is only allowed in > user domains. > > This message occurs

Re: [Nut-upsuser] UPS shuts down on NUT boot with low battery [APC Back-UPS RS 550G]

On Jun 11, 2019, at 1:37 AM, Marc Finns wrote: > > Thanks for the reply. However these two FAQ are unfortunately not describing > the situation. > - The first issue is that NUT switches off the UPS upon reboot on low battery > (not that it dies because of low battery) > - The second issue is

Re: [Nut-upsuser] nut vs ups fail

On May 12, 2019, at 1:52 PM, Gene Heskett wrote: > > On Sunday 12 May 2019 12:07:13 pm Charles Lepple wrote: > >> systemctl status nut-driver > ● nut-driver.service - Network UPS Tools - power device driver controller > Loaded: loaded (/lib/systemd/system/nut-driver.se

Re: [Nut-upsuser] nut vs ups fail

On May 12, 2019, at 2:51 PM, Gene Heskett wrote: > > On Sunday 12 May 2019 02:41:02 pm Charles Lepple wrote: > >> /lib/nut/usbhid-ups -a myups -DD > gene@coyote:~$ /lib/nut/usbhid-ups -a myups -DD > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > USB communication

Re: [Nut-upsuser] nut vs ups fail

On May 8, 2019, at 8:19 PM, Gene Heskett wrote: > > The real problem as I recall from a couple days back, is that the > usbhid-ups driver was left out of this kernel build. Since this is > pretty close to an rt kernel, I don't know if the LCNC folks will build > another kernel with it, and

Re: [Nut-upsuser] Is this an issue?

On May 11, 2019, at 7:17 AM, Leslie Rhorer wrote: > > I just set up a UPS on a Debian Stretch system for my sister-in-law. > Obviously, I want NUT to properly shut down the unit when the battery gets > low. This means upsmon must be running and healthy. When I run 'systemctl > status

Re: [Nut-upsuser] TrippLite AVR550U start on power

[please use reply-all to include the list] On May 20, 2019, at 5:30 PM, Steven Bixby wrote: > > I have a TrippLite AVR550U that my company uses several individual Linux > boxes in one large system, all running Ubuntu 18.04LTS, and all will be using > the package version of nut - 2.7.4.In

Re: [Nut-upsuser] Data Stale issue

On May 6, 2019, at 2:57 PM, Stuart D. Gathman wrote: > > On Mon, 6 May 2019, Gareth Davies wrote: > >> Just to say, I stopped the driver and started it again and the errors went >> away! However, I turned off power to the UPS but I wasn’t receiving any >> e-mails :( also when I rebooted the RPi

Re: [Nut-upsuser] PowerShield Defender 1200VA

On May 2, 2019, at 3:56 AM, Walter HILL wrote: > > I have read suggestions about modifying UDEV rules and changing the USB > cable. I've tried another cable. The UDEV rule file that ships with NUT > appears to contain a record for this UPS > The "ret -110" below is a timeout, and usually the

Re: [Nut-upsuser] nut vs ups fail

wiki to make the source build match the .deb packages. Let's try to make the Debian stretch packages work first. -- - Charles Lepple https://ghz.cc/charles/ ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Symmetra LX 16000

anufacturer=APC https://networkupstools.org/ddl/APC/ -- - Charles Lepple https://ghz.cc/charles/ > ___ > Nut-upsuser mailing list > Nut-upsuser@alioth-lists.debian.net > https://alioth-lists.debian.net/cg

Re: [Nut-upsuser] nut vs ups fail

On May 7, 2019, at 9:09 AM, Gene Heskett wrote: > > On Tuesday 07 May 2019 08:38:44 am Charles Lepple wrote: > >> On May 7, 2019, at 5:06 AM, Gene Heskett wrote: >>> New testing install(stretch) >>> pulled in nut stuff from repo. >>> copied o

Re: [Nut-upsuser] Data Stale issue

On May 6, 2019, at 8:10 AM, Gareth Davies wrote: > > Hello, > > I apologise if I've sent this question to the wrong place/e-mail! I'm new to > the site! I was wondering if anyone could help me... I downloaded Network UPS > Tools yesterday so that I could receive e-mail notifications of when my

Re: [Nut-upsuser] NUT on Raspberry PI 3b+

On May 2, 2019, at 6:22 PM, Vladimir Zaitchikov wrote: > > pi@raspberrypi:~ $ lsusb -v > > Bus 001 Device 004: ID 0d9f:0004 Powercom Co., Ltd What are the permissions on /dev/bus/usb/001/004? If the group is not "nut", and you installed NUT after plugging in the UPS USB cable, you may need

Re: [Nut-upsuser] New User Questions - With Belkin USB

On Jul 8, 2019, at 6:35 PM, David White wrote: > > This makes me think something remains broken. But > > upsc belkinusb > > right after this gets results. Does "upsc belkinusb@localhost" also work? If not, check to make sure that localhost doesn't resolve to a slightly different address than

Re: [Nut-upsuser] New User Questions - With Belkin USB

On Jul 12, 2019, at 2:39 PM, David White wrote: > > Thanks Roger for all your help here. I hope the 2 attachments come through. > The .sh is my doctored version of the script and the .report is its output. I > welcome any suggestions or ideas about what might be causing my problems with >

Re: [Nut-upsuser] Trouble getting Roline/Powercom UPS recognized

On Jul 16, 2019, at 9:50 AM, Patrick M. Hausen wrote: > > Hi all, > >> Am 16.07.2019 um 15:33 schrieb Charles Lepple : >> There may be an issue with the uhid driver binding to the device. I can't >> remember which versions of FreeBSD this affects, though. > > U

Re: [Nut-upsuser] raspberry pi and tripplite_usb

On Sep 10, 2019, at 10:40 AM, gru...@mailfence.com wrote: > > i have a OMNIVS1500XL > i have used nut for several years on a full sized pc with no problems > i am trying to get nut working with this ups on a raspberry pi > i tried with a pi 3b running raspbian stretch > i tried with a pi 3b

Re: [Nut-upsuser] Debian 10 nut 2.7.4-8 and APC Back UPS 600i on 940-0020B

On Sep 11, 2019, at 5:25 AM, tovis r-visor wrote: > > I does not change any of them. Simple, after boot, using > $ watch upsc MYUPS > what is give me "LB OL" > from another terminal I restart: > # systemctl restart nut-driver.service > after some seconds the status is changed to simply "OL".

Re: [Nut-upsuser] Sweex PP200 650VA UPS - Success report [HCL]

On Sep 6, 2019, at 3:43 PM, Martyn Hill wrote: > > Just thought to share my findings getting a Sweex PP200 650VA UPS working > with NUT (I didn't see this particular model listed on the HCL.) Thanks! One of the other Sweex models shows a few instant commands:

Re: [Nut-upsuser] "battery is low" logged

On Sep 6, 2019, at 6:28 PM, James wrote: > > I got around to unplugging my UPS and I found it doesn't last nearly as long > as estimated. The estimates are typically less accurate when the load is light (output is showing 5%). Also, as Eyal mentioned, five years is getting old for a lead-acid

Re: [Nut-upsuser] Changing UPS to a bigger APC 1500 1000WA, what driver?

On Sep 14, 2019, at 3:30 PM, Gene Heskett wrote: > > I've drug it as far under the table as I can get it on a 30% heart. > Yeah, I'm getting on, I'll be 85 in about 2 weeks. Heart surgury will be > scheduled in the next few days to replace a worn out, leaky aortic > valve. Piece if cake if

Re: [Nut-upsuser] Monitor UPS Brand SMS

On Aug 6, 2019, at 7:33 PM, Eyal Lebedinsky wrote: > >> I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a raspberry-pi. >> In compatibility list, is listed to use the blazer_ser driver. I use a USB >> adapter to RS-232 conected in to the No-Breake. Follow the comands e confs. >>

Re: [Nut-upsuser] Trouble getting Roline/Powercom UPS recognized

On Jul 17, 2019, at 10:59 AM, Patrick M. Hausen wrote: > > Hi! > >> Am 16.07.2019 um 15:50 schrieb Patrick M. Hausen : >>> Am 16.07.2019 um 15:33 schrieb Charles Lepple :We have >>> another branch that uses the libusb-1.0 API: >>> https://github.c

Re: [Nut-upsuser] Trouble getting Roline/Powercom UPS recognized

On Jul 18, 2019, at 5:09 AM, Patrick M. Hausen wrote: > > Hi! > >> Am 18.07.2019 um 05:02 schrieb Charles Lepple : >> @zykh recommends libusb-compat-1.0. I have not tested it recently, but when >> I last did, I had to run the driver as root on FreeBSD (probably 11.1

Re: [Nut-upsuser] New User Questions - With Belkin USB

On Jul 15, 2019, at 11:15 AM, David White wrote: > > 2. When I check the results from "netstat -t -n" I am NOT finding anything on > 3493. Hmmm. I then tried "netstat -l" since there should be a server socket > listening on 3494, right? There is nothing of 3493. But I do see an entry > with

Re: [Nut-upsuser] New User Questions - With Belkin USB

On Jul 9, 2019, at 12:22 PM, David White wrote: > > So I guess I am wondering if this is related to my problem. I have no idea > how the blazer_usb driver works. For the most part, NUT drivers ending in “_usb” (including blazer_usb) do not need a serial device node in /dev. They use libusb to

Re: [Nut-upsuser] UPS not recognized

On Nov 4, 2019, at 6:24 AM, Dragos Leahu wrote: > > root@omv:~# upscmd -l ups > Instant commands supported on UPS [ups]: > > beeper.toggle - Toggle the UPS beeper > load.off - Turn off the load immediately > load.on - Turn on the load immediately > shutdown.return - Turn off the load and return

Re: [Nut-upsuser] Problems with NUT on Raspberry Pi

On Oct 26, 2019, at 2:50 PM, EP wrote: > > So long I am struggling with other issues. The "newest" one is, NAT-Server > doesn't start anymore after rebooting the pi (USP ist unavailable). It's > driving me mad  Does this help?

Re: [Nut-upsuser] UPS not recognized

On Sep 27, 2019, at 9:19 AM, Dragos Leahu wrote: > > Hello, > > Replaced UPS Kstar Micropower Micro 1200 (managed via blazer_usb) with > https://www.njoy.ro/UPS/horus-plus-2000. The latter doesn't seem to be > supported. > > 1. I tried blazer_usb and usbhid-ups. Any other suggestions?

Re: [Nut-upsuser] How to setup the NUT client on Windows?

On Nov 12, 2019, at 3:49 AM, planet...@gmail.com wrote: > > If they can help me, I would be happy to write and release a How-to to > help others looking for information like me. I admire your persistence in trying to find and write documentation on the Windows port, but there's only so much

Re: [Nut-upsuser] new mobo, ups doesn't connect

On Dec 7, 2019, at 7:01 PM, Gene Heskett wrote: > > What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't seem > to want to talk to it, and the original name _(usbhid-ups) doesn't work > from new mobo. Oh wait, I can't spell. But that didn't help, and a > restart gets this

Re: [Nut-upsuser] Tripp Lite SMART1500LCD repeatedly disconnecting and reconnecting

On Dec 8, 2019, at 5:46 PM, Layne Fowler wrote: > > My UPS is connected to a Raspberry Pi by USB. After a few hours of working, > the service fails. Looking at kernel messages I noticed that the device is > repeatedly disconnecting and reconnecting. > > I have tried using a different USB port

Re: [Nut-upsuser] new mobo, ups doesn't connect

On Dec 8, 2019, at 10:26 PM, Gene Heskett wrote: > I put it back to original and restarted the nut-server. And its now > working. Go figure... >> [myups] >> #driver=hidraw >> driver=usbhid-ups >> #driver=belkin >> #driver=belkinunv >> #driver=genericups >> port=auto >> offdelay=120 >>

Re: [Nut-upsuser] How to setup the NUT client on Windows?

On Nov 12, 2019, at 6:16 PM, planet...@gmail.com wrote: > But... what you are basically saying is that this Windows port in 2019 > is still not usable, still has "major issues" so there's not point > trying to install it and write a documentation about how-to install > it? Not really. I'm

Re: [Nut-upsuser] Status of java interface

On Jan 31, 2020, at 12:13 PM, Mark McMillan wrote: > > I would prefer to use Java as a programming platform for this application, > but I see the NUT Java project has not been updated in a long time (7 > years?!). Is it being tested with new NUT releases or has been abandoned? The NUT

Re: [Nut-upsuser] Hardware compatibility report: APC Smart-UPS_1500 [HCL]

On Jan 8, 2020, at 3:44 PM, Roger Price wrote: > > Gene's posting: > https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-January/011654.html > contains a NUT 2.7.4 update for the APC Smart-UPS_1500 device dump at > https://networkupstools.org/ddl/APC/Smart-UPS_1500.html > > Please note

Re: [Nut-upsuser] nut on armhf, r-pi4b IOW

On Jan 10, 2020, at 5:29 PM, Gene Heskett wrote: > > input.transfer.high: 0 Shouldn't these two be something real > input.transfer.low: 0 ditto Known issue, but only cosmetic: https://github.com/networkupstools/nut/issues/482 ___

Re: [Nut-upsuser] nut on armhf, r-pi4b IOW

On Jan 11, 2020, at 1:58 AM, Gene Heskett wrote: > > On Friday 10 January 2020 20:43:55 Gene Heskett wrote: > >> On Friday 10 January 2020 19:04:11 Charles Lepple wrote: >>> On Jan 10, 2020, at 5:29 PM, Gene Heskett wrote: >>>> input.transfer.high: 0 S

Re: [Nut-upsuser] nut on armhf, r-pi4b IOW

On Jan 11, 2020, at 3:50 PM, Gene Heskett wrote: > >> The problem is further downstream. Even after you map HID names to NUT >> names, then you run into the fact that CPS and NUT are interpreting >> the HID Report Descriptor differently. (Some details here: >>

Re: [Nut-upsuser] nut on armhf, r-pi4b IOW

On Jan 21, 2020, at 10:34 PM, Gene Heskett wrote: > > On Tuesday 21 January 2020 19:52:01 Charles Lepple wrote: > >> sudo lsusb -v -d 0764:0501 > copious output, containing this: > idVendor 0x0764 Cyber Power System, Inc. > idProduct 0x0501 CP1

Re: [Nut-upsuser] nut on armhf, r-pi4b IOW

On Jan 9, 2020, at 4:39 PM, Gene Heskett wrote: > > So for starters, what's the best ./configure command line? There’s this page for matching the layout of an existing Debian install: https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu But remind me, what

Re: [Nut-upsuser] nut on armhf, r-pi4b IOW

On Jan 9, 2020, at 5:51 PM, Gene Heskett wrote: > > On Thursday 09 January 2020 16:59:12 Charles Lepple wrote: > >> On Jan 9, 2020, at 4:39 PM, Gene Heskett wrote: >>> So for starters, what's the best ./configure command line? >> >> There’s this page fo

Re: [Nut-upsuser] Belkin USB UPS Not Turning Off

On Jan 1, 2020, at 3:27 PM, Manuel Wolfshant wrote: > >> Well, I just tried "/sbin/upsdrvctl shutdown" and while I see some output >> and a message shutting down in 30 seconds, nothing happens to the host >> machine or the UPS. Hmmm. > that command only stops the drivers. generally speaking,

Re: [Nut-upsuser] CentOS 8 w/gnome and NUT

On Mar 27, 2020, at 11:51 PM, Ben Kamen wrote: > > I'm playing with a new CentOS 8 with a cyperpower OR500 (a smaller sibling to > the OR700) plugged in via USB. > > GNOME sees the UPS... but NUT does not (even if I shut down gnome). > >> [root@delp ups]# upsdrvctl start >> Network UPS Tools

Re: [Nut-upsuser] thoughts on tripp lite Smart Online UPSs?

rmation. Of those, the 1500s seem to have the most recent information (NUT 2.6.3). (Past performance is not a guarantee of future returns, IANAL, I don't speak for my employer, I don't work for an UPS manufacturer or reseller, I don't own any Tripp Lite stock, something about staying at a Holi

Re: [Nut-upsuser] USB drivers not found when compiling

On Mar 23, 2020, at 9:43 AM, Tyler Montney wrote: > > Compiling against http://www.networkupstools.org/source/2.7/nut-2.7.4.tar.gz > . I also have > libusb-0.1-4 installed but no joy. > The 2.7.4 tarball predates the work towards

Re: [Nut-upsuser] Power Shield Defender 1200 - The Story Continues [HCL]

On Mar 7, 2020, at 2:02 AM, HILL Walter wrote: > > idVendor 0x0665 Cypress Semiconductor > idProduct 0x5161 USB to Serial [...] > N.B. the Product ID and Vendor ID are unchanged between the two models > despite the fact that they function and operate quite differently. >

Re: [Nut-upsuser] Help with Tripp Lite Internet600U

On May 19, 2020, at 9:21 PM, Tom Cooper wrote: > > Bus 001 Device 004: ID 09ae:3024 Tripp Lite > We have only had reports of success with protocol 2010 of INTERNET600U (which would be 09ae:2010 in lsusb). More details:

Re: [Nut-upsuser] ups not being started sat reboot

On Sep 5, 2020, at 5:23 AM, Roger Price wrote: > > On Sat, 5 Sep 2020, Gene Heskett wrote: > >> But runs normally if started. On a rpi4 running an uptodate raspbian >> buster, how do I set it to auto start at boot time? > > Hello Gene, By "auto start" I assume you mean the automatic power on

Re: [Nut-upsuser] Multi UPS Monitoring

On Oct 9, 2020, at 8:07 PM, Rusty Bower wrote: > > Hey all, > > I've read through as many relevant mailing list posts and public blog posts > as I could, but I can't seem to find an answer to my issue. > > I currently have 2x Tripp Lite SMART1500LCDXLs, and I am attempting to > monitor both

Re: [Nut-upsuser] Eaton 5E 1100i USB UPS - failed to claim USB device error

On Aug 19, 2020, at 6:00 AM, Louis van Dyk wrote: > > @DEVS: Could you please re-add the code for using this UPS? It's > still being sold fast and furious in our region, and I'm sure more > people are having the same problem. Kernel quirks need to be added back by the kernel developers.

Re: [Nut-upsuser] Device recommendation Salicru

On Aug 19, 2020, at 8:20 AM, Charles Lepple wrote: > > Getting back to Marc's original question, this is all we have collected for > Salicru: https://github.com/networkupstools/nut-ddl/tree/master/Salicru > > That is not to say that other models don't work, but that information w

  1   2   >