# Hub Firmware Release Notes - 17.12/17.13/17.14

**URL:** <https://community.smartthings.com/t/hub-firmware-release-notes-17-12-17-13-17-14/83722>\
**Category:** Hub Firmware Release Notes\
**Created:** [April 4, 2017, 1:52pm UTC](https://community.smartthings.com/t/hub-firmware-release-notes-17-12-17-13-17-14/83722 "2017-04-04T13:52:14Z")\
**Posts on this page:** 1\
**Showing post:** 390

<div class="post-metadata">

**Author:** ![duncan](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/duncan/32/11724_2.png) [@duncan](https://community.smartthings.com/u/duncan)\
**Post date:** [June 8, 2017, 7:55pm UTC](https://community.smartthings.com/t/hub-firmware-release-notes-17-12-17-13-17-14/83722/390 "2017-06-08T19:55:43Z")

</div>

The issue was that the hub is automatically secure-encapsulating commands to securely-included devices. It’s now required that devices support everything securely that they support normally, but the first generation of Schlage locks predates that requirement so they were ignoring the secure-encapsulated AssociationSet and ManufacturerSpecificGet commands.

---

_[View the full topic](https://community.smartthings.com/t/hub-firmware-release-notes-17-12-17-13-17-14/83722)._
