Hey: mine moves to “unavailable” state after some hours of inactivity … don’t know exactly how many, some 12hr+. However, if the door is opened/closed, the sensor moves out of unavailable state. My guess, the sensor moves to “unavailable” state as it does not ‘talk’ (like, battery state) to ST.
One more question, did you pair in secure mode (3 sec. long press, instead of 3 short press of Z-button while paring)?
I have the Monoprice 15270 working with this device handler. The internal sensor indicator works just fine.
However, turning the “Enable External Sensor” slider to the on position doesn’t appear to do anything. When enabled even when nothing at all is connected to the external sensor contacts, when the magnet is placed by the 15270 sensor, the indicator changes to “Closed.”
I thought that when the “Enable External Sensor” slider is in the on position, it is supposed to show “Open” status unless both the internal sensor is closed (magnet adjacent) AND the circuit connected to the external contacts is also closed. Am I doing something wrong?
The device sleeps so if you didn’t wake it up after making that change then that’s the reason why it’s not working as expected.
I am not clear what is required to wake up the 15270.
I assumed that it is already awake because, in the SmartThings app, your device handler immediately shows the Open or Closed status every time I move the magnet away from or adjacent to the sensor.
EDIT: days later, the external sensor function is still not working. Suggestions?
This is a little late, but the device wakes up every time you open and close the cover.
Dang, this z-wave plus version of this device is giving me lots more trouble with the external sensor. I was using the Linear WADWAZ-1 before, but the sensor I had for it kept flapping open/close like crazy and initially I had range issues with it not being z-wave plus… so I had this monoprice one waiting to install.
I can get it to report open/closed using the main sensor, but I am not getting the external sensor to work at all - even while holding a magnet over the main sensor. I ordered this one to try to get a little better results than the noname brand before: https://www.amazon.com/gp/product/B003V1F8IY/ref=od_aui_detailpages00?ie=UTF8&psc=1
It looks like it’s normally open, so how the heck is this not working? Any ideas how I can test/debug?
It will open report closed when both contacts are closed. It will open report open if both contacts are closed and you open either one of them.
You also have to enable the external sensor in the settings and then wake the device up after making that change.
Yeah my process of having both closed, then open the external is not reporting the open… it is reporting open/closed like normal when I put a magnet against the main sensor, but it’s like the external sensor isn’t even hooked up as it has no impact on anything. And I’ve enabled it in software. Maybe I need to test continuity on it 
Did you enable it in the settings and then open the cover and close it about 5 seconds later?
Make sure you’re using the classic ST app because I don’t think the new app will show that setting.
I’ve enabled the external sensor, triggered (and visibly received) tamper alert, and as before now I have got absolutely no events coming from the device other than check-in or tamper. I have used the provided magnet to trigger (I can hear it) the main sensor back and forth, the external sensor, trigger the main while triggering the external… I have absolutely no events coming now. It just sits at “closed.” No contact event since 5/27.
Even log shows only check-ins & tamper & manual refresh from the device since then.
This is working far worse than the Linear Z-Wave one which was nearly identical… and it didn’t require the stupid external sensor to also have the main sensor closed magnetically. Considering just switching back to the old one… this was supposed to be an upgrade. Grrr.
I ended up buying a few of these because they were really cheap, but I don’t recommend them. I like the Linear version a lot more, but I think they discontinued them…
Yup, these things are totally unreliable (just like Monoprice’s motion sensors). I guess you get what you pay for.
I came across this trying to setup my Monoprice-purchased Z-Wave Plus Door/Window Sensors, but I don’t think it’s the same kind. Apparently mine are Hank-tech
Model: HKZW-DWS01
Raw Description: zw:S type:0701 mfr:0208 prod:0201 model:0008 ver:1.04 zwv:4.34 lib:03 cc:5E,86,72,71,59,85,80,84,73,70,7A,5A role:06 ff:8C00 ui:8C00
Specs: http://manuals-backend.z-wave.info/make.php?lang=en&sku=HKZW-DWS01&cert=ZC10-18046078)
I can get it to show up in ST and change the DTH (changed the fingerprint to match). I can also see the events update correctly on api.smartthings.com but the mobile app just gives the error “Can’t connect to device. Check device and try again.”
Is there something I’m missing? Why would the website be able to see events from the device but the mobile app can’t connect? It’s listed as Cloud Execution Location, but that’s not configurable (from what I can see).
Any tips or pointing in the right direction would be appreciated. Also, thanks to Kevin and all those making this community vibrant. If I figure out how to use these, I’ll update for those that may have similar.
Are you using the SmartThings Classic app or the new SmartThings (Samsung connect) app? Custom code will not work on the new app at this point.
Yep, that was it. Using the classic app now and can see it’s working. Thanks, jkp!
i had to write an app using the Groovy IDE to get the Hank contact sensor to produce notifications on my phone (using the new SmartThings app). the device could not be selected in the app when making a new Automation (it didn’t appear in the list).
Hi a bunch of mine keep going “unavailable” as well. It looks like it doesn’t respond to ping or refresh, but when it opens or closes, it immediately falls out of Unavailable for a short while, then goes back. Not sure what’s up? @krlaframboise, any thoughts? Great work on all the DTHs, btw
The device sleeps so it can’t respond to pings, but it wakes up at the interval specified in the settings. I believe there’s a setting for how many check ins it can miss before reporting offline so uncreasing that number might solve your problem.
update: i just realized this is the monoprice device handler which doesn’t have that setting so try changing the wake up/check in interval to 2 hours and then open the cover, wait 5-10 seconds to wake it up, and close the cover. That’s what mine are set to and I’ve never had them go offline.
Thanks, so I tried that.
But what seems to happen for me is even with that 2 hour interval set, it almost immediately stops responding to pings and goes offline.
It looks like it will come online. Then a ping is sent to it, and approximately 1 minute later is goes offline. Is the ping from the hub or is there a way to control that from the Device Handler to override that so it doesn’t ping as often?
The hub pings the device if it’s last check in exceeds the expected checkInterval, but the device can’t respond to the ping. The device is sleeping so it ignores all commands sent to it, this is a z-wave thing and there’s nothing that can be done about it.
If you have the check in interval set to 2 hours it should wake up every 2 hours and the expected checkInterval should be 6 hours 5 minutes so SmartThings shouldn’t ping the device or mark it offline until it misses 2 check-ins and is at least 5 minutes late for the 3rd which really shouldn’t happen.
On the device details screen in the IDE, what is the checkInterval value? If you’ve changed the check in setting to 2 hours, saved, and successfully woken up the device, that value should be something like 21900.
