Recommended Z-Wave Lock?

[Bollar]

We can subscribe to the incoming commands, then process the ones we're interested in, so yes.

Great! Here's the reply from setting user 10 to PIN 2345"

Code: Select all

   Z-Wave                          sent "Yale Kitchen Door" raw command [63 01 0A 01 32 33 34 35]
   Z-Wave Debug                    RCVD nonceFetch: node 046
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 2E 0A 98 80 60 E3 47 73 AB 7C 41 58 25 7A E7
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 70 0A (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0A 00 04 00 2E 04 71 05 70 0A FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 046, endpoint None, cmdClass 71, type 112, value 10, classSubKey 71700A

This decodes to:

Code: Select all

  0 
113 - COMMAND_CLASS_ALARM
  5 - Command REPORT
112 - User Added (see - 0x70 in table)
 10 - User 10

And deleting User 10. Indigo knows something about this command, so it adds "status update is on" to the log.

Code: Select all

   Z-Wave                          sent "Yale Kitchen Door" raw command [63 01 0A 00]
   Z-Wave Debug                    RCVD nonceFetch: node 046
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 2E 0A 98 80 E7 CB C1 95 68 59 6A C6 25 99 98
   Z-Wave Debug                    RCVD encryptedPacket: 00 71 05 21 0A (decrypted)
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0A 00 04 00 2E 04 71 05 21 0A FF
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 046, endpoint None, cmdClass 71, type 33, value 10, classSubKey 71210A
   Z-Wave                          received "Yale Kitchen Door" status update is on

Decoded:

Code: Select all

  0 
113 - COMMAND_CLASS_ALARM
  5 - Command REPORT
 33 - User Deleted (see - 0x21 in table)
 10 - User 10

[howartp]

Just updated the beta link - try new version.

It should set, clear and request codes, but not process and returned info yet.


Sent from my iPhone using Tapatalk

[durosity]

I'll test mine tonight

[howartp]

Bollar's is setting, clearing and requesting ok.

Just need to add processing for incoming results.


Sent from my iPhone using Tapatalk

[polycron]

Using a Schlage BE469 I get the following response:

Code: Select all

Z-Wave                          sent "Backdoor Deadbolt" raw command [63 02 01]
   Z-Wave Debug                    RCVD nonceFetch: node 032
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 20 0A 98 80 98 E0 D0 B7 20 9D 88 74 25 0C B8
   Z-Wave Debug                    RCVD encryptedPacket: 00 63 03 01 01 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A (decrypted)
   Z-Wave Debug                    RCVD requestReply1: 01 14 00 04 00 20 0E 63 03 01 01 2A 2A 2A 2A 2A 2A 2A 2A 2A 2A FF (hex)

I'm assuming this means the lock does not report the actual PIN since it shows ********** indicating that it has an assigned PIN?

When I queried slot 9 I received the following which I'm assuming means it was empty?

Code: Select all

  Z-Wave                          sent "Backdoor Deadbolt" raw command [63 02 09]
   Z-Wave Debug                    RCVD nonceFetch: node 032
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 20 0A 98 80 B4 C9 D6 6F 0F F0 99 1F 25 36 61
   Z-Wave Debug                    . .  nonceReport: requeuing 1 unsolicited packets
   Z-Wave Debug                    RCVD encryptedPacket: 00 63 03 09 00 (decrypted)
   Z-Wave Debug                    RCVD requestReply1: 01 0A 00 04 00 20 04 63 03 09 00 FF (hex)

Jeff

[howartp]

Some wierd results there.

I don't think your device is supporting the same lock statuses - OE 63 03 should be 08 63 03 for reporting alarm_class commands.

And 04 63 03 should be the same, though the 09 00 FF matches the same spec.


Sent from my iPhone using Tapatalk

[polycron]

I can run some additional tests tonight on all 4 of my Schlage locks.

If you want, I can post the results here or I can PM them to you if you are interested. I will also attempt to set a PIN and delete a PIN to see if that matches up with what you would expect based on the spec.

Jeff

[howartp]

Pm them and I'll look later in week. Busy tonight and tomorrow.


Sent from my iPhone using Tapatalk

[Bollar]

Some wierd results there.

I don't think your device is supporting the same lock statuses - OE 63 03 should be 08 63 03 for reporting alarm_class commands.

And 04 63 03 should be the same, though the 09 00 FF matches the same spec.

I don't know exactly what the 08 means, but I don't think it's a pertinent part of the returned message. Maybe it's a checksum or product identifier?

[durosity]

Fyi Adding a PIN is now working perfectly on my lock. The GET function is not though.

Action Group zz get pin
Zwave Lock Manager Debug getUserPin action called
Zwave Lock Manager Debug Indigo lock selected: 1414137297
Zwave Lock Manager Requesting PIN for user 4
Z-Wave sent “Hall - Front Door Lock” raw command [63 02 04]

but then no return from that.

Deleting pin works too:

Action Group zz remove pin
Zwave Lock Manager Debug clearUserPin action called
Zwave Lock Manager Debug Indigo lock selected: 1414137297
Zwave Lock Manager Clearing PIN for user 4
Z-Wave sent "Hall - Front Door Lock" raw command [63 01 04 00]
Z-Wave received "Hall - Front Door Lock" status update is on
Zwave Lock Manager Debug -----
Zwave Lock Manager Debug Lock Status Report received:
Zwave Lock Manager Debug Raw command: 01 0A 00 04 00 63 04 71 05 21 04 FF
Zwave Lock Manager Debug Node: 99
Zwave Lock Manager Debug User: 4
Zwave Lock Manager Debug Status: User deleted
Zwave Lock Manager User 4 removed from lock
Zwave Lock Manager Debug -----

[Bollar]

Fyi Adding a PIN is now working perfectly on my lock. The GET function is not though.

Which lock do you have? I have a YRD240 arriving tomorrow.

[durosity]

Yale Keyfree which I believe uses the exact same Z-Wave module as the keyless TRD240.. so I’d expect them to behave identically (assuming the same firmware, etc)

[estopka]

Hi, have a Schlage FE599 Z-Wave lock and was super excited (already bought license excited!) about Indigo 7, and its native support for locks. I have not had luck trying to get the Schlage lock to sync up when creating a new device. Here is what I have done:
Brought my Aeon dongle to the installed lock, pressed association button and held down, entered [six digit master code on Schlage lock]+"Schlage"+0 to make sure the lock was disassociated from the network.
Pressed dongle button to turn off programming.
Pressed dongle button again to begin association, entered [six digit master code on Schlage lock]+"Schlage"+0 to begin association. Dongle stayed solid, and Shlage Lock stayed orange, about the time that it takes to associate a new device.
Pushed button on dongle to remove from association mode, and then plugged back into Indigo Server.

Went into Indigo, Devices, New, Z-Wave, and selected the newly picked up node for the lock (I believe it was called keypad lock)
Hit Sync.
Received several promising indicators on the Indigo activity log, return path, and even picked up the manufacturer and model information, but then Indigo always times out.

Any thoughts or suggestions?

Thanks as always.

[matt (support)]

For the initial key exchange to work with the module, Indigo has to handle the inclusion. So exclude it again, then include it using the New with Encryption Enabled button inside the sync dialog. Once the Z-Stick is inclusion mode go to the lock and follow its magic steps to have it pair (note the Z-Stick stays in the Mac and you never press its button). Indigo's Event Log window should show you the result. If it doesn't work you can copy/paste its contents and we can troubleshoot further.

[estopka]

OK, tried the process, excluded the controller, so the node no longer showing up as available, entered inclusion mode in device>new,
(note the lock is well outside of the range of the controller)
Entered the Schlage codes to set in pairing mode, and the node did not show up on the controller. Note, the Schlage doesn't go into pairing mode very long, maybe 2 seconds max, before timing out.

So....

Unmounted the lock (keypad and battery compartment) from the door, brought it into the room with the controller (which was still plugged into the indigo server), and started the process:
New Device
Z-Wave
Select "New with Encryption Enabled", controller goes into search mode
Entered the Schlage code into the keypad, and the controller now finds the lock, and sets me up with a new node, 'Keypad Door Lock'
Hit Sync, and Indigo does its good thing, finds neighbors, gets codes, all the right things and most importantly the lock now works.

Problem again is, when I put the lock back in the area it will be, it is outside the range of all the neighbors that were found when I did the initial "new with encryption" search.

I've tried to work my way outwards from the controller, syncing in the hopes that new neighbors will be found, but this is not working. I'm afraid my only option might be to start at step 1, but bring my Indigo Server (with the controller plugged into it) to the installed lock, start the whole process from there, so that the neighbor list will get built properly. Is this the sanctioned answer?