hassio-addons / addon-zwave2mqtt

Z-Wave to MQTT - Home Assistant Community Add-ons

Home Assistant Community Add-on: Z-Wave to MQTT

Fully configurable Z-Wave to MQTT gateway and control panel.

Deprecation warning

This add-on is in a deprecated state!

The upstream project has been archived and will no longer receive updates. Therefore, there is no other solution but deprecating the add-on as well.

Please use the Z-Wave JS to MQTT add-on instead.

About

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 based ESP devices to directly respond or work with your Z-Wave network.

This add-on uses the Zwave2Mqtt software provided by OpenZWave.

📚 Read the full add-on documentation

Support

Got 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 Home Assistant Community Forum.
• Join the Reddit subreddit in /r/homeassistant

You could also open an issue here GitHub.

Contributing

This is an active open-source project. We are always open to people who want to use the code or contribute to it.

We have set up a separate document containing our contribution guidelines.

Thank you for being involved! 😍

Authors & contributors

The original setup of this repository is by Franck Nijhof.

For a full list of all authors and contributors, check the contributor's page.

We have got some Home Assistant add-ons for you

Want some more functionality to your Home Assistant instance?

We have created multiple add-ons for Home Assistant. For a full list, check out our GitHub Repository.

License

MIT License

Copyright (c) 2019-2021 Franck Nijhof

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

addon-zwave2mqtt's Issues

add socat

Problem/Motivation

need to run the addon remotely

Expected behavior

add socat support

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

please add socat support to connect to zwave stick remotely

Alpine Linux's openzwave{,-dev} packages are unmaintained and outdated.

Problem/Motivation

The openzwave packages in Alpine Linux, which are used by this package, were last built in 11/2019. It's using 1.6-974, while upstream's latest stable release is 1.16.1149:
https://pkgs.alpinelinux.org/packages?name=openzwave&branch=edge
https://pkgs.alpinelinux.org/packages?name=openzwave-dev&branch=edge

The package also appears to be unmaintained, and is therefore unlikely to be updated. This package also has a few bugs, some of which are referenced here (path issues). I also suspect, and am working to prove in that issue, that the actual TriggerRefreshValue issue is related as well.
OpenZWave/open-zwave#2264

Expected behavior

OpenZWave dependency is maintained, and is able to remain relatively up to date.

Actual behavior

The opposite.

Steps to reproduce

The age of the package is visible in the links above.

Proposed changes

I'm working right now to adjust the Dockerfile to build OpenZWave from source. Will open a PR once ready, if this approach is acceptable.

Another option might be to try and wrap the official Zwave2Mqtt image with the hassio magic. Dockerfile here:
https://github.com/OpenZWave/Zwave2Mqtt/tree/master/docker

GitHub

OpenZWave/Zwave2Mqtt

Fully configurable Zwave to MQTT gateway and Control Panel using NodeJS and Vue - OpenZWave/Zwave2Mqtt

MQTT Connection Issue after changing settings

Problem/Motivation

Changing MQTT settings causes the addon to no longer connect to MQTT.

Expected behavior

Settings can be changed without restarting after.

Actual behavior

Logs show issues connecting to MQTT after changing MQTT settings. Restarting the add-on seems to fix the problem.

2019-11-29T17:16:08.908Z z2m:Zwave zwave node 27: changed: 49-1-1:Temperature:19.4 -> 19.4
2019-11-29T17:16:08.909Z z2m:Mqtt Error while publishing a value client disconnecting
OpenZWave Detail, Node027, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x1b, 0x06, 0x31, 0x05, 0x01, 0x22, 0x00, 0xc2, 0x3f
OpenZWave Detail,
OpenZWave Info, Node027, Received SensorMultiLevel report from node 27, instance 1, Temperature: value=19.4C
OpenZWave Detail, Node027, Refreshed Value: old value=19.4, new value=19.4, type=decimal
OpenZWave Detail, Node027, Changes to this value are not verified
OpenZWave Detail, Node027, Notification: ValueChanged

Steps to reproduce

1. Click on settings
2. Change a setting in MQTT and click save.
3. Go to logs, see error "z2m:Mqtt Error while publishing a value client disconnecting"

Proposed changes

Unknown - It seems to be related to this: https://github.com/OpenZWave/Zwave2Mqtt/issues/64

Wrong install location of openzwave database

Problem/Motivation

If you run the addon without a custom zwave database path it will throw errors cause it can not find the config files.

Expected behavior

No config errors should occur on first start

Actual behavior

If you run the addon without a custom zwave database path it will throw errors cause it can not find the config files.

Log:

2020-03-12 16:12:37.105 Warning, Config File for ZHC5002 Z-Scene Controller does not exist - config/logicsoft/ZHC5002.xml
2020-03-12 16:12:37.105 Warning, Config File for STZW402+ Electronic Thermostat does not exist - config/stelpro/stzw402.xml
2020-03-12 16:12:37.105 Warning, Config File for PSC234ZW Smart Plug does not exist - config/permundo/psc234zw.xml
2020-03-12 16:12:37.106 Warning, Config File for PSC132ZW Smart Mini Plug does not exist - config/permundo/psc132zw.xml
2020-03-12 16:12:37.106 Warning, Config File for Door/Window Detector does not exist - config/shenzen_neo/nas-ds01z.xml
2020-03-12 16:12:37.106 Warning, Config File for NAS-PD01Z Battery Powered PIR Sensor does not exist - config/shenzen_neo/nas-pd01z.xml
2020-03-12 16:12:37.106 Warning, Config File for Water Leakage Detector does not exist - config/shenzen_neo/nas-ws02z.xml
2020-03-12 16:12:37.106 Warning, Config File for NAS-WR01Z Power plug 12A does not exist - config/shenzen_neo/nas-wr01z.xml
2020-03-12 16:12:37.106 Warning, Config File for Siren Alarm does not exist - config/shenzen_neo/nas-ab01z.xml
2020-03-12 16:12:37.106 Warning, Config File for SOS/Remote Control does not exist - config/shenzen_neo/nas-rc01z.xml
2020-03-12 16:12:37.106 Warning, Config File for Wall Switch (2 channels) does not exist - config/shenzen_neo/ls02ch.xml
2020-03-12 16:12:37.106 Warning, Config File for Wall Switch (1 channel) does not exist - config/shenzen_neo/ls01ch.xml

Steps to reproduce

Start a new container without any config

Proposed changes

Zwave2Mqtt looks for the zwave database under /usr/local/etc/openzwave/

So i think there are 3 choices to solve this problem:

1. Check with a script if a default config from zwave2mqtt is present and add the database path via sed
2. Update the dockerfile and move the openzwave database config to the default config folder
3. Provide a clear information in the Readme?

Updated message is incorrect

I noticed the add-on says there is a new version available when you start it:
Add-on version: 0.5.0
There is an update available for this add-on!
Latest add-on version: null

However, the new version is null. Seems incorrect to me.

Expected behavior

I expected no update message.

(What you expected to happen)

The logs says there is a new version available but there isn't any.

Create release based on master?

Can you create a release based on the master version? Currently in HA the most recent version is 0.5.0 which is using v2.2.0 of z2m, whereas your master version is on 3.0.1.

Zwave2MQTT v2.0.2 released

https://github.com/OpenZWave/Zwave2Mqtt/releases/tag/v2.0.2

username and password?

What are the username and password for this addon? I don't see anywhere to enable them. The credentials for home assistant don't seem to work, and using the front door open seems like a bad idea.

Battery powered devices "dead" after restart

After a restart, battery powered devices ( motion detectors ) are shown as "dead" without any node information.

Feat: Update openzwave db to include z-dim

Problem/Motivation

Update the openzwave db to rev 7ad4c22f4f3f78bad84a46de8a26906e35b28329 to include new z-dim component from Heatit

Expected behavior

My z-dim component is recognized and can be configured.

Actual behavior

Z-Dim component is unknown

Steps to reproduce

1. Get a Heatit Z-Dim
2. Try to include it

Proposed changes

Update the openzwave db to rev 7ad4c22f4f3f78bad84a46de8a26906e35b28329

PANIC: unprotected error in call to Lua API (bad light userdata pointer)

Problem/Motivation

when i open the webpage i have an error in the logs

Expected behavior

open the webpage

Steps to reproduce

install on HA (odroid-c2) the addons and try to go one the webpage

[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...

---

Add-on: Z-Wave to MQTT
Fully configurable Z-Wave to MQTT gateway and control panel

Add-on version: 0.6.0
You are running the latest version of this add-on.
System: Debian GNU/Linux 10 (buster) (aarch64 / odroid-c2)
Home Assistant Core: 0.109.6
Home Assistant Supervisor: 222

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.
[14:07:09] INFO: Starting the Z-Wave to MQTT...
2020-05-10T12:07:11.013Z z2m:Store settings.json not found
2020-05-10T12:07:11.029Z z2m:Store scenes.json not found
2020-05-10T12:07:11.030Z z2m:Store nodes.json not found
2020-05-10T12:07:12.840Z z2m:Gateway No customDevices file found
2020-05-10T12:07:12.849Z z2m:App Application path:/opt
2020-05-10T12:07:12.876Z z2m:Gateway Zwave settings are not valid
2020-05-10T12:07:13.189Z z2m:App Listening on port 44920
[14:07:13] 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)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)

GitHub

openresty/luajit2

OpenResty's Branch of LuaJIT 2. Contribute to openresty/luajit2 development by creating an account on GitHub.

OpenResty - Download

Add link to main project

Hi, I'm the author of Zwave2Mqtt, I think that would be useful for users a link to the main project to find all docs needed to set up the gateway.

https://github.com/OpenZWave/Zwave2Mqtt

Thanks :)

GitHub

OpenZWave/Zwave2Mqtt

Fully configurable Zwave to MQTT gateway and Control Panel using NodeJS and Vue - OpenZWave/Zwave2Mqtt

cant start on a fresh install as it is missing ssl cert

Problem/Motivation

After a fresh install (as in writen image to disk, booted it, waited, created user, installed zwave2mqtt plugin and hit start) it wont start because the log complains about missing SSL cert

Expected behavior

started addon

Actual behavior

not so started plugin

Steps to reproduce

pi3b+

1. write image to disk
2. booted it
3. wait for setup to complete
4. create user
5. installe zwave2mqtt plugin
6. hit start

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

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.4.2
 You are running the latest version of this add-on.
 System: HassOS 3.7  (armv7 / raspberrypi3)
 Home Assistant version: 0.103.5
 Supervisor version: 193
-----------------------------------------------------------
 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... 
[14:46:54] FATAL: 
[14:46:54] FATAL: SSL has been enabled using the 'ssl' option,
[14:46:54] FATAL: this requires a SSL certificate file which is
[14:46:54] FATAL: configured using the 'certfile' option in the
[14:46:54] FATAL: add-on configuration.
[14:46:54] FATAL: 
[14:46:54] FATAL: Unfortunately, the file specified in the
[14:46:54] FATAL: 'certfile' option does not exists.
[14:46:54] FATAL: 
[14:46:54] FATAL: Please ensure the certificate file exists and
[14:46:54] FATAL: is placed in the Hass.io '/ssl/' directory.
[14:46:54] FATAL: 
[14:46:54] FATAL: In case you don't have SSL yet, consider getting
[14:46:54] FATAL: a SSL certificate or setting the 'ssl' option
[14:46:54] FATAL: to 'false' in case you are not planning on using
[14:46:54] FATAL: SSL with this add-on.
[14:46:54] FATAL: 
[14:46:54] FATAL: Check the add-on manual for more information.
[14:46:54] FATAL: 
[cont-init.d] nginx.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.

 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

Difference with ozwdaemon

Sorry to post here, It's not a issue.

But since 0.110 there is another "official zwave implantation and I am lost!

What is the difference with ozwdaemon
https://github.com/marcelveldt/hassio-addons-repo/tree/master/ozwdaemon

Thanks in advance, and sorry to ask!

GitHub

marcelveldt/hassio-addons-repo

Marcelveldt's repo with hassio add-ons. Contribute to marcelveldt/hassio-addons-repo development by creating an account on GitHub.

zwave database update failed

Problem/Motivation

Downloading the newest zwave device database is failing.

Expected behavior

It should be downloded.

Actual behavior

2020-03-06 14:08:44.117 Warning, Download of http://download.db.openzwave.com/0001.0001.031e.xml Failed (Node: 0) 2020-03-06 14:08:44.273 Warning, Download of http://download.db.openzwave.com/0001.0003.031e.xml Failed (Node: 0) 2020-03-06 14:08:44.423 Warning, Download of http://download.db.openzwave.com/0001.0005.031e.xml Failed (Node: 0) 2020-03-06 14:08:44.577 Warning, Download of http://download.db.openzwave.com/0001.0006.031e.xml Failed (Node: 0) 2020-03-06 14:08:44.728 Warning, Download of http://download.db.openzwave.com/0001.0007.031e.xml Failed (Node: 0)

If I try this links wit a browser i got the following results:
Not Found
The requested URL /0001.0005.031e.xml was not found on this server.

Steps to reproduce

Restart zwave2mqtt and see the logs.

Proposed changes

I think the download links are broken.

404 Not Found

404 Not Found

404 Not Found

404 Not Found

404 Not Found

Auth failed

Problem/Motivation

Despite entering the same user and the same password used by Home Assistant the login fails.

Expected behavior

It successfully logs in.

Actual behavior

Re-asks for the credentials.

Steps to reproduce

I don't know if it's possible to reproduce it. It worked the very first time, then I had to pull the power from the pi and at the next boot it didn't work anymore.
I tried to remove the docker image and reinstall the hassio addon, but nothing changed.
It works with leave_front_door_open.
Nothing interesting can be found in the logs, even with "log_level": "info"

Proposed changes

None.

Proposal: Add Socat

Proposing that socat be added to the container. Then allow a variable to be passed to call socat on boot before the zwave daemon starts.

An example socat call would be:
socat PTY,link=/dev/zwave,raw,group=root,mode=777 TCP::7676

We would want to pass as a variable.

This would enable people to use zwave as serial devices over IP. If someone had a zwave stick on a raspberry pi or maybe they have a vera; this would enable the device to be passed to the zwave2mqtt addon.

Feature request: update button for zwave2mqtt

Is it posible to create an easy way to update the docker image with latest zwave2mqtt version without you have to create a new build of this plugin ?

Mount a z-wave dongle by /dev/serial/by-id not working

Problem/Motivation

I use usbip to broadcast by dongles to the server. Very often the tty* change when using usbip.

usbip can broadcast the usb device on insert and removal, but often the tty device name change. ttyUSB0 next time it is ttyUSB1 and then back to ttyUSB0. This depends on the reboot order and how many reboots.

Expected behavior

In zwave2mqtt I can only select tty* devices, not /dev/serial/by-id/xxxxxxxxxx devices.
If I type a /dev/serial/by-id/xxxxxxx device in the field, zwave2mqtt cannot open it.

Actual behavior

2019-12-24 00:48:09.197 Info, Trying to open serial port /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0 (attempt 1)
2019-12-24 00:48:09.232 Info, Serial port /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0 opened (attempt 1)

It simply fails. But if I change to ttyUSB0 it works (but the it could be ttyUSBx)

Steps to reproduce

Just endter a /dev/serial/by-id/ serial id.

Proposed changes

When i ssh into the docker container I can list the /dev/serial/by-id
but I see they have no link to the actual tty device, which they normally do in linux.

root@a0d7b954-zwave2mqtt:/$ ls -la /dev/serial/by-id/ total 0 drwxr-xr-x 2 root root 120 Dec 24 00:56 . drwxr-xr-x 3 root root 60 Dec 24 00:56 .. crw-rw---- 1 root dialout 188, 2 Dec 24 00:56 usb-1a86_USB2.0-Serial-if00-port0 crw-rw---- 1 root dialout 188, 3 Dec 24 00:56 usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0 crw-rw---- 1 root dialout 166, 2 Dec 24 00:56 usb-MySensors.org_Sensebender_GW_E8B45813514D355231202020FF18142B-if00 crw-rw---- 1 root dialout 166, 0 Dec 24 00:56 usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B00193672AA-if00

Expected is:

magpern@plexserver:~$ ls -la /dev/serial/by-id total 0 drwxr-xr-x 2 root root 120 Dec 23 23:45 . drwxr-xr-x 4 root root 80 Dec 23 23:37 .. lrwxrwxrwx 1 root root 13 Dec 23 23:45 usb-1a86_USB2.0-Serial-if00-port0 -> ../../ttyUSB2 lrwxrwxrwx 1 root root 13 Dec 23 23:45 usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0 -> ../../ttyUSB3 lrwxrwxrwx 1 root root 13 Dec 23 23:45 usb-MySensors.org_Sensebender_GW_E8B45813514D355231202020FF18142B-if00 -> ../../ttyACM2 lrwxrwxrwx 1 root root 13 Dec 23 23:38 usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B00193672AA-if00 -> ../../ttyACM0

FGDW002 Fibaro Door Sensors not working correct

Hi All,

Im done with add all my devices. Also 2 FGDW002 Fibaro Door Sensors.
They don't have any MQTT part to send OPEN/CLOSE

Zwave2MQTT is installed using Add-ON of Home Assistant.
Version: Openzwave 1.6.974

What can I do to let those 2 devices work correct?

zwcfg and zwscene files not saved

Problem/Motivation

When the zwave2mqtt container is restarted the zwcfg_hex.xml and zwscene.xml files are not saved since the folder they are saved in is not where the data volume is mounted (/opt). This is preventing node names and locations from being persisted.

Expected behavior

When the container is restarted the zwcfg_hex.xml and zwscene.xml files should be persisted.

Actual behavior

The zwcfg_hex.xml and zwscene.xml files are removed since they are not stored in a volume.

Steps to reproduce

Install addon, enable 'Save configuration' setting, restart addon.

Proposed changes

The files should be saved and loaded from /opt/store instead of /opt since that is where the data volume is mounted.

Cannot start addon

Problem/Motivation

I installed the addon, set ssl to false, hit Save and tried to start. The Start button flashes red indicating it did not start. There is no log file but when i look at the Home Assistant log i get the message

http://xxxxxxxxxxx/frontend_latest/chunk.feb8b7774cfc2dc8791f.js:1187:786 Uncaught TypeError: Cannot read property 'id' of undefined

Not sure if the error message has something to do with this addon but it's the only error message i can find so i posted it.

Not sure if there is something else I can post

Add - inclusion - is not adding securely

Problem/Motivation

I am in the process of adding some new devices to my zwave mesh and the UI is not prompting for Secure inclusion - I raised this concern on zwave2mqtt and was told this is not a problem with zwave2mqtt so I am entering it here

Expected behavior

I know my Key is correct because previously added devices are showing as "Yes" secure in the list, but when I add new devices (ZSE40 Sensor, Aeotec NanoMote, Inovelli Red Series Dimmer) they are not being prompted to add securely. The pop-up prompt is expected per zwave2mqtt

Actual behavior

Devices are being added but not using secure protocols which cause some of the functionality to be
reduced.

Steps to reproduce

remove - exclude device that was secure, then wait a while - add - inclusion - and it is not prompting for secure add.

Proposed changes

No workarounds are known at this point.

I am running HassOS 3.11 on a Raspberry PI B+, Supervisor 206 and Add-on Zwave2MQTT 0.5.0

Stop responding every day

Problem/Motivation

After I updated to the latest version my devices stop working almost every day and I have to restart the zwave2mqtt add-on.
Sometimes I cannot even open the web UI

On the previous version it's been Rock solid for months.

Expected behavior

Working without interruptions

Actual behavior

Stops working

Steps to reproduce

Proposed changes

Fix

g

Problem/Motivation

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

MQTT messages sent

Hey,

After uninstalling zwave2mqtt, MQTT messages are sent all the time. When I listen to topics, the HA page can hang for a few seconds. I can't go to the Supervisor tab and restart the raspberry, I need to disconnect the power supply and connect again.

Without listening for messages Home Assistant works fine.
The system crashes when trying to listen for the first time.
Home Assistant installed on Docker

Please help.

No configuration for FIBARO FGRM222

Problem/Motivation

There is no configuration visible in the Configuration panel for the roller shutter Fibaro FGRM222
But in the main panel the FGRM222 are rigthly identified with the constructors name

Expected behavior

Get the parameters visible in order to update them. It worked before, I can't say if it is link to a particular release or not

Actual behavior

nothing visible in the Configuration node

Thanks !
I don't know if it is related to the addon or the zwave lib... sorry if i'm not in the wrong depository...

Map database path to accessible folder?

I'm new to Docker environments in general so my apologies in advance if this is a stupid question...

My setup = very standard; HassOS 3.13 image on a RPi 3B+, Aeotec Gen5 stick, and this add-on.

Everything is working great but I'd like to use my own modified version of the OpenZWave database (for specific device configs).

I know I can specify the database path within Z2M, but I don't know how to map that path to an accessible folder within Home Assistant (i.e. addons, share, etc.). Can anyone help?

Removing or Renaming a device, doesn't cleanup at HASS

When a New device is discovered, if for any reason is been excluded from zwave2mqtt. The device gives no option to remove it from HomeAssistant.

The same happens when a device is renamed, or changed name in zwave2mqtt frontend (web ui).
Then I do see two times the same device.

There should be a way to cleanup the remove/renamed devices from HomeAssistant.

1. Restart doesn't help
2. Entities can be deleted but still left with empty devices.

ERROR: Not enough space in stream buffer

Problem/Motivation

Getting the following error in the log: ERROR: Not enough space in stream buffer

Steps to reproduce

New installation, migrated an existing zwave configuration by removing the existing HASS zwave config, copying the network_key from the /config/.storage and using that in my zwavetomqtt config. After a restart, all existing devices showed up in my config, but I started seeing the following error. zwave device changes dont seem to be publishing to mqtt anymore either.

Icons missing

Since today, on several PCs and several browsers:

icons are al gone... what's wrong?

panel: Controller action "Refresh node info" does not work in panel UI

Problem/Motivation

The "Refresh node info" controller action in the control panel does not seem to work when the UI is embedded as a panel in Home Assistant.

When not embedded, the zwave2mqtt will display an alert dialog prompting for a node id. When embedded, no alert appears.

Expected behavior

I expected to be prompted for the node to refresh.

Actual behavior

Nothing appeared to happen. There were no messages emitted in the OZW log.

Steps to reproduce

Configure zwave2mqtt to display as an embedded iframe in Home Assistant.

panel_iframe:

Z-Wave to MQTT

zwave2mqtt:
title: Z-Wave to MQTT
icon: mdi:z-wave
url: http://home-assistant.lan:8091

Using the Chrome web browser, open the zwave2mqtt control panel in Home Assistant, select the "Refresh node info" controller action near the top of the page, click the "send arrow" icon to invoke it.

Zwave2Mqtt MQTT autodiscovery

I have just published on Zwave2Mqtt master a first beta version with MQTT discovery. I'm looking for testers

How can I upgrade

Problem/Motivation

I am having issues with some devices, according to the zwave2mqtt developer it is because I am running an other version V2.2.0

How can I upgrade to the latest version?

I am running this addon in the Home Assistant Hypervisor.

Adjusting HASS Discovery Topic does not update on existing nodes

Problem/Motivation

At first set-up I’ve called the MQTT topic “ zwave2mqtt” and left the HASS discovery topic setting blank, thus it would use the general MQTT topic. However, I wanted to change the discovery topic to “ homeassistant”. This is all well, but it does not update the discovery topic for existing nodes, even not when I click “Rediscover” it retains the old discovery topic.

Expected behavior

After click “Rediscover” on existing nodes that it would update the discovery topic to the latest on as set in the Settings tab.

Actual behavior

Retains “old” discovery topic and does not update it on existing nodes.

Steps to reproduce

See above.

Proposed changes

Ensure the discovery topic is updated after clicking “Rediscover”

After restart every z-wave device disappeard

Problem/Motivation

After restart of the addon all my devices disappeard

Expected behavior

It will start with all devices

Actual behavior

No z-wave devices found
Here is my log at startup:

[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...

---

Add-on: Z-Wave to MQTT
Fully configurable Z-Wave to MQTT gateway and control panel

Add-on version: 0.5.0
You are running the latest version of this add-on.
System: Ubuntu 18.04.4 LTS (amd64 / qemux86-64)
Home Assistant Core: 0.106.2
Home Assistant Supervisor: 206

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
[00:03:21] INFO: Starting the Z-Wave to MQTT...
[services.d] done.
2020-03-02T23:03:21.315Z z2m:Store scenes.json not found
2020-03-02T23:03:21.785Z z2m:Gateway No customDevices file found
2020-03-02T23:03:21.787Z z2m:App Application path:/opt
Initialising OpenZWave 1.6.974 binary addon for Node.JS.
OpenZWave Security API is ENABLED
ZWave device db : etc/openzwave/
User settings path : /opt/store
Option Overrides : --Logging undefined --ConsoleOutput undefined --QueueLogLevel 6 --DriverMaxAttempts 9999 --SaveConfiguration true --PollInterval 5000 --AutoUpdateConfigFile true --AssumeAwake true
2020-03-02T23:03:21.891Z z2m:Zwave Connecting to /dev/ttyACM0
2020-03-03 00:03:21.892 Error, Cannot find a path to the configuration files at etc/openzwave/, Using config/ instead...
2020-03-03 00:03:21.892 Warning, Failed to Parse config/options.xml: Failed to open file
2020-03-03 00:03:21.892 Warning, Failed to Parse /opt/store/options.xml: Failed to open file
2020-03-03 00:03:21.892 Info, Options:
2020-03-03 00:03:21.892 Info, appendlogfile: false
2020-03-03 00:03:21.892 Info, associate: true
2020-03-03 00:03:21.892 Info, assumeawake: true
2020-03-03 00:03:21.892 Info, autoupdateconfigfile: true
2020-03-03 00:03:21.892 Info, configpath: config/
2020-03-03 00:03:21.892 Info, consoleoutput: true
2020-03-03 00:03:21.892 Info, customsecuredcc: 0x62,0x4c,0x63
2020-03-03 00:03:21.892 Info, drivermaxattempts: 9999
2020-03-03 00:03:21.892 Info, dumptriggerlevel: 1
2020-03-03 00:03:21.892 Info, enablesis: true
2020-03-03 00:03:21.892 Info, enforcesecurereception: true
2020-03-03 00:03:21.892 Info, exclude:
2020-03-03 00:03:21.892 Info, include:
2020-03-03 00:03:21.892 Info, includeinstancelabel: true
2020-03-03 00:03:21.892 Info, interface:
2020-03-03 00:03:21.893 Info, intervalbetweenpolls: false
2020-03-03 00:03:21.893 Info, language:
2020-03-03 00:03:21.893 Info, logfilename: OZW_Log.txt
2020-03-03 00:03:21.893 Info, logging: true
2020-03-03 00:03:21.893 Info, networkkey:
2020-03-03 00:03:21.893 Info, notifyondriverunload: false
2020-03-03 00:03:21.893 Info, notifytransactions: false
2020-03-03 00:03:21.893 Info, performreturnroutes: false
2020-03-03 00:03:21.893 Info, pollinterval: 5000
2020-03-03 00:03:21.893 Info, queueloglevel: 6
2020-03-03 00:03:21.893 Info, refreshallusercodes: false
2020-03-03 00:03:21.893 Info, reloadafterupdate: AWAKE
2020-03-03 00:03:21.893 Info, retrytimeout: 10000
2020-03-03 00:03:21.893 Info, saveconfiguration: true
2020-03-03 00:03:21.893 Info, saveloglevel: 8
2020-03-03 00:03:21.893 Info, securitystrategy: SUPPORTED
2020-03-03 00:03:21.893 Info, suppressvaluerefresh: false
2020-03-03 00:03:21.893 Info, userpath: /opt/store/
2020-03-03 00:03:21.893 Always, OpenZwave Version 1.6-974-ge89d2a16-dirty Starting Up
2020-03-03 00:03:21.894 Warning, Unable to load Localization file config/Localization.xml: Failed to open file
2020-03-03 00:03:21.894 Always, Using Language Localization
2020-03-03 00:03:21.894 Warning, Unable to load NotificationCCTypes file config/NotificationCCTypes.xml
2020-03-03 00:03:21.894 Warning, Unable to load SensorMultiLevelCCTypes file config/SensorMultiLevelCCTypes.xml
2020-03-03 00:03:21.894 Warning, Failed - Network Key Not Set
2020-03-02T23:03:21.897Z z2m:Zwave Zwave connected, Openzwave version: 1.6.974
2020-03-02T23:03:21.980Z z2m:App Listening on port 44920
2020-03-02T23:03:22.008Z z2m:Mqtt MQTT client connected
[00:03:22] 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)
2020-03-03 00:03:22.527 Warning, Config Revision of ManufacturerSpecific Database is out of date

Steps to reproduce

I don't konw

Proposed changes

Fix!

GitHub

openresty/luajit2

OpenResty's Branch of LuaJIT 2. Contribute to openresty/luajit2 development by creating an account on GitHub.

OpenResty - Download

GetSensorUnit - Unknown SensorType 1

Problem/Motivation

Version: 0.5.0

My Philio PAT02B sensor has unkown type at temperature and humindity.
I attached a picture about it.

Expected behavior

On the 0.4.2 version it was correct.

Actual behavior

Log:
2020-03-04 23:11:46.206 Warning, SensorMultiLevelCCTypes::GetSensorUnit - Unknown SensorType 1
2020-03-04 23:11:46.206 Warning, SensorMultiLevelCCTypes::GetSensorName - Unknown SensorType 1
2020-03-04T22:11:46.208Z z2m:Zwave zwave node 5: changed: 49-1-1:Unknown:22 -> 22.22
2020-03-04 23:11:46.229 Warning, SensorMultiLevelCCTypes::GetSensorUnit - Unknown SensorType 5
2020-03-04 23:11:46.229 Warning, SensorMultiLevelCCTypes::GetSensorName - Unknown SensorType 5
2020-03-04T22:11:46.230Z z2m:Zwave zwave node 5: changed: 49-1-5:Unknown:68.46 -> 68.25

Full OZW log:
OZW_Log.txt

Steps to reproduce

Add a Philio PAT02B sensor to your zwave network.

Proposed changes

Please modify the default "path to database" to /usr/etc/openzwave

Info, Failed to load device_classes.xml

Devices are discovered but the device type fields are blank and no custom device properties are applied.

This appears in the log at startup:
2020-03-18 15:26:46.457 Info, Failed to load device_classes.xml
2020-03-18 15:26:46.457 Info, Check that the config path provided when creating the Manager points to the correct location.

user/pass

Problem/Motivation

webif asking for user/pass

(Why the issue was filed)

Expected behavior

documentation to provide default user/pass

(What you expected to happen)
to login with default credntials

Actual behavior

the opposite

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Docker

Unable to open WebUI

Problem/Motivation

Unable to open WebUI after initial installation

Expected behavior

Have access to the WebUI

Actual behavior

Webpage gives an empty response

Steps to reproduce

Do a fresh install of the plugin, version 0.4.1.
See logging below
``
[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.4.1
You are running the latest version of this add-on.
System: HassOS 2.12 (aarch64 / odroid-c2)
Home Assistant version: 0.102.2
Supervisor version: 192

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:26:23] INFO: Starting the Z-Wave to MQTT...
2019-11-28T17:26:25.068Z z2m:Store settings.json not found
2019-11-28T17:26:25.081Z z2m:Store scenes.json not found
2019-11-28T17:26:25.084Z z2m:Store nodes.json not found
2019-11-28T17:26:30.894Z z2m:App Application path:/opt
2019-11-28T17:26:30.912Z z2m:Gateway Gateway needs both MQTT and Zwave Configuration to work
2019-11-28T17:26:31.179Z z2m:App Listening on port 44920
[18:26:31] 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)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
PANIC: unprotected error in call to Lua API (bad light userdata pointer)
``

GitHub

openresty/luajit2

OpenResty's Branch of LuaJIT 2. Contribute to openresty/luajit2 development by creating an account on GitHub.

OpenResty - Download

Enable ozw 1.6 in HA plugin

Problem/Motivation

How to enable ozw1.6, the default in the HA plugin is ozw1.4. Ozw1.4 is no longer supported by the developer and he advised to use 1.6 to fix some discovery issues and bugs.

(Why the issue was filed)

Discovery of newer devices already supported in ozw1.6, but the definition files will never be added to ozw1.4 because the developer is no longer working on 1.4 and is now working on ozw1.8

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Open Web UI

A little bug.

When ssl is configured at true, Open Web UI button open http url instead of https.

outdated/wrong ozw config after upgrade from 0.42 to 0.6

Problem/Motivation

I used the zwave2mqtt add-on in Version 0.42 until today successfully with SPIRIT-Z thermostats from Eurotronic. Today I did the upgrade and added the config path /etc/openzwave as mentioned in the "known issues" section.

Expected behavior

Normal Operation of the thermostats as it was in 0.42

Actual behavior

The "Heat Eco" was renamed to "Heat Econ" and the command class 67 was missing the set points for Heat (67-1-1) and Heat Eco (67-1-11). I checked the files in the add-on folder and found ozwcache_0xdc1c5352.xml containing exactly these wrong/outdated definitions. I compared it with https://github.com/OpenZWave/open-zwave/blob/master/config/eurotronic/eur_spiritz.xml
this is ozw 1.6 and the definition for command classes 64 and 67 are correct.

somehow I went from an actual device config to a outdated version by upgrading from 0.42 to 0.6 of the zwave2mqtt add-on

see also my post in the community:
https://community.home-assistant.io/t/zwave2mqtt-ozw-1-6-upgrade-broke-spiritz-eurotronic-thermostat/188938

Custom Components

Problem/Motivation

I use this addon with a couple of Eurotronics SpiritZ DVRs and the auto discovery of zwave2mqtt does not support complex types like climate or fans.
But they offer the custom components where you can define it.
https://github.com/OpenZWave/Zwave2Mqtt#custom-components

Proposed changes

I see two possible solutions for this:

1. I submit the spirit Z configuration directly to zwave2mqtt and wait until it got merged and the addon got it's update.

2. I would suggest to copy the device.js file on build into a mapped folder and symlink it back to hass/devices.js

If the second proposal looks acceptable i would like to offer an PR for this

GitHub

OpenZWave/Zwave2Mqtt

Fully configurable Zwave to MQTT gateway and Control Panel using NodeJS and Vue - OpenZWave/Zwave2Mqtt

Fails to load

Fresh install. Install successful. Start fails

[cont-init.d] nginx.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...

[question] I see the version 0.5.0 includes OZW 1.6.974

Question

I see the current distribution / version of 0.5.0 includes OZW 1.6.974 - there have been several stable releases after .974. What is the expectation on new updates that include newer versions of OZW?

Cover closed when addon restarts

Hi,

small issue noticed. When the addon restarts I have one of my cover being closed.
It is always the same one and it happens for every restart.

I can't enable the debbug before it happens, therefore I have nothing to share except the config.
but I have many covers, and only one is triggered.

Please let me know what info I can give you

Thanks

very old zwave2mqtt - can this be updated?

This addon used 3.0.2.

There are a lot of improvements for zwave2mqtt. Could this please be brought to the addon?

https://github.com/OpenZWave/Zwave2Mqtt/releases

GitHub

OpenZWave/Zwave2Mqtt

Fully configurable Zwave to MQTT gateway and Control Panel using NodeJS and Vue - OpenZWave/Zwave2Mqtt

zwave2mqtt versioning and update

7f3612e

Since Frenck point me to somewhere I do not know where in above post:
Please see where to get support and questions in general. Thanks.

I must have to open another issue. Since I do NOT know where to go for support and I am really looking for help on an update openzwave and zwave2mqtt pacakge... I am running the addon in hassos and this tells me the version is:

And I am up to date everywhere... Wehere and how can I get "support" Frenck? Please point me in the right direction or help me :-).

Thank you.