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

5iver · July 19, 2018, 10:59pm

Sent you a PM.

5iver · July 19, 2018, 11:01pm

If @r27 doesn’t get to this, I will play with it later tonight to get you some logs.

mhilbush · July 19, 2018, 11:09pm

FTR, I have three versions installed across 3 systems, and none of them exhibit the issue.

2.4.0.201807152137
2.4.0.201807181924
2.4.0.201807182237

I’ll install the latest on my test system and report back what happens.

r27 · July 19, 2018, 11:12pm

Installed this v and tested dimmer and lock. Works as expected.

mhilbush · July 19, 2018, 11:23pm

Playing catchup on this issue, as I’ve been offline for a couple hours.

@chris I’m running this version, which I just installed from post #1. Is this the one with the additional debug?

184 │ Active    │  80 │ 2.4.0.201807192329     │ org.openhab.binding.zwave

Is the issue specific to the DZMX1? Has it been observed on any other type of device?

r27 · July 19, 2018, 11:24pm

All battery powered devices with this version online as unrecognized devices.

5iver · July 19, 2018, 11:44pm

My plans changed, so I’m in for the night and can do some more testing. Using 2.4.0.201807192329, which should have the added debugging, deleting/rediscovering Things turned up DZMX1 and DZS15 as having the issue. Everything else I have appears to have come up OK.

Did you delete your zwave Things?

mhilbush · July 19, 2018, 11:46pm

Well, that explains why I can’t recreate it. I don’t have either of those devices.

r27 · July 19, 2018, 11:46pm

Yes I did, deleted all z-wave items. Added back. Restarted. So far only issue is battery powered nodes.

5iver · July 19, 2018, 11:47pm

Have they woken up?

r27 · July 19, 2018, 11:47pm

I triggered motion sensors and door sensor. That usually help, but not now.

mhilbush · July 19, 2018, 11:48pm

Did you mean to say Things?

r27 · July 19, 2018, 11:49pm

Sorry yes. I keep saying items when I mean things. My bad.

5iver · July 19, 2018, 11:50pm

Which devices do you have? Maybe this is another device affected by the issue.

r27 · July 19, 2018, 11:54pm

I was able to get one of the motion sensors to work by opening case. Now have to figure out what to do with door sensors. I’ll be back in 45 min. Thank you guys!

5iver · July 19, 2018, 11:57pm

Triggering them will not wake them up. Opening the case usually does it, but sometimes there’s a little hole or button. The manual usually tells you how.

They will wake up eventually on their own too.

5iver · July 19, 2018, 11:59pm

I’ve restarted a couple times, but haven’t found anything in the logs for ‘getConfigDescription’.

mhilbush · July 20, 2018, 12:12am

Same here. Nothing containing getConfigDescription in my logs.

5iver · July 20, 2018, 12:26am

I found the log entry after deleting/rediscovering a Thing. But this is one of the affected devices, so you may not see it. I’ll send my log to Chris. I also updated to the latest OH snapshot 1313, which still horribly breaks JSR223 .

2018-07-19 20:19:35.864 [DEBUG] [openhab.binding.zwave.internal.ZWaveConfigProvider] - No nodeId found in getConfigDescription thing:zwave:device:07cb40a2:node19

r27 · July 20, 2018, 1:15am

I am still experiencing problems with dimmers. They don’t report status if manually operated.
Door contacts don’t wake up and report status, same with motion detectors. With previous (stable) version of binding all devices work fine. Door contacts and dimmers report status immediately.