OpenHab2 and Linear NGD00Z-4 Garage Door Controller

Did you power it on and then do a manual open and close? I think I remember initially having this issue, but this was what got the tilt sensor to sync up.

I dont think i did. Should i do a reset? Think its hit the link button 5x…

I doubt you would need to exclude/include to get the tilt sensor working. I would try power cycling and then manually opening/closing. If that doesn’t work, I’d put a voltmeter (or tongue :stuck_out_tongue_winking_eye:) on that battery to make sure it’s still good.

Ok, thanks, ill try

@5iver you seem to be the guy to ask!

I’ve attempted to get this working but I seem to be running into an issue I don’t know how to fix. This is the readout I’m getting from the log:

16:56:16.599 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'Garage_Door_Position' received command 0
16:56:18.972 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:56:28.971 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:56:38.970 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:56:48.410 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:56:48.971 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:56:58.978 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:57:08.986 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:57:18.990 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:57:28.990 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:57:38.992 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:57:48.484 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_967a3cd9_serial_ack changed from 244 to 245
16:57:48.486 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_967a3cd9_serial_sof changed from 485 to 486
16:57:48.524 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_967a3cd9_serial_sof changed from 486 to 487
16:57:48.610 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_967a3cd9_serial_sof changed from 487 to 488
16:57:48.731 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_967a3cd9_serial_sof changed from 488 to 489
16:57:48.995 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:57:50.614 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_967a3cd9_serial_sof changed from 489 to 490
16:57:58.997 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:58:08.999 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:58:19.004 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:58:29.004 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:58:39.010 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:58:49.024 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:58:59.014 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:59:09.024 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:59:19.031 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:59:29.037 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:59:39.038 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:59:49.043 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights
16:59:59.052 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /api/e2fa01c1-df2a-4423-a0a8-fc11ab67f7df/lights

Any help you can provide would be great!

Questions to get started:

  • Are you using the test zwave binding from here?
  • Has the opener been securely included? (look in Habmin> Configuration> Things> Opener> Attributes> Using Security?.. it should be a green checkmark)
  • Do you get events in the log when you manually trigger the garage door? (From the log above, it looks like you do not have debugging turned on for the binding. Enter log:set DEBUG org.openhab.binding.zwave in the Karaf console.)

Thanks for the quick response! I’ve started on trying the test binding. Unfortunately, the garage controller and one of my lamps have quit communicating with the controller since the change. I’m trying to fight that battle and then I’ll move forward. If I can get these issues fixed I’ll report back with my current status.

So after hours of laboring…I finally have the test zwave binding working and the opener securely included. I ended up having to uninstall the opener, bring it next to my linux box with the z-stick plugged in and do the inclusion through habmin in order to get security to work. Your three simple questions led me down a rabbit hole that taught me a ton today. Thanks for the start!

I’ve stopped here for the night and I’ll pick up again tomorrow and provide a further update with my findings. Thanks again!

After updating to the newest test binding, obtaining secure inclusion, turning on debugging, and chasing down only one error (which was being caused by the ghost of a forgotten node), the garage door now works flawlessly! Thanks again @5iver for the direction…it was all I needed!


@chris, I haven’t gotten a reply from @ashgupta. Should I just clean these out of the db?

1 Like

Yep - I think it’s best. Thanks.

I’ll update your access in the database to demi-god so you can delete stuff (be careful! :wink: ).

That made me nervous… but the alarm CC is now removed from the db entry for the NGD00Z. TY!

@5iver - you mentioned in the other thread (Security ZWave Binding thread) about using Lambdas now for this device. Care to elaborate or share some of what you have going on? I’m working on re-tooling some rules and simplifying some things. I have a feeling this may be useful to do with this one since I have a bunch of rules to handle things like syncing the state of the switch vs a virtual switch and the barrier position numbers.

Sure thing! The door is controlled through the Switch item, which gets updated if the garage door is manually opened or closed.


Group    gGarageDoorOpener    "Garge Door Openers"    <garagedoor>
Switch    GarageAttached_Door    "Garage Door (Attached) [MAP(]"    <garagedoor>    (gGarageDoorOpener)
Number    GarageAttached_Door_Position    "Garage Door (Attached) [MAP(]"    <garagedoor>    (gGarageDoorOpener)    {channel="zwave:device:55555:node5:barrier_state"}
Switch    GarageDetached_Door    "Garage Door (Detached) [MAP(]"    <garagedoor>    (gGarageDoorOpener)|
Number    GarageDetached_Door_Position    "Garage Door (Detached) [MAP(]"    <garagedoor>    (gGarageDoorOpener)    {channel="zwave:device:55555:node55:barrier_state"}


// put this import at the top of your rule file
import org.eclipse.smarthome.model.script.ScriptServiceUtil

rule "Update garage door state"
    Member of gGarageDoorOpener received update
    val actionItem = ScriptServiceUtil.getItemRegistry.getItem(if ("_Position"))"_Position","") else ( + "_Position"))
    logDebug("Rules", "Garage door event: [{}] was updated to {} ({}): action item [{}], current state {} ({})",, triggeringItem.state, transform("MAP", "", triggeringItem.state.toString),, actionItem.state, transform("MAP", "", actionItem.state.toString))
    switch (triggeringItem.state.toString) {
        case "255",//open
        case "254",//opening
        case "253",//stopped
        case "252" : {//closing
            if (actionItem.state != OFF) {
                logDebug("Rules", "Garage door event: updated switch [{}] to OFF (OPEN) after barrier_state update",
        case "0" : {//closed
            if (actionItem.state != ON) {
                logDebug("Rules", "Garage door event: updated switch [{}] to ON (CLOSED) after barrier_state update",
        case "ON" : {
            if (actionItem.state != 0) {
                logDebug("Rules", "Garage door event: updated barrier_state [{}] to 0 (CLOSED) after switch state update",
        case "OFF" : {
            if (actionItem.state != 255) {
                logDebug("Rules", "Garage door event: updated barrier_state [{}] to 255 (OPEN) after switch state update",



EDIT: added handling of OPENING, STOPPED, and CLOSING states.
EDIT: removed lambda and change to ‘Member of’ trigger

Here is a similar example that I use for my door locks:


Nice!! Ok I think I recall seeing you share the one for the YRD lock that I have too. :wink: This looks quite similar.

I made a few untested updates :roll_eyes:

@chris, @5iver

I have recently done a clean install on a pi3…

My NGD-00Z is now securely included, but the only channel that is showing is the barrier-state. No other channels are available. Has this been seen anywhere else?

That is the only channel currently available. The other channels shouldn’t have been there… mostly ALARM CC, which is not supported by the opener.

Didnt realize it changed, my bad…i see you have added a lamda, do you use oh2? does the lamda go in a rules file?