Skip to main content

zwave-alarm-client

Async Python client (aiohttp) for the REST API of the Z-Wave Alarm service. Used by the Home Assistant integration; contains no Home Assistant code.

import aiohttp
from zwave_alarm_client import async_get_panel_state, async_stream_events, InvalidAuth, CannotConnect

async with aiohttp.ClientSession() as session:
    panel = await async_get_panel_state(session, "192.168.1.50", 3000, token)

    async for event in async_stream_events(session, "192.168.1.50", 3000, token):
        ...  # first event is a full `snapshot`, then `panel.changed`, `sensor.changed`, ...

Every call takes (session, host, port, token, ...); pass token=None to use a cookie session from async_login instead, and secure=True for https/wss.

Coverage

Area Calls
Auth async_login, async_logout
Panel async_get_panel_state, async_validate_connection, async_arm, async_disarm (zone-restricted guests return a panel with disarmedZoneIds)
Zones & sensors async_get_zones, async_create_zone, async_update_zone, async_delete_zone (force=), async_list_discoverable_sensors, async_assign_sensor, async_update_sensor, async_unassign_sensor
Users async_list_users (ha_person_id= filter), async_create_user (code optional; guest expiry / guest_zone_id, ha_person_id, ha_user_id), async_update_user, async_delete_user
Codes (write-only) async_set_user_code, async_clear_user_code; users expose only hasCode
Lockout policy async_get_lockout_policy, async_update_lockout_policy
Events async_get_events
HA links async_create_ha_link, async_delete_ha_link
Keypads async_list_keypads, async_chime_keypad
Push channel async_stream_events (sends keepalive pings, drops pongs; reconnect policy is the caller's)

Response shapes are available as TypedDicts in zwave_alarm_client.models.

Errors

All derive from ZwaveAlarmError: CannotConnect (unreachable, timeout, 5xx; ServiceUnavailable for 503), InvalidAuth (401), Forbidden (403), NotFound (404), BadRequest (400, message names the field), Conflict (409; CommandRejected for a lost arm/disarm race, ZoneNotEmpty, ZoneInUse, CodeInUse), AccountLocked (423), TooManyRequests (429, .retry_after).

Development

python -m venv .venv && . .venv/bin/activate
pip install -e '.[test]'
pytest

Commits follow Conventional Commits: fix releases a patch, feat a minor, BREAKING CHANGE/! a major. Releases are tagged and published to PyPI from main.

Metadata

Release files for zwave-alarm-client 0.4.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-alarm-client 0.4.0
File Size Uploaded
zwave_alarm_client-0.4.0.tar.gz 17.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for zwave-alarm-client 0.4.0
File Interpreter ABI Platform
zwave_alarm_client-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 29.6 kB

Release files / zwave_alarm_client-0.4.0.tar.gz

Download URL zwave_alarm_client-0.4.0.tar.gz
Size 17.5 kB
Tags Source
SHA-256 checksum
How to use checksums
071acb74482df68e11b7dfcc16782fd7e234badfb3d3f4e278d71f882d4dd5ea
BLAKE2b-256 checksum
How to use checksums
0881c07963fbc2d79b1a069942a35e28452fec00ee9f44676e75c50590eeb5b1
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 6, 2026.

Transparency log

Release files / zwave_alarm_client-0.4.0-py3-none-any.whl

Download URL zwave_alarm_client-0.4.0-py3-none-any.whl
Size 12.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a92322cd6ff75dcdfa3214ea767a3a410a88e541608c7f5cd01077e20aa14a1c
BLAKE2b-256 checksum
How to use checksums
5ce132cfc00a252d4732a3ff2b86c2a72e5d266fc733deb18b46feddf52431f3
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 6, 2026.

Transparency log

Release history Release notifications | RSS feed

0.4.1

2 release files

This release

0.4.0 This release

2 release files

0.3.0

2 release files

0.2.0

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