Fully configurable Zwave to MQTT Gateway and Control Panel.
Fully configurable Zwave to MQTT Gateway and Control Panel
Zwave to Mqtt Gateway: Configure how nodes and nodes values are
mapped between the two protocols
Secured: Supports HTTPS and users authentication
Control Panel UI: Directly control all your nodes and their
values from the UI, some of control panel features:
Nodes management: check all nodes discovered in the z-wave
network and manage their values
Firmware updates: update devices firmware, just select the
controller action Begin Firmware Update and upload the
Groups associations: add/edit nodes associations
Full zwave-js APIs support
Custom scenes management: create scenes and trigger them by using
MQTT apis (also supports timeouts)
Log debug in UI: See debug logs directly from the UI
Store directory management: all files are stored in store folder,
you can download/edit files inside this folder directly from the UI
Network graph: see how nodes are communicating with the controller,
useful for diagnostics purposes
Home Assistant integration: you can use official Zwavejs integration
by enabling zwavejs server or use integrated MQTT discovery integration
Channels in latest
This is how we use the different of channels in the latest track,
to give the user a chance to choose how often they want updates.
latest/stable: Latest version of the last major release. Will
only update once per major release and most likely by the end of
that release cycle. E.g when there is a new version b.a.a then
version a.b.c will be will be available.
latest/candidate: Latest minor or patch release of latest major
release. E.g when version a.b.c changes to a.b.d or a.c.a, then
version a.b.d or a.c.a will be available. Consider this rolling
latest/edge and latest/edge/dev: Every build (including tests) \n might be pushed to these channels.