Update LG webOS TV IQS

[thecode]

Proposed change

Docs update PRs:

• Align LG webOS TV docs with quality scale requirements home-assistant.io#36888
• Add removal instructions to LG webOS TV home-assistant.io#36836

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[joostlek]

Isn't it unavailable when someone doesnt have device triggers set up?

[thecode]

No, when triggers are not set the feature to power on the device is removed, but you can still power the device externally to the media player or to HA (for example the remote).

core/homeassistant/components/webostv/media_player.py

Lines 341 to 342 in 4dbf2b0

	if self._turn_on:
	return self._supported_features | MediaPlayerEntityFeature.TURN_ON

[joostlek]

you can still power the device externally to the media player or to HA (for example the remote).

How does that work?

[thecode]

The integration try to connect to the TV every 10 seconds:

core/homeassistant/components/webostv/media_player.py

Lines 330 to 332 in 4dbf2b0

	with suppress(*WEBOSTV_EXCEPTIONS):
	try:
	await self._client.connect()

So if the user power on the TV using the original remote (or any other type of power control that is not linked directly to the trigger, such as an IR blaster) and the device state (Idle, Playing, Paused) will be updated.

I had one of my TVs for few months without setting a trigger to power on since it is used by one of my kids and we do not power on the TV remotely, but we do monitor the daily usage or power off the TV remotely.

[joostlek]

But during the time it is off (and does not respond to anything) we can set it to unavailable right? Because we also cant do anything with it if the trigger is not used.

I believe samsung tv has this pattern as well

[thecode]

Why would you want your TV to show as unavailable when it is off? This is a bad user experience, I would rather keep the integration scale without any rating than showing a device that is off as unavailable.

Yes, Samsung TV mark the TV as unavailable when there is no trigger to turn on set, but I think this is an incorrect implementation by Samsung TV and should be fixed. HA already represent that correctly, if you remove the trigger the power/on off button will be removed from the UI so the user understand that he can't turn it on using HA, if we mark it unavailable it will be very confusing to users as they will not understand why the device is unavailable.

If you didn't set a trigger to turn on the device will show that HA doesn't have the capability to turn on the device, but it will still work if you turned it on.

[joostlek]

I think my reaction more comes from the fact that almost every other device in HA turns unavailable when we can't connect to it, even if that means the device is off. I get that a TV can be seen as a different kind of device. I think I am more looking for the "what is expected". And maybe I think samsungs implementation is slightly more correct, I am still 50/50 on what is right.

But I do think we should make it consistent in a way (maybe not across devices, but then across TV integrations).

cc @epenet

[epenet]

Sorry guys - I don't have a hard-set opinion on this.
It just feels like an arch discussion/decision to me.

Samsung has sooo many models with different firmware (and connectivity, etc.) that it's hard to work out the best behavior.
Some recent devices communicate on the network when they are off, therefore indicating that they are not unavailable - just off - so that makes it easier but for the others I don't know.