OH2 Z-Wave refactoring and testing... and SECURITY

[RayBe]

@chris

A fix to the “Unknown Device” problem - hopefully now devices will show up correctly in the inbox once the manufacturer information is known.

Does that mean that this is also resolved?

There is no XML-file created for the device: Remotec Z-URC 550EU

Thanks for all you hard work,
I will test and report back, thanks,
br,
Raymond

[chris (Chris Jackson)]

@RayBe

Does that mean that this is also resolved?

Unfortunately, no - sorry. This one needs some more thought to introduce a workaround to the responses this device is sending.

[RayBe]

@chris

Unfortunately, no - sorry. This one needs some more thought to introduce a workaround to the responses this device is sending.

There’s no reason to be sorry, you are doing a great job!
btw, do you want me to make a GitHub ticket for the SIS parameter?

br,
Raymond

[chris (Chris Jackson)]

Thanks.

@RayBe

btw, do you want me to make a GitHub ticket for the SIS parameter?

Yes please - then it’s on my radar

[01av (Olav)]

Of course. Ticket submitted.

[rgerrans]

@chris

Updates to the way multi-channel and multi-instance data is handled. This might impact some devices that use multiple endpoints - the main change is only during the device initialisation so it shouldn’t impact the actual use of a device.

Do we need to reinclude devices of this type to take advantage of the changes?

[chris (Chris Jackson)]

@rgerrans

Do we need to reinclude devices of this type to take advantage of the changes?

No - you should just need to update the binding.

[rgerrans]

@chris

No - you should just need to update the binding.

Great, thanks.

[mhilbush (Mark)]

Hey @chris! Been away from this for a while. Wow this thread is long…

Just installed the latest version, which is running well on my test platform.

I’ve been holding off on installing this on any of my prod systems until there’ll be no more breaking changes. Do you anticipate any more breaking changes?

BTW, I like the new STATE_UPDATE entries in the log viewer. Very helpful!

[RayBe]

when using High Power inclusion from HABmin i get:

zwave.event.inclusion_failed

in orange

[rdslw (Rado Sław)]

Do I need to use OpenHab 2.1.0 to test newest version of binding published today?

If so, is it enough to use beta channel (echo ‘deb http://dl.bintray.com/openhab/apt-repo2 testing main’ | sudo tee /etc/apt/sources.list.d/openhab2.list) ?

[chris (Chris Jackson)]

@mhilbush

Wow this thread is long…

I hope you read it all - there will be a test later

@mhilbush

Do you anticipate any more breaking changes?

I’m trying to avoid it, but yes, at some stage there will be. I suspect that it will be a little while away though, but I still need to implement the dynamic channels. So, I think it’s stable for the next few months at least…

My immediate plan is to iron out the major issues now, and get this merged to master after the next release (not exactly sure when that is, but I guess soonish).

[chris (Chris Jackson)]

@RayBe

when using High Power inclusion from HABmin i get:

That’s sad ;). I’m not really sure what it means - probably the controller returned an error that inclusion failed, but other than that, I’m not sure as there’s no further information (I think).

@rdslw

Do I need to use OpenHab 2.1.0 to test newest version of binding published today?

I think it is probably wise although I’m not 100% sure it’s needed. I can’t remember if there have been additions to the ESH/OH core or not, but to be safe, let’s say yes ;).

@rdslw

If so, is it enough to use beta channel

I guess that’s enough for the framework, but you still need to install this binding manually - see toward the top of this thread for installation info (about 6 messages down I think).

[mhilbush (Mark)]

@chris

I hope you read it all - there will be a test later

Guaranteed to fail! LOL

@chris

I’m trying to avoid it, but yes, at some stage there will be. I suspect that it will be a little while away though, but I still need to implement the dynamic channels. So, I think it’s stable for the next few months at least…

Ok, I’ll put it on the one prod system that still has a small number of nodes. The other prod system has about 30+ nodes and is about to have another 20 or so dimmers and a few more battery devices added to it.

One thing I just noticed for all my battery devices with temp sensors (ZW100, ST814, and FGMS001)… In HABmin, when I change the scale to Fahrenheit on the Temperature channel, it doesn’t seem to work. HABmin still reports it as C in the channel panel (after refreshing page), and I see in the log that the binding is not converting the reported temp to F. Is this a known issue?

Deleted node xml and deleted/readded things.

Looking at the Thing JSON for those nodes, they show this after changing the scale from C to F. Shouldn’t that be a 1?

          "label": "Sensor (temperature)",
          "configuration": {
            "properties": {
              "config_scale": "0"
            }

Edit: Looks like it might be a HABmin issue. It worked when I changed it with PaperUI.

          "label": "Sensor (temperature)",
          "configuration": {
            "properties": {
              "config_scale": "1"
            }
          },

[chris (Chris Jackson)]

@01av

I tried the last version, and I’m getting just ‘1’ (or ON) returned from alarm_number…

The reason for this is this is a notification report - not an alarm and the code I added was for alarms since alarms are not standardised within the ZWave standard…

Notifications are handled differently and should already support this if the type is decimal. What I don’t understand is why this is an OnOff type where it should be a decimal type according to the channel.xml file in the binding. Maybe something somewhere is remembering an old definition?

[nolan_garrett]

@whwkins

I had repaired tonight and was able to get it securely paired.

Any thoughts on how you did this? I am running the latest OH2 Z-Wave binding. I’ve tried pairing at this point at least 20 times - every time secure inclusion fails.

[rgerrans]

@chris So I just included my 914 and don’t see the new Alarm # Channel, just the general alarm channel in HABmin. So I went to follow @whwkins lead and add the channel to the xml file but I don’t see an xml file for the new node? I see all my other nodes that I created earlier but not for the new one I just added?

Also, is there an edit in the database to make the alarm number channel come through vs editing the xml?

Thanks as always for all the work.

[chris (Chris Jackson)]

@rgerrans

So I just included my 914 and don’t see the new Alarm # Channel

It doesn’t seem to have been added to the database yet -:

@rgerrans

So I went to follow @whwkins lead and add the channel to the xml file

You can’t add anything to the XML file - if you want to add it manually, then you need to edit the XML file in the JAR.

@rgerrans

Also, is there an edit in the database to make the alarm number channel come through vs editing the xml?

I’m not sure what you mean by this?

[rgerrans]

@chris

rgerrans:
Also, is there an edit in the database to make the alarm number channel come through vs editing the xml?

I’m not sure what you mean by this?

You answered that with the first one. I’m afraid to try to do a direct edit to the database since the last time I did I broke one of the Cooper switches (which as a tangential I don’t think ever got rolled back). I’m happy to try again though…

@chris

You can’t add anything to the XML file - if you want to add it manually, then you need to edit the XML file in the JAR.

Makes sense, though is it an issue that the node xml file didn’t get created in the \userdata\zwave\ directory?

Edit: I also noticed in the database that it’s showing User Codes and Entry Scheduling as channels but I’m not seeing those show up in HABmin. I only see Door Lock, General Alarm, and Battery channels?

Thanks.

[chris (Chris Jackson)]

Are both alarm_number and alarm_general required?