After configuring the UPS service and setting it to automatically start, it does not start up correctly after a full power cycle.
Instead, an alert is SOMETIMES generated, reflecting communication loss with the UPS:
And the system logs show the following:
At this point, the UPS cannot be seen via "upsc -l".
Issuing "systemctl restart nut-monitor" fixes the situation and the UPS is again visible via "upsc -l", implying that the NUT configuration being saved is correctly but that configuration is perhaps not available to the service at the correct time.