[Nut-upsuser] Debian 13 (NUT 2.8.1) fixes upssched bug, but floods systemctl log

[Roger Price]

I installed Debian 13.1 and was provided with NUT 2.8.1.  The good news is that 
this fixes the upssched habit of running a tight loop generating full cpu 
load. [1]

My ups.conf includes

 [heartbeat]
        driver = dummy-ups
        port = heartbeat.conf
        mode = dummy-loop
        desc = "Heart beat validation of NUT" 

and my heartbeat.conf specification is 

 # heartbeat.conf   10 minute heartbeat. Time unit is the second
 ups.status: OL 
 TIMER 300
 ups.status: OB
 TIMER 300

The heart-beat now runs correctly, but the command 

 root at titan /etc/nut systemctl status nut-monitor 
 ● nut-monitor.service - Network UPS Tools - power device monitor and shutdown 
   controller
     Loaded: loaded (/usr/lib/systemd/system/nut-monitor.service; enabled; 
             preset: enabled)

(lines skipped)

     Active: active (running) since Thu 2025-11-27 16:27:32 CET; 1 day 16h ago
             ├─87562 /lib/nut/upsmon -F
             └─87566 /usr/sbin/upssched "UPS heartbeat at localhost: On battery 
                                         +++ Onduleur sur batterie"

 Nov 29 07:40:57 titan nut-monitor[98134]: Network UPS Tools upsmon 2.8.1
 Nov 29 07:45:57 titan nut-monitor[98161]: Network UPS Tools upsmon 2.8.1
 Nov 29 07:51:02 titan nut-monitor[98181]: Network UPS Tools upsmon 2.8.1
 Nov 29 07:56:02 titan nut-monitor[98190]: Network UPS Tools upsmon 2.8.1
 Nov 29 08:01:02 titan nut-monitor[98229]: Network UPS Tools upsmon 2.8.1
 ...

fills the systemctl log with reminders every 300 seconds that this is indeed NUT 
2.8.1 .  It's good to have at least 2.8.1 in Debian, but is there some way of 
skipping the 300 second reminders ?

Roger

[1] https://www.mail-archive.com/nut-upsuser@alioth-lists.debian.net/msg02422.html