I dunno… I’ve got some doozies over here… LOL
My maximum “chunks” have steadily dropped lower over the years…
(What used to be 24, is now more like 17 or 18)
Which means some old pistons are now too large to edit & save.
The pattern I am seeing is:
The more code stored in webCoRE, the smaller size each piston can be.
I finally received more errors does this help
28b20c58-c01b-45c0-9ea8-de9b0ed60a74 12:07:52 PM: error Dashboard: Authentication failed due to an invalid token
28b20c58-c01b-45c0-9ea8-de9b0ed60a74 12:07:49 PM: error Dashboard: Authentication failed due to an invalid token
28b20c58-c01b-45c0-9ea8-de9b0ed60a74 12:04:47 PM: error Dashboard: Authentication failed due to an invalid token
28b20c58-c01b-45c0-9ea8-de9b0ed60a74 12:03:57 PM: error Dashboard: Authentication failed due to an invalid token
28b20c58-c01b-45c0-9ea8-de9b0ed60a74 12:02:41 PM: error Dashboard: Authentication failed due to an invalid token
nope i will wait. “At your own risk” scares the crap out of me. Did not have access to that topic anyways
You’re not alone with this issue. I’m having the same thing happen here. iPhone, iPad on Safari browser and Windows 10 PC on Chrome and FireFox.
There is an update in testing that lets you reset the token that this may be referencing. @jkp shared the link but that is a private category. If you want to give it a try you can update just the webCoRE app code without updating anything that runs your pistons.
If you have the dashboard working on any computer, try to download a backup of your pistons. The file downloaded from Backup Pistons is a lot easier to restore from than individual backup codes.
In the SmartThings mobile app you should see a new option at webCoRE > Settings > Security > Reset access token. Please read the warnings on that screen; if you use the External URL for any pistons those links will become invalid immediately. Otherwise you just have to sign back in to the dashboard. You can see the changes to webcore.groovy here.
Sorry for the late response, none of the @mentions emailed me. This is dealing with the access token issue only, no idea if the original issues are related.
Before I reset it, because warnings always scare me, it seems that I am not the only one having this issue. See @lflorack comments above. But if you say that this is my issue I will reset it.
This is a long thread with what seem to be unprecedented issues. The code posted above is a possible solution to the latest error, but perhaps the others are related.
Also @Mckenph, @lflorack, @smartie, which SmartThings shard are you on (the domain you get redirected to after signing in at account.smartthings.com)? I’m on graph.api.smartthings.com
I am seeing a number of pistons fail to load this evening, but failing with a 500 status code rather than 401 so not necessarily related. If this does end up hitting my account I’ll gladly hack away on it since my automation is all non-essential.
I am on Shard NA01: https://graph.api.smartthings.com/
I’m getting this error too - or just a spinning symbol with nothing loading:
and of course, I’ve beeen unable to load any pistons for the past hour or more and as soon as I turn on ST (IDE) logging to answer your question, it all starts to work (temporarily I’m sure) and I get no errors. I’ll keep watching.
On EU shard, having a hard time opening pistons, I get the “There was a problem loading…” Some pistons just won’t load, tells me to go home, but I’m already at my house?!
08:45:26: error physicalgraph.api.StatusCodeException: Invalid http status code returned: 401 @line 5054 (initIncidents)
08:45:21: error physicalgraph.api.StatusCodeException: Invalid http status code returned: 401 @line 950 (api_get_base_result)
08:44:11: error physicalgraph.api.StatusCodeException: Invalid http status code returned: 401 @line 950 (api_get_base_result)I’m also from EU and having exactly the same issues. Few of my pistons having serious delay issues (10-15 seconds) as well.
Does anyone want to try the token reset instructions posted earlier? This is now clearly a widespread issue, but it would be helpful if one person can check whether it helps to generate a new token for accessing SmartThings that would be informative.
You can add me to the list in the US.
NA02.
It seemed to get better last night and was fine this morning, but now I can only load about half my pistons.
[edit] Now it all seems to be working again.
Can somebody braver than me try @ipaterson’s suggestion above please and report back. I’m too scared to.
I’ll try the webCoRE update shortly and report back. For right now, I’m confirmig the ST Log (IDE) error that others have reported:
More context here: when you install webCoRE, ST generates a token that allows communicating with your specific smart apps. The token has a far future expiration date, something like 50 years, so normally you don’t need to refresh it but some people may choose to do so as a security measure. Some people have had account issues that required refreshing the token.
When you generate a new token, any browsers or apps that were logged in to the webCoRE dashboard have that old token and will no longer have access to your account until you re-authorize the browser for webCoRE. The token is also included in the external links for triggering a piston from a third party system, so any external links will become invalid when the token is reset. Otherwise, this does not have any effect on your pistons, GitHub integration, or other ST settings.
Thanks for following up everyone, I’m still monitoring my own account for these issues.
