# All tado devices unavailable after Homey update to 2.2.0

**URL:** <https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868>\
**Category:** Devices\
**Created:** [June 26, 2019, 4:58pm UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868 "2019-06-26T16:58:05Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ruud\_Verrijk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ruud_verrijk/32/903_2.png) [@Ruud\_Verrijk](https://community.homey.app/u/Ruud_Verrijk)\
**Post date:** [June 26, 2019, 4:58pm UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/1 "2019-06-26T16:58:05Z")

</div>

All my tado devices are unavailable after I upgraded Homey to 2.2.0 and iOS app 2.4.0. When I click a tado device it reports: Device is unavailable, invalid response (400). That was in tado app 3.0.2. I upgraded to tado 3.0.3. Still the same problem. Restarted Homey, same problem. I have a Homey Pro.

Anybody having similar experience after the Homey update to 2.2.0?

---

<div class="post-metadata">

**Author:** ![CyberSponk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cybersponk/32/8334_2.png) [@CyberSponk](https://community.homey.app/u/CyberSponk)\
**Post date:** [June 26, 2019, 6:04pm UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/2 "2019-06-26T18:04:50Z")

</div>

Have had this on 2.1.2 and it was gone with 2.2.0-Rc7. After Update 2.2.0 all was fine till Today.

Reoprted this Issue again to Athom and wait now for their Response.

---

<div class="post-metadata">

**Author:** ![Ruud\_Verrijk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ruud_verrijk/32/903_2.png) [@Ruud\_Verrijk](https://community.homey.app/u/Ruud_Verrijk)\
**Post date:** [June 26, 2019, 6:18pm UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/3 "2019-06-26T18:18:24Z")

</div>

Thanks. I reported as well.

---

<div class="post-metadata">

**Author:** ![Toon\_Vos](https://avatars.discourse-cdn.com/v4/letter/t/57b2e6/32.png) [@Toon\_Vos](https://community.homey.app/u/Toon_Vos)\
**Post date:** [June 26, 2019, 6:36pm UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/4 "2019-06-26T18:36:33Z")

</div>

I had this problem before the update and it is still the same.

---

<div class="post-metadata">

**Author:** ![Gerrit\_Kool](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gerrit_kool/32/102436_2.png) [@Gerrit\_Kool](https://community.homey.app/u/Gerrit_Kool)\
**Post date:** [June 26, 2019, 6:44pm UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/5 "2019-06-26T18:44:32Z")

</div>

The same here

---

<div class="post-metadata">

**Author:** ![Robin\_van\_Kekem](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robin_van_kekem/32/8187_2.png) [@Robin\_van\_Kekem](https://community.homey.app/u/Robin_van_Kekem)\
**Post date:** [June 26, 2019, 7:53pm UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/6 "2019-06-26T19:53:35Z")

</div>

Tado was working fine on 2.2.0 until today.  
It must be an Tado \<-\> Homey issue.

Let’s all report the issues!

[https://support.athom.com/hc/requests/new](https://support.athom.com/hc/requests/new)

---

<div class="post-metadata">

**Author:** ![PhilS](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phils/32/12941_2.png) [@PhilS](https://community.homey.app/u/PhilS)\
**Post date:** [June 26, 2019, 8:17pm UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/7 "2019-06-26T20:17:19Z")

</div>

I have this problems too since update. Made a request to the support.

---

<div class="post-metadata">

**Author:** ![M\_a\_r\_c\_o](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/m_a_r_c_o/32/146_2.png) [@M\_a\_r\_c\_o](https://community.homey.app/u/M_a_r_c_o)\
**Post date:** [June 26, 2019, 8:23pm UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/8 "2019-06-26T20:23:24Z")

</div>

From this afternoon I have on all Tado devices an Invalid response (400) error, tried herstarting the Tado app, but did not solved anything. Also created an issue.

---

<div class="post-metadata">

**Author:** ![PhilS](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phils/32/12941_2.png) [@PhilS](https://community.homey.app/u/PhilS)\
**Post date:** [June 27, 2019, 4:56am UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/9 "2019-06-27T04:56:18Z")

</div>

I solved the problem with deleting the app and reinstalling it again. Logged in again and all devices were back again.

But then I have to search all flows with tado devices to repair them.

---

<div class="post-metadata">

**Author:** ![M\_a\_r\_c\_o](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/m_a_r_c_o/32/146_2.png) [@M\_a\_r\_c\_o](https://community.homey.app/u/M_a_r_c_o)\
**Post date:** [June 27, 2019, 5:13am UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/10 "2019-06-27T05:13:50Z")

</div>

Without doing anything further, all devices start working again around 04:00 CET.

I use presence from Tado, and I came home at this time. I suspect it was a problem at Tado in their API service.

---

<div class="post-metadata">

**Author:** ![Ruud\_Verrijk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ruud_verrijk/32/903_2.png) [@Ruud\_Verrijk](https://community.homey.app/u/Ruud_Verrijk)\
**Post date:** [June 27, 2019, 5:38am UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/11 "2019-06-27T05:38:52Z")

</div>

I confirm my tado devices are available again this morning. Indeed the tado API service may have gone down almost simultaneously with people updating Homey to the new firmware and app, causing some confusion.

Thanks!

---

<div class="post-metadata">

**Author:** ![anon2681894](https://avatars.discourse-cdn.com/v4/letter/a/c67d28/32.png) [@anon2681894](https://community.homey.app/u/anon2681894)\
**Post date:** [June 27, 2019, 9:22am UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/12 "2019-06-27T09:22:51Z")

</div>

After deleting and re- adding tado devices(and fixing all my flows) it works again for me…

---

<div class="post-metadata">

**Author:** ![CyberSponk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cybersponk/32/8334_2.png) [@CyberSponk](https://community.homey.app/u/CyberSponk)\
**Post date:** [June 27, 2019, 1:36pm UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/13 "2019-06-27T13:36:15Z")

</div>

Restarted Tado-App after Support-Mail from @Bram. Now it works. Seems that the Problem was an Tado-Problem and not a Homey-Tado-App-Problem.

---

<div class="post-metadata">

**Author:** ![ramdyne](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ramdyne/32/13675_2.png) [@ramdyne](https://community.homey.app/u/ramdyne)\
**Post date:** [July 20, 2019, 9:42pm UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/14 "2019-07-20T21:42:47Z")

</div>

I have only updated to Homey v2 today, but for a number of weeks (2 months?) the integration with Tado hadn’t worked and I never investigated it because I linked it to me not running v2.

Today I updated to Homey v2.4.1, but all my configured Tado devices show a notification and when I want to investigate it shows an “Invalid response (400)” error. The same thing happens when I try to add a new device. Is the Tado \<-\> Homey integration broken?

–  
ramdynze

---

<div class="post-metadata">

**Author:** ![anon2681894](https://avatars.discourse-cdn.com/v4/letter/a/c67d28/32.png) [@anon2681894](https://community.homey.app/u/anon2681894)\
**Post date:** [July 21, 2019, 5:53am UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/15 "2019-07-21T05:53:43Z")

</div>

First delete all tado devises , then re add them 🙏

---

<div class="post-metadata">

**Author:** ![PhilS](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phils/32/12941_2.png) [@PhilS](https://community.homey.app/u/PhilS)\
**Post date:** [July 21, 2019, 5:53pm UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/16 "2019-07-21T17:53:42Z")

</div>

Indeed that is the only way to go

---

<div class="post-metadata">

**Author:** ![anon2681894](https://avatars.discourse-cdn.com/v4/letter/a/c67d28/32.png) [@anon2681894](https://community.homey.app/u/anon2681894)\
**Post date:** [July 22, 2019, 6:15am UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/17 "2019-07-22T06:15:59Z")

</div>

It’s due to a api update of tado. So Athom cannot help it…

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [November 8, 2025, 2:09pm UTC](https://community.homey.app/t/all-tado-devices-unavailable-after-homey-update-to-2-2-0/14868/18 "2025-11-08T14:09:54Z")

</div>

Archived on November 8, 2025, 2:09pm UTC


