Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

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.

Metadata

Release files for span-panel-api-schema-0 1.3.0b1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for span-panel-api-schema-0 1.3.0b1
File Size Uploaded
span_panel_api_schema_0-1.3.0b1.tar.gz 25.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for span-panel-api-schema-0 1.3.0b1
File Interpreter ABI Platform
span_panel_api_schema_0-1.3.0b1-py3-none-any.whl Python 3 none any Details

Total release size: 51.0 kB

Release files / span_panel_api_schema_0-1.3.0b1.tar.gz

Download URL span_panel_api_schema_0-1.3.0b1.tar.gz
Size 25.7 kB
Tags Source
SHA-256 checksum
How to use checksums
0acbffd7daf420beda060feda18aaea08a6af60ccf3a790cafbdabd5c93d4037
BLAKE2b-256 checksum
How to use checksums
60527b1bf1e1faf71ad9a986891a475a2a23fe2d96650ccee922a1bf25254edd
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 Oct 9, 2026.

Transparency log

Release files / span_panel_api_schema_0-1.3.0b1-py3-none-any.whl

Download URL span_panel_api_schema_0-1.3.0b1-py3-none-any.whl
Size 25.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8d8ba42e09a1f71f4f1cb0522828f37f91569dad4a963a6911524138553554b3
BLAKE2b-256 checksum
How to use checksums
acb414a08bdff6e6a0090ba1d37b6d359f89a5779a9ad2fead5092099b2b2dad
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 Oct 9, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page