ihcctl 0.2.0__tar.gz

ihcctl-0.2.0/PKG-INFO

@@ -0,0 +1,110 @@
+Metadata-Version: 2.4
+Name: ihcctl
+Version: 0.2.0
+Summary: Python library and CLI for local Zehnder IHC control
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+Requires-Dist: bleak>=0.22
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+
+# ihcctl
+
+`ihcctl` is a Python library and CLI for local Zehnder IHC controller control
+over Bluetooth Low Energy. Normal use does not require a cloud service.
+
+The distribution is `ihcctl`; the Python import namespace remains
+`zehnder_ihc`; the CLI command is `ihcctl`.
+
+## Install
+
+For the CLI, prefer pipx:
+
+```bash
+pipx install ihcctl
+ihcctl --help
+```
+
+Alternatively install into a Python environment:
+
+```bash
+python -m pip install ihcctl
+```
+
+The first public release, `ihcctl` 0.2.0, is prepared but not yet published.
+Until public publication and verification, these are the intended future
+commands rather than a current PyPI installation path.
+
+## Python library and CLI
+
+Use `import zehnder_ihc` or import public classes directly:
+
+```python
+from zehnder_ihc import IHCClient
+```
+
+The CLI requires a Bluetooth address and an externally stored identity file.
+Do not commit it or share it with Home Assistant.
+
+```bash
+ihcctl --help
+ihcctl register --help
+```
+
+Registration requires physical IHC confirmation. The help commands do not
+contact hardware. Do not keep the CLI connected while Home Assistant polls the
+same controller.
+
+## Home Assistant
+
+The custom integration uses the same `zehnder_ihc` library internally. During
+this preparation phase its `manifest.json` deliberately retains the existing
+local direct-wheel requirement; it has not switched to `ihcctl`.
+
+Only after a verified public PyPI release will a separately authorized change
+pin it to `ihcctl==0.2.0`. Do not manually install, uninstall, or remove
+packages in a Home Assistant container.
+
+The optional Schedule Manager resource is:
+
+```yaml
+url: /zehnder_ihc/frontend/zehnder-ihc-schedule-card.js
+type: module
+```
+
+## Development / fallback workflow
+
+`tools/start-local-pypi.sh` and local pypiserver remain development/fallback
+tools. They are not the normal workflow for new CLI users or the intended
+production Home Assistant workflow after public PyPI migration. Existing Home
+Assistant deployments still need the current local wheel until the later
+manifest migration succeeds.
+
+For repository work, use the existing test extra:
+
+```bash
+python -m venv .venv
+source .venv/bin/activate
+python -m pip install -e ".[test]"
+python -m pytest -q
+```
+
+Tests use sanitized frames and fake BLE backends; they do not contact IHC
+hardware or perform writes.
+
+## Publishing
+
+Maintainers must read [the publishing guide](docs/publishing-pypi.md). Local
+readiness never publishes:
+
+```bash
+tools/release-pypi.sh --check
+```
+
+TestPyPI and production PyPI require separate explicit authorization.
+
+## Safety
+
+Phase-1 research is frozen. Never commit client identities, `ihc-client*.json`,
+or files under `phase1-private/`. Hardware-changing tests need explicit
+approval and protocol-level readback where possible.

ihcctl-0.2.0/README.md

@@ -0,0 +1,100 @@
+# ihcctl
+
+`ihcctl` is a Python library and CLI for local Zehnder IHC controller control
+over Bluetooth Low Energy. Normal use does not require a cloud service.
+
+The distribution is `ihcctl`; the Python import namespace remains
+`zehnder_ihc`; the CLI command is `ihcctl`.
+
+## Install
+
+For the CLI, prefer pipx:
+
+```bash
+pipx install ihcctl
+ihcctl --help
+```
+
+Alternatively install into a Python environment:
+
+```bash
+python -m pip install ihcctl
+```
+
+The first public release, `ihcctl` 0.2.0, is prepared but not yet published.
+Until public publication and verification, these are the intended future
+commands rather than a current PyPI installation path.
+
+## Python library and CLI
+
+Use `import zehnder_ihc` or import public classes directly:
+
+```python
+from zehnder_ihc import IHCClient
+```
+
+The CLI requires a Bluetooth address and an externally stored identity file.
+Do not commit it or share it with Home Assistant.
+
+```bash
+ihcctl --help
+ihcctl register --help
+```
+
+Registration requires physical IHC confirmation. The help commands do not
+contact hardware. Do not keep the CLI connected while Home Assistant polls the
+same controller.
+
+## Home Assistant
+
+The custom integration uses the same `zehnder_ihc` library internally. During
+this preparation phase its `manifest.json` deliberately retains the existing
+local direct-wheel requirement; it has not switched to `ihcctl`.
+
+Only after a verified public PyPI release will a separately authorized change
+pin it to `ihcctl==0.2.0`. Do not manually install, uninstall, or remove
+packages in a Home Assistant container.
+
+The optional Schedule Manager resource is:
+
+```yaml
+url: /zehnder_ihc/frontend/zehnder-ihc-schedule-card.js
+type: module
+```
+
+## Development / fallback workflow
+
+`tools/start-local-pypi.sh` and local pypiserver remain development/fallback
+tools. They are not the normal workflow for new CLI users or the intended
+production Home Assistant workflow after public PyPI migration. Existing Home
+Assistant deployments still need the current local wheel until the later
+manifest migration succeeds.
+
+For repository work, use the existing test extra:
+
+```bash
+python -m venv .venv
+source .venv/bin/activate
+python -m pip install -e ".[test]"
+python -m pytest -q
+```
+
+Tests use sanitized frames and fake BLE backends; they do not contact IHC
+hardware or perform writes.
+
+## Publishing
+
+Maintainers must read [the publishing guide](docs/publishing-pypi.md). Local
+readiness never publishes:
+
+```bash
+tools/release-pypi.sh --check
+```
+
+TestPyPI and production PyPI require separate explicit authorization.
+
+## Safety
+
+Phase-1 research is frozen. Never commit client identities, `ihc-client*.json`,
+or files under `phase1-private/`. Hardware-changing tests need explicit
+approval and protocol-level readback where possible.

ihcctl-0.2.0/pyproject.toml

@@ -0,0 +1,23 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "ihcctl"
+version = "0.2.0"
+description = "Python library and CLI for local Zehnder IHC control"
+readme = "README.md"
+requires-python = ">=3.11"
+dependencies = ["bleak>=0.22"]
+
+[project.scripts]
+ihcctl = "zehnder_ihc.cli:main"
+
+[project.optional-dependencies]
+test = ["pytest>=8"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+
+[tool.setuptools.packages.find]
+where = ["src"]

ihcctl-0.2.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

ihcctl-0.2.0/src/ihcctl.egg-info/PKG-INFO

@@ -0,0 +1,110 @@
+Metadata-Version: 2.4
+Name: ihcctl
+Version: 0.2.0
+Summary: Python library and CLI for local Zehnder IHC control
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+Requires-Dist: bleak>=0.22
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+
+# ihcctl
+
+`ihcctl` is a Python library and CLI for local Zehnder IHC controller control
+over Bluetooth Low Energy. Normal use does not require a cloud service.
+
+The distribution is `ihcctl`; the Python import namespace remains
+`zehnder_ihc`; the CLI command is `ihcctl`.
+
+## Install
+
+For the CLI, prefer pipx:
+
+```bash
+pipx install ihcctl
+ihcctl --help
+```
+
+Alternatively install into a Python environment:
+
+```bash
+python -m pip install ihcctl
+```
+
+The first public release, `ihcctl` 0.2.0, is prepared but not yet published.
+Until public publication and verification, these are the intended future
+commands rather than a current PyPI installation path.
+
+## Python library and CLI
+
+Use `import zehnder_ihc` or import public classes directly:
+
+```python
+from zehnder_ihc import IHCClient
+```
+
+The CLI requires a Bluetooth address and an externally stored identity file.
+Do not commit it or share it with Home Assistant.
+
+```bash
+ihcctl --help
+ihcctl register --help
+```
+
+Registration requires physical IHC confirmation. The help commands do not
+contact hardware. Do not keep the CLI connected while Home Assistant polls the
+same controller.
+
+## Home Assistant
+
+The custom integration uses the same `zehnder_ihc` library internally. During
+this preparation phase its `manifest.json` deliberately retains the existing
+local direct-wheel requirement; it has not switched to `ihcctl`.
+
+Only after a verified public PyPI release will a separately authorized change
+pin it to `ihcctl==0.2.0`. Do not manually install, uninstall, or remove
+packages in a Home Assistant container.
+
+The optional Schedule Manager resource is:
+
+```yaml
+url: /zehnder_ihc/frontend/zehnder-ihc-schedule-card.js
+type: module
+```
+
+## Development / fallback workflow
+
+`tools/start-local-pypi.sh` and local pypiserver remain development/fallback
+tools. They are not the normal workflow for new CLI users or the intended
+production Home Assistant workflow after public PyPI migration. Existing Home
+Assistant deployments still need the current local wheel until the later
+manifest migration succeeds.
+
+For repository work, use the existing test extra:
+
+```bash
+python -m venv .venv
+source .venv/bin/activate
+python -m pip install -e ".[test]"
+python -m pytest -q
+```
+
+Tests use sanitized frames and fake BLE backends; they do not contact IHC
+hardware or perform writes.
+
+## Publishing
+
+Maintainers must read [the publishing guide](docs/publishing-pypi.md). Local
+readiness never publishes:
+
+```bash
+tools/release-pypi.sh --check
+```
+
+TestPyPI and production PyPI require separate explicit authorization.
+
+## Safety
+
+Phase-1 research is frozen. Never commit client identities, `ihc-client*.json`,
+or files under `phase1-private/`. Hardware-changing tests need explicit
+approval and protocol-level readback where possible.

ihcctl-0.2.0/src/ihcctl.egg-info/SOURCES.txt

@@ -0,0 +1,54 @@
+README.md
+pyproject.toml
+src/ihcctl.egg-info/PKG-INFO
+src/ihcctl.egg-info/SOURCES.txt
+src/ihcctl.egg-info/dependency_links.txt
+src/ihcctl.egg-info/entry_points.txt
+src/ihcctl.egg-info/requires.txt
+src/ihcctl.egg-info/top_level.txt
+src/zehnder_ihc/__init__.py
+src/zehnder_ihc/backup.py
+src/zehnder_ihc/bleak_backend.py
+src/zehnder_ihc/cli.py
+src/zehnder_ihc/client.py
+src/zehnder_ihc/errors.py
+src/zehnder_ihc/framing.py
+src/zehnder_ihc/identity.py
+src/zehnder_ihc/models.py
+src/zehnder_ihc/mutations.py
+src/zehnder_ihc/protocol.py
+src/zehnder_ihc/restore.py
+src/zehnder_ihc/transport.py
+tests/test_active_weekplan.py
+tests/test_bleak_backend.py
+tests/test_cli.py
+tests/test_client.py
+tests/test_dayplan_delete.py
+tests/test_framing.py
+tests/test_home_assistant_active_weekplan_select.py
+tests/test_home_assistant_boost.py
+tests/test_home_assistant_frontend_static.py
+tests/test_home_assistant_layout.py
+tests/test_home_assistant_schedule.py
+tests/test_home_assistant_schedule_backup_restore.py
+tests/test_home_assistant_structured_backend.py
+tests/test_home_assistant_values.py
+tests/test_identity.py
+tests/test_modes.py
+tests/test_package.py
+tests/test_protocol.py
+tests/test_quick_heating.py
+tests/test_release_helper.py
+tests/test_restore_executor.py
+tests/test_restore_planner.py
+tests/test_schedule_backup.py
+tests/test_schedule_backup_snapshot.py
+tests/test_schedule_client.py
+tests/test_schedule_lists.py
+tests/test_schedule_models.py
+tests/test_schedule_mutation_contract.py
+tests/test_schedule_protocol.py
+tests/test_status.py
+tests/test_task10a_hardware_tool.py
+tests/test_transport.py
+tests/test_weekplan_delete.py

ihcctl-0.2.0/src/ihcctl.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

ihcctl-0.2.0/src/ihcctl.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+ihcctl = zehnder_ihc.cli:main

ihcctl-0.2.0/src/ihcctl.egg-info/requires.txt

@@ -0,0 +1,4 @@
+bleak>=0.22
+
+[test]
+pytest>=8

ihcctl-0.2.0/src/ihcctl.egg-info/top_level.txt

@@ -0,0 +1 @@
+zehnder_ihc

ihcctl-0.2.0/src/zehnder_ihc/__init__.py

@@ -0,0 +1,66 @@
+"""Public Zehnder IHC client API."""
+
+from .bleak_backend import BleakBackend
+from .backup import BackupDayplanV1, BackupSourceDeviceV1, BackupWeekplanV1, ScheduleBackupV1
+from .client import IHCClient
+from .errors import (
+    ActivePlanDeletionError,
+    AmbiguousPlanNameError,
+    BackupDeviceMismatchError,
+    BackupValidationError,
+    IndeterminateRegistrationError,
+    PlanNotFoundError,
+    PlanReferencedError,
+)
+from .identity import Identity
+from .models import (
+    Dayplan,
+    DayplanQuickHeating,
+    DayplanTransition,
+    OperatingMode,
+    ScheduleInventory,
+    ScheduleState,
+    Status,
+    Weekday,
+    Weekplan,
+)
+from .restore import (
+    ScheduleRestoreActionKindV1,
+    ScheduleRestoreActionV1,
+    ScheduleRestoreExecutionStepV1,
+    ScheduleRestoreMappingV1,
+    ScheduleRestorePlanV1,
+)
+from .transport import BLETransport
+
+__all__ = [
+    "BLETransport",
+    "BleakBackend",
+    "ActivePlanDeletionError",
+    "AmbiguousPlanNameError",
+    "BackupDayplanV1",
+    "BackupDeviceMismatchError",
+    "BackupSourceDeviceV1",
+    "BackupValidationError",
+    "BackupWeekplanV1",
+    "Dayplan",
+    "DayplanQuickHeating",
+    "DayplanTransition",
+    "IHCClient",
+    "Identity",
+    "IndeterminateRegistrationError",
+    "OperatingMode",
+    "PlanNotFoundError",
+    "PlanReferencedError",
+    "ScheduleInventory",
+    "ScheduleBackupV1",
+    "ScheduleRestoreActionKindV1",
+    "ScheduleRestoreActionV1",
+    "ScheduleRestoreExecutionStepV1",
+    "ScheduleRestoreMappingV1",
+    "ScheduleRestorePlanV1",
+    "ScheduleState",
+    "Status",
+    "Weekday",
+    "Weekplan",
+]