kaco-serial 0.1.0__tar.gz

kaco_serial-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,30 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions: {}
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv sync --frozen --python ${{ matrix.python-version }}
+      - name: Lint
+        run: uv run ruff check .
+      - name: Format
+        run: uv run ruff format --check .
+      - name: Types
+        run: uv run mypy src/ tests/
+      - name: Tests
+        run: uv run pytest

kaco_serial-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,55 @@
+name: Release Please
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: "Tag to publish to PyPI. Leave empty to run release-please only."
+        required: false
+        type: string
+
+permissions: {}
+
+concurrency:
+  group: release
+  cancel-in-progress: false
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    permissions:
+      contents: write
+      pull-requests: write
+    outputs:
+      release_created: ${{ steps.release.outputs.release_created }}
+      tag_name: ${{ steps.release.outputs.tag_name }}
+    steps:
+      - uses: googleapis/release-please-action@v4
+        id: release
+        with:
+          config-file: release-please-config.json
+          manifest-file: .release-please-manifest.json
+
+  publish:
+    needs: release-please
+    if: needs.release-please.outputs.release_created == 'true' || inputs.tag != ''
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    permissions:
+      # Trusted publishing matches on this workflow's filename, so this file
+      # must stay release.yml — it is what the PyPI publisher is registered
+      # against.
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ inputs.tag || needs.release-please.outputs.tag_name }}
+      - uses: astral-sh/setup-uv@v5
+      - run: uv build
+      - uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          verbose: true
+          skip-existing: true

kaco_serial-0.1.0/.gitignore

@@ -0,0 +1,10 @@
+__pycache__/
+*.pyc
+.venv/
+dist/
+.pytest_cache/
+.ruff_cache/
+.idea/
+
+# Raw captures from a live installation — contain yield, uptime and serials
+private/

kaco_serial-0.1.0/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.1.0"
+}

kaco_serial-0.1.0/CHANGELOG.md

@@ -0,0 +1,26 @@
+# Changelog
+
+## 0.1.0 (2026-08-25)
+
+
+### Features
+
+* accept third-party captures as test fixtures ([e7c9ea8](https://github.com/g4bri3lDev/kaco-rs485/commit/e7c9ea8aceb3eff0bbfd2ed3df35b0fe90713785))
+* bus discovery instead of hardcoded addresses ([95ac5d1](https://github.com/g4bri3lDev/kaco-rs485/commit/95ac5d1f288641ee3101313662decac1c4b5bdc4))
+* fold in findings from the vendor firmware analysis ([e1c782a](https://github.com/g4bri3lDev/kaco-rs485/commit/e1c782ac9091267a160641327a5b214e4cc12140))
+* KACO xi RS485 library with URL-addressed transport ([ab6e9f5](https://github.com/g4bri3lDev/kaco-rs485/commit/ab6e9f5d3fa6c7705e93b349c19390742a1ca27f))
+* status code table with the two field-observed codes ([7c5efe4](https://github.com/g4bri3lDev/kaco-rs485/commit/7c5efe4d106f66f96eb2cd1b5dffcdb1563b736b))
+
+
+### Bug fixes
+
+* an empty listen is not evidence of a fault ([b7a5112](https://github.com/g4bri3lDev/kaco-rs485/commit/b7a51124939e692e06d10df4ddad2cf04afa543e))
+* connection loss must not kill a long-running poll ([54ff92f](https://github.com/g4bri3lDev/kaco-rs485/commit/54ff92f9769a53942e26ea993bc23a390eb89bcc))
+* narrow two types the checker could not follow ([7706eef](https://github.com/g4bri3lDev/kaco-rs485/commit/7706eef5b993a86e433719fe09e430d675a279de))
+* pace scan and sweep, they were polling back to back ([eb6bc7f](https://github.com/g4bri3lDev/kaco-rs485/commit/eb6bc7f50e579f16e9f021d51a7d5c28f871cb48))
+* remove installation-specific assumptions; instrument timings ([1296848](https://github.com/g4bri3lDev/kaco-rs485/commit/129684876d49d9700edc5dca1177095b248b5bff))
+
+
+### Performance
+
+* only pay the bus-settle gap after an address replies ([d2b008e](https://github.com/g4bri3lDev/kaco-rs485/commit/d2b008ee81765e976a2ee5f2472d368d140fc239))

kaco_serial-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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.

kaco_serial-0.1.0/PKG-INFO

@@ -0,0 +1,149 @@
+Metadata-Version: 2.5
+Name: kaco-serial
+Version: 0.1.0
+Summary: Read KACO Powador xi-series inverters over RS485, locally or via an ESPHome serial proxy.
+Project-URL: Homepage, https://github.com/g4bri3lDev/kaco-rs485
+Author-email: g4bri3lDev <admin@g4bri3l.de>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: esphome,home-assistant,kaco,powador,rs485,solar
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Home Automation
+Requires-Python: >=3.13
+Requires-Dist: serialx<2,>=1.8.2
+Provides-Extra: cli
+Requires-Dist: serialx[esphome]<2,>=1.8.2; extra == 'cli'
+Description-Content-Type: text/markdown
+
+# kaco-rs485
+
+Read KACO Powador **xi-series** inverters (6400xi, 8000xi, and relatives) over
+RS485 — from a local adapter, or across the network through an
+[ESPHome serial proxy](https://esphome.io/components/serial_proxy/).
+
+Companion to [`kaco-modbus`](https://github.com/g4bri3lDev/kaco-modbus), which
+covers the newer blueplanet units over SunSpec Modbus TCP. Different protocol,
+different hardware generation, same fleet.
+
+## Install
+
+```bash
+uv add kaco-serial         # library
+uv add 'kaco-serial[cli]'  # + the diagnostic CLI and ESPHome transport
+```
+
+## The bus is addressed by URL
+
+There is one transport, and it takes an opaque URL. serialx resolves the
+scheme, so nothing in this library knows or cares how the bytes get there:
+
+| URL | Where |
+|---|---|
+| `/dev/tty.usbserial-0001` | local RS485 adapter |
+| `esphome://host:6053/?port_name=RS-485` | ESPHome proxy, standalone |
+| `esphome-hass://esphome/<entry_id>?port_name=RS-485` | ESPHome proxy, inside Home Assistant |
+| `socket://host:port` | any ser2net-style bridge |
+
+The `esphome-hass` scheme is registered by Home Assistant and resolves the
+ESPHome integration's already-authenticated client — which is why the Home
+Assistant integration built on this library stores no host and no API key.
+
+## Library
+
+```python
+from kaco_rs485 import AsyncBus, KacoRs485Client
+from kaco_rs485.discovery import scan
+
+async with AsyncBus("esphome://proxy.local:6053/?port_name=RS-485") as bus:
+    found = await scan(bus)
+    client = KacoRs485Client(bus, [d.address for d in found.supported])
+    states = await client.poll_cycle()
+    for address, state in states.items():
+        print(address, state.measured.ac_power_w)
+```
+
+`KacoRs485Client` owns the pacing. Don't drive `AsyncBus` from two tasks at
+once — RS485 is a shared medium and interleaved requests garble each other.
+
+## Bringing up a bus
+
+Four CLI modes, in the order you actually need them:
+
+```bash
+# 1. Is anything there, and are A/B the right way round?
+#    Transmits nothing — safe while another master is still connected.
+kaco-rs485 --url <url> listen --seconds 30
+
+# 2. Which addresses are occupied, and what is at them?
+#    Probes all 32 addresses; a silent one costs ~2.5s.
+kaco-rs485 --url <url> scan
+
+# 3. Everything one address can tell you.
+kaco-rs485 --url <url> sweep --addresses 2 -v
+
+# 4. Does it keep working? Scans first if you omit --addresses.
+kaco-rs485 --url <url> poll
+```
+
+When nothing answers, the CLI prints a diagnostic checklist rather than just a
+timeout. **Only one master may drive an RS485 bus** — power down any other
+polling device before blaming the wiring.
+
+## Protocol notes
+
+The parsers were validated against bytes captured from a live installation,
+and they deliberately tolerate several places where real hardware diverges
+from the KACO specification:
+
+- Command `3` replies on xi units **omit** the `*<adr>3 ` header the spec
+  shows. Both shapes are accepted.
+- Command `3` total yield is in **kWh** on xi units, **Wh** on the blueplanet.
+  `total_yield_raw` is exposed unscaled; the caller decides.
+- Command `s` (serial number) is **unsupported** on xi units — they return
+  nothing. Use command `9` for identification.
+- The command `0` checksum byte may be **any** value 0-255, including CR and
+  LF. This is why framing is length-gated instead of scanning for a
+  terminator, and why readline-style parsing cannot work here.
+- xi units pause **>250 ms mid-frame**, between the checksum byte and the
+  trailing type string. Frames legitimately end anywhere from 58 to 65 bytes;
+  the type string is decorative.
+- Replies start **1-2 seconds** after the request.
+- Status codes **4 (feeding in)** and **6 (standby)** are observed in the
+  field but absent from the specification's table.
+
+`tests/reference/` holds real frames from a live bus. The framing tests replay
+them split at every possible byte boundary, because through a network proxy the
+arrival chunking is arbitrary.
+
+## Contributing a capture
+
+This library is developed against Powador **6400xi** and **8000xi** units. Other
+KACO hardware very likely works, or would with a small change, but that cannot
+be confirmed without bytes from someone who owns it. A capture from your
+installation is the single most useful contribution.
+
+```bash
+kaco-rs485 --url <url> --log-dir captures sweep
+```
+
+Open a pull request adding the resulting `.json` to `tests/reference/`. It is
+picked up automatically — every parser and framing test will run against it, so
+a file that breaks nothing is evidence your hardware is supported, and a file
+that breaks something is a bug report with a reproduction attached.
+
+Especially wanted:
+
+- **Other xi-series units** (2500xi, 3600xi, 4200xi, 5000xi…). Expected to use
+  the same series-"00" frames; confirmation is cheap and valuable.
+- **Series "000xi"** park inverters. These answer with command byte `4` instead
+  of `0` and need a parser that does not exist yet.
+- **blueplanet / TL / TR units**, which speak CRC16 Generic Protocol
+  (command byte `n`). A whole second protocol; captures are the prerequisite
+  for deciding whether to implement it here.
+
+**Before you open the PR, look at what is in the file.** A capture contains
+your total yield, operating hours, and — if command `s` answered — the
+inverter's serial number. None of it is dangerous, but total yield and uptime
+do describe the size and age of your installation, so it is your call. Deleting
+the `8`/`9`/`s` entries and keeping only `0` and `3` still makes a useful
+fixture.

kaco_serial-0.1.0/README.md

@@ -0,0 +1,132 @@
+# kaco-rs485
+
+Read KACO Powador **xi-series** inverters (6400xi, 8000xi, and relatives) over
+RS485 — from a local adapter, or across the network through an
+[ESPHome serial proxy](https://esphome.io/components/serial_proxy/).
+
+Companion to [`kaco-modbus`](https://github.com/g4bri3lDev/kaco-modbus), which
+covers the newer blueplanet units over SunSpec Modbus TCP. Different protocol,
+different hardware generation, same fleet.
+
+## Install
+
+```bash
+uv add kaco-serial         # library
+uv add 'kaco-serial[cli]'  # + the diagnostic CLI and ESPHome transport
+```
+
+## The bus is addressed by URL
+
+There is one transport, and it takes an opaque URL. serialx resolves the
+scheme, so nothing in this library knows or cares how the bytes get there:
+
+| URL | Where |
+|---|---|
+| `/dev/tty.usbserial-0001` | local RS485 adapter |
+| `esphome://host:6053/?port_name=RS-485` | ESPHome proxy, standalone |
+| `esphome-hass://esphome/<entry_id>?port_name=RS-485` | ESPHome proxy, inside Home Assistant |
+| `socket://host:port` | any ser2net-style bridge |
+
+The `esphome-hass` scheme is registered by Home Assistant and resolves the
+ESPHome integration's already-authenticated client — which is why the Home
+Assistant integration built on this library stores no host and no API key.
+
+## Library
+
+```python
+from kaco_rs485 import AsyncBus, KacoRs485Client
+from kaco_rs485.discovery import scan
+
+async with AsyncBus("esphome://proxy.local:6053/?port_name=RS-485") as bus:
+    found = await scan(bus)
+    client = KacoRs485Client(bus, [d.address for d in found.supported])
+    states = await client.poll_cycle()
+    for address, state in states.items():
+        print(address, state.measured.ac_power_w)
+```
+
+`KacoRs485Client` owns the pacing. Don't drive `AsyncBus` from two tasks at
+once — RS485 is a shared medium and interleaved requests garble each other.
+
+## Bringing up a bus
+
+Four CLI modes, in the order you actually need them:
+
+```bash
+# 1. Is anything there, and are A/B the right way round?
+#    Transmits nothing — safe while another master is still connected.
+kaco-rs485 --url <url> listen --seconds 30
+
+# 2. Which addresses are occupied, and what is at them?
+#    Probes all 32 addresses; a silent one costs ~2.5s.
+kaco-rs485 --url <url> scan
+
+# 3. Everything one address can tell you.
+kaco-rs485 --url <url> sweep --addresses 2 -v
+
+# 4. Does it keep working? Scans first if you omit --addresses.
+kaco-rs485 --url <url> poll
+```
+
+When nothing answers, the CLI prints a diagnostic checklist rather than just a
+timeout. **Only one master may drive an RS485 bus** — power down any other
+polling device before blaming the wiring.
+
+## Protocol notes
+
+The parsers were validated against bytes captured from a live installation,
+and they deliberately tolerate several places where real hardware diverges
+from the KACO specification:
+
+- Command `3` replies on xi units **omit** the `*<adr>3 ` header the spec
+  shows. Both shapes are accepted.
+- Command `3` total yield is in **kWh** on xi units, **Wh** on the blueplanet.
+  `total_yield_raw` is exposed unscaled; the caller decides.
+- Command `s` (serial number) is **unsupported** on xi units — they return
+  nothing. Use command `9` for identification.
+- The command `0` checksum byte may be **any** value 0-255, including CR and
+  LF. This is why framing is length-gated instead of scanning for a
+  terminator, and why readline-style parsing cannot work here.
+- xi units pause **>250 ms mid-frame**, between the checksum byte and the
+  trailing type string. Frames legitimately end anywhere from 58 to 65 bytes;
+  the type string is decorative.
+- Replies start **1-2 seconds** after the request.
+- Status codes **4 (feeding in)** and **6 (standby)** are observed in the
+  field but absent from the specification's table.
+
+`tests/reference/` holds real frames from a live bus. The framing tests replay
+them split at every possible byte boundary, because through a network proxy the
+arrival chunking is arbitrary.
+
+## Contributing a capture
+
+This library is developed against Powador **6400xi** and **8000xi** units. Other
+KACO hardware very likely works, or would with a small change, but that cannot
+be confirmed without bytes from someone who owns it. A capture from your
+installation is the single most useful contribution.
+
+```bash
+kaco-rs485 --url <url> --log-dir captures sweep
+```
+
+Open a pull request adding the resulting `.json` to `tests/reference/`. It is
+picked up automatically — every parser and framing test will run against it, so
+a file that breaks nothing is evidence your hardware is supported, and a file
+that breaks something is a bug report with a reproduction attached.
+
+Especially wanted:
+
+- **Other xi-series units** (2500xi, 3600xi, 4200xi, 5000xi…). Expected to use
+  the same series-"00" frames; confirmation is cheap and valuable.
+- **Series "000xi"** park inverters. These answer with command byte `4` instead
+  of `0` and need a parser that does not exist yet.
+- **blueplanet / TL / TR units**, which speak CRC16 Generic Protocol
+  (command byte `n`). A whole second protocol; captures are the prerequisite
+  for deciding whether to implement it here.
+
+**Before you open the PR, look at what is in the file.** A capture contains
+your total yield, operating hours, and — if command `s` answered — the
+inverter's serial number. None of it is dangerous, but total yield and uptime
+do describe the size and age of your installation, so it is your call. Deleting
+the `8`/`9`/`s` entries and keeping only `0` and `3` still makes a useful
+fixture.

kaco_serial-0.1.0/pyproject.toml

@@ -0,0 +1,52 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "kaco-serial"
+dynamic = ["version"]
+description = "Read KACO Powador xi-series inverters over RS485, locally or via an ESPHome serial proxy."
+readme = "README.md"
+requires-python = ">=3.13"
+license = "Apache-2.0"
+authors = [{ name = "g4bri3lDev", email = "admin@g4bri3l.de" }]
+keywords = ["rs485", "kaco", "powador", "solar", "home-assistant", "esphome"]
+classifiers = [
+    "Programming Language :: Python :: 3",
+    "Topic :: Home Automation",
+]
+# serialx replaces pyserial and gives us every transport for free: local
+# devices, socket://, and ESPHome serial proxies. Core pins 1.8.2.
+dependencies = ["serialx>=1.8.2,<2"]
+
+[project.optional-dependencies]
+# Only the standalone CLI needs this — inside Home Assistant, the `esphome`
+# integration already provides aioesphomeapi and registers the URI handler.
+cli = ["serialx[esphome]>=1.8.2,<2"]
+
+[project.scripts]
+kaco-rs485 = "kaco_rs485.cli:main"
+
+[project.urls]
+Homepage = "https://github.com/g4bri3lDev/kaco-rs485"
+
+[dependency-groups]
+dev = [
+    "pytest>=8",
+    "pytest-asyncio>=0.24",
+    "mypy>=1.14",
+    "ruff>=0.8",
+]
+
+[tool.hatch.version]
+path = "src/kaco_rs485/__init__.py"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/kaco_rs485"]
+
+[tool.pytest.ini_options]
+asyncio_mode = "auto"
+testpaths = ["tests"]
+
+[tool.ruff]
+line-length = 100