This release is a pre-release and may not be stable for production use.
vizaio-conjure
Developer-friendly VIZIO Conjure URL launching built on the upstream
vizaio SmartCast client.
Milestone 1
The first milestone serves a LAN-reachable HTML page and launches it through
the established Conjure launcher configuration: app 17, namespace 4.
uv sync --extra dev
just serve
From another terminal, set a paired token without putting it in the command line or repository:
$env:VIZAIO_AUTH = "..."
uv run vizaio-conjure launch http://HOST:8765/ --host TV_HOST:7345
Pairing and saved devices
The pairing PIN is used only for the short-lived TV pairing challenge. It is
never written to disk. The resulting auth token is stored through Python's
keyring library, using the operating
system credential store, while the local profile file contains only the TV
host and pairing identity.
Pair a TV interactively:
uv run vizaio-conjure discover
uv run vizaio-conjure pair TV_HOST:7345 --name living-room
uv run vizaio-conjure devices list
uv run vizaio-conjure devices test living-room
uv run vizaio-conjure launch http://HOST:8765/ --device living-room
Discovery uses the upstream SSDP and optional Zeroconf adapters. It may not cross a routed network boundary, so explicit hostnames and IP addresses remain supported. Install the optional discovery dependency for Zeroconf results:
uv tool install "vizaio-conjure[discovery]"
Use devices remove NAME to delete both the profile metadata and its keyring
credential. Pairing uses a stable, installation-specific device identity so it
does not reuse a generic identity belonging to another integration.
For a no-device validation:
uv run vizaio-conjure launch http://example.test/ --dry-run
Namespace ergonomics
The known Conjure namespace is available as VizioNamespace.CONJURE, while
raw integer namespaces remain supported for future firmware or undocumented
applications:
from vizaio_conjure import ConjureTarget, VizioNamespace
ConjureTarget("http://host:8765/", name_space=VizioNamespace.CONJURE)
ConjureTarget("http://host:8765/", name_space="CONJURE")
ConjureTarget("http://host:8765/", name_space=9)
This project deliberately does not implement the internal app-3001 route or privileged Conjure surfaces.
Development and release
Run uv sync --extra dev followed by just check. The CI workflow tests
Python 3.12, 3.13, and 3.14, publishes coverage and JUnit artifacts, runs
Ruff and Pyrefly as separate quality checks, and builds distributions before a
merge is considered ready. Tagged releases create GitHub release artifacts;
PyPI publication remains disabled until Trusted Publishing is configured.
See docs/releasing.md for the release checklist.
Metadata
Release files for vizaio-conjure 0.1.0rc1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| vizaio_conjure-0.1.0rc1.tar.gz | 104.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vizaio_conjure-0.1.0rc1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 116.3 kB
Release files / vizaio_conjure-0.1.0rc1.tar.gz
| Download URL | vizaio_conjure-0.1.0rc1.tar.gz |
|---|---|
| Size | 104.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f231d2a48a6b0364f100ee7543c7769de61b60b6e50710069f8426f9fab577c
|
|
BLAKE2b-256 checksum How to use checksums |
73db2073a078a0c4cc9bb467f0fe4ff20bfbb7bd61e63cb7ccdd32fac8c01b79
|
| 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 21, 2026.
Transparency logRelease files / vizaio_conjure-0.1.0rc1-py3-none-any.whl
| Download URL | vizaio_conjure-0.1.0rc1-py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
02b3ae346ee6d63e72b66ad5359b441663d8386526c287e4249a46dc0ad2c955
|
|
BLAKE2b-256 checksum How to use checksums |
9c4e91ce153eb2e936869ebb51566fca309dbaa5496332a7c7c60f7c8d44e6c9
|
| 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 21, 2026.
Transparency logSecurity for vizaio-conjure 0.1.0rc1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for vizaio_conjure-0.1.0rc1.tar.gz
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 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.