Trouble with Schedule Entry Lock CC on Kwikset HomeConnect 620 #6441
Replies: 2 comments 9 replies
-
|
Please make a driver log, loglevel I'd like to see exactly what the device reports. Also, do you have a manual for the device that actually explains the Z-Wave stuff like config parameters etc.? I can't find that online. |
Beta Was this translation helpful? Give feedback.
-
I think this is the problem. Z-Wave JS never learns about the number of supported schedules. You may be able to figure out how many schedules the lock actually supports by circumventing the check in the CC API and sending the commands directly. Something like this should work for the weekday schedule - let me know if you need help adapting it for the other schedule types: const { require } = this;
const {
ScheduleEntryLockCCWeekDayScheduleGet,
ScheduleEntryLockCCWeekDayScheduleSet,
ScheduleEntryLockSetAction,
ScheduleEntryLockWeekday,
} = require("@zwave-js/cc");
const nodeId = 2; // Put your node ID here
const endpoint = 0; // probably?
const userId = 1; // or whichever user ID this schedule is for
const slotId = 1; // increase this until the Get is no longer answered
const setWeekdaySchedule = new ScheduleEntryLockCCWeekDayScheduleSet(driver, {
nodeId,
endpoint,
userId,
slotId,
action: ScheduleEntryLockSetAction.Set, // or .Erase to clear a schedule - then omit the day and tiem
// Set whichever day and time you want
weekday: ScheduleEntryLockWeekday.Sunday,
startHour: 11,
startMinute: 11,
stopHour: 13,
stopMinute: 13,
});
// Send the Set command
await driver.sendCommand(setWeekdaySchedule);
// Query it again to see if the change was accepted
const getWeekdaySchedule = new ScheduleEntryLockCCWeekDayScheduleGet(driver, {
nodeId,
endpoint,
userId,
slotId,
});
// Send the Get command
await driver.sendCommand(getWeekdaySchedule);
// Now watch the logs for the responseIf you do find out how many schedules it supports, we can override the response for the command it doesn't respond to so this works out of the box. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the thoughtful response! Unfortunately, it looks like the same timeout is occurring on the get: I tried user 1's code on the lock, just in case the set is working but not the get. Sadly, the code still works. |
Beta Was this translation helpful? Give feedback.
-
|
Not being able to query schedules (even if they work) is going to be a headache though. |
Beta Was this translation helpful? Give feedback.
-
|
Agreed. I'm not even certain that the schedule is working, just that the door code stops working when I set the schedule. Since I'm unable to get the dateTime from the lock, I have no idea what the lock thinks the current date and time are, so I can't set a schedule to test. I was able to set and get the dateAndTime, on the TimeParametersCC, but that doesn't seem to be related (and I haven't come across any documentation that clarifies what TimeParametersCC is even for). |
Beta Was this translation helpful? Give feedback.
-
|
Time parameters CC is used to set the time and date on a device. You can't set the timezone though, this needs to be done with aa different CC. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I’ll take a look for it in the UI. Something I noticed about Time
Parameters CC, though, is that the time never changes, when I call get. It
seems to behave more like a timestamp. I’m not one to suspect incompetence
in anyone but myself, but is it possible Kwikset botched the Z-wave
implementation?
…On Wed, Oct 25, 2023 at 11:25 AM AlCalzone ***@***.***> wrote:
Time parameters CC is used to set the time and date on a device. You can't
set the timezone though, this needs to be done with aa different CC.
There's a helper method though that does the right thing(TM), and AFAIK
this is accessible through the UI.
—
Reply to this email directly, view it on GitHub
<#6441 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAINZPX4NFN7J6XXAHECPA3YBFDRXAVCNFSM6AAAAAA6LB2A56VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TGOBUGAYDE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Seems they botched quite a lot in that lock: #5566 |
Beta Was this translation helpful? Give feedback.
-
|
That's a bummer. When I try to find information about the best locks to use with Z-wave, all I can find is marketing bullshit. Do you happen to know of (maybe you can point me toward a list) any Z-wave locks that behave better? I bought an Assure Lock 2 with Z-wave, the same time as the Kwikset, but it arrived without it's Z-wave module, and I'm still waiting for Yale to respond to my request for the part. Maybe it would work better (assuming they ever send me a module)? |
Beta Was this translation helpful? Give feedback.
-
I'm super new to Zwave programming. I've spent days pouring through documentation, and experimenting with scripts in zwave-js, but I can't seem to make sense of the trouble I'm having with my Kiwkset Homeconnect 620. I'm trying to use the Schedule Entry Lock CC. The manual for the 620 says "Home Connect 620 smart lock supports multiple schedule types that can be assigned to access codes". When I query the 620 with 'supportsCC' and 'supportsCCAPI', it reports that Schedule Entry Lock CC is supported. The trouble is that when I call 'getSchedules', 'numSlots', 'set*Schedule', etc, the lock reports there are 0 schedule slots. In the case of 'setYearDaySchedule', for example, the error states: "The schedule slot # must be between 1 and the number of supported day-of-year slots 0". I can't find any way to create slots, on the lock. It makes no sense to me that Kwikset would build in support for the Schedule Entry Lock CC, but not have any slots to actually use it. I'm hoping this is just my noob-ness, and that a more experienced z-wave-er can point me in the right direction. Thank you to anyone who can provide some insight!!
Debug Log:
zwavejs_2023-10-23.log
Beta Was this translation helpful? Give feedback.
All reactions