TADO: unable to set home/away for last month or so- error in log "zoneStates"

[Markdevine79]

The problem

I have not made any changes to my automations, but noticed that my Tado has stopped turning off when I am away.
I use a device tracker on the homeassistant app to register whether my partner or I are in the house, and tado was set to turn both instances to "away" mode when both muy partner and I were away.
This all worked fine unitl around a month ago. Now I am unable to use homeassistant to alter home/away states of the trado system, although all other alterations (target temp, switch device off etc) all work fine.

I do not know which homeassistant upgrade caused this to happen, but I just rolled back with reinstallation to one from 6 months ago and the problem still happens which is odd- this makes me think it is something to do with tado altering their API?

Anyway- I have two different tado thermostats registered with two different email addresses, which makes this all complicated. To simplify, I created the following script which reproduces the problem- shown below:

alias: Set temp away mode
sequence:
  - device_id: 938d2d0401d6d3db05a93acce110966d
    domain: climate
    entity_id: 6f21c9ab4be581fa8ef086b34628945f
    type: set_preset_mode
    preset_mode: away
mode: single

This gives the following errors in the log:

Logger: homeassistant.components.tado
Source: components/tado/init.py:214
Integration: Tado (documentation, issues)
First occurred: 15 January 2024 at 22:02:59 (1091 occurrences)
Last logged: 13:36:59

Error for home ID 1267667 while updating mobile devices: [{'code': 'accessDenied', 'title': 'current user is not allowed to access home 1267655 (user is not a resident)'}]
Error for home ID 1267667 while updating mobile devices: [{'code': 'accessDenied', 'title': 'current user is not allowed to access home 1267667 (user is not a resident)'}]
Error for home ID 1267655 while updating mobile devices: [{'code': 'accessDenied', 'title': 'current user is not allowed to access home 1267655 (user is not a resident)'}]

Logger: homeassistant
Source: components/tado/init.py:292
First occurred: 04:58:01 (106 occurrences)
Last logged: 13:37:28

Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/tado/init.py", line 88, in
lambda now: tadoconnector.update(),
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/init.py", line 190, in wrapper
result = method(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/tado/init.py", line 196, in update
self.update_zones()
File "/usr/src/homeassistant/homeassistant/components/tado/init.py", line 292, in update_zones
zone_states = self.tado.get_zone_states()["zoneStates"]
~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
KeyError: 'zoneStates'

Logger: homeassistant.components.tado
Source: components/tado/init.py:214
Integration: Tado (documentation, issues)
First occurred: 15 January 2024 at 22:02:59 (1094 occurrences)
Last logged: 13:37:59

Error for home ID 1267667 while updating mobile devices: [{'code': 'accessDenied', 'title': 'current user is not allowed to access home 1267655 (user is not a resident)'}]
Error for home ID 1267667 while updating mobile devices: [{'code': 'accessDenied', 'title': 'current user is not allowed to access home 1267667 (user is not a resident)'}]
Error for home ID 1267655 while updating mobile devices: [{'code': 'accessDenied', 'title': 'current user is not allowed to access home 1267655 (user is not a resident)'}]

What version of Home Assistant Core has the issue?

core-2024.1.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

tado

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

alias: Set temp away mode
sequence:
  - device_id: 938d2d0401d6d3db05a93acce110966d
    domain: climate
    entity_id: 6f21c9ab4be581fa8ef086b34628945f
    type: set_preset_mode
    preset_mode: away
mode: single

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @chiefdragon, @erwindouna, mind taking a look at this issue as it has been labeled with an integration (tado) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tado can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign tado Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[WebSpider]

Do you still have the geofencing skill active in your home? I recall it's subscription based, depending on the gateway version

[Markdevine79]

No, I never subscribed to it. That's why I set up home assistant to do it

…

On Tue, 16 Jan 2024, 16:00 WebSpider, ***@***.***> wrote: Do you still have the geofencing skill active in your home? I recall it's subscription based, depending on the gateway version — Reply to this email directly, view it on GitHub <#108155 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4YD3O7FU5WXUQUNRVZLIDDYO2P2ZAVCNFSM6AAAAABB42W6KCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJUGAZTQNZUG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[erwindouna]

Thanks for reporting. The issue is clear and what the underlying root cause is. We're in the middle of providing a structural fix for it.

[Markdevine79]

Ah great - not just me then! Cheers and good luck with the work on it

…

On Tue, 16 Jan 2024, 16:33 Erwin Douna, ***@***.***> wrote: Thanks for reporting. The issue is clear and what the underlying root cause is. We're in the middle of providing a structural fix for it. — Reply to this email directly, view it on GitHub <#108155 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4YD3O745Y737U6F5SACV4DYO2TVFAVCNFSM6AAAAABB42W6KCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJUGA4TQOBXHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[dirtyharryiv]

I have the same problem. Thanks for your time and effort!