Nut upsuser - Aug 2018 - TrippLite SMX1500LCDT FreeBSD 11.2 trouble

Understood about unplugging USB - others with the 3016 devices have proposed
various methods with USB hubs that have per-port power switching, etc. to
simulate unplugging. I am not a fan of the concept, but I recognize that others
have made more significant investments than the single UPS that I bought.

After you get access to the UPS, what if you try running the driver with
"interrupt_only"? Reference:
https://github.com/networkupstools/nut/issues/300#issuecomment-414481547
> On Aug 20, 2018, at 9:19 AM, Valentin Merkulov <schnobel at
ickis.net> wrote:
> 
> I cannot unplug/re-plug USB though, because currently I'm away from
> the hardware location.
> 
> On Mon, Aug 20, 2018 at 4:07 PM, Valentin Merkulov <schnobel at
ickis.net> wrote:
>> After "No device" error the driver does not seem to be able
to
>> communicate with the UPS (as seen before with the port build):

With interruptonly the driver output goes into a loop (is it an
expected behavior?) After I interrupt the loop and launch the driver
again, it would return "No matching HID device found" until I unplug /
re-plug USB cable.

Gzipped output is attached.
> On Wed, Aug 22, 2018 at 3:49 PM Charles Lepple <clepple at gmail.com>
wrote:
>
> After you get access to the UPS, what if you try running the driver with
"interrupt_only"? Reference:
https://github.com/networkupstools/nut/issues/300#issuecomment-414481547
-------------- next part --------------
A non-text attachment was scrubbed...
Name: usbhid-ups-interruptonly.output.gz
Type: application/x-gzip
Size: 6615 bytes
Desc: not available
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20180822/727ab605/attachment-0001.bin>

On Aug 22, 2018, at 2:03 PM, Valentin Merkulov <schnobel at ickis.net>
wrote:
> 
> With interruptonly the driver output goes into a loop (is it an
> expected behavior?)
Yes, this is what the driver does in the background if you do not pass any
"-D" flags. If you were to start `upsd` at that point, it should be
able to provide data to clients like `upsc`. However, since you needed to pass
`-u root` to the driver, you may need to pass `-u root` to `upsd` as well.
> After I interrupt the loop and launch the driver
> again, it would return "No matching HID device found" until I
unplug /
> re-plug USB cable.
I am not sure which component is at fault: NUT for not resetting something
(though the automatic close-on-exit behavior in the OS should take care of this
- or at least, it has in every other case I am aware of), libusb or FreeBSD for
not cleaning up, or the UPS for not recovering properly.

Issue logged: https://github.com/networkupstools/nut/issues/600