How Migrate to Internal Webcore from User-Installed Webcore

[tonyk1322]

The user-snstalled Webcore has not been updated in a while. I understand the internal Webcore is more actively maintained, so I want to move to that version, along with all my settings, devices, variables, and pistons, as painlessly as possible. How can I do that?

[chrisbvt]

Outside of backing up all your pistons, and then restoring them to the new instance, I don't know of any way. Global variables do not get backed-up and they would have to be recreated.

It would be similar to when I moved Webcore from SmartThings to Hubitat. I restored all my pistons from backup, and recreated by global variables from screenshots I took beforehand.

The nice thing is that your device ID's are the same, unlike when I moved from SmartThings and I had to figure out what new device needed to be replaced in all the pistons, even though I had all my logic.

[terminal3]

I thought I remembered one of the developers saying there would be a tool or documented procedure posted to give a clear path to moving from the user installed to the internal. but it never seemed to materlize.

[Hatallica]

I have not yet been motivated to switch. Below are notes that I captured in mid-2024, for consideration only.

Summary

ADVANCED CONSIDERATIONS
• webCoRE global variable recreation (possibly categories also)
○ Evaluate which ones should be:
§ Deleted
§ Revised
§ Converted to HE global
• Aligning account identifier across multiple instances?
○ Consider logging out of each dashboard instance
• Anecdotal recommendations
○ Copy global variables into a text file
○ Validate built-in app before deleting user version
○ Apply a distinct name to the built-in app during setup
○ Built-in app install - add the same devices as the user version
○ Add global variables with correct variable type
○ Pistons
§ Open a dashboard for User and Built-in versions
§ Pause in User version
§ Built-in Version
□ Resume
□ Edit/Save to engage triggers
□ Update category
□ Allow back-up

MIGRATION
1. Backup
a. From dashboard IDE
i. Backup Piston(s) - select all piston to migrate
ii. Password - not needed
2. Restore
a. From dashboard IDE
i. New Piston --> Import a piston from a backup file
ii. Select the backup file (password if used)
iii. Dialog box displays pistons and warnings
1) Maintain "safest" sorting
iv. Import and view
1) Adjust piston name or category if needed
2) Resume now or later
v. Continue Import until complete

[tray_e]

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

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.

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…

The second link appears to state that you can run them both side by side. Might be worthwhile (if you want to transition) to install the built in and gradually move things over until the external is empty.

I did mine back when it first came out. I only had a few pistons for edge cases that RM couldn't handle. So, for me it was fairly easy to do in one shot.

[DGBQ]

@john022662k

Hello All,

I was having issues with HPM completing the Update of Webcore (specifically... it would time-out upgrading the Webcore Piston App). This has been happening for about a year and I was always able to get it to complete on the 2nd or 3rd try. I tried all the tricks of rebooting the the hub, using repair of App within HPM, etc.

I decided to take the leap and switch to the Built-In version.

This works well but it does take alot of time and steps to get it right and functioning. Below is a summary of advice to do this using the steps discussed above.

• Don't delete your User version of WebCore until this process is complete and confirmed to be working.
• I copied all of my Global Variables for the Dashboard using simple copy and paste into a text editor. They will come over all as one long string. I just inserted a return between the semi colon and the @ so that I could have essentially a list of all the Global Variables.
• When setting up the Built -n Webcore App, be sure to give the App a simple same difference. I called mine WebCore Built-In
• During the app install, be sure to add all of the devices that you use in all of your User Webcore App. I honestly just added them all with exception of the special devices that are not listed in Actuators, Sensors, or Devices. For the special devices, I only had about 10, so I just made sure those were selected as well.
• Once the app is installed and it's time to add Pistons, the first step should be to add all of your Global Variables. You will just need the string portion after the @ symbol which is the name of the variable. The app will place the @symbol at the start of the string. Obviously, you will need to select the correct type of Variable. It is very important to get the Global Variables input exactly as they are used in your piston or you will have to track down the differences later.
• As stated above, when restoring the Pistons into the New App, it will need to be done Piston by Piston. They will come in "Paused". For me, I added all the pistons one by one and completed the next steps below.
• I had two windows of the Dashboard open in my browser. One was from the User Version of Webcore, and the other from the Built-in version.
• Piston by Piston, I paused the piston in the User Version, Resumed the piston in the Built-In Version, edited the Built-In Version, and then saved again. The Edit and Save was just to get the App to recognize the Triggers.
• I did this for all 81 of my Pistons until complete. During the process, I was placing each Piston into the correct user category and allowing the Back-Up feature.

Total time was about 4 hours but worked perfectly.

Hope this helps.

John

This step-by-step guide looks really helpful. I’ve been holding off too — mostly waiting for that mythical “free afternoon” (or two) to appear so I can make the move. My biggest push to switch to the Hubitat webCoRE version? The external instance’s HPM timeout issue, which I still wrestle with today, meaning I’m stuck doing updates manually… every single time. Okay, stepping off my soapbox now. Let us know how it goes!

[nh.schottfam]

to be clear, there is no requirement to make this change.

You can if you wish, the two versions are generally in sync, or the user installed one may be ahead.

[tonyk1322]

Maybe wrongly, but I thought the internal Webcore was more up-to-date. I can stay with the user version if that makes sense. I currently have:

• @Field static final String sVER='v0.3.114.20220203'
  @Field static final String sHVER='v0.3.114.20240115_HE'
  @Field static final String sHVERSTR='v0.3.114.20240115_HE - September 19, 2025'

[nh.schottfam]

That is the last pushed update. In general webCoRE has been very stable, and there have not been lot of platform changes that required it to be changed.

You can see the running versions by going to:

HE console -> apps -> top level webcore instance

You will see some of those strings in the console