Skip to main content

Stewart Filmscreen Python Library

Async Stewart Filmscreen CVM client for long-running integrations (Home Assistant primary target).

Status

This is a clean implementation focused on reliability, explicit typing, and deterministic parsing.

Protocol reference used:

Design boundary:

  • This library owns protocol parsing, transport behavior, reconnect behavior, and safe command pacing.
  • Integrations built on top of it should focus on product-specific entity mapping and UX, not duplicate queueing or protocol safety rules.

Installation

pip install stewart-filmscreen

Quick Start

import asyncio

from stewart_filmscreen.client import StewartFilmscreenClient


async def main() -> None:
    client = StewartFilmscreenClient(
        host="192.168.1.50",
        username="your_username",
        password="your_password",
    )

    try:
        await client.start()
        await client.wait_authenticated(timeout=10)

        await client.move_down("1.1.1.MOTOR")
        await client.stop("1.1.1.MOTOR")
        await client.recall_preset(3)
    finally:
        await client.stop_client()


asyncio.run(main())

By default, commands are paced with a conservative 1.0s inter-command delay because some CVM controllers become unreliable when requests are sent too rapidly. Override command_throttle_seconds only if you have verified your controller tolerates a lower value.

Preset commands are validated against the documented CVM slot range of 1-24.

Development

uv sync --group dev
uv run ruff check .
uv run ruff format --check .
uv run ty check stewart_filmscreen
uv run pytest -v

Real Device Integration Tests (Read-Only)

The test suite includes a manual, read-only integration tier for validating behavior against a real CVM.

  • Marker: integration_real
  • Opt-in gate: STEWART_ITEST=1
  • Target host: STEWART_HOST=<ip-or-hostname>
  • Optional port override: STEWART_PORT=23
  • Credentials: STEWART_USERNAME, STEWART_PASSWORD
  • Optional metadata: STEWART_MAC
  • If the device is offline/unreachable, tests are skipped.

Set up local env:

cp .env.example .env

Run the real-device tests:

set -a && source .env && set +a && uv run pytest -v -m integration_real

Release files for stewart-filmscreen 0.1.3

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

Source distribution (sdist)

Source distribution for stewart-filmscreen 0.1.3
File Size Uploaded
stewart_filmscreen-0.1.3.tar.gz 23.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for stewart-filmscreen 0.1.3
File Interpreter ABI Platform
stewart_filmscreen-0.1.3-py3-none-any.whl Python 3 none any Details

Total release size: 32.2 kB

Release files / stewart_filmscreen-0.1.3.tar.gz

Download URL stewart_filmscreen-0.1.3.tar.gz
Size 23.0 kB
Tags Source
SHA-256 checksum
How to use checksums
759e3ddab536cd6ab4bccc92fe9df6d232de01923dc5d0e9fde716a1a41d1020
BLAKE2b-256 checksum
How to use checksums
435a490ff554fbc01ad7e21edf82feb15f14fd35c45ae5f75f9f8f763853fb22
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Apr 12, 2026.

Transparency log

Release files / stewart_filmscreen-0.1.3-py3-none-any.whl

Download URL stewart_filmscreen-0.1.3-py3-none-any.whl
Size 9.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9a78e2cd3708dfe7aa28093b86c4fe6a5cc4b6dea03627e1825e047c42c82ee0
BLAKE2b-256 checksum
How to use checksums
dbf76c9a4995755ece02ae45a8b73f0a4ac8497678dddedaed27314f0084f6f5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Apr 12, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.3 This release

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

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