Wrong target IP used if flashing a second device

[Toyzrme]

Expected Behavior

1. Flash RX 1 at 192.168.2.127 successfully
2. De-power Rx1
3. Power up Rx2
4. Rx2 appears in "Network Devices" (target device list), with IP=x.x.x.44
5. Click "Select" in "Network Devices"
6. "WiFi Devices" shows Rx2 at IP=x.44 is selected
7. Update options as desired
8. Click "FLASH"
9. Rx2 at x.44 is built/flashed successfully

Current Behavior

1-8 same
9. Configurator log shows it's trying to flash IP=x.127 (the PREVIOUS Rx), rather than x.44, and thus fails, despite IP=x.44 showing as selected

Steps to Reproduce

as above:

1. Flash one Rx
2. Keep Configurator running
3. Try to flash another Rx on a different IP by clicking "Select" in "Network Devices", then FLASH button

Possible Solution (Not obligatory)

Workarounds:

1. Restart Configurator each time - works fine for the first Rx flash

• OR -

2. Enter IP of Rx manually

Context

If people aren't watching the log, and paying attention to IP's, they could miss the simple workarounds

Your Environment

• Windows 10 Home, updated as of 1/7/24
• PC is on WiFi
• Rx's were (2x) Matek R24-D's, RadioMaster ER5A & ER5C

ATTACHMENTS:

1. Build log showing failure as it tries to flash IP=x.127
2. Image of the Configurator after the failure - note IP is x.44 in both in "Network Devices" & "WiFi Devices"

ADDITIONAL NOTE: Configurator didn't work on IPv6 - couldn't see the Rx. I had to disable it on the PC so it would fall back to IPv4 (not surprised, but might want to note and/or test for it to spare others)

[Toyzrme]

ExpressLRSBuildLog_20240108020229533 (Wrong IP - 44 selected, sends to 127)).txt

[Toyzrme]

Perhaps #515 was not completely fixed?