I’m curious about your comment. I wasn’t aware anything was happening to location modes? What your saying sounds like we won’t be able to make more. If that’s the case, what sense does that make if they intend to still allow the use of location modes?
I think I’m more interested in a use case of more modes than night, day, home and away?
I created some additional modes to mimic how Hubitat does modes OOTB.
Away, Day, Evening, Night
Plus some extras “just in case” since the IDE is currently the only easy way to create additional ones.
at this time, IDE is the only avenue to create new Location modes. You can only edit existing ones in the app. When IDE goes so will that feature unless it gets added elsewhere such as the app, my.smartthings.com or other. ST has not provided any details on certain features in IDE to date and whether they will still be available.
Ahhh, I hadn’t even considered the only way to make modes was the IDE. It’s been forever since I did it and I have the 4 I need. I have to think they will incorporate the important things from IDE into this new system. Especially something like modes.
I think what he’s asking for is a central location to find all the Edge Drivers. Yeah, there’s a wiki with a Table of devices and links to drivers, but it’s not at all updated. Searching this forum helps a bit, but it’s tedious at best.
A simple LOUD AND CLEAR message to all devs and manufacturers to please post drivers under a special ST created Topic would have been great. Then, searching that topic for a device or manufacturer would have at least eliminated some frustration.
Just a thought.
I have “guest” mode, that pauses most of Routines related to Open/Closed doors, as guests (kids) can go in and out 100 of times. Also lights are not shutting down or dimming automatically, when guest are present.
We have something similar to others with the “guest” modes. Used when company is over for overnight or more. We also have a “party” mode where lights aren’t turned off, HVAC isn’t touched, etc.
think I’m more interested in a use case of more modes than night, day, home and away?
At our house we distinguish between “night“ and “asleep“. In night mode, the motion sensor in the bedroom turns on the overhead light. In asleep mode, it doesn’t turn on the overhead light, it turns on a nightlight on the wall instead.
But there are lots of variations. 
There’s a discussion thread in the forum from the past for how different people have used them. The discussion of Webcore obviously no longer applies, but the examples of the different use cases should still be interesting:
I just created 4 dummy modes in case I ever need them. It appears you are limited to 8 modes.
There isn’t a central location for the Edge drivers? Really ?!?!?!
If only they had YEARS to figure this out. Come on Samsung. This is a truly awful migration.
#NotReadyForPrimeTime
I woked Up this morning and everything ist offline. Restart the Hub doesn’t help. Oh my god
There is a central location for the WWST certified Edge drivers. They are automatically handled by the hub/app.
There is not a central location for Community Edge drivers. No different than DTH’s. Hubitat Inc doesn’t provide or support a central location for Community drivers either.
I still don’t get the fake outrage at Samsung for some of this stuff… Its as if people love to just try and create drama…
Personally, I’m looking forward the change. To finally have all devices and (most) automations run locally. I get there is some transition pain, but I believe it will be worth it.
This community has done amazing things to fill the gap, and it is fair to argue that that shouldn’t have been necessary, but SmartThings has already relied on community support for DTHs, WebCore etc.
I just wish they’d pull the trigger and make the switch so I can see what’s broken and fix it.
It seems that there was a big mistake. All my device was offline even they had Edge Drivers. The only Thing I can do ist to pair them again.
This is …
That is a good idea. I accomplish similar things with various routines or… well, I used to use webcore. I’m now experimenting with Sharptools.
I’m going to have to think about these uses. They might make things simpler after the loss of webcore
I can see basically using them as variables. I guess in my mind they were always just location modes. I like the idea of the guest mode and I’ve added a vacation mode and emergency mode.
We’ve unfortunately had a few ambulance visits and it would have been nice to activate a mode to turn on all the lights, unlock the door and suspend certain automations.
I really love this forum. Thanks all.
I second that. I didn’t bother waiting I’ve now moved everything and disconnected all IDE based apps.
Just waiting on the Smart Lighting and the Action Tiles and then I’m finished.
Would be really helpful to know when the migration is going to start so I can set aside some time to deal with any issues…
I’ve prepared as much as I can:
My hub updated to 0.45.9 yesterday so should be ready to go.
I’d update them manually but almost all of my Z-Wave and Zigbee devices are relays in connection boxes that I’d have to open up to press the button to pair again!
There is a central location for the WWST certified Edge drivers. They are automatically handled by the hub/app.
Good. I thought that was what the person was talking about. I thought that because their communication has been lousy, IMO.
There is not a central location for Community Edge drivers. No different than DTH’s. Hubitat Inc doesn’t provide or support a central location for Community drivers either.
I would have liked to see a marketplace that was community moderated by approved moderators but progress shmogress.
I am not outraged. I am disappointed. I think this change is a step backwards because their scripting is limited and has a weird/verbose syntax. Local automation is great and should’ve been done before. Hubitat does that and still uses Groovy. This means that WebCore works for that.
I am finding Node-RED on HASSIO to be very easy to use so I guess; thanks Samsung.