The End of Groovy Has Arrived

I’m getting a bad link when I check that out

Should be fixed now.

I had one of each device type migrate and the one device that had previously migrated actually revert back - with drivers showing in hub device properties in the app. The easiest way to keep things consistent was to remove the devices (taking steps to not lose any routines) and then re-add them. Devices not yet showing as Placeholder are Hue and Sonos.

The Sonos driver for Edge isn’t quite ready for prime-time. It’s quirky and several commands don’t function as intended. SmartThings is working on it, but I’d be patient with that one.

Use EDGE driver, Does device will be executing locally?

yes, all Edge drivers run locally on the hub


so it appears Edge drivers take precedence over Groovy DTH including custom when pairing devices.

1 Like

I asked @nayelyz to check on this two weeks ago because we are seeing reports both ways in the forum now. Some people saying they had to delete a custom groovy DTH before the edge driver was accepted and others saying they didn’t.

I am starting to wonder if maybe it varies by model number now, but I just don’t know. Or maybe there’s even a flag on individual accounts for specific devices that have been automatically migrated. It still feels confusing. :thinking:


@JDRoberts And, the precedence actually switched for me from DTH precedence to Edge Driver precedence over the last few weeks. (for a Quirky Tripper from Sercomm (originally on Wink) )- so a pretty old/ now uncommon device).

It could be, and likely is, a complete coincidence, but I had my first ‘significant’ migration happen in the same period. (about a third of my Commercial Electric tunable downlights switched over) - just thought I’d mention it - it could be hub-specific. (I’m on V2, FWIW).

[CORRECTION - upon review I think that installing a custom driver with the exact fingerprint is what caused the ‘change in behavior’ - sorry about any confusion!]

1 Like

I changed today Fibaro Smart Implant (Z-wave device) from the custom DTH to Edge driver.

I made first Z-Wave Exclusion and then I made normal “scan nearby”
and Smart Implant onboarded with Edge driver.
I still have in IDE Smart Implant’s DTH.
So Edge driver for my Smart Implant is now taking precedence over the custom DTH.


Hi, @AlecM, @JDRoberts

I have checked how fingerprints work (order of preference) and already installed drivers should be preferred against custom DTHs.
However, it is strange for this to happen, it would be worth getting the Hub logs from someone experiencing this.
@AlecM, it was solved in your case, right?

First, I thought it could be that in some cases, the fingerprints on the DTH were more specific than those on the driver
But, if it’s a custom one, it should have the exact fingerprint of the device as I’ve seen users share them with the developer…

Hello @nayelyz. Yes, my slightly customized Edge driver (I just tweaked the stock one to add the Quirky Tripper fingerprint) is picking up a new Tripper just fine, although I can still see the custom DTH which also has the full fingerprint. That changed sometime in the last few weeks. All resolved for me. Thanks!

Actually, @nayelyz - I thought back and then realized that I had trouble with the DTH overriding when I was trying to pair to stock, not to a custom driver. Of course the stock doesn’t have the fingerprint. I think it worked ok right away once I figured out how to install a custom driver that had the correct fingerprint (either MCs or my own slightly tweaked stock). Apologies for the red herring!


Only 38 days until the end of Q1 - which is when everything is supposed to be moved over to Edge! :+1:

And I have only have 160 devices to go :grin:.


Ha! Here’s to hoping!

1 Like

That’s 4 devices a day.

How many devices do you have already migrated?

If they converted something every day that might not be so bad, lol.

I have a strong suspicion that we’ll see SmartThings announce another delay.