It should be as long as the firmware is up to date.
How? Is there a guide on how to assign Edge drivers to my devices? I know my way around the IDE, changing DTHs etc. but no clue on how the new stuff works.
Sheez! I wouldn’t classify my pistons as complex but then that’s relative to how simple the Routines functionality is. It may be that even my not-so-complex pistons are a pain the butt to setup. I think I might just start picking a few of the simplest ones and try and create routines.
This should help.
ST app is showing my hub as being on firmware version 000.044.00009. I’ve never manually updated the firmware as I assumed it will keep itself up to date.
That’s fine, then. Anything 43.4 or higher on a V2 should have full Edge Driver support.
The hubs do update firmware automatically, but sometimes someone has had one put away in a drawer and is just now setting it up, maybe for testing.
As mentioned in the original announcement, September 30th marks the kickoff of the final stage of the Groovy sunset. Below are some updated milestones to help you plan for the transition. We will also share additional info very soon regarding the continued support for Virtual Devices.
· Start ST-managed DTH migration
· Start migration of SmartLighting and Weather SmartApps to new plug-in
· Update IDE to only allow updates or deletion of existing DTHs
· Disable the ability to add new SmartApps
· Remove the IDE debugging tools (Live Logging and IDE simulator)
· Start migration of 3rd party DTH’s to a ST-owned lua driver if they fingerprint match, if not will move to the Thing driver
· Shutdown custom Groovy DTHs
· Shutdown SmartApp execution
· Removal of SmartApps from catalog
· Graph IDE access will be limited to read-only
Q1 of 2023
· Complete 1st Party DTH migrations
· Shutdown Graph IDE
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?
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…
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.
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:
- When I started with it, people had regular issues with database corruption. That has gotten better but you still see people needing to restore backups and do soft resets. I’ve never once had to reset anything on my ST hub.
- The 700 series zwave radio in it for some reason tends to have more issues with ghosts than the 500 in ST.
- “Reboot often” was a thing for people. Thats gotten better and I dont think people are doing that as much anymore, but i’ve never had to reboot my ST hub.
- The antenna performance for both zwave and zigbee isn’t as nearly as good as ST in the same physical location. An aftermarket antenna mod helps with this greatly.
- The mobile app is not as friendly as ST. Its getting better and closer.
- The backend UI on mobile is nearly unusable for me. Not responsive at all.
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.