# Saga Continues with My Schlage Connect and New Smartthings App

**URL:** <https://community.smartthings.com/t/saga-continues-with-my-schlage-connect-and-new-smartthings-app/205167>\
**Category:** General Discussion\
**Created:** [September 14, 2020, 4:58pm UTC](https://community.smartthings.com/t/saga-continues-with-my-schlage-connect-and-new-smartthings-app/205167 "2020-09-14T16:58:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![RBoy](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/rboy/32/62677_2.png) [@RBoy](https://community.smartthings.com/u/RBoy)\
**Post date:** [September 14, 2020, 10:52pm UTC](https://community.smartthings.com/t/saga-continues-with-my-schlage-connect-and-new-smartthings-app/205167/2 "2020-09-14T22:52:17Z")

</div>

Try a few things:

1. Exclude the lock
2. Remove the Alexa integration
3. Delete all your existing SmartThings devices from the native Alexa app
4. Pair the lock with the hub
5. Connect Alexa to SmartThings

You may also want to look at this topic which may help if you’re experiencing performance issues: [FAQ: why would I need another beaming repeater if my zwave lock is already close to my hub?](https://community.smartthings.com/t/faq-why-would-i-need-another-beaming-repeater-if-my-zwave-lock-is-already-close-to-my-hub/137629/2)

In addition the Schalge Connect BE449 has a firmware bug which causes missed notifications, this device handler can help fix that issue: [[RELEASE] Universal Enhanced Z-Wave Lock Device Handler for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung](https://community.smartthings.com/t/release-universal-enhanced-z-wave-lock-device-handler-for-schlage-yale-kwikset-idlock-popp-danalock-august-pro-keywe-philia-samsung/6241/1455)

---

_[View the full topic](https://community.smartthings.com/t/saga-continues-with-my-schlage-connect-and-new-smartthings-app/205167)._