<div dir="ltr">Thanks you are correct I didn't have upsd running.<div><br></div><div>pi@vpn02alp:/usr/local/ups/bin $ ../sbin/upsd<br>Network UPS Tools upsd 2.7.4-2124-g9defa7a9<br>fopen /var/state/ups/upsd.pid: No such file or directory<br>/usr/local/ups/etc/upsd.conf is world readable<br>listening on 127.0.0.1 port 3493<br>listening on ::1 port 3493<br>Connected to UPS [Liebert]: usbhid-ups-Liebert<br>/usr/local/ups/etc/upsd.users is world readable<br>pi@vpn02alp:/usr/local/ups/bin $ ./upsc Liebert<br>battery.charge: 100<br>battery.charge.low: 20<br>battery.charge.warning: 0<br>battery.type: PbAc<br>battery.voltage: 0.0<br>battery.voltage.nominal: 0.0<br>device.mfr: Emerson Network Power<br>device.model: Liebert GXT4<br>device.serial: 1718700042AFB93<br>device.type: ups<br><a href="http://driver.name">driver.name</a>: usbhid-ups<br>driver.parameter.pollfreq: 30<br>driver.parameter.pollinterval: 2<br>driver.parameter.port: auto<br>driver.parameter.productid: 0000<br>driver.parameter.synchronous: no<br>driver.version: 2.7.4-2124-g9defa7a9<br>driver.version.data: Belkin/Liebert HID 0.17<br>driver.version.internal: 0.43<br>ups.mfr: Emerson Network Power<br>ups.model: Liebert GXT4<br>ups.productid: 0000<br>ups.serial: 1718700042AFB93<br>ups.status: OL CHRG<br>ups.vendorid: 10af<br></div><div><br></div><div>The results are similar to the package available for the RPI. I should also mention that I moved to an RPI4 during this if you notice inconsistencies between my newer and earlier posts. I also upgraded the firmware of the RPI to the latest because of issues I saw connecting to a CyberPower UPS.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Feb 28, 2021 at 5:14 PM Jim Klimov <<a href="mailto:jimklimov@cos.ru">jimklimov@cos.ru</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On February 28, 2021 7:08:21 PM UTC, Matthew Rivett via Nut-upsuser <<a href="mailto:nut-upsuser@alioth-lists.debian.net" target="_blank">nut-upsuser@alioth-lists.debian.net</a>> wrote:<br>
>Thanks Jim. Attached are my notes from compiling on the Raspberry PI. <br>
>I<br>
>am having some permission issues but I think it is working enough that<br>
>I<br>
>see the similar results with the latest master.<br>
><br>
>On Mon, Feb 22, 2021 at 7:22 AM Matthew Rivett <<a href="mailto:mrivett@gmail.com" target="_blank">mrivett@gmail.com</a>><br>
>wrote:<br>
><br>
>> Thanks Jim. I will attempt to do the build and see if that works. <br>
>I'll<br>
>> respond back with my results. It might take awhile; I don't have<br>
>much<br>
>> experience compiling code but I"ll figure it out.<br>
>><br>
>> On Mon, Feb 22, 2021 at 6:36 AM Jim Klimov <<a href="mailto:jimklimov@gmail.com" target="_blank">jimklimov@gmail.com</a>><br>
>wrote:<br>
>><br>
>>> At this time, a newer version than pre-packaged would be a build<br>
>from<br>
>>> master branch on github. We are still tying up some loose ends to<br>
>cut a<br>
>>> nect official release.<br>
>>><br>
>>> Jim<br>
>>><br>
>>> On Fri, Feb 19, 2021, 05:06 Matthew Rivett via Nut-upsuser <<br>
>>> <a href="mailto:nut-upsuser@alioth-lists.debian.net" target="_blank">nut-upsuser@alioth-lists.debian.net</a>> wrote:<br>
>>><br>
>>>> Hello,<br>
>>>><br>
>>>> I am trying to connect to my Liebert GXT4 UPS using NUT. I have<br>
>been<br>
>>>> able to connect by using information from the following post.<br>
>>>><br>
>>>><br>
>>>><br>
><a href="https://alioth-lists.debian.net/pipermail/nut-upsuser/2017-June/010682.html" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/pipermail/nut-upsuser/2017-June/010682.html</a><br>
>>>><br>
>>>> I am running on a Raspberry PI 3 Model B Rev 1.2<br>
>>>> pi@vpn01alp:~ $ cat /etc/os-release<br>
>>>> PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"<br>
>>>> NAME="Raspbian GNU/Linux"<br>
>>>> VERSION_ID="9"<br>
>>>> VERSION="9 (stretch)"<br>
>>>> VERSION_CODENAME=stretch<br>
>>>> ID=raspbian<br>
>>>> ID_LIKE=debian<br>
>>>> HOME_URL="<a href="http://www.raspbian.org/" rel="noreferrer" target="_blank">http://www.raspbian.org/</a>"<br>
>>>> SUPPORT_URL="<a href="http://www.raspbian.org/RaspbianForums" rel="noreferrer" target="_blank">http://www.raspbian.org/RaspbianForums</a>"<br>
>>>> BUG_REPORT_URL="<a href="http://www.raspbian.org/RaspbianBugs" rel="noreferrer" target="_blank">http://www.raspbian.org/RaspbianBugs</a>"<br>
>>>><br>
>>>> I installed using<br>
>>>> apt-get install nut nut-server nut-client<br>
>>>><br>
>>>> My configuration is as follows<br>
>>>> pi@vpn01alp:~ $ tail /etc/nut/ups.conf<br>
>>>> # the -h option and/or read the driver's documentation.<br>
>>>><br>
>>>> # Set maxretry to 3 by default, this should mitigate race with slow<br>
>>>> devices:<br>
>>>> maxretry = 3<br>
>>>><br>
>>>> [Liebert]<br>
>>>> productid=0000<br>
>>>> driver = usbhid-ups<br>
>>>> port = auto<br>
>>>> desc = "Liebert"<br>
>>>><br>
>>>> I also added the following to <br>
>/lib/udev/rules.d/62-nut-usbups.rules<br>
>>>> # Liebert GXT4 - usbhid-ups<br>
>>>> ATTR{idVendor}=="10af", ATTR{idProduct}=="0004", MODE="664",<br>
>GROUP="nut"<br>
>>>><br>
>>>> That didn't work so I changed permissions using the following<br>
>>>> pi@vpn01alp:~ $ lsusb<br>
>>>> Bus 001 Device 004: ID 10af:0000 Liebert Corp. UPS<br>
>>>> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.<br>
>>>> SMSC9512/9514 Fast Ethernet Adapter<br>
>>>> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.<br>
>SMC9514 Hub<br>
>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
>>>> pi@vpn01alp:~ $ sudo chmod 0666 /dev/bus/usb/001/004<br>
>>>><br>
>>>> Now I can see the following information. It doesn't appear to be<br>
>>>> complete or accurate.<br>
>>>> pi@vpn01alp:~ $ upsc Liebert<br>
>>>> Init SSL without certificate database<br>
>>>> battery.charge: 100<br>
>>>> battery.charge.low: 20<br>
>>>> battery.charge.warning: 0<br>
>>>> battery.type: PbAc<br>
>>>> battery.voltage: 0.0<br>
>>>> battery.voltage.nominal: 0.0<br>
>>>> device.mfr: Emerson Network Power<br>
>>>> device.model: Liebert GXT4<br>
>>>> device.serial: 1718700042AFB93<br>
>>>> device.type: ups<br>
>>>> <a href="http://driver.name" rel="noreferrer" target="_blank">driver.name</a>: usbhid-ups<br>
>>>> driver.parameter.pollfreq: 30<br>
>>>> driver.parameter.pollinterval: 2<br>
>>>> driver.parameter.port: auto<br>
>>>> driver.parameter.productid: 0000<br>
>>>> driver.parameter.synchronous: no<br>
>>>> driver.version: 2.7.4<br>
>>>> driver.version.data: Belkin/Liebert HID 0.17<br>
>>>> driver.version.internal: 0.41<br>
>>>> ups.mfr: Emerson Network Power<br>
>>>> ups.model: Liebert GXT4<br>
>>>> ups.productid: 0000<br>
>>>> ups.serial: 1718700042AFB93<br>
>>>> ups.status: OL CHRG<br>
>>>> ups.vendorid: 10af<br>
>>>><br>
>>>> I'm not sure how to find the version of NUT I'm running. I found<br>
>the<br>
>>>> changelog (/usr/share/doc/nut) and I'm guessing this is my issue. <br>
>It<br>
>>>> appears the latest comment was from 2017.<br>
>>>><br>
>>>> nut (2.7.4-5) unstable; urgency=medium<br>
>>>><br>
>>>> * debian/control: Build-depends against asciidoc-dblatex,<br>
>Recommends<br>
>>>> are not<br>
>>>> pulled automatically by the buildd (Closes: #851015)<br>
>>>><br>
>>>> -- Laurent Bigonville <<a href="mailto:bigon@debian.org" target="_blank">bigon@debian.org</a>> Wed, 25 Jan 2017<br>
>09:14:10<br>
>>>> +0100<br>
>>>><br>
>>>> I am guessing I need to install a newer version. Is this correct?<br>
>>>><br>
>>>> Thanks,<br>
>>>> Matt<br>
>>>> _______________________________________________<br>
>>>> Nut-upsuser mailing list<br>
>>>> <a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
>>>><br>
><a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
>>><br>
>>><br>
<br>
Thanks for the detailed log. Seems your build went well and device was recognized. <br>
<br>
Note that with debugging mode (with `-D` args) daemons do not go to background currently. This may be okay for example with systemd (but for type=simple IIRC, not forking) but not for init scripts used in many OSes. So while you test, be sure to not abort the driver by Ctrl+C in the terminal :) (can Ctrl+Z and enter `bg` in the shell while experimenting). For production just start it with usual backgrounding debugless mode.<br>
<br>
Also you need to start upsd (also can go from terminal with debugging, but eventually also as a system service) - this is the networked daemon that represents local drivers (usbhid-ups) over network to clients (uupsc, upsmon and many others). I assume the last lines' Connection error is the lack of upsd on localhost.<br>
<br>
Jim<br>
--<br>
Typos courtesy of K-9 Mail on my Android<br>
</blockquote></div>