Zipato mini keypad and Zwave Lock Manager

[krissh]

howartp has been kind enough to include support for this keypad. Many thanks! I thought I'd write a few words on how to use it with the plugin.

Link to keypad info and manual

The device is battery operated, so you'll need to wake it so it can receive commands. To wake it, I've found the easiest is to send the command, and at the same time trigger the tamper switch and after 1-2 seconds reset the tamper switch. Alternatively you can set it to "always awake" by changing parameter 5 to 3, as described in the manual. Note that it will not accept codes and RFID tags in this mode, but it can be used for setting user codes.

At first you will need to set user codes. You can set pin codes (4-10 digits) or use RFID tags.

To set pin codes you can just use the "Set user pin" action of the plugin.

To set an RFID tag you'll need to do the following:
- Set the plugin to debug log
- Press "Home" or "Away" button and place the RFID tag on the keypad.
- You will receive a log output similar to this:

Code: Select all

   Z-Wave Lock Manager Debug       -----
   Z-Wave Lock Manager Debug       User Code Status received:
   Z-Wave Lock Manager Debug       Raw command: 01 14 00 04 00 0D 0E 63 03 00 00 XX XX XX XX XX XX XX XX XX XX 38
   Z-Wave Lock Manager Debug       Node:  13
   Z-Wave Lock Manager Debug       User:  0
   Z-Wave Lock Manager             Status:  User code 0 is blank [Node: 13]
   Z-Wave Lock Manager Debug       -----

- The 10x XX is the RFID code, which you'll need to copy
- Use the "set user pin" action and paste the RFID code.

That's it, you should now be able to set "home" and "away" using codes or RFID tags.
You'll receive log output like this and can make triggers for locking/unlocking for different user ids

Code: Select all

   Z-Wave Lock Manager             Status: Door unlocked by user 11 [Node: 13]
  Z-Wave Lock Manager             Status: Door locked by user 1 [Node: 13]

If invalid code or RFID tag is used, this will occur in the log:

Code: Select all

   Z-Wave Lock Manager             Status:  User code 0 is blank [Node: 13]

Note that the keypad is not yet supported by Indigo, so the Lock/Unlock state of Indigo does not update.

[howartp]

Thanks for writing this up!

Peter

[matt (support)]

That is awesome you all were able to get this working.

Thanks for figuring this out, getting it added to the Lock Manager plugin, and documenting it!

[Coolcaper]

Thanks for the write up!!

Works for my DHS RFID Wall Scene Controller as well which I think is a clone made by Wintop or vice vera!

http://www.digitalhomesystems.com.au/do ... n%20v1.pdf

[jonhug]

Currently I am seeing the below error message when using the Zipato mini keypad, does anyone know what it is ?

Z-Wave received "Entry Control - Home/Away Mode" status update is on
Z-Wave Lock Manager Status: Door locked by user 1 [Node: 61]
Z-Wave received "Entry Control - Home/Away Mode" status update is off
Z-Wave Lock Manager Status: Door unlocked by user 1 [Node: 61]
Z-Wave Lock Manager Error Error in plugin execution ReceivedBroadcast:

Traceback (most recent call last):
File "plugin.py", line 320, in zwaveCommandReceived
File "plugin.py", line 496, in triggerEvent
KeyError: key id 176739271 not found in database

[howartp]

That's looking for a trigger with ID 176739271 I believe - do you have one with this trigger ID? (Look at the columns in Indigo client when in triggers)


Sent from my iPhone using Tapatalk

[elov]

I have a problem with the Zipato Mini Keypad, mine does not identify itself with props.IsLockSubType = True.

So I manually changed the plugin code and removed the filter for props.IsLockSubType in all the event and actions.xml and the plugin.py.
I also made a change to the zwaveCommandReceived function so it would add my node by dev.name.startswith instead.

Code: Select all

		if nodeId not in self.checkedIDs:
			self.debugLog(u"Checking if node %s is a Lock..." % (nodeId))
			self.checkedIDs.append(nodeId)
			#for dev in indigo.devices.iter("indigo.zwave,props.IsLockSubType"):
			for dev in indigo.devices.iter("indigo.zwave"):
				if dev.name.startswith("025 - "): 
					dNodeID = dev.ownerProps['address']
					if dNodeID == nodeId:
						self.lockIDs.append(nodeId)
						self.debugLog(u"Node %s added to list of lockIDs" % (nodeId))

And this works! Everything else is OK and I can use the keypad and RFID tags.
But I wonder if there is an other way of changing the props.IsLockSubType to True for my device instead?

[howartp]

You'd be better using the device id rather than startswith("025 -") if you're going to hardcode it.

Matt/Jay will need to update the device definition for that device to set isLockSubType


Sent from my iPhone using Tapatalk

[krissh]

Actually, Matt added a property called isZipatoKeypad that can be filtered on. If you haven't already done so, the keypad needs to be re-synced after Indigo 7.0.3

The filter that can be used is

Code: Select all

	deviceFilter="indigo.zwave, props.IsLockSubType, props.IsZipatoKeypad"

I have a version of the lock manager plugin working with the keypad, I'll see if I can forward it to howartp tonight.

[eco]

I have a clone of this keypad which describes itself as a "Schlage Link Mini Keypad RFID":

Manufacturer: Digital Home Systems
Model: RFID Keypad, firmware 0.28

I can manually update the plugin so that its recognised but it would be great to have it added to the list of similar devices so that it get's picked up automatically in any updates from here.

The full device info is:
Model: RFID Keypad
Model ID: 61314501
Manufacturer: Digital Home Systems
Manufacturer ID: 0097
Protocol Version: 3.67
Application Version: 0.28
Model Definition Version: 2
Library Type: 3
Class Name: Entry Control
Class Hierarchy: 04 : 40 : 00
Command Class Base: 00
Command Versions: 20v1 80v1 63v1 84v1 85v1 86v1 70v1 71v1 72v1 25v1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking

To get around this in the meantime I've added a loop into plugin.py to check for devices of the model: RFID Keypad which works fine. I've also modified actions.xml to remove the device filter for props.IsLockType:

for dev in indigo.devices.iter("indigo.zwave,props.IsLockSubType"):
dNodeID = dev.ownerProps['address']
if dNodeID == nodeId:
self.lockIDs.append(nodeId)
self.debugLog(u"Node %s added to list of lockIDs" % (nodeId))

for dev in indigo.devices.iter("indigo.zwave"):
if dev.model == "RFID Keypad":
dNodeID = dev.ownerProps['address']
if dNodeID == nodeId:
self.lockIDs.append(nodeId)
self.debugLog(u"Node %s added to list of lockIDs" % (nodeId))

Cheers

[howartp]

I've just posted v1.0.35 to the live plugin link in the announcement thread - I'll update the thread in a second.

I've actually changed the way I identify locks in the beta version of the plugin which some of you, including Krisstian, are on - so all this talk about isLockSubType and isZipatoKeypad was going to be irrelevant going forward because I don't use any of it. I've therefore merged the new approach into the existing live plugin to sort out these recent queries with undefined clones.

When you install it, you need to create a new device called ZWave Lock Manager > Door Lock. When you create/edit it, it lists every Zwave device on your system, which might well be hundreds, but you only do this step once per lock so that doesn't matter. Thereafter, all events, triggers, actions etc present you with a list of Door Locks that you've defined, rather than a list of LockSubTypes or ZipatoKeypads etc. (For the purposes of my testing, I'm using a TKB plug socket as a pretend door lock, because I don't have any actual locks!)

You might need to edit your existing actions/triggers once you've created your Door Lock devices, but that should only be once; the beta version when it gets released live will build upon this approach.

Peter

[stuartcolman]

Hi,

I have managed to get the keypad working, and the RFID tag set. I am now coming to set my alarm when the lock is locked, however I am getting the following error:

Z-Wave Lock Manager Error Error in plugin execution ReceivedBroadcast:

Traceback (most recent call last):
File "plugin.py", line 346, in zwaveCommandReceived
File "plugin.py", line 526, in triggerEvent
KeyError: (1941669764,)

ID 1941669764 is the Zwave lock device that I created as per instructions. I am just trying to trigger a timer to start a 30 second count down when the RFID keypad is set to "Away".

I am currently using the Zipato RFID Keypad.

Thanks

Stuart

[howartp]

Hi Stuart.

Sorry, I'll get that sorted!

Peter


Sent from my iPhone using Tapatalk Pro

[howartp]

Give 1.0.38 a try... (same link)

Peter

[mat]

Plugin works great for me, just purchased two of these to see if they help out. Thank both of you.

Has anyone got the beep working? ie beep for 30 seconds before the alarm arms when away is set?

Cheers and a big thank you


Mat