Add power sensor for MyStrom

[OneCyrus]

Proposed change

Adds the power information from MyStrom switches as additional sensors. The power information was previously just an attribute and was removed in PR #68821

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)
• 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 Extract mystrom switch energy attributes into sensors #53319
• This PR is related to issue: Remove energy usage from the switch base class #68821
• 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
• The code has been formatted using Black (black --fast 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.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[homeassistant]

Hi @OneCyrus,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[probot-home-assistant]

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

[martinfrancois]

Any news on this one? I'm really missing support for mystrom power in home assistant...

[frenck]

@martinfrancois You can see any updates above your comment. There is no need to ask for such things. Let's keep comments on PR towards reviewing the contents of the PR itself. Thanks 👍

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

[OneCyrus]

waiting for PR #74719 with config flow

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

[OneCyrus]

still waiting for the upstream PR to move on.

[gjohansson-ST]

Setting as draft until this PR is ready

[ax42]

Am trying to replicate this functionality in NodeRed with little success -- looking forward to have it in the native plugin.

[gjohansson-ST]

Config flow PR is now merged.
Please rebase this PR.

[OneCyrus]

just moved the sensors to the new config flow device. I'm not sure what's the preferred way to link the sensor to the same device. Currently every sensor has it's own switch buttons but they are greyed out. Shouldn't sensors just be sensors without any buttons?

[OneCyrus]

let's move on with #97024. Looks like the proper approach.