[OBSOLETE] FAQ: [ST Edge] Edge D-day - how will "Things" move across?

Do we know what the maximum limits are?

As of this date:

You are limited to a total of 200 devices (per location), 200 local automations, and 50 edge drivers (per hub).

There was a recent discussion in the following thread:

What do I need to do to get ready for Sept 30?


with all of these virtual device and routines to sync states workarounds, you’d think SmartThings could at the very least create a something that does the same thing but more like a smartapp, instead of recommending this janky solution

1 Like

@JDRoberts hey there. I have a device that i have deleted and added many times but keep getting it as a “thing” between removing and adding i installed many drivers which i think was supposed to match. Im not sure if I’m doing something wrong while installing drivers or if I’m choosing the wrong driver. Any idea?

It’s a zemismart tuya zigbee curtain (the new one that comes without the wall switch)
AliExpress link:

Did you try use this one ?



Wow! You’re a lifesaver I spent two days of researchibg and bothering everyone. Thanks alot it worked like a charm.


Are the devices with the new Edge drivers available to be used in the groovy apps?

I had the first ones button with temps convert over for me, and as it was part of a groovy thermostat, it caused my thermostat to stop working. I removed that device from the thermostat, and it started working again.

Same here, two ST buttons and the Z-wave repeater side of two Iris smart plugs are the first devices I’ve seen automatically migrate, sometime in the 2-3 days since I last checked.

My Groovy Smart Lighting routines that use those two buttons seem to be broken - I get a “We’re having trouble connecting” error when I try to edit the routines. Fortunately they’re simple to recreate but not a good sign (CC @nayelyz )

SmartLighting routines that use the Iris plugs look to be intact, but they use the Zigbee plug part of the device, not the Z-wave repeater, so I wouldn’t expect them to be impacted.

1 Like

Yes, thanks for the details Mark, same ST buttons, exact same error when submitting edits.

1 Like

Hi, @Rick_VB
Is the “Groovy thermostat” a custom Groovy SmartApp? I want to see if it’s possible to check which elements of the device were being used.

When this happens, it’s hard for the team to track down the issue if you delete and recreate the elements.
I can report the issue to see if there’s something they can I need the following info:

  1. Routine’s name in SmartLighting. The name of the device involved.
  2. Access to your account:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (⋮) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

Sending a PM with details. I haven’t deleted or recreated the problem routines.

I sent an email in as well.

Has anybody come up with a virtual thermostat yet that I can wire up relatively simply yet with a temp sensor and a switch/on-off plug? I’m starting to get worried, as winter is coming and I have three of these that I depend on…

Could you use Mariano’s virtual thermostat tied to a sensor (ZigBee sensor version here: (EDGE Driver-Mc): Zigbee Temp Sensor and Child Thermostat Mc, Zigbee Temp Sensor with Thermostat Mc), and then create routines to tie the actions of the virtual thermostat to turn on and off a plug?

He has a zwave sensor version of the same driver if needed.

1 Like

Next devices that have moved: Sonoff / EweLink motion sensors. Associated Smart Lighting routines still exist and can be edited; I’ll check tonight whether they’re functioning normally.


Is it possible to force Switch to EDGE driver from a Custom DTH without repairing?

Not today, and it doesn’t seem like that’s going to be added. Automigration by Samsung only, or exclude/include (zwave) or delete and re-pair (Zigbee).


@Rick_VB, if you haven’t already dived into @Mariano_Colmenarejo’s Zigbee or Z-Wave temp sensor and thermostat edge drivers, I suggest you do.

I was hesitant at first, not wanting to have a multi-piece solution (thermostat device, routine to turn on switch, routine to turn off switch) to replace a single-piece solution that I had in the old groovy virtual thermostat smartapp.

Working with @Mariano_Colmenarejo to test the Z-Wave virtual thermostat has softened my stance. Building and maintaining (in my case) the 2 SharpTools Rules is suboptimal but OK, knowing that it’s a limitation of the edge architecture that disallows the virtual thermostat device from controlling the switch device directly.

Maybe someone someday will figure out how to use a bridge service/server on the LAN to bounce a command from one edge device on the hub to another edge device on the hub.

@BartschLabs isn’t Sharptools becoming obsolete with tbr closure of Groovy?

No, SharpTools is already up and running on the new SmartThings architecture



I’m sure you have some reason that I don’t know, but I don’t understand why you have to use sharp Tools to control a switch with the operating state capability of the thermostat.

I have done it with two very simple routines and with local execution

1- If Thermostat Operating status is heating then Switch Boiler ON

2- If Thermostat Operating status is Pending heat or Thermostat Mode is "Off " then Switch Boiler OFF