Doesn’t have anything to do with the cache. Add a buffering repeater, see this link for details: FAQ: why would I need another beaming repeater if my zwave lock is already close to my hub? - #2 by RBoy
Please post a screenshot of the device detail information from the ST Advanced Web App.
Attached is a screenshot of the device detail information from the ST Advanced Web App.
(Attachment SmartThings.pdf is missing)
Doesn’t seem to be there. Save it as a jpg and upload the image.
Attached are screenshots of the device detail information from the ST Advanced Web App
All the device capabilities look good, but none of the values are populated. Did you change from the stock driver to the rBoy driver without re-pairing the lock? If so, I would exclude the lock and re-pair it. It should pick up the rBoy driver automatically.
I have followed your instructions and though the lock paired with the correct driver there is no change. RBOY says I need a repeater,
there is an Aeotec z-wave Siren 2 feet from the lock, so I’m stumped.
I have an Aeotec z-wave Siren 2ft away from the lock.
You need a buffering device as described in the article link above, that’s a mains powered zwave device which provides buffering for FLiRS zwave devices like locks. Is your Siren mains powered with FLiRS buffering? All Z-Wave plus mains powered devices are buffering devices. No battery powered device has buffering. Locks need buffering FLiRS devices to operate properly.
I have 4 other locks that don’t have a problem. Why do they not need Flirs? Your driver doesn’t work. Fix it.
Hmm. Something else going on here. When you pull down on the device details tab in the mobile app, do you get any messages perhaps something like “Device has not updated all its details yet”?
At this point, I’m curious whether your hub is receiving messages properly from the device. My next step would be to use the ST CLI to do driver logging to see if the lock is generating messages and how the hub is responding to them. The CLI runs on a Linux/Windows/macOS computer and driver logging is performed using the command “smartthings edge:drivers:logcat”. You will be prompted to select the driver to be logged. If that doesn’t yield any results, you might want to include the “-a” parameter to the command which will do logging for all drivers (which can be a bit noisy if you have a lot of devices that are active).
Or better yet, cancel my subscription and refund my money. Thanks.
Thanks, I’ll try it and let you know.
Here is what I got from the cli:
2024-08-07T18:31:14.531590657Z INFO Universal Enhanced Z-Wave Lock Max lock codes not detected, getting information
2024-08-07T18:31:14.538451699Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> emitting event: {“attribute_id”:“lockCodes”,“capability_id”:“lockCodes”,“component_id”:“main”,“state”:{“value”:“{}”},“visibility”:{“displayed”:false}}
2024-08-07T18:31:14.557252032Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(1a2ef2b4) queued for radio transmission: CC:User Code, CID:0x04
2024-08-07T18:31:14.562362282Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“USER_CODE”, cmd_id=“USERS_NUMBER_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T18:31:14.587385657Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(816e8ed0) queued for radio transmission: CC:User Code, CID:0x02
2024-08-07T18:31:14.590163241Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={user_identifier=1}, cmd_class=“USER_CODE”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x01”, src_channel=0, version=1}
2024-08-07T18:31:14.633800032Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T18:31:14.644435782Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(af020a4b) queued for radio transmission: CC:User Code, CID:0x04
2024-08-07T18:31:14.658643699Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T18:31:14.663557949Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T18:31:14.678447782Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“USER_CODE”, cmd_id=“USERS_NUMBER_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T18:31:14.683723532Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T18:31:15.989855949Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(1a2ef2b4) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T18:31:16.237207657Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(816e8ed0) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T18:31:16.432371657Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(af020a4b) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T18:31:22.659948255Z TRACE Universal Enhanced Z-Wave Lock Validating if lock has been initialized
2024-08-07T18:31:22.815128306Z TRACE Universal Enhanced Z-Wave Lock Lock initialization incomplete, checking again in 60 seconds
2024-08-07T18:31:22.853153059Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T18:31:22.884685818Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(d47b339a) queued for radio transmission: CC:Door Lock, CID:0x02
2024-08-07T18:31:22.897611069Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T18:31:22.918387118Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T18:31:22.938599219Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T18:31:22.951519426Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“DOOR_LOCK”, cmd_id=“OPERATION_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T18:31:22.969123932Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T18:31:24.372478468Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(d47b339a) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T18:31:25.001164695Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(1cab4f23) queued for radio transmission: CC:Battery, CID:0x02
2024-08-07T18:31:25.007133928Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“BATTERY”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T18:31:25.012443332Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T18:31:25.232487049Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(1cab4f23) transmit status: TRANSMIT_COMPLETE_OK
So, I see that the hub/driver is generating ST commands and successfully transmitting the corresponding Z-Wave commands, but there seem to be no responses. Therefore, the lock is either not receiving them or failing to respond for some reason.
Next, I would do driver logging while manually operating the lock using both the keypad and manual knob to see if the lock generates events that the hub then receives.
1 Like
I physically unlocked and locked the lock:
2024-08-07T20:12:03.989057282Z INFO Universal Enhanced Z-Wave Lock Max lock codes not detected, getting information
2024-08-07T20:12:03.994540314Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(09ffceae) queued for radio transmission: CC:User Code, CID:0x04
2024-08-07T20:12:04.004360430Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> emitting event: {“attribute_id”:“lockCodes”,“capability_id”:“lockCodes”,“component_id”:“main”,“state”:{“value”:“{}”},“visibility”:{“displayed”:false}}
2024-08-07T20:12:04.015168414Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(b0856cdd) queued for radio transmission: CC:User Code, CID:0x02
2024-08-07T20:12:04.029007122Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“USER_CODE”, cmd_id=“USERS_NUMBER_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T20:12:04.040626762Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={user_identifier=1}, cmd_class=“USER_CODE”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x01”, src_channel=0, version=1}
2024-08-07T20:12:04.063193373Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:04.083721174Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(05ea208a) queued for radio transmission: CC:User Code, CID:0x04
2024-08-07T20:12:04.086451830Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:04.100347191Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:04.208937876Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“USER_CODE”, cmd_id=“USERS_NUMBER_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T20:12:04.248418773Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:05.342523677Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(09ffceae) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:12:05.562320938Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(b0856cdd) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:12:05.762256897Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(05ea208a) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:12:33.099148325Z TRACE Universal Enhanced Z-Wave Lock Validating if lock has been initialized
2024-08-07T20:12:33.119103325Z TRACE Universal Enhanced Z-Wave Lock Lock initialization incomplete, checking again in 60 seconds
2024-08-07T20:12:33.143583825Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:33.172144241Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(c18cae77) queued for radio transmission: CC:Door Lock, CID:0x02
2024-08-07T20:12:33.174906908Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:33.207453325Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:33.221711783Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:33.228587408Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“DOOR_LOCK”, cmd_id=“OPERATION_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T20:12:33.236250616Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:34.053251242Z TRACE Universal Enhanced Z-Wave Lock Found CapabilityCommandDispatcher handler in Universal Enhanced Z-Wave Lock → Z-Wave lock operations
2024-08-07T20:12:34.058367908Z TRACE Universal Enhanced Z-Wave Lock reload_all_codes, cmd {
args={},
capability=“lockCodes”,
command=“reloadAllCodes”,
positional_args={},
}
2024-08-07T20:12:34.084802117Z INFO Universal Enhanced Z-Wave Lock Max lock codes not detected, getting information
2024-08-07T20:12:34.100561158Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> emitting event: {“attribute_id”:“lockCodes”,“capability_id”:“lockCodes”,“component_id”:“main”,“state”:{“value”:“{}”},“visibility”:{“displayed”:false}}
2024-08-07T20:12:34.114874367Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(174151d4) queued for radio transmission: CC:User Code, CID:0x04
2024-08-07T20:12:34.124226950Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“USER_CODE”, cmd_id=“USERS_NUMBER_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T20:12:34.139530700Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(014b58f9) queued for radio transmission: CC:User Code, CID:0x02
2024-08-07T20:12:34.147176825Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={user_identifier=1}, cmd_class=“USER_CODE”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x01”, src_channel=0, version=1}
2024-08-07T20:12:34.165480950Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:34.178830200Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(14c89bb1) queued for radio transmission: CC:User Code, CID:0x04
2024-08-07T20:12:34.184312242Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:34.189334825Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:34.193853825Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“USER_CODE”, cmd_id=“USERS_NUMBER_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T20:12:34.199183742Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:34.632461242Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(c18cae77) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:12:34.862573450Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(174151d4) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:12:35.062414242Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(014b58f9) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:12:35.252281367Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(14c89bb1) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:12:35.320984658Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(1b8e203d) queued for radio transmission: CC:Battery, CID:0x02
2024-08-07T20:12:35.326662908Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“BATTERY”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T20:12:35.331878283Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:12:35.572958117Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(1b8e203d) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:13:04.172970704Z TRACE Universal Enhanced Z-Wave Lock Found CapabilityCommandDispatcher handler in Universal Enhanced Z-Wave Lock → Z-Wave lock operations
2024-08-07T20:13:04.183391620Z TRACE Universal Enhanced Z-Wave Lock reload_all_codes, cmd {
args={},
capability=“lockCodes”,
command=“reloadAllCodes”,
positional_args={},
}
2024-08-07T20:13:04.199138537Z INFO Universal Enhanced Z-Wave Lock Max lock codes not detected, getting information
2024-08-07T20:13:04.208982662Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(6c44cfad) queued for radio transmission: CC:User Code, CID:0x04
2024-08-07T20:13:04.211775079Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> emitting event: {“attribute_id”:“lockCodes”,“capability_id”:“lockCodes”,“component_id”:“main”,“state”:{“value”:“{}”},“visibility”:{“displayed”:false}}
2024-08-07T20:13:04.217994454Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“USER_CODE”, cmd_id=“USERS_NUMBER_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T20:13:04.228931245Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(7dc310fc) queued for radio transmission: CC:User Code, CID:0x02
2024-08-07T20:13:04.238907704Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={user_identifier=1}, cmd_class=“USER_CODE”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x01”, src_channel=0, version=1}
2024-08-07T20:13:04.252942995Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:04.267761120Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(00734bc4) queued for radio transmission: CC:User Code, CID:0x04
2024-08-07T20:13:04.270483162Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:04.277949370Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:04.286383787Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“USER_CODE”, cmd_id=“USERS_NUMBER_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T20:13:04.291787120Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:05.702463829Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(6c44cfad) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:13:05.962346495Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(7dc310fc) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:13:06.162276079Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(00734bc4) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:13:33.130088540Z TRACE Universal Enhanced Z-Wave Lock Validating if lock has been initialized
2024-08-07T20:13:33.146730165Z TRACE Universal Enhanced Z-Wave Lock Lock initialization incomplete, checking again in 60 seconds
2024-08-07T20:13:33.161191207Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:33.178027999Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(abd9203a) queued for radio transmission: CC:Door Lock, CID:0x02
2024-08-07T20:13:33.181878290Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:33.188376749Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:33.199488790Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:33.206324832Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“DOOR_LOCK”, cmd_id=“OPERATION_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T20:13:33.237930832Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:34.265226249Z TRACE Universal Enhanced Z-Wave Lock Found CapabilityCommandDispatcher handler in Universal Enhanced Z-Wave Lock → Z-Wave lock operations
2024-08-07T20:13:34.274524415Z TRACE Universal Enhanced Z-Wave Lock reload_all_codes, cmd {
args={},
capability=“lockCodes”,
command=“reloadAllCodes”,
positional_args={},
}
2024-08-07T20:13:34.288550040Z INFO Universal Enhanced Z-Wave Lock Max lock codes not detected, getting information
2024-08-07T20:13:34.299286165Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(afb05479) queued for radio transmission: CC:User Code, CID:0x04
2024-08-07T20:13:34.307974499Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> emitting event: {“attribute_id”:“lockCodes”,“capability_id”:“lockCodes”,“component_id”:“main”,“state”:{“value”:“{}”},“visibility”:{“displayed”:false}}
2024-08-07T20:13:34.315528749Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(b8ca45a8) queued for radio transmission: CC:User Code, CID:0x02
2024-08-07T20:13:34.321562624Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“USER_CODE”, cmd_id=“USERS_NUMBER_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T20:13:34.336301999Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={user_identifier=1}, cmd_class=“USER_CODE”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x01”, src_channel=0, version=1}
2024-08-07T20:13:34.348599207Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(0a33d855) queued for radio transmission: CC:User Code, CID:0x04
2024-08-07T20:13:34.354797915Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:34.403529040Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:34.428617582Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:34.458719374Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“USER_CODE”, cmd_id=“USERS_NUMBER_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T20:13:34.478653332Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:34.592601915Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(abd9203a) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:13:34.972420249Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(afb05479) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:13:35.202468916Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(b8ca45a8) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:13:35.354057791Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(96f37a88) queued for radio transmission: CC:Battery, CID:0x02
2024-08-07T20:13:35.378511082Z INFO Universal Enhanced Z-Wave Lock <ZwaveDevice: 66251ae3-a8f0-4d10-a6bf-f332d4efd28f [1A] (Kwikset Door Lock)> sending Z-Wave command: {args={}, cmd_class=“BATTERY”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-08-07T20:13:35.383816416Z DEBUG Universal Enhanced Z-Wave Lock Kwikset Door Lock device thread event handled
2024-08-07T20:13:35.462300291Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(0a33d855) transmit status: TRANSMIT_COMPLETE_OK
2024-08-07T20:13:35.662419957Z TRACE Universal Enhanced Z-Wave Lock Z-Wave command(96f37a88) transmit status: TRANSMIT_COMPLETE_OK
I don’t see any lock/unlock events received by the hub. Again, it appears as if the lock isn’t generating messages or they are not reaching the hub.
Since both drivers are exhibiting the same behavior, it’s got to be something with the lock and/or its location. Is this a brand new lock? It appears this lock supports Z-Wave Plus which means it likely supports S2 security. Did you scan a QR code to set it up or manually enter the DSK when prompted during set up?
Short of placing the lock directly next to the hub to verify that location is not an issue and barring that it’s not an S2 issue, I’d say there is something defective in the Z-Wave module of the device.
The driver is definitely stuck in a loop of trying to initialize the lock set up, but never gets any replies.
1 Like
It’s not a new lock but it was functioning with a Vivint hub at my daughters house. I set the lock up manually since I didn’t have a QR code for it.
I’ve excluded the lock four or five times, I’ve reset it to factory settings three times. Each time the user codes are setup and work. It pairs normally with smartthings,
but the app icon says “Connected” but when clicked on it gives me the “hasn’t updated” message everytime. I have 4 Yale Real living locks that function
very well. This is my first Kwikset smart lock. Your help is much appreciated.
Hmmm, did it ask you for the DSK and you bypassed adding it? Did you add the lock by doing a “Scan Nearby” or picking the specific model to add?
If you skipped adding the DSK, that could be part of the problem. The lock might be sending/expecting encrypted messages or vice versa for the hub.
1 Like
Just to clarify, the Aeotec siren is mains powered but it may not support FLiRS buffering. How can someone tell? Google is being singularly and circularly unhelpful, most of the results return this page and your post about needing a buffering repeater, plus Aeotec’s manuals which all state “do not poll FLiRS devices” in their troubleshooting section.
I have no problem with this driver, using it with different Kwikset 2 locks, but as we all know ST can change that with no notice and I’d like to be a little more bulletproof if I can be. If it’s a matter of suggesting a particular plug, for example, then I’ll put one on my shopping list for the next time I need one.