JPersson77 / LGTVCompanion

Power On and Off WebOS LG TVs together with your PC
MIT License
964 stars 40 forks source link

Can't enable multi-monitor topology #179

Closed shiftydev closed 10 months ago

shiftydev commented 10 months ago

Hello, I cannot enable support for multi-monitor topology as the program tells me no WebOS devices are detected. This is despite the device being setup and managed by LG TV Companion.

Running Windows 11 with LG C2 42 with Always Ready enabled. The screenshot was taken on the C2 running extended desktop, as instructed.

It may be related that I had to manually add the device with IP and MAC address since the scan function did not detect it.

Screenshot 2023-11-09 130233

JPersson77 commented 10 months ago

Hi @shiftydev can you confirm the TV is connected via HDMI as well? (I guess there will be some use cases where it is not - but this function is dependent on the device being physically connected )

The app is iterating through the details of enabled devices looking for a particular string ("LG TV"). Can you please check whether the device is available in device manager under "Monitors" and if so go into properties of the TV and please check what the value is in the details drop down box for the "Friendly name" item

shiftydev commented 10 months ago

The TV is indeed connected with HDMI to an Nvidia RTX 4080. The friendly name under Monitors in Device Manager is Generic Monitor (LG TV SSCR2).

JPersson77 commented 10 months ago

Can you click into properties of "Generic Monitor (LG TV SSCR2)" as well and go to the details tab and use the drop down box and see what the "Friendly name" is there please

shiftydev commented 10 months ago

That is what I did. Screenshot 2023-11-09 192625

JPersson77 commented 10 months ago

Thanks, can you join discord possibly and test a dev build? I'd need to add a little debug output to nderstand the issue

shiftydev commented 10 months ago

No problem. On there with same username. Let me know what you need me to do.

JPersson77 commented 10 months ago

After some troubleshooting the issue was likely caused by having renamed the device using CRU. Closing the issue, but feel free to reopen as necessary