Page 1 of 1

Re-instate Encrypted Devices

PostPosted: Sun Mar 04, 2018 12:59 pm
by AndyVirus
I had my HDD FS corruption. I was able to deregister my license and i already had backups of my Indigo directory and DB.
I wiped and re-installed OSX.
I re-installed Indigo and all plugins.
All works... except...

My locks now no longer communicate. When i sync'd them i sync'd them as encrypted. They worked great prior to the rebuild.
Now they just do communicate. I thought the Z-Wave stick would hold the keys but now I am thinking maybe its a software side key pair? If so i still have a backup of the indigo dir, is there a file or files i need to put back?

Basically am i boned or is there a fix as I you cant exclude these devices to re-include unless done by the original system (which has not changed other than OSX and and Indigo re-install)

They are Yale Keyfree Connected Locks and a Yale Keyless Connected lock.

Any advise would be greatly appreciated.

Re: Re-instate Encrypted Devices

PostPosted: Sun Mar 04, 2018 1:06 pm
by AndyVirus
If i try to re-sync I get:

Z-Wave Syncing - started for "Front Door Lock"
Z-Wave Syncing - retrieved module neighbors list: 10, 11, 12, 21, 30, 31, 37, 38, 40, 41, 42, 43, 44, 46, 47, 48, 49, 50, 53, 54, 55, 56, 57, 58, 59, 60
Z-Wave Syncing - assigning return route to "074 - Front Door Lock"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Yale - 0129, Keyfree Connected Lock - 00060000
Z-Wave Syncing - retrieved protocol version 3.34, app version 22.32
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Entry Control : Keypad Door Lock (04 : 40 : 03, base 62)
Z-Wave Syncing - retrieved command classes: 20v1 62v1 63v1 86v1 98v1 72v1
Z-Wave Syncing - retrieved encrypt commands: 80 85 86 8A 8B 4C 4E 98 62 63 70 71 72 75
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, security, frequentWaking

Z-Wave Error Syncing - failed
Z-Wave Error Timeout waiting for "074 - Front Door Lock". Module might be asleep, or is unreachable.

Re: Re-instate Encrypted Devices

PostPosted: Sun Mar 04, 2018 1:14 pm
by matt (support)
You can exclude any Z-Wave module with any Z-Wave interface (Z-Stick, etc.) even if it wasn't the original one to include it. So you should be able to exclude the module using Indigo or manually using the Z-Stick, then re-include it using Indigo w/ encryption enabled.

Re: Re-instate Encrypted Devices

PostPosted: Sun Mar 04, 2018 1:27 pm
by AndyVirus
Unfortunately not with the Yale modules it seems. I tried and exclusion does not happen, just times out. If it try to include in gives errors. I had this once before with a yale module and in the end i had to get a replacement as there is no way to exclude unless by the same system.
Page 21 of the manual back this up also : https://www.yale.co.uk/Yale/Yale_co_uk/ ... 014-2%20(1).pdf

"For security reasons a lock will not connect to a new home automation system if it is linked to another. If you have changed your home automation system please run through the disconnecting settings before adding the new one."

Re: Re-instate Encrypted Devices

PostPosted: Sun Mar 04, 2018 1:28 pm
by AndyVirus
Tried to reply to your PM but could not. I have it all working again now thanks to your info.

Thanks!