Schlage connect is stuck in "locked" state

Just moved all my stuff over to a new install due to unrelated issues. Have everything up and running again except for my schlage connect. Its acting oddly.

I completely unpaired it then factory reset the lock then repaired it (securely). After first boot, the front end will correctly show it unlocked. Toggling it will lock the lock and update the front end, although in its locked state the toggle will have a glow around it.

Toggling it again to unlock it will unlock the lock but after that HASS only shows its state as locked going forward and toggling the button does nothing.

I have done the unpairing - repairing procedure twice and that doesnt seem to do much of anything. Any ideas?

Im getting the following errors:

2017-02-11 12:53:43.642 Error, Node044, ERROR: Dropping command, expected response not received after 1 attempt(s)

017-02-11 12:53:07.101 Warning, Node003, WARNING: Device is not a sleeping node.
2017-02-11 12:53:07.101 Error, Node003, ERROR: node presumed dead

2017-02-11 12:53:22.582 Error, Node040, ERROR: Dropping command, expected response not received after 1 attempt(s)

Saw your comment, just stopping by to say that it somehow fixed itself. I am pretty sure that I did not update HA or anything, but it is unlocking and showing unlocked, then I can later lock it.

The ONLY possible change I recall is that I changed the door’s mode so it locks after 30 seconds of being unlocked.

Im confused…did you have this same issue?

I have this issue too. It’s my first z-wave device, so it’s possibly due to not having any additional nodes. I see the same things as you in my OZW_log.txt. I seem to be able to control it through the HASS UI for a short time after manually locking/unlocking and at random other times. The node will go dead and then suddenly become ready after I walk out the door and lock it manually. My lock is about 30 feet from my controller. I was able to pair it fine from this distance, so not 100% sure what the dealio is yet.