KeyWe & 2.1.6

🛎️ Get Help
21

I should have mentioned that I did try using the Lock Code Manager to create a new user in an empty slot and after refreshing, it shows "jobs-failed: 1". I just tried again and the Hubitat Logs showed:

dev:130 2019-11-05 11:04:21.570 am debugsetCode- 2
app:265 2019-11-05 11:04:21.560 am debugprocessJobs- try job:[130_2:[code:3, name:Test, codeState:pe, retry:9]]
app:265 2019-11-05 11:04:21.535 am infojobs:1
dev:130 2019-11-05 11:04:19.488 am debugsetCode- 2
app:265 2019-11-05 11:04:19.477 am debugprocessJobs- try job:[130_2:[code:3, name:Test, codeState:pe, retry:8]]
app:265 2019-11-05 11:04:19.450 am infojobs:1
dev:130 2019-11-05 11:04:17.406 am debugsetCode- 2
app:265 2019-11-05 11:04:17.393 am debugprocessJobs- try job:[130_2:[code:3, name:Test, codeState:pe, retry:7]]
app:265 2019-11-05 11:04:17.368 am infojobs:1
dev:130 2019-11-05 11:04:15.324 am debugsetCode- 2
app:265 2019-11-05 11:04:15.314 am debugprocessJobs- try job:[130_2:[code:3, name:Test, codeState:pe, retry:6]]
app:265 2019-11-05 11:04:15.297 am infojobs:1
dev:130 2019-11-05 11:04:13.257 am debugsetCode- 2
app:265 2019-11-05 11:04:13.251 am debugprocessJobs- try job:[130_2:[code:3, name:Test, codeState:pe, retry:5]]
app:265 2019-11-05 11:04:13.236 am infojobs:1
dev:130 2019-11-05 11:04:11.198 am debugsetCode- 2
app:265 2019-11-05 11:04:11.175 am debugprocessJobs- try job:[130_2:[code:3, name:Test, codeState:pe, retry:4]]
app:265 2019-11-05 11:04:11.149 am infojobs:1
dev:130 2019-11-05 11:04:09.110 am debugsetCode- 2
app:265 2019-11-05 11:04:09.100 am debugprocessJobs- try job:[130_2:[code:3, name:Test, codeState:pe, retry:3]]
app:265 2019-11-05 11:04:09.070 am infojobs:1
dev:130 2019-11-05 11:04:07.022 am debugsetCode- 2
app:265 2019-11-05 11:04:07.011 am debugprocessJobs- try job:[130_2:[code:3, name:Test, codeState:pe, retry:2]]
app:265 2019-11-05 11:04:06.965 am infojobs:1
dev:130 2019-11-05 11:04:04.926 am debugsetCode- 2
app:265 2019-11-05 11:04:04.912 am debugprocessJobs- try job:[130_2:[code:3, name:Test, codeState:pe, retry:1]]
app:265 2019-11-05 11:04:04.889 am infojobs:1
dev:130 2019-11-05 11:04:02.832 am debugsetCode- 2
app:265 2019-11-05 11:04:02.816 am debugprocessJobs- try job:[130_2:[code:3, name:Test, codeState:pe, retry:0]]
app:265 2019-11-05 11:04:02.794 am infojobs:1
22

we need to start with the basics here.
Please perform check the following and report the results.
when the lock is locked and unlocked manually, is this correctly reflected in the driver details?
If you add a lock code via the lock (not the driver), does this lock code show up in current states lock codes?
If you lock and unlock the lock via the driver details, does the lock actually lock and unlock?

23

Mike,

The current state of lock/unlock is not updated (checked for 2 minutes) unless I send a refresh. A refresh causes the correct lock state to be displayed.

New lock codes added directly on the lock do not show up in the Current States/lockCodes. The new codes do work when entered on the lock.

Locking and unlocking works directly from the driver details. Locking/unlocking via the driver does not update the current state of lock unless a refresh is sent.

Was there a firmware update for the KeyWe lock since it was shipped from the Kickstarter?

24

I don't know, I'm not even sure what version of the firmware I have running on mine, though I think it may not be the current version.

can you enable debug logging in the driver, then click the getCodes command and send me the log output?, thanks. PM these to me, otherwise some of your current lock codes may be exposed.

25

Mike,

Debug logging was already enabled. There are no Driver Events shown for the device after a Get Codes. Looking at the Logs, there is only:

dev:1302019-11-07 02:22:38.180 pm debuguserCodeGet (checkCode)- 1

dev:1302019-11-07 02:22:38.180 pm inforestarting code fetch, trying to fetch code:1

...so I didn't PM ya.

26

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.