Not sure how to respond to this.
Here's how inclusion happens:
1. When included, secure device should await for network key packet for 20 seconds or so.
2. Controller sends insecure SECURITY_SCHEME_GET packet to get encryption schemas supported by device (it should be available without encryption).
3. Lock responds with insecure SECURITY_SCHEME_REPORT to indicate what kind of encryption it supports.
4. If it supports required encryption scheme, we send a secure NETWORK_KEY_SET packet with a network key (encrypted with dummy key).
5. Lock should remember the new network key and respond with secure NETWORK_KEY_VERIFY (encrypted with just received new key).
6. Etc.
Your lock seems to fail step 3. It is not even an encrypted key exchange yet.
Probably you've shown incomplete log? It might be buffered, so run "sync" in console first.
Problem with lock from locstar
Re: Problem with lock from locstar
Hello,
The only truncated log was some "job deleted from queue", but i post new logs later, after doing the sync.
Otherwise, did you know a lock who works fine with this controler ?
Regards.
The only truncated log was some "job deleted from queue", but i post new logs later, after doing the sync.
Otherwise, did you know a lock who works fine with this controler ?
Regards.
Re: Problem with lock from locstar
We have made improvements in the latest v1.7.1 to fast up communications with the lockstar. Now it should pass interview without problems. Please give a try!
Re: Problem with lock from locstar
Perfect, the locstar is include and full interviewed, i can operate it
Good update thanks
Good update thanks