History

epenet 13f250319d Import websocket api constants from root (#78250 )		2022-09-12 22:07:58 -04:00
..
docs	…
translations	…
triggers	Rename zwave_js trigger helper to avoid confusion (#78331 )	2022-09-12 18:36:05 -04:00
README.md	…
__init__.py	Fix zwave_js device re-interview (#78046 )	2022-09-08 20:15:27 +02:00
addon.py	…
api.py	Import websocket api constants from root (#78250 )	2022-09-12 22:07:58 -04:00
binary_sensor.py	Switch to new entity naming schema across zwave_js (#77434 )	2022-09-12 09:14:59 +02:00
button.py	Switch to new entity naming schema across zwave_js (#77434 )	2022-09-12 09:14:59 +02:00
climate.py	Import climate constants from root [m-z] (#78178 )	2022-09-10 23:42:28 +02:00
config_flow.py	…
config_validation.py	…
const.py	Increase rate limit for zwave_js updates	2022-09-08 12:53:30 -04:00
cover.py	…
device_action.py	…
device_automation_helpers.py	…
device_condition.py	…
device_trigger.py	…
diagnostics.py	Import constants from root (#78271 )	2022-09-12 18:53:05 +02:00
discovery.py	Add zwave_js speed configuration for Leviton ZW4SF fans (#60677 )	2022-09-09 22:06:01 +02:00
discovery_data_template.py	…
entity.py	Switch to new entity naming schema across zwave_js (#77434 )	2022-09-12 09:14:59 +02:00
fan.py	…
helpers.py	…
humidifier.py	Use platform constants from root (#78032 )	2022-09-08 12:24:45 +02:00
light.py	…
lock.py	…
logbook.py	Use platform constants from root (#78032 )	2022-09-08 12:24:45 +02:00
manifest.json	…
migrate.py	…
number.py	Switch to new entity naming schema across zwave_js (#77434 )	2022-09-12 09:14:59 +02:00
select.py	Switch to new entity naming schema across zwave_js (#77434 )	2022-09-12 09:14:59 +02:00
sensor.py	Switch to new entity naming schema across zwave_js (#77434 )	2022-09-12 09:14:59 +02:00
services.py	…
services.yaml	…
siren.py	Use platform constants from root (#78032 )	2022-09-08 12:24:45 +02:00
strings.json	…
switch.py	…
trigger.py	…
update.py	Import update constants from root (#78251 )	2022-09-12 18:22:22 +02:00

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.