Scheduled jobs failing (again) (again 😥) (Ongoing Known Issue)

[JDRoberts]

@bago

FYI, this also plagued the ecobee’s - hitting the ecobee website would sometimes trip the time limit because of the cloud to cloud dependencies (it’s much better now, but I suspect they lengthened the time for that specific use case).

I think the point being made in the reply to the above was that SmartThings has very recently implemented a platform change which allows devices, including the ecobee, which use a cloud to cloud communication To third-party services to go to asynchronous contact, meaning the time spent waiting for the ecobee cloud to answer is not counted against the smartapp’s execution time. This change was completely independent of the change that @vlad has been discussing with regard to the database errors. But it has a similar end result, in that there will be fewer time outs.

@yvesracine was verifying that he has changed his ecobee smartapps ( which are quite popular in the community) to use the new asynchronous method.

Asynchronous HTTP API - Beta Launch

Originally published at: http://devblog.smartthings.com/2016/10/17/asynchronous-http-api-beta-launch/ SmartThings Developers - we’re excited to announce a beta version of APIs that allow developers to make HTTP requests to third party services asynchronously. These APIs work similarly to existing APIs like httpGet(), httpPut(), etc., but with one big difference - they are executed asynchronously. Here’s an example of making an asynchronous GET request: include ‘asynchttp_v1’ def initialize() { def params = [ uri: “https://api.github.com”, path: “/search/code”, query: [q:‘httpGet+repo:SmartThingsCommunity/SmartThingsPublic’] ] // make request, passing the name of the method to call // with the response asynchttp_v1.get(“responseHandle…

SmartThings is a very versatile system, but that also means it can fail in many different ways. A fix to one doesn’t always fix another.

Since ecobee was mentioned specifically, I think it reasonable to bring up that people can see improvements in timeouts for that device if they have switched to any device type handler that now use the asynchronous method.