Status dashes after pairing my Schlage be469zp zwave smartthings

Devices & Integrations
1

Hello Here

I am running to continious failure with Schlage be469zp devide unresponsive Smartthings hub v3

networkSecurityLevel": “ZWAVE_S2_ACCESS_CONTROL”,

“provisioningState”: “NONFUNCTIONAL”

Tried everything:

Excluded multiple time

Hub less than 1 feet from the lock

reset a lock

Pairing using code

Pairing using QR

Any suggestions?

2

Hi,
Could you please enable support access on your account so we can review some details?

  1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM.
  2. Enable support access to your account:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (⋮) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

More info about this access here: https://support.smartthings.com/hc/en-us/articles/36170233944852-Enabling-Account-Data-Access-for-Support

3

Hello
I did updated settings as required

4

We’re going to need additional information to properly analyze the issue.
Please follow the steps to capture the driver logs first.
Logs of the driver:

  1. Open the ST CLI
  2. Enter the command smartthings edge:drivers:logcat
  3. Enter the information requested by CLI
  4. Now you must be able to see the logs once you see the message “connected”
  5. Then, send the commands (that aren’t working) to the devices so they get registered there
  6. Copy those logs into a file and share it with us. You can send it to build@smartthings.com.

Note: If you get an error related to the connection, verify that the hub and the computer are in the same network.

Once that’s done, please send us the Hub logs as well.
Provide the Hub logs through the my.smartthings.com:

  1. In the my.smartthings, enter “your hubs”
  2. Enter the corresponding Hub
  3. Click on “Dump Hub Logs”
  4. Change the reason for requesting hub logs if needed
  5. Click on “Dump Hub Logs”
  6. Confirm that the request is submitted
    Note: If you have more than one Hub, the name of the one involved in the issue.

Also, please don’t forget to share the exact timestamp (including the time zone) when you send the command.
This will help our team review the full sequence of events.