Evohome client Latest Eula Not Accepted

[willumpie82]

The problem

When using the Evohome integration (evohomeasync) an 'HTTP 403 forbidden' error is thrown in the log with the response code: "LatestEulaNotAccepted" and followed with a warning that it is unable to obtain high-precision temperature

A similar issue has been brought up in an old Evohome client discussion evohomeclient: issue-53 but was not actually solved

What I tried:

• Changing password (generated, excluding 'strange' characters) -> no sollution
• Logging in via the homeConnect website, works fine (with the same PW as above)

Despite this error the temperatures seem to be updated regularly on the frontend

Ofcource it is debatable if it is an issue since data is updated and if high precision is needed.

What version of Home Assistant Core has the issue?

2022.8.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

evohome

Link to integration documentation on our website

https://www.home-assistant.io/integrations/evohome

Diagnostics information

No response

Example YAML snippet

evohome:
  username: "my@email.nl"
  password: !secret Evohome

Anything in the logs that might be useful for us?

2022-08-11 08:35:43.983 ERROR (MainThread) [evohomeasync] HTTP Status = 403, Response = [
{
"code": "LatestEulaNotAccepted",
"message": "Latest Eula is not accepted."
}
]
2022-08-11 08:35:43.994 WARNING (MainThread) [homeassistant.components.evohome] Unable to obtain the latest high-precision temperatures. Check your network and the vendor's service status page. Proceeding with low-precision temperatures. Message is: 403, message='Forbidden', url=URL('https://tccna.honeywell.com/WebAPI/api/locations?userId=2980537&allData=True')

Additional information

I have an NL account at honeywell (resido), didn't have this issue when I'm using e.g. Athom Homey

[probot-home-assistant[bot]]

evohome documentation evohome source _{^{(message by IssueLinks)}}

[probot-home-assistant[bot]]

Hey there @zxdavb, mind taking a look at this issue as it has been labeled with an integration (evohome) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

[zxdavb]

The solution to this problem is to log onto the relevant website and accept the new EULA.

The client uses a second URL when high-precision temperatures are enabled. In this case it appears that it is that website which is requiring a new EULA...

The main URL is currently: https://www.mytotalconnectcomfort.com/

I am sorry, I don't know the URL for the (high-precision) v1 API...

The workaround is to do without high-precision temps. You can get this data offline (without needing access to the Internet via ramses_rf with a USB-to-RF dongle running evofw3).