Credentials no longer working - can't read data

[MartinG]

Some time ago (>30 days according to my Indigo logs), the Evohome plugin became unable to read data from the cloud API service.

I've verified the credentials using the website, and updated the credentials in the pluging to be certain they're correct, but get an error dialog when do this: "Unable to connect to the Evohome API with these credentials".

Did something change, or am I being an idiot?

[CliveS]

No, you are not alone.

I also had this problem, originally got round it by using my Home Assistant Server to log into the EU Evohome server and used Home Assistant Agent plugin to control radiators. I then bought a RAMSES-ESP dongle so I could control the radiators locally after getting Claude to write the code and has been working fine for over 2 months now.

Still cant log into the TCC EU server using the iPhone App and changed my password several times so no idea what is happening but now controlling the radiators locally so not too worried and also I don't keep finding that they have taken their server off line for maintenance which was annoying me on a daily basis!

[MartinG]

I'm not doing any controlling, just monitoring - my HA philosophy is to have standalone off the shelf systems for everything I can. Then when I mess up the server/it crashes, the house still 'works'.

With your RAMSES approach, can you read room temperatures, thermostat on/off, boiler status etc

[CliveS]

I only use it for controlling the radiators so not sure about thermostat and boiler controls but the details for the RAMSES dongle is at
https://indalo-tech.onlineweb.shop/product/ramses-esp , you may need to go on the waiting list , I had to wait about a month before the next batch arrived in stock

[boekweg]

Thanks to codex, I (well codex) was able to resolve the problem. Updated Honeywell.py to replace the retired tccna.honeywell.com endpoint with tccna.resideo.com. The old hostname no longer resolves, preventing the plugin from connecting to the Evohome API.
The update also improves token handling by automatically performing a fresh login when a stored token is no longer valid, and fixes a capitalization error in the username preference check. Open the attached file and save it as Honeywell.py. In order to solve the problem replace the honeywell.py file within the plugin. reload the plugin and it's working again.