[Nut-upsuser] Liebert GXT4

Mon Mar 1 00:02:48 GMT 2021

I'm new to this project.  What would the next steps be to get the values
working correctly?  I will help where I have the necessary skills.

On Sun, Feb 28, 2021 at 5:39 PM Matthew Rivett <mrivett at gmail.com> wrote:

> Thanks you are correct I didn't have upsd running.
>
> pi at vpn02alp:/usr/local/ups/bin $ ../sbin/upsd
> Network UPS Tools upsd 2.7.4-2124-g9defa7a9
> fopen /var/state/ups/upsd.pid: No such file or directory
> /usr/local/ups/etc/upsd.conf is world readable
> listening on 127.0.0.1 port 3493
> listening on ::1 port 3493
> Connected to UPS [Liebert]: usbhid-ups-Liebert
> /usr/local/ups/etc/upsd.users is world readable
> pi at vpn02alp:/usr/local/ups/bin $ ./upsc Liebert
> battery.charge: 100
> battery.charge.low: 20
> battery.charge.warning: 0
> battery.type: PbAc
> battery.voltage: 0.0
> battery.voltage.nominal: 0.0
> device.mfr: Emerson Network Power
> device.model: Liebert GXT4
> device.serial: 1718700042AFB93
> device.type: ups
> driver.name: usbhid-ups
> driver.parameter.pollfreq: 30
> driver.parameter.pollinterval: 2
> driver.parameter.port: auto
> driver.parameter.productid: 0000
> driver.parameter.synchronous: no
> driver.version: 2.7.4-2124-g9defa7a9
> driver.version.data: Belkin/Liebert HID 0.17
> driver.version.internal: 0.43
> ups.mfr: Emerson Network Power
> ups.model: Liebert GXT4
> ups.productid: 0000
> ups.serial: 1718700042AFB93
> ups.status: OL CHRG
> ups.vendorid: 10af
>
> 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.
>
>
> On Sun, Feb 28, 2021 at 5:14 PM Jim Klimov <jimklimov at cos.ru> wrote:
>
>> On February 28, 2021 7:08:21 PM UTC, Matthew Rivett via Nut-upsuser <
>> nut-upsuser at alioth-lists.debian.net> wrote:
>> >Thanks Jim.  Attached are my notes from compiling on the Raspberry PI.
>> >I
>> >am having some permission issues but I think it is working enough that
>> >I
>> >see the similar results with the latest master.
>> >
>> >On Mon, Feb 22, 2021 at 7:22 AM Matthew Rivett <mrivett at gmail.com>
>> >wrote:
>> >
>> >> Thanks Jim.  I will attempt to do the build and see if that works.
>> >I'll
>> >> respond back with my results.  It might take awhile; I don't have
>> >much
>> >> experience compiling code but I"ll figure it out.
>> >>
>> >> On Mon, Feb 22, 2021 at 6:36 AM Jim Klimov <jimklimov at gmail.com>
>> >wrote:
>> >>
>> >>> At this time, a newer version than pre-packaged would be a build
>> >from
>> >>> master branch on github. We are still tying up some loose ends to
>> >cut a
>> >>> nect official release.
>> >>>
>> >>> Jim
>> >>>
>> >>> On Fri, Feb 19, 2021, 05:06 Matthew Rivett via Nut-upsuser <
>> >>> nut-upsuser at alioth-lists.debian.net> wrote:
>> >>>
>> >>>> Hello,
>> >>>>
>> >>>> I am trying to connect to my Liebert GXT4 UPS using NUT.  I have
>> >been
>> >>>> able to connect by using information from the following post.
>> >>>>
>> >>>>
>> >>>>
>> >
>> https://alioth-lists.debian.net/pipermail/nut-upsuser/2017-June/010682.html
>> >>>>
>> >>>> I am running on a Raspberry PI 3 Model B Rev 1.2
>> >>>> pi at vpn01alp:~ $ cat /etc/os-release
>> >>>> PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
>> >>>> NAME="Raspbian GNU/Linux"
>> >>>> VERSION_ID="9"
>> >>>> VERSION="9 (stretch)"
>> >>>> VERSION_CODENAME=stretch
>> >>>> ID=raspbian
>> >>>> ID_LIKE=debian
>> >>>> HOME_URL="http://www.raspbian.org/"
>> >>>> SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
>> >>>> BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
>> >>>>
>> >>>> I installed using
>> >>>> apt-get install nut nut-server nut-client
>> >>>>
>> >>>> My configuration is as follows
>> >>>>  pi at vpn01alp:~ $ tail /etc/nut/ups.conf
>> >>>> # the -h option and/or read the driver's documentation.
>> >>>>
>> >>>> # Set maxretry to 3 by default, this should mitigate race with slow
>> >>>> devices:
>> >>>> maxretry = 3
>> >>>>
>> >>>> [Liebert]
>> >>>>         productid=0000
>> >>>>         driver = usbhid-ups
>> >>>>         port = auto
>> >>>>         desc = "Liebert"
>> >>>>
>> >>>> I also added the following to
>> >/lib/udev/rules.d/62-nut-usbups.rules
>> >>>> #  Liebert GXT4  - usbhid-ups
>> >>>> ATTR{idVendor}=="10af", ATTR{idProduct}=="0004", MODE="664",
>> >GROUP="nut"
>> >>>>
>> >>>> That didn't work so I changed permissions using the following
>> >>>> pi at vpn01alp:~ $ lsusb
>> >>>> Bus 001 Device 004: ID 10af:0000 Liebert Corp. UPS
>> >>>> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
>> >>>> SMSC9512/9514 Fast Ethernet Adapter
>> >>>> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
>> >SMC9514 Hub
>> >>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> >>>> pi at vpn01alp:~ $ sudo chmod 0666 /dev/bus/usb/001/004
>> >>>>
>> >>>> Now I can see the following information.  It doesn't appear to be
>> >>>> complete or accurate.
>> >>>> pi at vpn01alp:~ $ upsc Liebert
>> >>>> Init SSL without certificate database
>> >>>> battery.charge: 100
>> >>>> battery.charge.low: 20
>> >>>> battery.charge.warning: 0
>> >>>> battery.type: PbAc
>> >>>> battery.voltage: 0.0
>> >>>> battery.voltage.nominal: 0.0
>> >>>> device.mfr: Emerson Network Power
>> >>>> device.model: Liebert GXT4
>> >>>> device.serial: 1718700042AFB93
>> >>>> device.type: ups
>> >>>> driver.name: usbhid-ups
>> >>>> driver.parameter.pollfreq: 30
>> >>>> driver.parameter.pollinterval: 2
>> >>>> driver.parameter.port: auto
>> >>>> driver.parameter.productid: 0000
>> >>>> driver.parameter.synchronous: no
>> >>>> driver.version: 2.7.4
>> >>>> driver.version.data: Belkin/Liebert HID 0.17
>> >>>> driver.version.internal: 0.41
>> >>>> ups.mfr: Emerson Network Power
>> >>>> ups.model: Liebert GXT4
>> >>>> ups.productid: 0000
>> >>>> ups.serial: 1718700042AFB93
>> >>>> ups.status: OL CHRG
>> >>>> ups.vendorid: 10af
>> >>>>
>> >>>> I'm not sure how to find the version of NUT I'm running.  I found
>> >the
>> >>>> changelog (/usr/share/doc/nut) and I'm guessing this is my issue.
>> >It
>> >>>> appears the latest comment was from 2017.
>> >>>>
>> >>>> nut (2.7.4-5) unstable; urgency=medium
>> >>>>
>> >>>>   * debian/control: Build-depends against asciidoc-dblatex,
>> >Recommends
>> >>>> are not
>> >>>>     pulled automatically by the buildd (Closes: #851015)
>> >>>>
>> >>>>  -- Laurent Bigonville <bigon at debian.org>  Wed, 25 Jan 2017
>> >09:14:10
>> >>>> +0100
>> >>>>
>> >>>> I am guessing I need to install a newer version.  Is this correct?
>> >>>>
>> >>>> Thanks,
>> >>>> Matt
>> >>>> _______________________________________________
>> >>>> Nut-upsuser mailing list
>> >>>> Nut-upsuser at alioth-lists.debian.net
>> >>>>
>> >https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>> >>>
>> >>>
>>
>> Thanks for the detailed log. Seems your build went well and device was
>> recognized.
>>
>> 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.
>>
>> 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.
>>
>> Jim
>> --
>> Typos courtesy of K-9 Mail on my Android
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20210228/7a7e0081/attachment.htm>