History

GitHub Action f0c9f443d1 [ci skip] Translation update		2021-11-15 00:12:46 +00:00
..
docs	…
translations	[ci skip] Translation update	2021-11-15 00:12:46 +00:00
triggers	…
README.md	…
__init__.py	…
addon.py	…
api.py	…
binary_sensor.py	Add zwave_js binary sensor entity category (#58703 )	2021-11-09 18:26:34 +01:00
climate.py	…
config_flow.py	…
const.py	Allow dict as input to zwave_js.set_value service (#59370 )	2021-11-10 07:08:43 +01:00
cover.py	…
device_action.py	…
device_automation_helpers.py	…
device_condition.py	…
device_trigger.py	…
discovery.py	…
discovery_data_template.py	…
entity.py	…
fan.py	Always use a step size of 1 for z-wave js fans (#59622 )	2021-11-13 13:00:36 +01:00
helpers.py	…
light.py	…
lock.py	…
manifest.json	…
migrate.py	…
number.py	…
select.py	Add zwave_js select entity category (#59157 )	2021-11-05 10:31:51 -04:00
sensor.py	…
services.py	…
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.