ISSUE: setting user code never moves beyond "connecting"

FutureTense / lock-manager

Home Assistant Lock Manager

55 stars 19 forks source link

ISSUE: setting user code never moves beyond "connecting" #76

Closed autumnwalker closed 3 years ago

autumnwalker commented 3 years ago

Describe the bug When attempting to set user code 1 on one of my my Schlage BE469 locks it never moves beyond "connecting". No errors shown in logs. Works fine on my other BE469. Code slots 2 and 3 work fine.

Environment (please complete the following information):

OS: Home Assistant Container
Type of device: Docker
Home Assistant version: 2020.12.1
Hassio/Docker/Core? Docker
Component version: 0.0.45

Logs N/A

firstof9 commented 3 years ago

ozw or zwave ?

autumnwalker commented 3 years ago

zwave as built with 2020.12.1.

I saw the preference for ozw, but I already had a zwave network built.

firstof9 commented 3 years ago

zwave and the BE469 locks have a love/hate relationship with each other, they don't always work correctly. Fortunately they seem to work flawlessly in ozw, so that is the ultimate fix at this time.

belav commented 3 years ago

I left this comment on another issue, I was able to get past the stuck connecting state by using Reset Code Slot under the advanced options section. I'm using ozw, so I'm not sure if that would affect it.