Hello fRANz, This sounds like an issue with 2023+ "BXnnnnMI" APC models, addressed with PR https://github.com/networkupstools/nut/pull/2565 - see also issues https://github.com/networkupstools/nut/issues/2347 and https://github.com/networkupstools/nut/issues/2533 for related context.
The solution is not part of a published NUT release yet, so your best bet at the moment would be a custom build of NUT - see e.g. https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests for instructions. Hope this helps, Jim Klimov On Sun, Dec 1, 2024 at 2:03 PM Greg Troxel via Nut-upsuser < [email protected]> wrote: > 1) you didn't say what happened when you read the manual and looked at > the device's indications (audible alarms, lights) > > 2) you didn't say how long you let it sit after plugging it in > > 3) 2.8.0 is old. Please update to 2.8.1 at least. (That Debian has an > old version is a Debian problem, not a nut problem.) > > I dimly recall a parsing fix for multiple status items at once. > > If you have ok status in the log and bad notifications then the tg.sh > is likely relevant, but you didn't post that. > > (As alawys, follow up on list, not to me directly. It would be rude of > me to quote private mail on the list, and I don't want to provide > offlist help as that doesn't help the next person.) > > _______________________________________________ > Nut-upsuser mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
