[ANSWERED]: Linear GD00Z-4 GD00Z-4 Z-Wave Garage Door Opener

Well I guess I spoke to soon. This morning the Garage Door wouldn't open. I had to exclude it and include it again so I got about 3 days of it working correctly before it failed. Also it still has no Firmware version.

So what's the verdict on this device? I see people kinda getting it to work, but it's not on the official list.

This would go on a system with Indigo7 and ZStick w/500 series chip.

Amazon's having a sale. Should I buy it? haha

I've had this installed at my house for a couple of months now and it functions just fine. I'm got the older Gen 2 Z-Stick (shortly to be replaced) with the latest version of Indigo. It just works.

[matt (support)]

Yep, it is officially supported now. We'll be adding it to the supported device list page soon.

[matt (support)]

I needed to make a change to the device definition for this module because of a problem with an OEM'd version of it. I believe the change is compatible with the Linear version, but I want to make sure. So if you previously had this module working then can you try this beta release of the Z-Wave library? I'm interested in knowing of both a re-sync succeeds as well as the ability to open/close it continues to work. Thanks!

I installed and confirmed it still works with my original "Linear" branded device. I still don't get push notifications of status change.

Z-Wave Debug SENT nonceRequest: 01 09 00 13 0F 02 98 40 25 08 1D
Z-Wave Debug RCVD nonceReport: node 015, nonce AD 01 06 D6 1B 84 29 64
Z-Wave Debug SENT requestBarrierStatus: 66 02 (encrypted)
Z-Wave Debug RCVD nonceReport: node 015, nonce 23 C5 A5 3C 8F 1A 4A 6A (saving)
Z-Wave sent "Main Garage Door" status request
Z-Wave Debug RCVD nonceFetch: node 015
Z-Wave Debug SENT nonceReport: 01 11 00 13 0F 0A 98 80 DF 46 8C 46 F5 59 E2 19 25 0A CB
Z-Wave Debug RCVD encryptedPacket: 00 66 03 FF (decrypted)
Z-Wave Debug RCVD requestBarrierStatus: 01 09 00 04 00 0F 03 66 03 FF FF
Z-Wave Debug . . requestBarrierStatus: node 015, endpoint None, value 255
Z-Wave received "Main Garage Door" status update is open
Z-Wave Debug SENT setBarrierValue: 66 01 00 (encrypted)
Z-Wave Debug RCVD nonceReport: node 015, nonce 8C FE 39 66 01 11 61 31 (saving)
Z-Wave sent "Main Garage Door" close
Z-Wave Debug intiatingSyncUI (timeout in 1500 seconds)
Z-Wave Syncing - started for "Main Garage Door"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 0F 01 01 76
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 9E 80 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 42
Z-Wave Debug . . getNodeNeighbors: nodeId 015, neighbors: 2, 3, 4, 5, 8, 16, 18
Z-Wave Syncing - retrieved module neighbors list: 2, 3, 4, 5, 8, 16, 18
Z-Wave Syncing - assigning return route to "015 - Main Garage Door"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 0F 01 B2
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 015, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 0F 24 0C BE
Z-Wave Debug RCVD nodeInfoFrame: 01 0C 00 49 84 0F 06 04 40 07 72 98 5A C4
Z-Wave Debug . . nodeInfoFrame: node 015, combined class list: 20v1 98v1 72v1 5Av1 66v1
Z-Wave Debug SENT nonceRequest: 01 09 00 13 0F 02 98 40 25 0D 18
Z-Wave Debug RCVD nonceReport: node 015, nonce AC 99 B6 5D BD 61 EC EC
Z-Wave Debug SENT requestEncryptedCmdClasses: 98 02 (encrypted)
Z-Wave Debug RCVD nonceReport: node 015, nonce 0A F2 48 35 90 F3 A4 FC (saving)
Z-Wave Debug RCVD nonceFetch: node 015
Z-Wave Debug SENT nonceReport: 01 11 00 13 0F 0A 98 80 3B 17 90 3A 52 1C 4B F0 25 0F B9
Z-Wave Debug RCVD encryptedPacket: 00 98 03 00 86 66 22 71 85 EF (decrypted)
Z-Wave Debug RCVD requestEncryptedCmdClasses: 01 0F 00 04 00 0F 09 98 03 00 86 66 22 71 85 EF FF
Z-Wave Debug RCVD requestEncryptedCmdClasses: node 015, classes 86 66 22 71 85 EF
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 0F 02 72 04 25 10 AB
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 0F 08 72 05 01 4F 47 44 30 30 C8
Z-Wave Debug . . requestManufactureInfo: node 015, manufacturerId 014F, productId 47443030
Z-Wave Debug . . requestManufactureInfo: LinearLinc, Garage Door Controller (GD00Z-4)
Z-Wave Syncing - retrieved manufacture and model names: LinearLinc - 014F, Garage Door Controller (GD00Z-4) - 47443030
Z-Wave Debug SENT requestVersInfoGen: 86 11 (encrypted)
Z-Wave Debug RCVD nonceReport: node 015, nonce E2 E2 B3 36 FE 2E CE 71 (saving)
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug SENT nonceRequest: 01 09 00 13 0F 02 98 40 25 12 07
Z-Wave Debug RCVD nonceReport: node 015, nonce 57 5B 83 88 40 08 5A 11
Z-Wave Debug SENT requestVersInfoGen: 86 11 (encrypted)
Z-Wave Debug RCVD nonceReport: node 015, nonce 6D F3 B2 F3 43 06 C4 34 (saving)
Z-Wave Debug RCVD nonceFetch: node 015
Z-Wave Debug SENT nonceReport: 01 11 00 13 0F 0A 98 80 18 E2 CB B2 DB F6 C2 A2 25 14 1F
Z-Wave Debug RCVD encryptedPacket: 00 86 12 03 03 43 01 02 01 01 01 02 (decrypted)
Z-Wave Debug RCVD requestVersInfoGen: 01 11 00 04 00 0F 0B 86 12 03 03 43 01 02 01 01 01 02 FF
Z-Wave Debug . . requestVersInfoGen: node 015, protoVers 3.67, appVers 1.02
Z-Wave Syncing - retrieved protocol version 3.67, app version 1.02
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Entry Control : Secure Barrier Add-On (04 : 40 : 07, base 66)
Z-Wave Syncing - retrieved command classes: 20v1 22v1 86v1 66v1 71v1 72v1 98v1 5Av1 85v1
Z-Wave Syncing - retrieved encrypt commands: 22 85 66 71 86
Z-Wave Syncing - retrieved capabilities: routing, beaming, security
Z-Wave Debug SENT requestAssociationGroupCount: 85 05 (encrypted)
Z-Wave Debug RCVD nonceReport: node 015, nonce AB CC 4A 67 6F 7B 79 E0 (saving)
Z-Wave Debug . . requestAssociationGroupCount: requeuing 1 unsolicited packets
Z-Wave Debug reusing outgoing nonce 18 E2 CB B2 DB F6 C2 A2
Z-Wave Debug RCVD encryptedPacket: 00 86 12 03 03 43 01 02 01 01 01 02 (decrypted)
Z-Wave Debug RCVD requestVersInfoGen: 01 11 00 04 00 0F 0B 86 12 03 03 43 01 02 01 01 01 02 FF
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug SENT nonceRequest: 01 09 00 13 0F 02 98 40 25 16 03
Z-Wave Debug RCVD nonceReport: node 015, nonce DE A5 A5 A5 EA 6E 66 BB
Z-Wave Debug SENT requestAssociationGroupCount: 85 05 (encrypted)
Z-Wave Debug RCVD nonceReport: node 015, nonce EB B7 3B 77 25 89 AA DB (saving)
Z-Wave Debug RCVD nonceReport: node 015, nonce EB B7 3B 77 25 89 AA DB (saving)
Z-Wave Debug RCVD nonceFetch: node 015
Z-Wave Debug SENT nonceReport: 01 11 00 13 0F 0A 98 80 C2 F0 E8 8F 55 26 F2 22 25 18 2B
Z-Wave Debug RCVD encryptedPacket: 00 85 06 01 (decrypted)
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 0F 03 85 06 01 FF
Z-Wave Debug . . requestAssociationGroupCount: node 015, group count: 1
Z-Wave Debug SENT requestAssociations: 85 02 01 (encrypted)
Z-Wave Debug RCVD nonceReport: node 015, nonce 8A 6C 8A 26 34 84 84 D9 (saving)
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug SENT nonceRequest: 01 09 00 13 0F 02 98 40 25 1A 0F
Z-Wave Debug RCVD nonceReport: node 015, nonce D5 A7 C2 0D DC B5 37 F5
Z-Wave Debug SENT requestAssociations: 85 02 01 (encrypted)
Z-Wave Debug RCVD nonceReport: node 015, nonce 0D 52 E4 C2 B1 0D B8 0E (saving)
Z-Wave Debug RCVD nonceFetch: node 015
Z-Wave Debug SENT nonceReport: 01 11 00 13 0F 0A 98 80 1C 44 A1 F1 15 E6 BE CF 25 1C 53
Z-Wave Debug RCVD encryptedPacket: 00 85 03 01 01 00 (decrypted)
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 0F 05 85 03 01 01 00 FF
Z-Wave Debug . . requestAssociations: node 015, group: 1, num associations: 0, max associations: 1, replies left: 0
Z-Wave Debug . . requestAssociations: node 015, group: 1, associations: []
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Debug SENT addInterfaceAssociation: 85 01 01 01 (encrypted)
Z-Wave Debug RCVD nonceReport: node 015, nonce A4 7D 2D DA D2 4A B0 4E (saving)
Z-Wave Syncing - added group 1 association to interface
Z-Wave Debug . . addInterfaceAssociation: node 015, group: 1, associations: [1]
Z-Wave Syncing - complete
Z-Wave Debug started polling of "015 - Main Garage Door" approx every 300 seconds
Z-Wave Debug SENT requestBarrierStatus: 66 02 (encrypted)
Z-Wave Debug RCVD nonceReport: node 015, nonce 62 7A AF 24 3B C1 9A 2D (saving)
Z-Wave sent "Main Garage Door" status request
Z-Wave Debug RCVD nonceFetch: node 015
Z-Wave Debug SENT nonceReport: 01 11 00 13 0F 0A 98 80 1C 44 A1 F1 15 E6 BE CF 25 1F 50
Z-Wave Debug RCVD encryptedPacket: 00 66 03 FF (decrypted)
Z-Wave Debug RCVD requestBarrierStatus: 01 09 00 04 00 0F 03 66 03 FF FF
Z-Wave Debug . . requestBarrierStatus: node 015, endpoint None, value 255
Z-Wave received "Main Garage Door" status update is open
Z-Wave Debug terminatingSyncUI
Z-Wave Debug SENT nonceRequest: 01 09 00 13 0F 02 98 40 25 20 35
Z-Wave Debug RCVD nonceReport: node 015, nonce 99 67 83 4A 7B 04 92 D4
Z-Wave Debug SENT setBarrierValue: 66 01 00 (encrypted)
Z-Wave Debug RCVD nonceReport: node 015, nonce 21 A0 35 D6 F0 D6 DE C5 (saving)
Z-Wave sent "Main Garage Door" close

Feb 26, 2017, 12:23:17 PM
Z-Wave Debug SENT nonceRequest: 01 09 00 13 0F 02 98 40 25 22 37
Z-Wave Debug RCVD nonceReport: node 015, nonce 18 3B 82 F1 C7 12 44 62
Z-Wave Debug SENT requestBarrierStatus: 66 02 (encrypted)
Z-Wave Debug RCVD nonceReport: node 015, nonce 2A C3 14 65 63 F4 AF 63 (saving)
Z-Wave sent "Main Garage Door" status request
Z-Wave Debug RCVD nonceFetch: node 015
Z-Wave Debug SENT nonceReport: 01 11 00 13 0F 0A 98 80 D6 64 29 73 AC 29 EB 50 25 24 37
Z-Wave Debug RCVD encryptedPacket: 00 66 03 00 (decrypted)
Z-Wave Debug RCVD requestBarrierStatus: 01 09 00 04 00 0F 03 66 03 00 FF
Z-Wave Debug . . requestBarrierStatus: node 015, endpoint None, value 0
Z-Wave received "Main Garage Door" status update is closed

I bought two new controllers from Amazon. The first one I tried times out on sync. These things are goofy and I am about done all together. :0

Is there any update on this unit? I have still got to sync mine every day or two or it stops working. This is the second unit I bought with the same result. I had used this for two years with it bridged from Vera with almost no issues why so unstable now?

Thought I would give the Bata library a try since it couldn't hurt and now the unit won't even Sync

Z-Wave Syncing - started for "Garage Door 2"
Z-Wave Syncing - retrieved module neighbors list: 3, 4, 5, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18, 21, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 39, 41, 43, 44, 45, 46, 47, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 69, 86, 87
Z-Wave Syncing - assigning return route to "096 - Garage Door 2"
Z-Wave Syncing - assigned return route

Mar 15, 2017, 12:27:02 AM
Z-Wave Syncing - retrieved manufacture and model names: LinearLinc - 014F, Garage Door Controller (GD00Z-4) - 47443030

Mar 15, 2017, 12:27:23 AM
Z-Wave Error Syncing - failed
Z-Wave Error Timeout waiting for "096 - Garage Door 2". Module might be asleep, or is unreachable.

How can I roll back my Z-Wave Library since the bata doesn't even find my device now?

[matt (support)]

You can just download and re-run the full Indigo installer. But I don't think it is going to help the problem you are seeing. The beta changes didn't have anything to do with the sync failures you are seeing. I don't know exactly what is occurring with your modules, unfortunately.

I'm not sure why yours stops working or why a resync would get it working again (sometimes). Previously you said even with Vera sometimes it would drop off. I don't know if the problem is a Z-Wave networking issue (range/interference/etc.) or just a buggy firmware in the versions you have. The fact that they don't even report a firmware version is strange. Have you tried contacting the manufacturer to see if this is a know problem?

When the problem occurred with Vera it was prior to Vera officially supporting the device and it had to be installed as a generic. Once the device had officially been defined the problems stopped. The device sits in the garage which is about 20 feet from the Mac mini running Indigo and is only decided by one door with about 10 or 15 devices in between. Other devices in the garage work just fine with the range. I tried to roll back the library by doing a full install and now Indigo says it is always sleeping although it does start the include process from scratch but once I get to the Sync it fails.

I am really at a loss as to why it is giving so many problems. My next step was going to be doing an Upgrade to newest OS since I'm running 10.11.16. I really don't want to go back to bridging it since that was the biggest selling point on I7 was having locks without Vera. I will say I don't have the latest Z-Stick could that be it?

As an additional test a got the Vera back out set it all up again and put the Garage Door in pair. Vera picked it right up and it is currently working fine. I also installed Vera Bridge to make sure it would work that way and it does. The vera is sitting next to my Mac mini so the distance and obstructions is the same with one difference. Vera only has the garage door so no network. I don't want to sound harsh but I am starting to think the unit is fine as well as the zwave network and the problem lies in how Indigo is communicating with this device.

[matt (support)]

The newer model Z-Stick (Gen5) might work better with it. I know there is one other module (don't recall which one) that someone reported didn't work with the older Z-Stick but did well with the gen5 version. That isn't supposed to be the case (even newer Z-Wave devices should work with the older Z-Stick), but that doesn't mean that some modules might have bugs/issues with the older version. I don't know what the odds are that the newer Z-Stick will work better, unfortunately, but there is at least a non-zero possibility of it. I'd hate to recommend a new Z-Stick just to try to see if it works better, but if you were considering getting one anyway (for the improved range and speed) then now could be a good time to try it.

The problem might be related to how Indigo communicates with the module, but I'm not sure even where to start with that. The fact that the module totally goes out-to-lunch and stops responding to commands indicates that at the very least it has some firmware bugs. There might be a way for Indigo to communicate differently in some manner (not send commands as fast, not use a particular command, etc.) that avoids the lock-up problem, but tracking down those types of issues is difficult. It would be much easier if the module consistently didn't like a particular command and reported some type of error as a result of that. But in this case it sounds like it sometimes works for a short period of time after a full reset but then just stops working, and there is no specific step/command that causes the problem.

I've had this device functioning in my home for a few months now. Don't really use it that often, but its nice to have it when you do need it.

I've noticed that my log shows periodic reports from the device confirming that the door is closed. About every 10-15 minutes I see

Code: Select all

  Z-Wave                          received "Garage Door" status update is closed

This happens without any activity from the opener. Its not really an issue for me, just wondering if there is a way to turn this off. I don't see anything in the device configuration dialog that pertains to it.

[matt (support)]

There isn't currently an option for that, but we'll add it to the request list.