python-izone 1.3.9__tar.gz → 1.3.11__tar.gz

{python_izone-1.3.9 → python_izone-1.3.11}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: python-izone
-Version: 1.3.9
+Version: 1.3.11
 Summary: A python interface to the iZone airconditioner controller
 Project-URL: Homepage, https://github.com/Swamp-Ig/pizone
 Author-email: Penny Wood <pypl@ninjateaparty.com>
@@ -15,7 +15,7 @@ Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Home Automation
 Classifier: Topic :: System :: Hardware
 Requires-Python: >=3.14
-Requires-Dist: aiohttp>=3.14.1
+Requires-Dist: aiohttp>=3.14.3
 Requires-Dist: ifaddr>=0.2.0
 Provides-Extra: test
 Requires-Dist: pytest-aio; extra == 'test'

python_izone-1.3.11/docs/release-notes/v1.3.10.md

@@ -0,0 +1,15 @@
+# Release notes — v1.3.10
+
+**Compare range:** https://github.com/Swamp-Ig/pizone/compare/v1.3.9...v1.3.10
+
+## Since v1.3.9
+
+### Control setpoint (new)
+
+- `Controller.control_setpoint_owner` — the controller, the matching zone, or `None` for who owns the unit target. RAS mode, master with CtrlZone past the configured zone count, or a missing AUTO CTS selects the controller. CONST/OPCL `Temp:0` does not.
+- `Controller.control_setpoint` — that owner's setpoint (°C)
+
+### Fixes / hardening
+
+- Drop the `Connection: close` / `force_close` HTTP keepalive workaround (core#176536)
+- Require `aiohttp>=3.14.3` for CVE-2026-69244

python_izone-1.3.11/docs/release-notes/v1.3.11.md

@@ -0,0 +1,21 @@
+# Release notes — v1.3.11
+
+**Compare range:** https://github.com/Swamp-Ig/pizone/compare/v1.3.10...v1.3.11
+
+## Since v1.3.10
+
+### API v2 (new)
+
+- Prefer the bridge's V2 API for reads when it returns useful data, and send writes through `iZoneCommandV2`. V2 data is normalized into the same V1-shaped caches, so the public API is unchanged (#35)
+- Confirm V2 zone mode changes by reading them back, within fixed time limits, and yield between polling reads so queued commands are not held up by a full zone sweep. See [V2 zone mode confirmation](../v2-confirmation.md)
+- Keep the zone setpoint when selecting AUTO mode over V2
+- Validate V2 zone snapshots, and keep a zero airflow value instead of dropping it
+- Correct the V2 sensor and fan enums against the vendor header
+- Free Air: try the V2 `iSaveOn` command first and fall back to the V1 `FreeAir` endpoint if the bridge rejects it, remembering the result per controller
+- Free Air status is now read from `iSaveEnable`/`iSaveOn`. Before, V2 bridges always reported it as off
+
+### Fixes / hardening
+
+- Allow controllers with no zones (unit-only systems). A negative zone count is still treated as a fault (#33, #34)
+- Put a time limit on closing the discovery UDP transport. If the socket is not released within 1 s, abort it instead of hanging shutdown (Windows Proactor) (#41, #42)
+- Document that setting a sleep timer can turn the unit on with some bridges

python_izone-1.3.11/docs/v2-confirmation.md

@@ -0,0 +1,71 @@
+# V2 zone mode confirmation
+
+This proposal changes only the native V2 path, not the legacy polling pathway
+or V1 writes. It does not promise faster mechanical damper movement.
+
+## Contract
+
+- Mode selection returns after the existing command transport acknowledges it.
+- A controller-owned worker first attempts readback after 250 ms, subject to
+  the existing serialized transport and a shared two-second read-start limit.
+- Multiple selections of one zone replace the earlier pending expectation.
+  Commands remain ordered and are not dropped or resent by confirmation.
+- A fresh contradictory mode is masked for at most six seconds after ACK.
+  Afterwards the observed mode is published, while tracking continues for at
+  most 30 seconds. Other fields, including temperatures, remain observed data.
+- Normal polling can satisfy a pending confirmation. It no longer holds the
+  command lock across the entire system/zone sweep; requests are still serial.
+- A confirmation deadline includes time waiting for the lock and doing I/O.
+  Expiry logs an unconfirmed selection but does not by itself mark the bridge
+  offline. A real ConnectionError retains the existing disconnected/scan path.
+- Controller close or discovery shutdown cancels owned confirmation work.
+
+Explicit setpoint, fan, system-power and airflow commands retain their existing
+confirmation behaviour. The existing AUTO-mode-only contribution is needed for
+AUTO to take this fast path; otherwise the parent branch encodes AUTO as a
+setpoint write. These changes should be reviewed together before release.
+
+## Type=7 bulk-read assessment
+
+The official [API header v1.41](https://developer.izone.com.au/downloads/iZone_JSON_datastrings.h)
+documents request Type=7 as system status. A separate local adapter on one
+V2-only bridge has successfully read `iZoneStatusV2.Zones` with that request.
+This is a documented endpoint with single-installation read evidence, not a
+guarantee of support across all firmware. The native branch currently has
+Type=1/2 fixtures. Type=7 carries dynamic zone fields but does not replace
+the full Type=2 metadata, such as zone names and types.
+
+This PR therefore does not silently switch polling to Type=7. A later bulk-read
+implementation should have all of the following acceptance cases:
+
+1. Explicit capability detection, with bounded Type=2 fallback for unsupported
+   or incomplete responses; no parallel request storm.
+2. Expected bridge identity, unique zone indices and complete zone coverage.
+3. No merging of a partial failed bulk response with an unrelated fallback read.
+4. Defined refresh/invalidation of names, types and any other cached metadata,
+   including changed zone counts, endpoint replacement and controller reload.
+5. Tests for rapid commands, stale in-flight snapshots and bounded confirmation
+   that preserve the newest acknowledged selection.
+6. Hardware validation on both a V2-only and a dual-stack bridge, plus unchanged
+   V1 regressions. A complete native-branch hardware test remains outstanding.
+
+The lower-risk immediate improvement is command interleaving between Type=2
+reads plus bounded read-only confirmation. It needs no new firmware assumption.
+
+## Documentation boundaries
+
+The [zone reference](https://developer.izone.com.au/docs/reference/zone/)
+defines mode selection separately from setpoint updates, supporting the
+mode-only AUTO contribution. Neither this page nor the Postman examples
+specifies a guaranteed acknowledgement or mechanical damper latency. The
+confirmation timings above remain measured/tested implementation choices.
+
+The [cloud event service](https://developer.izone.com.au/docs/getting-started/cloud/event/)
+is a separate vendor-arranged service, not a documented local WebSocket API
+that this library can enable for instant zone updates. Existing local UDP
+change notifications should not be confused with cloud event subscriptions.
+
+The [discovery guide](https://developer.izone.com.au/docs/getting-started/local/discovery/)
+says V2 devices retain V1 support, but issue #35 and the tested V2-only bridge
+contradict that assumption. Keep usable-response probing and actual V2 writes;
+an HTTP 200 response with an empty V1 body is not proof of V1 compatibility.