I’m getting the same thing. SmartThings status page shows all green for me. Hmm…
Thankfully I only logged out of my dashboard and logged back in, but the error persists. I will sit patiently and wait.
I’m getting the same thing. SmartThings status page shows all green for me. Hmm…
Thankfully I only logged out of my dashboard and logged back in, but the error persists. I will sit patiently and wait.
We have had reports now from all 4 times zones in the US, as well as UK issues…
The error is being produced on line 950 of the webCoRE SmartApp, where there is a check for active incidents in SHM. The same error was experienced in the UK in about March 2018 when it was on line 956.
I’ve commented out line 950 on my installation to see what happens. What doesn’t happen is the error loading the dashboard or the error message in the logs. That gets you into the dashboard.
A second problem is opening up pistons for editing. That gives a similar error in each piston. The fix I’m trying for that is to edit out the contents of initIncidents().
That seems to get past that.
I’ll admit to it. I was working on a piston when it went down. I had just saved it. It was my piston that took down the webcore universe
Down for me too in the UK. Only just upgraded to the New ST app so thought that may be it…
Those of us that have used SmartThings/webCoRE for years are familiar with the old “There was a problem loading the dashboard data” error. The big challenge as a user is that we have no easy way of knowing if it’s just an issue for us and we simply need to clear our cache or if it’s a system-wide issue.
Is there anyway to surface better error info to users so that we know when it’s a bigger issue like this? I spent an hour this morning trying various things including uninstalling and reinstalling webCoRE before I found this thread.
Same here, oddly my pistons are still firing. ST app I can use my devices. One of my pistons has my google home mini saying “door opened for 3 minutes, close it” – I just got the text WebCORE sends, but instead of speaking the message on the Home Mini, it just does the “beep” it makes before it speaks the words, weird. Something obviously amiss somewhere.
Not quite black & white, but generally speaking:
If the error happens when you are editing or saving a piston, then it may be localized only, and might resolve itself with a “cache clear” and/or log out/in…
If the error happens when you did absolutely nothing in webCoRE, then it may be a SmartThing issue, and I would recommend patience while changing nothing.
In my case, it gave me an error while editing, so I assumed it was for me only.
(apparently, I just had bad timing, LOL)
Same issue here. I thought I was going crazy trying to debut it. Probably coincidentally, the issue started when I saved a short piston using a new device handler.
same issue… earlier this morning it was fine… then later i went to edit a piston and got the message.
2:11:33 PM: error physicalgraph.api.StatusCodeException: Invalid http status code returned: 401 @line 950 (api_get_base_result)
2:11:33 PM: error Dashboard: Authentication failed due to an invalid token
2:11:30 PM: error Dashboard: Authentication failed due to an invalid token
2:15:58 PM: error physicalgraph.api.StatusCodeException: Invalid http status code returned: 401 @line 5054 (initIncidents)
are the errors i get when i try to register a browser to view my pistons
Unfortunately, I was tinkering around trying to figure out how to do some new stuff so I definitely thought it was localized. I spent an hour frantically trying to fix it before the yelling family started.
Hailing from Cambridgeshire in the UK, dashboard is down as well. Spent the last two hours assuming I screwed something up with my 8 little pistons. Let’s hope it clears up soon.