Before going live with this HE I wanted to test it first. Based on all the complaints about z-wave locks with HE I figured i would do my own testing first. So far I have had one negative experience with adding a user code that had a start and end date and got some strange error. I posted about that already but it worked the next time I tried so will leave that one for now.
However what just happened today has now happened twice. Yesterday and today. Essentially what happens is my Yale YRD240 with Z-Wave module that is sitting 2 ft from my HE (latest FW available installed as of today) with a beaming repeater less then 10ft away will sometimes ignore an unlock command from dashboard. The deadbolt was locked and dashboard showed that correct. I pressed on the lock from my PC using the mouse and nothing happened to the lock but the icon for the lock on the dashboard hung showing “sending” and I let it sit there for over 3 mins and it never went away. Deadbolt still locked. So next I went to the devices tab and check the state of the lock and it shows locked as status still. I went back to dashboard and it still shows locked not sending as it was hung in. So it’s as if it never got the command. I even check the logs and you can see logs so nothing at all about trying to unlock this deadbolt.
I then try a second time doing the same thing and deadbolt unlocks just fine instantly. I locked it again from dashboard and it locks. Logs show this as photos show below.
Both times this has happened it was the first time I used the lock for the day on 2 separate days. Also have only tried this from my PC, not through the iOS app. Will try with the app next tomorrow. Thoughts?
Search YRD240. There a several reports of issues with the Z-Wave version. However, my YRD256 Z-Wave Plus has never given me any trouble. I don’t have any Z-Wave repeaters or AC powered Z-Wave devices.
I have the EXACT same issues as you. Exact. I'll be watching this thread like you to see if there are recommendations for a fix. This is the only aspect of my home automation at this point that is buggy. But it works almost all the time. Except when it doesn't. And I have a YRD256. I will add that I have a Z-Wave repeater 6 feet away. So it can't be the signal. It's gotta be something else. 90 percent of time it works but when it doesn't I have the same experience as OP.
So a quick update here since my last post. To be sure I can try and isolate the issue, I unplugged the network and power cables and removed the batteries from my SmartThings hub. The only reason I had left it connected was to play Sonos announcements when the Ring doorbell was pressed. But I had migrated everything else to Hubitat already, So after researching how to do it on this forum, I learned how to create a virtual switch in Hubitat, connect the Ring doorbell to Amazon Alexa, create a routine in Alexa, and set up the Notifications App in Hubitat to play announcements over Sonos. Success!! And most important, I am now fully SmartThings free!
Anyway, my theory is that maybe the Z-wave signal coming out of the SmartThings hub was interfering with my Hubitat Z-wave network. I have nothing still connected to the SmartThings z-wave network - but maybe there is frequency overlap or interference, etc.
So now that is gone - there is only one z-wave network in the house. We will see if this changes anything. I was at a 90% success rate but maybe this gets me to 99%+.
Figured I would update my troubleshooting theories if it helps others.
