Add invert option to switch_as_x

[emontnemery]

Proposed change

Add invert option to switch_as_x cover, lock and valve entities.
When the invert option is enabled, the state of the entity is reversed, as an example an inverted switch_as_x valve will be open when the switch is turned off.

Needs frontend change

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 Core 2024.1.0 - Valve Domain - Open / Closed are Inverted #107011
• This PR is related to issue:
• Link to documentation pull request:
• Link to frontend PR: Allow inverting switch_as_x cover, lock, valve frontend#19324

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.
• Untested files have been added to .coveragerc.

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 (switch_as_x) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of switch_as_x can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign switch_as_x Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[gjohansson-ST]

This means that if someone has upgraded and configured a switch_as_x with invert=True and then downgrades it will change the option for that entry to invert=False hence changing how that entity works (even if the user then upgrade again).

It should probably only set this option if it's not already there?

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[MartinHjelmare]

Thanks!

[MartinHjelmare]

An approved frontend PR should be linked and the PR description checklist should be filled out. After that we can merge.

[MartinHjelmare]

I found the frontend PR and linked it in the PR description. It's approved but not merged.

[MartinHjelmare]

Please fill out the PR description and merge.