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?
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.
Changes:
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.
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?
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!
David
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.
The base motion function seems to not be impacted. I actually have one outside however. It was kind of cool seeing what the outside temperature was. This is how I caught it.
(I am not sure how it will fare in the winter, but I thought I would give it a go. It is in a covered and sheltered area not exposed to sun/wind/rain(snow). I purchased the GoControl kit and so I kind of had an extra motion sensor ā¦ weāll see how it fares.)
It looks like SmartThings broke the convertTemperatureIfNeeded function for precision 0 and it now adds a period at the end which isnāt a valid number and is causing this problem.
I just released a new version with a workaround that should fix the problem.
Funny, I recently asked about this function and @tpmanley (Tom) kindly filled in some details. He noticed an issue in the code & created a ticket for it. Perhaps someone tried to fix it & broke what you found, Kevin.
(Another case where running unit tests before merging to mainline would have caught it.)
Thatās actually what I just did because I knew there was a firmware bug that is going to cause problems if you use it outdoors in the winter, but I couldnāt remember the details.
Once the temperature drops below 32Ā°F the device starts reporting using a -52Ā°F offset.
The device reports 31Ā°F as -21Ā°F
Thatās the value that the device is reporting so itās not something that ST or my DTH is doing.
Since thereās no way the device would actually function at -21Ā°F I just released another version that adds a +52Ā°F offset when the temperature drops below it.
The device I have always reports the value in F, but if thereās a European version of the device that reports it in C then Iām not sure if this change will break anything.
. Iāll file another ticket.