crestron-nvx
An unofficial async Python client for direct local communication with Crestron DM NVX AV-over-IP endpoints.
API provenance
This library implements Crestron's publicly documented DM NVX REST API. The authoritative external references are Crestron's public:
Those references describe the API's HTTPS authentication, GET/POST methods, object paths, property types, and model-specific applicability. This repository does not copy or redistribute Crestron manuals, schemas, examples, firmware, or other proprietary material. The external documentation and device behaviour may change, and continued compatibility is not guaranteed.
See API_PROVENANCE.md for the project's source and fixture policy.
Status
Version 0.2 remains deliberately read-only. It authenticates over HTTPS and reads device identity, device-specific state, A/V I/O status, receive streams, and transmit streams. An allow-listed read method also supports safe exploration of documented objects such as Preview.
await client.async_get_preview_info() detects optional preview capability.
await client.async_get_preview() returns NvxPreviewImage (JPEG bytes and
dimensions), or raises NvxPreviewUnavailable when no local image is available.
Other failures use existing typed API exceptions. Unsupported/string-valued
objects are normal on old firmware. No firmware cutoff is assumed.
Only same-origin JPEG paths without redirects are accepted. Responses are limited to 2 MiB and bounded dimensions, with one authentication retry. Client operations are serialized to protect the session. Images are not persisted or logged. Preview display and updates have been validated through Home Assistant on a firmware 7.1 DM-NVX-360, including remote iOS viewing. Other models and physical outage/restart recovery remain to be validated.
No reboot, routing, input, mode, stream, or configuration write can be issued by this release.
The declared initial support scope is:
| Model | Firmware 6.0 | Firmware 7.1 |
|---|---|---|
| DM-NVX-350 | Supported; validation pending | Supported; hardware validated |
| DM-NVX-360 | Supported; validation pending | Supported; hardware validated |
| DM-NVX-E30 | Supported; hardware validated | Supported; validation pending |
The parser detects capabilities from returned objects and fields. It does not reject other firmware versions, but versions outside this table are currently best-effort.
A DM-NVX-350 on 1.3707.00028 also passed authentication and API-shape probing;
its string-valued Preview response is treated as unsupported. HA and lifecycle
testing on this firmware remain pending.
Installation
Install the package from PyPI:
python -m pip install crestron-nvx
For development:
python -m pip install --editable '.[test]'
Usage
from aiohttp import ClientSession
from crestron_nvx import NvxClient
async with ClientSession() as session:
client = NvxClient(
session,
"192.0.2.10",
"username",
"password",
verify_ssl=False,
)
snapshot = await client.async_get_snapshot()
print(snapshot.device.model)
verify_ssl=False accepts an endpoint without authenticating its certificate.
This is often necessary for factory/self-signed DM NVX certificates, but an
on-path device could then impersonate the endpoint and receive its credentials.
Use that mode only on a trusted, isolated local network. Prefer
verify_ssl=True whenever the endpoint certificate is trusted by the client
host. Never log credentials, authentication cookies, raw device responses, or
personally identifying endpoint data.
Development
Install the test dependencies and run:
ruff format --check .
ruff check .
mypy
pytest --cov=crestron_nvx --cov-report=term-missing
python -m build
twine check dist/*
Tests use small, invented fixtures that describe only the fields required to exercise library behaviour. Raw device responses must not be committed.
Licence
Copyright © 2026 Daniel Wilson (@Danw33)
Licensed under the Apache License, Version 2.0. See LICENSE and NOTICE. The licence covers this project's code and documentation; it does not grant rights to third-party trademarks, firmware, documentation, or other materials.
Crestron and DM NVX are trademarks of their respective owners.
Release files for crestron-nvx 0.2.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 | |
|---|---|---|---|
| crestron_nvx-0.2.0.tar.gz | 26.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| crestron_nvx-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.1 kB
Release files / crestron_nvx-0.2.0.tar.gz
| Download URL | crestron_nvx-0.2.0.tar.gz |
|---|---|
| Size | 26.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c98fbccf60344646e6983866f8e6f949336025c9fc935b46cb4b0f9f90c43401
|
|
BLAKE2b-256 checksum How to use checksums |
90726876089255d274019aa5f6d27f4187d360a58196abcf3897e48622dae4e3
|
| 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 Sep 24, 2026.
Transparency logRelease files / crestron_nvx-0.2.0-py3-none-any.whl
| Download URL | crestron_nvx-0.2.0-py3-none-any.whl |
|---|---|
| Size | 17.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
578e02f133c9bfce57b261645965c900a2ee73b2f7ab82bd807b1dc69f697d9a
|
|
BLAKE2b-256 checksum How to use checksums |
d523f6ea9be3f0f0a0d113a5a053aab79a576bb715dcd05bc411c0d72cadd99b
|
| 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 Sep 24, 2026.
Transparency log