Connected pop up not appearing after reconnecting in some situations

[gbakeman]

On Win10 I got a single notification when the nut server stopped. "Reconnection In Progress\nReconnection..."
To be perfect a second notification an hour later when the nut server restarted would be nice.

When I look at the recent messages drop down list in WinNUT Client there are three messages.

1. Lost Connect to rpi:3493 (should it say "Lost Connection to rpi:3493"?)
2. Reconnection In Progress (should the notification say "Lost Connection: Reconnection In Progress" as no "Connection lost" notification was given?)
3. Connection to Nut Host rpi:3493 Established (should this GUI message also be sent as a Windows notification?)

Originally posted by @yoyoma2 in #65 (comment)

Here's what I see on Win10. Only one notification for the entire backup process starting at 7:42 AM ending an hour later. It was a little surprising to see "reconnecting" without any "Lost connection" text.

Points of possible interest:

• I'm on Win10 not Win11

• The RaspiBackup script stops the nut server service during the backup but the ethernet connection to the rpi is never broken (different code path than disabling network adapter?)

• The WinNUT client GUI has the "Connection to NUT Host rpi:3493 Established" message precisely after the backup but no Windows notification at all

• My "Create LogFile" setting was off (Next backup I'll enable the log file)

• The Miscellaneous tab title has a typo (missing 'e')

So things are actually working perfectly but the re-connection notification is missing.

I backed up the rpi (which stops the NUT server for an hour) with Debug level log enabled in the WinNUT client. The whole time WinNUT client was closed to systray. Here's are the notifications:

Description of log:

• Line 2156 (2:45:37 PM the backup starts and we get a reconnection in progress notification)

• Line 4414 (3:47:25 PM the backup ends and there is no notification) This is bad!

• Line 8710 (4:08:13 PM I manually turn off logging and Not Connected, Connected notifications appear)

Here is the log. WinNUT-Client-2024-08-14.zip

The connection being reestablished is somehow not being reported even though it is happening.

Log excerpt:

8/14/2024 3:47:18 PM [14084, UPS_Device]: Attempting reconnection...
8/14/2024 3:47:18 PM [14084, UPS_Device]: Beginning connection: [], Name: [][AutoReconnect]
8/14/2024 3:47:18 PM [14084, Nut_Socket]: Attempting TCP socket connection to []:3493...
8/14/2024 3:47:23 PM [14084, UPS_Device]: Attempting reconnection...
8/14/2024 3:47:23 PM [14084, UPS_Device]: Beginning connection: [], Name: [][AutoReconnect]
8/14/2024 3:47:23 PM [14084, Nut_Socket]: Attempting TCP socket connection to rpi:3493...
8/14/2024 3:47:25 PM [14084, Nut_Socket]: Connection established and streams ready.
8/14/2024 3:47:25 PM [14084, Nut_Socket]: Gathering basic info about the NUT server...
8/14/2024 3:47:25 PM [14084, Nut_Socket]: Server version: []
8/14/2024 3:47:25 PM [14084, Nut_Socket]: Protocol version: []
8/14/2024 3:47:25 PM [14084, Nut_Socket]: Completed gathering basic info about NUT server.
8/14/2024 3:47:25 PM [14084, UPS_Device]: Retrieving basic UPS product information...
8/14/2024 3:47:25 PM [14084, UPS_Device]: Initializing other well-known UPS variables...
8/14/2024 3:47:25 PM [14084, UPS_Device]: output.current is not supported by server.
8/14/2024 3:47:25 PM [14084, UPS_Device]: output.voltage is not supported by server.
8/14/2024 3:47:25 PM [14084, UPS_Device]: output.realpower is not supported by server.
8/14/2024 3:47:25 PM [14084, UPS_Device]: Determining best method to calculate power usage...
8/14/2024 3:47:25 PM [14084, UPS_Device]: ups.realpower is not supported by server.
8/14/2024 3:47:25 PM [14084, UPS_Device]: Using RPNomLoadPct method.
8/14/2024 3:47:25 PM [14084, UPS_Device]: battery.capacity is not supported by server.
8/14/2024 3:47:25 PM [14084, UPS_Device]: Apply Fallback Value when retrieving battery.capacity
8/14/2024 3:47:25 PM [14084, UPS_Device]: output.frequency.nominal is not supported by server.
8/14/2024 3:47:25 PM [14084, UPS_Device]: Apply Fallback Value when retrieving output.frequency.nominal
8/14/2024 3:47:25 PM [14084, UPS_Device]: Completed retrieval of basic UPS product information.
8/14/2024 3:47:25 PM [14084, WinNUT]: []has indicated it's ready to start sending data.
8/14/2024 3:47:25 PM [14084, WinNUT]: Update Icon
8/14/2024 3:47:25 PM [14084, WinNUT]: NotifyIcon Text => 
WinNUT Client - 2.3
Connected
8/14/2024 3:47:25 PM [14084, WinNUT]: Connection to Nut Host Established
8/14/2024 3:47:25 PM [14084, String]: New Log to CB_Current Log : Connection to Nut Host [] Established
8/14/2024 3:47:25 PM [14084, UPS_Device]: Nut Host Reconnected
8/14/2024 3:47:30 PM [14084, UPS_Device]: Enter Retrieve_UPS_Datas

Connection code seems to be running OK, with WinNUT processing events. Unclear since there's no logging code if the toast trigger is running.