aiosolarfocus 0.1.0__tar.gz

aiosolarfocus-0.1.0/.gitignore

@@ -0,0 +1,13 @@
+__pycache__/
+*.py[cod]
+.venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.coverage
+htmlcov/
+coverage.xml
+.DS_Store

aiosolarfocus-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

aiosolarfocus-0.1.0/NOTICE

@@ -0,0 +1,13 @@
+aiosolarfocus
+Copyright 2026 Jeroen Laverman
+
+Portions of this work are derived from pysolarfocus
+(https://github.com/lavermanjj/pysolarfocus), Copyright Jeroen Laverman,
+licensed under the Apache License, Version 2.0. In particular the Modbus
+register map, the component base addressing, and the recorded behaviour of the
+Solarfocus eco manager-touch controller originate there.
+
+This product is not affiliated with, endorsed by, or supported by
+Solarfocus GmbH. "Solarfocus", "eco manager-touch", "vampair", "therminator",
+"ecotop", "octoplus" and "Pellet Elegance" are trademarks of their respective
+owners.

aiosolarfocus-0.1.0/PKG-INFO

@@ -0,0 +1,180 @@
+Metadata-Version: 2.5
+Name: aiosolarfocus
+Version: 0.1.0
+Summary: Async Python client for Solarfocus eco manager-touch heating systems
+Project-URL: Homepage, https://github.com/lavermanjj/aiosolarfocus
+Project-URL: Repository, https://github.com/lavermanjj/aiosolarfocus
+Project-URL: Issues, https://github.com/lavermanjj/aiosolarfocus/issues
+Author-email: Jeroen Laverman <jjlaverman@web.de>
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: asyncio,heat pump,heating,home assistant,modbus,solarfocus
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: AsyncIO
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Home Automation
+Classifier: Typing :: Typed
+Requires-Python: >=3.13
+Requires-Dist: pymodbus<4,>=3.10
+Description-Content-Type: text/markdown
+
+# aiosolarfocus
+
+Async Python client for [Solarfocus](https://www.solarfocus.com) **eco<sup>manager-touch</sup>**
+heating systems, over Modbus TCP.
+
+> [!WARNING]
+> Unofficial, and developed without support from Solarfocus. Writing to a
+> heating system can damage the system or the building. Check with Solarfocus or
+> your installer before changing anything you do not understand.
+
+## Install
+
+```sh
+pip install aiosolarfocus
+```
+
+## Read
+
+```python
+import asyncio
+
+from aiosolarfocus import ApiVersion, SolarfocusClient, SolarfocusConfig, Systems
+
+
+async def main() -> None:
+    config = SolarfocusConfig(
+        host="10.0.0.5",
+        system=Systems.VAMPAIR,
+        api_version=ApiVersion.V_26_020,
+        heating_circuits=1,
+        buffers=1,
+        boilers=1,
+    )
+    async with SolarfocusClient(config) as client:
+        result = await client.update()
+
+        print(client.heat_pump.supply_temperature)  # float | None
+        print(client.heating_circuits[0].mode)  # HeatingCircuitMode | None
+        print(client.heat_pump.cop_heating)  # float | None
+
+        if not result.ok:
+            print("not read:", *result.failed)
+
+
+asyncio.run(main())
+```
+
+Reading a value is not asynchronous — it is the last reading, already decoded.
+Only the calls that talk to the controller are awaited.
+
+`None` means one of three things, and callers almost always want the same
+behaviour for all of them: this firmware or system does not have the register,
+it has not been read yet or its last read failed, or the channel is reporting
+one of the values an open sensor gives instead of a measurement.
+`component.raw()` and `component.info()` tell them apart.
+
+Values the library works out from registers — the heat pump's coefficients of
+performance, its seasonal figures — are declared beside the registers they come
+from, so `component.available_values()` offers them alongside everything else
+and `component.info()` describes them. An idle heat pump reports `None` for a
+coefficient of performance rather than zero.
+
+## Write
+
+```python
+from aiosolarfocus import HeatingCircuitMode
+
+await client.heating_circuits[0].set_mode(HeatingCircuitMode.AUTOMATIC)
+await client.heating_circuits[0].set_target_supply_temperature(45.0)
+await client.photovoltaic.set_smart_meter(-1500)  # the library does the two's complement
+
+# Registers the controller wants written together go out together.
+await client.heating_circuits[0].set_operating_state(
+    mode=HeatingCircuitMode.AUTOMATIC,
+    target_supply_temperature=18.0,
+)
+```
+
+A successful write updates the component's own cache, so the new value is
+readable straight away without re-reading anything.
+
+## Errors
+
+`update()` raises only when the connection itself is the problem, because that
+is the one failure that says nothing about any particular component. Everything
+else — a range this firmware refuses, a controller answering an exception — is
+attributed to the components whose registers were in that read:
+
+```python
+try:
+    result = await client.update()
+except SolarfocusConnectionError:
+    ...  # the whole controller is unreachable
+for key, error in result.failed.items():
+    ...  # just these components went quiet
+```
+
+## Without asyncio
+
+```python
+from aiosolarfocus import SolarfocusConfig, SolarfocusSync
+
+with SolarfocusSync(SolarfocusConfig(host="10.0.0.5")) as sync:
+    sync.update()
+    print(sync.client.heat_pump.supply_temperature)
+```
+
+## Command line
+
+```sh
+python -m aiosolarfocus detect    --host 10.0.0.5 --evidence
+python -m aiosolarfocus dump      --host 10.0.0.5
+python -m aiosolarfocus watch     --host 10.0.0.5 --interval 10   # prints only what changed
+python -m aiosolarfocus set       --host 10.0.0.5 heating_circuits.1.mode automatic
+
+python -m aiosolarfocus registers --system Vampair --api-version 26.020   # no controller needed
+python -m aiosolarfocus plan      --system Vampair --api-version 26.020   # no controller needed
+```
+
+## Supported
+
+Systems: vampair, therminator, ecotop, Pellet Elegance, octoplus.
+Firmware: 20.110 through 26.020. Give the version the controller prints on its
+own screen; a newer one clamps to the newest this library knows.
+
+Only the vampair has been tested against real hardware. The other four are
+reasoned from the register specification — a
+[register dump](CONTRIBUTING.md#producing-a-register-dump) from one of them is
+the most useful thing you can contribute.
+
+## Documentation
+
+- [`docs/registers.md`](docs/registers.md) — the register map, generated from the tables.
+- [`docs/protocol.md`](docs/protocol.md) — how the controller actually behaves, including the ways it misbehaves.
+- [`docs/porting-from-pysolarfocus.md`](docs/porting-from-pysolarfocus.md) — coming from the synchronous library.
+
+## Testing against it
+
+`aiosolarfocus.testing` ships in the wheel, so a downstream test suite can drive
+a real client against a fake controller that reproduces the real one's
+behaviour — including refusing unmapped addresses and compacting reads that span
+a gap.
+
+```python
+from aiosolarfocus.testing import FakeController
+
+config = SolarfocusConfig(host="test")
+client = SolarfocusClient(config, transport=FakeController.for_config(config))
+```
+
+## About
+
+Successor to [pysolarfocus](https://github.com/lavermanjj/pysolarfocus),
+rewritten async-native with the register map as validated data. Portions of this
+work derive from that project; see [`NOTICE`](NOTICE).
+
+Not affiliated with, endorsed by, or supported by Solarfocus GmbH.

aiosolarfocus-0.1.0/README.md

@@ -0,0 +1,157 @@
+# aiosolarfocus
+
+Async Python client for [Solarfocus](https://www.solarfocus.com) **eco<sup>manager-touch</sup>**
+heating systems, over Modbus TCP.
+
+> [!WARNING]
+> Unofficial, and developed without support from Solarfocus. Writing to a
+> heating system can damage the system or the building. Check with Solarfocus or
+> your installer before changing anything you do not understand.
+
+## Install
+
+```sh
+pip install aiosolarfocus
+```
+
+## Read
+
+```python
+import asyncio
+
+from aiosolarfocus import ApiVersion, SolarfocusClient, SolarfocusConfig, Systems
+
+
+async def main() -> None:
+    config = SolarfocusConfig(
+        host="10.0.0.5",
+        system=Systems.VAMPAIR,
+        api_version=ApiVersion.V_26_020,
+        heating_circuits=1,
+        buffers=1,
+        boilers=1,
+    )
+    async with SolarfocusClient(config) as client:
+        result = await client.update()
+
+        print(client.heat_pump.supply_temperature)  # float | None
+        print(client.heating_circuits[0].mode)  # HeatingCircuitMode | None
+        print(client.heat_pump.cop_heating)  # float | None
+
+        if not result.ok:
+            print("not read:", *result.failed)
+
+
+asyncio.run(main())
+```
+
+Reading a value is not asynchronous — it is the last reading, already decoded.
+Only the calls that talk to the controller are awaited.
+
+`None` means one of three things, and callers almost always want the same
+behaviour for all of them: this firmware or system does not have the register,
+it has not been read yet or its last read failed, or the channel is reporting
+one of the values an open sensor gives instead of a measurement.
+`component.raw()` and `component.info()` tell them apart.
+
+Values the library works out from registers — the heat pump's coefficients of
+performance, its seasonal figures — are declared beside the registers they come
+from, so `component.available_values()` offers them alongside everything else
+and `component.info()` describes them. An idle heat pump reports `None` for a
+coefficient of performance rather than zero.
+
+## Write
+
+```python
+from aiosolarfocus import HeatingCircuitMode
+
+await client.heating_circuits[0].set_mode(HeatingCircuitMode.AUTOMATIC)
+await client.heating_circuits[0].set_target_supply_temperature(45.0)
+await client.photovoltaic.set_smart_meter(-1500)  # the library does the two's complement
+
+# Registers the controller wants written together go out together.
+await client.heating_circuits[0].set_operating_state(
+    mode=HeatingCircuitMode.AUTOMATIC,
+    target_supply_temperature=18.0,
+)
+```
+
+A successful write updates the component's own cache, so the new value is
+readable straight away without re-reading anything.
+
+## Errors
+
+`update()` raises only when the connection itself is the problem, because that
+is the one failure that says nothing about any particular component. Everything
+else — a range this firmware refuses, a controller answering an exception — is
+attributed to the components whose registers were in that read:
+
+```python
+try:
+    result = await client.update()
+except SolarfocusConnectionError:
+    ...  # the whole controller is unreachable
+for key, error in result.failed.items():
+    ...  # just these components went quiet
+```
+
+## Without asyncio
+
+```python
+from aiosolarfocus import SolarfocusConfig, SolarfocusSync
+
+with SolarfocusSync(SolarfocusConfig(host="10.0.0.5")) as sync:
+    sync.update()
+    print(sync.client.heat_pump.supply_temperature)
+```
+
+## Command line
+
+```sh
+python -m aiosolarfocus detect    --host 10.0.0.5 --evidence
+python -m aiosolarfocus dump      --host 10.0.0.5
+python -m aiosolarfocus watch     --host 10.0.0.5 --interval 10   # prints only what changed
+python -m aiosolarfocus set       --host 10.0.0.5 heating_circuits.1.mode automatic
+
+python -m aiosolarfocus registers --system Vampair --api-version 26.020   # no controller needed
+python -m aiosolarfocus plan      --system Vampair --api-version 26.020   # no controller needed
+```
+
+## Supported
+
+Systems: vampair, therminator, ecotop, Pellet Elegance, octoplus.
+Firmware: 20.110 through 26.020. Give the version the controller prints on its
+own screen; a newer one clamps to the newest this library knows.
+
+Only the vampair has been tested against real hardware. The other four are
+reasoned from the register specification — a
+[register dump](CONTRIBUTING.md#producing-a-register-dump) from one of them is
+the most useful thing you can contribute.
+
+## Documentation
+
+- [`docs/registers.md`](docs/registers.md) — the register map, generated from the tables.
+- [`docs/protocol.md`](docs/protocol.md) — how the controller actually behaves, including the ways it misbehaves.
+- [`docs/porting-from-pysolarfocus.md`](docs/porting-from-pysolarfocus.md) — coming from the synchronous library.
+
+## Testing against it
+
+`aiosolarfocus.testing` ships in the wheel, so a downstream test suite can drive
+a real client against a fake controller that reproduces the real one's
+behaviour — including refusing unmapped addresses and compacting reads that span
+a gap.
+
+```python
+from aiosolarfocus.testing import FakeController
+
+config = SolarfocusConfig(host="test")
+client = SolarfocusClient(config, transport=FakeController.for_config(config))
+```
+
+## About
+
+Successor to [pysolarfocus](https://github.com/lavermanjj/pysolarfocus),
+rewritten async-native with the register map as validated data. Portions of this
+work derive from that project; see [`NOTICE`](NOTICE).
+
+Not affiliated with, endorsed by, or supported by Solarfocus GmbH.

aiosolarfocus-0.1.0/docs/porting-from-pysolarfocus.md

@@ -0,0 +1,118 @@
+# Porting from pysolarfocus
+
+`aiosolarfocus` is not a drop-in replacement. The value API is deliberately
+different; this is what maps to what.
+
+## Reading
+
+| pysolarfocus | aiosolarfocus |
+|---|---|
+| `api.heating_circuits[0].supply_temperature.scaled_value` | `client.heating_circuits[0].supply_temperature` |
+| `api.heatpump` | `client.heat_pump` |
+| `api.biomassboiler` | `client.biomass_boiler` |
+| `getattr(component, key).scaled_value` | `component.value_of(Register)` or plain attribute access |
+| `getattr(component, key).value` | `component.raw(Register)` |
+| `{n: p.scaled_value for n, p in vars(component).items() if isinstance(p, Part)}` | `component.snapshot()` or `client.snapshot()` |
+| `api.update()` → `bool` | `await client.update()` → `UpdateResult`, raising on connection failure |
+| `api.update_heating()` | `await client.update(components=[ComponentId.HEATING_CIRCUITS])` |
+| `api.is_connected` | `client.connected` |
+| `api.api_version.greater_or_equal("22.090")` | `config.api_version >= ApiVersion.V_22_090` |
+| `heatpump.performance_overall` | `heat_pump.seasonal_performance` |
+| `heatpump.performance_overall_heating` | `heat_pump.seasonal_performance_heating` |
+| `heatpump.performance_overall_drinking_water` | `heat_pump.seasonal_performance_drinking_water` |
+
+The heat pump's derived figures kept their meaning and changed their names: a
+"performance overall" that is a seasonal figure reads better as one. They are
+rounded to two decimals — `pysolarfocus` reported `3.7369392844083906`.
+
+They are still first-class. In `pysolarfocus` they were `PerformanceCalculator`
+objects, indistinguishable from registers to anything reading the component;
+here they are declared with `@derived` beside the registers they are worked out
+from, and they appear in `component.available_values()`, `component.info()`,
+`component.supports()`, `component.snapshot()` and the command line's
+`registers` and `dump` output.
+
+**Build entities from `available_values()`, not `available_registers()`.** The
+latter is registers only, and would drop all five coefficients of performance —
+which the Home Assistant integration has a sensor for apiece.
+
+## Writing
+
+```python
+# pysolarfocus
+value = api.heating_circuits[0].mode
+value.set_unscaled_value(HeatingCircuitMode.AUTOMATIC)
+value.commit()
+component.update()  # to see the change
+
+# aiosolarfocus
+await client.heating_circuits[0].set_mode(HeatingCircuitMode.AUTOMATIC)
+```
+
+The re-read is gone: a successful write updates the component's own cache, so
+the value is readable immediately.
+
+`SolarfocusAPI.set_heating_circuit_mode(index, mode)` and its siblings have no
+equivalent, because the integration that was meant to use them never called one.
+The setters live on the component.
+
+## What the library now does that the caller used to
+
+- **Two's complement.** `await pv.set_smart_meter(-1500)` puts `0xFA24` on the
+  wire. The caller no longer needs to know the register is signed.
+- **Version and system gating.** `component.available_registers()` is exactly
+  what this controller has, so a consumer need not carry a
+  `min_required_version` and an `unsupported_systems` list per entity.
+- **Bounds, step and unit.** `component.info(Register)` reports them, instead of
+  each consumer copying them out of the register document.
+- **Sentinel readings.** An open sensor channel decodes to `None` rather than
+  130.0 °C.
+- **Rounding.** A reading is rounded to the precision its scale carries.
+  `304 * 0.1` is `30.400000000000002` in binary floating point, and the old
+  library passed that through for Home Assistant to record.
+
+## Semantic changes to watch for
+
+- **Scaling runs one direction only**: engineering value = raw × scale.
+  `pysolarfocus` multiplied for input registers and divided for holding ones.
+  Values agree; the declaration does not.
+- **`None` is a real answer.** It means the register is absent on this firmware
+  or system, has not been read, or is reporting an open channel. `raw()` and
+  `info()` tell those apart.
+- **Errors raise.** `SolarfocusConnectionError` for the connection;
+  everything else lands in `UpdateResult.failed`, per component.
+- **Enumerations decode to `IntEnum` members** for closed sets like `mode`, and
+  stay `int` for open ones like `state`, where firmware keeps adding codes.
+
+## Bugs fixed rather than carried over
+
+- The fresh water module cascade and the circulation module were never built by
+  `ComponentManager`, so `update_fresh_water_module_cascade()` raised
+  `AttributeError` on every controller running 23.040 or newer.
+- `TherminatorHeatingCircuit.__init__` dropped `api_version`, so those systems
+  resolved every register against a default version — which on 21.140 declared
+  `heating_mode` at 32608, a register that firmware does not have, and so
+  shifted the three registers before it (see `protocol.md`).
+- `PerformanceCalculator` returned `0.0` when the denominator was zero, so an
+  idle heat pump reported a coefficient of performance of zero all night. Now
+  `None`.
+- A single failing read failed a whole component; and a failing instance of a
+  multi-instance component hid the ones after it.
+- Negative writes were the caller's problem.
+- **Registers belonging to one system were read on all of them.** `2409`
+  (Kesselbetriebsart, therminator), `2411` (Speichertemperatur oben, octoplus),
+  `2412` (Stückholz, therminator) and buffer `1902` (X35, therminator) were read
+  on systems the document does not give them to. A Pellet Elegance maps neither
+  `2409` nor `2413`, so the boiler read spanned them and came back compacted:
+  the return flow temperature reported 270.0 °C where the sensor said 22.1 °C,
+  and the buffer's pump reported the status register. See
+  home-assistant-solarfocus issue #217. A test now holds every register against
+  the system the document names in its own description.
+
+## Deliberately *not* changed
+
+`TherminatorBuffer` never read the external X44/X36/X35 holding registers. That
+looked like the same class of bug, but the Home Assistant integration
+independently marks those three entities `unsupported_systems=[THERMINATOR,
+ECOTOP]`. Two sources agreeing was enough to carry the behaviour over rather
+than "fix" it against hardware nobody could test. See `Buffer._external`.