You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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.
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?
The text was updated successfully, but these errors were encountered: