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)
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.
Yes, I’m working on it now so it should be available either late this week or the beginning of next week.
Thank you Kevin, Much appreciated.
Jesse
Is this device handler designed to work with the Dome Door/Window Sensor Pro (DMDP1)?
No, but it just came on the market so I’ll be writing a new handler as soon as it arrives.
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?
Are you sure you have the “Dome Door Sensor” and not the “Dome Door/Window Sensor Plus”?
Have you tried taking out the battery, waiting a few seconds and then putting it back in?
It’s this one:
https://www.amazon.com/gp/product/B01JGMZNNG/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1
Matches the DMWD1 you mentioned in the OP. Did remove battery just now and put it back, still stuck on closed.
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
The names are close so I just wanted to make sure.
I believe the device and magnet have lines on them that have to be aligned and on the same side of the device.
After opening or closing the sensor have you gone back to the Things screen and re-opened the device to see if it changed?
Yes, unfortunately it’s still stuck on closed.
I’m not sure if I have a defective one at this point. It’s definitely online and broadcasting but the magnets are not showing open/closed.
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!
This is unrelated, but I recommend changing the check in interval to at least an hour because waking up every 10 minutes will drain the batteries.
How many times did you open and close the sensor during those 20 minutes?
At least 10… and noted.
The device isn’t sending any commands to the device when the contact is moved.
Have you tried resetting the device? Remove it from SmartThings, open the cover, and hold the connect button for at least 10 seconds.
If that doesn’t fix it then it’s defective.
Yep, quite a few times. Doing a return through Amazon at this point!
Thanks for the help. Makes me wary of this company which sucks as it was affordable.
One faulty device doesn’t make it a bad company…
