Energy
Opower
opower
Built inCloud pollingPlatinum
The Opower integration allows you to get energy information from utilities that use Opower.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
sensor | Sensor (air quality) |
What people report
Cloud utility accounts (AEP, ComEd, PECO, Indiana Michigan Power, ConEdison) frequently break when utilities change login or enforce MFA; data lags several days.
- Works3
- Not working2
- Requested1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| AEP Ohio (Opower utility) | Works Cloud | 'async_login not called' error; closed as completedSaved copyThe problem 2024-02-07 17:05:09.602 ERROR (MainThread) [homeassistant.components.opower.coordinator] Unexpected error fetching Opower data: async_login not called Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/opower/coordinator.py", line 83, in _async_update_data forecasts: list[Forecast] = await self.api.async_get_forecast() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File … Excerpt saved from GitHub on 2026-10-23. | Issue #110019 · 2024-02 | |
| ComEd (Opower utility) | Works Cloud | Mandatory MFA broke it; MFA support requested then closed completedSaved copyThe problem ComEd has enabled mandatory MFA on accounts and Opower is no longer able to connect. Need MFA support for ComEd provider. ### What version of Home Assistant Core has the issue? core-2025.9.3 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Opower ### Link to integration documentation on our website https://www.home-assistant.io/integrations/opower ### Diagnostics information _No response_ ### Example YAML snippet [code] ### Anything in the logs that might … Excerpt saved from GitHub on 2026-10-23. | Issue #152243 · 2025-09 | |
| ConEdison (Opower utility) | Works Cloud | MFA auth support added as virtual integrationSaved copyProposed change This adds support for MFA authentication mechanisms in Opower which is being added in https://github.com/tronikos/opower/pull/13 and uses it to add explicit support for ConEdison as a virtual integration. ## Type of change <!-- What type of change does your P Excerpt saved from GitHub on 2026-10-23. | PR #97878 · 2023-08 | |
| Indiana Michigan Power (Opower utility) | Not working Cloud | Login spins or invalid login; awaiting upstream fixSaved copyAlso seeing an error when trying to add a ComEd account: Logger: homeassistant.components.opower.config_flow Source: components/opower/config_flow.py:50 integration: Opower (documentation, issues) First occurred: 6:49:36 PM (5 occurrences) Last logged: 7:18:24 PM Could not connect to Commonwealth Edison (ComEd) Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/opower/opower.py", line 199, in async_login self.access_token = await self.utility.async_login( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/opower/utilities/exelon.py", … Excerpt saved from GitHub on 2026-10-23. | Issue #130368 · 2024-11 | |
| PECO (Opower utility) | Not working Cloud | Stopped working February 2024; duplicate of another issueSaved copyThe problem I had OPower working with PECO for several months. Then in February, it stopped working. I tried removing and adding it back but it still would not work. The error I am getting is below. ### What version of Home Assistant Core has the issue? 2024.3.3 ### What was the last working version of Home Assistant Core? 2024.1.1 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue OPower ### Link to integration documentation on our website https://www.home-assistant.io/integrations/opower ### Diagnostics information Logger: … Excerpt saved from GitHub on 2026-10-23. | Issue #114140 · 2024-03 | |
| PG&E (Opower utility) | Requested | MFA support PR closed unmergedSaved copyBreaking change ## Proposed change <!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves Excerpt saved from GitHub on 2026-10-23. | PR #149030 · 2025-07 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Cloud polling
Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.
Details
| Installs (analytics) | 3,753 (0.53%) |
|---|---|
| Quality scale | Platinum |
| Added in | Home Assistant 2023.8 |
| Set up in the UI | Yes |
| Maintainers | @tronikos |
Limitations from the docs
- There is a delay, often for up to a few days, for sensors and statistics to have up-to-date data.
- For some utilities, there are no usage/cost sensors added by this integration, or they may constantly show a value of 0. This is expected and fine; you should use the statistics instead.
- For some utilities, the usage/cost sensors might disappear or become unavailable at the beginning of your bill period.
- Sensors for typical monthly usage and cost are not populated for accounts younger than a year.
- Many utilities provide granular usage (for example, daily or hourly) but not cost. They only provide cost for billing periods (for example, a month). This means daily and hourly cost statistics show 0. This has been reported with Consolidated Edison (ConEd) electricity and gas, Puget Sound Energy (PSE) gas, and AEP …
- For some utilities, the account number displayed in Home Assistant might not match the account number on your utility bill or web portal. This is expected behavior. The integration uses an internal identifier from the Opower system (preferredUtilityAccountId), which can differ from your public billing account number …
Brands that work through it
Home Assistant lists these brands as supported by Opower.
- AEP Ohio
- AEP Texas
- Appalachian Power
- Atlantic City Electric
- Baltimore Gas and Electric (BGE)
- Burbank Water and Power (BWP)
- City of Austin Utilities
- Commonwealth Edison (ComEd)
- Consolidated Edison (ConEd)
- Delmarva Power
- Duquesne Light
- Evergy
- Indiana Michigan Power
- Kentucky Power
- Orange and Rockland Utilities (ORU) Opower
- Pacific Gas & Electric (PG&E)
- PECO Energy Company (PECO)
- Potomac Electric Power Company (Pepco)
- Public Service Company of Oklahoma (PSO)
- Puget Sound Energy (PSE)
- Sacramento Municipal Utility District (SMUD)
- Seattle City Light (SCL)
- Southwestern Electric Power Company (SWEPCO)
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
