Thanks @RBoy, this makes more sense in that context. I do recall reading in the docs about ST killing long running processes but I didn’t connect that when looking at those long execution times.
The delay I can live with as this is still < 1 sec but what I am wondering about is the long exec time which could be getting killed off by ST. IMO, this long exec time is probably code execution time and not caused by ST running slow. If it is ST crawling then I would agree that there is nothing we can do to fix that other than open up a case which who knows how long it would take to have addressed, sorry to say - I had one case to delete two phantom devices that took in excess of a month.
Regardless, I’m curious to see if I can figure out where the slowness is coming from. I’m not saying the thermostat app is to blame but rather that something is getting hung up. What about connectivity to the device? In this case it is two ZigBee devices but they both seem pretty responsive normally. Or maybe some coding issues in the DTH. Is there a way I can up the logging on the app to sort of profile it a bit? I’m going to try and force some manual executions of the initialize() to see if it happens repeatedly.