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 ofEndpointGroupby group ID, empty if the device config defines none.EndpointGroup.endpoints: the endpoints of the group that exist on the node.EndpointGroup.endpoint_indicesalso 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, orNoneif it is ungrouped.
1 maintainer
Metadata
1 maintainer
Release files for zwave-js-server-python 0.74.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 | |
|---|---|---|---|
| zwave_js_server_python-0.74.0.tar.gz | 95.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zwave_js_server_python-0.74.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 215.6 kB
Release files / zwave_js_server_python-0.74.0.tar.gz
| Download URL | zwave_js_server_python-0.74.0.tar.gz |
|---|---|
| Size | 95.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
243160a2bfd4fce45458e73e26ad171a179e67b311b812fca303322eca4d4229
|
|
BLAKE2b-256 checksum How to use checksums |
12549346ccae90f61ebbefba1c0ce138e78776275a72c314d7ee6a92d157013c
|
| 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 30, 2026.
Transparency logRelease files / zwave_js_server_python-0.74.0-py3-none-any.whl
| Download URL | zwave_js_server_python-0.74.0-py3-none-any.whl |
|---|---|
| Size | 120.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab195dbc47cadca46e351ff29685093de8a4d753574535cf0b2404005517b2e7
|
|
BLAKE2b-256 checksum How to use checksums |
0a01e3d570f255fa8cd602ea186e7dffd053e718e5900ba2099eea692bdd49b4
|
| 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 30, 2026.
Transparency log
