Thanks for posting all those details; they are interesting.
I think it would be helpful to publish the config, at least the nut
logic part, and the details of cyberpower actual vs documented behavior.
(nut github wiki if Jim thinks that makes sense?) Or maybe there is a
better place.
It seems that while how a UPS has to behave to reliably and safely
handle loss of power and restart, with all the possible sequencing, is
pretty well understood on this list, a lot of devices don't do it right.
So having documentation per model that enables buying something that
works seems key, and I don't find that.
Perhaps a warning not to buy cyberpower products would result in bug
fixes. Perhaps not.
It strikes me that it should be possible to express start delay as e.g.
wait until both are true:
power has been stable for 120s
battery is at least 80% charged
For your own situation, I wonder if this is a job for a microcontroller
and a bunch of relays, to patch up your UPS and make your power
sequencing do what you want. Or a tiny computer like an RPI, maybe with
its own extended battery, or hooked into your dhcp server. Maybe that's
a crazy idea, and I know it has a lot of downsides.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220605/7420433c/attachment.sig>