Node Types
There are 3 node types which are installed with this contrib: zwave-js, zwave-device and event-filter
This is the main node, it is the node that is responsible for everything, and also serves as the configuration for your USB Z-Wave radio. This node is the only place to send or receive commands to/from the controller. The node can send commands to all of your devices. It will receive all commands from all of your devices. It accepts all commands (controller or device, using any API).
To configure it, drag the node to your flow, double click, and choose (at least) your USB serial port address/name. Note: Only 1 copy of this node can be deployed.
More information about the controller node and it's configuration is available here
The Swiss army knife!
This node works in conjunction with the zwave-js node above, be sure to have the controller running before adding device nodes.
This node is extremely flexible, it can:
- work with 1 device or many
- can be used in a Subflow with environment variable support
- can use Z-Wave Multicast (for supported devices)
- be configured as a Send, Receive, or 2-way node in your flow
- be used as many times as you like across your flows/subflows
Like the main node, double click it to configure.
Note: zwave-device only supports device specific commands - either CC API or Value API.
A much much bigger Swiss army knife
This node allows advanced filtration of the various value events that a node may send. It further allows filtering the type of data that was updated i.e. a Motion Event, Air Temp changes, Door Sensors, etc.
The UI panel on the right - can be used to provide the filter values, removing the need to write them yourself, but of course you can use manual entries if you prefer.
Everything we know about the event-filter node is available at this wiki page