core icon indicating copy to clipboard operation
core copied to clipboard

Add Grid import export to Enphase Envoy

Open catsmanac opened this issue 1 year ago • 1 comments

Proposed change

Implement net consumption (grid import) and net production (grid export) for Enphase envoy metered with installed and configured CT.

Added sensor entities:

  • Envoy current net power consumption (positive/negative grid power exchange)
  • Envoy lifetime net energy consumption (grid energy import)
  • Envoy lifetime net energy production (grid energy export)

In the energy dashboard one can use Envoy lifetime net energy consumption for Grid consumption and Envoy lifetime net energy production for Return to grid.

These entities are also available for phases if more then 1 phase is configured in the Envoy.

Also added as disabled by integration, user can enable as needed:

  • Envoy Frequency net consumption ct (grid frequency)
  • Envoy Voltage net consumption ct (grid voltage)
  • Envoy Metering status net consumption CT
  • Envoy Meter status flags active net consumption ct
  • Envoy Metering status production CT
  • Envoy Meter status flags active production CT

Type of change

  • [ ] Dependency upgrade
  • [ ] Bugfix (non-breaking change which fixes an issue)
  • [ ] New integration (thank you!)
  • [x] 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 #82879 , #31426
  • This PR is related to issue:
  • Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/31491

Checklist

  • [x] The code change is tested and works locally.
  • [x] Local tests pass. Your PR cannot be merged unless tests pass
  • [x] There is no commented out code in this PR.
  • [x] I have followed the development checklist
  • [x] I have followed the perfect PR recommendations
  • [x] The code has been formatted using Ruff (ruff format homeassistant tests)
  • [x] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

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:

catsmanac avatar Feb 18 '24 18:02 catsmanac

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

Code owner commands

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

home-assistant[bot] avatar Feb 18 '24 18:02 home-assistant[bot]