HE Sees my Kwikset 910 Locks, but stopped controlling it

[charlesrblack]

I have had a Kwikset 190 up and running great (excet for the time it became unresponsive becuse the batteries were dead), and it recently stopped repsonding.

HE can see it, it shows up in my logs, but I can't control it. Here is a snippet of my recent logs, during this time I tried to change the state of the lock both through the web interface and the app...

dev:1422021-01-26 05:48:49.194 pm infoGarage Door Lock is locked

dev:1422021-01-26 05:48:49.190 pm debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:0, doorLockMode:255, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:0)

dev:1422021-01-26 05:48:49.180 pm debugparse: zw device: 2D, command: 9881, payload: 00 62 03 FF 00 00 FE FE , isMulticast: false

dev:1422021-01-26 05:48:38.972 pm infoGarage Door Lock battery is 100%

dev:1422021-01-26 05:48:38.968 pm debugBatteryReport: BatteryReport(batteryLevel:100)

dev:1422021-01-26 05:48:38.948 pm debugparse: zw device: 2D, command: 9881, payload: 00 80 03 64 , isMulticast: false

dev:1422021-01-26 05:48:28.991 pm infoGarage Door Lock is locked

dev:1422021-01-26 05:48:28.987 pm debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:0, doorLockMode:255, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:0)

dev:1422021-01-26 05:48:28.938 pm debugparse: zw device: 2D, command: 9881, payload: 00 62 03 FF 00 00 FE FE , isMulticast: false

dev:1422021-01-26 05:47:21.590 pm infoGarage Door Lock was locked manually [physical][21]

dev:1422021-01-26 05:47:21.586 pm debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:21, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:0, zwaveAlarmStatus:0, zwaveAlarmType:0)

dev:1422021-01-26 05:47:21.448 pm debugparse: zw device: 2D, command: 9881, payload: 00 71 05 15 01 , isMulticast: false

--- Live Log Started, waiting for events ---

[thebearmay]

What driver are you using on it? (might also want to include hub type and version)

[charlesrblack]

I believe it's the C-5. And I'm using the generic z-wave driver

[thebearmay]

Did you move the hub or a repeater recently? One thing you could try is adding the reliable lock app and see if that corrects it.

[Release] Reliable Locks

Reliable Locks app for Hubitat An app that will create virtual locks that 'wrap' your physical lock devices, making them more reliable. Purpose Some smart locks are not reliable about reporting their status changes. For example, my Kwikset z-wave locks will sometimes accept a lock command from Hubitat, lock themselves, but never report the 'locked' state back to Hubitat. This app 'wraps' the locks inside a virtual lock that tries to make them more reliable. Then you expose the virtual re…

[charlesrblack]

I removed a repeater recently, which MIGHT have had something to do with it. Ran a Z-Wave repair and now it's responding again.

Thanks!

[CAL.hub]

I have the same problem. A C-3 hub, Kwikset Z-wave 910. Using Generic Z-wave Lock driver It's been installed a couple of years and I'd say it's never been solid but at least worked most of the time. For the last few months, it reports events but never responds to lock/unlock commands. No log entry, no nothing. I don't think the reliable locks app would help since no number of retries seem to make it through.

I'm on the lookout for a good deal on a Kwikset Zigbee Convert (got a couple last year for $20'ish) to cannibalize.

But it would be nice to get the Z-wave lock to (mostly) functionality.

[thebearmay]

That sounds like it's not receiving the command, have you tried adding a repeater,