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-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-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: [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-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-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-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

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

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

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

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

  1   2   3   4   5   6   7   8   9   10   >