Will SmartLighting be converted to Routines/Rules or will it be a separate app/driver? If Routines, what happens if the conversion pushes you past the 200 limit?
What Weather SmartApps? Is it still just the Severe Weather Alerts or will the smart weather tile be included?
This is going to become an issue for all those who just use Smartthings as something that happens quietly in the background and are not interested enough in the mechanics to visit here regularly.
The email sent out is short notice and vague and maybe people will grasp the implications of so few smartapps being migrated - but few can be expected to understand the linked Platform Transition FAQ page.
Itâs easy enough to create a routine with trigger conditions but itâs just impossible - and not a lack of familiarity - to do what I need to replace the smartapp - select a preset with Sonos speaker control as one example.
There doesnt seem to be any clear process by which we can get things like that implemented.
Time has been spent implementing niche features like trigger conditions for current humidity or current Hue colour temp etc and not making sure all - not some but all - existing Smartthings provided smartapps features are retained.
This is a classic example of ST using terminology that has never been revealed to the end users. My guess is that a ânew plug-inâ might mean something similar to the Routines/Scenes creators but who knows.
What @JDRoberts said⌠You have to follow the guide. You will need to subscribe for the Beta program and enroll in their (Smartthings) Channel, then browse around the Community to try other Edge drivers created by the developers here (and there are some brilliant drivers already that I am using). (Youâll have to enroll to the developersâ channels as well). But yes - youâll need to do some reading before all that, regrettably.
Agree, start from a few simple ones. The others will require some thinking, and might require thinking, nut as I said most stuff is doable at the expense of numerous routines.
I was told it will be a separate smartapp that uses Rules API as the backend.
I have one like this, literally (somewhere). Should I fire it up and get it running just to update the firmware?
Which one of these will move 3rd party DTH to 3rd party Edge lua driver?
I think the latter, frankly, but who am I to say? 
Just my best guessâŚ
Hey @SmartThings
Could someone illuminate us on whether this app will still have geographic restrictions, despite its being re-written afresh?
Havenât been here in a while⌠but have been watching this from a far for quite some time. I have been a ST user since around 2015, and IMHO it has always been poorly/incompletely documented and supported. If it wasnât for this community (and I have contributed here a lot) I would not have been able to create the smart home I currently avail myself of. Back then it was worth the extra effort as there was little else comparable. But that is no longer the case.
And now, it is obvious that Samsung has no issue with taking an eraser to the years of work we have all put into the SmartThings platform. And quite frankly, my disrespect to the original SmartThings staff is almost second to none⌠with number one being my experience with a handful of other pretty top line Samsung products over the years that has compelled me to feel that they donât give an âEfâ about their customers.
After digesting the majority of this thread, I am a bit surprised (maybe even flabbergasted) that any of you wish to continue investing another dime of your money, or ten minutes of your time to this debacle of a platform⌠especially considering the alternatives such as Hubitat or open source software.
As soon as any DTH or SmartApp I have created and care about stops working, I am gone⌠pointing my middle finger to both the original crowd-sourced company staff, and of course Samsung.
YMMV⌠but I recommend you keep in mind how the folks here that have worked hard to ensure the success of this platform have been treated when making your decision to continue or abandon this platform.
Best 'o luck on that decision.
-SiP
There was a semi documented point where older firmware wouldnât update (had to be version XXX or later) but they have seemly worked past that as I just recently updated a V2 hub that had never been powered up and it updated to the latest. It took over an hour and went thru ~10 intermediate updates to get there, but it finally did.
But it canât hurt to put it online to update just in case. And it may come in handy to do testing.
Iâm choosing to stay to see how it shakes out and for the most part my environment should be fine (but Im not webcore or heavy on smart apps). I use Hubitat as well and its a good platform but its not perfect either. Not a fan boy, just saying change happens and sometimes the pain is too much, sometimes its worth going along for the ride. At least its not Insteon or Wink.
May I ask what (if anything) is less than perfect about it than SmartThings?
LOL⌠my X10 stuff still works, along with a decades old HW interface/app that lets me communicate to my HA server and SmartThings via AppleScript calls. Sadly, I think that communication to SmartThings will be ending soon.
Just my experience with the C7:
All that being said its a good platform and the forum over there is filled with people who can help and provide support. Lots and lots of pros with it too.
I have to say, I am incredibly disappointed in this. I spent a lot of time tweaking Smartthings and getting SmartApps and Device Handlers for retail products that I purchased as they work with ST and also a few custom integration type things. Now with this change, my smarthome will essentially be broken. Fortunately, I have a few home servers and have fired up HomeAssistant on one of them and am starting to learn it. Between the unreliability of this platform (âSomethings not quite rightâ), the changes being made with little regard to customers setups, investment in products, near non-existent customer service, etc, I am abandoning Samsung entirely. Weâve bought their phones, tvs, appliances, mini-splits, etc for sometime just to keep things in the same ecosystem but its just not worth it. It doesnât matter what product line you choose, the customer service is scripted and awful. I remember a year ago there was in issues with Honeywell and Smartthings not working for a few days. I contacted both and both kept pointing the finger at the other. LOL In the end it was Honeywell but Samsung didnât even try to help or make contact with Honeywell. Anyway⌠I have lost all respect for this platform and its constant changes from classic which was a nightmare to migrate from and I do not seeing this much better. With the amount of smart home products I have, I am not going to run around like an idiot readding them all and trying to figure out how to make it all work yet again.
There may be a way to play a favorite via a simple POST command to the SmartThings REST API, but thatâs one command I havenât exposed yet. I got several commands working in the limited time Iâve spent tinkering with it, but not that one ⌠yet.
Some years ago, I started running node.js on Raspberry Pi and installed jishiâs code to control my household Sonos system. Itâs still running today and remains my go-to as it has all the advanced capabilities (and more) that I could want for controlling my system. Plus, the Pi being a always-on local device, a playlist can be invoked via a group preset or to a single device by making a simple one-line request like this:
http://localhost:5005/living room/favorite/myplaylist
These and other requests can easily be included in Routines and Scenes in SmartThings (but not SharpTools, which does not have local access) using a Edge Driver like this one.
That was a very specific case related to old V1 hubs. At some point ST changed the way the hub is informed where to pickup its firmware (in preparation for the new infrastructure if im not mistaken) that required a firmware update to tell devices where to pickup the new firmware and then later sending down firmware from the new location before decommissioning the OLD location - But by that time the V1 hub had been unsupported for quite some time so there was literally no way to tell the hub where to pickup the new firmware location, let alone the firmware itself. Manual intervention would be required on a hub that had already been more than a year out of support and multiple years from its last firmware update.
That said, I put my v2 online every couple months now⌠Just in case. Iâm due to do it again this weekend in fact.
Customer support needs guidance. A few weeks ago. I was installing a new device and it had issues. I was told to uninstall edge drivers because they are beta and go back to groovy. WTF. That is not even possible as far as i know once a device installs with an edge driver you cannot go back to groovy. I was told to reach out to the community forum for help.
Someone needs training or just admit there will be no support for anyone and the customer is on their own.
At the present time, before they turn groovy off, a custom groovy DTH will take precedence over a production edge driver.
So to go back, you would have to:
Two) remove any custom edge Driver for that device
Three) add a custom groovy DTH for that device
Four) re-add the device.
It should pick up the Groovy DTH that time.
And, yes, that means you have to re-create any rules, routines, and automations that were using that device. So annoying, but possible.
The purpose here is no doubt to avoid the likely significant cost of freely hosting DTH and SmartApps on Amazon Web Services. I, for one, would have gladly paid a reasonably monthly fee to maintain the ability. I do think these changes are going to be good in the long run but wonder if weâll lose some functionality and capability.