webCoRE for Hubitat Updates

an39511 · May 9, 2020, 1:23pm

I run webCoRE for 98% of all automatons. I am curious, does your automatons make heavy use of variables? For me I make http get calls to a LAN server running a weather station and populate about dozen variables, mostly numbers but some string. I also make a fair amount of math calculations with variables too,

I have rule machine loaded but not using it for anything. (Just uninstalled it yesterday as a test) The only other native app is for running the dashboard. All other native apps have been uninstalled or disabled.

I must reboot my hub every three days otherwise it noticeably starts slowing down on day four and slows to a crawl on day six.

The hub slowdowns are happening to a lot of people including those that have never installed webCoRE so I know it isn't the cause, but I am hypothesizing that maybe it is the repeated use of variable space that is filling up memory and gets purged when a reboot occurs. In other words, is it a problem in the groovy language itself that is the root cause.

mik3 · May 9, 2020, 1:37pm

Remove rule machine and dashboard all together.

I’d be interested to see your results.

If all is good, install dashboard and test. Then move on to rule machine.

TranDzung · May 12, 2020, 5:16pm

I register a browser ( Chrome, or IE ), and I got these Error :

I can create a new piston, editing ... all piston ran good. When done, I log out, then log in , still get the Error.
How to fix the Error " ... invalid token " ?
( v0.3..1009 HE: ...20200210_HE )
Thanks.

nh.schottfam · May 12, 2020, 6:08pm

in your webcore dashboard, you want to logout.

In your HE console -> apps -> webcore -> settings -> security -> "Clear all security Tokens"

and "done", or "next" your way out.

You can clear the cache of your browser, and the go back into the webcore Dashboard.

bobbles · May 12, 2020, 6:15pm

Personally I think it's global variables, RM4.0 or webCoRE, that causes issues.
I'm pretty sure there something about this on ST when I was using the ST hub but it was so long ago I cannot remember.

TranDzung · May 12, 2020, 8:05pm

Thanks. On this HE hub, no RM, no global variables. Only webCoRE and Hue integration apps, HubConnect .

bobbles · May 20, 2020, 4:22pm

I've just loaded the latest update, 2.2.0.129, and webCoRE is now trashed for me on both my hubs.
A restore to the previous backup is still failing. Will try the old firmware.
Thought I'd let you all now in case you experience the same.

bobbles · May 20, 2020, 4:27pm

Reverted to 2.2.0.128 and webCoRE is now working again. Oh dear!!!!!!

dioffo · May 20, 2020, 4:33pm

That's good to know, I was just about to do the firmware update

Royski · May 20, 2020, 4:34pm

Hmmm well that puts me off that version somewhat

an39511 · May 20, 2020, 5:36pm

CONFIRMED! 2.2.0.129 breaks webCoRE
When bringing up the webCoRE app through the IDE returns Unexpected error.
Logs show nothing about the problem.

nh.schottfam · May 20, 2020, 5:46pm

If anyone sees more logs, would be interested. I have not moved my hubs to .129 yet, but any logging might help understand what the issue is.

On the IDE unexpected error - is that the HE console -> Apps -> webCoRE ? or is it the webCoRE console?

an39511 · May 20, 2020, 5:59pm

Yes.
HE APPS webCoRE
Nothing was reported in the log.

When trying to load pistons through the webCoRE portal it reports that it is unable to load and when trying to edit a piston it just sits and spins.

Reverting back to 2.2.0.128 fixes the problem

bobbles · May 20, 2020, 6:04pm

@nh.schottfam
Also, when on .129, if you try and update the webCoRE app by doing an import of the code, when you save it gives this.
Again in the logs, no errors.

PS I have one hub at the latest build and one at the old build so can do any testing if you need it.

nh.schottfam · May 20, 2020, 6:17pm

thx for the data...not giving much to go on.

@chuck.schwer any thoughts on what changed?

bertabcd1234 · May 20, 2020, 6:19pm

Seems a little odd that there aren't even release notes or an announcement posted for 2.2.0.129. Think I'll stay on .128 until we hear something.

[EDIT: The notes linked to below were not there when I posted this. But .130 is out now with a fix, so yay!]

bravenel · May 20, 2020, 6:29pm

We will be releasing another hot fix to correct this problem.

bravenel · May 20, 2020, 6:36pm

bravenel · May 20, 2020, 6:45pm

This problem has been fixed in Release 2.2.0.130.

bobbles · May 20, 2020, 7:03pm

All fixed.
Thanks Bruce for great service once again.