TCC App slow to start

[G4RHL]

Over the last few weeks or so the app has not always loaded in first time on either my iPhone or iPad. I use facial recognition to start it. When I do often it just locks with a blank screen and the only way forward is ensure the app is closed and then start again. It then works. I assume the bug in it is that once it has been opened it is not always happy if you go back a few hours later and wants all reference to it having been opened already removed. Anybody else had this issue? It is also slower than it used to be and I am sure someone has already commented on that.

[philchillbill]

I recently had to increase the time-out in my API calls to 10 seconds from 6. That’s how slow the API has become. And the TCC app also uses the API so it suffers from the same slowdown. I believe Resideo hosts TCC on its own hardware and I expect it’s very old stuff at this stage. Pity they don’t use the likes of AWS Lambdas that are elastic and scale instantly from zero to a million users and back to zero again in a second if needed.

[filbert]

Just got this when I opened the app:

"Upcoming Maintenance

We are updating our Total Connect Comfort (TCC) application to better serve you. The services will be unavailable for approximately 76 hours

starting at 07:00 on February 02."

Maybe they've noticed? 76 hours is long enough for significant work. It's also strangely specific at 3 days and 4 hours, if my mental arithmetic is correct.

[philchillbill]

Let’s dream and hope they’re going to add demand via the API and give us the 0.1 deg accuracy that’s there anyway

[G4RHL]

I’ll dream! 11.5 years or so since I installed Evohome and even then the app and controls seemed dated and installation could be confusing for a new user. My breath will not be held. 76 hours is though a long time.

[G4RHL]

I notice now that the 76 hours has been reduced to 4 hours on the 3rd February in the UK.

[WiteWulf]

Yeah, me too. The Evohome app on iOS is painfully slow to start for the last couple of weeks, but changed made via the API and Home Assistant were responsive. I had thought it was maybe to do with my DNS filtering, but am relieved to see it's not just me.

[G4RHL]

It’s slow. Often I have to try to open it twice as the first time it does not recognise my face and I know I haven’t changed that. It is just possible that on the 3rd or thereafter we will have a faster and better programme.

[philchillbill]

The fastest TCC ever responds is about 600ms (per request) but I very regularly see north of 7000ms. For those people who use a HGI-80 with EvoControl, a response from HA or Domoticz takes in the range 13ms to 200ms (it mainly depends on their ISP speed). Most people with HA and Domoticz run things on RPi hardware so you can just imagine what TCC must be runniing on

[G4RHL]

It’s now the 4th February and the app won’t open. It did though yesterday afternoon when the scheduled maintenance would have finished. It was not then quick to open.

30 minutes later I tried again and it opened as normal, slow doing so though. My WiFi was working fine.