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

[chris (Chris Jackson)]

@romain

I don’t know if I’m telling you something obvious, but did you try what your logs suggest ?

Well - this is a good clue - but for a slightly different reason.

The log is not from the right version of the binding - it’s an old version that doesn’t support security. It has security messages, but it doesn’t work.

[chris (Chris Jackson)]

@romain

The problem still seems to be

The 7FFFFFFF business normally means the binding hasn’t received the manufacturer information from the device.

The log seems to confirm this, but I don’t really know why it’s not working - I could guess that there’s a communication issue - ie it’s too far away from the controller? Is that likely?

It does look like it’s securely included ok, but there are a number of retries. It could also be caused by something else with security, but it’s hard to diagnose unfortunately.

[romain]

Thanks chris for your help.

@chris

The log seems to confirm this, but I don’t really know why it’s not working - I could guess that there’s a communication issue - ie it’s too far away from the controller? Is that likely?

Very unlikely. I stick the device to the controller when I give it a try.

What do you think about the “Unknown command class 0xffffff84” ?

2018-02-24 19:59:24.086 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 28: Unknown command class 0xffffff84

[chris (Chris Jackson)]

@romain

What do you think about the “Unknown command class 0xffffff84” ?

I think it’s probably a small bug, but unlikely it’s the actual problem.

Another thought - try deleting the XML for this node and restarting the binding - let’s see if that helps. Provide the log if it doesn’t.

[paulfaure]

This is the binding that I have Active:

openhab> bundle:list | grep ZWave
246 │ Active    │  80 │ 2.3.0.201802081624     │ ZWave Binding
247 │ Installed │  80 │ 2.2.0                  │ ZWave Binding
openhab>

Does it not have security?

[5iver (Scott Rushworth)]

You can’t have two versions installed. Do a bundle:uninstall 247.

[chris (Chris Jackson)]

@paulfaure

Does it not have security?

It is not a binding that I have in my list as having created - no.

The log entries from classes like SecurityCommandClassWithInitialization don’t even exist in the binding so this is definitely not the right version.

[paulfaure]

Thanks @chris
Could you send me a link to your latest build?

[chris (Chris Jackson)]

The link is right at the top of this thread.

[paulfaure]

I must have looked at the top of the thread a half dozen times… kept missing the first line !
Got the right one now

Here are my logs:
http://faure.ca/~paul/openhab_feb25.log

I seem to be missing: /home/AD.FAURE.CA/openhab/openhab/userdata/zwave/network_0184eb0f__node_9.xml

Is that created during the inclusion? If so, i will redo that part…

[romain]

Hi @chris

Thanks for your message.
I’ve deleted XML and restarted the binding : nothing more than the usual “unknown device”, “manufacturer not set”, etc… Please find here the operation logs.

I noticed today something I didn’t understand before : even if the discovery fails, the logs show that openhab see the buttons pressed (I have an event “CENTRAL_SCENE” when I press a button). Is there a way to declare manually the device ? that could stop openhab trying to retry and retry the device identification ?

I also notice some

2018-02-25 20:28:22.275 [ERROR] [col.security.ZWaveSecureNonceTracker] - NODE 28: SECURITY_ERROR Device message contained nonce that is unknown to us, id=-55.

but I don’t know if it is related.

And finally, after several wake-ups, any new dialog initiated by the device wake-up finishes by

“Unknown command class 0xffffff84”

I don’t know if this last step prevents the binding to discover more, or if it is really unrelated.

[chris (Chris Jackson)]

@paulfaure

Is that created during the inclusion? If so, i will redo that part

No - it’s created during initialisation. However, if you have a secure device, you MUST redo the inclusion as it absolutely must be done with this binding. You have to reset the device then include it with the binding running.

[peterd (pd)]

@chris

here

Hi Jack,

It seems, I’ve the some problems with 5 brand new fibaro windows sensors (latest model). 3 work perfect, 2 one don’t show on/off, get off from time to time etc.) When do you plan to bring the current test binding in the master version?. I use openhabian latest version, so the question is, does it makes sense to do all the manual stuff or waiting for your master binding … Using openhabian, is there still the seriell topic valid? Thx
Peter

[stratt (Steven Tratt)]

Does this development binding work with OH2.3 or should I stick to OH2.2?

[Jeff_Donze]

Hi, where can I find the log shown in the picture here? Thanks!

[Jeff_Donze]

It’s working for me: openHAB 2.2.0 Release Build

$ openhab-cli console
openhab> bundle:list | grep -i zwave
226 │ Active │ 80 │ 2.3.0.201802082157 │ ZWave Binding

I think it’s mentioned earlier: uninstall the 2.2 binding via PaperUI, download to /usr/share/openhab2/addons and restart openhab.

This version got my Schlage lock working since it has security. What’s not working is any feedback from devices. For example, when I physically lock to deadbolt it doesn’t update in OH. That’s what I’m struggling with now.

[DanielMalmgren]

@Jeff_Donze

It’s working for me: openHAB 2.2.0 Release Build

But he asked the other way around From what I can understand it works in both 2.2 and 2.3.

[chris (Chris Jackson)]

@stratt

Does this development binding work with OH2.3

Yes - the binding name is version 2.3 and it works fine with OH 2.3.

@Jeff_Donze

Hi, where can I find the log shown in the picture here? Thanks!

http://www.cd-jackson.com/index.php/openhab/zwave-log-viewer

[5iver (Scott Rushworth)]

@Jeff_Donze

What’s not working is any feedback from devices. For example, when I physically lock to deadbolt it doesn’t update in OH. That’s what I’m struggling with now.

Some locks, including the Schlage Connect series, do not report lock/unlock through the lock_door channel. You will need to create some rules and utilize the alarm_raw channel if you want to have a single Switch item to display the lock state. Here is an example…

Zwave - Yale YRD220 Lock

Here is my current rule for parsing alarm_raw. My locks (Schlage BE469) do not update the lock_door channel, so I use alarm_raw to update the items linked to lock_door, and base rules off of that item’s state. Maybe all locks behave this way? You’ll find several examples of using the JSONPATH transform to parse the data in the lambda. This can be tricky though, because JSONPATH will throw an exception if the element name you are searching for does not exist in the JSON. I haven’t had any issues…

More discussion here…

Schlage BE469 - Zwave binding with security - missing features

Continuing the discussion from here specifically around the Schlage BE469 lock: I am using the lates snapshot of the z-wave binding and tryign to integrate with my Schlage BE469 deadlock. I have created a rule to determine the ‘state’ of the lock based on the ‘notification_access_control’ property. From experimentation and help from user @5iver I have determined the following: 1 = Locked manually 2 = Unlocked manually 5 = Locked with keypad 6 = Unlocked with keypad 9 = Auto lock 11= …

[paulfaure]

Hi @chris Could you review the logs and let me know why I can’t add my lock to the network?
http://www.faure.ca/~paul/openhab_feb27.log
It seems to error out even before I start joining the network on the lock.
Thanks,
Paul