I have had an Alfred DB2S lock on our zwave network for some months now working great. I noticed it is no longer locking when I hit a button at night before I go to bed. Saw that it maybe was a ghost, got it excluded, powered down hub and it was gone on reboot. Did a secure inclusion, but it is not asking for a code, which I thought it did first time I included it. Still cannot lock or unlock door but does get status from door. Zwave pairing info says Zwave Secure Pairing Complete
true
What do you think it problem, it is not connected securely even though it says it is?
Did you put new batteries in it? Thats probably all that was wrong before you excluded it.
Did you include manually or with Smart Start?
Lets see a screenshot of the device in the z-wave details. That shows you the security it is paired with.
I included manually. I recharged the battery some months ago, don't know if that when it stopped responding to lock commands.
Looking for a screenshot from z-wave details. Settings > Z-wave details
From that however, it looks like the pairing may have failed to complete. Some of the info is missing like the secure clusters. If you checked logs during pairing it possibly tossed an error.
Again, possibly a battery issue, and I don't mean new batteries caused the issue. I mean the batteries are possibly weak which is causing the issue.
Click the Refresh Stats button at the top of the page, wait 30 seconds and reload the page, then get a screenshot again.
The Security is showing correctly on there but it would have asked for the 5 digit DSK. I suspect you missed that or there was a failure and the inclusion bailed but you did not check the logs to see the issue.
Based on the missing info on the device page I think its an incomplete inclusion which would explain why the device is not cooperating.
You might have better luck trying again with Smart Start. Also for sure fresh batteries. See Posts 1 & 2: [APP] SmartStart Manager for Z-Wave (Long Range support)
You will want to be sure to exclude the device from the hub, and make sure the z-wave node is removed before you try to include it again if that's what needs to be done.
I'm not sure how to include with smart start. The qr code is on the back of the zwave module. I would have to remove it it to scan it. The lithium battery is at top charge
Well its up to you, was just a suggestion. But if it still wont work correctly I would exclude and include again. Keep the logs open while including to see if there are any errors. Make sure you select to use security and provide the 5 digit PIN/DSK if you include manually.
I keep my boxes for this reason. They usually have the code on the.
I had the smart start card in my zwave folder. I excluded it, powered down hubitat, waited 5 minutes, powered back on. Used smart start and I can now lock and unlock using new Entry Control device. There is a device called door lock and and another called entry control. Only entry control shows up in zwave settings. I have disabled the door lock entry in devices.
1 Like
If you have an extra orphaned device in the devices list, it should be safe to just remove it.
If you check the device info tab, check the DNI (Device Network ID) and it should be a 2 char hex code if it was once attached to a z-wave node. If that is true, and that node is not in the zwave details anymore, then you can remove that device. You may just want to make sure you dont have any rules or apps attached to it anymore.
This thread has me interested in these locks. I didn't see a lot of info on drivers and what is supported on hubitat VS the Alfred app. Since you guys are using them is the zwave module supported VS maybe not the zigbee module? The manager works for codes and we can see which code was used for an unlock? Anyone know if the DB2S card support is visible when using hubitat?
I'm in the US. Frustrated that the lock choices all get me 80% of what I want and almost nothing is perfect in appearance. The Alfred locks look OK and I like the interconnect option they have.
I just have a regular DB1-C. In order to see which code was used to unlock I had to get a firmware update, but that now works. Everything works about the same as my other locks which is one Yale and two Schlage. Works fine with LCM, gives the usual reports.
The family is always confused when they do have to put a code in though. The Yale and Schlage have a very obvious check mark and then the Alfred has a # and * at the bottom of they keypad, they never remember which one is the "enter" button. It is a door we mostly only lock when asleep so we don't use the codes to unlock it very often.
Yes that is a 2 char HEX actually, just happens to have both numbers in it. The working one should be listed in the Z-wave details as 0x00## for the node ID, and the other wont be in the z-wave details. Looks to me like 0x39 has the most recent activity so that might be the working one.
I really like our Alfredb2s. There have been issues with the wifi gateway twice both times swiftly dealt with warranty. 1st time for issue with Zwave. I have nfc card on back of my phone for access. Had lock cylinder swapped out by locksmith to kwikset so keys fit. Locks automatically after 30 seconds and also with goodnight button by my bed.
Thanks. Do you have any control in Hubitat for the rfid functionality? Do you get unlock events with some card info?
Does a person need the wifi gateway?
You do not need the wifi gateway if you are using the zwave plug in module.
I don’t use nfc so can not comment but I can tell you the lock reports what lock code was last used.
No nfc card support in Hubitat that I see. I use the wifi gateway as backup to Zwave and I find that it is easier to manage lock with it. But no, you don't need it to add or remove NFC cards, that is done at the lock
Thanks. That's helpful. Would be useful to manage removing cards from hubitat. Do you get an event that tells you which card was used to unlock?