# Why are apps developed by athom so poorly supported

**URL:** <https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914>\
**Category:** Apps\
**Created:** [October 6, 2019, 12:08pm UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914 "2019-10-06T12:08:24Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Erik\_de\_Vries](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erik_de_vries/32/4138_2.png) [@Erik\_de\_Vries](https://community.homey.app/u/Erik_de_Vries)\
**Post date:** [October 6, 2019, 12:08pm UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/1 "2019-10-06T12:08:24Z")

</div>

Hello, i have 2 apps from athom on my homey that have again problems with the api…  
First one is Tado, it lost connection with the devices and after remove and reinstall it never finds the devices anymore when added, screen stays empty…

2nd one is Nest, login got disconnected somehow and now it always says something went wrong wen giving permissions to homey, i did not convert my nest account to google so should still work.  
But athom decided to remove the app from the store so i cannot uninstall and reinstall it…

Do others users have problems with one of those apps at the moment and have found a solution?

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [October 6, 2019, 1:11pm UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/2 "2019-10-06T13:11:43Z")

</div>

Don’t use tado so no clue.

Have no issues here with the nest app (also still on nest account, and didn’t activate the 2nd authentication (you get this prompt when you open the nest mobile app)) but if you know how to sideload an app, the code is still on their [github](https://github.com/athombv/com.nest).

---

<div class="post-metadata">

**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\
**Post date:** [October 6, 2019, 1:25pm UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/3 "2019-10-06T13:25:34Z")

</div>

Maybe an open door, but you already reported this to Athom support?

---

<div class="post-metadata">

**Author:** ![Erik\_de\_Vries](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erik_de_vries/32/4138_2.png) [@Erik\_de\_Vries](https://community.homey.app/u/Erik_de_Vries)\
**Post date:** [October 6, 2019, 2:03pm UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/4 "2019-10-06T14:03:48Z")

</div>

Yes offcourse, but always slow to respond and most of the time more questions and no solutions compared to the developers of the “community” made apps.  
Some app developers are super quick with solutions and great in communication.  
Athom devs simply not 😇, last time the Tado issues took 9 months to solve(token lost issue)

Now i get this after an long empty screen after logon:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/1/b13a2106397eaaac4c13cc14149985051561cff4.jpeg)

So Oauth issues again 🙄

---

<div class="post-metadata">

**Author:** ![tlangelaar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tlangelaar/32/10980_2.png) [@tlangelaar](https://community.homey.app/u/tlangelaar)\
**Post date:** [October 6, 2019, 2:15pm UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/5 "2019-10-06T14:15:07Z")

</div>

Advise you to remove your picture with personal data, or to strike through the token and id’s.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 6, 2019, 3:22pm UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/6 "2019-10-06T15:22:40Z")

</div>

> [@Erik\_de\_Vries](#):
>
> So Oauth issues again

No, networking issues: the EAI\_AGAIN error means that the DNS server that Homey is using was unable to handle the request (which was to look up the IP-address for `auth.tado.com`). It’s likely to be a temporary issue, but if it remains, try power-cycling your Homey.

---

<div class="post-metadata">

**Author:** ![Erik\_M\_Madsen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erik_m_madsen/32/18191_2.png) [@Erik\_M\_Madsen](https://community.homey.app/u/Erik_M_Madsen)\
**Post date:** [October 7, 2019, 9:44am UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/7 "2019-10-07T09:44:19Z")

</div>

And you are sure not uding the BETA app??

Mine also lost contact, found out I´ve never updated to prod app.  
Updated to prod app and after that, 3 days ago, no problems.

---

<div class="post-metadata">

**Author:** ![Erik\_de\_Vries](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erik_de_vries/32/4138_2.png) [@Erik\_de\_Vries](https://community.homey.app/u/Erik_de_Vries)\
**Post date:** [October 7, 2019, 9:26pm UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/8 "2019-10-07T21:26:19Z")

</div>

Tado problem is solved by restarting router/wifi again.  
Now only the Nest problem remain, getting this error:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/c/5cd75576f30ab6a443e1da9ab63cee26184ba2ac.jpeg)  
App is not supported anymore but should still work…

---

<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:** [October 9, 2019, 7:53am UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/9 "2019-10-09T07:53:57Z")

</div>

I have also problems with 2 Athom apps  
Tado, same problem as you described, before the devices lose connection and app crashes it complains about connection time out.  
I can’t solve it since January, I randomly ask Athom development to help me since then, no reaction.

Chromecast looses connection to Chromecast audio and JBL link view  
Also unfortunately no solution from Athom

Problems look to me as the same sort, loosing connection over time. Maybe this problems have the same root cause as your former fault. What path should I try to solve it?

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 9, 2019, 7:59am UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/10 "2019-10-09T07:59:28Z")

</div>

> [@Toon\_Vos](#):
>
> What path should I try to solve it?

Some people reboot their Homey automatically daily, or once every few days.

---

<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:** [October 9, 2019, 8:01am UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/11 "2019-10-09T08:01:41Z")

</div>

But Tado only works for an hour or so

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 9, 2019, 8:02am UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/12 "2019-10-09T08:02:48Z")

</div>

If that’s the case, and the app developer isn’t responding, there’s not a whole lot you can do I’m afraid. Perhaps try re-pairing the devices to see if that “resets” Homey.

---

<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:** [October 9, 2019, 8:14am UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/13 "2019-10-09T08:14:10Z")

</div>

Done that too, a couple of times.

But I will try to do some research on the connection. Fixing the ip addresses. erik\_de\_vries got me thinking. Who knows…

---

<div class="post-metadata">

**Author:** ![Budda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/budda/32/7956_2.png) [@Budda](https://community.homey.app/u/Budda)\
**Post date:** [October 12, 2019, 10:46pm UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/14 "2019-10-12T22:46:34Z")

</div>

My Nest device in Homey says “This device is no longer available in your Nest account” in a red banner when I tap the device.  
I too have not converted my Nest account to a Google one, and I can see my Protect device in the app.

Is the Nest problems related to the Works With Nest program retirement mentioned on [https://developers.nest.com/](https://developers.nest.com/) maybe?

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [October 13, 2019, 7:53am UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/15 "2019-10-13T07:53:28Z")

</div>

And you also didn’t click the button “I understand” instead of “not now” when you opened the official Nest mobile app?  
It is a really tricky one that you can click really easily when you don’t read everything, haven’t been able to take a screenshot of the message (at the bottom of the screen) as it hasn’t reappeared yet for me, but have seen it twice now.

It isn’t fully the same reason, it is still using the “works with nest”, but not the default authentication anymore and thus your devices stop working.

---

<div class="post-metadata">

**Author:** ![Budda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/budda/32/7956_2.png) [@Budda](https://community.homey.app/u/Budda)\
**Post date:** [November 13, 2019, 12:54am UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/16 "2019-11-13T00:54:42Z")

</div>

I don’t recall the “I understand” button now.  
When I run the Nest iOS app i still get asked about the 2 step verification.

 ![IMG_F9421801EC10-1](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/d/edfc388f8bace55c5af3045207d1ea57b286eef3.jpeg)

---

<div class="post-metadata">

**Author:** ![Cuflee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cuflee/32/12515_2.png) [@Cuflee](https://community.homey.app/u/Cuflee)\
**Post date:** [November 15, 2019, 10:36am UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/17 "2019-11-15T10:36:28Z")

</div>

Completely agree with you! The Aeotec app from Athom seems to be abandoned. Never got new devices as the new LED bulb or tristate sensor anymore, sensor 7 did got added but does not work.

Oh, forgot to mention the TERRIBLE Bosch-Siemens Home Connect app that simply loses connectivity over and over again without reason and never seems to get fixed.

Chromecast issues where you need to add all of your chromecast devices again after every update. NetAtmo app that does not trigger motion alerts correctly…

I thought Athom created/supported apps would be a lot better, but the community supported apps seem a lot more powerfull. I never had any issues with Heimdall, better logic, etc.

---

<div class="post-metadata">

**Author:** ![HansieNL](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hansienl/32/10634_2.png) [@HansieNL](https://community.homey.app/u/HansieNL)\
**Post date:** [November 16, 2019, 3:16am UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/18 "2019-11-16T03:16:51Z")

</div>

I asked Athom for adding the Aeotec nanomote quad. A new Nice small remote controller. Their answer was: We are not gonna support this. I think Athom is killing their own company this way.

---

<div class="post-metadata">

**Author:** ![Jamie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jamie/32/5274_2.png) [@Jamie](https://community.homey.app/u/Jamie)\
**Post date:** [November 16, 2019, 5:38am UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/19 "2019-11-16T05:38:08Z")

</div>

Sure they said “won’t support it” and not “can’t support this”?

---

<div class="post-metadata">

**Author:** ![HansieNL](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hansienl/32/10634_2.png) [@HansieNL](https://community.homey.app/u/HansieNL)\
**Post date:** [November 16, 2019, 2:05pm UTC](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914/20 "2019-11-16T14:05:35Z")

</div>

This is part of the answer:  
We currently do not have plans to add this device to the Aeotec app.  
You can however request the implementation of new devices via [this form](https://goo.gl/forms/6GpSTBD3tpHNgVir2).

I have sent a request also. I even have sent a message to Stefan on slack, because I think this is a nice small remote device for using with homey.

[Next page](https://community.homey.app/t/why-are-apps-developed-by-athom-so-poorly-supported/18914.md?page=2)
