Re: [Nut-upsuser] Liebert GXT4
On Mar 3, 2021, at 7:43 AM, Matthew Rivett via Nut-upsuser wrote: > > Charles, > > Being me I'd love to have all the data but that shouldn't be necessary. :) That's fair :-) > What got me interested is that the frequency is shown on the UPS and I was > curious what was going on when the power issues around President's Day. I > wondered if I could capture that output from the UPS. The short answer is that there isn't anything that looks like low-hanging fruit for frequency. If an UPS includes a frequency Usage ID in its HID Report Descriptor, NUT can usually pick that up (even if it gets the value wrong), and I'm not seeing something that maps to input.frequency. If you wanted to log values over time, there are a bunch of "UPS.PowerSummary.Undefined" lines, and the bytes before them are candidates for frequency. Here's a simple example for a value that seems to be working: 0.113694 [D3] Report[get]: (2 bytes) => 13 14 0.113860 [D1] Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8, Value: 20 The first line with the hex bytes is the raw data coming back from the UPS. First byte (0x13) is the report ID, which you can see listed on the next line. The Path is the list of HID Usage IDs that are accumulated while NUT parses the Report Descriptor. They generally map 1:1 with NUT variables, so ...RemainingCapacityLimit is "battery.charge.low". The Offset and Size fields tell NUT how to carve up the bits after the ReportID. Offset and Size are in bits, so the 8 bits after 0x13 are 0x14, which is 20. Frequency is a little more complicated. You probably want more precision than just 59 or 60 Hz, so it is typically multiplied by some scaling factor so that integers can represent e.g. 59.9 Hz with a scale factor of 10. Unless it's a small scale factor (under 5), the scaled value won't fit into a single byte (0-255). HID reports are little-endian, so for a 16-bit value, you would need to add two contiguous bytes, and multiply the second byte by 256. There are a lot of potential factors, but I don't see any likely candidates at the moment. You'd probably want to collect a lot of data, and grab a few readings from the front panel to correlate. I'm not sure what to make of the other values. 0.208056 [D3] Report[buf]: (5 bytes) => 05 36 00 30 00 0.208187 [D2] Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset: 0, Size: 16, Value: 0 0.208311 LineVoltage exponent looks wrong, but not correcting. 0.208463 [D3] Report[buf]: (5 bytes) => 05 36 00 30 00 0.208593 [D2] Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: 16, Size: 16, Value: 0 0.208718 ConfigVoltage exponent looks wrong, but not correcting. Those lines talk about LineVoltage and ConfigVoltage, which usually refer to AC voltages when taken together, but the values in the descriptor (54 and 48 decimal, from 0x0036 and 0x0030) seem like they could be DC battery voltage, and nominal battery voltage. (The correction refers to backing out an errant exponent which forces the values to be very close to zero.) > I guess whatever the minimum data to have nut work properly. I wouldn't mind > using this to shutdown multiple computers in the event of a power outage. This one's a little easier - you just need working OL/OB and LB bits in ups.status, plus a working shutdown command. There are potential timing gotchas (I don't see shutdown delay values in upsc output, so hopefully there are fixed delays that are long enough), but you'll want to make sure you can do the simple stuff first, and the best way to be sure about that is to test. There are suggestions in the NUT documentation about using dummy loads, etc. ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Liebert GXT4
On Feb 28, 2021, at 7:02 PM, Matthew Rivett via Nut-upsuser wrote: > > 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. I can't promise if/when I will have time to look at the results, but to debug the 0.0 values, it would be useful to increase the driver debug output level from -D2 to -D3. That includes the raw bytes from the UPS. Also, what other variables are you looking for? (Previous Liebert GXT units have not provided as many measurements as other UPSes.) -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Liebert GXT4
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 wrote:
> Thanks you are correct I didn't have upsd running.
>
> pi@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@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:
> 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:
> 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 wrote:
>
>> On February 28, 2021 7:08:21 PM UTC, Matthew Rivett via Nut-upsuser <
>> nut-upsuser@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
>> >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
>> >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@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@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@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=
>> 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@vpn01alp:~ $ lsusb
>> Bus 001 Device 004: ID 10af: 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@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@vpn01alp:~ $ upsc Liebert
>> Init SSL without
Re: [Nut-upsuser] Liebert GXT4
Thanks you are correct I didn't have upsd running.
pi@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@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:
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:
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 wrote:
> On February 28, 2021 7:08:21 PM UTC, Matthew Rivett via Nut-upsuser <
> nut-upsuser@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
> >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
> >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@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@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@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=
> 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@vpn01alp:~ $ lsusb
> Bus 001 Device 004: ID 10af: 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@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@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
>
Re: [Nut-upsuser] Liebert GXT4
pi@vpn02alp:/usr/local/ups/bin $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster 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; On Sun, Feb 28, 2021 at 2:32 PM Matthew Rivett wrote: > I should note that I switched to an RPI4 since I first started this. > > Linux vpn02alp 5.10.17-v7l+ #1403 SMP Mon Feb 22 11:33:35 GMT 2021 armv7l > GNU/Linux > > On Sun, Feb 28, 2021 at 2:22 PM Roger Price wrote: > >> On Sun, 28 Feb 2021, Matthew Rivett via Nut-upsuser wrote: >> >> > I am running on a Raspberry PI 3 Model B Rev 1.2 >> > pi@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 >> >> Hello Matthew, Sorry if this is off-topic. What is the result of command >> >>uname -a >> >> on your Raspberry Pi ? Thanks, Roger >> >> ___ >> Nut-upsuser mailing list >> Nut-upsuser@alioth-lists.debian.net >> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >> > ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Liebert GXT4
On Sun, 28 Feb 2021, Matthew Rivett via Nut-upsuser wrote: I am running on a Raspberry PI 3 Model B Rev 1.2 pi@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 Hello Matthew, Sorry if this is off-topic. What is the result of command uname -a on your Raspberry Pi ? Thanks, Roger ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Liebert GXT4
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 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 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@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@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@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=
>>> 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@vpn01alp:~ $ lsusb
>>> Bus 001 Device 004: ID 10af: 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@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@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:
>>> 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:
>>> 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 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@alioth-lists.debian.net
>>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>>
>>
<>
<>
___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Liebert GXT4
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 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@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@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@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=
>> 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@vpn01alp:~ $ lsusb
>> Bus 001 Device 004: ID 10af: 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@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@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:
>> 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:
>> 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 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@alioth-lists.debian.net
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
>
___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
