The End of Groovy Has Arrived

Same. Nothing migrated and I haven’t installed anything in 3 or 4 months. Hub is V2, 45.9 firmware, no beta, no community drivers, all cleaned up and waiting…

I was wondering the same thing. I saw one thing that migrated several weeks ago (before the supposed date), but nothing since then.

After the migrations of Groovy device DTHs, what the third-party equipment needs to do, and how to do?

During the migrations of Groovy device DTHs, What the third-party equipment needs to do

Wanted to ask a question that was asked by someone above: Is there a ball-park consensus among the community on how many devices/drivers one can install before hitting the new memory wall? I just factory reset my v3 hub due to it being full and rebooting randomly. Now I’m getting the “almost full” message and I’m at 90/15. Also I’m curious if custom edge drivers like virtual device creators eat up more memory. One can wish that there’s some sort of “memory manager” in our future.

I have 54 devices listed (includes phones) and 30 Edge drivers installed.

No memory issues yet.

Is the any instruction or if someone can help with it. how to migrate DTH to edge? I used for for long time, gouldner “RG Linear GD00Z Garage Door Opener - V2” and i really dont like how working existing one Z-WAVE GARAGE DOOR OPENER (and stock one not been migrated to edge yet).
Thank you

Just rec’d my first two Edge drivers (what a mess).

I noticed my two GE Link deck lights stopped working. Checked the IDE and saw “Placeholder” in the driver column. Deleted the devices using the ST App… reset the devices… and did a scan for new devices in the App… NOTHING. Repeated all of the above and still nothing.

Checked the IDE again and devices were still listed, and “Online”. Deleted the devices from the IDE, then did another scan from the app and they were found and connected and are now functional.

Glad the ID still exists as I would have been screwed without it.

Does that mean devices that were automatically migrated rather than being removed / re-added by you? I just looked over my list and nothing’s changed so far that I haven’t changed myself.

Yes. But it seems that migration broke their operation, and prevented me from successfully deleting the devices from the ST app. In order to re-pair them to the hub I needed to use the IDE to delete them.

Just curious did they reconnect and function on a new edge driver? Or did they fall back to their original DTH.

I have 45 of 73 devices that are migrated, most of which I did myself. Some of these are virtual devices. Like another community member the devices migrated are ST Motion and Leak sensors. I also had a few smart plugs migrate and a First Alert Smoke & CO Alarm. What has not migrated are ST Plugs my ST Multipurpose sensors using the SmartSense DTH, EnerWave relay and child devices, a Ultraloq Zwave Deadbolt, several Sylvania Smart Plugs, Sengled Smart Plugs, Bhyve B-Byve Sprinkler controller and a GoControl Dry Contact switch that I am using as a momentary switch to activate my garage door opener. I am enrolled in the ST Beta Channel and I have accepted several other channel invites as well to enroll many of my 45 devices.

AFAICT they’re on new Edge drivers.

I got the full message on a New hub with 15 items and a hand full of edge drivers. I am now thinking that message is just random.

I am running HA in Oracle Virtual Box on a PC that is on 24/7. I will be getting Nabu Casa (NC) to handle the outside access needed for SmartThings since ST won’t communicate inside my network :confused: . I could roll my own but it’s not much and NC supports the project. Maybe I will jump through the hoops to do the Nabu Casa stuff at some point. I am keeping ST for now because I do like some simple stuff but using it for complex tasks (websites/IF…Then) is not what Samsung cares about now.

Yeah I’m gonna give St another go for a while maybe even look at giving my own drivers a go.

I think Nabu is expensive tbf but it’s a simple solution that also resolves the Google voice integration out. HA is more of a project. I’ll be very interested in what smartapps can be made in the new system.

I also have a Konnected system which gave me the added completion of tunneling that communication inside the network whilst being able to secure the outside.

Hubitat is the unknown for me but £140 for that isn’t on the cards right now!

Hi, @Marcin_K! This is normal as it is a work in progress, have you verified your devices are using a stock DTH?
On this page, there’s info about what happens for devices depending on their current handler:

@abcd, please, also check the link above. As I understand, “third-party equipment” means devices that aren’t certified as Works With SmartThings, right?
You can find a replacement, there are some Community members that have created drivers for Zigbee, Z-Wave devices and help people to add their device’s fingerprints. You can find some in this category:
https://community.smartthings.com/tag/edge-device

And, you can also download the ones from SmartThings and modify them to support your devices. For this, you can take a look at the Developer’s documentation: Get Started with SmartThings Edge | Developer Documentation | SmartThings

When this happens, you can reach out to us so we can collect information about this issue and see what caused it and help you solve it. When you delete the device, we cannot get its ID of when it was migrated to look at the logs.
Also, if you already deleted a device from the app but cannot add it again, you can check the ST API and delete it from there.
The ST CLI is a tool to help you interact with it but you can also make direct REST requests to it. There are some mobile apps that can help you or PC software like Postman.

@nayelyz do you have any information on when custom DTHs will be migrated to edge drivers. I believe those are my only devices that have not been migrated yet. Thanks!

Hi, @Terri_Baker!
I think this is the date set for option 4 mentioned on the Platform transition page (Replacement with custom Lua Edge Driver from ST Community) but let me double-check.