Linear NGDZ00-4 Garage Door

So this would imply that the 1 binary_sensor and 5 sensors are useless and should be hidden?

Iā€™d say itā€™s safe to ignore/hide them.

Check your core.entity_registry for multiple instances of the garage door. I have one cover, 5 sensors, and one zwave entity. I use the _burglar sensor to send tamper alerts for the up/down sensor.

So am I to understand that after all this waiting, I now need to remove and re-add the garage door device? I secure included my garage door device before I switch to HA (when I was on OH no issues) - I just hate having to remove and re-add devices. If this will do the trick, Iā€™ll have to suck it up, but Iā€™m wondering if there isnā€™t an easier way to just wipe out what is ā€œdiscoveredā€ at the moment in HA, and have it force a re-discover in HA?

I didnā€™t have to re-add mine.

1 Like

Ok not sure what did it, but miraculously after I now ask for help, it solves itself. :smiley:

I did come in and try to refresh the node, and heal the node as some people mentioned in here. Perhaps those actions kicked off what was needed to recognize the new items. For some reason before it wasnā€™t detecting the new cover device and placing it as expected on the UI. Now that I come to ask what I might need to do, and it is now there. Thanks to everyone here for the continued support and help!!

After the last update I was able to pair my opener securely and it shows up as a cover now in has.io. Unfortunately the state is wrong (always shows the door as open) and nothing happens after pressing the close button (even if the door is open).

It shows as ready in the zwave panel. Where should I look to troubleshoot? It wouldnā€™t surprise me if I need to replace the battery in the tilt sensor, but I thought it would show up dead if that were the case.

Start with the tilt sensor battery

No dice. Replaced the battery, restarted hassio and ran a heal network. The cover sensor still shows open regardless of the actual state and the close button doesnā€™t seem to do anything.

If you run tail -f OZW_Log.txt (or otherwise monitor/capture the openzwave log output) when you try to open or close it via HA, does anything helpful appear there?

Here is the zwave log after hitting the close button (with garage door currently open):

2018-11-18 11:26:06.856 Info, Node038, Value::Set - COMMAND_CLASS_BARRIER_OPERATOR - Barrier State Label - 1 - 1 - Closed
2018-11-18 11:26:06.857 Info, Node038, BarrierOperator::Set - Requesting barrier to be Closed
2018-11-18 11:26:06.857 Detail, Node038, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_BARRIER_OPERATOR
2018-11-18 11:26:06.857 Detail, Node038, Queuing (Send) BarrierOperatorCmd_Set (Node=38): 0x01, 0x0a, 0x00, 0x13, 0x26, 0x03, 0x66, 0x01, 0x00, 0x25, 0x1e, 0x9f
2018-11-18 11:26:06.857 Detail,
2018-11-18 11:26:06.857 Info, Node038, Processing (Send) Nonce Request message (Callback ID=0x1e, Expected Reply=0x13)
2018-11-18 11:26:06.858 Info, Node038, Sending (Send) message (Callback ID=0x1e, Expected Reply=0x13) - Nonce_Get(BarrierOperatorCmd_Set) - 0x01, 0x09, 0x00, 0x13, 0x26, 0x02, 0x98, 0x40, 0x05, 0x02:
2018-11-18 11:26:06.866 Detail, Node038, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-11-18 11:26:06.866 Detail, Node038, ZW_SEND_DATA delivered to Z-Wave stack
2018-11-18 11:26:07.003 Detail, Node038, Received: 0x01, 0x07, 0x00, 0x13, 0x02, 0x00, 0x00, 0x0e, 0xe7
2018-11-18 11:26:07.004 Detail, Node038, ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2018-11-18 11:26:07.004 Info, Node038, Request RTT 146 Average Request RTT 181
2018-11-18 11:26:07.094 Detail, Node038, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x26, 0x0a, 0x98, 0x80, 0x13, 0xf6, 0x55, 0x1d, 0x7d, 0x4e, 0x1a, 0xe3, 0xb8
2018-11-18 11:26:07.094 Info, Node038, Received SecurityCmd_NonceReport from node 38
2018-11-18 11:26:07.095 Info, Node038, Sending (Send) message (Callback ID=0x1f, Expected Reply=0x13) - BarrierOperatorCmd_Set (Node=38): 0x01, 0x0a, 0x00, 0x13, 0x26, 0x03, 0x66, 0x01, 0x00, 0x25, 0x1f, 0x9e
2018-11-18 11:26:07.107 Detail, Node038, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-11-18 11:26:07.107 Detail, Node038, ZW_SEND_DATA delivered to Z-Wave stack
2018-11-18 11:26:07.256 Detail, Node038, Received: 0x01, 0x07, 0x00, 0x13, 0x1f, 0x00, 0x00, 0x10, 0xe4
2018-11-18 11:26:07.256 Detail, Node038, ZW_SEND_DATA Request with callback ID 0x1f received (expected 0x1f)
2018-11-18 11:26:07.257 Info, Node038, Request RTT 399 Average Request RTT 290
2018-11-18 11:26:07.257 Detail, Expected callbackId was received
2018-11-18 11:26:07.257 Detail, Expected reply was received
2018-11-18 11:26:07.257 Detail, Message transaction complete
2018-11-18 11:26:07.257 Detail,
2018-11-18 11:26:07.257 Detail, Node038, Removing current message
2018-11-18 11:26:07.305 Detail, Node038, Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x26, 0x02, 0x98, 0x40, 0x0f
2018-11-18 11:26:07.305 Info, Node038, Received SecurityCmd_NonceGet from node 38
2018-11-18 11:26:07.305 Info, NONCES: 0x69, 0xb4, 0x7e, 0xca, 0xa8, 0xc2, 0x27, 0x3a
2018-11-18 11:26:07.306 Info, NONCES: 0x5b, 0x94, 0x69, 0x46, 0x4b, 0x39, 0x9e, 0x0b
2018-11-18 11:26:07.306 Info, NONCES: 0x7f, 0xb3, 0x95, 0x5c, 0x57, 0xb6, 0x4e, 0x09
2018-11-18 11:26:07.306 Info, NONCES: 0xcb, 0x1c, 0x8f, 0x66, 0x65, 0xf7, 0x4f, 0x5f
2018-11-18 11:26:07.306 Info, NONCES: 0xf1, 0xe1, 0xb8, 0x31, 0xfd, 0x7d, 0x4f, 0x5e
2018-11-18 11:26:07.306 Info, NONCES: 0x87, 0x64, 0xa7, 0x21, 0x78, 0x78, 0x57, 0x4d
2018-11-18 11:26:07.306 Info, NONCES: 0x44, 0x32, 0xd5, 0x42, 0xd4, 0x38, 0xb4, 0x6d
2018-11-18 11:26:07.306 Info, NONCES: 0x2d, 0x89, 0x03, 0x81, 0x61, 0x86, 0xf0, 0xc2
2018-11-18 11:26:07.306 Info, Node038, Sending (Send) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x26, 0x0a, 0x98, 0x80, 0x2d, 0x89, 0x03, 0x81, 0x61, 0x86, 0xf0, 0xc2, 0x05, 0x01, 0x3e:
2018-11-18 11:26:07.314 Detail, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-11-18 11:26:07.315 Detail, ZW_SEND_DATA delivered to Z-Wave stack
2018-11-18 11:26:07.528 Detail, Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x16, 0xfc
2018-11-18 11:26:07.531 Detail, ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2018-11-18 11:26:07.592 Detail, Node038, Received: 0x01, 0x1d, 0x00, 0x04, 0x00, 0x26, 0x17, 0x98, 0x81, 0xec, 0x79, 0x2e, 0x1b, 0x1b, 0xf1, 0x4f, 0xde, 0x7d, 0xba, 0xf5, 0x8b, 0x2d, 0x97, 0xd6, 0x83, 0x11, 0xac, 0xd8, 0x6b, 0x3e, 0x73
2018-11-18 11:26:07.593 Info, Raw: 0x98, 0x81, 0xec, 0x79, 0x2e, 0x1b, 0x1b, 0xf1, 0x4f, 0xde, 0x7d, 0xba, 0xf5, 0x8b, 0x2d, 0x97, 0xd6, 0x83, 0x11, 0xac, 0xd8, 0x6b, 0x3e, 0x73
2018-11-18 11:26:07.593 Detail, Node038, Decrypted Packet: 0x00, 0x66, 0x03, 0xfd
2018-11-18 11:26:07.593 Detail,
2018-11-18 11:26:07.593 Detail, Node038, Refreshed Value: old value=2, new value=2, type=list
2018-11-18 11:26:07.593 Detail, Node038, Changes to this value are not verified
2018-11-18 11:26:07.593 Detail, Node038, Notification: ValueChanged

Strange. The log indicates everything is communicating as expected, including the secure channel. If the controller doesnā€™t beep when this happens, then maybe thereā€™s an internal hardware failure. Iā€™ve heard people mention that this has happened to them. The problem with the tilt sensor is worrisome, unless thereā€™s some special ā€œsync-upā€ routine you have to follow after replacing the battery (not sure yet as Iā€™ve never had to do mine).

Anyone else on the thread run into the problem where HA/OZW looks perfect but the controller does nothing?

I do not know where I saw this but it wasnā€™t more than a couple of weeks ago. When I saw this I thought ā€œinteresting, I should take noteā€ and promptly forgot where I saw it.
It was about reversing the state of the tilt sensor. It may have been in the Zwave node settings but may have been somewhere entirely. It was in relation to the Linear / Go Control opener though

yes, I came here to start a new post - but see others with the same issue now as well. Cover entity populates, OZW log looks fine, etc etcā€¦nothing opens/closes. Iā€™m thinking it may have something to do with the way I probably screwed up the cover config. for example - which entity should be associated with the cover class? And why platform: zwave with no entity? Do I need to cover class definition set to garage? I have a garage door with up/down showing on my frontend. Hassio on pi

Hereā€™s my config:

In config

    cover:
      - platform: zwave    

In Groups

garage_door:
  name: Garage Door 
  entities: 
     - cover.linear_gd00z4_garage_door_opener_remote_controller_barrier_state_label

In Customize (I started changing around config, since door wonā€™t open have no idea whatā€™s correct)

cover.linear_gd00z4_garage_door_opener_remote_controller_barrier_state_label:
    device_class: garage
    friendly_name: Garage Door  

hereā€™s my log with the same scenario (door open, command is to close)

2018-11-20 19:08:22.116 Detail,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2018-11-20 19:08:22.133 Detail, Node013,   Received: 0x01, 0x1d, 0x00, 0x04, 0x00, 0x0d, 0x17, 0x98, 0x81, 0x93, 0x75, 0x92, 0xdf, 0x0b, 0x26, 0x21, 0xac, 0xed, 0x81, 0x21, 0x46, 0x73, 0x90, 0x4e, 0xfe, 0x1b, 0xb5, 0x3d, 0xf4, 0x69, 0xb8
2018-11-20 19:08:22.134 Info, Raw: 0x98, 0x81, 0x93, 0x75, 0x92, 0xdf, 0x0b, 0x26, 0x21, 0xac, 0xed, 0x81, 0x21, 0x46, 0x73, 0x90, 0x4e, 0xfe, 0x1b, 0xb5, 0x3d, 0xf4, 0x69, 0xb8
2018-11-20 19:08:22.134 Detail, Node013, Decrypted Packet: 0x00, 0x66, 0x03, 0xfd
2018-11-20 19:08:22.134 Detail,
2018-11-20 19:08:22.134 Detail, Node013, Refreshed Value: old value=2, new value=2, type=list
2018-11-20 19:08:22.134 Detail, Node013, Changes to this value are not verified
2018-11-20 19:08:22.134 Detail, Node013, Notification: ValueChanged
2018-11-20 19:28:22.530 Detail, Node013,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x0d, 0x02, 0x98, 0x40, 0x24
2018-11-20 19:28:22.530 Info, Node013, Received SecurityCmd_NonceGet from node 13
2018-11-20 19:28:22.530 Info, NONCES: 0x73, 0x1c, 0x4e, 0xfb, 0x15, 0x38, 0xad, 0xea
2018-11-20 19:28:22.531 Info, NONCES: 0x99, 0xca, 0x41, 0xd4, 0xad, 0x8f, 0x27, 0x99
2018-11-20 19:28:22.531 Info, NONCES: 0x34, 0xe1, 0xf6, 0x49, 0x40, 0xa9, 0xa2, 0x41
2018-11-20 19:28:22.531 Info, NONCES: 0xb3, 0x2a, 0x8d, 0xbd, 0x6d, 0x8c, 0xa7, 0x49
2018-11-20 19:28:22.531 Info, NONCES: 0xff, 0x99, 0xfc, 0x52, 0xc2, 0x51, 0x95, 0xb9
2018-11-20 19:28:22.531 Info, NONCES: 0xbe, 0x82, 0x4e, 0x14, 0x96, 0xf1, 0xa4, 0x53
2018-11-20 19:28:22.531 Info, NONCES: 0x5e, 0xbc, 0x58, 0x7b, 0x20, 0xb4, 0xe7, 0xed
2018-11-20 19:28:22.531 Info, NONCES: 0xf6, 0x31, 0xd2, 0x33, 0x70, 0x61, 0xd1, 0x52
2018-11-20 19:28:22.531 Info, Node013, Sending (Command) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x0d, 0x0a, 0x98, 0x80, 0x99, 0xca, 0x41, 0xd4, 0xad, 0x8f, 0x27, 0x99, 0x05, 0x01, 0xbc:
2018-11-20 19:28:22.540 Detail,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-11-20 19:28:22.540 Detail,   ZW_SEND_DATA delivered to Z-Wave stack
2018-11-20 19:28:22.557 Detail,   Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x02, 0xe8
2018-11-20 19:28:22.557 Detail,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2018-11-20 19:28:22.574 Detail, Node013,   Received: 0x01, 0x1d, 0x00, 0x04, 0x00, 0x0d, 0x17, 0x98, 0x81, 0xa6, 0x02, 0xca, 0x2f, 0x2c, 0x07, 0x16, 0xe1, 0x79, 0x74, 0x0c, 0x9d, 0x99, 0x23, 0x29, 0xc1, 0xaf, 0xcc, 0x19, 0xa8, 0x9b, 0xff
2018-11-20 19:28:22.574 Info, Raw: 0x98, 0x81, 0xa6, 0x02, 0xca, 0x2f, 0x2c, 0x07, 0x16, 0xe1, 0x79, 0x74, 0x0c, 0x9d, 0x99, 0x23, 0x29, 0xc1, 0xaf, 0xcc, 0x19, 0xa8, 0x9b, 0xff
2018-11-20 19:28:22.574 Detail, Node013, Decrypted Packet: 0x00, 0x66, 0x03, 0xfd
2018-11-20 19:28:22.574 Detail,
2018-11-20 19:28:22.574 Detail, Node013, Refreshed Value: old value=2, new value=2, type=list
2018-11-20 19:28:22.574 Detail, Node013, Changes to this value are not verified
2018-11-20 19:28:22.574 Detail, Node013, Notification: ValueChanged
2018-11-20 19:48:22.970 Detail, Node013,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x0d, 0x02, 0x98, 0x40, 0x24
2018-11-20 19:48:22.970 Info, Node013, Received SecurityCmd_NonceGet from node 13
2018-11-20 19:48:22.970 Info, NONCES: 0x73, 0x1c, 0x4e, 0xfb, 0x15, 0x38, 0xad, 0xea
2018-11-20 19:48:22.970 Info, NONCES: 0x99, 0xca, 0x41, 0xd4, 0xad, 0x8f, 0x27, 0x99
2018-11-20 19:48:22.970 Info, NONCES: 0x89, 0x77, 0x11, 0x0e, 0x07, 0x8f, 0xcd, 0x8f
2018-11-20 19:48:22.970 Info, NONCES: 0xb3, 0x2a, 0x8d, 0xbd, 0x6d, 0x8c, 0xa7, 0x49
2018-11-20 19:48:22.971 Info, NONCES: 0xff, 0x99, 0xfc, 0x52, 0xc2, 0x51, 0x95, 0xb9
2018-11-20 19:48:22.971 Info, NONCES: 0xbe, 0x82, 0x4e, 0x14, 0x96, 0xf1, 0xa4, 0x53
2018-11-20 19:48:22.971 Info, NONCES: 0x5e, 0xbc, 0x58, 0x7b, 0x20, 0xb4, 0xe7, 0xed
2018-11-20 19:48:22.971 Info, NONCES: 0xf6, 0x31, 0xd2, 0x33, 0x70, 0x61, 0xd1, 0x52
2018-11-20 19:48:22.971 Info, Node013, Sending (Command) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x0d, 0x0a, 0x98, 0x80, 0x89, 0x77, 0x11, 0x0e, 0x07, 0x8f, 0xcd, 0x8f, 0x05, 0x01, 0xcd:
2018-11-20 19:48:22.980 Detail,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-11-20 19:48:22.980 Detail,   ZW_SEND_DATA delivered to Z-Wave stack
2018-11-20 19:48:22.996 Detail,   Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x02, 0xe8
2018-11-20 19:48:22.997 Detail,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2018-11-20 19:48:23.013 Detail, Node013,   Received: 0x01, 0x1d, 0x00, 0x04, 0x00, 0x0d, 0x17, 0x98, 0x81, 0x01, 0x9e, 0x06, 0x86, 0xb4, 0x6b, 0x08, 0xe3, 0xbe, 0xca, 0x69, 0x32, 0x89, 0x27, 0xd9, 0xf2, 0x6a, 0x57, 0x35, 0xe1, 0x7f, 0xf2
2018-11-20 19:48:23.014 Info, Raw: 0x98, 0x81, 0x01, 0x9e, 0x06, 0x86, 0xb4, 0x6b, 0x08, 0xe3, 0xbe, 0xca, 0x69, 0x32, 0x89, 0x27, 0xd9, 0xf2, 0x6a, 0x57, 0x35, 0xe1, 0x7f, 0xf2
2018-11-20 19:48:23.014 Detail, Node013, Decrypted Packet: 0x00, 0x66, 0x03, 0xfd
2018-11-20 19:48:23.014 Detail,
2018-11-20 19:48:23.014 Detail, Node013, Refreshed Value: old value=2, new value=2, type=list
2018-11-20 19:48:23.014 Detail, Node013, Changes to this value are not verified
2018-11-20 19:48:23.014 Detail, Node013, Notification: ValueChanged
2018-11-20 19:50:01.230 Info, Node013, Value::Set - COMMAND_CLASS_BARRIER_OPERATOR - Barrier State Label - 1 - 1 - Closed
2018-11-20 19:50:01.230 Info, Node013, BarrierOperator::Set - Requesting barrier to be Closed
2018-11-20 19:50:01.230 Detail, Node013, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_BARRIER_OPERATOR
2018-11-20 19:50:01.231 Detail, Node013, Queuing (Send) BarrierOperatorCmd_Set (Node=13): 0x01, 0x0a, 0x00, 0x13, 0x0d, 0x03, 0x66, 0x01, 0x00, 0x25, 0x79, 0xd3
2018-11-20 19:50:01.231 Detail,
2018-11-20 19:50:01.231 Info, Node013, Processing (Send) Nonce Request message (Callback ID=0x79, Expected Reply=0x13)
2018-11-20 19:50:01.231 Info, Node013, Sending (Send) message (Callback ID=0x79, Expected Reply=0x13) - Nonce_Get(BarrierOperatorCmd_Set) - 0x01, 0x09, 0x00, 0x13, 0x0d, 0x02, 0x98, 0x40, 0x05, 0x02:
2018-11-20 19:50:01.239 Detail, Node013,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-11-20 19:50:01.240 Detail, Node013,   ZW_SEND_DATA delivered to Z-Wave stack
2018-11-20 19:50:01.255 Detail, Node013,   Received: 0x01, 0x07, 0x00, 0x13, 0x02, 0x00, 0x00, 0x02, 0xeb
2018-11-20 19:50:01.255 Detail, Node013,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2018-11-20 19:50:01.256 Info, Node013, Request RTT 24 Average Request RTT 39
2018-11-20 19:50:01.268 Detail, Node013,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x0d, 0x0a, 0x98, 0x80, 0x43, 0xfb, 0xec, 0x88, 0xd9, 0xe7, 0x3a, 0x31, 0x1d
2018-11-20 19:50:01.268 Info, Node013, Received SecurityCmd_NonceReport from node 13
2018-11-20 19:50:01.269 Info, Node013, Sending (Send) message (Callback ID=0x7a, Expected Reply=0x13) - BarrierOperatorCmd_Set (Node=13): 0x01, 0x0a, 0x00, 0x13, 0x0d, 0x03, 0x66, 0x01, 0x00, 0x25, 0x7a, 0xd0
2018-11-20 19:50:01.279 Detail, Node013,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-11-20 19:50:01.280 Detail, Node013,   ZW_SEND_DATA delivered to Z-Wave stack
2018-11-20 19:50:01.297 Detail, Node013,   Received: 0x01, 0x07, 0x00, 0x13, 0x7a, 0x00, 0x00, 0x03, 0x92
2018-11-20 19:50:01.297 Detail, Node013,   ZW_SEND_DATA Request with callback ID 0x7a received (expected 0x7a)
2018-11-20 19:50:01.298 Info, Node013, Request RTT 65 Average Request RTT 52
2018-11-20 19:50:01.298 Detail,   Expected callbackId was received
2018-11-20 19:50:01.298 Detail,   Expected reply was received
2018-11-20 19:50:01.298 Detail,   Message transaction complete

I found a fix.
I added the cover: -platform: zwave entry into my configuration.yaml (maybe not needed, but added anyway)
And then, when you add the linear garage door opener using secure add node use the below process

  1. click ā€œadd secure nodeā€ in HA
  2. click the button on the garage door opener and wait for the 3 beeps
  3. click the button again on the garage door opener

This worked for me, hope it helps !

Open your door once via your button, then attempt it via HomeAssistant.

Iā€™ve definitely pressed the manual button a few times just opening and closing the door (since HA wonā€™t work), but also to try and register the up-down sensor. Door still always shows open.

Iā€™ll try that tonightā€¦ Any idea what it does? I think pressing that button again sends the linear device into a pairing state again?

I tried that after i first paired mine and it wasnā€™t working. Itā€™s described in the zwave cover docs: https://www.home-assistant.io/components/cover.zwave/

zwave:
  device_config:
    cover.my_cover:
      invert_openclose_buttons: true

I added that and restarted but didnā€™t notice any difference.

Iā€™ll try unpairing and repairing again.

do you know if any of the zwcfg xml info is needed if Iā€™m running hassio on a pi?