Sorry to be slow on this but before buying I just want to be sure - this allows using the contact sensor and the external contacts simultaneously right? My Ecolink sensors are an either or setup.
If it’s the same model as the one I wrote the handler for 3 years ago then yes, but I’m pretty sure they discontinued that device a while ago…
Thank you for this DTH. I am using the dry contact feature of this sensor to interface with a network video recorder alarm. It’s working fine except the state is reversed (default (no motion) shows ‘open’ when I’d like it to show 'closed;). I initially tried modifying the generic ZWave device handler unsuccessfully before happening across your work in this thread. Any chance you could guide me in the lines of code I’d need to modify to reverse the reported state?
Please disregard my question. I had another look at your first post and realized that I could customize the attributes and have the primary state report as a motion sensor (which is basically what I’m using it for via the video recorder).
I’m not able to do anything with this device in the new Smarttthings app. Clicking the tile gives me “Can’t connect to Device. Check device and try again.”
In the classic app, this device has always functioned flawlessly and still is. I have Webcore Pistons set up that still function and the IDE still shows everything as online.
I believe this is the last device I need to get working in the new Android App.
I’ve done a lot of searching but have not found any real generic migration tips.
Does anyone have any troubleshooting tips for this?
What features are you using that aren’t supported by the built-in DTH?
I had to refer back to where I posted about how I was using this back in Jun 2018 since I couldn’t remember. The only thing I modified from your original version was naming conventions but the below post indicates how I modified the unit for my use.
Changing the definition section to the following should at least allow you to open the device and see the water, battery, and tamper states.
The new mobile app caches the UI for 12 hours so you might have to change the device to a different DTH and then back to this one to see if the change worked. That doesn’t always work so it’s sometimes easier to just create a new handler with a different name.
name: "GoControl Multifunction Contact Sensor", namespace: "krlaframboise", author: "Kevin LaFramboise", ocfDeviceType: "x.com.st.d.sensor.moisture", vid:"generic-leak"
Thank you very much. This did work to show the basic stats as indicated. Do you think there will be a more permanent fix once SmartThings stops changing things around?
The device can only appear as one type of primary device, but this handler supports a bunch of different capabilities so changing the ocfDeviceType to the type you want it displayed as is the permanent solution…