The End of Groovy Has Arrived

[nayelyz (SmartThings Developer Support)]

@949BFN

Only devices showing the “device type” as “Placeholder” in the IDE, have been updated to the edge drivers

If you’re in the beta group, you can verify the list on this announcement to check which devices have been migrated.
Also, if your devices joined with a stock DTH by default (this doesn’t include when you select a specific stock DTH to control the device in the IDE), they will be migrated.

@949BFN

The only way to manually / force an update to the Edge driver is to exclude and re-include devices. (I.e. climbing into the attic; getting on ladders to get to switches; moving furniture around, opening walls etc.) And if the device requires a custom driver, one has to find a new custom Edge driver before being able to re-include the device

This is in case you want to move to Edge now, but the team mentioned that if you have a device working with a custom DTH and you install a custom driver (eg. from a Community member) to control it, it will be migrated.

The End of Groovy Has Arrived

If your Zigbee or Z-Wave device is currently backed by a Custom DTH (not published in the ST repo) and you have a replacement community Edge Driver on your hub, ST will migrate those devices for you to the installed community driver (What is highlighted in Option 4 from the FAQs). Please note this will not work for Lan devices. Also, because we don’t know the entirety of the custom DTH was and what it’s replacement driver is, we cannot guarantee the expirence will be exactly the same (as we haven’t reviewed the code of either and it isn’t in our repo). When in this situation, I recommend to please check the name of your preferences between the Customer DTH and the Non SmartThings owned Driver. If they are not the same, preferences will not migrate. I don’t know the previous communicat…

Please, take a look at the FAQ page - Will there be an impact on my current connected devices?

@949BFN

IDE will eventually also disappear and the only way one will be able to manage device/device settings, will be via the Apple or Android apps.

There are other options:

• Using the CLI

• Using API clients like Postman to make direct queries to the API.
  

  
  
  Note: For this option, you’ll need a Personal Access Token to use in the authorization tab

• my.smartthings.com page (Beta phase)

@949BFN

we really in a position where we must wait until the last moment to see if Samsung will migrate devices to the new drivers? If we wait too long, we’ll end up with lots of devices and automations not working.

The ones you need to look further are those using custom DTHs which you mentioned are 35. For them, you need to check what actually changed because sometimes they were a little different from the stock ones, this way, you could take the official driver and apply the required modifications and install it yourself. (We can help you with any questions you may have)
Also, there are Community members that have published custom drivers and you can kindly ask them to add your device’s fingerprint (and install them) which will help in the migration-

@949BFN

I fear that once Groovy is gone, webCore will not be accessible at all?

WebCore is a third-party app, its web page access isn’t handled by ST. So, it should be available.
The Rules API can be used to migrate that automation, the team continues improving this tool based on devs’ comments.
Also, if you need help “translating” the automation from WebCore to Rules, we can help you out. You just need to create a post in “Developer Programs” and tag us @nayelyz or @andresg

@949BFN

Once a device is using an Edge driver, will it be necessary to remove and add the device to change the native Edge driver for the device, to a custom edge drive should one become available?

No, in the app, there’s an option to change which driver controls the device. However, for a driver to appear on that page, it needs to have:

• The device’s fingerprint or
• A generic fingerprint that makes it compatible with the device