Yes Generic.
I'll try the Alfred, remove my polling, and see if it play nice with the Kwikset.
Cheers.
PS I just noticed that the locks refresh fine if you manually lock them.
If you press the lock button on the keypad that's when they don't refresh!
Never put 2+2 together before.
Driver issue then?
Possibly, would need debug logs when you press that button. Filter to just the device and Screenshot please, copy/paste text is hard to read. I think I have looked at this before for that exact situation on the same locks and determined the device is not sending any communication out so in that case it is a device firmware problem.
Also I don't think the Alfred driver will help in this case since the action is started from the device. The refresh on the Alfred driver is when you issue a command from the hub.
One workaround that someone came up with was they have a contact sensor on the door so they refresh the lock a minute or two after the door closes, assuming that the door was possibly just locked from the button upon exiting.
I have 5 Kwikset Home Connect 620 z-wave+ v2 deadbolts. They are all paired using S2. They work fine with the built-in Generic Z-Wave Lock device driver.
This is mine on the newest 700 series and the 500 older ones.
Strangely, I tried the button 3 times and I didn't get a refresh so I thought I had narrowed the issue down.
Just tried it (the button) again and the damn thing refreshed every time. Grrrr
My back door still said Unlocked and hour after I came in, of course I had paused the polling at that point.
I think I blame firmware.
I have a 620 ..
And also does the exact same thing it never used to it seemed like it worked for a long time but just stopped working not sure if it's the hub software or the driver's changed somehow.
Everything works fine updates just fine unless you use the auto lock feature top and above the keypad. Very strange I also think I added it through Smart start..