Hello all, While investigating some outstanding issues still labelled as being for NUT v2.8.3 release, I stumbled upon https://github.com/networkupstools/nut/issues/415 and thread https://alioth-lists.debian.net/pipermail/nut-upsuser/2017-April/010591.html (unfortunately it is not in my mailbox, so I can't reply to the old thread), which raised a few distinct points, including:
* Lack of "ALARM" handling in `upsmon` and other notifications - that is now addressed via https://github.com/networkupstools/nut/pull/2658 * Lack of notification about not-handled status tokens - should be logged as part of https://github.com/networkupstools/nut/pull/2709 (but no notification for those "OTHER" tokens as such yet - subject to change in this or later PR) * Presence of unknown tokens - raised a discussion in nut-upsdev and issue https://github.com/networkupstools/nut/issues/2708 * Lack of RB token in ups.status => upsmon REPLBATT notification, when we saw "No battery installed!" - another part of https://github.com/networkupstools/nut/pull/2709 should now set the status flag as well as the alarm message (so two notifications may happen by different triggers... better safe than sorry). So while it took 7 years to bubble through the backlog (with a PoC by Arnaud made almost instantly), there is now some closure to that discussion - and hey, it spawned some others :) Cheers, Jim Klimov
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
