The End of Groovy Has Arrived

@orangebucket See jkp’s response above. ST acknowledged Scenes run in the cloud and it is their plan to make them local, eventually.

I quit using scenes. Instead I created a virtual switch (with vDev Controller) and a routine to perform the needed tasks like turn devices on, off, dim etc. The last line of the routine turns off the virtual switch with a 5 sec delay. Turning on the switch can be done using the App, a button or by Alexa.


That was a year ago.

I coincidentally came across this thread yesterday - there was a beta for local scene execution but it looks like it may have stalled out.

I who am not a programmer, wonder why it is not possible to directly use all the devices locally through the app, if they allow it. I have shelly devices, which is true, they are in wifi, but the app itself, if used in the same wifi network as shelly, allows you to turn devices on and off locally. This would be great if it could be done.

1 Like

It’s just a question of design. For example, the exact same Meross smart plug will work totally locally with Apple HomeKit (including app control), but requires an active internet connection to work with SmartThings.

Even after Matter deployment, SmartThings still requires an active internet connection for app control.

They didn’t have to design it that way, but they did, and so now it’s a SmartThings requirement.

Maybe some day, especially if Matter takes off, this will change, you never know. :thinking:

1 Like

An Edge driver can be written to talk to local devices. The manufacturer of the device will need to build the new driver, if they want to play with Smartthings locally. Might SmartThings write some drivers with this capability? It’s possible but unlikely.

Yes, but the question was about the app, and the SmartThings app currently always requires an active Internet connection to the smartthings cloud in order to talk to the hub, even if both the hub and the phone are on the same Wi-Fi network. You can see that in the upper right corner of the official schematic I posted.

Again, they didn’t have to design it that way, but they did.

Also, my guess is that almost all device manufacturers would choose to do a Matter integration before doing anything that was smartthings – specific. It’s just a better use of their resources. And a matter integration would give you local operation of the device whether you have a hub or not. But it still wouldn’t change the fact that the SmartThings app needs the cloud.

1 Like

I’m not going to get into an argument about the SmartThings architecture. I bought it years ago and the improvements are greatly appreciated.

If you wish to use SmartThings and want all local, then utilize a button device to initiate scenes or automations.

Our primary interface used to be buttons. Today, it is primarily Alexa, which is cloud based anyway. I use the app for configuration and not day to day operation.


Good point, but scenes currently require the cloud as well.

There are definitely simple automations that can run locally when triggered by a button press, and that may be all that many people need. :sunglasses:


I was really disappointed when I learned Zwave was effectively being deprecated from ST’s newer hubs. While I may not fully understand all of the technical or political pros/cons, I’ve yet to change a single battery in ANY of my Zwave sensors in 4 YEARS!! (They’re also placed at much further distances from my router with far more physical barriers.) Contrast that with the 2-3x annual battery replacements I’ve had to perform with my functionally equivalent Zigbee sensors which mostly sit within spitting distance of my hub. :face_with_raised_eyebrow: My zigbee devices also seem to cause occasional ‘hiccups’ (congestion/interference) with my WiFi; not so much with the Zwave ones.

I know Zwave isn’t perfect by any means, but I think there are still some very strong use cases for it. Switching to a v3+ hub would’ve meant dumping tons of devices, replacing them with thread/zigbee equivalents, and potentially winding up with less performant WiFi and even more battery replacements. No thank you! :rofl: Not a fan of planned obsolescence, especially when it’s arguably regressionary.

I’m glad ST didn’t deprecate the v2 HUB and that we basically achieve (better than) v3 feature parity by simply adding a thread border router onto our network. Easy peasy. ¯_(ツ)_/¯


You got the Quirky Tripper working? I been off here for a year or so. Now i’m confused on whats going on. lol. all i want is my Quirky Tripper to work again.

Looks like @Mariano_Colmenarejo added the fingerprint to his driver.


I have several devices that still have not changed over to Edge drivers, including a Kwikset lock (Smart Code 910). I am reluctant to remove the device because I don’t want to lose functionality if it won’t re-add. Any help would be appreciated.

1 Like

For your peace of mind … you may want to go ahead and rip the bandage off. Exclude the lock and add it back. Of course, you may need to recreate any Routines that it was associated with. If there are issues, community members will always assist.

OR wait until ST migrates it when you least expect it. Nothing will go wrong… right? :wink:


If you do delete and add it back, create a virtual device to use as a placeholder in your routines which you can delete when you add your locks back to the routine. This way the routine won’t get deleted when you delete the lock.


I have Kwikset locks but there all Zigbee and they work perfectly with Mariano’s Zigbee Lock MC. I have heard the Zwave Kwikset locks work with Philh30’s Zwave Lock driver but I don’t have any Zwave units so no way for me to say for sure. I would find the fingerprints for your lock first and then check the appropriate driver yml file to make sure your fingerprints are included.

I got it changed over! Thanks for all the help! It was a Z-wave lock and everything works but there are no additional features/options when I look at the device in ST.

I have read that the Philh30 Zwave driver has extra functions. @h0ckeysk8er knows a little more than I do about this.

1 Like

There doesn’t seem to be a separate profile for Kwikset locks, but for Schlage you get quite a few more settings. Additionally, his beta version exposes unlockCodeName in the device panel and in Routines as a trigger.

  Capability                                  Attribute               Value          
 platinummassive43262.schlageInteriorButton  interiorButton          "enable"       
 platinummassive43262.keypadBeep             keypadBeep              "beep"         
 platinummassive43262.autoLock               autoLock                "off"          
 platinummassive43262.schlageLockAlarm       alarmMode               "off"          
 platinummassive43262.schlageLockAlarm       activitySensitivity     3              
 platinummassive43262.schlageLockAlarm       forcedEntrySensitivity  3              
 platinummassive43262.schlageLockAlarm       tamperSensitivity       3              
 platemusic11009.deviceNetworkId             deviceNetworkId         "[71]"         
 platinummassive43262.lockAndLeave           lockAndLeave            "lockandleave" 
 platinummassive43262.vacationMode           vacationMode            "off"          
1 Like