Kwikset Deadbolt Problems

I have had the same thing happen with me on an Internet outage. However, it is less of concern than me on the cloud area as it is still something in my control. I have my router setup to auto use my aircard if there is an outage. What does concern me is how scalable their backend is. In a way I almost wish they were charging a monthly fee to make sure they never had an excuse to let their infrastructure get behind on the demands placed on it.

Their system sure has its positives and negatives that’s for sure. Their HUB seems to be little more than a glorified dumb transmitter and I imagine that it will be dirt cheap to mass produce. However, that places a lot of reliance on a lot of other factors.

BTW, so far your app is working great. I don’t know if it has resolved the issue of the commands not working every now and then…but if nothing else at last now I don’t have 10 apps for each presence tag’s lock & unlock.

It turns out the Kwikset locks can send notifications when they are manually locked or unlocked, but our hub currently isn’t setting up the Z-Wave association properly to subscribe to these notifications. We’re working to get these notifications interpreted properly.

Thanks for sticking with it as we work through all the issues with door locks. They’re tricky because of the Z-Wave security layer, and they also vary in functionality a lot.

@jleonar I ran into a similar issue today with your app as I have in the past with the default one. I arrived home and my tag jumped right on the network, and your app ran doing its thing with the refresh, and then the unlock command. But, the lock simply never executed the command.

This seems to happen about 1 out of 10 times. Not a huge deal, but the wife has little patience for when I over complicate simple things and then they don’t work as reliably :slight_smile:

That stinks. Hopefully some of the updates that smartthings makes to the Z-wave security layer improves reliability. It sounds like the hub just isn’t sending the command because z-wave has fault tolerance built in and should be able to confirm a command was received by a device.

A good feature for smartthings to lift is failure notifications. The Vera Lite could send me text messages when a lock failed to execute. This only happened in the past for me when I didn’t close the door all the way.

I am really interested to know if the hub received the command and just didn’t do anything or where the communication breakdown is occurring.

EDIT: I forgot to ask, how many security compatible beaming devices do you have in your z-wave network?

I have a lot… But none between the lock and hub. Today it the lock has been acting very odd. It has been failing left and right all day.

The lock continues to fail like crazy over the last 24 hours. The only thing that has changed is I got a new wireless router that’s only a foot away or so (media closet) Would the 2.5/5GHZ frequencies mess with Z-Wave?

@jleonar, ends up my issue was being caused by interference in my media closet. More than likely by my AP with 4G backup modem attached.

@duncan Has there been any progress getting the notifications interpreted properly from the lock?

Also i was trying to get the battery status from the lock with a custom device type but i could not get it working. Is the following code correct?

def battery() {
log.debug "battery"
	zwave.securityV1.securityMessageEncapsulation().encapsulate(
		zwave.batteryv1.BatteryGet()
	).format()
}