Closed Chris0706 closed 1 year ago
Hi @Chris0706, thanks too! Can you please enable logging in the global options and upload it to pastebin or similar so I can have a look? Please indicate the timestamps when it does not turn on automatically and refrain from turning it on manually for at least a minute. Cheers
` Tue 07:34:49 > LGTV Companion Service started (v 1.8.0) --------------------------- Tue 07:34:49 > Configuration file successfully read Tue 07:34:49 > Data path: C:\ProgramData\LGTV Companion\ Tue 07:34:49 > Device1, [LG] webOS TV OLED42C29LB, with IP 192.168.2.127 initiated (Enabled:yes, WOL:2, PairingKey:538eb18f973750ff3411d57bb7880a92, MAC: 64:CB:E9:3A:F7:2C , VerifyHdmiInput:off, SetHdmiInput:1, BlankOnIdle:off) Tue 07:34:49 > Host IP detected: 192.168.2.103 Tue 07:34:49 > Setting shutdown parameter level 0x3FF Tue 07:34:49 > ** System requests displays ON. Tue 07:34:49 > Device1, spawning DisplayPowerOnThread(). Tue 07:34:49 > Device1, spawning DisplaySetHdmiInputThread(). Tue 07:34:49 > Device1, repeating WOL broadcast started to MAC: 64:CB:E9:3A:F7:2C using IP address: 192.168.2.127 Tue 07:34:49 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:34:49 > Device1, WARNING! DisplayPowerOnThread(): connect: Eine bestehende Verbindung wurde softwaregesteuert
durch den Hostcomputer abgebrochen hen Tue 07:34:51 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:34:53 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:34:55 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:34:57 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:34:59 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:01 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:03 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:05 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:07 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:09 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:11 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:13 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:15 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:16 > Device1, WARNING! SetDisplayHdmiInputThread(): connect: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat Tue 07:35:16 > Device1, WARNING! DisplayPowerOnThread(): connect: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat Tue 07:35:17 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:19 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:21 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:23 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:24 > IPC, Daemon has started. Tue 07:35:25 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:27 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:29 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 07:35:31 > Device1, repeating WOL broadcast ended Tue 07:35:37 > Device1, WARNING! DisplayPowerOnThread(): connect: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat hat `
This is an occasion when it didn't turn on.
'Tue 05:10:23 > LGTV Companion Service started (v 1.8.0) --------------------------- Tue 05:10:23 > Configuration file successfully read Tue 05:10:23 > Data path: C:\ProgramData\LGTV Companion\ Tue 05:10:23 > Device1, [LG] webOS TV OLED42C29LB, with IP 192.168.2.127 initiated (Enabled:yes, WOL:2, PairingKey:538eb18f973750ff3411d57bb7880a92, MAC: 64:CB:E9:3A:F7:2C , VerifyHdmiInput:off, SetHdmiInput:1, BlankOnIdle:off) Tue 05:10:23 > Host IP detected: 192.168.2.103 Tue 05:10:23 > Setting shutdown parameter level 0x3FF Tue 05:10:23 > ** System requests displays ON. Tue 05:10:23 > Device1, spawning DisplaySetHdmiInputThread(). Tue 05:10:23 > Device1, repeating WOL broadcast started to MAC: 64:CB:E9:3A:F7:2C using IP address: 192.168.2.127 Tue 05:10:23 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:23 > Device1, WARNING! DisplayPowerOnThread(): connect: Eine bestehende Verbindung wurde softwaregesteuert
durch den Hostcomputer abgebrochen Tue 05:10:23 > Device1, WARNING! SetDisplayHdmiInputThread(): connect: Eine bestehende Verbindung wurde softwaregesteuert
durch den Hostcomputer abgebrochen Tue 05:10:25 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:27 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:29 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:31 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:33 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:35 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:37 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:39 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:41 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:43 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:45 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:47 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:49 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:51 > Device1, WARNING! SetDisplayHdmiInputThread(): connect: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat Tue 05:10:51 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:53 > IPC, Daemon has started. Tue 05:10:53 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:55 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:10:57 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:11:00 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:11:02 > GetBestRoute2() selected interface index 10 LUID 1689399699963904 route protocol 2 Tue 05:11:04 > Device1, repeating WOL broadcast ended Tue 05:11:12 > Device1, WARNING! SetDisplayHdmiInputThread(): connect: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat Tue 05:11:12 > Device1, WARNING! DisplayPowerOnThread(): connect: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat '
Do you think that using WiFi on the TV could give such problems?
Hi @Chris0706 indeed it looks liike the app cannot connect to the TV over the network - looks like the TV is not present on the network. I agree that the WiFi could be the issue as there is evidence to support that if the TV for some reason lose the connection to the WiFi it will not automatically reconnect until it is manually powered on. If you have the opportunity to try with a network cable that might solve this problem.
Seeing that you have a C2- first also try to enable "Always ready" and see if that potentially alleviates the issue and please report your findings :)
hi @Chris0706 any feedback on this issue?
I've been waiting to be sure. But it seems like 'Always ready' was not a fully sustainable solution. Now I've attached an Ethernet Cable and disabled 'Always ready' again and it has been working without any problems.
OK, thanks for feedback - appreciate it. Fingers crossed
Hi JPersson,
thanks for developing this and trying to make our lives easier :)
I've got the companion working pretty okay, but 1/3 of the starts it does not turn on the TV. Any way to troubleshoot it? This are the dependencies of the service.. do I need to add more manually maybe? Or change it to delayed automatic start?
Best regards Christian