Yep, very nice work. 
There’s already an author thread in this forum about the project:
1 Like
Any Update on when these fingerprints will be added? We are 9 days away from the death of Groovy DTH
1 Like
Maybe it’s just me, but I feel like this is the stage we’re at. Only we’re the people inside the palace. 
1 Like
Where’s the panel illustration with the multiple stakes ready to catch someone jumping over the wall blindly, @JDRoberts? 
4 Likes
Ninjas don’t jump over blindly. They jump on top of the wall, check things out, then decide the best place to come down.
unless, of course, they’re on a reality TV show.
Just sayin’… 
4 Likes
A little over a week away (with two holidays in the mix) from “groovy shutdown” and still not all “officially supported devices” have fingerprints in production drivers and not all devices have migrated. AND worst part no official communication or any communication for that matter from Samsung on any updates.
Best guess everyone is groovy really will be shutdown in a few days or if that deadline deadline is sliding again? I just gotta plan for grandma’s house out of state.
1 Like
Check the first post of this thread… dates have been modified.
But you should still go visit your Grabdma. 
6 Likes
If you use a stock Smartthings Groovy DTH then there will be no issues for you until early 2023
(See @JDRoberts post below for caveat)
If you use a custom Device type or smart app, it dies Dec 31
Thats my read on it
5 Likes
I’m not sure I would say “no issues.”
We’ve already seen issues with some of the stock edge drivers, so as devices get migrated, new issues can occur. And since there’s no official changelog for which drivers get added or changed, or any tracking for individual device migration, if you do run into issues you’ll have to just start researching devices individually. 🕵🏼♂️
4 Likes
So if I have a driver installed for a device with a custom DTH, it will definitely transition before Dec 31st? I have Zooz Zen51 relay working as a garage door opener, and I had to install a custom DTH when setting it up, because the driver was not ready yet. Now I have the driver, and I’ve been waiting for the transition for several weeks.
Not to mention one of my Yoolax shades is still using the 1st party DTH and haven’t migrated too, and I have the driver as well, because I used it from the beginning for my newer Yoolax shades which I installed later.
It “should” BUT who knows! The dates could change so always check out the first post of this thread. No one will say “definitely”.
1 Like
SharpTools is the way, I love it compared to WebCore.
4 Likes
Does anybody have Lightify gardenspots that have been migrated by ST to an edge driver yet?
I have Lightify GardenSpots. They have not been migrated.
I’m starting to wonder if they will be. Or are we going to have to do it after the first.
I am aware of this. And I will probably use that. I’m just waiting to see if Smartthings does it first. I really don’t feel like deleting and re-adding them and editing my routines that use them.
2 Likes
I’m not at all clear on the process for custom devices so someone may correct me…
If you have a driver installed that matches the fingerprint of the devices when automatic migration is attempted, I believe the process will select that driver. If nothing matches then you get a “thing” driver and possibly lose your routines.
So it’s probably useful to install the community driver even if you don’t do a manual migration of your devices.
While true, we’ve been told that it doesn’t have to be an exact fingerprint match. The system will also attempt to match based on generic capabilities if no fingerprint match was found.
Only if that also fails, will it then be matched as a “thing.“
1 Like