Steve L Posted July 18 Posted July 18 Two years ago, I bought and installed a Baldwin Touchscreen entry lock, which has the guts of a Kwikset 916. I had no trouble adding it to the ISY994 I had at the time, and it migrated fine to an EISY. Today I bought a second of the same model, but when I added it as a device, all that shows up is "Entry Control" and none of the actual useful nodes I see for the old one. I tried enabling Compatibility Mode, removed and re-added it multiple times, to no effect. This is what I see now: 026 is my old lock, 068 the new one. I've also attached the debug log from adding. There must be something I am missing - please help. ISY-Events-Log.v5.8.4__Thu 2024.07.18 01.21.47 PM.txt
Techman Posted July 18 Posted July 18 What nodes are missing that you need? What device nodes display in the admin console window? It appears that you added the lock in the S0 (non-secure) mode rather than the S2 (secure) mode. The eisy uses a different zwave chipset the the ISY. It's also possible that the device firmware may be different between your 2 devices which could explain the display difference between the 2 locks. Zwave devices will quite often install numerous nodes of which some may not be applicable. This is due to the fact the different hubs support and require different nodes. You can just ignore the nodes that you're not using and/or move them into a folder, which you could call unused nodes, so you don't have to look at them.
Steve L Posted July 18 Author Posted July 18 (edited) I am missing all the nodes that let me control and view the state of the lock - lock, unlock, set codes, view battery level, etc. I show a screenshot of what admin is showing me. The 026 devices has the nodes I want, the 068 does not. This lock does not support S2. Edited July 18 by Steve L
Techman Posted July 18 Posted July 18 What is the ISY firmware and UI? It's possible that when you included the lock something was amiss. Move the lock close to the ISY, then exclude the lock and re-include it
Steve L Posted July 18 Author Posted July 18 EISY 5.8.4 (firmware and UI). I put the lock inches away from the EISY and tried again, same result.
Steve L Posted July 18 Author Posted July 18 Baldwin 8235003ZW. It is electronically the same as the Kwikset 916.
Steve L Posted July 18 Author Posted July 18 No, it is Zwave. Baldwin doesn't offer a Zigbee version.
Techman Posted July 18 Posted July 18 The only other option I can suggest is to remove the lock, do a factory reset on the lock then re-install it. If that doesn't resolve the problem then it's best to open a support ticket as it's possible that the lock isn't fully supported by the eisy https://www.universal-devices.com/my-tickets
Adam Ant Posted July 19 Posted July 19 19 hours ago, Techman said: The only other option I can suggest is to remove the lock, do a factory reset on the lock then re-install it. If that doesn't resolve the problem then it's best to open a support ticket as it's possible that the lock isn't fully supported by the eisy https://www.universal-devices.com/my-tickets Hello, I ran into the same problem with a Kwikset model 206. I have 4 locks (all new). The first two added fine but the 2nd two added as 'entry control" devices that are not controllable. I raised a ticked two days ago but have not heard back. I spent allot money on these locks because i have used them in the past with no issues. Would appreciate any suggestions. I have done a factory reset of the devices but have not done a reset of the dongle (because i don't understand what that would do).
Techman Posted July 19 Posted July 19 Factory resetting the dongle most likely won't resolve the issue, It's best to wait for a reply on your support ticket.
Adam Ant Posted July 19 Posted July 19 11 minutes ago, Techman said: Factory resetting the dongle most likely won't resolve the issue, It's best to wait for a reply on your support ticket. Will do!
Solution Steve L Posted July 23 Author Solution Posted July 23 (edited) My case, at least, was self-inflicted by not carefully reading the instructions. The lock has a central round "Program" button, and two other buttons generally labeled A and B in the instructions. I had been pressing the Program button when adding the lock, but this was incorrect - I should instead have pushed the A button (upper left corner) as directed in the instructions. When I did this, all the nodes got properly added. One does need to clean out the old nodes first. Since this was my second lock, I assumed I knew what to do, but it had been two years and you know what they say about "assume". Edited July 23 by Steve L 1
bob123 Posted July 23 Posted July 23 I had this same issue with a yale lock. I removed the lock from the door and placed it very close to my Policy. Then removed and added it back to the zwave network. Solved the issue.
Recommended Posts