Nut upsuser - Apr 2020 - Issues with usbhid-ups on TrippLite INTERNET600U

Hello,
  I am trying to get my synology DS 418play to connect to my new
INTERNET600U UPS, but it appears not to work. I contacted TrippLite and
they said the unit is using a new comm protocol 3024. Is there a way to
make this work with usbhid-ups?

More details of my story here:
https://community.synology.com/enu/forum/1/post/132984

Thanks for your help!
-Troy

----------------------------------------------
Troy Bouman
616.990.2699
www.TroyBouman.com <http://www.troybouman.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200411/3f7d290f/attachment.html>

On April 11, 2020 2:31:11 PM UTC, Troy Bouman <tmbouman at mtu.edu>
wrote:
>Hello,
>  I am trying to get my synology DS 418play to connect to my new
>INTERNET600U UPS, but it appears not to work. I contacted TrippLite and
>they said the unit is using a new comm protocol 3024. Is there a way to
>make this work with usbhid-ups?
>
>More details of my story here:
>https://community.synology.com/enu/forum/1/post/132984
>
>Thanks for your help!
>-Troy
>
>----------------------------------------------
>Troy Bouman
>616.990.2699
>www.TroyBouman.com <http://www.troybouman.com/>
Do you have a possibility to build code on/for synology? Specifically, the
version strings of usbhid-ups 0.38
https://github.com/networkupstools/nut/blame/6b3b27e5b445e36f5ddc6381d037394d40825b1a/drivers/usbhid-ups.c
and tripplite hid 0.81
https://github.com/networkupstools/nut/blame/master/drivers/tripplite-hid.c date
synology's fork used there between 2012 and 2014 which is rather old
(between 2.6.5 and 2.7.3 by upstream dates, probably 2.6.5 as latest of that
series).

Perhaps you can try a package of that older code on some other machine vs. this
UPS to see if it misbehaves similarly. If yes, try then a build of master branch
from GitHub, or even of one of the branches for libusb-1.0 integration rather
than old libusb-0.1 that had problems with long-term connections (see issue #300
and recent email archive for details). BTW, Your post mentioned a USB hub, it is
generally a dice-roll to get one whose chip-makers implenented the protocol,
reset-support in chaining, etc. correctly, so for UPSes prefer a direct link.

If that newer build does work, it would rule out issues with the ups itself
against modern NUT, and you can somehow get an updated NUT package for synology
(ask them, build yours, ...) and if it still does not work, there is work on NUT
community side (anyone welcome to join anytime) and there gotta be ways to try
getting a data dump from device to figure out the protocol, or preferably get a
vendor's spec.

I am not at a computer now so can't check if usbhid-ups has a subdriver for
a sort of standard hid fallback, like IETF MIB for SNMP UPSes. Probably one
should be there, and the Tripplite answer implies the device should talk that.

Finally, on OS side there may be different USB frameworks - for example,
"usb hid" on Solaris is for kbd/mouse, the real Human Interface
Devices, and for UPSes there is "ugen".

Hope this helps,
Jim Klimov
--
Typos courtesy of K-9 Mail on my Android