Add production power sensor that is compatible with the energy power dashboard for supported homewizard devices

[jbouwh]

Proposed change

For Home Wizard Energy devices that have a power sensor, this sensor is behaving positive values if the device is consuming, and negative values if the device is generating. Except for the P1 adapter, other devices are mainly for monitoring internal power.
The Home Assistant energy dashboard allows to visualize power generation and usage.
Consuming devices should supply a positive power sensor if a device is added to that category.
Generating devices, like home batteries and solar panels should be considered as a power source. The power sensor value should be positive value for the generated power.

This PR allows adds a production power sensor for supported devices, The production power sensor for plugin batteries is added by default. For energy monitoring devices the production power sensor will be disabled by default or the total energy export is 0.

Users can use the production sensor on the energy dashboard for the power generating devices, such as batteries or solar panels.

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 HomeWizard plugin battery show negative power when discharing while enery panel expects a positive value instead #159121
• This PR is related to issue:
• Link to documentation pull request: Add production power sensor for supported homewizard devices home-assistant.io#42690
• 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 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.

[home-assistant]

Hey there @DCSBL, mind taking a look at this pull request as it has been labeled with an integration (homewizard) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of homewizard 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 homewizard 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.

[DCSBL]

Looks great, Thanks! 🎄

[frenck]

Thanks, @jbouwh 👍

../Frenck