Patched webCoRE for Hubitat (2018/09/09)

Yup. warning to everyone....DO NOT UPDATE TO THIS VERSION!!!!!

My hub is now totally f'ed because I have tried to restore a backup which DOES NOT work well at all. Every smart app lost its authorization tokens.

Which version is working at the moment?

Here's the link to @nh.schottfam version.

Looking at @Ryan780 post above though. Is this the version he is referring to?

That is the version I am talking about. After loading that one I am not unable to load the orignal and unable to access any of my pistons. Doing a restore from a backup, I have discovered, is completely worthless for WebCoRE as you aren't able to access the dashboard at all because the token stored won't match whats in your browser. I am going to try and restore again and clear cookies and hopefully I'll be able to get back into webCoRE.

When I restored the prior version from a Hubitat backup, I was unable to access the dashboard until I gave it the code provided by the 'register a browser' button on the Hubitat WebCoRE app page. When you sign out of the dashboard (mine is run locally on an RPi uisng the same level of code that I had just restored Hubitat to), it will prompt for this code.

This whole excercise finally motivated me to do a backup of the SD card in my RPi. I don't want to re-create that thing if/when I update its dashboard code should something go wrong...

Are you manually updating your RPi or are you doing a 'github pull'?
If the later did you have to amend anything on the RPi as we are now using a different repository.
Thanks.

The problem is that I'm not being prompted for a code after doing a restore.

Could you try registering another instance or do you not get access to the menus.

Prior to this latest version update, I had updated the RPi by doing git pull from putnamjwp's repository. When I updated WC a few days ago, I neglected to update the code on the RPi (I was still able to use the dashboard in spite of the 'there is a later version' warning). I haven't tried the most recent WebCoRE update (and may pass because of the reports of issues) so haven't changed anything on my RPi yet (I just backed it up so I can revert if necessary if/when I do try to update it).

Can you get to the 'sign out' button (on the lower left of the dashboard screen)? I wasn't prompted for a code until I signed out of the dashboard and tried to access it again.

How can i sign out if the dashboard won't load? This is all i get:

image

Ah, so you're just getting the spinning circle. I had that issue too, temporarily. Have you tried rebooting your Hub? Note that I never did update my RPi code to the 'slimmed down' version; it remained at the same level of code that I had just restored to my Hubitat.

Why would that be the problem? The problem is definitely in my HE. This is the error I get:
2019-03-05 04:15:12.833 pm errorDashboard: Authentication failed due to an invalid token null

After clearing cookie, I can log in but my pistons don't show up and I get this error:

[app:9](http://192.168.1.12/logs#app9)2019-03-05 04:17:34.455 pm [error](http://192.168.1.12/installedapp/configure/9)groovy.lang.MissingMethodException: No signature of method: com.hubitat.hub.executor.AppExecutor.trace() is applicable for argument types: (org.codehaus.groovy.runtime.GStringImpl, null) values: [Dashboard: Generating new security token after a successful PIN authentication, ...] Possible solutions: wait(), any(), grep(), page(java.util.Map), page(java.util.Map, groovy.lang.Closure), each(groovy.lang.Closure) on line 2551 (api_intf_dashboard_load)

[app:9](http://192.168.1.12/logs#app9)2019-03-05 04:17:34.321 pm [error](http://192.168.1.12/installedapp/configure/9)Dashboard: Authentication failed due to an invalid token null

[app:9](http://192.168.1.12/logs#app9)2019-03-05 04:17:32.802 pm [error](http://192.168.1.12/installedapp/configure/9)Dashboard: Authentication failed due to an invalid token null

[app:9](http://192.168.1.12/logs#app9)2019-03-05 04:17:11.006 pm [error](http://192.168.1.12/installedapp/configure/9)groovy.lang.MissingMethodException: No signature of method: com.hubitat.hub.executor.AppExecutor.warn() is applicable for argument types: (org.codehaus.groovy.runtime.GStringImpl, null) values: [Updating webCoRE v0.3.108.20180906, null] Possible solutions: wait(), any(), wait(long), wait(long, int), now(), every() on line 2553 (updated)

[dev:1666](http://192.168.1.12/logs#dev1666)2019-03-05 04:16:50.933 pm [debug](http://192.168.1.12/device/edit/1666)descMap: [raw:catchall: 0104 0020 01 01 0040 00 9E81 01 00 0000 00 01 , profileId:0104, clusterId:0020, clusterInt:32, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E81, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:01, data:[]]

[app:9](http://192.168.1.12/logs#app9)2019-03-05 04:16:46.126 pm [error](http://192.168.1.12/installedapp/configure/9)groovy.lang.MissingMethodException: No signature of method: com.hubitat.hub.executor.AppExecutor.trace() is applicable for argument types: (org.codehaus.groovy.runtime.GStringImpl, null) values: [Dashboard: Generating new security token after a successful PIN authentication, ...] Possible solutions: wait(), any(), grep(), page(java.util.Map), page(java.util.Map, groovy.lang.Closure), each(groovy.lang.Closure) on line 2551 (api_intf_dashboard_load)

Basically, I'm screwed. I will have to delete webcore and rebuilt my pistons. That's the only option at this point

There are authentication errors in the logs; did you try signing out of the dashboard, getting a new token (as previously described)

Of course.

Not sure if this is any consolation, but if you do load a new instance when you do get back in and you define a new piston you may see the old instances pistons and be able to duplicate from the old instance. You will have to amend for the devices etc. but it may work.
Just thinking aloud.

How would I see the old instances pistons? They will disappear when i remove webcore. they're stored on the hub, not in the dashboard.

I know the pistons run locally on your hub but the pistons are known on the webCoRE server ( I believe). That is how I am able to duplicate one of your pistons if you give me the backup code. (Assuming you are not hosting webCoRE locally for new/amend/deleting).
I'm sure I've seen this. Maybe I'm wrong but its worth a look.