span-panel-api-schema-0
The flat-schema parser for span-panel-api: the single-device Homie model published by SPAN firmware r202603 through r202627, which carries no data-model-version.
Why this is a separate distribution
span-panel-api is a transport and a dispatcher. It knows how to connect to a panel's MQTT broker, route messages, and choose a parser — but it contains no parsing code and no Homie type strings. Each wire format ships as its own distribution and
registers itself under the span_panel_api.schema_adapters entry-point group.
That split exists because the two halves break on different axes. The wire format changes when SPAN ships firmware; the library API changes when we do. Separate distributions let each carry its own version, so a consumer can pin them independently and add support for a new panel schema by installing a package rather than by upgrading the transport.
Installation
pip install "span-panel-api[schema-0]"
Installing this package is what makes flat-schema panels work. span-panel-api on its own will connect and then raise SpanPanelAdapterMissingError naming the adapter it could not find.
A consumer that wants to support panels on either schema installs both adapters:
pip install "span-panel-api[schema-0,schema-1]"
Dispatch happens at runtime, per panel, from the data-model-version the panel reports. The extras are the recommended spelling because they give pip install -U a correct upgrade path — the dependency arrow runs from adapter to bootstrap, so upgrading
the bootstrap alone would otherwise leave a stale adapter wheel that discovery then rejects, with pip reporting success. Naming the distributions directly works too.
Retirement
SPAN retires the flat schema in the same release that introduces the parent/child model (r202633, fleet rollout projected for early September 2026). When the fleet has moved, consumers drop this package from their requirements. Published versions stay on
PyPI for anyone still running older firmware.
Release files for span-panel-api-schema-0 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| span_panel_api_schema_0-1.0.0.tar.gz | 19.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| span_panel_api_schema_0-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.9 kB
Release files / span_panel_api_schema_0-1.0.0.tar.gz
| Download URL | span_panel_api_schema_0-1.0.0.tar.gz |
|---|---|
| Size | 19.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b95b82ab28f77300e57a3ae94c5e53c2fb7d54b6558c787f181b8ae5bb0f5177
|
|
BLAKE2b-256 checksum How to use checksums |
f0e73230840726cff409f64e895a589ad84ce681552f5218c8403fe50a0a2d54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.
Transparency logRelease files / span_panel_api_schema_0-1.0.0-py3-none-any.whl
| Download URL | span_panel_api_schema_0-1.0.0-py3-none-any.whl |
|---|---|
| Size | 20.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ebe34bebf880ee3a2f96192735854a5acb79b6e2bb93432a5ab64c8a37ffb50d
|
|
BLAKE2b-256 checksum How to use checksums |
847cc9dce5cac874571e040c8f4459121cf1a812da102264997e518bc336959a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.
Transparency log