Auto Re-lock issue.

[arskrett]

I can not for the life of me get plugin to adjust the auto re-lock timer for my Shlage lock (BE369/468/469).

I make a trigger that set the new time to re-lock ( 250 sec) and I see in log that it sends some raw commands. but it never changes..

any idea?

[dscottbuch]

I had the same issue with my Yale lock. I looked at the python code and the debugging and saw that the checkbox indicating whether you wanted to lock/unlock was not being read and that the setRelock function was ALWAYS calling relockON as false and so always turning off auto relock.

Following the setRelock code I could use the Indigo 'Send Raw Z-Wave Command' to send the following two commands, in sequence, to the lock and it would set Autolock to on with an appropriate time.

Relock 120
0x70 0x04 0x02 0x01 0xFF
0x70 0x04 0x03 0x01 0x78

the 0x78 is 120 seconds as that's what I wanted. Just change the )x78 to appropriate number of seconds, in hex, and this might work.

If your into scripting the following python might work in your own action with nsec the number of second in base 10, and devID the ID number of your lock

codeStr = [112, 04, 02, 01, 255]
indigo.zwave.sendRaw(device= indigo.devices[devID] ,cmdBytes=codeStr,sendMode=1)
#indigo.server.log("Sending raw command: [" + convertListToStr(codeStr) + "] to device " + str(indigoDev))
codeStr = [112, 04, 03, 01, nsec]
indigo.zwave.sendRaw(device= indigo.devices[devID],cmdBytes=codeStr,sendMode=1)

[howartp]

Apologies, I’ll have a look at this.

Perer


Sent from my iPhone using Tapatalk Pro

[agame]

just FYI having similar issues with the KAS locks configuring auto relock, I'd assumed it was another zwave version issue with these locks. I'm ok just to disable the feature.

[howartp]

v1.0.63 is now live with this fix.

It was checking for "On" in the code, but it was saved as "on" in the config so the check didn't match.

Peter