[bug] not detecting all of lock manual state changes

[jaburges]

Version Build/Run method

• [X] Docker
• [ ] PKG
• [ ] Manually built (git clone - npm install - npm run build )

Zwave2Mqtt version: 3.0.0 (same on 2.2.0) Openzwave Version: 1.6

Describe the bug Locks in Z2M are not reporting certain manual state changes.

• Keypad lock on BE469 Schlage is being sent and IS detected by Z2M
• Manual internal lock turn (lock or unlock) is not being picked up by Z2M

Locks include BE469, Kwikset Z-wave lock

To Reproduce Steps to reproduce the behavior:

1. Turn internal lock mechanism
2. notice no change to state

Expected behavior The internal lock mechanism used to be picked up by Z2M

Additional context Debug logs do NOT show internal mechanism state change

[jaburges]

This issue (on searching the web goes back as far as 2018 so doesnt seem like a new thing).

Also the BE469 is in fact z-wave alliance certified: https://products.z-wavealliance.org/products/1051 so not sure I understand the part about it being non-compliant. My model is specifically BE469NX

[jaburges]

so the solution was to replace the BE469 with a BE469ZP (zwave Plus) - oddly there was an error on first inclusion but the new lock does not have the issue. NOTE - despite being securely added, it is showing in the UI as NOT securely added, and whilst i can lock/unlock the user codes are not configurable. EDIT: the new lock is now dropping commands with the new node number when locking via Z2M. This can only mean something is wrong with the stick OR some kind of interference specifically in that area? All 3 locks are pretty close, no more than 15ft from the controller. The saga continues!

Now the Kwikset continues to have the same issue. I have used Node-Red to solve this temporarily listening to 512 and 513 and submitting the correct state to 98.

[jaburges]

@robertsLando but mostly @Fishwaldo i thought I was losing my mind (turns out i'm not) As above the Brand NEW BE469ZP was securely added (showed in the UI as secure). Then for some reason changed to not secure?! weird thought I may have done something wrong. Excluded the lock, and then re-added it securely. next morning the lock is no longer showing as Secure. And validated by the fact I no longer see the user code parameters in the UI. I guess Z2M is working correctly.

Why an earth is a device losing its secure connection?

[robertsLando]

@jaburges don’t trust that flag. If you added it securely it is secure. There is an open issue for that

_{Sent with GitHawk}

[jaburges]

Normally I’d agree, however the user code Parameters (the ability to enter and store user codes in the UI) disappears once the secure flag changes to ‘No’

[robertsLando]

@jaburges That's must be a bug with the device so :confused: I never seen such things @Fishwaldo what do you think?

[jaburges]

I actually think it could be RF interference, that randomly causes dropped z-wave commands. In a 24 hour period seemingly if a certain command is dropped (not sure which) the lock stops communicating securely (and Z2M actually behaves correctly, as updates the Secure flag = No, and removes secure functionality).

[robertsLando]

@jaburges That's really weird

[jaburges]

The weirdest thing is the interference is potentially from 2.4GHz !?

[robertsLando]

@Fishwaldo

[jaburges]

everything is stable without the possible interference. I'm going to regret doing this, but i'm going to test if that is the case, and replace the possible interference and see if the issue returns - update to follow

[robertsLando]

@jaburges Ok thanks! Please close this if fixed once you test

[jaburges]

Ok tested and moved the RF interference back. I’ll close this issue, but my concern is we never got to the bottom of it. The locks just stopped working (and I ended up getting a newer Zwave plus lock)

For completeness:

The new BE469ZP has issues when dropping commands, however after a few days I guess when the zwave network may have stablized? I removed and re-added this lock and it works, reports manual state AND remains securely added.

The Kwikset locks needed the fix above from fishwaldo, but now also report manual lock state changes correctly.

No idea what caused the issue, but hope it holds as is. Thanks for your help!

[onedr0p]

I have a Kwikset 916. The file you'll need to change the index number in is smartcode.xml

[robertsLando]

I suggest to open this device related question in openzwave repo, unfortunately I cannot help with this kind of issues

---

Daniel

On 14 Jul 2020, at 22:09, Devin Buhl notifications@github.com wrote:

 I have a Kwikset 916 door lock and notice it doesn't refresh on manual lock / unlock. What file do I need to change?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.