Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Locks Status update slow after SmartThing Firmware 25.26 #116

Open
scottyfutorg opened this issue Mar 29, 2019 · 3 comments
Open

Locks Status update slow after SmartThing Firmware 25.26 #116

scottyfutorg opened this issue Mar 29, 2019 · 3 comments

Comments

@scottyfutorg
Copy link

scottyfutorg commented Mar 29, 2019

After the SmartThings 25.26 firmware upgrade, status stopped updating. I switched to the ZWave Lock IDE to get status to function properly. I have automation based on current status. Then of course Lock Manager doesn't function correctly with the basic handler. Locks are all Kwikset 912.
Additionally, Battery level was previously not updating at all while on the ZWave Lock Reporting device handler.
Any ideas?

@aselinger2
Copy link

I'm having this same issue. Since the update, manual lock state changes are not updated. Forcing a refresh from SmartThings or using it to lock/unlock makes the lock update status properly. Kwikset 910 locks. If I go back to a standard handler, status refreshes immediately so the issue is definitely with the Lock Manager.

@mxdumas
Copy link

mxdumas commented Mar 31, 2019

Same here. The lock stopped arming and disarming the house since last firmware upgrade. Also on 25.26.

@aselinger2
Copy link

I was able to resolve this. Found that I was using a much older version of the lock manager that has custom device handlers and separate components for the Smart App. I set the locks back to the default "Zwave Lock" device handlers, deleted the Lock Manager device manager and all of the Smart App modules. Then, updated the Smart App from Repo, installed in the SmartThings app (Classic), re-configured the locks and all is well. Manual events are recorded properly and now, as a bonus, it even reports which code was used by user name instead of saying "unlocked by Code 1", etc.

Hope this helps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants