Open flowerdealer opened 2 years ago
There is already logic that keeps track whether the local "console" is connected or disconnected. If you connect remotely, the local console is disconnected and ColorControl will no longer automatically power on the TV.
But it could be that this is buggy and/or not working in all cases. I've only tested it briefly. One simple test is leaving the lock screen open and waiting for the screensaver to power off the TV and then opening a RDP connection to the PC from another device. The TV should not power on then.
In the log lines like these should be visible:
Detected a disconnect from the console
Detected a connect to the console
The problem is that this only works for Windows RDP. There are dozens of other remoting software, specially for gaming. I use Moonlight, Parsec, Steam Link and others like SuperDisplay, but I don't use RDP.
I often remote to the PC that is connected to my Oled, so I don't want the TV to turn on while I'm doing that. Also, some of the remoting software doesn't allow for the screensaver or power off functions to run, so the TV might just stay on after that happens, even if I'm not actively using the remoting software, leading to possible burn in. However, I do want the TV power off behaviors of those settings for when I'm using my pc with the TV directly (not remotely).