Eula issue evohome client version 1 about evohome-client

[zxdavb]

All I can tell you is that : a) I have never seen the EULA message you describe above, b) I am (currently) still able to retrieve v1 temps with no issues.

[zxdavb]

A lot of the original work for this api was done here, and I see no mention of EULA there.

[boe22]

Good to know that it is a rare event.

I Figured out a solution:
a) Remove evohome from evohome account
b) Remove evohome account
c) Create a new account and connect to evohome again. In this second account I chose English as language, not sure if that is relevant.

The new account works as supposed.

Although also this second account mentions "latestEulaAccepted": false in the UserInfo. Weird...

[nomis]

This should still be handled because there's nothing worse than an intermittent exception that doesn't explain what went wrong.

[nomis]

I created a second account and shared the location with it from the first account.

The second account now gets just the EULA message on the full_data part of the process, but the V1 API may not support shared locations.