Indigo Domotics

Using (for >1 year) yale z-wave UK-spec lock. No issues. In fact, I also converted US-spec locks to the EU standard using EU z-wave modules from Yale.

Interesting idea, Shapa!


Sent from my iPhone using Tapatalk Pro

Firstly, thanks you for developing a great plugin!

I have the Yale Keyless connected lock and am trying to get it to report various unlock methods.
Identifying user unlock by key code works great but when unlocked via a key tag, it reports an unknown status:

Z-Wave received "Back Door Lock" status update is on
Z-Wave Lock Manager Unknown lock status received: 144 [Node: 15]

Could you update the plugin to report this as Unlocked via Key Tag/Key Card or such like?
An alternative would be to add a Event such as "Status equals or contains" etc."

Looking forward to seeing the plugin evolve!

Chris
--

Could you turn on debug (Plugins > Lock Manager > configure) and post what it sees when you tag it?

Peter

Hi Peter,

Here's the debug logging as requested...

8 Oct 2018, 20:19:35
Z-Wave Lock Manager Debug logging enabled
Z-Wave Lock Manager Debug Node ID 15 (Hex 15) found in lockIDs
Z-Wave received "Back Door Lock" status update is on
Z-Wave Lock Manager Debug Node ID 15 (Hex 15) found in lockIDs
Z-Wave Lock Manager Debug Raw: 01 0A 00 04 00 0F 04 71 05 90 02 FF
Z-Wave Lock Manager Unknown lock status received: 144 [Node: 15]
Z-Wave Lock Manager Debug -----
Z-Wave Lock Manager Debug Node ID 15 (Hex 15) found in lockIDs
Z-Wave Lock Manager Debug Node ID 15 (Hex 15) found in lockIDs
Z-Wave received "Back Door Lock" status update locked (via timer)
Z-Wave Lock Manager Debug Node ID 15 (Hex 15) found in lockIDs
Z-Wave Lock Manager Debug Raw: 01 0A 00 04 00 0F 04 71 05 1B 01 FF
Z-Wave Lock Manager Status: Door re-locked automatically [Node: 15]
Z-Wave Lock Manager Debug triggerEvent called: relockedAuto
Z-Wave Lock Manager Debug Updating state: lockState
Z-Wave Lock Manager Debug -----
Z-Wave Lock Manager Debug Node ID 15 (Hex 15) found in lockIDs

I also took the liberty of testing with a key card rather than a key tag incase it's different but the Raw code (and status response) appears to be the same...

8 Oct 2018, 20:19:35
Z-Wave Lock Manager Debug logging enabled
Z-Wave Lock Manager Debug Node ID 15 (Hex 15) found in lockIDs
Z-Wave received "Back Door Lock" status update is on
Z-Wave Lock Manager Debug Node ID 15 (Hex 15) found in lockIDs
Z-Wave Lock Manager Debug Raw: 01 0A 00 04 00 0F 04 71 05 90 02 FF
Z-Wave Lock Manager Unknown lock status received: 144 [Node: 15]
Z-Wave Lock Manager Debug -----
Z-Wave Lock Manager Debug Node ID 15 (Hex 15) found in lockIDs
Z-Wave Lock Manager Debug Node ID 15 (Hex 15) found in lockIDs
Z-Wave received "Back Door Lock" status update locked (via timer)
Z-Wave Lock Manager Debug Node ID 15 (Hex 15) found in lockIDs
Z-Wave Lock Manager Debug Raw: 01 0A 00 04 00 0F 04 71 05 1B 01 FF
Z-Wave Lock Manager Status: Door re-locked automatically [Node: 15]
Z-Wave Lock Manager Debug triggerEvent called: relockedAuto
Z-Wave Lock Manager Debug Updating state: lockState
Z-Wave Lock Manager Debug -----
Z-Wave Lock Manager Debug Node ID 15 (Hex 15) found in lockIDs

I hope that helps!
Let me know if you'd like anything else tested.
Looking forward to user key code logging being implemented

Many thanks,

Chris
--

Hi Peter,

Have you had any luck with identifying the Key Tag/Card unlock status?

Many thanks,

Chris
--

Hi Peter,

Any news on the identification of unlock by Key Tag/Card?
Looking forward to the next version of your amazing plugin!

Cheers,

Chris
--

Hi Chris.

Z-Wave Lock Manager Debug Raw: 01 0A 00 04 00 0F 04 71 05 90 02 FF

The 71 05 90 02 is the bit we need.

71 05 is the alarm class, which all the lock commands use. 71 05 16 for example is "Manual unlock".

90 is undefined in any spec I can find, but Yale have obviously used it for key tags.

02 suggests there's an 01 value as well, but as it's not defined anywhere I can't specifically code against it.

I'll add a log/trigger for 71 05 90 02 but note that it will be subject to user acceptance that it's not specced anywhere so may not be accurate.

I'd love it if you saw 71 05 90 01 in your logs and could tell me what it corresponded to.

Peter

Hi Peter,

Many thanks for your update and feedback.
If you’d like me to test any beta you compile, happy to do so!
With regards to the 01 vs 02, I’d expect it to be key card vs tag but in testing my end, the log output was the same for both as I confirmed in the earlier post.
Let me know how I can help in your coding wizardry

Chris

Chris,

If you hit Define/Sync on the lock, can you tell me what the Retrieved Command Classes says in the log?

Peter

ps - in the Yale manual, Key Cards and Tags are different to Key Fobs, so it's possible 90 01 is for Fobs, whilst 90 02 is Cards/Tags.

Hi Peter,

Thanks for getting in touch.
Here are the details you requested...
Syncing - retrieved command classes: 80v1 85v1 86v1 8Av1 8Bv1 4Cv1 4Ev1 98v1 20v1 62v1 63v1 70v1 71v1 72v1 75v1

Hope that helps! Let me know if you need anything else.

Chris
--