Premise Kwikset info

Motorola Premise
etc6849 Im not sure if you have seen this link, but there may be some new info you have not seen before on the kwikset deadbolt.

http://s7d5.scene7.c...II-Z-Wave-Locks

The schedule part is interesting only Im not sure if the lock has a real time clock and if so how to read and set the clock if it has one is a mystery to me.
 
What ever happened to the good old days of the hackable key fob locks..... :(

Nice piece of documentation, though.
 
Yes, that's how you do it. From the link above, COMMAND_CLASS_CLOCK = 129, so we can try a get command and see if we obtain anything.

Now, you'll have to figure how to decode the answer, which doesn't look easy unless the conversion is similar to the COMMAND_CLASS_SCHEDULE_ENTRY_LOCK that is detailed in the application note you reference.

Here's what mine does:
Code:
>N4SS129,2
<E000
<E000
<N004:152,128,065,208,225,144,118,233,215,228
<X000

PS: does everyone else see E000 twice? According to Leviton's documention, E000 means the request has been processed, so it actually gets processed twice before sending (X000)... WTF?!?!
 
So I've thought about this and how not to get banned from cocoontech.com. However, this will probably help you alot, so here goes. I do not advocate copyright infringement, but I also have not signed a non-disclosure agreement with Zensys and I am merely explaining one method to obtain a file that will help to answer all of your questions.

I searched google for:
SDS11060 "Z-Wave Command Class Specification" site:www.doc88.com

and found this page:
http://www.doc88.com...6273616438.html

EDIT: DISCLAIMER: I do not know Mandarin and I did not post the file on doc88.
 
Yes, that's how you do it. From the link above, COMMAND_CLASS_CLOCK = 129, so we can try a get command and see if we obtain anything.

Now, you'll have to figure how to decode the answer, which doesn't look easy unless the conversion is similar to the COMMAND_CLASS_SCHEDULE_ENTRY_LOCK that is detailed in the application note you reference.

Here's what mine does:
Code:
>N4SS129,2
<E000
<E000
<N004:152,128,065,208,225,144,118,233,215,228
<X000

PS: does everyone else see E000 twice? According to Leviton's documention, E000 means the request has been processed, so it actually gets processed twice before sending (X000)... WTF?!?!



I think it should be the time parameters class 139.

According to this link http://www.pepper1.net/zwavedb/uploads/resources/d4a7289ef02ac0d04f50719d4cbef0e10fa1a929.pdf
 
Thanks for another great document. You are correct. My lock outputs as follows:


Code:
>N4SS139,2
<E000
<E000
<N004:152,128,132,116,190,078,039,089,212,020
<X000
<N004:152,064
<n004:000,139,003,007,209,003,012,004,003,049

It's strange how the lock responds to the clock get command, but since the VRC0P doesn't output a lower case n packet, I don't think the COMMAND_CLASS_CLOCK is supported, only the COMMAND_CLASS_TIME_PARAMETERS. That earlier link I posted shows how to decode the packet.

PS: What system are you using the VRC0P with?
 
Thanks for another great document. You are correct. My lock outputs as follows:


Code:
>N4SS139,2
<E000
<E000
<N004:152,128,132,116,190,078,039,089,212,020
<X000
<N004:152,064
<n004:000,139,003,007,209,003,012,004,003,049

It's strange how the lock responds to the clock get command, but since the VRC0P doesn't output a lower case n packet, I don't think the COMMAND_CLASS_CLOCK is supported, only the COMMAND_CLASS_TIME_PARAMETERS. That earlier link I posted shows how to decode the packet.

PS: What system are you using the VRC0P with?

Im using the ECS software with the VRCOP+3

Looks like your lock has the year 2001

I think this would set the clock. NXSS139,1,(MSB year),(LSB year),month,day,hour,min,sec


Also on my first thread above. I think there is a typo in that document on Table 2 for the schedules. I think the sid value for thursday should be 5 and not 7.
 
Back
Top