I have had my Alfred for 10 months now and I am loving it. This is the first time I am having an issue.
It is no longer responding to lock and unlock commands from RM.
I first noticed this two nights ago. I have been keeping up with the software patches so I don’t know if it’s related or not. I have it connected to a C7 with S2 enabled of course.
Just getting to debugging a bit today. I don’t see any errors in the logs.
I can not lock/unlock from the device page either.
The state of the lock is being reported just as fast as it always has and is sending lock codes being detected etc. Everything’s else seems normal.
Operation from the Alfred app connected via BT is fine, so there isn’t any electromechanical issues. Batteries were at 55% but I replaced them just in case.
Just seeing if anybody else has issues before I factory reset the lock and reinclude.
I've had the db2 for about 8 months and haven't had any issues. This is been the most consistent lock that I've had yet. I think the routing suggestion is a good choice.
I was only able to role back to 2.2.8.154. Tried it and same thing.
I will exclude tomorrow and factory reset and reinclude.
I would have done it tonight but I can’t remember how to exclude/include. I will have to dig out my documentation. I could only find the factory reset procedure online.
New zwave module from Alfred. No change. Still gets stuck on INITIALIZING after I type in the five digit S2 key.
Back in zwave details if I hit DISCOVER I get zwave busy messages.
Leaning on @bobbyD i have excluded my two Zooz double plugs that have always been in my system since receiving my C7. They have power reporting disabled or minimized where available and parameter 18 set.
Anyway they are now gone.
Inclusion of the DB2-B still gets stuck, busy messages still present when I try to discover.
Really running out of options but I am leaning towards thinking my hub is at fault.
My wife has already told me to just put in a regular lock. WHAT ?!?!?
Next I am going to try am inclusion of a zen76 that I have on the shelf in S2 mode to see if that is successful.
It wasn't a re-flash perse. He upgraded the Z-Wave firmware to a version that it was in internal testing at that time (7.15, if I remembercorrectly). Since then, a newer version is publicly available. If you didn't update the Z-Wave firmware, give it a shot.