ralbright Posted July 16, 2017 Posted July 16, 2017 Ok, I may have bricked the Z-wave module.... I have been a long time user of Insteon and ISY (started back with the ISY-26). Moved to my new house a few months ago, and I have been slowly redoing the electrical and adding Insteon. Decided that I needed temp/humidity sensors and Z-Wave offered the best bang for my buck. I bought the daughter board for the ISY-994i for Z-Wave installed it, added the module. Even included a few battery operated multi-sensors near the ISY. They would update correctly, moved them to their final position, and viola they were only sporadically responding, tried adding a few range extenders (Aeotec Range Extender 6) to the mix. I even went so far as to have an outlet installed in the attic for the sole purpose of adding a range extender up there (remember redoing electrical...) Well things were still hit-or-miss, so I think I did something STUPID. I tried excluding every device, removed all of my devices (I did not have programs built yet), upgraded firmware on the daughter board (showing as Static Controller, v4.55), reset the dongle, and factory reset the ISY.... (I had in mind to start from scratch similar to what I have done countless times with Insteon.) Insteon devices added back in, no problem. Z-wave.... not so much. I go through the inclusion process when the range extenders first, have them plugged about 1 ft away from the ISY, ISY does not seem them. Grabbed a brand new range extender out of its box, ISY does not see it. Tried the exclusion process, that is a negative ghost rider. Tried the Receive mode, nada. Looking at the Event Viewer with Level 3, and nothing. OH NO!! Looking at the logs this is what I see when I tried adding devices: Sun 07/16/2017 12:17:55 AM : [ZWAVE-TX-NR ] [0105004AC11766] Sun 07/16/2017 12:17:55 AM : [UZW-CMD 1 ] Start Include Sun 07/16/2017 12:17:55 AM : [ZWAVE-RX ] ACK Sun 07/16/2017 12:17:55 AM : [ZWAVE-RX ] [0107004A17010000]... Sun 07/16/2017 12:17:55 AM : [ZWAVE-TX ] ACK Sun 07/16/2017 12:17:55 AM : Listening for Z-Wave devices to add to the network Sun 07/16/2017 12:19:07 AM : [ZWAVE-TX-NR ] [0105004A85182D] Sun 07/16/2017 12:19:07 AM : [UZW-CMD 8 ] Cancel Include/Exclude/Learn Sun 07/16/2017 12:19:07 AM : [ZWAVE-RX ] ACK Sun 07/16/2017 12:19:07 AM : [ZWAVE-RX ] [0107004A18060000]... Sun 07/16/2017 12:19:07 AM : [ZWAVE-TX ] ACK Sun 07/16/2017 12:19:07 AM : Adding Z-Wave devices stopped Sun 07/16/2017 12:19:08 AM : [ZWAVE-TX ] [01030020DC] Sun 07/16/2017 12:19:08 AM : [ZWAVE-RX ] ACK Sun 07/16/2017 12:19:08 AM : [ZWAVE-RX ] [01080120F64C5346]... Sun 07/16/2017 12:19:08 AM : [ZWAVE-TX ] ACK Sun 07/16/2017 12:19:08 AM : [ZWAVE-TX ] [01030002FE] Sun 07/16/2017 12:19:08 AM : [ZWAVE-RX ] ACK Sun 07/16/2017 12:19:08 AM : [ZWAVE-RX ] [0125010205001D01]... Sun 07/16/2017 12:19:08 AM : [ZWAVE-TX ] ACK Sun 07/16/2017 12:19:08 AM : [ZWAVE-TX ] [01030005F9] Sun 07/16/2017 12:19:08 AM : [ZWAVE-RX ] ACK Sun 07/16/2017 12:19:08 AM : [ZWAVE-RX ] [0104010528D7] Sun 07/16/2017 12:19:08 AM : [ZWAVE-TX ] ACK What did I do? How do I fix this? I tried pulling and reseating the daughter board (it is in the lower set of the pins), power cycling, and the other common troubleshooting, but Z-wave is now dead. HELP!!!
ralbright Posted July 16, 2017 Author Posted July 16, 2017 Looking over the error log (which is REALLY full), I find this. Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-29-5] 192.168.2.245:52391->80 Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-29]: GET-->/desc Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-29-5] 192.168.2.245:52394->80 Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-29]: GET-->/services.wsdl Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-29-5] 192.168.2.245:52397->80 Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-29]: GET-->/elkServices.wsdl Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-29-0] Socket not active#2 Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-29] Closing socket w/failure Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-32-5] 192.168.2.245:52400->80 Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-32]: GET-->/sepServices.wsdl Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-32-5] 192.168.2.245:52403->80 Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-32]: GET-->/zwaveServices.wsdl Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-32-0] Socket not active#2 Sun 2017/07/16 08:12:12 AM System -170001 [HTTP:0-32] Closing socket w/failure Sun 2017/07/16 08:12:21 AM System -170001 [HTTP:0-32-5] 192.168.2.48:54670->80 Sun 2017/07/16 08:12:21 AM System -170001 [HTTP:0-32]: POST[1]-->/zwaveServices Sun 2017/07/16 08:12:21 AM System -170001 <s:Envelope><s:Body><u:IncludeDevice xmlns:u="u Sun 2017/07/16 08:12:30 AM System -170001 [HTTP:0-32-5] 192.168.2.245:52422->80 Sun 2017/07/16 08:12:30 AM System -170001 [HTTP:1-29-5] 192.168.2.250:57882->80 Sun 2017/07/16 08:12:30 AM System -170001 [HTTP:0-32]: GET-->/desc Sun 2017/07/16 08:12:30 AM System -170001 [HTTP:1-29]: GET-->/desc Sun 2017/07/16 08:12:30 AM System -170001 [HTTP:0-29-5] 192.168.2.245:52425->80 Sun 2017/07/16 08:12:30 AM System -170001 [HTTP:0-29]: GET-->/services.wsdl Sun 2017/07/16 08:12:30 AM System -170001 [HTTP:0-32-5] 192.168.2.250:57885->80 Sun 2017/07/16 08:12:30 AM System -170001 [HTTP:0-32]: GET-->/services.wsdl Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-29-5] 192.168.2.245:52428->80 Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-29]: GET-->/elkServices.wsdl Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-29-0] Socket not active#2 Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-29] Closing socket w/failure Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-32-5] 192.168.2.250:57888->80 Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-32]: GET-->/elkServices.wsdl Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-32-6] Socket not active#2 Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-32] Closing socket w/failure Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-31-5] 192.168.2.245:52431->80 Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-31]: GET-->/sepServices.wsdl Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-29-5] 192.168.2.250:57891->80 Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-29]: GET-->/sepServices.wsdl Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-31-5] 192.168.2.245:52434->80 Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-31]: GET-->/zwaveServices.wsdl Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-31-0] Socket not active#2 Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-31] Closing socket w/failure Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-29-5] 192.168.2.250:57894->80 Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-29]: GET-->/zwaveServices.wsdl Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-29-6] Socket not active#2 Sun 2017/07/16 08:12:31 AM System -170001 [HTTP:0-29] Closing socket w/failure Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-29-5] 192.168.2.250:57921->80 Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-29]: GET-->/desc Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-29-5] 192.168.2.250:57924->80 Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-29]: GET-->/services.wsdl Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-29-5] 192.168.2.250:57927->80 Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-29]: GET-->/elkServices.wsdl Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-29-6] Socket not active#2 Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-29] Closing socket w/failure Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-31-5] 192.168.2.250:57930->80 Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-31]: GET-->/sepServices.wsdl Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-31-5] 192.168.2.250:57933->80 Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-31]: GET-->/zwaveServices.wsdl Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-31-0] Socket not active#2 Sun 2017/07/16 08:12:36 AM System -170001 [HTTP:0-31] Closing socket w/failure ISY Error Log.v4.6.2__Sun 2017.07.16 08.15.37 AM.txt
jrisken Posted August 6, 2017 Posted August 6, 2017 That just happened to me as well. 1. I have a mostly insteon network 2. I included a zwave device - two, in fact. They both worked fine but at ranges of only a few feet 3. I excluded the devices. 4. I upgraded the zwave firmware (not needed, apparently, since it was already 4.55 - or is that the zwave software?). anyway... 5. I've tried including back in the devices that had included eariler. Zero success. I've tried resetting the zwave dongle (wired in - pro version) to its factory defaults. Rebotting, etc. etc. I'm really disappointed that nobody has responded to your original note. That does not speak well for the forum admin.
dbuss Posted August 6, 2017 Posted August 6, 2017 That just happened to me as well. 1. I have a mostly insteon network 2. I included a zwave device - two, in fact. They both worked fine but at ranges of only a few feet 3. I excluded the devices. 4. I upgraded the zwave firmware (not needed, apparently, since it was already 4.55 - or is that the zwave software?). anyway... 5. I've tried including back in the devices that had included eariler. Zero success. I've tried resetting the zwave dongle (wired in - pro version) to its factory defaults. Rebotting, etc. etc. I'm really disappointed that nobody has responded to your original note. That does not speak well for the forum admin. 4.55 is the correct Z-Wave firmware. What devices are you trying to add?
DennisC Posted August 6, 2017 Posted August 6, 2017 Try excluding the devices again, several times before adding back the weave devices. Sometimes this helps. Dennis
stusviews Posted August 6, 2017 Posted August 6, 2017 I'm really disappointed that nobody has responded to your original note. That does not speak well for the forum admin. jrisken, this is primarily a user-to-user forum. BTW, most Z-Wave networks require a range extender such as the Aeon siren or doorbell. The DSD37 is virtually useless. Also, there's no Z-Wave "pro" module, do you mean an ISY Pro?. ralbright, I don't believe that it's possible to "brick" the Z-Wave module. Have you tried all the Z-Wave correction procedures, for example, healing the network (takes time) and other techniques? And Dennis is correct, excluding before including usually helps.
jrisken Posted August 7, 2017 Posted August 7, 2017 OK. An update. As soon as I posted the above I decided to clear out my logs and see if I could replicate a nice, clean failure path. 1. I deleted the error log. 2. I deleted the other log. 3. I tried re-excluding one device. It was not recognized. 5. I tried including again. It included. 6. So did the other device. The only thing I can think of is that at an earlier stage I did delete a device from the database after it had been unsuccessfully excluded. Another thing: One of the two devices had to be flicked three times in five seconds to exclude it. I mistakenly did it only once. And when it didn't exclude I canceled the exclusion. Maybe that left ISY in some strange state, waiting for further keypresses from the one device while I tried to exclude the next. I have no idea what effect clearing the logs would have had. And I'm sorry I was not more rigorous in enumerating my steps. But in any case things are working again.
stusviews Posted August 7, 2017 Posted August 7, 2017 Z-Wave devices need to be excluded using the Z-Wave menu. Deleting the device using the ISY delete function can leave the Z-Wave mesh network in an unexpected state. Tip: if you delete a Z-Wave device instead of excluding it, then rebooting the ISY will usually bring the device back for the correct exclusion. Tip 2: if the device no longer exists, but appears in the ISY list of devices, then right clicking on the device brings up a menu that allows forcing the failed node to be removed. And I'm glad that everything is working for you
jrisken Posted August 7, 2017 Posted August 7, 2017 DennisC: Yeah. Multiple exclusions may be what finally did it. I suspect part of the issue, though, was the firmware upgrade (which ralbright also mentioned): after that when I tried to exclude I got a message that some system data file could not be found. stusviews: Yeah, by 'Pro' is meant the ISY Pro - in which the ZWave dongle can't get unseated - one of the things I usually check for. As to a range extender:, I was using an iNovelli NZW36 - which I could not get the ISY to 'include' the second time around. People seem agreed on at least a couple of things: The ISY ZWave dongle has abysmal range - unreliable at 10 feet going through only one wall. And: the Aeon Siren may be the best bet for a good range exender. Thanks, everyone, for the responses.
stusviews Posted August 7, 2017 Posted August 7, 2017 After extensive testing, I found that the Aeon (Aeotech) Doorbell as a Z-Wave repeater is equally effective as is the Aeon Siren. Thanks, Gerry.
MWareman Posted August 7, 2017 Posted August 7, 2017 The ISY ZWave dongle has abysmal range - unreliable at 10 feet going through only one wall. The ISY with its zwave dongle was certified by the zwave alliance to perform to at least minimum standards with respect to performance and range. Either way, it's well known that a zwave network needs AT LEAST 3 non-battery powered nodes to function at a minimal reliability level (the ISY is one) - more in larger buildings. Battery devices never repeat, and zwave needs at least two paths to relay the signal for fault tolerance. A zwave network needs designing, unlike Insteon (which is very much plug and play).
mwester Posted August 7, 2017 Posted August 7, 2017 ... A zwave network needs designing, unlike Insteon (which is very much plug and play). For some. For others, the noise susceptibility problems of Insteon make it very much "plug and pray".
Recommended Posts
Archived
This topic is now archived and is closed to further replies.