For anyone that’s interested, I scanned the user manual. I’ll throw it up in the op as well.
If someone can create a fully functioning DTH I’d definitely be interested in these. Been holding off on the AEOTEC because of the $$.
I updated op with pic from monoprice that shows all the accessories. These all came in the box.
Thank you for the scan. It’s very well documented and should thus be easy to put together a dth (ie 10 min) unless there are firmware bugs. Will put one together if a I have chance this weekend. Won’t be able to test it since ST is only at the office, not at home.
I could test it for you -
Might be buggy and I can’t test. Anyway, try it. I’ll update it on Monday after I can actually test it. Will also implement setting of wake-up time interval.
Here’s the spec page with another version of the manual:
Another thought – if the default dth works and is local (not in the cloud), might be worth using that even if the battery level is not working
Updated. Now works.
BUT, the Zwave Plus Door default dth worked for me, with battery state. I assume it’s local (haven’t checked), if so, I would just use that.
Need to know if anyone is needing to use my version of the DTH or if using the stock Zwave plus door sensor. And, if using mine, do you want an adjustable wake up (battery reporting) interval – factory set at 6 hrs.
I’m trying with the stock z-wave plus door sensor, but it’s always reporting as open. Any ideas?
Sounds like the sensor itself might be an issue. Remove it from network. Pull the battery. Give it 30 secs. Replace the battery. Observe if the red led flashes when you bring the magnet close to the reed switch and then again when you pull it away.
Added it back to network while logging. Make sure it installs with “Z-Wave Plus Door/Window Sensor”, See if it works at this point.
Can you describe what you mean by adding it back while logging?
Also, it installs with the generic z-wave door window sensor, and I was manually going into graph.api to change device type to the plus.
Have “Live Logging” on the screen while adding it to the network – just in case we need to look at the logs to figure out what is going on.
11:16:15 PM: debug Parsed 'zw device: 10, command: 9881, payload: 00 80 03 3C ' to [[name:battery, unit:%, value:60, isStateChange:true, displayed:true, linkText:Z-Wave Plus Door/Window Sensor, descriptionText:Z-Wave Plus Door/Window Sensor battery is 60%]] 11:16:15 PM: debug encapsulated: BatteryReport(batteryLevel: 60) 11:16:14 PM: debug Parsed 'zw device: 10, command: 9881, payload: 00 72 05 01 09 20 22 22 01 ' to [[name:ManufacturerCode, value:0109, isStateChange:true, displayed:true, linkText:Z-Wave Plus Door/Window Sensor, descriptionText:Z-Wave Plus Door/Window Sensor manufacturer code is 0109], [name:ProduceTypeCode, value:2022, isStateChange:true, displayed:true, linkText:Z-Wave Plus Door/Window Sensor, descriptionText:Z-Wave Plus Door/Window Sensor produce type code is 2022], [name:ProductCode, value:2201, isStateChange:true, displayed:true, linkText:Z-Wave Plus Door/Window Sensor, descriptionText:Z-Wave Plus Door/Window Sensor product code is 2201], [name:WirelessConfig, value:ZWP, isStateChange:true, displayed:true, linkText:Z-Wave Plus Door/Window Sensor, descriptionText:Z-Wave Plus Door/Window Sensor wireless config is ZWP]] 11:16:14 PM: debug MSR 0109 2022 2201 11:16:14 PM: debug encapsulated: ManufacturerSpecificReport(manufacturerId: 265, manufacturerName: Vision Security, productId: 8705, productTypeId: 8226) 11:16:11 PM: debug configure()
Interestingly, this time it installed with the plus DTH
Does yours report battery properly, or is the 60% likely a glitch in the DHT?
Thanks again for all your help, I think other than the weird battery reporting, this works great.
I suspect that the 60% is correct. You can pull the battery and check the voltage (I think 3V is 100% and 2.1 is 0%)
Glad the sensor is working.
I just wanted to add to this thread in case someone is having trouble with these and comes upon it like I did.
These sensors are extremely sensative to distance during the initial inclusion. I had three of them, one came in as a standard z-wave door/window, one came in as a z-wave plus, and one came in as a device type I didn’t understand (just said active and inactive, no battery, etc). I ended up excluding all three and then rejoining while 3 feet from the hub (which I should have followed the instructions better). Once I did that they correctly all identified as z-wave plus door/contact and worked fine.
Overall they are nice for the money. Look a lot better then the SmartThings multi purpose sensors I had on my doors before. They react very quick but as someone said the door has too be open a good amount. The magnets that come with it are pretty hefty.
Hey, thanks for doing this! I just have been using these sensors for a while now and decided to look for a handler because I am still somewhat a noob.
It had been working fine but I was wondering if the handler will give me more usage with webCoRE?
Also will I see any differences from my ST app interface with this? The only thing I noticed is that it greyed out the status of the door. IE it use to be a blue when it was closed and red when it was opened. Now it’s just grey. Do I need to remove my device and re-add it to ST when I add a handler?
Hi. The custom handler won’t give any increased functionality with webCoRE. Since they are working fine, I would not recommend switching the handler.
Can you tell me what I should be seeing? Since I have done the handler the only difference I am seeing in ST app is the colors of the open/close. Should I be seeing more?