Android App Oddity

[JOHN WADE]

Michael,  I have a customer with multiple kwikset zwave locks.  Often when using the app, one of them will show up as unassigned.  The zwave tools show the device in normal status with good signal strength and battery level and multiple routing paths.  Can you advise?

[Michael Burrell]

John,

I believe what they are experiencing is a jammed or malfunctioning state in the lock. It has been reported that in this event the android app will indicate an unassigned lock as it is having trouble displaying the trouble issue. Physically locking or unlocking the lock clears the issue. We are working on an update to address the issue.

Thanks,

Mike

[JOHN WADE]

This is still an issue that seems unrelated to lock troubles/errors and extends to zwave devices being randomly shown as “missing” despite apparently good signal strength and multiple connections.  The latest lock to show unassigned has ten device connections.  When you click on it to assign it to a named lock, the save is accepted but it still shows unassigned.

[Michael Burrell]

John – We have addressed this in a firmware that we have been testing that will resolve this. We plan to update the control and mobile apps. The mobile app update will remove this missing/unassigned issue. But the controls handling of zwave messages will be updated as we.

The issue your currently seeing is the app does not support the error codes properly from the Z-wave device. So it defaults to missing/unassigned, which is not intended behavior.

I will update this when we get the releases out.

Thanks,

Mike

[Keith Belt]

This may also be partially a Kwikset issue.  I’m not sure how similar\dis-similar the ZWave operates between M1 versus E27, but we have a half dozen Kwikset locks across three different M1 installations, and all of them frequently “forget” the locks are out there.  They show fine on the ZWave controller, but the M1’s can’t seem to operate them.  It comes and goes, but more often than not we can’t get them to work.  I’m guessing its because the M1 ZW interface doesn’t actually assign the locks directly by ID but based on “the first lock it finds”.

[Jeff Noel]

I have seen this issue on Weiser locks (Canadian version of Kwikset as far as I understand).  I have talked to Michael about this in the past, and actually a firmware update this winter did seem to improve things for me.  So if you aren’t running the latest firmware, I would recommend that you get it updated.

When I was having issues last year, I would have to go in and unassign the Lock from the device I had made for it, and save it.  Then go back in and reassign the lock to the device.  This would usually get it working again for a while.

Since the update this winter I have not been having that issue as often, they seem a lot more stable.

The fact there are further improvements coming will be good though, as I’ve found Weiser locks to always be finicky.

[Author]

Posts