opower

A Python library and command-line tool for getting historical and forecasted usage/cost data from utilities that use opower.com.

This library is used by the Opower integration in Home Assistant.

Supported Utilities

AES Indiana
American Electric Power (AEP) subsidiaries
- AEP Ohio
- AEP Texas
- Appalachian Power
- Indiana Michigan Power
- Kentucky Power
- Public Service Company of Oklahoma (PSO)
- Southwestern Electric Power Company (SWEPCO)
Burbank Water and Power (BWP)
City of Austin Utilities
Clark Public Utilities
Consolidated Edison (ConEd) and subsidiaries
- Orange & Rockland Utilities (ORU)
Duquesne Light Company (DQE)
Evergy
Eversource
Exelon subsidiaries
- Atlantic City Electric
- Baltimore Gas and Electric (BGE)
- Commonwealth Edison (ComEd)
- Delmarva Power
- PECO Energy Company (PECO)
- Potomac Electric Power Company (Pepco)
Glendale Water and Power (GWP)
Northern Indiana Public Service Company (NIPSCO)
Pacific Gas & Electric (PG&E)
Puget Sound Energy (PSE)
Rhode Island Energy (RIEnergy)
Sacramento Municipal Utility District (SMUD)
Seattle City Light (SCL)
Southern Maryland Electric Cooperative (SMECO)
Southwest Gas

Contributing

Contributions are welcome! Please feel free to submit a pull request.

Adding a New Utility

To add support for a new Opower-based utility, follow these steps:

Verify it's an Opower utility: Use your browser's developer tools on your utility's website. If the network tab shows requests to a domain like utility.opower.com, it's a good candidate.
Create a utility file: Add a new file in src/opower/utilities that inherits from UtilityBase. Name the file after the utility's website (e.g., newutility.py for newutility.com).
Respect scraping limitations: This library is used by Home Assistant and must adhere to its architecture rules. A headless browser cannot be a dependency, and HTML parsing is only allowed for the authentication phase.

An exception is made for the authentication phase. An integration is allowed to extract fields from forms. To make it more robust, data should not be gathered by scraping individual fields but instead scrape all fields at once.

Development environment

python3 -m venv .venv
source .venv/bin/activate
# for Windows CMD:
# .venv\Scripts\activate.bat
# for Windows PowerShell:
# .venv\Scripts\Activate.ps1

# Install dependencies
python -m pip install --upgrade pip
python -m pip install -e .

# Run pre-commit
python -m pip install pre-commit
pre-commit install
pre-commit run --all-files

# Run tests
python -m pip install -e ".[test]"
pytest

# Run command line
python -m opower --help
# To output debug logs and API responses to a file run:
python -m opower -vv 2> out.txt

Instead of passing credentials on the command line or typing them at the prompts, you can put them in the environment or in a .env file in the current directory:

OPOWER_UTILITY=pge
OPOWER_USERNAME=user@example.com
OPOWER_PASSWORD=secret
# Only for utilities with TOTP-based MFA
OPOWER_TOTP_SECRET=...
# Only for utilities with interactive MFA, e.g. PG&E
OPOWER_LOGIN_DATA_FILE=login_data.txt

Real environment variables take precedence over the .env file, and command line arguments take precedence over both.

# Build package
python -m pip install build
python -m build

Metadata

Release files for opower 0.21.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for opower 0.21.0
File	Size	Uploaded
opower-0.21.0.tar.gz	83.4 kB	Sep 4, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for opower 0.21.0
File	Interpreter	ABI	Platform	Reset
opower-0.21.0-py3-none-any.whl 83.1 kB Sep 4, 2026	Python 3	none	any	Details

Total release size: 166.5 kB

Release files / opower-0.21.0.tar.gz

Download URL	opower-0.21.0.tar.gz
Size	83.4 kB
Tags	Source
SHA-256 checksum How to use checksums	`1e674a4217298b7c25af9faa993288ed0605334409c884db6b7fcd5378ea4df2`
BLAKE2b-256 checksum How to use checksums	`b043c2c3c807588dd6b9258c0c70435cd7dc3448b26a2b4609b33393c2c2e990`
Upload date	Sep 4, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/tronikos/opower
Publishing commit: github.com/tronikos/opower/tree/8f0e7acdb4c3fa41fdf67e94acea8138db8e6595

Workflow

Publishing configuration: github.com/tronikos/opower/blob/8f0e7acdb4c3fa41fdf67e94acea8138db8e6595/.github/workflows/python-publish.yml
Publishing logs: github.com/tronikos/opower/actions/runs/33849884416/attempts/1

Artifact

Subject: opower-0.21.0.tar.gz
SHA-256 checksum: 1e674a4217298b7c25af9faa993288ed0605334409c884db6b7fcd5378ea4df2 Verifying attestations

Release files / opower-0.21.0-py3-none-any.whl

Download URL	opower-0.21.0-py3-none-any.whl
Size	83.1 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`17e62ac030cef0445ef7074f105123eb8bb28cd46eaf8960a06c4c431040dca2`
BLAKE2b-256 checksum How to use checksums	`c319841363b53b36454793aea9d3defa8f0842c78c6eea97e6917e56403083b5`
Upload date	Sep 4, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/tronikos/opower
Publishing commit: github.com/tronikos/opower/tree/8f0e7acdb4c3fa41fdf67e94acea8138db8e6595

Workflow

Publishing configuration: github.com/tronikos/opower/blob/8f0e7acdb4c3fa41fdf67e94acea8138db8e6595/.github/workflows/python-publish.yml
Publishing logs: github.com/tronikos/opower/actions/runs/33849884416/attempts/1

Artifact

Subject: opower-0.21.0-py3-none-any.whl
SHA-256 checksum: 17e62ac030cef0445ef7074f105123eb8bb28cd46eaf8960a06c4c431040dca2 Verifying attestations