Core: Missing support of Z-Wave device (Inovelli LZW30-SN)

Created on 13 Oct 2019  路  7Comments  路  Source: home-assistant/core

Home Assistant release with the issue:

v0.100.1

Last working Home Assistant release (if known):
None

Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io

Integration:

https://www.home-assistant.io/integrations/zwave/

Description of problem:
Missing a support of the devices Inovelli LZW30-SN
https://github.com/OpenZWave/open-zwave/blob/master/config/inovelli/lzw30-sn.xml

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):


Traceback (if applicable):


Additional information:

zwave stale

Most helpful comment

We're currently on an older OpenZWave build (1.4) and the OpenZWave master repository is for OpenZWave 1.6. I'm in the process of updating the Home Assistant zwave component to use OpenZWave 1.6 but it's still a few weeks out at the earliest.

All 7 comments

Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with a integration (zwave) you are listed as a codeowner for? Thanks!

We're currently on an older OpenZWave build (1.4) and the OpenZWave master repository is for OpenZWave 1.6. I'm in the process of updating the Home Assistant zwave component to use OpenZWave 1.6 but it's still a few weeks out at the earliest.

@cgarwood Is it possible to sync xml config files with openzwave before v1.6 became alive?

A user from the Inovelli forums has created a set of device files compatible with 1.4. Instructions are here.

You could try your luck and submit a PR to the HA fork of OZW with those files. It looks like a couple of PRs for device files have been accepted "recently", but YMMV.

Easiest would be to just maintain your own files for now.

I'm in the process of updating the Home Assistant zwave component to use OpenZWave 1.6 but it's still a few weeks out at the earliest.

Is there another issue or something I can watch/subscribe to in order to see when this is released? I did some searching but didn鈥檛 see one.

@ViViDboarder We've changed direction a bit from the original plan... Still working on OZW1.6 support but its going to end up being a new component using a new method of communicating with OpenZWave via MQTT. This will be using an MQTT interface supported by the OpenZWave core developers and will allow for multiple zwave instances and solves the problem of having to wait multiple minutes for all of the nodes to be queried before zwave devices are usable when you restart Home Assistant.

https://github.com/cgarwood/python-openzwave-mqtt is the python wrapper for it we're working on, so that's the best place to follow for now. It's still pretty early/basic.

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

missedtheapex picture missedtheapex  路  3Comments

sibbl picture sibbl  路  3Comments

arangates picture arangates  路  3Comments

kirichkov picture kirichkov  路  3Comments

bdraco picture bdraco  路  3Comments