vmastros Posted February 7, 2020 Posted February 7, 2020 I have an ISY 991i running my Inseteon system. Currently, I have a Mi Product deadbolt lock operating through a Morning Link control. My skills are limited as I don't write code or understand it. I want to get a new Z Wave deadbolt, but, after reading all the trials and tribulations about installs on this forum, I'm not so sure I can pull off a successful install without a lot of help. I know people using the forum are ones having problems and there may be many people who have no problem. I know I have to add the Z Wave dongle. So, my question is, "Can a novice pull off a successful installation?"
Mecheng70 Posted February 7, 2020 Posted February 7, 2020 Will this be the only zwave device in the system? If so, then you have communication issues due to distance/walls/etc. I have 4 doors locks and >15 hard wired zwave bulbs/relays/switches. When I initially set up the system there was only 4 doors locks. The communication was sporatic. Once the mesh network was built out and healed, it has been stable.
vmastros Posted February 7, 2020 Author Posted February 7, 2020 At this point, yes that would be the only Z wave device. Physically it would be about 20 feet from the ISY to the deadbolt but there’s a few walls in between.
Mecheng70 Posted February 7, 2020 Posted February 7, 2020 IHMO I would install a zwave plug or switch near the door lock. They have zwave repeaters that may work. Aeotec Don't have any experience with them as the plan was to go completely zwave in all my switches/outlets. If you are going to spend $30 for the repeater that uses an outlet, I would purchase an zwave outlet so that there would be 2 usable outlets. Zwave Outlet Remember to exclude before include.... <<<- my biggest learning with Zwave
vmastros Posted February 7, 2020 Author Posted February 7, 2020 so, if the zwave mesh network is good, is it similar to adding an Insteon device? Would a Smarthub be the way to go for me?
simplextech Posted February 7, 2020 Posted February 7, 2020 1 minute ago, vmastros said: so, if the zwave mesh network is good, is it similar to adding an Insteon device? Would a Smarthub be the way to go for me? The ISY is a "smart hub" and the difficulty/problems will be the exact same with any other "hub". Z-Wave devices especially locks require a good mesh network to operate. The ISY z-wave radio is fairly weak so you may need more devices to create a good mesh than you might with another system but you will still need more than 1 device. All Z-Wave Plus powered devices act as repeaters so there's a lot to choose from. If you are going to use Network Wide Inclusion (NWI) then you will need devices that also support encryption. Generally as locks are battery powered it's easiest to include them BEFORE installing them and do it very close to the ISY to ensure the encryption keys are exchanged correctly and verify functionality before installing the lock. Then if you have problems you can add repeaters and perform a network heal and continue adding repeaters and performing a network heal until you have satisfactory results from the lock. Some have general ideas of distances between devices but it really varies between devices and their radio strength. I have some plugs that have great radio's and I get great distance from them even through walls. I have other plugs that don't operate correctly in the same room as the ISY and need another repeater to work.
lilyoyo1 Posted February 7, 2020 Posted February 7, 2020 1 hour ago, vmastros said: At this point, yes that would be the only Z wave device. Physically it would be about 20 feet from the ISY to the deadbolt but there’s a few walls in between. When it comes to supported devices, most issues are due to user error, poor zwave mesh, or a combination of both. Unless you plan on investing in repeaters then you shouldn't go down this path. Without a strong mesh network you'll have problems (even if it initially works). Generally I use 20-30 feet line of sight to determine how many devices I need. For every wall, I cut that number in half. Once I have a count, I add 1 to it due to the self healing nature of zwave. I do not count the controller as they are notoriously weak devices for talking to battery operated devices. In your case, 2 devices should suffice. Ensure that everything you purchase is zwave plus and the repeaters support beaming. I don't like plug in devices so I use ge outlets
vmastros Posted February 7, 2020 Author Posted February 7, 2020 Ok, thanks again. I think I'm up for the challenge (with your help, of course).
vmastros Posted February 12, 2020 Author Posted February 12, 2020 OK, I have the Z Wave Module installed. I think I was successful adding the lock. I can operate the lock from the Admin Console, however, I get this error message. I tried to exclude the device (per Mecheng70), but ISY does not seem to find it. What do you folks think is going on? Thanks for the help.
dbuss Posted February 12, 2020 Posted February 12, 2020 Most likely you will need to add additional zwave devices to build your mesh network to improve the communications between devices.Sent from my SM-N950U using Tapatalk
lilyoyo1 Posted February 12, 2020 Posted February 12, 2020 56 minutes ago, vmastros said: OK, I have the Z Wave Module installed. I think I was successful adding the lock. I can operate the lock from the Admin Console, however, I get this error message. I tried to exclude the device (per Mecheng70), but ISY does not seem to find it. What do you folks think is going on? Thanks for the help. Did you get the repeaters installed?
vmastros Posted February 12, 2020 Author Posted February 12, 2020 Right now, the lock is about 6 inches away from the ISY. Is that not close enough? I know I might need more devices for the mesh network when I install the lock on the door, but I'm thinking communication should not be an issue when the device is next to the ISY. Am I wrong? The part that confuses me is that I can operate the lock via ISY but I still get the communication error message.
dbuss Posted February 12, 2020 Posted February 12, 2020 Many times the lock needs to be that close to the ISY to make the initial inclusion, so that was a good decision on your part. It's unusual for the device to be that close to your ISY and be able to operate the lock from the admin console and still get communication errors. I would be tempted to exclude the lock and then add it again to your ISY.Sent from my SM-N950U using Tapatalk
dbuss Posted February 12, 2020 Posted February 12, 2020 You may also want to try and move the lock a little further away from your ISY. When you have transmitters and receivers that close, it's possible to overload a receiver with the rf signal and cause the receiver to not work properly.Sent from my SM-N950U using Tapatalk
vmastros Posted February 12, 2020 Author Posted February 12, 2020 This is what I got when I added a GE receptacle. The device works fine, even used it in a program. Back to the lock, I deleted the lock which caused other problems. I put the lock in program mode, the ISY identifies a Z Wave device but the lock times out before ISY can complete the addition. It adds it as an "unitiated device". I don't know how I was able to add the lock the first time.
Mecheng70 Posted February 12, 2020 Posted February 12, 2020 I have received those unsolicited messages before. Michael mentioned to me not to worry about them. Is the GE switch near the lock? between the ISY and door lock? You mentioned "delete" did you mean "excluded"? Not sure the action that you need to do it you deleted the node and didn't exclude. Is there a factory reset option on the lock? With my kwikset locks, I had to do this at least once. After doing a factory reset, try to exclude it. Then go into the zwave menu and turn on the keep alive for battery devices. Turn that on for the inclusion process then it to put back to sleep. Put the device in inclusion mode and ISY into inclusion mode. Until it "grabs it" I normally lock and unlock the device so that it sending out a signal. go into zwave menu and "heal network" -> some may say that this isn't necessary, however, I do this after any inclusion.
vmastros Posted February 13, 2020 Author Posted February 13, 2020 1. They are in the same room with the ISY. 2. I put the lock in pairing mode and then clicked the exclude tab but ISY never found any device to exclude. So I just deleted the device. 3.Did That 4.Did that but got no confirmation it was excluded. 5.Did that 6. Did that; got this 7.Healing did not help I don't know what else to do except send it all back. Thanks for your help though.
Mecheng70 Posted February 13, 2020 Posted February 13, 2020 I would send in a message to support. They are pretty responsive.
lilyoyo1 Posted February 13, 2020 Posted February 13, 2020 What's your firmware and UI? I would clear java cache, factory reset the zwave board, and then try again
vmastros Posted February 13, 2020 Author Posted February 13, 2020 I have cleared the cache and reset the lock with no improvement. Firmware and UI are both 4.7.5
lilyoyo1 Posted February 13, 2020 Posted February 13, 2020 what zwave board are you using? If its the 500 series then its the wrong one which could be contributing to your issues
Mecheng70 Posted February 13, 2020 Posted February 13, 2020 FYI - There is a report of schlage locks and B/C firmware possibly not working.
vmastros Posted February 14, 2020 Author Posted February 14, 2020 Thank you all for your help. After several email back and forth with Michel, I was not able to get either the lock or the receptacle working properly. I had the lock working on my first install attempt but got many communication error messages. I deleted the lock but was never able to add it again. After a day and half working on it, I gave up. I don't know if the lock or the ISY, or both, were the problem. Most likely is user error though. The answer to my original question is "Harder than it should be."
Mecheng70 Posted February 14, 2020 Posted February 14, 2020 Sorry to hear that. Very strange that the receptacle and lock are both not working.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.