Adding 2nd Ethernet Adapter Causes Intermittent LGTVCompanion Command Failures

[githwithit]

Initial configuration:
LG C2 tv connected to LAN with a WAN port to Internet
LGTVCompanion 3.1.5 on computer1 = Windows 10 with adapter1 = 1gb connected to LAN with a WAN port to Internet
LGTVCompanion power management and manual lgtvcli commands work perfectly.

Addition to computer1: adapter2 = 2.5gb connected with a crossover cable to computer2
Now, LGTVCompanion running on computer1 initially sees the lower routing metric of the new 2.5gb adapter and tries to contact the LG C2 but can not since adapter2 is on a crossover cable to computer2 and can not route to the tv.
After a failure, LGTVCompanion seems to try adapter1 which has a higher metric and then the service commands and lgtvcli commands work.

Is it possible to add an option in LGTVCompanion to only use a specific adapter?
E.g. a drop-down set to Auto but with specific options for each adapter installed in the system.
In this way I could select adapter1 and LGTVCompanion would always work perfectly.

Here's a slightly cleaned log of app failing then succeeding:

Sat 10:37:33 > LGTV Companion Service started (v 3.1.5) ---------------------------
Sat 10:37:33 > Data path: C:\ProgramData\LGTV Companion
Sat 10:37:33 > Device1, LGTV, with IP 192.168.1.177 initiated (Enabled:yes, NewConn:yes, WOL:2, SubnetMask:255.255.255.0, PairingKey:0123456789, MAC: xxx , VerifyHdmiInput:off, SetHdmiInput:off, BlankOnIdle:off)
Sat 10:37:33 > Host IPs detected: 192.168.1.122, 192.168.1.22
Sat 10:37:33 > Shutdown timing: default
Sat 10:37:33 > ** System requests displays ON.
Sat 10:37:33 > Device1, spawning Thread_DisplayOn().
Sat 10:37:33 > Device1, repeating WOL broadcast started to MAC: xxx using IP address: 192.168.1.177
Sat 10:37:33 > Device1, Best route to IP - interface index 14 LUID x36 route protocol 2
Sat 10:37:33 > -daemon 1 started
Sat 10:37:33 > [IPC Daemon 1] Started.
Sat 10:37:54 > Device1, WARNING! Thread_DisplayOn(): connect: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond [system:10060 at D:\a\LGTVCompanion\LGTVCompanion\vcpkg_installed\x64-windows-static\x64-windows-static\include\boost\asio\detail\win_iocp_socket_service.hpp:632:5 in function 'connect']
Sat 10:38:14 > Device1, repeating WOL broadcast ended
Sat 10:38:15 > Device1, WARNING! Thread_DisplayOn(): connect: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond [system:10060 at D:\a\LGTVCompanion\LGTVCompanion\vcpkg_installed\x64-windows-static\x64-windows-static\include\boost\asio\detail\win_iocp_socket_service.hpp:632:5 in function 'connect']
Sat 10:42:48 > ** System requests displays OFF.
Sat 10:42:48 > Device1, spawning Thread_DisplayOff().
Sat 10:42:48 > Device1, [DEBUG] (SSL) OFF response 1: {"type":"registered","id":"register_0","payload":{"client-key":"0123456789"}}
Sat 10:42:48 > Device1, [DEBUG] (SSL) OFF response 2: {"type":"response","id":1,"payload":{"state":"Active","returnValue":true}}
Sat 10:42:48 > Device1, [DEBUG] (SSL) OFF response 4: {"type":"response","id":2,"payload":{"returnValue":true}}
Sat 10:42:48 > Device1, power state is: OFF.
Sat 10:55:51 > ** System requests displays ON.
Sat 10:55:51 > Device1, spawning Thread_DisplayOn().
Sat 10:55:51 > Device1, repeating WOL broadcast started to MAC: xxx using IP address: 192.168.1.177
Sat 10:55:51 > Device1, Best route to IP - interface index 21 LUID x52 route protocol 2
Sat 10:56:12 > Device1, [DEBUG] (SSL) ON response 1: {"type":"registered","id":"register_0","payload":{"client-key":"0123456789"}}
Sat 10:56:12 > Device1, [DEBUG] (SSL) ON response 2: {"type":"error","id":3,"error":"500 Application error","payload":{"returnValue":false,"state":"Active","errorCode":"-102","errorText":"The current sub state must be 'screen off'"}}
Sat 10:56:12 > Device1, [DEBUG] (SSL) ON response 3: {"type":"response","id":4,"payload":{"state":"Screen Off","returnValue":true}}
Sat 10:56:12 > Device1, [DEBUG] (SSL) ON response 1: {"type":"registered","id":"register_0","payload":{"client-key":"0123456789"}}
Sat 10:56:12 > Device1, [DEBUG] (SSL) ON response 2: {"type":"response","id":5,"payload":{"returnValue":true,"state":"Active"}}
Sat 10:56:12 > Device1, [DEBUG] (SSL) ON response 3: {"type":"response","id":6,"payload":{"state":"Active","returnValue":true}}
Sat 10:56:12 > Device1, power state is: ON
Sat 10:56:13 > Device1, repeating WOL broadcast ended

[JPersson77]

Hi @githwithit sorry for slow reply, vacation times. I'll note it down as a feature request