Hey @Cory_Booth - I hope you don’t mind that I moved this part of your Show Off Your Dashboards post to it’s own thread – I figured it would likely generate some discussion and is a good topic with the upcoming SmartThings platform changes. 
–
SmartThings recently started rolling out first-party Edge Drivers to production for newly onboarded devices and they plan on migrating first-party Groovy DTHs automatically at some point in the future (though time will tell what this actually looks like).
If you’re using community Groovy DTHs, you’ll either have to switch back to the standard first-party SmartThings DTHs so you can auto-migrate to Edge Drivers, manually move to an equivalent Edge Driver if there is one*, or the DTH will stop working when Groovy is sunset.
A key caveat to moving from a custom DTH to a community edge driver is anytime a device is removed from SmartThings and re-onboarded, it gets created as a completely new device. That means that any rules/automations you’ve built in SmartThings, or any SmartApps that used the ‘old’ reference to the device are no longer valid. So you have to update your rules or SmartApps to reference the ‘new’ instance of the device. That means that SharpTools also sees it as a brand new device, so it would impact your dashboards.
As you might surmise, the simplest approach from a migration perspective is to use built-in DTHs that automatically get transitioned to drivers so all the references stay the same.