Not connecting after extended power off

[Nezzy808]

If tv has been manually powered on recently I can control though CC and power on/off commands work as intended: TV automatically powers on/off with PC power down and reset. If PC / TV have been powered down for a couple of hours TV will not power up with PC and only respond to CC commands after being turned on by other methods, (remote, thinQ app, home kit.) TV not showing up up in auto detect but works with manual input of MAC address and IP address. IP address of TV is static. PC and TV on wifi. 2021 48" LG C1. image of log below.

[Maassoft]

Thanks for the report. I'm having this issue myself as well, especially when the PC resumes from standby. I'm seeing the same as in your log: WOL succeeded, but the app is unable to connect with the TV. Sometimes it does work however. At this moment I don't know what the culprit is. Logically I would point to the app, but even sending a manual WOL from the app won't turn it on. You're saying it works from home kit (also WOL?) so I'll have to investigate further.

[MrKiko136]

Unfortunately I'm having the same behavior. WOL just works inconsistently. Sometimes reopening CC allows me to turn the TV on, but it doesn't always happen. From the log it gives "WOL succeded" in any case aswell.

I have a rooted LG C1 3.21.20 fw and I'm using Windows 10

When I can't turn it on from CC, I can do it from the official app. I wish I could be more helpful in solving this problem. Being able to use WOL from PC is really good

[thoriphes]

First of all, apologies since english is not my mother tongue =P

Might not be related (no idea, TBH) but I think I'll share my case, since I believe it might shed some light on this matter.

Everything was working flawlessly, up until I Installed Hyper-V. Then suddenly WOL stopped working.

As can be seen in the logs, apparently the broadcast was being sent through the Hyper-V virtual ethernet interface:

2022-07-01 15:38:53.4453|DEBUG|ColorControl.Common.WOL|Sending WOL packet to MAC-address 64-CB-E9-8D-6B-20
2022-07-01 15:38:53.4766|DEBUG|ColorControl.Common.WOL|Found network: Ethernet (Intel(R) I211 Gigabit Network Connection), type: Ethernet
2022-07-01 15:38:53.4766|DEBUG|ColorControl.Common.WOL|Found network: Local Area Connection* 16 (Microsoft Wi-Fi Direct Virtual Adapter #8), type: Wireless80211
2022-07-01 15:38:53.4766|DEBUG|ColorControl.Common.WOL|Found network: Wi-Fi 2 (TP-Link Wireless USB Adapter), type: Wireless80211
2022-07-01 15:38:53.4766|DEBUG|ColorControl.Common.WOL|Found network: Bluetooth Network Connection 2 (Bluetooth Device (Personal Area Network) #2), type: Ethernet
2022-07-01 15:38:53.4766|DEBUG|ColorControl.Common.WOL|Found network: vEthernet (Default Switch) (Hyper-V Virtual Ethernet Adapter), type: Ethernet
2022-07-01 15:38:53.4766|DEBUG|ColorControl.Common.WOL|Broadcast WOL in network: vEthernet (Default Switch) (Hyper-V Virtual Ethernet Adapter), local address: 172.22.144.1
2022-07-01 15:38:53.4766|DEBUG|ColorControl.Services.LG.LgDevice|WOL succeeded

After uninstalling the Hyper-V Windows feature, the broadcast went back to being sent through the Wi-Fi interface, and everything started working again.

2022-07-01 15:45:06.6138|DEBUG|ColorControl.Common.WOL|Sending WOL packet to MAC-address 64-CB-E9-8D-6B-20
2022-07-01 15:45:06.6292|DEBUG|ColorControl.Common.WOL|Found network: Ethernet (Intel(R) I211 Gigabit Network Connection), type: Ethernet
2022-07-01 15:45:06.6458|DEBUG|ColorControl.Common.WOL|Found network: Local Area Connection* 16 (Microsoft Wi-Fi Direct Virtual Adapter #8), type: Wireless80211
2022-07-01 15:45:06.6458|DEBUG|ColorControl.Common.WOL|Found network: Wi-Fi 2 (TP-Link Wireless USB Adapter), type: Wireless80211
2022-07-01 15:45:06.6458|DEBUG|ColorControl.Common.WOL|Broadcast WOL in network: Wi-Fi 2 (TP-Link Wireless USB Adapter), local address: 192.168.0.28
2022-07-01 15:45:06.6458|DEBUG|ColorControl.Common.WOL|Found network: Bluetooth Network Connection 2 (Bluetooth Device (Personal Area Network) #2), type: Ethernet
2022-07-01 15:45:06.6458|DEBUG|ColorControl.Services.LG.LgDevice|WOL succeeded

So might be related in some cases to the interface PowerColor chooses to send the broadcast through?