I have Schlage Camelot deadbolts on multiple homes which all became highly unreliable when I swapped from the Groovy based device driver (Rboy) to the Generic Z-Wave Lock w/ Codes driver. They only occasionally work and after several minutes of delays in communicating with the hub. In an attempt to remedy this I excluded one of my test locks from the system, and did an automatic device add.
Problem - The device is immediately added back my network using the old Groovy driver published for my account! Smartthings itself decides that that’s the best driver and selects it. And the lock works perfectly.
So - should I just leave the lock using the old driver and hope for the best? This seems like a “rolling the dice” situation and I don’t like doing that.
you need to delete the rboy DTH ( i also deleted the smart app)
from the smart things ide. exclude the lock and then readd it. Rboys was what was causing my issues. Once i deleted it both my schlage and yale lock started working where are prior to that i was having issues. Literally did it 530am this morning when i got up and realized that when my kid got home last night at midnight the door never relocked.
During this transition time, if you have a custom groovy Device type handler on your account, that will be given preference until your device has been officially migrated by the automatic process.
As @woolfman72 said, you have to first delete the custom DTH from your account before the edge driver will be chosen. (But no delete it there’s no longer any way to add it back. So be sure that’s what you want to do.)
I just wanted to mention that that is true for any custom DTH, not just @rboy ‘s.
See the official transition FAQ code
So what you are seeing is the expected behavior, even if it’s a confusing process.
Terminology note, just to reduce a little bit of the confusion: there are no “groovy drivers.” There are “groovy handlers“ and “edge drivers.“
Thanks for the very helpful replies. I actually tried to delete the device handler and I was not able to do so. I will keep looking for how to accomplish that.
I am concerned however that I can’t just switch to the edge driver. Inside the IDE I can select whatever driver I want but regardless of which one I select I seem to have problems. So I’m a little concerned about deleting the working device handler not knowing if I will ever be able to get it to work again. Does that make sense?
It’s super annoying right now, but again, this is only part of the transition process. You won’t be able to remove the DTH unless you have deleted all of the devices that use it. Which mean that, yes, you will also have to re-create all of your automations that use those devices.
This is why many people are just leaving things as they are until the automatic migration happens, and then dealing with any issues afterwards. Because that’s the only way to avoid removing and re-adding the device.
Here’s the community FAQ on how to use edge drivers which will explain the process if you want to do it manually:
How does one determine what driver is currently in use, and how would one specify use of an “edge” driver? I have previously used ide.smartthings.com to manage all of my devices, handlers, etc. Am I correct in assuming that everything there is Groovy based and will be depreciated? Or only the customer device handlers? Are all the Samsung provided drivers now Edge based?
Is there by any change an “Edge Migration Guide” that provides a step by step? This is just massively confusing for an average user.
EDIT: I found a few resources to answer a lot of my own questions: https://support.smartthings.com/hc/en-us/articles/9339624925204-Platform-Transition-FAQ for example. Unfortunately this appears tremendously more complex than the previous architecture for a light weigh power user. We live in a world moving toward codeless development solutions, I’m dissapointed to read pages of instructions for loading libraries, running command line clients, etc. On the flip side I can really see the advantages of local execution, so that’s a big plus. But a a (former) “power user” of Smartthings, who developed 7-8 Groovy smartapps - this looks like a bridge too far for me. Sharptools looks promising, but still significantly lags behind WebCORE.
Fingers crossed we can iron out these challenges and get back to where we started ASAP, which was a vibrant and easy to access development community. I’m hopefull and will stick around until hopefully that happens