pyOgero: Ogero API Python module
Ogero does not currently provide a rest api to access it services, therefore this module web scrap the mobile version of the pages to collect data.
Async client
The async client (pyogero.asyncio.Ogero) requires an injected aiohttp.ClientSession (for example from Home Assistant async_get_clientsession(hass)):
import aiohttp
from pyogero.asyncio import Ogero
async with aiohttp.ClientSession() as session:
client = Ogero("user", "pass", session=session)
await client.login()
Home Assistant compatibility
Runtime dependency versions are capped at the versions used by Home Assistant 2026.3.2 (requests, aiohttp, beautifulsoup4, pydantic). To install exact pins in a virtual environment:
pip install -e . -c constraints-home-assistant-2026.3.2.txt
Development
This project uses uv for dependencies and a PEP 621 pyproject.toml for package metadata. Python 3.14 is used for CI and local development (see .python-version).
uv sync --group dev
uv run pytest tests/ -m "not integration"
uv run ruff check .
uv run ruff format .
To match Home Assistant pins after syncing dev dependencies:
uv sync --group dev
uv pip install -c constraints-home-assistant-2026.3.2.txt -e .
Build release artifacts with uv run python -m build (requires dev dependencies).
Releasing
- Bump
versioninpyproject.tomland document changes inCHANGELOG.md. - Merge to
main. CI runs on push; the Release workflow then runs tests and creates tagvX.Y.Zif that tag does not exist yet. - Pushing the new tag triggers the publish job (GitHub release + PyPI). Re-pushing
mainwithout a version bump does not re-release because the tag already exists. - You can also run the Release workflow manually via
workflow_dispatchto re-run pre-release checks.
PyPI publishing
CI publishes with trusted publishing (OIDC) when the PyPI project is linked to this GitHub repository. The workflow also supports PYPI_TOKEN in repository secrets as a fallback if trusted publishing is not configured yet.
1 maintainer
Metadata
1 maintainer
Release files for pyogero 0.14.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pyogero-0.14.3.tar.gz | 16.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyogero-0.14.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.9 kB
Release files / pyogero-0.14.3.tar.gz
| Download URL | pyogero-0.14.3.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62d005e742bab3055cda07dd65c6d2ef5e06d2ff925e597a3122ff0f51eec6c3
|
|
BLAKE2b-256 checksum How to use checksums |
e370232f697a8311f5d65e98915cbc0b1ca407ddfe8e0371a1d53d70045d0fe4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / pyogero-0.14.3-py3-none-any.whl
| Download URL | pyogero-0.14.3-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1e0257c90093854c2346041f6facc18e6253bb290269add88c0f7ab4f699e2f7
|
|
BLAKE2b-256 checksum How to use checksums |
054f9e65c4c6b75502d3070864a0af8ca8c7aa0c7f4618d228e2af697d81e2b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
