Schlage lock logging support still broken in v1.4
Posted: 27 Sep 2013 12:21
I was very excited about 1.4 and the promise of lock logging support, but Schlage locks still don't work right. The interview (even when forced) never returns that they are Lock Logging capable. And they seem to report the last used code as an alarm on 0x71.
This thread seems to imply that 0x71 should be supported in this version - but it is not: http://en.z-wave.me/content/proper-door-lock-support
I think the confusion is that 0x71 is alarm not lock logging and it looks like schlage uses the alarm command class to report the code entered.
From the log:
[2013-09-27 02:12:49.854] Node 5:0 CC Security: passing decrypted packet to application level: [ 71 05 10 02 ]
[2013-09-27 02:12:49.855] Node 5:0 CC Security: Got secure frame, but Command Class 0x71 isn't registered, instantiating it as not supported
[2013-09-27 02:12:49.856] Trying to create command for unknown CC 0x71
[2013-09-27 02:12:49.857] Command Class 0x71 is not supported (requested for node 5:0)
71 05 10 XX where XX refers to the number of the user code.
1) Any plans to support Alarm very soon? (we're so past our deadline we have to get Schlage support to work or use other controller hardware)
2) Is there any way with the current version to just bind to that signal? We are not using the UI and don't care about that - we just need a way to get that information out (besides parsing the logs). Preferably so it shows up when get updates like this: ZWaveAPI/Data/TIMESTAMP as a piece of data returned - but I'll take just about anything at this point.
Thanks!
This thread seems to imply that 0x71 should be supported in this version - but it is not: http://en.z-wave.me/content/proper-door-lock-support
I think the confusion is that 0x71 is alarm not lock logging and it looks like schlage uses the alarm command class to report the code entered.
From the log:
[2013-09-27 02:12:49.854] Node 5:0 CC Security: passing decrypted packet to application level: [ 71 05 10 02 ]
[2013-09-27 02:12:49.855] Node 5:0 CC Security: Got secure frame, but Command Class 0x71 isn't registered, instantiating it as not supported
[2013-09-27 02:12:49.856] Trying to create command for unknown CC 0x71
[2013-09-27 02:12:49.857] Command Class 0x71 is not supported (requested for node 5:0)
71 05 10 XX where XX refers to the number of the user code.
1) Any plans to support Alarm very soon? (we're so past our deadline we have to get Schlage support to work or use other controller hardware)
2) Is there any way with the current version to just bind to that signal? We are not using the UI and don't care about that - we just need a way to get that information out (besides parsing the logs). Preferably so it shows up when get updates like this: ZWaveAPI/Data/TIMESTAMP as a piece of data returned - but I'll take just about anything at this point.
Thanks!