Zwave lock BE469 and new BE469ZP

[kfly]

Just replaced a Dead Schlage lock (BE469) now cannot even do a “Query unit info” on the new lock.
Seems the new units are BE469ZP  ZP for zwave plus so I assume that is causing the issue. I use CQC/Aeotec controller as a secondary controller to the Smartthings Hub.

Guess I am out of luck with getting the new model locks to work  with CQC. Just wondering if anyone got them working in CQC as a main controller. Just trying to figure out if it’s the S2_ACCESS_CONTROL causing an issue during Aeotec replication(as a zwave remote) or something in the Driver itself that could be fixed like type and manufactor/model.
Kevin


OLD Schlage BE469
Data
MSR: 003B-6341-5044
fw: 104.21
manufacturer: Schlage
networkSecurityLevel: ZWAVE_S0_LEGACY
Raw Description zw:Fs type:4003 mfr:003B prod:6341 model:5044 ver:104.21 zwv:3.42 lib:06 cc:22,72,7A,98,86 sec:5D,85,20,80,70,62,71,63


New Schlage BE469ZP
Data
MSR: 003B-0001-0469
fw: 3.3
manufacturer: Schlage
networkSecurityLevel: ZWAVE_S2_ACCESS_CONTROL
Raw Description zw:Fs2ac type:4003 mfr:003B prod:0001 model:0469 ver:3.03 zwv:6.03 lib:06 cc:5E,98,9F,55 sec:6C,8A,22,5D,85,70,80,62,71,63,4E,72,86,7A,59,5A,73,87

[Dean Roddey]

Apparently S2 security is a completely new scheme that uses public key encryption, so a radically different animal. We never really knew how to do S0, because it requires buying the expensive SDK. It was figured out by a lot of trial and error.

If it doesn't have an option to force it to use S0, then it wouldn't ever work. If you can, it would probably work as the old model.