I released Pyecobee 2.0.0b1 after spending the past week modernizing the library. The offline suite is in good shape, with 92 tests running on Python 3.12 through 3.14, but I have not been able to test this version against the live ecobee API.
ecobee no longer accepts new developer registrations. I still have a developer account, but no working application key or tokens, so I need help from someone who already has API access.
If that is you, install the beta with:
python -m pip install pyecobee==2.0.0b1
Please read the 2.0 migration guide first. Credentials work differently in this release, and refresh tokens must be saved whenever ecobee replaces them.
There is also a read-only integration script in the tagged source:
git clone --branch v2.0.0b1 --depth 1 https://github.com/sherif-fanous/Pyecobee.git
cd Pyecobee
uv sync --locked
ECOBEE_APPLICATION_KEY=your_application_key uv run python tests/live_integration.py
The script reads the thermostat summary, thermostat details, yesterday's runtime report, and groups. It does not change thermostat settings. It stores credentials in ~/.config/pyecobee/live_integration.json.
One caution: the script may refresh credentials, which invalidates the previous refresh token. Do not give it a copy of credentials that another running installation still expects to use. Read the credential section of the migration guide before using existing tokens.
When reporting back, please include your Python version, thermostat model, which calls succeeded, and whether authorization or token renewal occurred. Redact application keys, access tokens, refresh tokens, PINs, thermostat identifiers, addresses, and any other personal data before posting logs.
Even a short report saying that all four read operations passed would help a lot.
I released Pyecobee 2.0.0b1 after spending the past week modernizing the library. The offline suite is in good shape, with 92 tests running on Python 3.12 through 3.14, but I have not been able to test this version against the live ecobee API.
ecobee no longer accepts new developer registrations. I still have a developer account, but no working application key or tokens, so I need help from someone who already has API access.
If that is you, install the beta with:
Please read the 2.0 migration guide first. Credentials work differently in this release, and refresh tokens must be saved whenever ecobee replaces them.
There is also a read-only integration script in the tagged source:
git clone --branch v2.0.0b1 --depth 1 https://github.com/sherif-fanous/Pyecobee.git cd Pyecobee uv sync --locked ECOBEE_APPLICATION_KEY=your_application_key uv run python tests/live_integration.pyThe script reads the thermostat summary, thermostat details, yesterday's runtime report, and groups. It does not change thermostat settings. It stores credentials in
~/.config/pyecobee/live_integration.json.One caution: the script may refresh credentials, which invalidates the previous refresh token. Do not give it a copy of credentials that another running installation still expects to use. Read the credential section of the migration guide before using existing tokens.
When reporting back, please include your Python version, thermostat model, which calls succeeded, and whether authorization or token renewal occurred. Redact application keys, access tokens, refresh tokens, PINs, thermostat identifiers, addresses, and any other personal data before posting logs.
Even a short report saying that all four read operations passed would help a lot.