Use dedicated power commands for LG infrared

[balloob]

Breaking change

Proposed change

It was using the power toggle command instead of dedicated power on/off commands.

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:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• 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.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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 diff between library versions and ideally a link to the changelog/release notes 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.

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (lg_infrared) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of lg_infrared can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant mark-draft Mark the pull request as draft.
• @home-assistant ready-for-review Remove the draft status from the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign lg_infrared Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant update-branch Update the pull request branch with the base branch.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

[Copilot]

Pull request overview

This PR updates the LG Infrared media player to use discrete power on/off IR commands instead of a power toggle, aligning service behavior with explicit on/off intent.

Changes:

• Switch async_turn_on to send LGTVCode.POWER_ON instead of LGTVCode.POWER.
• Switch async_turn_off to send LGTVCode.POWER_OFF instead of LGTVCode.POWER.

[balloob]

@copilot fix test

[Copilot]

@copilot fix test

Fixed in dc7117bd: updated tests/components/lg_infrared/test_media_player.py to expect LGTVCode.POWER_ON for turn_on and LGTVCode.POWER_OFF for turn_off.

[edenhaus]

Thanks @balloob 👍

[abmantis]

This now always sends turn_off, since the interface only shows 1 button, right?
The UI should show separate On/Off buttons when assumed_state = True.

Alternatively, we could toggle _attr_state in turn_on() and turn_off(), but that is a worse UX than just sending POWER all the times instead.

[balloob]

Yeah, we do this for light already. We should do this in the frontend too for media player turn on/off buttons.