I several devices, that (I thought) before yesterdays snapshot would update the display when triggered locally (for example in habpanel or PaperUI > Control.
At this point I have been able to get a DSC26 Micro Switch G2 to do this by setting parameter 80 to Basic CC Report Sent.
I thought previously I had the NAS-WR01ZE Metered Plug working this way. But, It now does not update when switched. And I don’t see parameter 80 in it’s configuration parameters.
(Side note on this device: I know I had it reporting the voltage (with and paperui generated item) but, now I have this item in a .items file as shown below. But, it always shows as 0.0)
Number Plug_11_V "Voltage [%.2f]" {channel="zwave:device:16500637f6a:node11:meter_voltage"}
I also have added a NZW36 Smart Plug. It shows no configuration parameters and the folowing attributes:
Actually, since I buggered it all up when I updated to 1360 I have deleted and re-added all my zwave devices including the controller over the past 48 hours.
Also, I just added a brand new NZW36 and it shows 3 topics under Device Configuration and nothing under Configuration.
I’m also wondering if those two devices should be combined, seems to be just different type and id’s, @chris what do you think? (Yes, I would have some spare time to do that )
Yes - I agree. I’ve just deleted the older of the two as it had less information. I didn’t add the other device IDs to the newer entry though, so if you don’t mind, that would be great .
I did a diff on the 36 and 39 xml files on that github page.
The files are 781 lines long and only about 5 differences. The first of which is line 30 and the diff is the name, i.e. 36 vs 39. The rest look like formatting or java stuff.
As for trying what he said…
The 39 shows association groups, but mine are empty (habmin) and the ui updates on local switch.
The 36 shows no association groups, so yeah, not set.
Eric Maycock <ericm@inovelli.com>
3:59 PM (1 minute ago)
to Eric, me
Hi Mac, other Eric here. Thanks for writing in. We have pushed the configuration parameters to open-z-wave so
if the version of OpenHAB you are using has the latest open-z-wave config, you should be already set. If not,
you can see the configuration files from their github:
https://github.com/OpenZWave/open-zwave/tree/master/config/inovelli
As for the problem you are seeing, I would guess that during inclusion the hub did not add its node id to the
NZW36s association group 1. Can you try that and let me know if it fixes the issue? Group 1 is the lifeline group
for the NZW36 and is used to send basic reports for when it is turned on/off. It should have the node ID of your
z-wave stick in it. Usually that is node id 1.
Eric M
VP Technology | Inovelli
We must be looking at different files! Each are ~25 lines with 2 parameters. The one for the NZW39 is missing most of the configuration parameters that I deciphered from the SmartThings DTH. As Chris mentioned, these are OpenZWave xmls and are not compatible with OH. If they had all the info, someone could use them to pick out the parameters to manually add though.
The OZW file format is reasonably simple. Look for the command class 112 (which is configuration) -:
<CommandClass id="112">
<Value genre="config" index="1" value="0" label="LED Indicator Control" units="" size="1" min="0" max="255" type="list">
<Help>Choose if you want the LED indicator to turn on when switch is on or off or disable completely.</Help>
<Item value="0" label="LED on when switch is off"/>
<Item value="1" label="LED on when switch is on"/>
<Item value="2" label="LED is disabled"/>
</Value>
<Value genre="config" index="2" value="0" label="Automatically turn switch off after interval" units="seconds" size="2" min="0" max="32767" type="short">
<Help>Automatically turn the switch off after this many seconds. 0 is disabled</Help>
</Value>
</CommandClass>
In here you find an entry for each parameter - there are 2 (index 1 and 2). These are the parameter IDs in the OH database - the other information ought to be reasonably self explanatory (label, min and max values, size etc) - these all have similar names in the OH database.
You can then add options into the OH database - these are the item tags in the OZW database - again the data should be self explanatory (value and label).