[BUG] Default input not changing

[Nokloklo]

Describe the bug

Hi, I've physically changed my display input from HDMI 4 to HDMI 2 and changed the setting in LGTVCompanion to power on my monitor on HDMI 2 at startup but it keep powering my TV on HDMI 4. I've uninstalled and installed many times but nothing is working.
Is there somes residual files that can cause this behaviour ?

Thanks

What was the expected behavior

When starting my computer, the monitor should wake up and change input device to HDMI 2.

What is your system?

Win 11, build 22631.4460, LG OLED C2

Log file and screenshots

log.txt

[JPersson77]

Hi @Nokloklo

There is nothing in the log to indicate that the app sets the TV to input 4 so I assume that input 4 was selected manually or by some other device.

From the log it looks like the correct command to switch to input 2 is sent as soon as the TV reports that it is powered on. All looks good. So either your TV does not like to receive the HDMI-switch command so soon after being powered on (which can be helped by a user configurable delay) or there is another device overriding via CEC (in which case a user configurable delay could help as well).

I will look into a user configurable delay for sending the hdmi switch command after powering on for the next release version of LGTVC

[fards]

I've got the same issue - except changing anything in lgtv bounces the connection back to the last used input.

I can't see anything in the logs. I ended up completely uninstalling the daemon and starting again.
I'm wondering if this is to do with latest Dev win insider build - 26120.1930

I did update the firmware on my c2 and there's now sddp and ip network control options, including generate a key.

[JPersson77]

hi @fards if it is not in the logs it seems unlikely to be due to LGTVC unless there is a second process running (which would be a bug). But please paste a link to a log paste at pastebin or similar and i will have a look

[JPersson77]

hi @fards any input wr t the above?

[fards]

Sorry been busy with a series of life disasters.
Will try to grab some logs, but it appears renaming the config file has fixed it my end.
Looks like a write permissions error, I did wonder if that was the issue as charges made were being ignored.
There was only the main config file. Once that was renamed/deleted, two new files created and all working fine including changed being saved. Hope that helps?
On insider dev build.

[JPersson77]

Hmm, I've heard of at least one other user with a similar problem. It is not a widespread issue by any measure but I will review the code for saving/loading the config file. Thanks for the feedback

[JPersson77]

hi @Nokloklo @fards see if the latest version v4.1.0 resolves some or all of the issues.

[Nokloklo]

Hi @JPersson77, no more issues since the last update ! Thank you so much :)