I won’t be converting the Dome Door Sensor DTH into an Edge Driver so it will stop working once the Groovy platform is retired, but it doesn’t need a custom driver.
This is the Official device handler for the Dome Door Sensor (Model: DMWD1)
Allows you to change the wake up interval and battery reporting interval.
Thank you Kevin, this worked great, I found these and purchased them before I realised they were not officially supported in Smartthings so I truly appreciate the work you put in to create this.
Any chance you have something similar for the Dome motion sensors? I have a few of these as well.
So i setup this device handler and included the sensor in my system. However, it’s stuck reporting ‘Closed’ even though I have the pieces separated. I added a 1minute interval in the handler just to test and nothing will trigger open/closed.
Are there any tricks / things I’m missing to get this to work?
Checkins are fine:
2017-09-09 2:18 PM CDT - moments ago lastCheckin 09/09/2017 02:18:54 PM
2017-09-09 2:18 PM CDT - moments ago lastCheckin 09/09/2017 02:18:53 PM
2017-09-09 2:18 PM CDT - moments ago lastCheckin 09/09/2017 02:18:51 PM
2017-09-09 2:08 PM CDT - 13 minutes ago lastCheckin 09/09/2017 02:08:46 PM
Other info from device in IDE:
Dome Door Sensor Device Dome Door Sensor
Name Dome Door Sensor
Label Dome Door Sensor
Type Dome Door Sensor
Version Published
Device Network Id 0E
Status ONLINE
Hub Hastings Hub
Last Activity At 2017-09-09 2:18 PM CDT
Date Created 2017-09-09 2:08 PM CDT
Last Updated 2017-09-09 2:09 PM CDT
Data No data found for device
Raw Description zw:S type:0701 mfr:021F prod:0003 model:0101 ver:3.77 zwv:4.05 lib:06 cc:5E,86,72,5A,73,80,71,30,85,59,84,70 role:06 ff:8C06 ui:8C06
Current States
battery: 95 %
contact: closed
checkInterval: 1320
lastCheckin: 09/09/2017 02:18:54 PM
Preferences (edit)
Name Type Value
batteryReportingInterval enum 12 Hours (Default)
debugOutput bool true
wakeUpInterval enum 10 Minutes
Execution Location Cloud
Events List Events
In Use By
At the very bottom of the code there’s a line that starts like // log.trace, remove the slashes and save/publish the code.
Open Live Logging, move the magnet away from the device, wait about 10 seconds, touch the magnet to the device (make sure the lines match up), wait about 10 seconds, do both again, and then post the live logging data.
Clear
a8ac073a-2d9a-4551-be4c-b493c0f2ee77 5:20:24 PM: trace Skipping battery check because it was already checked within the last 12 Hours (Default).
a8ac073a-2d9a-4551-be4c-b493c0f2ee77 5:20:24 PM: trace WakeUpNotification: WakeUpNotification()
a8ac073a-2d9a-4551-be4c-b493c0f2ee77 5:10:19 PM: trace Skipping battery check because it was already checked within the last 12 Hours (Default).
a8ac073a-2d9a-4551-be4c-b493c0f2ee77 5:10:19 PM: trace WakeUpNotification: WakeUpNotification()
a8ac073a-2d9a-4551-be4c-b493c0f2ee77 5:00:13 PM: trace Skipping battery check because it was already checked within the last 12 Hours (Default).
a8ac073a-2d9a-4551-be4c-b493c0f2ee77 5:00:13 PM: trace WakeUpNotification: WakeUpNotification()
All the data I’ve had. It’s got to be defective at this point, right? Thanks for helping me diagnose nonetheless!