Gocontrol door sensor always open

Yes it is in driver stock and must work fine
@nayelyz Please, how or where is this failure of the stock Z-wave Sensor driver reported?

I can report it. @dav55, or someone else in the same situation, could you share the driver logs to see the events received by it, please?
I think this is because the device reports differently its status and those messages aren’t being handled properly.

For this, you need to:

  1. Set up the ST CLI and run the command below:
smartthings edge:drivers:logcat

Note: You’ll find the Hub’s IP address in the IDE > “My Hubs” section
2. Replicate the issue, and let us know the sequence of actions, for example, open > close > open. To see what was interpreted at the moment.

send the file to build@smartthings.com

having issues running it.
first time it said
logging in … done
error; read ECONNRESET

now I get connecting…failed

I have the exact same door sensors and had the exact same problem. I had to use the masquerade driver by @philh30 and they work perfectly now.

thank you @Raegoul that worked!

This initially worked for me, but now the sensors randomly open. Does anyone else experience that behavior?

Since upgrading the drivers I have not had any issues.

I added philh30 masquerade v1.01 to my hub and the gocontrol door sensors work now.

exact same gocontrol contact sensor and exact same issue. the masquerade by phil30 works. havent experienced random open, but will update if it does. so far it is working fine for me.

UPDATE: random open status like previous poster said. I believe this only happens if you connect the sensors with your existing wire contacts. All my contact sensors that are using the wire connection are having issues, the others that are not using the wires are fine.

1 Like

Hi, everyone.

Sorry for the delay, I don’t know why this happened, it could be the IP address being incorrect.

Is there someone that still has the issue and could share the driver logs, please?

I just started this topic since apparently I didn’t search well enough before posting. As noted above, the Masquerade driver does work but only for one set of contacts. I’m looking for a solution that will also integrate the set of external contacts as originally intended by the manufacturer.
Thank you

A post was merged into an existing topic: Nortek Linear GoControl Z-Wave Multisensor ST Edge Driver help needed (WADWAZ-1)

I have this same problem with my GoControl sensors. I use 6 of them for my hard wired windows, so having them all report “open” starting a month ago is extremely annoying, and very disappointing. Was there an Edge driver switch 1 month ago? Sorry for the ignorance…I haven’t been on the community in a long time because everything was working ok for the past year.

My thanks to @valkokir for correcting me on the model number. I have updated this post.

If someone who has this problem could temporarily assign the sensor to Mariano’s Z wave configuration driver and let us know both the parameter values and the association groups, that might help, Note that you will have to wake the device up to get the information, so you will also need the user manual.

@nayelyz

Tried it with partial success. It reports the association groups immediately on waking up, but when I tried to use the parameter scan the “waiting for device response” message cleared but no data appeared. I’ll try to work with Mariano in the other thread tomorrow when I can (maybe) get CLI logging up while I do it.

1 Like

Initial device add with all switches closed:

2023-03-09T13:25:07.276956935+00:00 WARN Z-Wave Device Config Mc  Unexpected filesystem lookup for capability legendabsolute60149.wakeUpValue
2023-03-09T13:25:07.316680519+00:00 TRACE Z-Wave Device Config Mc  Setup driver zwave_thing with lifecycle handlers:
DeviceLifecycleDispatcher: zwave_thing
  default_handlers:
    doConfigure:
    added:
    driverSwitched:
    infoChanged:
    init:
  child_dispatchers:

2023-03-09T13:25:07.321047269+00:00 TRACE Z-Wave Device Config Mc  Setup driver zwave_thing with Capability handlers:
CapabilityCommandDispatcher: zwave_thing
  default_handlers:
    legendabsolute60149.parameterend:
      setParameterEnd
    refresh:
      refresh
    legendabsolute60149.groupNumber:
      setGroupNumber
    legendabsolute60149.groupNumberEnd:
      setGroupNumberEnd
    legendabsolute60149.groupNumberStart:
      setGroupNumberStart
    legendabsolute60149.deviceParameter:
      setDeviceParameter
    legendabsolute60149.deviceAssociationType:
      setDeviceAssociationType
    legendabsolute60149.groupCommandOption:
      setGroupCommandOption
    legendabsolute60149.parameterSize:
      setParameterSize
    legendabsolute60149.parameterStart:
      setParameterStart
    legendabsolute60149.commandConfig1:
      setCommandConfig
    legendabsolute60149.nodeEndPoint:
      setNodeEndPoint
    legendabsolute60149.nodeToWriteHex:
      setNodeToWrite
    legendabsolute60149.parameterValue:
      setParameterValue
    legendabsolute60149.actionbutton2:
      push
  child_dispatchers:

2023-03-09T13:25:07.321778310+00:00 TRACE Z-Wave Device Config Mc  Setup driver zwave_thing with Z-Wave handlers:
ZwaveDispatcher: zwave_thing
  default_handlers:
    CONFIGURATION:
      REPORT
    ASSOCIATION:
      REPORT
    VERSION:
      REPORT
    MULTI_CHANNEL_ASSOCIATION:
      REPORT
  child_dispatchers:

2023-03-09T13:25:07.331929685+00:00 TRACE Z-Wave Device Config Mc  Z-Wave Device: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696
Manufacturer: 0x014F Product Type: 0x2001 Product ID: 0x0102
        [0]: NOTIFICATION, ASSOCIATION, BATTERY, MANUFACTURER_SPECIFIC, SENSOR_BINARY, VERSION, WAKE_UP
2023-03-09T13:25:07.332652602+00:00 TRACE Z-Wave Device Config Mc  Received event with handler _resync
2023-03-09T13:25:07.333304435+00:00 TRACE Z-Wave Device Config Mc  Received event with handler environment_info
2023-03-09T13:25:07.344525769+00:00 TRACE Z-Wave Device Config Mc  Found DeviceLifecycleDispatcher handler in zwave_thing
2023-03-09T13:25:07.346142269+00:00 TRACE Z-Wave Device Config Mc  Z-Wave command(286ca378) queued for radio transmission: CC:Version, CID:0x11
2023-03-09T13:25:07.346879269+00:00 PRINT Z-Wave Device Config Mc  <<<<<<<< device:get_field(firmVersion)
2023-03-09T13:25:07.347524352+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> sending Z-Wave command: {args={}, cmd_class="VERSION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2023-03-09T13:25:07.358553019+00:00 TRACE Z-Wave Device Config Mc  Z-Wave command(45164e7a) queued for radio transmission: CC:Version, CID:0x11
2023-03-09T13:25:07.359063852+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled
2023-03-09T13:25:07.359842810+00:00 TRACE Z-Wave Device Config Mc  Received event with handler environment_info
2023-03-09T13:25:07.360666227+00:00 DEBUG Z-Wave Device Config Mc  Z-Wave hub node ID environment changed.
2023-03-09T13:25:07.361284769+00:00 TRACE Z-Wave Device Config Mc  Received event with handler device_lifecycle
2023-03-09T13:25:07.361893602+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> received lifecycle event: added
2023-03-09T13:25:07.362896394+00:00 TRACE Z-Wave Device Config Mc  Found DeviceLifecycleDispatcher handler in zwave_thing
2023-03-09T13:25:07.363528310+00:00 PRINT Z-Wave Device Config Mc  <<<<<<<< device:get_field(firmVersion)
2023-03-09T13:25:07.374054102+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> sending Z-Wave command: {args={}, cmd_class="VERSION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2023-03-09T13:25:07.374865727+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled
2023-03-09T13:25:07.375567810+00:00 TRACE Z-Wave Device Config Mc  Received event with handler device_lifecycle
2023-03-09T13:25:07.376184685+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> received lifecycle event: driverSwitched
2023-03-09T13:25:07.377164102+00:00 TRACE Z-Wave Device Config Mc  Found DeviceLifecycleDispatcher handler in zwave_thing
2023-03-09T13:25:07.378078560+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled
2023-03-09T13:25:07.384042060+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled
2023-03-09T13:25:07.608166394+00:00 TRACE Z-Wave Device Config Mc  Received event with handler device_lifecycle
2023-03-09T13:25:07.614499936+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> received lifecycle event: infoChanged
2023-03-09T13:25:07.616712977+00:00 TRACE Z-Wave Device Config Mc  Found DeviceLifecycleDispatcher handler in zwave_thing
2023-03-09T13:25:07.617377602+00:00 PRINT Z-Wave Device Config Mc  device.preferences[infoChanged]=             preferences:    version
2023-03-09T13:25:07.617996936+00:00 PRINT Z-Wave Device Config Mc  << Preference changed name:  version old value:     nil      new value:
2023-03-09T13:25:07.618661852+00:00 PRINT Z-Wave Device Config Mc  device.preferences[infoChanged]=     Info    preferences:    changeConfigProfile
2023-03-09T13:25:07.619277602+00:00 PRINT Z-Wave Device Config Mc  << Preference changed name:  changeConfigProfile    old value:       nil     new value:      Info
2023-03-09T13:25:07.626439102+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled
2023-03-09T13:25:07.629420311+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled
2023-03-09T13:25:08.641652686+00:00 TRACE Z-Wave Device Config Mc  Z-Wave command(1240ecb6) queued for radio transmission: CC:Version, CID:0x11
2023-03-09T13:25:08.642345936+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> sending Z-Wave command: {args={}, cmd_class="VERSION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2023-03-09T13:25:08.647889311+00:00 TRACE Z-Wave Device Config Mc  Z-Wave command(4572680c) queued for radio transmission: CC:Version, CID:0x11
2023-03-09T13:25:08.648378103+00:00 PRINT Z-Wave Device Config Mc  <<<<<<<< device:get_field(firmVersion)
2023-03-09T13:25:08.649006644+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> sending Z-Wave command: {args={}, cmd_class="VERSION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2023-03-09T13:25:08.653549978+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled
2023-03-09T13:25:11.756965771+00:00 TRACE Z-Wave Device Config Mc  Z-Wave command(286ca378) transmit status: TRANSMIT_COMPLETE_NO_ACK
2023-03-09T13:25:16.176937940+00:00 TRACE Z-Wave Device Config Mc  Z-Wave command(45164e7a) transmit status: TRANSMIT_COMPLETE_NO_ACK
2023-03-09T13:25:20.546989317+00:00 TRACE Z-Wave Device Config Mc  Z-Wave command(1240ecb6) transmit status: TRANSMIT_COMPLETE_NO_ACK
2023-03-09T13:25:24.826947027+00:00 TRACE Z-Wave Device Config Mc  Z-Wave command(4572680c) transmit status: TRANSMIT_COMPLETE_NO_ACK

Magnetic Contact Open

2023-03-09T13:27:04.437966700+00:00 TRACE Z-Wave Device Config Mc  Received event with handler unnamed
2023-03-09T13:27:04.439856325+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> received Z-Wave command: {args={value=255}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="NONE", payload="\xFF", src_channel=0, version=1}
2023-03-09T13:27:04.446349158+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled
2023-03-09T13:27:04.446817033+00:00 TRACE Z-Wave Device Config Mc  Received event with handler unnamed
2023-03-09T13:27:04.447434241+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> received Z-Wave command: {args={alarm_level=255, alarm_type=7, event="INTRUSION", event_parameter="", notification_status="ON", notification_type="HOME_SECURITY", v1_alarm_level=255, v1_alarm_type=7, z_wave_alarm_event="INTRUSION", z_wave_alarm_status="ON", z_wave_alarm_type="BURGLAR", zensor_net_source_node_id=0}, cmd_class="NOTIFICATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x07\xFF\x00\xFF\x07\x02\x00\x00", src_channel=0, version=3}
2023-03-09T13:27:04.448600033+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled

Magnetic Contact Close

2023-03-09T13:28:49.475975883+00:00 TRACE Z-Wave Device Config Mc  Received event with handler unnamed
2023-03-09T13:28:49.476534050+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> received Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="NONE", payload="\x00", src_channel=0, version=1}
2023-03-09T13:28:49.486170592+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled
2023-03-09T13:28:49.488502967+00:00 TRACE Z-Wave Device Config Mc  Received event with handler unnamed
2023-03-09T13:28:49.490738967+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> received Z-Wave command: {args={alarm_level=0, alarm_type=7, event="INTRUSION", event_parameter="", notification_status="ON", notification_type="HOME_SECURITY", v1_alarm_level=0, v1_alarm_type=7, z_wave_alarm_event="INTRUSION", z_wave_alarm_status="ON", z_wave_alarm_type="BURGLAR", zensor_net_source_node_id=0}, cmd_class="NOTIFICATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x07\x00\x00\xFF\x07\x02\x00\x00", src_channel=0, version=3}
2023-03-09T13:28:49.494762925+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled

External Contact Open

2023-03-09T13:29:58.678590541+00:00 TRACE Z-Wave Device Config Mc  Received event with handler unnamed
2023-03-09T13:29:58.681095750+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> received Z-Wave command: {args={alarm_level=0, alarm_type=7, event="UNKNOWN_EVENT_STATE", event_parameter="", notification_status="ON", notification_type="HOME_SECURITY", v1_alarm_level=0, v1_alarm_type=7, z_wave_alarm_event="UNKNOWN_EVENT_STATE", z_wave_alarm_status="ON", z_wave_alarm_type="BURGLAR", zensor_net_source_node_id=0}, cmd_class="NOTIFICATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x07\x00\x00\xFF\x07\xFE\x00\x00", src_channel=0, version=3}
2023-03-09T13:29:58.684650791+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled

External Contact Close

2023-03-09T13:30:39.198300019+00:00 TRACE Z-Wave Device Config Mc  Received event with handler unnamed
2023-03-09T13:30:39.208899311+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> received Z-Wave command: {args={alarm_level=255, alarm_type=7, event="UNKNOWN_EVENT_STATE", event_parameter="", notification_status="ON", notification_type="HOME_SECURITY", v1_alarm_level=255, v1_alarm_type=7, z_wave_alarm_event="UNKNOWN_EVENT_STATE", z_wave_alarm_status="ON", z_wave_alarm_type="BURGLAR", zensor_net_source_node_id=0}, cmd_class="NOTIFICATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x07\xFF\x00\xFF\x07\xFE\x00\x00", src_channel=0, version=3}
2023-03-09T13:30:39.214381102+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled

Tamper Open

2023-03-09T13:32:28.178367105+00:00 TRACE Z-Wave Device Config Mc  Received event with handler unnamed
2023-03-09T13:32:28.180995314+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> received Z-Wave command: {args={alarm_level=255, alarm_type=7, event="TAMPERING_PRODUCT_COVER_REMOVED", event_parameter="", notification_status="ON", notification_type="HOME_SECURITY", v1_alarm_level=255, v1_alarm_type=7, z_wave_alarm_event="TAMPERING_PRODUCT_COVER_REMOVED", z_wave_alarm_status="ON", z_wave_alarm_type="BURGLAR", zensor_net_source_node_id=0}, cmd_class="NOTIFICATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x07\xFF\x00\xFF\x07\x03\x00\x00", src_channel=0, version=3}
2023-03-09T13:32:28.184551814+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled

Tamper Closed

2023-03-09T13:32:57.616315744+00:00 TRACE Z-Wave Device Config Mc  Received event with handler unnamed
2023-03-09T13:32:57.616988786+00:00 INFO Z-Wave Device Config Mc  <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> received Z-Wave command: {args={}, cmd_class="WAKE_UP", cmd_id="NOTIFICATION", dst_channels={}, encap="NONE", payload="", src_channel=0, version=1}
2023-03-09T13:32:57.618007953+00:00 DEBUG Z-Wave Device Config Mc  Nortek Open/Closed Sensor device thread event handled

Please note the other thread that was split from this thread also.
Thanks for any help!

1 Like

Just want to clarify on this sensor that it has some differences compared to the Ecolink, at least according to this description. I do not have an Ecolink to verify what this document says but I do have the Nortek/gocontrol: The Nortek reed switch/ external contacts are not in parallel. They do, in fact control two different parameters not an either/or
Thanks

1 Like

Hi @valkokir

The problem with this device is that in the driver it uses the default contactSensor handler and to emit the open close event it uses the event:

local contact_notification_events_map = {
     [Notification.event.home_security.INTRUSION_LOCATION_PROVIDED] = capabilities.contactSensor.contact.open(),
     [Notification.event.home_security.INTRUSION] = capabilities.contactSensor.contact.open(),
     [Notification.event.home_security.STATE_IDLE] = capabilities.contactSensor.contact.closed(),
     [Notification.event.access_control.WINDOW_DOOR_IS_OPEN] = capabilities.contactSensor.contact.open(),
     [Notification.event.access_control.WINDOW_DOOR_IS_CLOSED] = capabilities.contactSensor.contact.closed()
   }

And the device always sends the same event = “INTRUSION” and what changes is the alarm_level=0 for closed and alarm_level=255 for open.

Sensor Closed:

2023-03-09T13:28:49.490738967+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> received Z-Wave command: {args={alarm_level=0, alarm_type=7, event=“INTRUSION”, event_parameter=“”, notification_status=“ON”, notification_type=“HOME_SECURITY”, v1_alarm_level=0, v1_alarm_type=7, z_wave_alarm_event=“INTRUSION”, z_wave_alarm_status=“ON”, z_wave_alarm_type=“BURGLAR”, zensor_net_source_node_id=0}, cmd_class=“NOTIFICATION”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\x07\x00\x00\xFF\x07\x02\x00\x00”, src_channel=0, version=3}

Sensor open:

2023-03-09T13:27:04.447434241+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: 1a8b55d9-9eff-4581-a8b0-4b8c30ee2696 [02] (Nortek Open/Closed Sensor)> received Z-Wave command: {args={alarm_level=255, alarm_type=7, event=“INTRUSION”, event_parameter=“”, notification_status=“ON”, notification_type=“HOME_SECURITY”, v1_alarm_level=255, v1_alarm_type=7, z_wave_alarm_event=“INTRUSION”, z_wave_alarm_status=“ON”, z_wave_alarm_type=“BURGLAR”, zensor_net_source_node_id=0}, cmd_class=“NOTIFICATION”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\x07\xFF\x00\xFF\x07\x02\x00\x00”, src_channel=0, version=3}

For external contact use event=“UNKNOWN_EVENT_STATE” and values are 0 for open and 255 for closed and the default do not handle this event

It would be necessary to modify the diver and add a subdriver to handle the [Notification.REPORT] for this device instead use default handler

I don’t know if the device configuration can change the type of event sent for contacts

1 Like

While smartthings fixes the stock driver you can try to see if it works with this driver that is on my channel

──────────────────────────────────────────────────────
 Name         Z-Wave Sensor and Child Thermostat TEST 
 Version      2023-03-09T15:36:56.027436797
──────────────────────────────────────────────────────

driver deleted, it seems that it is not necessary

1 Like

Thank you, my error. I have edited my post above.