LG WebOS wake-on-lan

Configuration
19

Just wanted to reply to say thank you,

Watch 5 youtube videos and couldnt get my newer LG to work, the Switch method seemed to work when written into config.yaml

# TV
switch:
  - platform: wake_on_lan
    name: Bedroom_LG_TV_turnon
    host: 00.00.00.191
    "mac": "XX:XX:XX:XX:XX:XX"
    broadcast_address: 00.00.0.255

webostv:
    host: 00.00.00.191
    name: Bedroom LG TV
    turn_on_action:
      service: switch.turn_on
      entity_id: switch.Bedroom_LG_TV_turnon
    customize:
      sources:
        - AV
        - All 4
        - Amazon Prime Video
        - BBC iPlayer
        - Component
        - DuplexPlay
        - HDMI 1
        - HDMI 2
        - HDMI 3
        - ITV Hub
        - LG Content Store
        - Live TV
        - Music
        - My5
        - NOW
        - Netflix
        - Photo & Video
        - Rakuten TV
        - Sky Store
        - Web Browser
2 Likes
20

Glad it worked for you!

21

Guyz,
just out of curiosity. I know that its different thread but when i open netflix it is asking for profile to choose. So basicaly i cant control it from the home assistant. just change the sources. Do you have solution how to control it? Or must use their app?

22

You’ll need to write a script and execute it from a button on the dashboard

Can be done through GUI or scripts.yaml

rumpus_tv_enter:
  alias: Rumpus TV Enter
  sequence:
  - service: webostv.button
    data:
      entity_id: media_player.rumpus_room_tv
      button: ENTER
  mode: single

Known possible values are LEFT, RIGHT, DOWN, UP, HOME, MENU, BACK, ENTER, DASH, INFO, ASTERISK, CC, EXIT, MUTE, RED, GREEN, BLUE, VOLUMEUP, VOLUMEDOWN, CHANNELUP, CHANNELDOWN, PLAY, PAUSE, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9

2 Likes
23

I wasn’t able to get my TV to turn on. I didn’t add one line from the full example to my configuration.yaml file and even though it doesn’t sound like it has anything to do with WOL it is what made mine work in the end.

media_player:
24

FYI, this is what I did to get my LG WebOS TV working with wake-on-lan from inside docker, without using host network.

25

The LG WebOS config moved to the UI now.
The wake on lan action part has not moved?

turn_on_action:
service: wake_on_lan.send_magic_packet
data:
mac:

does not get moved over.
Any help?

26

Have a look here you need to make an automation for WOL turn on

27

For me the issue was a setting on the TV. I looked around on the tv setting and found All Settings → General → Devices → External Devices → TV On With Mobile → Turn on via WiFi, which was off. My TV is hard wired, so I’m not using WiFi. I still needed this feature enabled for wake_on_lan to work.

2 Likes
28

Stumbled onto this thread as I had issues waking my LG SM8500PLA (2020?) up through WOL via it’s ethernet connection. I tried using pfsense to send WOL packets just to ensure that it did not stumble in HA configuration. Turns out the TV would not turn on. I went into the TV settings, enabled wifi and there was a switch for enabling wol. Somehow the ethernet settings did not have a corresponding switch. Anyhow, after enabling wol for wifi, ethernet would start responding to wol packets. Maybe this will help a fellow LG owner that is not able wol through HA.

1 Like
29

Thank you!!

30

I’ve been getting these for several months now during startup:

Logger: homeassistant.helpers.config_validation
Source: helpers/config_validation.py:1065
First occurred: 09:33:50 (1 occurrences)
Last logged: 09:33:50

The wake_on_lan integration does not support any configuration parameters, got {'mac': 'xx:xx:xx:xx:xx:xx'}. Please remove the configuration parameters from your configuration.

(Real mac address removed)

In configuration.yaml I have repectively

wake_on_lan:
   mac: xx:xx:xx:xx:xx:xx:xx

The funny thing is that in the HA WOL documentation (Wake on LAN - Home Assistant) mac is the only parameter that is NOT optional…

However, I also use lg-remote-control custom card, where mac is also defined

type: custom:lg-remote-control
entity: media_player.office_tv
mac: xx:xx:xx:xx:xx:xx

Should the other one be removed or what?

31

wake_on_lan: Should only be in configuration.yaml

Then on your service calls / switches use the mac address as in the docs:

switch:
  - platform: wake_on_lan
    mac: MAC_ADDRESS

Scroll up a few posts and there’s a few examples of what to use

32

If you look closely, you’ll notice that this “optional no” refer to the wake_on_lan.send_magic_packet service…

33

@koying

…then again, a bit later:

image

34

That’s the config for the switch

35

Yes, “wake_on_lan” is only in configuration.yaml.
The only place I use it, is in lg-remote-control card, where I refer to the same mac as follows

type: custom:lg-remote-control
entity: media_player.office_tv
mac: xx:xx:xx:xx:xx:xx
colors:
  active-background-button-color: ‘#0080ff’
  deactive-background-button-color: ‘#f2f0fa’
  button-border-standard: ‘rgba(0, 128, 255, .5)’
  state-icon-active-color: ‘#0080ff’
  buttons: black
...
...
...
etc...

It works OK and has been doing so somewhat 2 years. The device (LG TV) gets up when virtual remote controller power button is clicked.

It is just the warninng I have been getting for few months

EDIT: I have been searching the error message every now and then, but I can not find any references fron net. Surely there are other users that have come across this?

36

You just need to remove the mac from configuration.yaml so only
wake_on_lan:
is there

37

OK, I try it later.

However, isn’t that a bit controversary to what was said earlier?

wake_on_lan: Should only be in configuration.yaml

Anyway, it does not much matter to me, since it is only my wife who in general even watches TV :grin:
However, I do not wish her to generate error messages either…

38

No I meant only wake_on_lan: should be in configuration.yaml