Page 1 of 1

Plugin error (Couldn't connect to server)

Posted: Friday 27 December 2024 10:38
by fvdp80
Since yesterday the Evohome API plugin can't seem to connect to the server with the following error:

Code: Select all

Error: EvoHome: Login failed with message: Couldn't connect to server
I can connect to TCC through web and Homey, so service is up and running.
More users with the same issue?

Re: Plugin error (Couldn't connect to server)

Posted: Saturday 08 March 2025 20:02
by franzelare
did you get this fixed?
since last week my evo home using the web API is not working anymore

2025-03-08 20:01:47.372 Error: (EvoHome) retrieve installation info returned message: Request was bad formatted or cannot find required ID parameter in the URL.
2025-03-08 20:01:47.373 Error: (EvoHome) failed to retrieve installation info from server

Re: Plugin error (Couldn't connect to server)

Posted: Sunday 09 March 2025 22:55
by phkpr
Hi,

From Almere Netherlands same issue. Domoticz Version: 2024.7

Evohome connection is not the most stable
but since last week I have the same errors as described in this thread.

2025-03-09 22:44:17.896 Error: EVOHOME: Retrieve installation info failed with message: Timeout was reached
2025-03-09 22:44:17.896 Error: EVOHOME: Failed to retrieve installation info from server

The TCC app on android and the TCC website are working fine.

Grtz.
Frits.

Re: Plugin error (Couldn't connect to server)

Posted: Monday 10 March 2025 21:39
by philchillbill
I use a HGI-80 with Evohome for Domoticz so no issues there. However, I’m the author of the EvoControl Alexa skill for Evohome and it does use TCC with a dedicated API key. I can see in the skill’s logs that TCC has been misbehaving a lot in the last week for users all over Europe. Some of my users have mentioned that the TCC mobile app has also been unstable. So it is likely just a temporary issue until Resideo finish whatever maintenance they are doing.

Re: Plugin error (Couldn't connect to server)

Posted: Thursday 13 March 2025 13:28
by franzelare
i see there has been communication until last night 0:59
it renamed my zones and supplied data
but now getting the same error again

Re: Plugin error (Couldn't connect to server)

Posted: Friday 14 March 2025 9:57
by uncledulgaria
I've had errors at various rates since May 2024, but only one issue (Noveember last year) with the TCC app on my android phone, on the odd occasion I've used it.

Error messages from Domoticz vary between one to approximately 10 in any one day, I receive them by email.
What is strange however, is that I still obtain data from the TCC servers, nicely recorded in Domoticz.


On 7th March at 16:29 UTC I got an email from [email protected]
Dear user,
We would like to notify you that the Total Connect Comfort service restored communication with the heating system installed in the following location:
I'd had a few messages around 2 a.m. that morning, but after the email the Domoticz errors almost stopped completely for a couple of days. There was only one on the 8th and one on the 9th, until 12:51 UTC on the 10th, when they were continuous for an hour. They stopped at 14:06, started again from 15:47, errors came again for about half an hour then stopped completely until 12:47 on the 13th March. They have barely stopped since.
I temporarily disabled the Evohome via Web API hardware item for a while to stop the spamming, which has of course resulted in the loss of data.

On re-enabling, the error messages are back, so I've disabled notifications for now.
The most recent error was :-
2025-03-14 14:15:01.473 Error: 17 SP Evohome: Status request failed with message: Timeout was reached
Has anyone seen similar patterns ?
Is there a way to get more information about the nature of the failure to connect ?
Why do I get data via the APi even though the messages are as shown by phkpr ?
Poll interval is 300 seconds
Synchronize schedule, Show schedule and Show location are all enabled.