LG WebOS TV slow to change state to "on"

Configuration
21

Mine takes 25 seconds to register as off and 10 seconds to register as on in HA. The turn on/off when triggered is immediate though. It’s connected via ethernet and Quick Start+ is enabled. I think the problem lies somewhere in the integration, probably polling related…

22

I just picked up a Samsung 43" for my bedroom to replace the Toshiba FireTV which was always going unavailable with Android Debug Bridge until I turned it on with the remote, so virtually useless for me as far as HA integration. Note: Alexa could always turn it on though at ANY time. The Samsung is working flawlessly with SamsungTVSmart (HACS) integration as far as quick on/off detection/control but it only has volume, source (this model only has HDMI or TV) and a couple other options like key send etc.

I’m now constatly considering replacing the LG 50" in the living room every time I wait 10-20 seconds for my automations to respond…

23

Does anyone know what might be the cause of my TV’s behaviour with the integration:

  1. When the state change is registered (either to ON of OFF), it is rather instant, however…
  2. It is rarely registered at all…there might be days it only registers ON events, but no OFF events whatsoever. Or vice versa. And there are occasions where it does not register either of them. At all.

This is really annoying since it prevents from using the TV state in automations.

24

Logs? Where are they?

25

WiFi or LAN connection?

WiFi connections can be disconnected b fore the state is updated in HA.

26

Make sure the TV is connected via LAN.

Try using a ping-sensor for the TV’s IP. Does it change the behaviour?

Is Quickstart+ turned on on the TV? If so, try turning it off. If not, try turning it on.
Don’t ask. It’s an LG, it does what it wants. You are not alone.

3 Likes
27

For me the issue is intermittent and appears to be more common if the TV has been off for several hours. Quikstart+, LAN ow wifi, none has any effect. My guess is that quick start+ can fix it from always to sometimes and the same for a more stable connection (obviously), so this is why those appear to be reliable fixes.

If you connect your TV to the thinQ app and watch it there, you will see the exact same behaviour, so the one thing we can be sure of sadly is that it is some sort of software problem on LG’s side. I am not aware of any official way of contacting them or requesting features (their approach appears to be ‘go fuck yourself’), I don’t think this will ever get fixed.

Sorry, bit of a rant, but after trying to fix this issue for the 10th time I’m so fed up with them.

1 Like