Kwikset 910 z-wave This device hasn't updated all of its status

Devices & Integrations
1

I’ve been struggling to get 2 locks I bought off Facebook market place to work. I’m not sure what else to try.
I’m able to connect them to my location and they display as “Connected”
On the app when i click the locks I get the message: “This device hasn’t updated all of its status information yet. Check again later.”
I’ve done the following multiple times with the same result. My other locks work just fine. Same model.

  • I’ve reset the locks (Z-Wave Exclusion, Reset Locks)
  • Rebooted the hub
  • Added the locks
  • Z-Wave Repair
    I also enrolled the hub via the website into “SmartThings Drivers Beta” and installed Z-Wave Lock Driver. Driver ID:0f206d13-508e-4342-9cbb-937e02489141
    After this I took the above steps multiple times, and still no luck.

Kwikset 910 z-wave locks
Model: 450191 IC: 3022A-450191ZWV
SmartThings Hub Firmware Version: 000.053.00019

image
image414×818 31 KB

2

Try the Z-Wave Lock PH driver

3

Thank you for the response.
I enrolled in the channel Z-Wave Drivers - phih30 and installed the Z-Wave Lock PH driver.
On the app I was able to update and select Z-wave Lock PH Driver for the locks
After that no change unfortunately.

  • I did a Z-Wave Repair, hub reboot and then Z-wave repair again, still no change.
  • I just finished doing a Z-Wave Exclusion for the kwikset locks on the app, and adding them again. They installed with the Z-wave Lock PH Driver automatically this time. But I still get the same result on the app.

Any other things to try?

4

I would try to be exclude lock and then repair the lock so it picks up the new driver

5

I tried doing things in the suggested order and no luck.

6

I downloaded smartthings.exe on my windows pc to use the smartthings-cli and logging.
And ran this: command .\smartthings edge:drivers:logcat
I went back to using the Z-Wave Lock driver

Is possible even though the locks “work” and connect to smartthings, but that they are faulty or corrupted in someway? If i can determine this, I could then send them back and get a refund. And just buy new locks.

Logs look ok to me. I would have to compare them to a working lock, to see the difference though.
…
8 0f206d13-508e-4342-9cbb-937e02489141 Z-Wave Lock
9 58b24fe2-78dc-413c-bd11-ed386676ef9e Z-Wave Lock PH
10 59869ce8-ee90-4c26-b465-19b7b071d521 Z-Wave Lock PH BETA
Select a driver. 8
connecting… connected
2024-09-21T14:11:54.060553825Z TRACE Z-Wave Lock Found CapabilityCommandDispatcher handler in zwave_lock
2024-09-21T14:11:54.076743950Z TRACE Z-Wave Lock Z-Wave command(04ff25c0) queued for radio transmission: CC:User Code, CID:0x04
2024-09-21T14:11:54.093181992Z INFO Z-Wave Lock <ZwaveDevice: ebb2d167-bc28-4bfd-9455-92c95c10a142 [11] (KwikSet Door Lock 2)> emitting event: {“attribute_id”:“lockCodes”,“capability_id”:“lockCodes”,“component_id”:“main”,“state”:{“value”:“{}”},“visibility”:{“displayed”:false}}
2024-09-21T14:11:54.097730659Z TRACE Z-Wave Lock Z-Wave command(5a18ad67) queued for radio transmission: CC:User Code, CID:0x02
2024-09-21T14:11:54.103053409Z INFO Z-Wave Lock <ZwaveDevice: ebb2d167-bc28-4bfd-9455-92c95c10a142 [11] (KwikSet Door Lock 2)> 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-09-21T14:11:54.114210075Z INFO Z-Wave Lock <ZwaveDevice: ebb2d167-bc28-4bfd-9455-92c95c10a142 [11] (KwikSet Door Lock 2)> 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-09-21T14:11:54.122851492Z DEBUG Z-Wave Lock KwikSet Door Lock 2 device thread event handled
2024-09-21T14:11:54.131875575Z DEBUG Z-Wave Lock KwikSet Door Lock 2 device thread event handled
2024-09-21T14:11:56.765715409Z TRACE Z-Wave Lock Z-Wave command(04ff25c0) transmit status: TRANSMIT_COMPLETE_OK
2024-09-21T14:11:56.995554492Z TRACE Z-Wave Lock Z-Wave command(5a18ad67) transmit status: TRANSMIT_COMPLETE_OK
2024-09-21T14:12:15.490019745Z TRACE Z-Wave Lock Received event with handler capability
2024-09-21T14:12:15.678529495Z TRACE Z-Wave Lock Z-Wave command(6d38559b) queued for radio transmission: CC:Door Lock, CID:0x02
2024-09-21T14:12:15.749189745Z INFO Z-Wave Lock <ZwaveDevice: ebb2d167-bc28-4bfd-9455-92c95c10a142 [11] (KwikSet Door Lock 2)> received command: {“args”:{},“capability”:“refresh”,“command”:“refresh”,“component”:“main”,“positional_args”:{}}
2024-09-21T14:12:15.755555036Z TRACE Z-Wave Lock Z-Wave command(34bbf667) queued for radio transmission: CC:Battery, CID:0x02
2024-09-21T14:12:15.842608828Z TRACE Z-Wave Lock Found CapabilityCommandDispatcher handler in zwave_lock
2024-09-21T14:12:15.910207036Z INFO Z-Wave Lock <ZwaveDevice: ebb2d167-bc28-4bfd-9455-92c95c10a142 [11] (KwikSet Door Lock 2)> sending Z-Wave command: {args={}, cmd_class=“DOOR_LOCK”, cmd_id=“OPERATION_GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-09-21T14:12:15.934905245Z INFO Z-Wave Lock <ZwaveDevice: ebb2d167-bc28-4bfd-9455-92c95c10a142 [11] (KwikSet Door Lock 2)> sending Z-Wave command: {args={}, cmd_class=“BATTERY”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2024-09-21T14:12:15.942639286Z DEBUG Z-Wave Lock KwikSet Door Lock 2 device thread event handled
2024-09-21T14:12:17.095807245Z TRACE Z-Wave Lock Z-Wave command(6d38559b) transmit status: TRANSMIT_COMPLETE_OK
2024-09-21T14:12:17.295574078Z TRACE Z-Wave Lock Z-Wave command(34bbf667) transmit status: TRANSMIT_COMPLETE_OK
2024-09-21T14:12:18.523147037Z TRACE Z-Wave Lock Received event with handler capability
2024-09-21T14:12:18.544756495Z TRACE Z-Wave Lock Z-Wave command(c38c6751) queued for radio transmission: CC:Door Lock, CID:0x02
2024-09-21T14:12:18.552633870Z INFO Z-Wave Lock <ZwaveDevice: ebb2d167-bc28-4bfd-9455-92c95c10a142 [11] (KwikSet Door Lock 2)> received command: {“args”:{},“capability”:“refresh”,“command”:“refresh”,“component”:“main”,“positional_args”:{}}
2024-09-21T14:12:18.557174370Z TRACE Z-Wave Lock Z-Wave command(4ca9aa5c) queued for radio transmission: CC:Battery, CID:0x02

7

This issue is a classic symptom of packet loss in the network. Locks are FliRS devices and need special buffering devices to reliable communications. See this post for details

Drivers by themselves cannot fix a packet loss issue, there are other features which can be enabled through drivers, see this post for a list of available features for this lock over zwave

2 Likes
8

I purchased the Minoston 800 z-wave plug, and still have the same issue.
I placed my repeater and lock close together and about 45ft away from the hub. Rebooting the router, and hub. Also removed and readded the lock, doing z-wave repairs along the way.
From the logs, I can’t tell if the lock is using the Minoston to communicate or not though.