violet-poolController-api 0.0.37__tar.gz → 0.0.39__tar.gz

{violet_poolcontroller_api-0.0.37/violet_poolController_api.egg-info → violet_poolcontroller_api-0.0.39}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: violet-poolController-api
-Version: 0.0.37
+Version: 0.0.39
 Summary: Asynchronous Python client for the Violet Pool Controller.
 Author-email: "Basti (Xerolux)" <git@xerolux.de>
 License-Expression: AGPL-3.0-or-later
@@ -20,7 +20,7 @@ Classifier: Topic :: Home Automation
 Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: aiohttp<3.15,>=3.11.0
+Requires-Dist: aiohttp>=3.11.0
 Provides-Extra: test
 Requires-Dist: aioresponses>=0.7.9; extra == "test"
 Requires-Dist: mypy>=1.15; extra == "test"
@@ -40,7 +40,7 @@ Dynamic: license-file
 
 An asynchronous Python client for interacting with the **Violet Pool Controller**.
 
-This library is primarily designed to power the official [Violet Pool Controller Home Assistant Integration](https://github.com/Xerolux/violet-hass), but it can be used independently for any Python project that needs to fetch readings or control a Violet Pool system.
+This library is primarily designed to power the [Violet Pool Controller Home Assistant Integration](https://github.com/Xerolux/violet-hass), but it can be used independently for any Python project that needs to fetch readings or control a Violet Pool system.
 
 > **📖 Documentation:**
 > - GitHub Pages: https://xerolux.github.io/violet-poolController-api/
@@ -117,7 +117,7 @@ The API client includes many more functions tailored to the Violet Controller:
 - `set_pv_surplus(active=True)`: Enable the PV-Surplus mode.
 - `manual_dosing(dosing_type="Chlor", duration=120)`: Trigger manual chemical dosing.
 
-For a full list of available commands and more detailed examples, please refer to the [Wiki](https://github.com/Xerolux/violet-poolController-api/wiki) or the source code in `api.py`.
+For a full list of available commands and more detailed examples, please refer to the [Wiki](https://github.com/Xerolux/violet-poolController-api/wiki) or the `_api_*.py` mixins, which hold the public methods.
 
 ## Violet Dosing Standalone Mode
 
@@ -136,7 +136,7 @@ api = VioletPoolAPI(
 In this mode, dosing functions (for example `manual_dosing` and dosing parameter/target updates) stay available, while base-module-only switch functions (for example pump/light/backwash) are blocked with a clear error message.
 
 **Note on getReadings format:**
-As of version `0.0.7`, the API client automatically detects and normalizes the payload output from the controller. Whether your Violet Controller returns the classic base-module `dict` structure (`{"PUMPSTATE": "2", "PH": 7.2}`) or the new standalone `list` structure, the `get_readings()` and `get_specific_readings()` functions will always return a seamless, flattened key-value dictionary. Your Home Assistant integration or downstream application will work uniformly with both formats without requiring any extra code!
+As of version `0.0.7`, the API client automatically detects and normalizes the payload output from the controller. Whether your Violet Controller returns the classic base-module `dict` structure (`{"PUMPSTATE": "2", "PH": 7.2}`) or the new standalone `list` structure, the `get_readings()` and `get_specific_readings()` functions always return a flattened key-value view. `get_readings()` returns a `VioletReadings`, a read-only `Mapping` with typed accessors on top; use `dict(readings)` where a plain `dict` is required, for example before JSON serialization. Your Home Assistant integration or downstream application will work uniformly with both formats without requiring any extra code!
 
 **Hardware Profile Detection:**
 As of the latest release, the API client provides a method to detect the specific hardware configuration of your Violet Controller.
@@ -152,7 +152,7 @@ print(profile)
 #     "extension_module_2": False,
 # }
 ```
-This detection parses `get_readings()` to check for the presence of certain internal status parameters (`SYSTEM_dosagemodule_cpu_temperature`, `EXT1_1`, `EXT2_1`), allowing your application to dynamically adapt to the connected modules (Base Module, Dosing Module, Relay Extension 1 and 2). By utilizing this detection, developers and integrations can accurately filter out features for missing hardware, ensuring that only supported options are exposed to the user.
+This detection reads the controller's own module counters (`SYSTEM_dosagemodule_alive_count`, `SYSTEM_ext1module_alive_count`, `SYSTEM_ext2module_alive_count`), allowing your application to dynamically adapt to the connected modules (Base Module, Dosing Module, Relay Extension 1 and 2). By utilizing this detection, developers and integrations can accurately filter out features for missing hardware, ensuring that only supported options are exposed to the user.
 
 ## Mock Server (Testing Without Hardware)
 
@@ -229,7 +229,7 @@ GNU Affero General Public License v3.0 or later (AGPLv3+)
 
 The **VIOLET Pool Controller** by [PoolDigital GmbH & Co. KG](https://www.pooldigital.de/) is a premium smart pool automation system developed in Germany, featuring a JSON API for seamless Home Assistant integration.
 
-- **Offizieller Shop:** [pooldigital.de](https://www.pooldigital.de/)
+- **Official shop:** [pooldigital.de](https://www.pooldigital.de/)
 - **Community:** [PoolDigital Forum](http://forum.pooldigital.de/)
 
 **Disclaimer:**

{violet_poolcontroller_api-0.0.37 → violet_poolcontroller_api-0.0.39}/README.md

@@ -10,7 +10,7 @@
 
 An asynchronous Python client for interacting with the **Violet Pool Controller**.
 
-This library is primarily designed to power the official [Violet Pool Controller Home Assistant Integration](https://github.com/Xerolux/violet-hass), but it can be used independently for any Python project that needs to fetch readings or control a Violet Pool system.
+This library is primarily designed to power the [Violet Pool Controller Home Assistant Integration](https://github.com/Xerolux/violet-hass), but it can be used independently for any Python project that needs to fetch readings or control a Violet Pool system.
 
 > **📖 Documentation:**
 > - GitHub Pages: https://xerolux.github.io/violet-poolController-api/
@@ -87,7 +87,7 @@ The API client includes many more functions tailored to the Violet Controller:
 - `set_pv_surplus(active=True)`: Enable the PV-Surplus mode.
 - `manual_dosing(dosing_type="Chlor", duration=120)`: Trigger manual chemical dosing.
 
-For a full list of available commands and more detailed examples, please refer to the [Wiki](https://github.com/Xerolux/violet-poolController-api/wiki) or the source code in `api.py`.
+For a full list of available commands and more detailed examples, please refer to the [Wiki](https://github.com/Xerolux/violet-poolController-api/wiki) or the `_api_*.py` mixins, which hold the public methods.
 
 ## Violet Dosing Standalone Mode
 
@@ -106,7 +106,7 @@ api = VioletPoolAPI(
 In this mode, dosing functions (for example `manual_dosing` and dosing parameter/target updates) stay available, while base-module-only switch functions (for example pump/light/backwash) are blocked with a clear error message.
 
 **Note on getReadings format:**
-As of version `0.0.7`, the API client automatically detects and normalizes the payload output from the controller. Whether your Violet Controller returns the classic base-module `dict` structure (`{"PUMPSTATE": "2", "PH": 7.2}`) or the new standalone `list` structure, the `get_readings()` and `get_specific_readings()` functions will always return a seamless, flattened key-value dictionary. Your Home Assistant integration or downstream application will work uniformly with both formats without requiring any extra code!
+As of version `0.0.7`, the API client automatically detects and normalizes the payload output from the controller. Whether your Violet Controller returns the classic base-module `dict` structure (`{"PUMPSTATE": "2", "PH": 7.2}`) or the new standalone `list` structure, the `get_readings()` and `get_specific_readings()` functions always return a flattened key-value view. `get_readings()` returns a `VioletReadings`, a read-only `Mapping` with typed accessors on top; use `dict(readings)` where a plain `dict` is required, for example before JSON serialization. Your Home Assistant integration or downstream application will work uniformly with both formats without requiring any extra code!
 
 **Hardware Profile Detection:**
 As of the latest release, the API client provides a method to detect the specific hardware configuration of your Violet Controller.
@@ -122,7 +122,7 @@ print(profile)
 #     "extension_module_2": False,
 # }
 ```
-This detection parses `get_readings()` to check for the presence of certain internal status parameters (`SYSTEM_dosagemodule_cpu_temperature`, `EXT1_1`, `EXT2_1`), allowing your application to dynamically adapt to the connected modules (Base Module, Dosing Module, Relay Extension 1 and 2). By utilizing this detection, developers and integrations can accurately filter out features for missing hardware, ensuring that only supported options are exposed to the user.
+This detection reads the controller's own module counters (`SYSTEM_dosagemodule_alive_count`, `SYSTEM_ext1module_alive_count`, `SYSTEM_ext2module_alive_count`), allowing your application to dynamically adapt to the connected modules (Base Module, Dosing Module, Relay Extension 1 and 2). By utilizing this detection, developers and integrations can accurately filter out features for missing hardware, ensuring that only supported options are exposed to the user.
 
 ## Mock Server (Testing Without Hardware)
 
@@ -199,7 +199,7 @@ GNU Affero General Public License v3.0 or later (AGPLv3+)
 
 The **VIOLET Pool Controller** by [PoolDigital GmbH & Co. KG](https://www.pooldigital.de/) is a premium smart pool automation system developed in Germany, featuring a JSON API for seamless Home Assistant integration.
 
-- **Offizieller Shop:** [pooldigital.de](https://www.pooldigital.de/)
+- **Official shop:** [pooldigital.de](https://www.pooldigital.de/)
 - **Community:** [PoolDigital Forum](http://forum.pooldigital.de/)
 
 **Disclaimer:**

{violet_poolcontroller_api-0.0.37 → violet_poolcontroller_api-0.0.39}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "violet-poolController-api"
-version = "0.0.37"
+version = "0.0.39"
 authors = [
   { name="Basti (Xerolux)", email="git@xerolux.de" },
 ]
@@ -25,7 +25,11 @@ classifiers = [
     "Topic :: Home Automation",
 ]
 dependencies = [
-    "aiohttp>=3.11.0,<3.15",
+    # No upper bound on purpose: Home Assistant installs this package into
+    # its own environment and follows aiohttp closely.  A "<3.15" cap made pip
+    # refuse the install the day HA moved past it, taking the integration down
+    # with it.  Compatibility with newer aiohttp is handled in the test shim.
+    "aiohttp>=3.11.0",
 ]
 
 [project.optional-dependencies]

{violet_poolcontroller_api-0.0.37 → violet_poolcontroller_api-0.0.39}/tests/test_api.py

@@ -1,4 +1,4 @@
-# violet-poolController-api - API für Violet Pool Controller
+# violet-poolController-api - API for Violet Pool Controller
 # Copyright (C) 2024-2026  Xerolux
 #
 # This program is free software: you can redistribute it and/or modify
@@ -274,11 +274,56 @@ async def test_set_config_sanitizes_payload_before_request(
 
     monkeypatch.setattr(api_client, "_request", fake_request)
 
-    result = await api_client.set_config({"pool mode": "A<mode>", "speed": 3.7})
+    result = await api_client.set_config({"POOL_MODE": "A<mode>", "speed": 3.7})
 
     assert result["success"] is True
     assert result["response"] == "OK"
-    assert captured["data"] == {"poolmode": "A<mode>", "speed": 3.7}
+    assert captured["data"] == {"POOL_MODE": "A<mode>", "speed": 3.7}
+
+
+@pytest.mark.asyncio
+async def test_set_config_rejects_invalid_key_instead_of_rewriting_it(
+    api_client: VioletPoolAPI,
+    monkeypatch: pytest.Monkeypatch,
+) -> None:
+    """A malformed key is an error, never a silent write to a different key.
+
+    ``"pool mode"`` used to be rewritten to ``"poolmode"`` and sent, so a typo
+    in a configuration key changed a setting the caller never named.
+    """
+    sent = False
+
+    async def fake_request(_endpoint: str, **_kwargs: Any) -> str:  # noqa: ANN401
+        nonlocal sent
+        sent = True
+        return "OK"
+
+    monkeypatch.setattr(api_client, "_request", fake_request)
+
+    with pytest.raises(VioletPoolAPIError, match="Invalid configuration parameter"):
+        await api_client.set_config({"pool mode": "A"})
+
+    assert sent is False
+
+
+@pytest.mark.asyncio
+async def test_set_config_rejects_unsupported_value_types(
+    api_client: VioletPoolAPI,
+    monkeypatch: pytest.Monkeypatch,
+) -> None:
+    """None and containers must not reach the controller as "None" or "1 2"."""
+
+    async def fake_request(_endpoint: str, **_kwargs: Any) -> str:  # noqa: ANN401
+        return "OK"
+
+    monkeypatch.setattr(api_client, "_request", fake_request)
+
+    for bad_value in (None, [1, 2], {"a": 1}):
+        with pytest.raises(VioletPoolAPIError):
+            await api_client.set_config({"SOME_KEY": bad_value})
+
+    with pytest.raises(VioletPoolAPIError, match="Non-finite"):
+        await api_client.set_config({"SOME_KEY": float("nan")})
 
 
 @pytest.mark.asyncio
@@ -1383,14 +1428,20 @@ async def test_command_result_dosing_started(
 
 
 @pytest.mark.asyncio
-async def test_command_result_dict_passthrough(
+async def test_command_result_normalizes_dict_input(
     api_client: VioletPoolAPI,
 ) -> None:
-    """Test _command_result passes dict through unchanged."""
+    """A dict body is normalized, so ``success`` is always present.
+
+    The old passthrough returned the dict unchanged, so a caller reading
+    ``result["success"]`` got a KeyError instead of a result.
+    """
     data = {"key": "value", "nested": {"a": 1}}
     result = VioletPoolAPI._command_result(data)
 
-    assert result is data
+    assert result["success"] is True
+    assert result["key"] == "value"
+    assert result["nested"] == {"a": 1}
 
 
 @pytest.mark.asyncio
@@ -2130,3 +2181,163 @@ def test_input_sanitizer_no_duplicate_validate_duration() -> None:
 
     assert not hasattr(InputSanitizer, "validate_duration")
     assert not hasattr(InputSanitizer, "validate_speed")
+
+
+def _request_count(mocked: aioresponses, method: str, path: str) -> int:
+    """Count recorded requests to *path*, ignoring query-string normalization.
+
+    yarl rewrites a value-less query (``?PUMP,ON,0,0``) by appending ``=``, so
+    the recorded key never equals the URL that was requested.
+    """
+    return sum(
+        len(calls)
+        for (recorded_method, url), calls in mocked.requests.items()
+        if recorded_method == method and url.path == path
+    )
+
+
+# ---------------------------------------------------------------------------
+# Regression: state-changing commands are sent exactly once (0.0.39)
+# ---------------------------------------------------------------------------
+
+
+@pytest.mark.asyncio
+async def test_switch_command_is_not_retried(
+    mock_aioresponse: aioresponses,
+) -> None:
+    """A failed switch command must not be repeated.
+
+    The controller applies state changes through GET, and a request that
+    timed out may well have been applied.  Repeating it can toggle the output
+    back or apply it a second time.
+    """
+    url = "http://192.168.1.100/setFunctionManually?PUMP,ON,0,0"
+    mock_aioresponse.get(url, status=500, body="boom")
+
+    async with aiohttp.ClientSession() as session:
+        api = VioletPoolAPI(host="192.168.1.100", session=session, max_retries=3)
+        with pytest.raises(VioletPoolAPIError):
+            await api.set_switch_state("PUMP", "ON")
+
+    assert _request_count(mock_aioresponse, "GET", "/setFunctionManually") == 1
+
+
+@pytest.mark.asyncio
+async def test_digital_rule_trigger_is_not_retried(
+    mock_aioresponse: aioresponses,
+) -> None:
+    """PUSH is a toggle: a retry would undo the change it just made."""
+    url = "http://192.168.1.100/setFunctionManually?DIRULE_1,PUSH,0,0"
+    mock_aioresponse.get(url, status=500, body="boom")
+
+    async with aiohttp.ClientSession() as session:
+        api = VioletPoolAPI(host="192.168.1.100", session=session, max_retries=3)
+        with pytest.raises(VioletPoolAPIError):
+            await api.trigger_digital_input_rule("DIRULE_1")
+
+    assert _request_count(mock_aioresponse, "GET", "/setFunctionManually") == 1
+
+
+@pytest.mark.asyncio
+async def test_init_update_is_not_retried(
+    mock_aioresponse: aioresponses,
+) -> None:
+    """Starting a firmware update twice is not harmless."""
+    url = "http://192.168.1.100/initUpdate"
+    mock_aioresponse.get(url, status=503, body="busy")
+
+    async with aiohttp.ClientSession() as session:
+        api = VioletPoolAPI(host="192.168.1.100", session=session, max_retries=3)
+        with pytest.raises(VioletPoolAPIError):
+            await api.init_update()
+
+    assert _request_count(mock_aioresponse, "GET", "/initUpdate") == 1
+
+
+@pytest.mark.asyncio
+async def test_reads_are_still_retried(
+    mock_aioresponse: aioresponses,
+) -> None:
+    """The read path keeps its retries; repeating a read costs nothing."""
+    url = "http://192.168.1.100/getReadings?ALL"
+    mock_aioresponse.get(url, status=500, body="boom")
+    mock_aioresponse.get(url, status=500, body="boom")
+    mock_aioresponse.get(url, payload={"getReadings": {"PUMP": "1"}}, status=200)
+
+    async with aiohttp.ClientSession() as session:
+        api = VioletPoolAPI(host="192.168.1.100", session=session, max_retries=3)
+        readings = await api.get_readings()
+
+    assert readings["PUMP"] == "1"
+    assert _request_count(mock_aioresponse, "GET", "/getReadings") == 3
+
+
+@pytest.mark.asyncio
+async def test_rate_limit_wait_timeout_fails_instead_of_bypassing(
+    mock_aioresponse: aioresponses,
+    monkeypatch: pytest.Monkeypatch,
+) -> None:
+    """A limiter timeout must fail the request, not send it without a token.
+
+    Sending anyway let every caller that waited out the timeout hit the
+    controller at once, which is the pile-up the limiter exists to prevent.
+    """
+    url = "http://192.168.1.100/getReadings?ALL"
+    mock_aioresponse.get(url, payload={"getReadings": {}}, status=200)
+
+    async with aiohttp.ClientSession() as session:
+        api = VioletPoolAPI(host="192.168.1.100", session=session, max_retries=1)
+
+        async def always_timeout(**_kwargs: Any) -> None:
+            raise TimeoutError
+
+        monkeypatch.setattr(api._rate_limiter, "wait_if_needed", always_timeout)
+
+        with pytest.raises(VioletPoolAPIError, match="Rate limit wait"):
+            await api.get_readings()
+
+    assert _request_count(mock_aioresponse, "GET", "/getReadings") == 0
+
+
+@pytest.mark.asyncio
+async def test_html_login_page_does_not_open_the_circuit_breaker(
+    mock_aioresponse: aioresponses,
+) -> None:
+    """A captive portal answers 200 with HTML every time, deterministically.
+
+    Counting those as transient failures opened the breaker and replaced the
+    payload error that explains the actual problem.
+    """
+    url = "http://192.168.1.100/getReadings?ALL"
+    for _ in range(8):
+        mock_aioresponse.get(url, body="<html>login</html>", status=200)
+
+    async with aiohttp.ClientSession() as session:
+        api = VioletPoolAPI(host="192.168.1.100", session=session, max_retries=1)
+        for _ in range(8):
+            with pytest.raises(VioletPoolAPIError) as excinfo:
+                await api.get_readings()
+            assert "Invalid JSON payload" in str(excinfo.value)
+
+
+def test_hostname_error_never_echoes_credentials() -> None:
+    """The message reaches config-flow errors and logs; it must stay clean."""
+    with pytest.raises(ValueError, match="must not contain credentials") as excinfo:
+        VioletPoolAPI._build_secure_base_url(
+            VioletPoolAPI,
+            "http://admin:s3cret@192.168.1.5",
+            use_ssl=False,
+        )
+
+    assert "s3cret" not in str(excinfo.value)
+
+
+def test_hostname_accepts_underscores() -> None:
+    """mDNS and router-assigned names use underscores."""
+    url = VioletPoolAPI._build_secure_base_url(
+        VioletPoolAPI,
+        "violet_pool.local",
+        use_ssl=False,
+    )
+
+    assert url == "http://violet_pool.local"

violet_poolcontroller_api-0.0.39/tests/test_language_policy.py

@@ -0,0 +1,154 @@
+# violet-poolController-api - API for Violet Pool Controller
+# Copyright (C) 2024-2026  Xerolux
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU Affero General Public License as published
+# by the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU Affero General Public License for more details.
+#
+# You should have received a copy of the GNU Affero General Public License
+# along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+"""Everything written into this repository is English.
+
+The policy lives in AGENTS.md; this file is what makes it hold. Two things are
+deliberately exempt and must stay exempt: the controller's own error strings in
+``const_api.py`` (and the German payloads the mock server replays), which are
+data rather than prose, and the German half of the bilingual documentation
+under ``docs/de/``.
+"""
+
+# ruff: noqa: S101
+
+from __future__ import annotations
+
+import re
+from pathlib import Path
+
+import pytest
+
+REPO = Path(__file__).parent.parent
+PACKAGE = REPO / "violet_poolcontroller_api"
+
+# Text the controller emits, reproduced verbatim. Translating it would break
+# the match with what the device actually says.
+#
+# Matched by file name, not by path: `python -m build` copies the package into
+# `build/lib/`, and an exemption keyed to the original path does not cover the
+# copy. That is not hypothetical - it failed the 0.0.38 release job, because
+# the release builds the wheel before running the checks.
+CONTROLLER_VERBATIM = frozenset({"const_api.py", "mock_server.py"})
+
+# This file has to name the German words it looks for.
+SELF = Path(__file__).name
+
+# Directories that hold generated or vendored copies of the sources. Scanning
+# them says nothing about what is written in this repository.
+GENERATED_DIRS = frozenset({".git", ".tox", ".venv", "venv", "build", "dist", "__pycache__"})
+
+# Words that only appear in German prose. Deliberately not "in", "die" or "der":
+# those collide with English or with identifiers.
+GERMAN_WORDS = (
+    "für",
+    "über",
+    "nicht",
+    "wird",
+    "werden",
+    "wenn",
+    "diese",
+    "dieser",
+    "keine",
+    "sollte",
+    # Added after 0.0.38 shipped with ~20 German docstrings and log lines in
+    # utils_sanitizer.py and utils_rate_limiter.py that this list did not see.
+    "einen",
+    "eine",
+    "verwende",
+    "ungültig",
+    "ungültige",
+    "ungültigen",
+    "ungültiger",
+    "verfügbar",
+    "gefährlich",
+    "gefährliche",
+    "erlaubt",
+    "erlaubter",
+    "zurückgesetzt",
+    "initialisiert",
+    "unbekannter",
+    "warte",
+)
+_GERMAN = re.compile(r"\b(" + "|".join(GERMAN_WORDS) + r")\b", re.IGNORECASE)
+
+
+def _python_sources() -> list[Path]:
+    """Return every Python file the policy applies to."""
+    return sorted(
+        path
+        for path in REPO.rglob("*.py")
+        if not (GENERATED_DIRS & set(path.parts))
+        and not any(part.endswith(".egg-info") for part in path.parts)
+        and path.name not in CONTROLLER_VERBATIM
+        and path.name != SELF
+    )
+
+
+@pytest.mark.parametrize("path", _python_sources(), ids=lambda p: p.name)
+def test_python_sources_are_english(path: Path) -> None:
+    """A German comment is read by people who do not speak German."""
+    offenders = [
+        f"{path.relative_to(REPO)}:{number}: {line.strip()}"
+        for number, line in enumerate(path.read_text(encoding="utf-8").splitlines(), 1)
+        if _GERMAN.search(line)
+    ]
+
+    assert not offenders, "German text outside the exempt files:\n" + "\n".join(offenders)
+
+
+def test_the_changelog_is_english() -> None:
+    """The changelog is what a consumer reads when a version breaks something.
+
+    Code spans are quotations, not prose: an entry that removes a German string
+    has to be able to name the string it removed.
+    """
+    changelog = (REPO / "CHANGELOG.md").read_text(encoding="utf-8")
+    prose = re.sub(r"`[^`]*`", "", changelog)
+
+    offenders = sorted({match.group(0).lower() for match in _GERMAN.finditer(prose)})
+
+    assert not offenders, f"German outside code spans in CHANGELOG.md: {offenders}"
+
+
+def test_the_controller_strings_stay_german() -> None:
+    """The exemption is the point, not an oversight - guard it too.
+
+    If someone "cleans up" the error table into English, the messages stop
+    matching what the device reports.
+    """
+    const_api = (PACKAGE / "const_api.py").read_text(encoding="utf-8")
+
+    assert "Filterdrucküberwachung (Druck zu niedrig)" in const_api
+
+
+def test_generated_copies_are_not_scanned() -> None:
+    """A built wheel is not source, and scanning its copy fails the release.
+
+    `python -m build` writes `build/lib/<package>/`, so the release job runs
+    the checks with a duplicate of every module on disk.
+    """
+    scanned = {path.name for path in _python_sources()}
+
+    assert "const_api.py" not in scanned
+    assert not [path for path in _python_sources() if "build" in path.parts]
+
+
+def test_the_policy_is_written_down() -> None:
+    """Without the rule in AGENTS.md this file is just an opinion."""
+    agents = (REPO / "AGENTS.md").read_text(encoding="utf-8")
+
+    assert "## Language Policy" in agents

{violet_poolcontroller_api-0.0.37 → violet_poolcontroller_api-0.0.39/violet_poolController_api.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: violet-poolController-api
-Version: 0.0.37
+Version: 0.0.39
 Summary: Asynchronous Python client for the Violet Pool Controller.
 Author-email: "Basti (Xerolux)" <git@xerolux.de>
 License-Expression: AGPL-3.0-or-later
@@ -20,7 +20,7 @@ Classifier: Topic :: Home Automation
 Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: aiohttp<3.15,>=3.11.0
+Requires-Dist: aiohttp>=3.11.0
 Provides-Extra: test
 Requires-Dist: aioresponses>=0.7.9; extra == "test"
 Requires-Dist: mypy>=1.15; extra == "test"
@@ -40,7 +40,7 @@ Dynamic: license-file
 
 An asynchronous Python client for interacting with the **Violet Pool Controller**.
 
-This library is primarily designed to power the official [Violet Pool Controller Home Assistant Integration](https://github.com/Xerolux/violet-hass), but it can be used independently for any Python project that needs to fetch readings or control a Violet Pool system.
+This library is primarily designed to power the [Violet Pool Controller Home Assistant Integration](https://github.com/Xerolux/violet-hass), but it can be used independently for any Python project that needs to fetch readings or control a Violet Pool system.
 
 > **📖 Documentation:**
 > - GitHub Pages: https://xerolux.github.io/violet-poolController-api/
@@ -117,7 +117,7 @@ The API client includes many more functions tailored to the Violet Controller:
 - `set_pv_surplus(active=True)`: Enable the PV-Surplus mode.
 - `manual_dosing(dosing_type="Chlor", duration=120)`: Trigger manual chemical dosing.
 
-For a full list of available commands and more detailed examples, please refer to the [Wiki](https://github.com/Xerolux/violet-poolController-api/wiki) or the source code in `api.py`.
+For a full list of available commands and more detailed examples, please refer to the [Wiki](https://github.com/Xerolux/violet-poolController-api/wiki) or the `_api_*.py` mixins, which hold the public methods.
 
 ## Violet Dosing Standalone Mode
 
@@ -136,7 +136,7 @@ api = VioletPoolAPI(
 In this mode, dosing functions (for example `manual_dosing` and dosing parameter/target updates) stay available, while base-module-only switch functions (for example pump/light/backwash) are blocked with a clear error message.
 
 **Note on getReadings format:**
-As of version `0.0.7`, the API client automatically detects and normalizes the payload output from the controller. Whether your Violet Controller returns the classic base-module `dict` structure (`{"PUMPSTATE": "2", "PH": 7.2}`) or the new standalone `list` structure, the `get_readings()` and `get_specific_readings()` functions will always return a seamless, flattened key-value dictionary. Your Home Assistant integration or downstream application will work uniformly with both formats without requiring any extra code!
+As of version `0.0.7`, the API client automatically detects and normalizes the payload output from the controller. Whether your Violet Controller returns the classic base-module `dict` structure (`{"PUMPSTATE": "2", "PH": 7.2}`) or the new standalone `list` structure, the `get_readings()` and `get_specific_readings()` functions always return a flattened key-value view. `get_readings()` returns a `VioletReadings`, a read-only `Mapping` with typed accessors on top; use `dict(readings)` where a plain `dict` is required, for example before JSON serialization. Your Home Assistant integration or downstream application will work uniformly with both formats without requiring any extra code!
 
 **Hardware Profile Detection:**
 As of the latest release, the API client provides a method to detect the specific hardware configuration of your Violet Controller.
@@ -152,7 +152,7 @@ print(profile)
 #     "extension_module_2": False,
 # }
 ```
-This detection parses `get_readings()` to check for the presence of certain internal status parameters (`SYSTEM_dosagemodule_cpu_temperature`, `EXT1_1`, `EXT2_1`), allowing your application to dynamically adapt to the connected modules (Base Module, Dosing Module, Relay Extension 1 and 2). By utilizing this detection, developers and integrations can accurately filter out features for missing hardware, ensuring that only supported options are exposed to the user.
+This detection reads the controller's own module counters (`SYSTEM_dosagemodule_alive_count`, `SYSTEM_ext1module_alive_count`, `SYSTEM_ext2module_alive_count`), allowing your application to dynamically adapt to the connected modules (Base Module, Dosing Module, Relay Extension 1 and 2). By utilizing this detection, developers and integrations can accurately filter out features for missing hardware, ensuring that only supported options are exposed to the user.
 
 ## Mock Server (Testing Without Hardware)
 
@@ -229,7 +229,7 @@ GNU Affero General Public License v3.0 or later (AGPLv3+)
 
 The **VIOLET Pool Controller** by [PoolDigital GmbH & Co. KG](https://www.pooldigital.de/) is a premium smart pool automation system developed in Germany, featuring a JSON API for seamless Home Assistant integration.
 
-- **Offizieller Shop:** [pooldigital.de](https://www.pooldigital.de/)
+- **Official shop:** [pooldigital.de](https://www.pooldigital.de/)
 - **Community:** [PoolDigital Forum](http://forum.pooldigital.de/)
 
 **Disclaimer:**

{violet_poolcontroller_api-0.0.37 → violet_poolcontroller_api-0.0.39}/violet_poolController_api.egg-info/SOURCES.txt

@@ -4,6 +4,7 @@ pyproject.toml
 tests/test_api.py
 tests/test_api_smoke.py
 tests/test_circuit_breaker.py
+tests/test_language_policy.py
 tests/test_mock_server.py
 tests/test_parsers.py
 tests/test_rate_limiter.py

{violet_poolcontroller_api-0.0.37 → violet_poolcontroller_api-0.0.39}/violet_poolController_api.egg-info/requires.txt

@@ -1,4 +1,4 @@
-aiohttp<3.15,>=3.11.0
+aiohttp>=3.11.0
 
 [test]
 aioresponses>=0.7.9