#Hi All I just bought by second Kwikset
1 messages ยท Page 1 of 1 (latest)
I have 32 other z-wave devices and never had this much trouble connecting one
A full hard reset doesn't help either
Not that it helps with the Quickset... But I've had good luck with the Yale locks. I have 3 of their Assure z-wave locks (2 from 2017 and 1 from 2021) and they all work well. I also have an old Schlage Connect from 2017 that works, mostly, HA misses events from it - though it joins and can be controlled just fine). That schlage happily joined from as far away from the hub as it could be and both devices still be in my house.
I'm pretty close to returning this and trying out the ULTRALOQ since it has door closed sensor
This is especially frustrating because I already have a working Kwikset 620 lock ๐ฆ
An included door closed sensor would be nice. The Yale and Schlage locks I have don't have that.
I have four doors that could use smart locks. Two doors I use the most have Eufy locks with fingerprint and bluetooth but when I added the first Kwikset z-wave lock (no fingerprint) I really like being able to check it's status from HA. I've been eyeing the ULTRALOQ for like a year now but it's 160 without fingerprint and 200 with fingerprint. Ideally I'd have 4 of those with fingerprint but 800 for door locks is a bit much
I just noticed that when provisioning by scanning the QR code I see it's only one of two devices showing without "S2 Unauthenticated, S2 Authenticated"
The other device is my other Kwikset lock ๐คฆโโ๏ธ
Seems it uses S0 Legacy
I restarted z-wave js server with http log level and reseated battery in the z-wave lock and see in the logs
New client
2023-07-14T17:47:11.071Z DRIVER Dropping message with invalid payload
2023-07-14T17:47:12.670Z DRIVER Dropping message with invalid payload
Don't
Kwikset is sending me a replacement lock that is expected to arrive tomorrow
Got the replacement yesterday. I improvised the old one that never came up, scanned the new QR code, put the batteries in, and it came up nearly instantly. Seems it was definitely a problem with that device
I did some quick testing and the lock would quickly register manual opening and closing but trying to trigger an open or close from home assistant would not actually make the lock physically open or closed but show as the state changed in home assistant which is not good.
I'm hoping the network just needs a little time to bake.
Might want to capture some driver logs of your locking attempts from HA
Yeah planning to do that today
So it's still happening. Based on the logs it seems that the messages from Home Assistant to the lock may not be making it to the lock through the intermediary node 218 which is a Zooz ZSE40 multisensor that is battery powered.
2023-07-23T16:20:02.895Z CNTRLR [Node 218] treating BasicCC::Set as a report
2023-07-23T16:20:14.584Z CNTRLR [Node 218] treating BasicCC::Set as a report
2023-07-23T16:20:18.453Z CNTRLR [Node 223] [Notification]
type: Access Control
event: Manual unlock operation
2023-07-23T16:20:23.257Z DRIVER Dropping message with invalid payload
2023-07-23T16:20:28.483Z CNTRLR [Node 218] treating BasicCC::Set as a report
2023-07-23T16:20:29.485Z CNTRLR [Node 223] [Notification]
type: Access Control
event: Manual lock operation
2023-07-23T16:20:40.173Z CNTRLR [Node 218] treating BasicCC::Set as a report
There is a firmware update but the changelog doesn't indicate there are any fixes in there from version 32.32
https://www.support.getzooz.com/kb/article/1007-zse40-700-4-in-1-sensor-change-log/
Well that might not have anything to do with this issue. The motion sensor is just above the door with the Kwikset lock so I was activating it when in the room.
Trying to lock and unlock with HA from outside resulted in no such logs and only got this this time
2023-07-23T16:43:29.348Z DRIVER Dropping message with invalid payload
2023-07-23T16:44:02.056Z DRIVER Dropping message with invalid payload
I do see the invalid payload thing every so often
I tried healing the device but that hasn't helped
I guess I need to try moving the lock closer to the hub.
But it does seem strange that the lock would work fine sending back to HA
I do see the firmware version of this like is 7.21.0 while the firmware version of the other lock I've had that works fine is 7.20.0
I also can't seem to find where to download the firmware for this lock ๐
Well, just now I took the batteries out for a few seconds and put them back in...and now it's working!!! ๐
you're not looking at debug-level driver logs, so they don't tell you why messages are being dropped