[Nut-upsuser] Cyber power CP1500AVR required pollonly?

Jim Klimov jimklimov+nut at gmail.com
Mon Jun 6 16:30:28 BST 2022

According to issues discussed over the past year or so on github, seems so
- that at least some models and/or OSes and/or chipsets have a problem with
libusb interrupt mode; more often failing during device discovery than
after some successful uptime.

I don't think there was reliable statistics to incriminate certain
situations enough to hardcode some preferences however.

Maybe it could help generally to at least log the suggestion for pollonly
(or interruptonly) when the preferred method fails. Or at best try to
change the preference on the fly if not bolted by explicit config.
Question to community: would such change (especially if also of default
behavior) be beneficial?


On Sat, Jun 4, 2022, 19:16 Selva Nair via Nut-upsuser <
nut-upsuser at alioth-lists.debian.net> wrote:

> Ubuntu 22.04
> NUT 2.7.4
> CYberPower CP1500AVRLCDa  using usbhid-ups
> Hello,
> The above combination works well for a few minutes -- including shutdown on
> pulling power or on upsmon -c fsd, notifications etc. Until the driver
> starts reporting error in libusb_get_string, kernel messages on
> USDEVFS_CONTROL failures and upsmon logs 'Data stale'
> It seems the UPS does not support interrupt transfer (or is buggy). On
> adding pollonly=enabled to ups.conf, everything appears to be working
> fine again.
> Is this a known issue? I have seen a number of success reports on this
> model, none mentioning the need for pollonly, so wondering whether I
> should troubleshoot this further.
> Thanks,
> Selva
> _______________________________________________
> 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/20220606/ef027e96/attachment.htm>

More information about the Nut-upsuser mailing list