Linear Door-Windows Sensor WADWAZ-1 (GoControl Home Security Suite)

No, but my DTH for the GoControl Contact Sensor changes the contact attribute based on which ever one changed last and it also has the attributes “internalContact” and “externalContact”. That allows you to use a SmartApp like CoRE to perform different actions based on if the internal or external contact changed.

These devices go by several names and some have different firmware, but the Linear and GoControl versions use the same manual and product number so I’m pretty sure they also have the same firmware.

2 Likes

Nice!
Tnx.

I have problem with the windows sensor with v2 hub too. I do know how to set sensor to inclusion mode, and I am seeing the light blinking. I have no problem connect and remove this sensor with my v1 hub. It seems to be a hub issue. Here are some of my hub info. I have zwaveControllerStatus: 01 in my v1 working hub, but 09 in this v2hub. Does it matter?

presenceTimeout: 2
updaterVersion: 75
uptime: 40276
videocoreVersion: 0.8.16
zigbeeChannel: 15
zigbeeEui: D052A8A662420001
zigbeeFirmware: 2.1.10
zigbeeNodeID: 0000
zigbeePanID: 3298
zigbeePowerLevel: -6
zigbeeRadioDetected: true
zigbeeRadioEnabled: true
zigbeeRadioFunctional: true
zigbeeUnsecureRejoin: false
zwaveControllerStatus: 09
zwaveHomeID: C436603B
zwaveNodeID: 01
zwavePowerLevel: full
zwaveRadioDetected: true
zwaveRadioEnabled: true
zwaveRadioFunctional: true
zwaveRegion: US
zwaveSerialVersion: 4
zwaveSucID: 01
zwaveVersion: 3.83

Kevin, If I use your DTH, is there a way to detect if EITHER contact is open and just call it an open sensor rather than whichever happened last? I have a dual window, and if I have them both open and then only close 1, there is no security in place anymore since the sensor now reports all closed since that was the last signal. Does one of the stock DTH handle the inputs like this?

I don’t believe the stock device handlers work with the external sensor, but I could be wrong.

I need to make some changes to that DTH soon so when I do, I’ll add a setting that allows you to change that behavior. I’ll try to make this change some time this week.

The Monoprice Door/Window Sensors look the same as these, but when the external contact is enabled, the device won’t report closed unless both are closed.

ok great, thanks for working on that for me. The ones I have are the Go-Control (from the security suite) so I presume just changing to the monoprice DTH won’t help is what you are saying?

Correct, the Monoprice devices physically work like that so it has nothing to do with the DTH.

Another option is to create 2 virtual contact sensors and use CoRE to change their closed state based on this device’s “internalContact” and “externalContact” attributes.

It would be a pain to setup and you’d probably have to search the forum to find a virtual/simulated contact sensor DTH that allows you to manually change their state, but it would solve your problem.

I actually know how to setup the virtual switch, but I can’t figure out how to detect which of the 2 contact types to read off of, do you have a screen shot or can you explain that one? This is what I was trying originally but couldn’t figure out how to tell which contact I was reading and how to do both.

The internalContact attribute is the physical device and its magnet, the externContact is the one attached to the terminals.

It’s a little more complicated than I originally thought because CoRE doesn’t allow you to enter a value when using a custom attribute so you have to create a variable with the value “closed” in order for this to work.

To create the custom variables:

  1. Open or Create a New Piston
  2. Scroll down near the bottom and tap “Local Variables”.
  3. Tap “Initialize a variable”.
  4. Type closed into the first field and closed into the second field.
  5. then tap “Initialize”
  6. Tap Done three times to get back to the main screen of the piston.

Setting up the Trigger/Condition

  1. When setting up the trigger/condition Select the actual device and choose “internalContact” for the attribute field instead of using “contact”.
  2. Use whatever you want for the “Comparison” field.
  3. Use the “or choose a variable to compare” option to select the closed variable you set up earlier.
  4. Use the “when true, do…” and “when false, do…” fields to set the open/closed state of the virtual device you created for the internal sensor.
  5. Repeat steps above using the externalContact attribute and the virtual device being used for the external contact.

Kevin, I am not getting the option to select internal contact, what I am doing is selecting piston mode “Basic” --> “IF…” --> “Add condition”–> Capability “Contact Sensor” --> “Dining Room Window” -->

Now the only option I get is Comparison where you show Attribute

Was I supposed to do something different than the basic piston and an IF statement?

1 Like

I didn’t realize that was only visible when you have “Expert Mode” enabled.

If you want to enable it, go to the bottom of the page that lists all your pistols, tap settings, and enable it.

I think I got it, made my rule, but it doesn’t seem to think the window is “closed”. I get the rule to make the virtual switch change state, and when I opened the window, the virtual switch said open, however it would not revert to closed. The piston shows “false” all the time for the closed detection. I am going to try playing around more but its sooooo cold out I can’t play with the window much, I may grab another sensor and do bench testing.

I’ll most likely have the changes I mentioned completed sometime this weekend…

I just released a new version that has the feature you were looking for.

Kevin, you’re awesome, thanks for all your help and your code, I cant wait to try it!

1 Like

Works like a charm, I love this community and people like you that help like this.

1 Like

probably a stupid question, but I"m going to ask anyway.

I opened up my GoControl door sensor to get a look at the battery and it triggered the tamper switch, so now the sensor is showing as always open. I found the user manual online, and it mentions that this is the expected behavior, but they don’t talk about how to fix it.

Can someone help me figure out how to reset the tamper switch without having to re-pair the device (and recreate all my automations) ?

Thanks!

If you use my Go Control Contact Sensor DTH then you can change the tamper attribute back to clear by tapping the “Refresh” tile.

@krlaframboise What are the chances you can get your DTHs for the Go Control devices into the SmartThings Master repo, and have them get these working locally? I personally use the external sensor setup to have my double hung windows alert correctly when the bottom or top is open, and also use it on a multiple-window setup where its 2 or 3 wide… This DTH should be the default for these devices in my opinion!

SmartThings stopped accepting publication requests a long time ago and they’re switching to a new platform so there’s no chance of that happening.

If you want everything to run locally then you might want to consider switching to a different hub like Hubitat which is similar to SmartThings, but everything runs locally, and it has a fully functional built-in handler for this device.