C5 -> C8 migration and webCoRE

I purchased the new C8 hub and plan to upgrade tomorrow -- but I have been running the "User" version of webCoRE on my C5, and wanted to know if there are any steps I should do ahead of time (or after restore on the C8) to also migrate to the built-in webCoRE.

Do I just need to:

  • backup my pistons
  • (remove the "User" webCoRE?)
  • install the built-in webCoRE
  • restore pistons?
    Or is there some other process I might want to do instead?

Thanks!

1 Like

Ensure prior to the upgrade you are up to date with webCoRE

HPM repair if needed.

After webCoRE updates, wait at least 10 mins as if the webCoRE version changed, it will do a few internal cleanups a few mins after the update.

During the HE migration, you take a backup on old hub, so now you can take that backup - when you restore on new hub, you will have all the webCoRE and pistons there.

You should logout of the webCoRE IDE, as on the new hub, there will a new hub UID/URLs for the IDE that will be picked on when you login again when the new hub is up.

Any external access to webCoRE pistons will change the URL if you are using those.

If you have to re-pair any devices (zigbee for example), do ensure you replace them so they keep the identifiers clean.

You should not have to backup / restore all you pistons separately (you can if you wish, but you don't have to go this route).

So explain it to me like I am 5 because I still cant get webcore to carry over and work.

On my C7 I make sure firmware and webcore are current. (Also make sure C8 is on same firmware) I open up webcore in my C7 when I can create new pistons edit pause ect... and select log out.

Then I backup for migration, Restore on C8 and when I try and open webcore app it just keep going around in circles, the app never opens?

What am I doing wrong?

Did you logout of the webCoRE IDE as stated in note 2?

In general I would

  • politely reboot your hub

  • wait 5 mins

  • ensure you logout of the webCoRE IDE

  • then go ahead and register your browser.

I would check that you are up to date for either user install or built-in install

it should be dated March 2, 2023

So I redid everything again,
Logged out of IDE before migration backup? Yes,
Made sure everything was up to date, hubitat and webcore? Yes
Rebooted hub, waited 10 mins, recreated migration backup.
Shut down C7

Booted C8, Made sure it was also up to date, restored from new migration backup, waited 10 mins, webcore would not open to register new browser, just got the waiting wheel like it was trying to load. Rebooted hub waited 10 mins still gave me waiting wheel.

Had to leave for a few hours and by the time I got home it was working. SO my guess is 10min was not long enough. But all is working now. Thanks for the help. and hope this helps others. Just wait longer. :slight_smile:

1 Like

I also had the same issue (of being unable to access my pistons) immediately after the update. It seems that a lot is going on shortly after migration, and it takes a while before the piston can be accessed. Having once lost all my pistons with Smartthings, I still suffer from that trauma and panic when something like this happens. Fortunately, all is good now.
I have another problem after the migrations, which I have been unable to resolve - the weather reports use the wrong location (reports the current temperature as -2C, whilst it is currently 33C.
I've deleted and re-entered the Hubitat location settings; re-entered the OpenWeatherMap API in the webCoRE app; temporarily changed the weather provider in the webCoRE app to something else; returned to OpenWeatherMap as provider; re-entered a new API key for the latter; restarted the hub numerous times. Nothing seems to help.
What else can I try, or what have I been missing?
Thanks

In private message, would want to see the webCoRE main settings

HE console -> apps -> webCoRE -> gear icon

and the webCoRE Storage settings (where weather data is gathered/stored)

HE Console -> apps -> webCoRE storage -> gear icon

So this turned out to be the setting was for $weather to be in Celsius.

Easy fix, adjust the setting to what is desired.

2 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.