>> [Roger wrote:] >>> By the way, do you have offdelay and ondelay values in your ups.conf ? >> >> No, I haven’t. I just added. Should I add more lines here? >> >> maxretry = 3 >> >> [ups] >> driver = usbhid-ups >> port = auto >> desc = "CPS" >> pollinterval = 15>Yes, ondelay and offdelay would go after the [ups] line.>> >> BTW: I testet the ups with the Synology-NAS in the meantime, running the nas as UPS-Server. Same behavior as with the pi. Synology goes to safe mode, turns off the ups. After a second the ups starts up itself again without power >> on line.> This sounds a lot like this issue, so beware that ondelay for CyberPower may not work as described in the generic usbhid-ups documentation:> https://github.com/networkupstools/nut/issues/625OK, thanks, I had a look into this. Does that mean I have to add a line "ondelay=0" and that should result in keeping the UPS off until the power returns?
On Oct 26, 2019, at 10:10 AM, EP wrote:> >> This sounds a lot like this issue, so beware that ondelay for CyberPower may not work as described in the generic usbhid-ups documentation: > >> https://github.com/networkupstools/nut/issues/625 > > > > OK, thanks, I had a look into this. Does that mean I have to add a line "ondelay=0" and that should result in keeping the UPS off until the power returns?I think so. Also, depending on how solid the power is when it comes back on, you may want to consider FAQ #49: https://networkupstools.org/docs/FAQ.html#_my_ups_powers_up_immediately_after_a_power_failure_instead_of_waiting_for_the_batteries_to_recharge I haven't looked into how to fix this in the presence of systemd (assuming Raspbian). It seems complicated, since there are timeouts when systemd starts each unit.
That's it. It works with ondelay=0 (ups shuts down and stays so until power returns). Thanks a lot for your help, I never would have figured this out on my own. Let me ask one more question even if it is not on topic. Is there any chance to tell NUT - server to shut down the system at a battery percentage of i. e. 50? By now it waits until the battery is about 10 %. That's really not good for battery life and there is no advantage for me in keeping the router and switches running for another 10 minutes, the system only shall shutdown cleanly. Am 26. Oktober 2019 16:20:30 MESZ schrieb Charles Lepple <clepple at gmail.com>:>On Oct 26, 2019, at 10:10 AM, EP wrote: >> >>> This sounds a lot like this issue, so beware that ondelay for >CyberPower may not work as described in the generic usbhid-ups >documentation: >> >>> https://github.com/networkupstools/nut/issues/625 >> >> >> >> OK, thanks, I had a look into this. Does that mean I have to add a >line "ondelay=0" and that should result in keeping the UPS off until >the power returns? > >I think so. > >Also, depending on how solid the power is when it comes back on, you >may want to consider FAQ #49: > >https://networkupstools.org/docs/FAQ.html#_my_ups_powers_up_immediately_after_a_power_failure_instead_of_waiting_for_the_batteries_to_recharge > >I haven't looked into how to fix this in the presence of systemd >(assuming Raspbian). It seems complicated, since there are timeouts >when systemd starts each unit.-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20191026/0969ea5e/attachment.html>