Is webcore down no piston access [401 HTTP status codes]

[smartie]

Having the same issues. Everything stopped working. It appears ST pushes an update today.

[ipaterson]

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.

[ipaterson]

Having the same issues.

Which specific errors in ST live logging are the same?

[smartie]

Looks like it is working now.

[ipaterson]

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.

[lflorack]

…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 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.

[Alwas]

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)

[Ervin]

I’m also from EU and having exactly the same issues. Few of my pistons having serious delay issues (10-15 seconds) as well.

[ipaterson]

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.

Is webcore down no piston access [401 HTTP status codes]

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. Sign in at account.smartthings.com Go to My SmartApps Edit webCoRE Replace the code with the new version which allows resetting the tokens Click Save at the top of the editor and Publish > For me If you have the dashboard working on…

[Terminal]

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.

[Alwas]

Can somebody braver than me try @ipaterson’s suggestion above please and report back. I’m too scared to.

[lflorack]

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.

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:

[ipaterson]

Does anyone want to try the token reset instructions posted earlier?

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.

[ipaterson]

Does anyone want to try the token reset instructions posted earlier?

No longer necessary. I was able to get the 401 error consistently on my scrap instance of webCoRE and resetting the token had no effect. Time to reach out to SmartThings; status page currently showing no issues.

[ipaterson]

It seems like ST is having some internal issues with incidents. If you need access to the dashboard and pistons before this is resolved on their end, stay tuned for code tweaks. It is unclear whether this is isolated to incident lookup, but the issue is anecdotally resolved on my end when incident lookup is skipped.

[kevinsunny]

Issues here with EU aswell. Can’t open pistons.
Sorry, an error occurred while retrieving the piston data.

[lflorack]

Maybe related to the issues at ST, maybe not - ignore as needed:

Although less than I’ve seen for the past three weeks or so, I’m still getting quite a few of these in my piston logs:

"Error while executing physical command [my_device_name].refresh([]): java.lang.reflect.UndeclaredThrowableException"

@ipaterson Thanks for your continued efforts on this.

[ipaterson]

It seems like ST is having some internal issues with incidents. If you need access to the dashboard and pistons before this is resolved on their end, stay tuned for code tweaks. It is unclear whether this is isolated to incident lookup, but the issue is anecdotally resolved on my end when incident lookup is skipped.

The temporary code patch is now available, see all changes here. Copy and paste in place of the corresponding smart app, then save and publish changes.

While active, this code patch will eliminate any incident tracking in webCoRE since the incident lookup is what seems to be failing. Only install if you are aware of this limitation and will revert the changes once the problem is resolved.

If your piston uses $incidents or $shmTripped directly those values will report null regardless of current incidents. The patch also logs a warning as a reminder to revert once the problem is resolved.

webCoRE SmartApp
webCoRE Piston SmartApp

[Terminal]

Thanks @ipaterson, I will wait a little while and see if things get fixed on their end. I don’t really need to modify anything right now.

Most of my pistons seems to be working but I have seen some things things that were delayed or did not complete. So this not only effects editing but operations as well?

[ipaterson]

So this not only effects editing but operations as well?

This could affect any pistons that use incidents, such as with $incidents or $shmTripped. It is not clear whether any other operations would be affected.