I got my C8 this morning. I followed the process and got the new hub updated and the cloud backup from my C7 up and running. Everything is working well, except web core. I look at the community posts and see one that says you have to update your old hub to the newest firmware before migrating. Well, I already did the migration, and now I can't get web core to work.
Update: I hooked up my c7 and have updated it to the newest firmware, and now it won't backup to the cloud, so that I can start the process over again.
What are my solutions?
I would suggest removing your other 2 or more posts about this same issue to consolidate your replies in one place (or this one, whatever you think is best).
Worst case, you can back up your pistons from the old "location" in the webCoRE IDE, treat the new hub as a new one, and restore them, and as long as you've authorized all the same devices in the parent app, things should fall back into place. But I think others have had luck with just hitting "Done" in the parent app to update the cloud URLs on the webCoRE side.
If that doesn't help, providing more details about your problems may be helpful. For example, anything in Logs while these problems are happening? And what do you see on your side?
1 Like
I would not try to start the migration over.
I would ensure webcore is up to date on your C8
then wait 10 mins, and politely reboot the C8.
The latest software update from yesterday morning didn't fix it?
I couldn't get into my webcore. It would just spin saying loading and there were a lot of error log entries when I would try.
I don't know if it was dumb luck or what but after the latest update (.103) it just started working on it's own.
FWIW I'm using the community version of the app.
Also if you don't have any other cloud stuff, make sure the hub is using the correct DNS. From the network tools page, do the ping but specify yahoo.com or something like that so it has to resolve it. For some reason my hub was using the wrong DNS server and none of my cloud stuff worked at first.
I hooked up my c7 to try and update that to the new firmware, and restart, but for some reason it wouldn't update. So, I backed up the web core database, and then deleted web core from my c8, and restored it. Everything seems to be there and shows correct. But some pistons don't seem to be working completely.
I am going to trouble shoot them over the next few days. Thanks for the tip on backing up all of web core. I had no idea I could do that.
Hi All... I tried to Migrate to the C8 Hub and followed instruction explicitly. Everything seemed to work OK on the C8 with exception of WebCore. I have been using WebCore with Hubitat for at least 2 years. I also use Hubutat Package Manager to keep WebCore updated and have not done anything to use the "Built In" WebCore. Maybe that is the problem except I know I'm using the latest WebCore version. I also made sure to update my C7 before the Migration.
I have Shutdown the C8 and Rebooted the C7 and all is working.
Can someone possibly help me with how to get moved to the C8 and be able to get WebCore to function,
When I try to go into the WebCore APP from the Hubitat C8 UI, I get the spinning wheel after I click on the WebCore app. I've allowed this to continue to Spin for 30 minutes and nothing happened.
I went into the WebCore Dashboard site and it shows some details of not being able to load the current database and does not show the name of my hub while I'm trying to use the C8. Just switching back to the C7 solves all of this.
Thanks in Advance.
Some people have reported that using the DNS Override in Network Setup to set the option to the default servers listed resolved their issues.
Right for Webcore, using 8.8.8.8, 8.8.4.4, 1.1.1.1, 1.0.0.1, 9.9.9.9 as DNS override in Settings make Webcore works for me. But my zigbee network still not work 
Thanks @thebearmay .... I don't have any idea what that is. Can you give some more information or instructions on how to do that?
Settings
Network Setup
Override DNS Settings
8.8.8.8, 8.8.4.4, 1.1.1.1, 1.0.0.1, 9.9.9.9
Thanks @jbilodea.... should I do the Network Setup on the C7, then Save a Back-Up, then try the C8 Migration again..... or do I put the setting in when I have migrated to the C8
Thanks @aaiyar and @jbilodea The DNS Override worked great for WebCore. I did run into another issue with Actiontiles not working properly and I use that as my main interface through my home. So....I went back to the C7. However, now I have a method to get WebCore to migrate to the C8 once I figure out this Actiontiles issue.
Thanks Again
2 Likes
Did not seem to work for me. Is being an Xfinity customer has anything to do with that?
I suggest logout of webcore ide
I hope you got this resolved by now. For anyone else with this issue, I just upgraded to C8 and also struggled with Webcore. I have over 70 pistons, and I didn't look forward to restoring them, along with all of my global variables. I checked the log and saw that Webcore was getting hung up on the first piston. I think it was overloading. This is how I got it to finally work, after trying everything else that was suggested.
- In Apps, tick the disable box for all of the Webcore pistons.
- Reboot Hubitat.
- Using Hubitat Package Manager, run repair on Webcore. (I rebooted again just because.)
- Open the Webcore App. No spinning wheel this time!
- Through the app, open the Webcore Dashboard. It opened, and all of my pistons were there but disabled. That's good.
- Close the Dashboard.
- Enable the pistons in Hubitat, a few at a time.
- Reopen the Dashboard to check it's still working.
- Close the Dashboard.
- Repeat enabling and checking a handful of pistons at a time until all of the pistons have been reactivated.
2 Likes
I migrated C7 to C8 this morning. Had the Webcore problem. I did the Override DNS. It did not work. I started down @user1143 's fix above. Step #3 failed as Package Manager still cannot update webcore. But after it failed, I logged out of Webcore and opened a new dashboard and all seems to be working well now.
1 Like
Yes, I started running into the Webcore update issue, as well. Probably because Hubitat is offering it as a standard app now. I bit the bullet and installed the standard Webcore app. I gradually migrated my pistons over. I also recreated my global variables as hub variables in Hubitat settings, since this was the 2nd time I had to recreate them. This way, they will stay in place. Some of them didn't have the same variable type options in Hubitat settings. I found I could apply the type in Webcore, though, once they were created. I have everything migrated and working now, and I finally got up the nerve to delete the PM version.
1 Like
Well, I spoke too soon. None of my Zigbee devices worked after migration. I followed the migration instructions to the letter. The Zigbee devices did migrate but would not function or communicate. I did the migration again. Same result. I am in the process of adding back all 39 Zigbee devices. They seem to add easily and fall right back into place with my automations (THANKFULLY).
Just migrated (C7 --> C8 Pro) and thankfully saved a link to this thread. After the Spinning Wheel of Death, I followed this and was running as expected within 15 minutes. Much thanks.
1 Like
