Cheers all,
Got an interesting report at
https://github.com/networkupstools/nut/issues/2208 about Qx devices that do
not respond to NUT unless `upsmart` somehow inits them first (until a
re-plug). This behavior is something I've heard of a couple of times, and
now there are pcap captures to help smart folks make heads or tails of it
and teach `nutdrv_qx` the optionto initialize the UPS communications
similarly.
Any takers lurking on the dev list? ;)
In other news, at https://github.com/networkupstools/nut/issues/2207
there's a low-hanging fruit RFE to make upsmon data-stale logging less
intensive in a comms outage.
I've got a large backlog IRL, so would love someone stepping up here to
propose PRs.
Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20231129/cb55a259/attachment.htm>
