@bloomo, this won't survive a reboot, correct? Have you created a feature request ticket for this to be added to the GUI?
@budmannxx You're totally correct. It resets every time. It seems the system overwrites all the nut files every time the machine reboots.
The core ups process, which uses ups.conf gets its amended values (if any) from the GUI auxiliary – Obviously why it survives reboot – because those parameters are written in every time. As far as I can tell (and this is just me jumping to conclusions from reading the .sample files and the nut documentation) the ups.conf, upsd.conf and upsmon.conf all configure their relevant processes – different aspects of the nut service that don't share values in their .confs, which is why I did'nt add the MAXAGE value to the GUI ups aux section, as it would have written into ups.conf.
@cyberjock technically it's not a bad setting as the nut upsd
docs seem to think that a 15 second driver response time is fair (default MAXAGE is 15 and that's what is does, but you probably knew that).
What I can't comment on is if this is a CyberPower specific issue or across the board. Also, is this response affected by things like power states? Maybe I'm overthinking it, but I clearly had times in my log that the "stale data" message was more prolific – generally at night when no one was using the system. BUT that said, even during the day the messages were still present, just not on clockwork. Still, I turned off all sleep and power saving features on my drives and it persisted. Maybe more messages at night was just time passing and the messages weren't broken up. Bumping MAXAGE was a clean and definitive fix.
I will create a feature request ticket, but @budmannxx or @cyberdog, would you suggest I request that MAXAGE is bumped or that upsd.conf be editable as aux field? Or this just confuses things?