Add return energy stats and separate consumption/return costs to Opower

[parkerbxyz]

Breaking change

Negative consumption from Opower {utility name} elec {account number} consumption is no longer shown in the electricity usage graph on the energy dashboard. Add the new Opower {utility name} elec {account number} return under Return to grid to see return energy statistics. To keep costs accurate, you should track costs using the new Opower {utility name} elec {account number} consumption cost and Opower {utility name} elec {account number} return cost entities.

Proposed change

Resolves tronikos/opower#74.

Since I'm set up with net metering, I will see my consumption go negative when my solar output exceeds usage.

If the negative values could be separated and entered into "Return to Grid" (as a positive value), the dashboard would accurately reflect how much energy is being consumed/generated over time.

Before:

Only a single sensor was available for all consumption and return to grid. Return to grid showed as negative consumption.

After:

There are now separate sensors for consumption and return to grid, each with a new corresponding cost tracking entity so you can see the cost/credit for each.

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 #113851 and addresses similar community discussions/requests:

• https://community.home-assistant.io/t/resolve-combine-multiple-energy-sources-in-energy-dashboard/625113/4

  Just a bump in here after realizing another difficulty with the status quo-
  Opower has one statistic that provides a net power consumption value over some time window.
  There’s no explicit sensor for power returned to grid, which is also a bit annoying, since I can’t see it separately with the more granular data from my solar system without trashing the energy panel’s information.

• https://www.reddit.com/r/homeassistant/comments/18dvj2o/tesla_powerwall_solar_owners_with_pto_calculating/

  I'm a new Tesla Powerwall owner with a solar inverter. Using the Tesla Powerwall Integration sensors, I can calculate how many kW's are sent back to the Grid daily.

  However, I have no way of calculating credit $ for KW sent back to the power company.

  In order to do that, I think I would need to convince the developer for OPower Integration to provide a new sensor that receives the current cost per kilowatt (based on the time of day and rate plan we subscribe to)... if available in the API.

  Or... maybe just convincing the OPower developer to add a new sensor that receives current PTO credit so far.. if available in the API.

  Can someone please confirm if the above 2 features for Opower would help me do what I want? Or, maybe I'm missing something?

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.

To help with the load of incoming pull requests:

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

[home-assistant]

Hi @parkerbxyz

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!

[home-assistant]

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

Code owner commands

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