[RELEASE] GoControl Door/Window Sensor, Motion Sensor, and Siren DTH

Kevin, how would I mod the original contact sensor handler to show a Garage Door Icon rather than a standard contact sensor icon? I find the lines of code but have no idea what to replace them with.

I’m using a regular sensor on the garage door itself. Nothing more than wanting to change the icon. Can you possibly post a couple modified lines of code to replace, or instructions on how to do this. As code goes, consider me able to find anything you point to but have no idea what I’m doing with it. :slight_smile:

I just added an option for “contact-garage” to my GoControl/Linear Multifunction Contact Sensor device handler so if you switch to that one you won’t have to modify the code.

If you’d prefer to keep the the simple version of the DTH and modify the code, all you have to do is replace “st.contact.contact.closed” with “st.doors.garage.garage-closed” and replace “st.contact.contact.open” with “st.doors.garage.garage-open”.

1 Like

GoControl/Linear Door/Window Sensor v1.9

I just released version 1.9 that has the setting “Create Device for External Sensor?”. If you install the “GoControl External Contact Sensor” DTH and enable that setting a new device will be created for for the External Contact.

If you change the “Main Contact Behavior” to “Internal Contact Only” you’ll be able to use the internal and external sensors as separate devices.

The new version of this device handler and the child device handler can be found in the first post of this topic.

1 Like

Does this work with Monoprice 15271 (PIR Motion Detector with Temperature)?

They do work, but recently the temperature has not been reporting… Maybe @krlaframboise can assist in troubleshooting?

I’ve removed and re-paired each one to no avail…

Are you on the latest version of this DTH and have you gone into the device settings and saved since upgrading to it?

Is it the Monoprice motion sensor that stopped reporting temperature? I know it’s a similar product, but I wasn’t aware that it worked with this device handler.

It is a monoprice sensor… it worked with release 1.2 but not 1.3. I’m pretty sure the gocontrol and monoprice are the same ones no?

The only manual I could find for the Monoprice motion sensor doesn’t mention anything about it reporting temperature so I’m unable to verify if it’s the same device.

I compared the DTH versions and besides having to go in and change the configuration settings after upgrading, I don’t see any changes that could have broke the temperature reporting.

I recently starting using this external sensor for my GarageDoor2 with my primary contact on GarageDoor1. Previously I had 2 contact sensors both using external (because I had previously mounted reed switches). I mounted the WADWAZ-1 next to the door and it seems to be working great with the internal sensor on door 1. Forr the external sensor on door 2 however, the external sensor sometimes (20%???) misses a close (door shows open even though it is truly closed). I seems to correct itself on the next open/close cycle.

Anyone else use both sensors in one WADWAZ-1 and see this type of problem?


GoControl Contact Sensor v1.10


This update may temporarily cause the primary tile to display the wrong state. It will correct itself the next time the device wakes up or you can force it to immediately correct itself by opening the settings and tapping Done. The values of the capabilities that other SmartApps use are not effected.


  • New setting that allows you to display the main tile as a garage door sensor.

  • Removed the ability to manually change the icon because when that’s enabled the Android app is unable to display different icons for open vs closed. I’m not sure if that problem effects the iOS app.

  • Improved Health Check integration which should reduce the number of false offline statuses. Due to the way SmartThings implemented the Health Check feature the device will appear offline/unavaiable every time the Hub goes offline and won’t change back to online until it is opened/closed or wakes up. I recommend setting the “Checkin Interval” setting to 2 Hours so that if the status shows offline for more than 2 hours you’ll know that it really is offline.

  • Switched to SmartThings new color theme.

  • Added tile that displays the last activity time which is the last time that the device communicated with the hub.

  • The items in the recently tab are only kept for 7 days so beyond that you have no way of knowing when the sensor was last opened and/or closed so I’ve added tiles that display those times.

Let me know if you run into any problems with this version or have any comments about the changes that I’ve made.

Also let me know if you think I should create a separate topic for the contact sensor.


A new topic might be nice to seperate it out.

My first post here - be nice :slight_smile:

These devices are great! The child control for the external sensor for the window/door device is slick.

Can an external control be created for the tamper alert/notification also?

The external contact can be used as a separate device, but all that tamper does is notify you that the cover was removed from the device so what would be the point?

The basic idea is if my kids try to mess the door sensor I can get a notification via the tamper alert. Right now I think the tamper alert/warning just lets you know through the SmartThings app that I would only see if I manually checked it versus a text or notification. Make sense?

If you use the SmartApp CoRE you can send notifications based on the Tamper Alert trigger.

I actually got webCoRE to work too.

Thanks for the suggestion!

Hello Kevin,

The device handlers are just great, the windows/doors sensors works perfectly but I had an issue with the motion sensor. When I added the DTH for this devices and configured offsets, thresholds, chekin, etc, the temperature always reports 0°C and the battery to 85% (the batteries are just new), but when I rolled back to the default handler (I think is from Aeon) the temperature starts reporting just fine (unfortunately the battery is not reported in the default handler). Did the same had happened to you/someone. is there a fix for this or maybe is some configuration?
Thank you so much!

Yesterday all of my motion sensors started reporting 0 degrees. Coincidentally after the .22 update. They were all working great prior. I have not pulled the battery on the motion sensor but I did try a hub reboot and a zwave repair. I did pull the back off of the motion sensor. Others seeing this too?

Yes, mine started doing the same thing. Some of them started reporting properly again so I was hoping SmartThings was going to fix whatever they broke so I wouldn’t have to troubleshoot it, but it looks like some of them are still doing it this morning.

If it’s not fixed by tonight I’ll look into it and publish a new version that fixes it.


Yes, here too. I’m away from home at the moment & haven’t had a chance to do any troubleshooting :worried: