Migrate Webcore from "User" to newly built-in app?

[accd2793e8934ca914d6]

So happy to see Webcore becoming an official built in app. Former Smartthings user here, and love Webcore. What's the migration path from the "User" webcore app to the forthcoming built-in app? Will all pistons automagically migrate or will there be a manual process?

[jsarcone]

I would like to understand the Web for migration from the add on/user app to the Built-in app as well. I have many rules and I would like to make sure that they will be ported over correctly.

[cznkane]

Came here looking for this answer as well, same situation here.

[eibyer]

Bobby's reply on the topic.

webCoRE for Hubitat Updates

Will be seamless transition from user installed app to system app, without user interaction.

[bravenel]

Actually, that's not true (what Bobby wrote). You will need to load pistons into the built-in app once you get it...

[bobbyD]

@jsarcone

would like to understand the Web for migration from the add on/user app to the Built-in app as well. I have many rules and I would like to make sure that they will be ported over correctly

If you have the webCoRE running already, there is no advantage to transition to the built-in app. The seamless migration I mentioned before, didn't make sense to be implemented, as it could create more problems for existing users.

The upcoming built-in app is for new users who don't already have webCoRE running on Hubitat Elevation. It will allow them to get pistons imported from other platforms or create new pistons effortlessly.

[dnickel]

That answers me previous post but...
Where to the updates come from? The built-in app would be from the Hubitat build (I assume) but will we be updating via HPM/nh.shottfam code as usual?

[bravenel]

@dnickel

will we be updating via HPM/nh.shottfam code as usual?

If you convert to the built-in app, you can reload your pistons into it, and be done with the user version. The whole point being that the updates will be automatic in a hub update, and you won't need to deal with webCoRE updates with HPM separately going forward.

[accd2793e8934ca914d6]

Will device IDs or whatever under the covers ID remain the same....so if I import my pistons to the built-in Webcore that it will re-associate all my devices properly (for a seamless restore)?

[jsarcone]

Thanks for the update. Happy Holidays and new year.

[nh.schottfam]

webCoRE built-in on Hubitat - Do I need to transition and how?

As many have heard announcement, Hubitat is building webCoRE into their image. I will use this wiki to update folks on integration status and options they have. Current update: January 3, 2023 What does this mean? For new installs, installing from the built in version is much easier. (If installing a new instance this is recommended) you select HE Console -> apps -> "Add Built-in App" and scroll down to webCoRE the app will automatically update as Hubibat releases new image…

[jsarcone]

@bobbyD

@bobbyD

For those who are already running webCoRE on Hubitat Elevation, they may consider migrating to the built-in version to take advantage of automated updates that will continue to be released when necessary, along with the regular platform updates.

I'm a little confused about this statement.

1. Should we migrate to the built-in application?
2. If yes, how do we do this?
3. What are the differences, advantages and disadvantages between the two deployments?

Sorry for all the questions.
Thanks!

[bobbyD]

@jsarcone

differences, advantages and disadvantages between the two deployments?

No differences now, or going forward. Advantage is that updates to source code will come automatically with the platform releases. The process of switching from user to built in is the same as the process of coming from other platforms to Hubitat (backup pistons, install built-in, load backup).

[jsarcone]

Thanks for the clarification.

[DubbyDad]

Will we still be required to enter our hub-specific "Authenticate" password when launching the built-in version of WebCoRE, as we currently must for the user version?

If not, that change alone would convince me to switch over.

[nh.schottfam]

you do need to authenticate (typically once) when you connect the webCoRE ide.