Kwikset Locks...

[dylancaponi]

I found this manual: http://s7d5.scene7.com/is/content/BDHHI ... Manual.pdf

Which has instructions for Automatic - Bolt Direction Determination (Door Handling) on page 5 - section 8. After following instructions (with lock on desk and no obstructions) and refreshing alarm request the code I get is 20. Any idea what 20 corresponds to? Then I press lock on the keypad and get code 17.

After repeating the Door Handling instructions but using my fingers to block rotation of the turnpiece in one direction I get code 21! Here are the cases I tested refreshing the browser after each attempt:
Unlock with keypad + no obstruction = 17 (error)
Lock with keypad + obstruction = 18 (lock event!)
Unlock with keypad + obstruction = 19 (unlock event!)
Lock with ExpertUI + obstruction = 19 (not registered?! but expert control panel shows "closed")
Unlock with ExpertUI + obstruction = 25 (unlock event! and control panel shows "open")
Lock with ExpertUI + obstruction (attempt 2) = 25 (no change?! but control panel shows "closed")

So it seems to debug this lock I need to actually install it or place more precise physical restrictions on it.

Also, the lock command when sent from expertUI seems to not send an alarm update although things change in the control panel. Any idea why this might be occurring?

[Mike Yeager]

How exactly are you capturing the events as the occur? I was polling each device but I figured out how to get the JSON updates using the timeStamp and it's much more efficient. Haven't missed a single event yet although some events show up in my debug log twice. I'm figuring the data update spanned the timeStamp read...

[dylancaponi]

I'm just refreshing the browser a couple seconds after:
http://rasIP:8083/ZWaveAPI/Run/devices[ ... Type.value

[Mike Yeager]

Are you up to the stage of trying to program for this yet or still just kicking the tires? I'm working in Python but learning more every day about JavaScript. Not sure I'll be changing over any time soon though...

[attilahooper]

I already posted regarding my Yale YRL220 - When I manually lock/unlock, through either the panel or button, the HA UI never updates to show change in lock status. I only receive an alarmtype=21 event. Is the yrl not sending correct msgs to update UI ? Is this a Yale specific problem ? Does the lock need to be polled at interval ?

I also have a generic motion sensor and it does influence the HA UI when motion sensed.

Code: Select all

[2014-09-14 16:32:33.286] Node 3:0 CC Security: passing decrypted packet to application level: [ 71 05 15 01 ]
[2014-09-14 16:32:33.288] SETDATA devices.3.instances.0.commandClasses.113.data.V1event.alarmType = 21 (0x00000015)
[2014-09-14 16:32:33.289] SETDATA devices.3.instances.0.commandClasses.113.data.V1event.level = 1 (0x00000001)
[2014-09-14 16:32:33.290] SETDATA devices.3.instances.0.commandClasses.113.data.V1event = Empty

[pofs]

I only receive an alarmtype=21 event. Is the yrl not sending correct msgs to update UI ? Is this a Yale specific problem ? Does the lock need to be polled at interval ?

We do not update UI on V1 events, because they are too much vendor-dependent. But there's still a few possibilities to workaround it.

1) If you know which event types and levels are sent for specific state, you may add an alarm mapping into ZDDX file.
There's an optional section for that. For example:

Code: Select all

<alarmMappings>
    <alarmMapping alarmTypeV1="15" alarmLevelV1="00" alarmTypeV2="08" alarmEventV2="01" />
    <alarmMapping alarmTypeV1="15" alarmLevelV1="01" alarmTypeV2="08" alarmEventV2="ff" />
    ... more mappings ...
</alarmMappings>

It will map device-specific V1 alarm type and level to standardised V2 alarm type and event.

I'm not sure if it helps with updating UI in the current version, but there's a huge chance it will be handled in the future.

2) Place a handler on a data holder and request state when any event comes from a lock. That will be the same as pressing update button, but it will happen automatically.

You can create a custom module for both scenarios.

[attilahooper]

Thanks for the explanation and the sample code. I've looked at openhab and openzwave for a total solution but no one there seems to have cracked locks - or yale specific. openHAB logs do demonstrate interface to ttyAMA0 but bindings to locks are missing.