Webcore Not Working Since Update

#1

Is anyone else experiencing problems with WebCore? I am no longer seeing any pistons on my desktop and while I can see pistons in the app, I get the following message when Webcore is loaded, “There was a problem loading the dashboard data. The data shown below may be outdated; please log out if this problem persists.”

The location name is also missing. Instead all I see is “getLocationMode()}”. Tried the Cleanup and rebuild data cache function, but just get a message saying that “Something’s wrong”.

I installed the new Webcore smartapp releases earlier today and since then I have not been able to get Webcore to work.

The Live Logging is showing the following Javascript error, “12:50:33 AM: error java.lang.reflect.UndeclaredThrowableException @line 1713 (listAvailableDevices)” (See screenshot), so that would seem to be related somehow.

2019-06-28_005113
2019-06-28_005113.jpg1279×827 452 KB

#2
  1. did you publish all the Smartapps when you updated them?
  2. do you use echo devices through echo speaks?
#3

Yes, all of the smartapps were updated.

Not using any echo devices.

#4

I can load the dashboard but I cannot load any pistons. I just get the spinner.

@ipaterson

#5

I rolled back the last Webcore updates from Github to the previous version of files (v0.3.10c.20190522), and that solved the problem.

So it would appear that there is a bug of some sort in the latest release.

#6

Logs please, @Nezmo. Since no one reported that the workaround earlier this year from ady had fixed the UndeclaredThrowableException and tons of people were complaining about both that exception and the fact that the workaround caused the piston page to show NaN for device attributes, the workaround was reverted.

@warrisr please take some time to confirm whether this is failing for you 100% of the time on the new version of the smart apps and that rolling back fixes it 100% of the time. The UndeclaredThrowableException is very spotty for people with just a few too many devices since it depends on the load of the ST platform and whether it can load your devices quickly enough at the time you load the dashboard.

Seems we can’t win on this one; the ST Groovy platform is abandoned as far as scaling is concerned so the exceptions will continue to affect more people. If ady’s workaround fixes dashboard access for a few people I guess that gives them a bit more time to find a home automation platform that will work for their needs.

#7

Definitely 100% failure rate with the 3.10d code. Tried it on several different devices over 24 hours and always had the same results. I just did the rollback to 3.10c about 2 hours ago and have only tested on one computer, but so far the problem has not re-surfaced.

I have 111 devices in one Webcore account and 22 in another. 3.10d would not work in either.

I know that Samsung has deprecated the ST Groovy platform, but it has never been clear to me what the long term implications are for WebCore. Is Webcore a dead end now? Like many others here, I have put a tremendous amount of work into setting this up, so it will be very disappointing if Webcore is ultimately going to be abandoned. And if that is the case, what are the alternatives?

#8

I am seeing the same issue as above in the logs when trying to access a piston:

1:25:41 PM: error java.lang.reflect.UndeclaredThrowableException @line 1713 (listAvailableDevices)

#9

I am seeing an issue editing current pistons, the progress wheel just keeps going…

#10

Yes, absolutely the current webCoRE and CoRE smart apps will no longer work once the Groovy platform is discontinued. There is no known date or official statement on that but since the platform must be incredibly expensive for ST to operate and they’ve been working on a replacement we can only assume that eventually the day will come. Hopefully SmartThings is motivated enough to keep us as customers to provide some sort of migration path. The developer of webCORE has been working for SmartThings for awhile now so it’s a possibility that we and users of the other most popular smart apps will have something new to look forward to with official SmartThings support.

Many have had success running webCoRE locally on their Hubitat Elevation hub and a fork of webCoRE is maintained by some members of this community for compatibility with HE. webCoRE is not designed to run on a single device, but it’s an option for those who prefer to keep their distance from SmartThings.

I suppose for now the decision is yours; continue building with webCoRE and accept the possibility that there may be no successor when the platform eventually goes away, or look for an alternative now.

#11

Ady’s workaround is reinstated in v0.3.10e.20190628

#12

Thanks Ian. Back in action here.

#13

Truly a shame. WebCore has been a fantastic solution and will be extremely difficult to replace.

I would not hold my breath hoping that Samsung will provide a migration path to a service that offers as much power and flexibility as WebCore. Their objective will be to attract smart home users in the millions. A few tens of thousand home automation enthusiasts are not going to be of much interest to them.

At this point, I am now re-thinking the whole concept of a cloud or subscription-based service where I don’t have control over the on/off switch.