Closed Petahh closed 3 years ago
Hi, you should also provide your LG TV model and ideally the WebOS version it is using (that i usually in the logs). WebOS version 2.0 and below have limited functionality so not everything might work.
Besides that, in order to see the full debug log you need to start your homebridge in debug mode (see README) or the deepDebugLog flag will have no effect.
Thanks, I have somehow missed that debug option in HB. Managed to re-trigger pairing request so got full blown log. I have at the end decided to use Homekit native integration from LGTV and I hidden TV Service from plugin, although i don't like it's slow response times. So far random shutdowns (turn offs) have stopped not sure what was causing them, could be also some quirk with CEC accessory..
This is what happens when I try to turn ON tv with plugin:
[4/26/2021, 11:15:40 AM] [homebridge-webos-tv] [LGTV] Wake on LAN callback - sent magic packet, trying to connect to tv... [4/26/2021, 11:15:40 AM] [homebridge-webos-tv] [LGTV] Trying to wake up TV! Mac: 64:95:6C:33:19:D8, BroadcastAdr: 255.255.255.255 [4/26/2021, 11:15:40 AM] [homebridge-webos-tv] [LGTV] Connecting to TV
Then just spam "Connecting to TV" my TV is home-kit enabled, maybe that is the problem, dunno.
Below is the full log from pairing, might be of some use as I'm having rather newer model of TV (attached as it's far too big)
You have a webOS 4.5 TV so turn On should actually work. Make sure that the mac address which you entered there is correct, this is essential. Also it might indicate that there is some kind of issue with your home network, maybe firewall, maybe multiple networks, maybe something is blocking the requests. You would need to investigate that.
I'm having the exact same issue, everything works except turning the TV on. Using a OLED65CXPUA WebOS v5
[5/2/2021, 2:11:48 AM] [webostv] [OLED] TV webOS version: 5.0
[5/2/2021, 2:11:49 AM] [webostv] [OLED] App launched, current appId: com.webos.app.hdmi2
[5/2/2021, 2:11:49 AM] [webostv] [OLED] TV turned on!
[5/2/2021, 2:11:49 AM] [webostv] [OLED] Sound output changed. Current sound output: external_arc
[5/2/2021, 2:11:58 AM] [webostv] [OLED] Subscribed to TV services
[5/2/2021, 2:11:58 AM] [webostv] [OLED] Connected to remote pointer input socket
[5/2/2021, 2:11:58 AM] [webostv] [OLED] Setup finished
[5/2/2021, 2:11:58 AM] [webostv] [OLED] TV setup finished, ready to control tv
[5/2/2021, 2:13:04 AM] [webostv] [OLED] TV turned off!
[5/2/2021, 2:13:14 AM] [webostv] [OLED] Disconnected from TV
[5/2/2021, 2:13:19 AM] [webostv] [OLED] Starting TV alive polling
In the log here you can see me rebooting homebridge with the TV already on, I use webos-tv
to turn it off and then when turning it back on from the Home app the tile lights up but there's nothing additional in the logs and the TV doesn't turn on.
I don't think it's network related, since off works fine, unless I'm mistaken? But there's nothing on my firewall that would be preventing this from communicating.
Let me know if there's additional information I can provide.
Ok forget all that, I just figured it out. I had to go into settings
All Settings -> Connection -> Mobile Connection Management -> TV On with Mobile
and enable Turn on via Wi-Fi
, that fixed it. For some reason Turn on via Bluetooth
was enabled. Disabling Bluetooth was fine and once Wi-Fi was enabled it turned on as normal. Could this also be your issue @Petahh? Not sure if that's what you meant by
Mobile TV in webos settings is turned ON.
I encountered the same issues on my 2 LG CX. It's intermittent, sometimes it gets 'stuck' and turn on doesn't work until I turn TV on manually first time and then it works. I have yet to identify how to really trigger it consistently and reproduce it. On both TVs turn on bt Wi-Fi and BT is correctly enabled and turn on works via ThinQ LG app. If I will be able to do I will also provide full debug logs to investigate and hopefully fix the issue.
All the issues related to the TV not turning on are mostly related to either network issues (where the wake up packet does not arrive at the TV) or with the TV itself (where simply the required options needs to be enabled).
Also if you unplug the TV from the power source even for a slight moment, then the TV will lose its network connection and first needs to be booted at least once in order to recover that. I also noticed that when i restart my router then the TV will also not react to the wake up packet anymore till i turn it on at least once manually so that the connection to the network is restored.
There are many small factors which affects this functionality and you need to make sure that all of them are met.
All the issues related to the TV not turning on are mostly related to either network issues (where the wake up packet does not arrive at the TV) or with the TV itself (where simply the required options needs to be enabled).
Also if you unplug the TV from the power source even for a slight moment, then the TV will lose its network connection and first needs to be booted at least once in order to recover that.
I also noticed that when i restart my router then the TV will also not react to the wake up packet anymore till i turn it on at least once manually so that the connection to the network is restored.
There are many small factors which affects this functionality and you need to make sure that all of them are met.
You are indeed probably right. I will check in depth once it happens again just in case. Thank you for now.
I'm also having these intermittent issues after some network changes in my house.
If the request to turn on/off the TV comes from a HomeKit automation, thus coming from a hub (like HomePod or tv), would that get sent to the Homebridge hardware to then send the WoL packet to wake-up the TV? Or would the WoL packet be sent from the hub itself?
That would explain the results I'm getting. My Homebridge hardware is on the same VLAN as the TV, but my HomeKit hubs aren't. All requests coming from my phone works. All requests coming from my iPhone work fine, but the ones coming from automations or other HomeKit requests, like switches and Siri commands don't.
The WOL request is always sent from the machine where homebridge is running on.
Not sure what was going on. But getting all devices on the same VLAN fixed it. Thanks!
Hello All, having really strange issue with ON/OFF
Firstly when I try to turn on TV through home-kit it literally does nothing, meaning no logs are being generated even with deep debug on. After 1 minute or so tile in home-kit returns back to OFF.
Secondly, if I choose to turn on TV manually with remote it of course works but only for few minutes, then TV is turned off by the plugin, without me issuing command through home-kit.
Besides this ON/OFF problem everything works, I can change inputs, modify volume, control media, I can even turn TV OFF. I'm at the end of the rope here, I have depleted all my ideas what could be wrong.
Here is my config:
Mobile TV in webos settings is turned ON.
Any help or ideas appreciated.
Oddly and luckily enough I found out this random turn OFF is not happening when my Nvidia Shield TV is turned ON. So to workaround it at the moment I'm having my Shield always on and using it also to turn on the TV.