(Zwave 1.4) Dimmer Support in HomeAssistant?

EricM_Inovelli · November 7, 2019, 11:49pm

The config files for open-zwave based hubs has been posted. We’ll work on getting these committed into the open-zwave repository, but for those that want to use them manually, they are there.

cba123 · November 8, 2019, 12:32am

@EricM_Inovelli .
Can you arrange to send the dimmer info to the OpenHab Zwave developer (Chris) so that the new dimmers get into their Java-based Zwave device database used in OpenHab:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devices

Knoxie89 · November 10, 2019, 7:17pm

Are these OZW1.4 config files for HomeAssistant? Do you have those available? HASS is apprently stuck at 1.4 for foreseable future??

cgarwood · November 10, 2019, 9:56pm

Just a heads up, the master branch of OpenZWave is for OpenZWave 1.6 and Home Assistant is still on OpenZWave 1.4. There’s an effort underway to get Home Assistant on OpenZWave 1.6 but my guess is it will be the end of the year before Home Assistant’s updated to 1.6. My understanding is 1.6 config files are not compatible with 1.4.

natemate · November 10, 2019, 10:22pm

Thanks for this. @EricM_Inovelli, any chance for 1.4 config files? I try to stay away from HA upgrades for as long as I can since I have a working set up and no desire to upgrade.

Knoxie89 · November 11, 2019, 12:43am

You can create support yourself in the short term by doing the following:

Shutdown Homeassistant.
Download the ‘config’ directory from the open zwave github. It just needs to be the [1.4 branch version]. And put it somewhere your Homeassistant can access it.
Place these new files in the inovelli directory inside the config directroy. Download them/copy them from here.
In the ozwave config directory edit the manufacturer_specific.xml to include the following xml after the entry for innovelli.

< Manufacturer id=“0312” name=“Invoelli”>

with

 <Manufacturer id="031E" name="Inovelli">
    <Product type="0002" id="0001" name="LZW30-SN Switch Red Series" config="inovelli/lzw30-sn.
    <Product type="0001" id="0001" name="LZW31-SN Dimmer Red Series" config="inovelli/lzw31-sn.xml"/>
  </Manufacturer>

In your configuration.xml add the config parmater to your

zwave:
config_path: < path to ozwave config >
Pray

You should now, in theory be able to remove your node from the zwave network (if you already added it.) And re-include the node. If you haven’t added the node yet, you should just be able to include it.

EricM_Inovelli · November 13, 2019, 12:00am

So it does look like those config files will work with 1.4. That is good to know.

@cba123 I’m working on getting the xml files & info for Chris this week. Hopefully I’ll have some good luck getting these things integrated into OpenHAB.

datzent83 · November 21, 2019, 1:07am

Is there any update on getting the config file into the OpenZWave? I just got my dimmers but cant fully utilize them because home assistant doesn’t recognize the dimmers correctly.

doublepedaldylan · November 22, 2019, 1:51am

@datzent83 - Use the process outlined by @Knoxie89 above. It’s an issue on HA’s end, not Inovelli. Home Assistant hasn’t updated their OZW version, and it sounds like it’s going to be a while still.

I have access to all listed parameters currently after following the process.

cba123 · November 22, 2019, 10:49pm

@EricM_Inovelli Thanks, I saw the Red dimmer is in the database, but the Black dimmer hasn’t been added yet. Did you submit for both?

I am in no rush since I am in Canada and the dimmers still aren’t available to us yet, so I am sure someone in the US will get this sorted out and working before then. The switches were probably added by someone in the US since it was there before Canada could order those on amazon.ca and I don’t think you knew that OpenHab was not based on OpenZwave yet.

platup · November 23, 2019, 8:25pm

Good news in Home Assistant’s State of the Union

Quote:

Z-WAVE

We’ve been working with the Open Z-Wave developers on a new solution that will allow us to migrate to the new Open Z-Wave 1.6 relase and make it easier to stay up to date in the future.

We’re expecting to launch an MVP soon. This effort is driven by @cgarwood.

Source code

EricM_Inovelli · November 25, 2019, 5:27am

I will get the black series up as soon as possible.

nanreh · November 28, 2019, 9:53pm

Any update on getting the black series xml files posted somewhere? Sorry to be impatient, really looking forward to having these working fully with HomeAssistant.

nanreh · November 28, 2019, 10:16pm

FWIW, using the xml files for the red series works. Shitilly, but it works.

cmminear · November 30, 2019, 11:28pm

Can you point me to the red series dimmer in the database, I cant find the lzw31-sn.xml

ldd · December 6, 2019, 10:15pm

I followed a somewhat different method from yours. I took the files from Inovelli’s repository and edited the device files to make them conform to the format that Open Zwave 1.4 expects. (I deleted the Metadata elements along with their contents, and changed the Product opening tag to remove the Revision attribute and set the xmlns to that expected by 1.4.) I referred to your method to make sure I was not forgetting anything. I found two issues with your process:

Your XML fragment in step 4 is incorrect. The first Product tag is incomplete: the config attribute on that tag is truncated, never terminated and the tag itself is not terminated.
For those folks who have already added the node to their ZWave network, it is not necessary to exclude the switch from the network and reinclude it to get the benefit of the fixed Open ZWave database. Instead, while Home Assistant is shut down, they can edit the zwcfg_[hash].xml file. The [hash] part of the name is different for installations. It is a hex number like 0xdeadbeef. They need to find in that file the Node element with an id that corresponds to the ID of the node they’ve added. Then they need to delete that element from start tag to end tag, and all contents of the element. They need to do that for all nodes for which they want HA to fetch the information anew from the database of ZWave devices. After they restart HA and the ZWave network is completely initialized, the nodes will have the correct device information. This is what I did. I did not have to exclude the node and reinclude it.

datzent83 · December 13, 2019, 10:47pm

Why not include this into OZW 1.4?

ldd · December 14, 2019, 1:20am

OZW 1.4 is no longer in development. The developers of OZW do not accept pull requests for that version anymore.

LongDono · December 16, 2019, 5:21pm

I received black and red switches last week and had a quick look at re-constructing the zwcfg_[hash].xml but aside from changing the name, quickly decided I didn’t have the patience for it that day.

We should collect and store the proper device template for each of the black and red switches, and black and dimmers so that everyone can manually update their zwcfg* files rather than trying to re-create the wheel. I suspect we may be waiting a while before HA moves to OpenZwave 1.6 due to the custom 1.4 in HA.

Right now, my Inovelli switches turn on or off with the generic device information, but instead of the device status updating immediately, it stays in the on or off state until about 5-10 seconds, then it updates. No changes can be made to the power state during this time. If you make the mistake of toggling the power more than once, the events will queue up and it will take a while for the sequence to complete.

akguwabr · December 18, 2019, 9:30pm

Just found this thread. My switches were showing up as unknown in HA. I merged the files and removed/re-added the nodes to HA. So far so good.

I did merge the configs provided by Inovelli and OZW v1.4

Here is the repo with updated manufaturer_specific.xml and xml product specs:

https://github.com/bmtKIA6/home-assistant-Inovelli-openzwave