Files

Raman Gupta 82ebb7047f Bump zwave-js-server-python to 0.35.0 (#66785 )

* Bump zwave-js-server-python to 0.35.0

* Remove support for new event type which should go in a separate PR

2022-02-18 02:36:27 -05:00

docs

…

translations

[ci skip] Translation update

2022-02-12 00:16:37 +00:00

triggers

…

__init__.py

Add button entity to ping zwave_js node (#66129 )

2022-02-14 15:38:22 -05:00

addon.py

…

api.py

Add inclusion state to zwave_js/network_status WS API cmd (#65398 )

2022-02-17 11:38:20 +01:00

binary_sensor.py

…

button.py

Add button entity to ping zwave_js node (#66129 )

2022-02-14 15:38:22 -05:00

climate.py

…

config_flow.py

…

const.py

…

cover.py

…

device_action.py

Improve zwave_js device automation strings for config parameters (#66428 )

2022-02-14 15:14:02 -05:00

device_automation_helpers.py

Improve zwave_js device automation strings for config parameters (#66428 )

2022-02-14 15:14:02 -05:00

device_condition.py

Fix zwave_js device condition bug (#66626 )

2022-02-15 23:05:12 -05:00

device_trigger.py

Improve zwave_js device automation strings for config parameters (#66428 )

2022-02-14 15:14:02 -05:00

diagnostics.py

Bump zwave-js-server-python to 0.35.0 (#66785 )

2022-02-18 02:36:27 -05:00

discovery_data_template.py

…

discovery.py

…

entity.py

Simplify get_unique_id helper function for zwave_js (#66221 )

2022-02-10 08:46:32 +01:00

fan.py

…

helpers.py

Add button entity to ping zwave_js node (#66129 )

2022-02-14 15:38:22 -05:00

light.py

…

lock.py

…

manifest.json

Bump zwave-js-server-python to 0.35.0 (#66785 )

2022-02-18 02:36:27 -05:00

migrate.py

Simplify get_unique_id helper function for zwave_js (#66221 )

2022-02-10 08:46:32 +01:00

number.py

…

README.md

…

select.py

…

sensor.py

Add button entity to ping zwave_js node (#66129 )

2022-02-14 15:38:22 -05:00

services.py

Add button entity to ping zwave_js node (#66129 )

2022-02-14 15:38:22 -05:00

services.yaml

…

siren.py

…

strings.json

…

switch.py

…

trigger.py

…

README.md

Z-Wave JS Architecture

This document describes the architecture of Z-Wave JS in Home Assistant and how the integration is connected all the way to the Z-Wave USB stick controller.

Architecture

Connection diagram

Z-Wave USB stick

Communicates with devices via the Z-Wave radio and stores device pairing.

Z-Wave JS

Represents the USB stick serial protocol as devices.

Z-Wave JS Server

Forward the state of Z-Wave JS over a WebSocket connection.

Z-Wave JS Server Python

Consumes the WebSocket connection and makes the Z-Wave JS state available in Python.

Z-Wave JS integration

Represents Z-Wave devices in Home Assistant and allows control.

Home Assistant

Best home automation platform in the world.

Running Z-Wave JS Server

Z-Wave JS Server can be run as a standalone Node app.

It can also run as part of Z-Wave JS 2 MQTT, which is also a standalone Node app.

Both apps are available as Home Assistant add-ons. There are also Docker containers etc.