Time of Use (Peak/Mid-Peak/Off-Peak) cost breakdown in the Energy dashboard from the Opower API — SMUD, PG&E, and friends #4488
Unanswered
Borillion
asked this question in
Integration enhancements
Replies: 2 comments
|
🏷️ I've automatically added the |
0 replies
|
This is a great addition! We have PECO which has Opower and on their TOU plan, so this will be great enhancement. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Integration name
Opower
Link to integration documentation on our website
https://www.home-assistant.io/integrations/opower/
Describe the enhancement
Today the Opower integration imports total consumption and cost only, so on a time-of-use (TOU) or tiered rate the Energy dashboard can't show which portion of usage and money went to each rate period. On those plans that's the number that actually matters, and every utility shows it on its own billing site.
It turns out the Opower API already returns the per-period breakdown in the same cost responses the integration fetches today: a
readComponents[]array with per-TOU-period (dayPart) or per-tier (tierType/tierNumber) kWh and cost, at both daily and hourly resolution. The integration's library just doesn't parse it. No new API requests are needed.The enhancement: parse that field and have the integration create per-rate-period statistics (e.g. Peak / Mid-Peak / Off-Peak energy and cost) alongside the existing totals. Users could then add them as grid sources in the Energy dashboard for a full breakdown. No config changes required; the extra statistics would simply be available.
Here's a proof of concept with the parsed data feeding a real Energy dashboard (a real day from my SMUD meter; the Peak band appears only 5 to 8 PM, matching the rate schedule.
Use cases
tierType/tierNumber, so tiered-rate users get their breakdown too.Anything else?
Implementation is staged:
readComponents): submitted as Parse readComponents (TOU / tier cost breakdown) from cost reads tronikos/opower#208, investigation in Expose Time of Use / Tier cost breakdown ( readComponents ) already present in cost reads tronikos/opower#207. Purely additive; the new field defaults to empty, so nothing changes for existing consumers.All reactions