The Z-Wave to MQTT add-on allows you to decouple your Z-Wave network from your Home Assistant instance by leveraging your MQTT broker. It ships with a web-based control panel, allowing you to configure every aspect of your Z-Wave network and how they are published in MQTT.
Some advantages and use-cases for this are:
Your Z-Wave network will keep running between Home Assistant restarts.
You can directly use things like Node-RED with your Z-Wave network, while it is available for Home Assistant at the same time.
Allow [ESPHome.io][esphome] based ESP devices to directly respond or work with your Z-Wave network.
Installation
The installation of this add-on is pretty straightforward and not different in comparison to installing any other add-on.
Search for the “Z-Wave to MQTT” add-on in the add-on store and install it.
Install the “Z-Wave to MQTT” add-on.
Start the “Z-Wave to MQTT” add-on.
Check the logs of the “Z-Wave to MQTT” add-on to see if everything went well.
Click the “OPEN WEB UI” button.
Enjoy the add-on!
Please read the documentation for more information about the use and configuration of this add-on.
Support
You can always try to get support from the community here at the Home Assistant community forums, join the conversation!
Questions? You have several options to get them answered:
The Home Assistant Community Add-ons Discord Chat server for add-on support and feature requests.
The Home Assistant Discord Chat Server for general Home Assistant discussions and questions.
The primary goal of our add-ons project is to provide you (as a Home Assistant user) with additional, high quality, add-ons that allow you to take your automated home to the next level.
I am Franck Nijhof, and I have 30 years of programming experience, in many languages. I am using this experience to work on the Home Assistant project by giving back my knowledge and time to the open source community.
The add-on you are currently looking at right now was developed/packaged by me. It is not the only add-on I have created; there are many many more
However, I have a problem… I am an addict. A addict that is. Lucky for you, I turn that C8H10N4O2 (caffeine molecule) into code (and add-ons)!
If you want to show your appreciation, consider supporting me for buying a cup of high octane wakey juice via one of the platforms below!
Enjoy your add-on, while I enjoy the brain juice.
Thanks for all the
…/Frenck
P.S.: In case you want to ask me a question: AMA (Ask Me Anything). Most of the time I am online at the Discord chat. (I go by @Frenck in there as well).
Looks to be a valuable add-on. Installed but can’t open web ui. I’m on hass.io v92.2.
Log…
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Hass.io Add-on: Z-Wave to MQTT
Fully configurable Z-Wave to MQTT gateway and control panel
-----------------------------------------------------------
Add-on version: 0.1.0
You are running the latest version of this add-on.
System: Debian GNU/Linux 9 (stretch) (amd64 / qemux86-64)
Home Assistant version: 0.92.2
Supervisor version: 162
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] zwave2mqtt.sh: executing...
[cont-init.d] zwave2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[18:20:16] INFO: Starting the Z-Wave to MQTT...
2019-05-09T22:20:16.700Z z2m:Store settings.json not found
2019-05-09T22:20:16.706Z z2m:Store scenes.json not found
2019-05-09T22:20:17.186Z z2m:App Application path:/opt
2019-05-09T22:20:17.193Z z2m:Gateway Gateway needs both MQTT and Zwave Configuration to work
2019-05-09T22:20:17.275Z z2m:App Listening on port 44920
[18:20:17] INFO: Starting NGinx...
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
You made my day!
This will improve the WAF drastically. No more waiting for all the battery devices to turn up hours after a restart.
Will surely try this out this evening and buy you some coffees!
Hi,
could you perhaps share your config settings for z-wave and mqtt?
I’m getting “your configuration contains errors” all the time.
Using the Mosquitto broker add-on to act as the mqtt bridge.
To be honest, I’m not using it. I only installed it to verify if the webUI was broken for everyone or not.
As for configuration, the link below is for the original project’s github page. They explain what the configuration options are, and what they should be set to. It will probably help you set it up.
Sorry, real noob with mqtt, how should I see the devices appearing?
I got the gatway configured as
type: “configured manually”
payload type: “JSON”
Figured this out. Frenck helped me out on discord - the network key is in your /config/.storage directory. Just grep for it in there. Once you have that, enter it as it’s shown in the config file, but with NO spaces.
Are you running hassbian by chance? Or venv? or? FYI, it’s a hidden directory (because of the dot), so you’ll need to do an ls -al to see it once you’re in your config directory.