After migrating I have lots of things that no longer work.
For axample i have an old core piston that has a restrictions to only run when in mode (armed stay) that will no longer run.
Dose core and are webcore nolonger see modes?
I know it canât see STHM status but I thought modes should still worked!
There are two different kinds of modes: location modes and security modes. STHM (The feature in the new V3 app which is similar to the old SHM) uses security modes. But the STHM security modes are not exposed to Webcore or Core.
People are using to workarounds for this.
if you only use the default location modes, you may be able to just make the security mode mirrored the location modes. But that generally doesnât work for people who have custom location modes.
alternatively, you can create a virtual switch for each security mode and turn it on and off as STHM changes the security mode. Then you can trigger your piston off of the virtual switch.
Itâs annoying, but it works.
Thanks for replying @JDRoberts
I am using the location mode and not the security mode/status.
I have just been looking at some Webcore pistons and Webcore does seem to still be working with Location Modes.
But apparently the original Core is no longer seeing location modes.
The question is, is it worth rewriting all my old core pistons in Webcore are is webcore just going to be killed soon too?
Webcore has a tail. A long one.
First the IDE already has a declared life of about a year.
Second, Ady has already stated he has plans to upgrade WebCoRE to use the RulesAPI when RulesAPI supports variables.
CoRE has been unsupported for over a year.
So yes. Uograde yiur pistons.
Iâm getting a bit confused here because âarmed stayâ isnât one of the default location modes, it is an SHM alarm system status.
I migrated Friday and finally got my things âmostlyâ working again today on Sunday.
So I have around 130~ devices. Mostly a mix of GE Zwave wall switches, Ecolink Zwave tilt and contact sensors, a few iris contact sensors a water cop Zwave valve and then a bunch of SmartThings branded zigbee devices, including water, outlet and multipurpose sensors. I also have a modified contact sensor as smoke with a kiddie relay as well as a bunch of âcloudâ devices including those from alarmserver, ring, honeywell and myq.
All of my physical devices migrated as well as automations using those devices.
However, I make use of alarmserver - envisalink- DSC to get my alarm and itâs sensors into SmartThings as well as Lock Manager and thatâs where things went south immediately.
I purposely remove lock manager prior to the migration because I wanted to try out the new SmartThings lock solution.
Finally gave up and manually deleted all of the DSC devices that come in from alarmserver via IDE, then reran alarmserver to get them recreated - they then showed up in the new app and I was able to recreate my automations that use the devices
Support = 0, me = 1
Stupid decisions.
SmartThings devs = -3
Fortunately Lock Manager still works for now though it all has to still be managed via the old app.
Come on Devs!!! You call this a production ready release ???
What a joke.
People keep mentioning things like this. The migration does nothing to those devices, or other SmartApps. Before the migration they would have worked in both apps and after the migration they would continue to work in both apps.
Blockquote
As I mentioned, my PHYSICAL devices were fine. However, my CLOUD devices were hosed. I understand that they were not SUPPOSED to be screwed, but they were in fact SCREWED.
Iâve deleted EchoSpeaks and Alexa. Installed the New Alexa App after deleting everything in the old App. Actually went pretty smooth. Had to rename a couple of things but all in all, wasnât that bad.
As of now, I am going through all of my virtual switches created by a couple of Apps and recreating those in the IDE to be Simulated Switches. Tedious process but making it through.
The timeline given, IMHO, has been enough to make needed transitions. Hate I have to go through all of this but hopefully, the future will be promising.
Good note, Alexa is much faster now!
Bad note, this process would have been impossible without knowing which Apps were tied to which Devices. ST needs to FIX THIS ISSUE ASAP!
It may not be a âdefault modeâ, I had probably created it years ago for only god knows why!
Thatâs the biggest problem I am having with this whole mess is trying to remember what did what and why.
Fair enough. I sometimes wonder if the ability to control SHM from third party apps has ultimately caused more harm than good.
Its not just the risk of things breaking, its also the fact that there will be NO support whatsoever to help you out afterwards.
I have made the switch 2-3 weeks ago, and have YET to receive any form of support. Either I am being ignored (from within the app), or the Samsung Support doesnt know what to do (âbecause we are sperated from smartthingsâ).
Its a nightmare.
Support has thrown in the towel⌠Iâve had a ticket open for 2 months, just to have a smartapp removed that was inaccessible.
Iâve lot count of how many times they asked me to reinstall the new app 
Hi all,
Following up on my questions. Anyone has managed to combine an NA location with an EU location in the same account in the new smartthings app ?? Appreciate help or any hint
Thx!
Fab
If youâre in the Asia Pacific region, there have been multiple problems. They were listed on the status page.
New incident in Americas now on the status page
Same here. Smartapps wonât even load for me and it shows I donât have any installed.
Thread started
