Files

Raman Gupta 9e4e43cf77 Handle zwave_js metadata/value updates when the unit changes (#63579 )

* Handle zwave_js metadata updates when the unit changes

* Use value updated event instead of metadata updated event so we don't get an invalid state value

* update comments and formatting

* simplify

* Update tests/components/zwave_js/test_sensor.py

Co-authored-by: Martin Hjelmare <marhje52@gmail.com>

* Update tests/components/zwave_js/test_sensor.py

Co-authored-by: Martin Hjelmare <marhje52@gmail.com>

* Update tests/components/zwave_js/test_sensor.py

Co-authored-by: Martin Hjelmare <marhje52@gmail.com>

* fix tests

* add additional assertions

* Add unit checks and simplify logic

* Add unit assertion

Co-authored-by: Martin Hjelmare <marhje52@gmail.com>

2022-01-08 13:23:29 +01:00

docs

…

translations

[ci skip] Translation update

2022-01-08 00:14:39 +00:00

triggers

…

__init__.py

Avoid removing zwave_js devices for non-ready nodes (#59964 )

2021-12-27 12:31:31 +01:00

addon.py

Start using ParamSpec for decorator functions (#63148 )

2022-01-04 18:37:46 +01:00

api.py

…

binary_sensor.py

…

climate.py

…

config_flow.py

…

const.py

…

cover.py

Fix zwave_js ZWaveTiltCover docstring (#62972 )

2021-12-28 19:24:27 -05:00

device_action.py

…

device_automation_helpers.py

…

device_condition.py

Use correct relative imports [n-z] (#63471 )

2022-01-05 17:23:49 +01:00

device_trigger.py

…

discovery_data_template.py

…

discovery.py

Add zwave_js support for Fortrezz SSA3 (#62765 )

2021-12-25 10:33:20 +01:00

entity.py

Avoid removing zwave_js devices for non-ready nodes (#59964 )

2021-12-27 12:31:31 +01:00

fan.py

…

helpers.py

Avoid removing zwave_js devices for non-ready nodes (#59964 )

2021-12-27 12:31:31 +01:00

light.py

…

lock.py

…

manifest.json

…

migrate.py

…

number.py

…

README.md

…

select.py

…

sensor.py

Handle zwave_js metadata/value updates when the unit changes (#63579 )

2022-01-08 13:23:29 +01:00

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.