Nut upsuser - May 2023 - NUT support for the new Tripp Lite AVR700U (USB 3024) under OpenWrt?

I'm mostly not online for a few more days, so can't check directly.

The general answers to the two questions would be:

1) checking if it is there:
* revise if it is mentioned in the NEWS file (in sources - release tarball
or on github);
* check issues on github;
* search/grep for 3024 in current/release-tagged codebase...

2) getting it to your system: versioning looks debianish, some
distros/repos (sid, experimental?) already shipped 2.8.0, maybe you can
lift such a build to your box. Otherwise, build your own (in this case
current master may be preferable to a year-old release with its few known
issues baked in and fixed since, or making and adding custom patches to
existing package recipe). It may be possible Several styles of instructions
are in source docs, github wiki...

Good luck, and
Hope this helps,
Jim Klimov


On Sun, May 7, 2023, 01:27 Feliciano Chavez <chavezfeliciano at
hotmail.com>
wrote:
> That It may be right (I don't know), however, where could we confirm
> whether 3024 is already supported for 2.8.0 or newer?
> And let's suppose it is. Because current OpenWrt releases are built
> arround 2.7.4-27, what could I try to backport that (driver mod) to
> 2.7.4-27?
>
> ------------------------------
> *De:* Jim Klimov <jimklimov+nut at gmail.com>
> *Enviado:* s?bado, 6 de mayo de 2023 4:21 p. m.
> *Para:* Feliciano Chavez <chavezfeliciano at hotmail.com>
> *Cc:* Arnaud Quette via Nut-upsuser <nut-upsuser at
alioth-lists.debian.net>
> *Asunto:* Re: [Nut-upsuser] NUT support for the new Tripp Lite AVR700U
> (USB 3024) under OpenWrt?
>
> I think 3024 was added after NUT 2.7.4 release.
>
> On Thu, May 4, 2023, 18:20 Feliciano Chavez via Nut-upsuser <
> nut-upsuser at alioth-lists.debian.net> wrote:
>
> Dears,
>
> I'm trying to connect this new version of the AVR700U to nut - 2.7.4-27
> running over OpenWrt 22.03.5, installed from the stable release
> repositories, for an ath79 USB2.0 gigabit WiFi router.
>
> According to the supported list, I thought this UPS was supposed to use
> the USB 2010 protocol, but I guess that was an old version because now uses
> the 3024 protocol (perhaps it would be good to add a note for future
> buyers).
> root at Router:/# lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux 5.10.176 ehci_hcd EHCI Host
> Controller
> Bus 002 Device 002: ID 09ae:3024 Tripp Lite AVR700U
> Bus 002 Device 001: ID 1d6b:0001 Linux 5.10.176 ohci_hcd Generic Platform
> OHCI controller
>
> Under networkupstools at github, I noticed the issue 808, which states
> this could be (partially) supported by including the vendor id and
> productid in ups.conf. Therefore, for the OpenWrt use case, I would have to
> add the following to /etc/config/nut-server:
> config driver 'tripplite'
> option driver usbhid-ups
> option port auto
> option vendorid 09ae
> option productid 3024
> This avoids the previous 3024 "not supported" error message,
> root at Router:/# upsdrvctl start
> Network UPS Tools - UPS driver controller 2.7.4
> Network UPS Tools - Generic HID driver 0.41 (2.7.4)
> USB communication driver 0.33
> Using subdriver: TrippLite HID 0.82
>
> but still can't connect to the UPS:
> root at Router:/# upsc tripplite
> Error: Driver not connected
>
> So I kindly ask you what could we do in this case
>
> Note: I haven't seen an udev rules file under the running OpenWrt.
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20230508/894d7eff/attachment.htm>

> I think 3024 was added after NUT 2.7.4 release.
Just chiming in to confirm that this is correct (if it was added at all?). 2.7.4
did not include 3024. That is where the product ID in the conf file comes in.

Thanks for your support, Jim.

I found a workaround:
logread showed some access-denied errors, and because I don't know exactly
what it may be (except the lack of udev rules perhaps), I ran upsd as root and
it connected with the UPS. Therefore I wonder whether a more elegant solution
could be used for this part?

But there are several things about the readings with the 2.7.4 usbhid-ups driver
with this UPS that doesn't make sense:
.- the frequency here should be around 60Hz, but it reports 6010 or 5990 or so.
I suppose a 100 division is missing
.- the input/output and battery voltages are 0V, etc.

I have built some OpenWrt firmware images, but mostly customizing stuff, I
don't have experience integrating a new version of a solution, I would have
to keep investigating to avoid bricking my test device. I would prefer to mod
the currently running files/libraries, if possible.

FWIW, here's the version info about the relevant objects of the current
22.03.5 stable release of this embedded distro that ships with nut 2.7.4 (I
don't know whether is debian-based, but .ipk packages are installed via
opkg):
.-
kernel&kmod-usb-core&kmod-usb-ohci&kmod-hid&kmod-hid-generic&kmod-usb-hid
5.10.176-1,
.- usbutils 014-1
.- nut&nut-common&nut-server&nut-upsc&nut-driver-usbhid-ups
2.7.4-27
.- usbhid-ups 0.41 (2.7.4) USB communication driver 0.33

________________________________
De: Jim Klimov <jimklimov+nut at gmail.com>
Enviado: lunes, 8 de mayo de 2023 7:27 a. m.
Para: Feliciano Chavez <chavezfeliciano at hotmail.com>
Cc: Arnaud Quette via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>
Asunto: Re: [Nut-upsuser] NUT support for the new Tripp Lite AVR700U (USB 3024)
under OpenWrt?

I'm mostly not online for a few more days, so can't check directly.

The general answers to the two questions would be:

1) checking if it is there:
* revise if it is mentioned in the NEWS file (in sources - release tarball or on
github);
* check issues on github;
* search/grep for 3024 in current/release-tagged codebase...

2) getting it to your system: versioning looks debianish, some distros/repos
(sid, experimental?) already shipped 2.8.0, maybe you can lift such a build to
your box. Otherwise, build your own (in this case current master may be
preferable to a year-old release with its few known issues baked in and fixed
since, or making and adding custom patches to existing package recipe). It may
be possible Several styles of instructions are in source docs, github wiki...

Good luck, and
Hope this helps,
Jim Klimov


On Sun, May 7, 2023, 01:27 Feliciano Chavez <chavezfeliciano at
hotmail.com<mailto:chavezfeliciano at hotmail.com>> wrote:
That It may be right (I don't know), however, where could we confirm whether
3024 is already supported for 2.8.0 or newer?
And let's suppose it is. Because current OpenWrt releases are built arround
2.7.4-27, what could I try to backport that (driver mod) to 2.7.4-27?

________________________________
De: Jim Klimov <jimklimov+nut at gmail.com<mailto:jimklimov%2Bnut at
gmail.com>>
Enviado: s?bado, 6 de mayo de 2023 4:21 p. m.
Para: Feliciano Chavez <chavezfeliciano at
hotmail.com<mailto:chavezfeliciano at hotmail.com>>
Cc: Arnaud Quette via Nut-upsuser <nut-upsuser at
alioth-lists.debian.net<mailto:nut-upsuser at alioth-lists.debian.net>>
Asunto: Re: [Nut-upsuser] NUT support for the new Tripp Lite AVR700U (USB 3024)
under OpenWrt?

I think 3024 was added after NUT 2.7.4 release.

On Thu, May 4, 2023, 18:20 Feliciano Chavez via Nut-upsuser <nut-upsuser at
alioth-lists.debian.net<mailto:nut-upsuser at alioth-lists.debian.net>>
wrote:
Dears,

I'm trying to connect this new version of the AVR700U to nut - 2.7.4-27
running over OpenWrt 22.03.5, installed from the stable release repositories,
for an ath79 USB2.0 gigabit WiFi router.

According to the supported list, I thought this UPS was supposed to use the USB
2010 protocol, but I guess that was an old version because now uses the 3024
protocol (perhaps it would be good to add a note for future buyers).
root at Router:/# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux 5.10.176 ehci_hcd EHCI Host Controller
Bus 002 Device 002: ID 09ae:3024 Tripp Lite AVR700U
Bus 002 Device 001: ID 1d6b:0001 Linux 5.10.176 ohci_hcd Generic Platform OHCI
controller

Under networkupstools at github, I noticed the issue 808, which states this
could be (partially) supported by including the vendor id and productid in
ups.conf. Therefore, for the OpenWrt use case, I would have to add the following
to /etc/config/nut-server:
config driver 'tripplite'
??????option driver usbhid-ups
??????option port auto
??????option vendorid 09ae
??????option productid 3024
This avoids the previous 3024 "not supported" error message,
root at Router:/# upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
Using subdriver: TrippLite HID 0.82

but still can't connect to the UPS:
root at Router:/# upsc tripplite
Error: Driver not connected

So I kindly ask you what could we do in this case

Note: I haven't seen an udev rules file under the running OpenWrt.

_______________________________________________
Nut-upsuser mailing list
Nut-upsuser at alioth-lists.debian.net<mailto:Nut-upsuser at
alioth-lists.debian.net>
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20230508/58fa5074/attachment-0001.htm>