>> TL;DR: Despite otherwise seeming to work correctly, I can’t monitor a Back-UPS BX1600MI in Linux without seeing a constant stream of spurious battery detach/reattach and power fail/restore events that last less than 2 seconds each.
It sounds like the Windows software probably debounces the incoming events, only bubbling up those that are sufficiently time-stable, to account for bargain sensor false positives?
I'd bet you're right. Experience at $Job is that certain cheapo UPS's can be miserably twitchy about detecting power problems and switching to their inverters. After a week of the clickity-clicks of the cut-over relays - $Employee and his office mates may ask for the UPS to be removed.
Right, the window tool debounces the events, IMO the battery attach/disconnnect messages are a poor mans heartbeat signal on the protocol. That ACPI/Windows didn't "sleep" the USB port, or that the controller in the UPS (chinese junk) didn't crash.
It sounds like the Windows software probably debounces the incoming events, only bubbling up those that are sufficiently time-stable, to account for bargain sensor false positives?
Edit: Looks like the apcupsd collection also has some EEPROM programming utilities... (for supported devices) http://www.apcupsd.org/manual/#configuration-directives-used...