The End of Groovy Has Arrived

Yep. I’m betting they’ll announce another extension to the planned end of first party driver migrations. Churn in the beta firmware releases makes me think most of their attention is there rather than on driver migration.

I’ve got a dozen devices not yet migrated. Almost all of them are additional instances of make/models I have which were migrated before Christmas.

Me too, one of my first back in November I believe. Still has the old Rboy driver issue of every once in awhile it shows opening and is stuck like that until I open and close it.

Does someone here tried to contact smartthings support regarding a device not working properly after migration?

It’s been almost 2 weeks now and never heard back from them…

If you ask in the forum, other Community members may be able to help or offer advice. You will probably get it resolved quicker in the forum :slight_smile:

what device - brand/model? what Edge driver was it migrated to?

They are smart plug
1 from aeotec smart switch 6
1 is a generic brand

aotec was migrated to aoetec smart switch 6 (advanced options)
the other was migrated to z-wave switch

also tried to z-wave switch mc from mariano

nothing in the event, when I click to turn it on/off, it seem to do nothing and kind of timeout after I while
I used a driver named virtual momentary switch to test, it seem to turn on the device and turn it off after a couple of second. This driver is working for them, but it’s not what I want

Thanks

anyone got some tips for me ?

Just the standard advice for re-pairing a Zwave device:

  1. Do a zwave exclude from the device, then delete the device using the app
  2. Go into the SmartThings IDE, delete it from there if it still shows up
  3. If there is a custom DTH there, delete it.

There should now be no trace of the device in the SmartThings system

  1. Do a factory reset on the device
  2. Pair the device with the SmartThings app

Hopefully when you pair the device with the app it will pick up the correct stock driver

Any reason for this advice? “By brand” seems superior to “Scan for nearby devices” for zwave/zigbee. It lets you turn on discovery for just one radio without also triggering the discovery function of any LAN drivers.

4 days to go and about 35 devices left. Wonder if they will stick with the revised, revised, revised date and just pull the plug on the 31st. April fool’s!

It might be a revised, revised, revised date but it was still announced on 21st September last year, in the broadest of terms (Q1 of 2023), ten days before the nominal start date of the whole process. As the device I am waiting for hasn’t been ported yet they certainly won’t literally make the deadline but I don’t think they will be all that far off the spirit of it.

I really don’t care if they hit the deadline. My stuff is all working, and as long as it is, they can take their time.

perhaps they will provide an update on April 1st :wink:

I’m at 97 devices left. One light transitioned over as a switch in the last month or so using an existing Edge driver. But as others pointed out, functioning vs the timeline is most important.

February 12 was the last time I had any devices transition. I still have the same 8 devices left that I am still hoping will auto transition:

6 - NuTone NWD500Z Smart Z-Wave Enabled Wall Dimmer Switch
1 - Zigbee Switch, Inle Smart Light Switch
1 - Enbrighten Z-Wave Plus Smart Outdoor Switch, 1-Outlet Plug-In (2nd Gen.)

These are just a rebranded Nortek/Linear/GoControl WD500Z, so that one is probably just a fingerprint issue.

This is a summary of what I still have on DTHs.

Device Count
Hue 60
Sonos 17
Switch ZW 10
Motion 9
Switch ZB 7
Fan 6
Minimote 6
Wemo 5
Contact ZW 4
Harmony 4
Life360 2
Tilt 1
Energy Meter 1
Weather 1
Leak 1
Presence 1
Relay ZW 1
Grand Total 136

So, half of my remaining list will get taken care of when the Hues and Sonos are moved over.

I actually use the community Hue Edge driver for all Hue Rooms, Zones and devices except lights (and boy it is good). I have a feeling whatever ST come up with in their Hue support will be inferior so we’ll see where I go there. But, the number of automations I have with Hue devices is deterring me from regenerating new light devices in the community driver.

My four Harmony devices in the list are Harmony hub devices from the old Harmony integration. I can delete those having moved fully to the community Harmony Edge driver (another well executed and feature-rich driver).

(Yes, I know I need to find a replacement for the Life360 stuff …)

I guess this isn’t surprising. Sort of funny that there is a start date, but no end date… I’ll be curious to see how fast this new process happens, given that most of my devices have yet to transition.

Another 37 devices just added to the migration list ST groovy to edge migration list

ST has a dedicated Edge driver for Hue in the beta channel. But TBH it looks about the same functionality as Matter would provide…if SmartThings actually supported Matter bridges.