wmcneil Posted January 29 Posted January 29 I am having a problem including a new GD00Z-8-GC zwave garage door controller in my eisy zwave network. I opened a ticket (#25957) with ISY 30 days ago. It was ignored for quite some time, then I had one response, now it has gone dark again. Universal Devices - what is going on here?: Your usual stellar support has fallen apart for me on this?! The GD00Z-8-GC is supposed to be a new (replacement) device, but it is not functioning correctly after being added, and is appearing differently than other successfully functioning instances of this device in the past. It's not clear to me if the supposedly new device is defective, or if some other problem is occurring? When the device is included, it is appearing as a Entry Control device only. In the past, successful instances of this device have added as a Barrier device (primary device), with three sub devices: Barrier Alarm, Home Security Alarm, and Tamper Alarm. When the eisy saw the device during the include, it prompted me for the PIN, and had S2 and S0 selected, which I left selected (which is what I have done in the past). I clicked on the verify button when the confirm dialog appeared. I have attached the log. On line 1251, "Interview not complete: total=7 successful=2 attempted=3" is reported. It appears that security is not being established during the include. I have tried many reboots, many excludes and includes, and a factory reset of the GD00Z-8-GC device, all with no change in behavior Thanks in advance for you help with this! ISY-Events-Log.v5.8.4__Fri 2025.01.24 02.10.27 PM.txt Quote
wmcneil Posted January 31 Author Posted January 31 To whatever admin changed the title of my thread - I'm trying to understand why the usually excellent support Universal Devices has provided in the past is not currently present for this problem. This is a valid concern, and my title was neither inappropropriate nor inaccurate. Quote
Geddy Posted January 31 Posted January 31 @wmcneil Since you have a ticket open you would need to reply to the existing ticket to possibly make it active again or to bring it to the queue again. It's been stated many times in the last couple of years that the forums are user-to-user support. Yes, UD might monitor the forums and answer questions that are easily answered, but for more involved support it's best to run through the support ticket process. Quote
wmcneil Posted January 31 Author Posted January 31 1 hour ago, Geddy said: @wmcneil Since you have a ticket open you would need to reply to the existing ticket to possibly make it active again or to bring it to the queue again. It's been stated many times in the last couple of years that the forums are user-to-user support. Yes, UD might monitor the forums and answer questions that are easily answered, but for more involved support it's best to run through the support ticket process. As described further above: I am using the ticket process, I have updated the ticket several times to bring attention to it, and the ticket has been open 30 days! The process is clearly broken. Quote
wmcneil Posted February 14 Author Posted February 14 Update on my issue for those who may also have issues with their gd00z-8: In response to my ticket, UD did a remote session and spent a bunch of time looking at the issue. The final conclusion was that the gd00z-8 was not following correct protocols for inclusion using security. I was able to eventually get nortek/nice to ship me another replacement device, and it is behaving exactly the same way: During the inclusion process, after entering the PIN, and verifying the window that contains the full key, a few seconds later the gd00z-8 beeps three times. The eisy continues with the interview process, and eventually the device is added as only an Entry Control device. With all my prior successful instances of successfully adding this device, it appears as a Barrier device (primary device), with three sub devices: Barrier Alarm, Home Security Alarm, and Tamper Alarm. Zwave interview timeout is set to 1 minute. I have tried exclude followed by a factory reset multiple times, and moving the gd00z-8 a couple feet away from the zmatter antenna, all to no avail. I'm fairly certain the three beeps from the gd00z-8 during the inclusion process is an indication that something is not correct. I have spent a large amount of time on this (and UD spent a good hour on it), Nortek/Nice is difficult to deal with (the last rep I talked to insisted they do not support end users). I will spend no more time on this. I'm going to open a new thread to see what other solutions out there are working for folks. Quote
Guy Lavoie Posted February 14 Posted February 14 Interesting, because I picked up one of these just last week (as an open box item on marketplace, for a ridiculous price). I already have a well functioning garage door setup with an Insteon IOLinc. I just thought I'd give it a try and see how it goes, and learn along the way, for possible use if worthwhile. I installed on on my eisy, which has the Zooz 700 series dongle. It took a bit of fiddling but it linked and installed ok, and does appear as a barrier device as you say it should. Works correctly too, as I simulate the door movement with the tilt sensor in my hand. My device list shows 5 nodes; the ones you listed plus "Unattended Op alarm". Are you using a Zooz dongle or the Zmatter one? Quote
wmcneil Posted February 14 Author Posted February 14 1 minute ago, Guy Lavoie said: Are you using a Zooz dongle or the Zmatter one? I am using the Zmatter dongle. I also have successfully used the gd00z-8 in the past, and am currently using one at my vacation home (with a polisy and zmatter dongle) without issues.....The company who currently owns GoControl have not been very helpful, and I've spent all the time I am going to spend with them. UD told me that others have been having trouble recently with their GoControl garage door controllers. Quote
Guy Lavoie Posted February 14 Posted February 14 Sounds like it might be a firmware issue in the opener's controller, especially if the trouble reported by others are for people installing new openers. Quote
wmcneil Posted February 14 Author Posted February 14 44 minutes ago, Guy Lavoie said: Sounds like it might be a firmware issue in the opener's controller, especially if the trouble reported by others are for people installing new openers. I agree, seems likely. If their customer support was better, I'd make another run at them, but after the "We don't support end users" discussion, I'm done. 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.