True, but I made no reference to your DTH. Please let the conversation stay on track and not deviate. I wasn’t talking about your app, but all cloud to cloud connections. BTW, asynchronous or not, they can still fail (as stated above).
I believe that you brought the ecobee cloud-to-cloud integration topic in a previous post as stated above in this thread.
So, what I’m saying is that for the ecobee integration, there is less timeouts now because of the async http requests. I’ve been testing them at different user locations, and I’ve noticed less timeouts with my custom DTH.
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.
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.
@vlad : whatever SmartThings did on its cloud, congratulations, it worked for me : the SmartApp which had been failing with timeouts for the last 3 weeks executed again this morning without any problem !
Note that my SmartApp is read-only (accessing about 500 events history records of 11 temperature sensors), so I probably see a greater improvement compared to SmartApps which write also, according to what you wrote.
PLEASE, try not to break anything again, at least for a few more months…
PS : just in case it was only a lucky glitch, I did not tempt fate with trying to execute my SmartApp twice : would have been foolish, right ?
I had zwave devices dropping likes flies. The app became unbearably slow. Schedules were running, just behind. Automations were running, but seriously delayed. Even turning something on with the app had an huge lag. Hopefully today will be better.
My motion sensors were significantly lagging to turn on the lights in the hallways last night. I’ve not seen them that slow in the near year I’ve had them. I thought they were running local since they were previously so fast, but I haven’t dug into my account to verify (aeon6, st sensors with GE dimmers)