webOS Turn On button disappeared

[milkywayfarer]

The problem

After the latest Core update, LG webOS integration lost its Turn On media player button, and calling the service directly also doesn't work.

What version of Home Assistant Core has the issue?

2022.2.0

What was the last working version of Home Assistant Core?

2021.12.10

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

LG webOS Smart TV

Link to integration documentation on our website

https://www.home-assistant.io/integrations/webostv

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Configuration done from Home Assistant UI.

[probot-home-assistant]

Hey there @bendavid, @thecode, mind taking a look at this issue as it has been labeled with an integration (webostv) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

---

webostv documentation
webostv source
_{^{(message by IssueLinks)}}

[thecode]

Updated documentation: https://www.home-assistant.io/integrations/webostv/

This is from the breaking changes section:

LG webOS Smart TV

The Turn on action for turning on the TV via WakeOnLan or HDMI-CEC was using a service call via YAML, and the turn on action is changed to use a custom automation trigger webostv.turn_on or a device trigger automation that can be setup from the UI.

There are two options to define it back:

From the UI:

Goto Configuration --> Devices & Services
Click on the device:

Click the + under automations:

Click on Device is requested to turn on

Under Actions -> action type select Call service

Add the same service as you used before

Using YAML trigger automation:

automation:
  trigger:
    - platform: webostv.turn_on
      entity_id: media_player.lg_webos_smart_tv
  action:
    - service: wake_on_lan.send_magic_packet
      data:
        mac: AA-BB-CC-DD-EE-FF

[Will-L-Brown]

@thecode Something worth noting is most webOS devices won't turn on via the WoL service if broadcast_address is defined, even correctly. This is reflected in your note here, but is shown in the documentation and should be removed then explicitly called out. Otherwise someone else may spend a couple hours trying to figure out what broke wakeup besides the breaking change.

[blacknell]

Under Actions -> action type select Call service

There is strange behaviour here. Not sure it's in the integration rather than the UI but

1. when I leave broadcast address blank, the Save button is enabled but doesn't do anything. An attempt go back arrow brings are the leave/stay warning. After a couple of attempts, somehow I had 4 new automations created - probably the number of save clicks. Save only closes the form if I entered a broadcast address
2. the broadcast address (if mandatory judging from 1) behaviour is a check box option so I'm guessing it is not
3. going into the automation to delete it wasn't working either

[thecode]

@thecode Thanks for the explanation, it works for me but there is a weird problem, after a while the power button does not appear while TV is off, if I reload the automations the power button comes back again while the TV is off.

Anyone else have this issue?

I also get following error in my logs, maybe it has to do with this? 2022-02-05 08:11:43 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry Woonkamer TV LG for media_player Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 466, in async_unload result = await component.async_unload_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/media_player/__init__.py", line 383, in async_unload_entry return await component.async_unload_entry(entry) File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 172, in async_unload_entry raise ValueError("Config entry was never loaded!") ValueError: Config entry was never loaded!

Please create a new issue