Over the past few months I keep seeing there is an update for Webcore and each time it fails. This time I tried to import the webcore driver by importing it directly.
It appears based on the detail below the code is the issue not HPM
Looks like your manual import is trying to add a app to Drivers Code instead of Apps Code. And if you're updating it, it should already be there (and you can re-import) rather than adding a new.
If you want to troubleshoot HPM, I'd start by checking Logs for errors (or sharing it here) and making sure that HPM itself and your hub platform software are both up to date.
Thank you, I just ran HPM again, it failed with this message
I then tried to import into the App not theDriver
This process ran for ages with the spinning wheel and then simply timed out after around 3 minutes
Now when I try to view a piston I see this
I hope that's helpful data,
Paul
I would check Logs as suggested, not the app UI. It is a large app that may take some time to install, but on recent platform versions, I think HPM (and manual) still works.
The error in webCoRE itself is probably something else unless maybe your app code is very old. The code will either install or not; if it errors out, there's no "partial" state where it can get stuck causing an error (at least for any single app). Trying a different browser, clearing cache, and other common steps for troubleshooting that kind of problem may help.
It's a long standing problem with the size of WebCoRE vs the Hub's timeout. Said another way, the upload+compile time exceeds the timeout. BUT the timeout is in the Hub code, not HPM.
That's very very simplified and someone with better search skills than me can find that discussion, I'm sure 
1 Like
Thank you for your time.
I changed over to the WC Built in version to mitigate against this issue.
In my opinion it was worth doing.
The built in version is updated to the latest should any changes occur but you will only get the updates on a hub build update. As WC is pretty stable now there are not many updates coming through any more.
Might be worth considering.
1 Like
I mainly use simple automation rules and notice I appear to have two Webcore in the app section neither of which I can open.
You might want to simply restore a recent backup of the hub, so that you can at least open the webCoRE pistons. Just an option in case you hadn’t already considered this.
3 Likes
For the update problem, It may be memory size / free on your hub (as others have mentioned).
You might disable temporarily some applications, or services (matter, or hub mesh), reboot to stabilize / update webcore, then re-enable the apps / services.
A C8-pro has much more memory - fyi. You will notice some new HE features are only available on C8-pro due to memory needs.
Thank you, I have to say I have never experienced any performance issues, I am mainly monitoring Temp and humidity and operating lights with around 49 devices. Good thought though, thank you. Hopefully I will be moving before Christmas and the latest Hub is on the shopping list for the new place.
