- Posted on
Wed Apr 14, 2021 2:44 pm
-
dscottbuch
offline
-
- Posts: 90
- Joined: Jan 19, 2004
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)