This is really best discussed on the common mailing list since more people
can relate to their more experiences.
In the top screenshot, third line, upsd says it can not connect to the
driver's socket. Is the driver daemon started? (NUT has a 3-layer
architecture with vendor protocol/media drivers represented by upsd on same
system, and networked clients like upsmon running anywhere).
USB can suffer a number of problems, some with hardware (chipmakers do cut
corners; built-in MoBo or external hubs can add to the problem), some with
software stack (released NUT versions still use libusb-0.1, supporting the
very different 1.0 is part of why new release is protracted), some with OS
(device node permissions, e.g. see udev docs if on linux)...
It may help to run the driver as root to rule out the latter at least. Also
in the terminal you can bump verbosity to the max with `-DDDDDD` option to
check what it may complain about, e.g. discovery by device id, etc. Vendors
(in any industry) reserve the right and often do exercise it to change
components and their id's sometimes, to the point of marketing same names
for unrelated devices.
Jim
On Thu, Feb 25, 2021, 00:53 Stephan Macey <sjmacey28 at gmail.com> wrote:
> Hi there-
>
> I emailed you a few weeks ago about the Cyberpower UPS not working so now
> I have a APC BR1000MS which I know is supported because my co worker has
> this exact model is able to get it up and running just using the regular
> local USB, regular HID selection
>
> I always get stuck at UPS monitor demon pending for the status, eventually
> it says failed to retrieve status, I'm not sure if I need to specify
the
> driver because its showing in the system logs driver not found?
>
> [image: image.png]
>
> Whats strange here is that the other package APCupsd is able to see it
> perfectly fine:
>
> [image: image.png]
>
> Any thoughts? I'm desperate to get this to work
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20210225/ab466ab8/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 294106 bytes
Desc: not available
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20210225/ab466ab8/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 110196 bytes
Desc: not available
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20210225/ab466ab8/attachment-0003.png>