Skip to main content

zwave-js-server-python

Python library for communicating with zwave-js-server. Goal for this library is to replicate the structure and the events of Z-Wave JS 1:1. So it has a Driver, Controller and Node classes.

Setup development environment

To setup your development environment, run scripts/setup, which will install all requirements and set up pre-commit checks.

Trying it out

python3 -m zwave_js_server ws://localhost:3000

Or get the version of the server

python3 -m zwave_js_server ws://localhost:3000 --server-version

Or dump the state. Optionally add --event-timeout 5 if you want to listen 5 seconds extra for events.

python3 -m zwave_js_server ws://localhost:3000 --dump-state

Sending commands

try:
    result = await client.async_send_command({ "command": "start_listening" })
except zwave_js_server.client.FailedCommand as err:
    print("Command failed with", err.error_code)

Access control

Schema 48 adds typed access-control helpers exposed via the AccessControlAPI wrapper:

  • node.access_control: shortcut for the root endpoint API.
  • endpoint.access_control: API for a specific endpoint.
  • Call await endpoint.access_control.is_supported() before using other methods.
  • Credential payloads accept str | bytes; binary credentials are converted to the websocket Buffer transport shape internally.

Endpoint groups

Schema 51 exposes the endpoint groups defined in a device's config file. They semantically group the endpoints of a device, like the individual clamps of a multi-clamp energy meter:

  • node.endpoint_groups: dict of EndpointGroup by group ID, empty if the device config defines none.
  • EndpointGroup.endpoints: the endpoints of the group that exist on the node. EndpointGroup.endpoint_indices also contains indices the node does not have.
  • EndpointGroup.is_main_device: whether the group represents the device as a whole.
  • endpoint.endpoint_group / node.get_endpoint_group(index): the group an endpoint belongs to, or None if it is ungrouped.

Metadata

Release files for zwave-js-server-python 0.75.0

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

Source distribution (sdist)

Source distribution for zwave-js-server-python 0.75.0
File Size Uploaded Provenance Actions
zwave_js_server_python-0.75.0.tar.gz 96.0 kB With provenance Details for zwave_js_server_python-0.75.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for zwave-js-server-python 0.75.0
File Interpreter ABI Platform Actions
zwave_js_server_python-0.75.0-py3-none-any.whl Python 3 none any Details for zwave_js_server_python-0.75.0-py3-none-any.whl

Total release size: 217.2 kB

Release files / zwave_js_server_python-0.75.0.tar.gz

Download URL zwave_js_server_python-0.75.0.tar.gz
Size 96.0 kB
Tags Source
SHA-256 checksum
How to use checksums
99e898770410f41c24caca3079b58b249075e53d9baf54cd72c0c657cdda31c5
BLAKE2b-256 checksum
How to use checksums
3bd60373ad45912eca7fd6b6fd35d755b5b7312edefdd6614e00544132cd82d7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Release files / zwave_js_server_python-0.75.0-py3-none-any.whl

Download URL zwave_js_server_python-0.75.0-py3-none-any.whl
Size 121.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b91dcfdc0e4c71b8d686bef065fae1cb225dfb63b82b2d8de364e23cb53c66d0
BLAKE2b-256 checksum
How to use checksums
d75dc7e6b1d431ffd63b24e7a7c5ab2ddd16c05768f15baf0f32eae19ce5b86a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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

Transparency log

Security for zwave-js-server-python 0.75.0

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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for zwave_js_server_python-0.75.0.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 Nov 12, 2026.

Transparency log

A 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.

Release history Release notifications | RSS feed

This release

0.75.0 This release

2 release files Full provenance

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