I am trying out an older 500 series strip from Sensative. The fingerprint is in the list for the standard ST zwave sensor driver. However, when scanning devices, it keeps picking up the DTH instead of the edge driver. Any ideas? The driver is installed, as I use it for a bunch of other sensors.
It is worth noting that the DTH is used by other devices beside this one. Does the hub give it preference if it is in use elsewhere?
hmmm…then it kind of sucks that we can’t delete DTH’s from our account. The end-of-groovy sticky specifically said you would be allowed to edit or delete existing DTH’s after 10/15, but in fact all that happened is that ALL edit features were disabled, so now we can’t even delete a DTH in order to test an Edge driver.
Are you still having issues with the device? In the past, we have seen this happening because the device is not responding correctly to the “call” from the Hub to get its fingerprints, and sometimes, it doesn’t send all the information. Some users faced this issue after changing the device’s battery which is strange as well.
If the issue is still present, we would need to check your Hub’s logs.
If it wasn’t returning the fingerprint correctly, why would it pick the DTH? It has to have the correct fingerprint to be grabbing the DTH that is being used.
I just mentioned what I’ve seen before. There have been no other recent reports about something similar.
So, please share the following information to report this issue:
Confirm the email account registered in the forum is the same one you use for SmartThings. If not, share it over DM.
Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.