pyyorkshirewater 0.4.0__tar.gz

pyyorkshirewater-0.4.0/.gitignore

@@ -0,0 +1,44 @@
+# Byte-compiled / optimised
+__pycache__/
+*.py[cod]
+*$py.class
+
+# Distribution / packaging
+build/
+dist/
+*.egg-info/
+.eggs/
+wheels/
+pip-wheel-metadata/
+
+# Virtual environments
+.venv/
+venv/
+env/
+
+# Editors
+.idea/
+.vscode/
+.DS_Store
+
+# Testing and coverage
+.pytest_cache/
+.coverage
+.coverage.*
+htmlcov/
+coverage.xml
+.tox/
+.nox/
+
+# Type checkers
+.mypy_cache/
+.pyright/
+.pyre/
+
+# Ruff
+.ruff_cache/
+
+# Local secrets used during integration testing
+.env
+.env.local
+secrets.toml

pyyorkshirewater-0.4.0/CHANGELOG.md

@@ -0,0 +1,146 @@
+# Changelog
+
+All notable changes to `pyyorkshirewater` are recorded here. The project follows
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html) and the
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/) format.
+
+## [Unreleased]
+
+## [0.4.1] - 2026-05-09
+
+First PyPI release. Identical code to v0.4.0; this version exists
+only because the v0.4.0 tag predated the GitHub Actions publish
+workflow trigger that fires on tag push. The workflow now publishes
+this and every subsequent tag automatically via PyPI Trusted
+Publisher OIDC.
+
+## [0.4.0] - 2026-05-06
+
+Data-model expansion (multi-property), no behaviour change to single-
+property accounts. See `git log v0.3.3..v0.4.0` for the diff. Not
+published to PyPI.
+
+## [0.3.0] - 2026-05-06
+
+Data model rewrite based on SPA bundle analysis.
+
+### Changed
+
+- **Breaking**: `DailyConsumptionPoint`, `UsagePeriod` and
+  `YearlyConsumptionPoint` rewritten with the field names the Yorkshire
+  Water SPA actually uses, per static analysis of the customer portal
+  bundle. The single `consumption` field is replaced with the typed pair
+  `total_consumption_litres` (litres) and `total_consumption_m3` (cubic
+  metres).
+- New per-day fields: `total_cost`, `total_cost_including_sewerage`,
+  `clean_water_cost`, `is_estimated`, `continuous_flow_alarm`. The SPA
+  exposes three spellings of the sewerage field; all three are accepted.
+- `UsagePeriod` now carries period totals (`period_total_litres`,
+  `period_total_consumption_m3`, costs and daily averages) plus the
+  per-day breakdown via `daily_points`.
+
+Callers using the old `consumption` attribute will need to update to
+`total_consumption_litres`.
+
+## [0.2.3] - 2026-05-06
+
+Smart meter rollout cohort fix.
+
+### Changed
+
+- `get_meter_details` and `get_current_consumption` now treat HTTP 404 as
+  "the account has no smart meter yet" rather than raising. They return
+  empty `MeterDetails` / `CurrentConsumption` objects so callers' code
+  paths stay straightforward and `meter_status` correctly reflects
+  `NO_METER`. Other HTTP error codes (5xx, 429, etc.) still raise as
+  before.
+
+## [0.2.2] - 2026-05-06
+
+Second pre-publish security pass.
+
+### Added
+
+- Authorize-redirect target validation. The library now rejects any
+  authorize redirect whose `Location` host or path does not match the
+  registered redirect URI, even if the response carries a valid state
+  and code. Defence in depth against tampered IdP responses.
+- RFC 9207 issuer parameter validation. If the redirect carries an
+  `iss` parameter, it must equal the configured IdP issuer (compared
+  with `hmac.compare_digest`). The Yorkshire Water IdP advertises
+  `authorization_response_iss_parameter_supported`, so this kicks in
+  whenever the IdP includes the parameter.
+
+### Changed
+
+- Test suite expanded with cases covering the new redirect target and
+  iss parameter validations.
+
+## [0.2.1] - 2026-05-06
+
+Security hardening from a pre-publish review.
+
+### Changed
+
+- The OAuth `state` parameter on the silent renewal redirect is now
+  required (a missing `state` raises `YorkshireWaterAuthError`) and the
+  comparison uses `hmac.compare_digest` for constant-time equality.
+- `YorkshireWaterAPIError` raised for non-JSON responses no longer inlines
+  the response body into the error message; the body remains available on
+  the exception's `body` attribute for debugging but cannot leak through
+  HA's user-visible repair issues.
+
+## [0.2.0] - 2026-05-06
+
+Auth model rewrite.
+
+### Changed
+
+- **Breaking**: Authentication now uses cookie-based silent renewal against
+  the IdentityServer at `login.yorkshirewater.com`. The `YorkshireWaterClient`
+  constructor takes a `cookies` argument and no longer accepts `email`,
+  `password` or `refresh_token`. Empirical testing confirmed that the SPA
+  OAuth client is not permitted to use the password grant or the device flow,
+  the SPA scope set does not include `offline_access`, and the login form is
+  protected by invisible reCAPTCHA v3.
+- The library now drives `/connect/authorize?prompt=none` with a fresh PKCE
+  verifier on every renewal, captures the authorization code from the
+  redirect Location header and exchanges it at `/connect/token`. There is no
+  refresh token flow because none is issued.
+- `close()` no longer revokes anything. There is no server-side credential
+  the library can revoke without a refresh token. The IdP session cookie is
+  the long-lived credential, managed by the user's browser.
+
+### Added
+
+- `CookieSessionExpiredError` (subclass of `YorkshireWaterAuthError`) raised
+  when silent renewal returns `error=login_required`. Callers should catch
+  this and prompt the user to re-export cookies from a fresh browser session.
+- `IDP_COOKIE_DOMAIN` constant exposed so callers can scope their cookie
+  capture correctly.
+
+### Removed
+
+- ROPC password grant support.
+- `refresh_token` constructor parameter.
+- Email and password storage in any client state.
+
+## [0.1.0] - 2026-05-06
+
+Initial release. ROPC-based authentication.
+
+DEPRECATED. The auth model in 0.1.0 was based on a static reading of the
+public OIDC discovery document, which lists the `password` grant as
+supported. Empirical testing against the live IdP showed that
+`password` is supported by the IdP but is rejected for the SPA client
+(`unauthorized_client`). 0.1 therefore cannot authenticate against any real
+account and was superseded by 0.2.0 within hours of release.
+
+### Added
+
+- Async client (`YorkshireWaterClient`) for the Yorkshire Water customer
+  self-service API at `my.yorkshirewater.com`.
+- Authentication via OpenID Connect Resource Owner Password Credentials
+  against the IdentityServer. Did not work in practice.
+- Smart meter endpoints, three-state `MeterStatus` enum, typed exceptions,
+  PEP 561 type information.

pyyorkshirewater-0.4.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Dan Simms
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

pyyorkshirewater-0.4.0/PKG-INFO

@@ -0,0 +1,171 @@
+Metadata-Version: 2.4
+Name: pyyorkshirewater
+Version: 0.4.0
+Summary: Async Python client for Yorkshire Water's customer self-service API. Unofficial and not affiliated with Yorkshire Water.
+Project-URL: Homepage, https://github.com/dan-simms1/pyyorkshirewater
+Project-URL: Repository, https://github.com/dan-simms1/pyyorkshirewater
+Project-URL: Issues, https://github.com/dan-simms1/pyyorkshirewater/issues
+Project-URL: Changelog, https://github.com/dan-simms1/pyyorkshirewater/blob/main/CHANGELOG.md
+Author: Dan Simms
+License: MIT
+License-File: LICENSE
+Keywords: home-assistant,smart-meter,utility,water,yorkshire-water
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: AsyncIO
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Home Automation
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: httpx<1.0,>=0.27
+Provides-Extra: dev
+Requires-Dist: mypy>=1.10; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest-cov>=5.0; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: respx>=0.21; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# pyyorkshirewater
+
+Async Python client for the Yorkshire Water customer self-service API.
+
+This library is unofficial and not affiliated with Yorkshire Water. It exists
+so that customers can read their own smart meter consumption data from the
+same backend that powers `my.yorkshirewater.com`.
+
+## Status
+
+Early alpha. The smart meter rollout is in progress across the Yorkshire
+Water region between 2025 and 2030, so most accounts will not yet have a live
+meter. Until a meter is live the client will report a `MeterStatus` of
+`NO_METER` or `PENDING_ACTIVATION`, and the consumption endpoints
+(`get_your_usage`, `get_daily_consumption`, `get_yearly_consumption`) will
+raise `YorkshireWaterMeterNotReadyError`. The readiness probes
+(`get_meter_details`, `get_current_consumption`) work in every state.
+
+## Why cookies, not email and password
+
+Yorkshire Water's portal SPA uses Duende IdentityServer with authorization
+code plus PKCE only. The SPA OAuth client (`css-onlineaccount-fe`) is not
+permitted to use the password grant, the device flow or `offline_access`,
+and the login form is protected by invisible Google reCAPTCHA v3 which a
+non-browser HTTP client cannot pass.
+
+The workable architecture is therefore: the user logs in to
+my.yorkshirewater.com once in their own browser, where reCAPTCHA succeeds
+naturally, and exports the IdentityServer session cookie. This library uses
+that cookie to drive `/connect/authorize?prompt=none` for silent renewal,
+mints fresh access tokens on demand and never sees the user's password.
+
+The companion Chrome extension (separate repository) makes cookie export a
+single click.
+
+## Install
+
+```bash
+pip install pyyorkshirewater
+```
+
+Python 3.11 or newer.
+
+## Quick start
+
+```python
+import asyncio
+from pyyorkshirewater import YorkshireWaterClient, MeterStatus
+
+cookies = {
+    "idsrv": "<value from a logged-in browser session>",
+    "idsrv.session": "<value from a logged-in browser session>",
+    # any other login.yorkshirewater.com cookies your browser holds
+}
+
+async def main():
+    async with YorkshireWaterClient(cookies=cookies) as client:
+        await client.login()
+
+        if client.meter_status is MeterStatus.LIVE:
+            daily = await client.get_daily_consumption()
+            print(daily)
+        else:
+            print(f"Meter is {client.meter_status.value}, no data yet.")
+
+asyncio.run(main())
+```
+
+## Cookie lifetime
+
+The IdentityServer session cookie typically lives between several hours and
+several weeks depending on the provider's configuration. Each silent renewal
+call may extend it (sliding expiration) on servers configured for that. When
+the cookie eventually expires, the library raises
+`CookieSessionExpiredError` (a subclass of `YorkshireWaterAuthError`) with
+`error="login_required"`. Callers should catch this and prompt the user for
+fresh cookies. The Home Assistant integration handles this via a reauth
+flow.
+
+## Meter readiness states
+
+Yorkshire Water's portal exposes a three-state model. The library mirrors it
+through the `MeterStatus` enum:
+
+- `NO_METER`: the account has no smart meter on it.
+- `PENDING_ACTIVATION`: a meter is registered but is awaiting network setup
+  by Yorkshire Water.
+- `LIVE`: the meter is reporting data and the consumption endpoints will
+  return real values.
+
+Application code should check `client.meter_status` before requesting
+consumption data.
+
+## Logging
+
+The library logs to a named logger called `pyyorkshirewater` at the `DEBUG`
+level. Configure it in the usual way:
+
+```python
+import logging
+logging.getLogger("pyyorkshirewater").setLevel(logging.DEBUG)
+```
+
+## Errors
+
+All errors raised by the library inherit from `YorkshireWaterError`. The
+specific subclasses are:
+
+- `YorkshireWaterAuthError`: silent renewal failed for a reason that is not
+  cookie expiry. The original IdentityServer `error` and `error_description`
+  are exposed on the exception.
+- `CookieSessionExpiredError` (subclass of `YorkshireWaterAuthError`): the
+  IdP session cookie is expired or invalid. Re-export from a fresh browser
+  session.
+- `YorkshireWaterAPIError`: a non-auth HTTP error from the customer API.
+- `YorkshireWaterMeterNotReadyError`: raised when a consumption endpoint is
+  called against a meter that is not yet `LIVE`.
+- `YorkshireWaterRateLimitError`: 429 response with optional `retry_after`.
+
+## Related projects
+
+- [`dan-simms1/ha-yorkshire-water`](https://github.com/dan-simms1/ha-yorkshire-water):
+  Home Assistant integration that uses this library.
+- (forthcoming) Chrome extension that extracts the cookies needed by this
+  library and the integration with one click.
+
+## Disclaimer
+
+This project is unofficial and not affiliated with, endorsed by or supported
+by Yorkshire Water Services Limited. Trademarks are the property of their
+respective owners. Use this software at your own risk and only against
+accounts that you own.
+
+## Licence
+
+MIT. See [LICENSE](LICENSE).

pyyorkshirewater-0.4.0/README.md

@@ -0,0 +1,136 @@
+# pyyorkshirewater
+
+Async Python client for the Yorkshire Water customer self-service API.
+
+This library is unofficial and not affiliated with Yorkshire Water. It exists
+so that customers can read their own smart meter consumption data from the
+same backend that powers `my.yorkshirewater.com`.
+
+## Status
+
+Early alpha. The smart meter rollout is in progress across the Yorkshire
+Water region between 2025 and 2030, so most accounts will not yet have a live
+meter. Until a meter is live the client will report a `MeterStatus` of
+`NO_METER` or `PENDING_ACTIVATION`, and the consumption endpoints
+(`get_your_usage`, `get_daily_consumption`, `get_yearly_consumption`) will
+raise `YorkshireWaterMeterNotReadyError`. The readiness probes
+(`get_meter_details`, `get_current_consumption`) work in every state.
+
+## Why cookies, not email and password
+
+Yorkshire Water's portal SPA uses Duende IdentityServer with authorization
+code plus PKCE only. The SPA OAuth client (`css-onlineaccount-fe`) is not
+permitted to use the password grant, the device flow or `offline_access`,
+and the login form is protected by invisible Google reCAPTCHA v3 which a
+non-browser HTTP client cannot pass.
+
+The workable architecture is therefore: the user logs in to
+my.yorkshirewater.com once in their own browser, where reCAPTCHA succeeds
+naturally, and exports the IdentityServer session cookie. This library uses
+that cookie to drive `/connect/authorize?prompt=none` for silent renewal,
+mints fresh access tokens on demand and never sees the user's password.
+
+The companion Chrome extension (separate repository) makes cookie export a
+single click.
+
+## Install
+
+```bash
+pip install pyyorkshirewater
+```
+
+Python 3.11 or newer.
+
+## Quick start
+
+```python
+import asyncio
+from pyyorkshirewater import YorkshireWaterClient, MeterStatus
+
+cookies = {
+    "idsrv": "<value from a logged-in browser session>",
+    "idsrv.session": "<value from a logged-in browser session>",
+    # any other login.yorkshirewater.com cookies your browser holds
+}
+
+async def main():
+    async with YorkshireWaterClient(cookies=cookies) as client:
+        await client.login()
+
+        if client.meter_status is MeterStatus.LIVE:
+            daily = await client.get_daily_consumption()
+            print(daily)
+        else:
+            print(f"Meter is {client.meter_status.value}, no data yet.")
+
+asyncio.run(main())
+```
+
+## Cookie lifetime
+
+The IdentityServer session cookie typically lives between several hours and
+several weeks depending on the provider's configuration. Each silent renewal
+call may extend it (sliding expiration) on servers configured for that. When
+the cookie eventually expires, the library raises
+`CookieSessionExpiredError` (a subclass of `YorkshireWaterAuthError`) with
+`error="login_required"`. Callers should catch this and prompt the user for
+fresh cookies. The Home Assistant integration handles this via a reauth
+flow.
+
+## Meter readiness states
+
+Yorkshire Water's portal exposes a three-state model. The library mirrors it
+through the `MeterStatus` enum:
+
+- `NO_METER`: the account has no smart meter on it.
+- `PENDING_ACTIVATION`: a meter is registered but is awaiting network setup
+  by Yorkshire Water.
+- `LIVE`: the meter is reporting data and the consumption endpoints will
+  return real values.
+
+Application code should check `client.meter_status` before requesting
+consumption data.
+
+## Logging
+
+The library logs to a named logger called `pyyorkshirewater` at the `DEBUG`
+level. Configure it in the usual way:
+
+```python
+import logging
+logging.getLogger("pyyorkshirewater").setLevel(logging.DEBUG)
+```
+
+## Errors
+
+All errors raised by the library inherit from `YorkshireWaterError`. The
+specific subclasses are:
+
+- `YorkshireWaterAuthError`: silent renewal failed for a reason that is not
+  cookie expiry. The original IdentityServer `error` and `error_description`
+  are exposed on the exception.
+- `CookieSessionExpiredError` (subclass of `YorkshireWaterAuthError`): the
+  IdP session cookie is expired or invalid. Re-export from a fresh browser
+  session.
+- `YorkshireWaterAPIError`: a non-auth HTTP error from the customer API.
+- `YorkshireWaterMeterNotReadyError`: raised when a consumption endpoint is
+  called against a meter that is not yet `LIVE`.
+- `YorkshireWaterRateLimitError`: 429 response with optional `retry_after`.
+
+## Related projects
+
+- [`dan-simms1/ha-yorkshire-water`](https://github.com/dan-simms1/ha-yorkshire-water):
+  Home Assistant integration that uses this library.
+- (forthcoming) Chrome extension that extracts the cookies needed by this
+  library and the integration with one click.
+
+## Disclaimer
+
+This project is unofficial and not affiliated with, endorsed by or supported
+by Yorkshire Water Services Limited. Trademarks are the property of their
+respective owners. Use this software at your own risk and only against
+accounts that you own.
+
+## Licence
+
+MIT. See [LICENSE](LICENSE).

pyyorkshirewater-0.4.0/pyproject.toml

@@ -0,0 +1,94 @@
+[build-system]
+requires = ["hatchling>=1.24"]
+build-backend = "hatchling.build"
+
+[project]
+name = "pyyorkshirewater"
+version = "0.4.0"
+description = "Async Python client for Yorkshire Water's customer self-service API. Unofficial and not affiliated with Yorkshire Water."
+readme = "README.md"
+license = { text = "MIT" }
+requires-python = ">=3.11"
+authors = [{ name = "Dan Simms" }]
+keywords = ["yorkshire-water", "smart-meter", "home-assistant", "water", "utility"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Framework :: AsyncIO",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Home Automation",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+    "Typing :: Typed",
+]
+dependencies = [
+    "httpx>=0.27,<1.0",
+]
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=8.0",
+    "pytest-asyncio>=0.23",
+    "pytest-cov>=5.0",
+    "respx>=0.21",
+    "ruff>=0.6",
+    "mypy>=1.10",
+]
+
+[project.urls]
+Homepage = "https://github.com/dan-simms1/pyyorkshirewater"
+Repository = "https://github.com/dan-simms1/pyyorkshirewater"
+Issues = "https://github.com/dan-simms1/pyyorkshirewater/issues"
+Changelog = "https://github.com/dan-simms1/pyyorkshirewater/blob/main/CHANGELOG.md"
+
+[tool.hatch.build.targets.wheel]
+packages = ["pyyorkshirewater"]
+
+[tool.hatch.build.targets.sdist]
+include = [
+    "pyyorkshirewater",
+    "tests",
+    "README.md",
+    "CHANGELOG.md",
+    "LICENSE",
+    "pyproject.toml",
+]
+
+[tool.pytest.ini_options]
+minversion = "8.0"
+asyncio_mode = "auto"
+testpaths = ["tests"]
+addopts = [
+    "-ra",
+    "--strict-markers",
+    "--strict-config",
+]
+markers = [
+    "integration: live integration tests against the real Yorkshire Water API. Skipped unless YW_INTEGRATION_TESTS=1.",
+]
+
+[tool.coverage.run]
+source = ["pyyorkshirewater"]
+branch = true
+
+[tool.coverage.report]
+show_missing = true
+skip_covered = false
+fail_under = 80
+exclude_lines = [
+    "pragma: no cover",
+    "raise NotImplementedError",
+    "if TYPE_CHECKING:",
+    "if __name__ == .__main__.:",
+]
+
+[tool.mypy]
+python_version = "3.11"
+strict = true
+warn_unused_ignores = true
+warn_redundant_casts = true
+disallow_untyped_defs = true

pyyorkshirewater-0.4.0/pyyorkshirewater/__init__.py

@@ -0,0 +1,69 @@
+"""Async Python client for Yorkshire Water's customer self-service API.
+
+This library is unofficial and not affiliated with Yorkshire Water Services
+Limited. It exists to let customers access their own smart meter data through
+the same backend that powers `my.yorkshirewater.com`.
+
+Authentication uses cookie-based silent renewal against the IdentityServer at
+`login.yorkshirewater.com`. The user logs in once via their own browser
+(reCAPTCHA passes naturally there) and exports the session cookie; the
+library uses it to mint fresh access tokens via
+`/connect/authorize?prompt=none` whenever needed.
+"""
+
+from __future__ import annotations
+
+from .auth import (
+    Authenticator,
+    CookieSessionExpiredError,
+)
+from .client import YorkshireWaterClient
+from .const import IDP_COOKIE_DOMAIN
+from .exceptions import (
+    YorkshireWaterAPIError,
+    YorkshireWaterAuthError,
+    YorkshireWaterError,
+    YorkshireWaterMeterNotReadyError,
+    YorkshireWaterRateLimitError,
+)
+from .models import (
+    Address,
+    ContinuousFlowAlarm,
+    CurrentConsumption,
+    Customer,
+    DailyConsumptionPoint,
+    MeterDetails,
+    MeterStatus,
+    PropertiesPage,
+    Property,
+    TokenSet,
+    UsagePeriod,
+    YearlyConsumptionPoint,
+)
+
+__version__ = "0.4.0"
+
+__all__ = [
+    "IDP_COOKIE_DOMAIN",
+    "Address",
+    "Authenticator",
+    "ContinuousFlowAlarm",
+    "CookieSessionExpiredError",
+    "CurrentConsumption",
+    "Customer",
+    "DailyConsumptionPoint",
+    "MeterDetails",
+    "MeterStatus",
+    "PropertiesPage",
+    "Property",
+    "TokenSet",
+    "UsagePeriod",
+    "YearlyConsumptionPoint",
+    "YorkshireWaterAPIError",
+    "YorkshireWaterAuthError",
+    "YorkshireWaterClient",
+    "YorkshireWaterError",
+    "YorkshireWaterMeterNotReadyError",
+    "YorkshireWaterRateLimitError",
+    "__version__",
+]