Z-Wave DTHs: Changes to Encapsulation Handling Starting in 0.25.X Hub Firmware Release

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

It’s for DTH’s (no changes required for SmartApps) and it was released 2 months ago well before the 25.x firmware was deployed:

[RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung

IMPORTANT: REQUIRED UPDATE FOR UPCOMING FIRMWARE 25.x for V2 and V3 hubs This update is required to continue receiving lock/user usage notifications once ST deploys the 25.x firmware to the hubs (this update is backwards compatible with 24.x and older firmware) Universal Enhanced Z-Wave Lock for Schlage, Yale, Kwikset, IDLock, DanaLock, August Pro, Samsung, Locstar, Delaney, KeyWe and Popp Z-Wave Keypad Device Handler - Version 04.03.01 Support for upcoming 25.x firmware z-wave framework user/lock notifications Improved compatibility with SmartLocks Schlage Lock Alarm Mode and Sensitivity Change and Monitor - Version 02.02.00 < no changes > A SmartApp like Lock User Management (LUM) or SmartLocks is required for programming user codes. To get real time updates with the Smart Locks…

FYI - this topic isn’t related to the Feb release. There were other changes we had incorporated for the 25.x which should fix your locking/unlocking trigger actions.

All our DTH’s are compliant with this update requirement from the get go so it shouldn’t have any impact for most devices. My conversation is Kianoosh is related to a different matter for specific devices which don’t like using secure encapsulation for a specific subset of commands.