Cleanups in HomeWizard Energy sensors

[frenck]

Proposed change

When a HomeWizard Energy device only measures a single phase (e.g., a plug or single-phase kWh meter), it will create a duplicate power sensor.

Normally the integration creates a sensor for each phase + a total. However, when there is just a single phase, the total & the phase sensors, will have the same value (and thus, duplicate data is shown and recorded).

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 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.

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.

[DCSBL]

This maybe needs to be flagged as breaking, as it removes the l1 sensor for sockets/single-phase meters. (Which may cause issues with automations and stuff)

[frenck]

This maybe needs to be flagged as breaking, as it removes the l1 sensor for sockets/single-phase meters. (Which may cause issues with automations and stuff)

You are right. Going to combine some more breaking changes into this PR in that case, to make a single breaking change PR.

[frenck]

The current state is not good for the HWE-SKT type devices, as they do expose a single phase, but don't expose a total. But, it is past night here now, will pick up in the morning.

[DCSBL]

Instead of hiding the duplicate entities, can’t we just disable them by default? This makes it non-breaking.

[DCSBL]

The current state is not good for the HWE-SKT type devices, as they do expose a single phase, but don't expose a total. But, it is past night here now, will pick up in the morning.

Let me fix that in the python library, as we plan to add total_power_*_kwh to the actual API.

I will update the library to always have that datapoint when total_power_*_t1_kwh is set.

[frenck]

Closing this one. There is not much in it, but it is intertwined.