This bug seems to be non-version specific, but has been happening since at least 10.12.
Whenever I install apcupsd on a MacBook (which already has an internal battery), it claims that it can't access the UPS:
'ioupsd' is not running, yet it's as if it's taking control of all battery-class devices, regardless of if they're internal or external.
When I run it in a VM and pass through the UPS, it sees it just fine:
With apcupsd uninstalled, it sees the battery just fine.
Apple says it's only able to see one battery at a time. That is a perplexing statement.
A design oversight, perhaps?
Whenever I install apcupsd on a MacBook (which already has an internal battery), it claims that it can't access the UPS:
'ioupsd' is not running, yet it's as if it's taking control of all battery-class devices, regardless of if they're internal or external.
When I run it in a VM and pass through the UPS, it sees it just fine:
With apcupsd uninstalled, it sees the battery just fine.
Apple says it's only able to see one battery at a time. That is a perplexing statement.
A design oversight, perhaps?
Last edited: