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:
2 Likes
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:
https://a.aliexpress.com/_mNGD0n6
Did you try use this one ?
2 Likes
Wow! Youâre a lifesaver I spent two days of researchibg and bothering everyone. Thanks alot it worked like a charm.
2 Likes
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:
- Routineâs name in SmartLighting. The name of the device involved.
- Access to your account:
- Go to the SmartThings Web (my.smartthings.com)
- Log in to your Samsung Account
- Select Menu (âŽ) and choose Settings
- Toggle on Account Data Access
- 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.
5 Likes
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).
2 Likes
@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
4 Likes
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
