WebCoRE and migrating from Classic to the new ST app


#1

ST is currently in the process of migrating users from the Classic to the new SmartThings app.

If you opt to use the ST migration tool and have the following in your pistons:

  • call Routines
  • set SHM status such as disarmed, armed/stay and armed/away

You will need to edit any pistons that contain those because they will no longer work after you run the migration tool.

Routines are converted to automations/scenes in the new app and the ability to use routines in the Classic app will cease.
SHM and SHM custom rules will be converted to STHM and automations/scenes in the new app. SHM will cease to function.


Anyone else having issues with webcore after the migration?
#2

Thanks for the heads up! As always, your proactive posts are invaluable!

My classic V2 hub and webCore apps still rocks! I have dual HE hubs (C5/C7) as a fall back, so waiting to make the final decision for 2020 primary house controller…

My moto is, ‘When it isn’t broken, I tend to not fix it’… So, when I am forced to migrate, I’ll turn the key!


#3

I understand we can no longer set SHM status, but can Webcore still read it?

I have a few pistons that tun lights on and off when we’re on vacation (Armed mode).


#4

Once you run the migration tool, the status is set to disarmed in IDE and no longer can be changed from the Classic app. While the SHM window remains available in the Classic app —> selecting any of the options (Disarmed, armed/away, armed/stay) has no effect. Also the ability to view or edit SHM custom rules is removed.

So webcore is only going to see a state of disarmed.

Note: the migration tools asks that you set the state to disarmed before running.


#5

So I’m thinking to use my vacation lighting routines I probably need to make a virtual switch that enables or disables them.

That kinda sucks. :confused: I’ll have to see if I can use a built in lighting automation to toggle that virtual switch or such.

[EDIT] Apparently the built in lighting automations can’t see STHM status either. :confused:


#6

The date has been set for sunsetting the Classic app —> October 14, 2020


#7

I appreciate the update, although I think you can understand why I did not heart your post, LOL


#8

So, once migrated to the new app, and the Classic app shuts down, how do you go into WebCoRe app to do things like adding devices? Is that available in the New App?


#9

yes it is in the new app. click on menu (3 bars in the upper left of the screen)
choose Smartapps and locate your instance of webcore.

to add an instance, on the dashboard, click on + in the upper right of the screen and choose smartapp, then webcore

Please note: when adding devices, the done button appears on the first screen then next and next but then you will see Cancel, Cancel, Discard. Yes, it is a bug but the devices you select are saved even though you selected Cancel, Cancel, Discard. go figure!


#10

I have been getting the very recent emails about the ST platform changes coming soon. The EchoSpeaks notification is crazy short and ST should have done something proactive about the resource usage before now. It’s obviously an in demand feature we were looking for.

What is going to happen with WebCoRE ?

Am I missing the thread that is announcing or talking about the move to WebCoRE v2 ?

Thanks


#11

There is a thread on the forum discussing this topic. Basically, it is unknown at this time until ST completes their new rules API.

WebCoRE is based on groovy which is set to be retired at some point in 2021.


#12

We need to recruit @WCmore to edit the two locations for installing webCoRE in the wiki to reflect how to install and configure from the new app and remove all references to the Classic app.

How was that for one long sentence :slight_smile:

By two locations - there are two separate sections with the same installation instructions


#13

Installing webCoRE

  1. Open the SmartThings app on your mobile device.
  2. From the Home screen, you have two options from where to add a new instance of webCoRE… touch the Plus (+) icon and select Smartapp or Select Menu ( Menu icon ) and touch SmartApps and touch the Plus (+) icon
  3. Scroll down to the Custom section until you find webCoRE and tap it. If you can’t find webCore you likely skipped some steps above.
  4. Do not tap webCoRE Dashboard, webCoRE Piston or webCoRE Storage.
  5. Tap Next.
  6. On this screen you can …
    • set the name for your webCoRE instance to anything you desire,
    • scroll down and Choose a security password for your webCoRE dashboard
    • choose how often the dashboard login expires
  7. Tap Next.
  8. Scroll through the list and select all of the devices you want webCoRE to have access to. If you do not do this, you will not be able to use those devices in webCoRE. This must also be done again when adding new devices to your SmartThings Account (see adding new or additional devices below). webCoRE will not automatically import them.
  9. Tap Next.
  10. Tap Done.

Adding New or additional Devices to your Instance of webCoRE

  1. Select Menu ( Menu icon ) and touch SmartApps.
  2. Scroll down and tap the name of the webCoRE instance you are trying to access. This is typically webCoRE, unless you edited the name during the installation process.
  3. Select Settings
  4. Tap Available Devices
  5. Tap Available Devices
  6. There are two sections;
    • Select devices by type: Which actuators and Which sensors
    • Select devices by capability: Capability group 1-3

If you don’t find your devices in the first section, be sure to go through group 1-3 in section 2

Note: there is a display bug when exiting after you select your devices. Click Done, Next and Next again but then you will encounter Cancel, Cancel and Discard. Don’t worry - your devices you selected are saved.

Opening the new dashboard from your phone

  1. From within the SmartThings app,
  2. Select Menu ( Menu icon ) and touch SmartApps.
    Scroll down and tap the name of the webCoRE instance you are trying to access. This is typically webCoRE, unless you edited the name during the installation process.
  3. Tap Dashboard.
  4. You will be prompted to enter the security password, the same password you created when you installed webCoRE.

Using webCoRE from another browser

You cannot bookmark the URL you launched from the SmartThing app. In order to use webCoRE on another device you must follow these instructions.

  1. Select Menu (Menu icon) and touch SmartApps.
  2. Scroll down and tap the name of the webCoRE instance you are trying to access. This is typically webCoRE, unless you edited the name during the installation process.
  3. Tap Register a browser , a page will appear providing you with a registration code. The code expires in 3 minutes and can only be used once.
  4. On your other device, open the browser and visit dashboard.webcore.co
  5. Enter the code and click Register .
  6. You will be prompted to enter the security password, the same password you created when you installed webCoRE.

#14

Give me a few hours, and I will add your last post to the wiki.
(in all four places, LOL)


Edit:

Well, maybe I will make a new page, and simply link to the new page from all four locations.


#15

I’ll try this post instead of creating a new one. Where does webCoRE stand as far as being able to control and receive data about scenes and STHM?


#16

It can not do either directly but you can use virtual devices in between.

For myself, I use webcore to manage presence —> location mode of Home and away. And I use automations to manage STHM state of armed/away, armed/stay and disarmed.

But I have seen others on the ST forum using virtual devices between 3rd party apps like ActionTiles and webcore.


#17

A new page in the Wiki has been created to help people with the new ST app.

Thanks @jkp for taking the time to write this up!
(and please, let me know of any errors or additions, and I will update the page again)


Note: The only change I made to your original text was to the Registration Link.


#18

Semi-related (I’ll start a new thread if that’s recommended, but…) as I’ve been migrating to the new app I’ve also been migrating from my 2.0 hub to the 3.0 hub (which I already had as part of the Smartthings WiFi hubs).

So, what I need to do is migrate some of my WC pistons from the old location (old hub) to the new location (new hub) and I’m having a really hard time doing that. Whenever I try to do it with “restore” and input the backup code, I get an error message. And I can’t figure out a way to cut and paste (if there even is one).

I’d prefer not to start 100% from scratch with my Pistons, but will do so if I have to. Any tips would be very welcome. Thanks in advance!


#19

Have you tried ‘create a duplicate’ and then select the piston from the old instance to import to the new instance?


#20

I recently tried to log in to webCoRE through my app after migrating. I have had webCoRE running great for over two years and recently tried to login and it fails everywhere (mobile, desktop browser, etc.). I added a screenshot of the issue. I have tried logging in and out. It seems that the pistons still run as my devices have changed their state since I’ve noticed this issue. I cannot manage them (CRUD operations) from the page. Note this only happened AFTER the migration.