# Homey unresponsive after 12 hours.in v2

**URL:** <https://community.homey.app/t/homey-unresponsive-after-12-hours-in-v2/8826>\
**Category:** Questions & Help\
**Created:** [February 6, 2019, 8:07pm UTC](https://community.homey.app/t/homey-unresponsive-after-12-hours-in-v2/8826 "2019-02-06T20:07:13Z")\
**Posts on this page:** 7\
**Page:** 4

<div class="post-metadata">

**Author:** ![Martin\_H](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_h/32/7964_2.png) [@Martin\_H](https://community.homey.app/u/Martin_H)\
**Post date:** [March 15, 2019, 10:45am UTC](https://community.homey.app/t/homey-unresponsive-after-12-hours-in-v2/8826/62 "2019-03-15T10:45:40Z")

</div>

no diffrence in Homey v2.0.5 experimental needs restart every 12th hour.

---

<div class="post-metadata">

**Author:** ![gnrk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gnrk/32/8660_2.png) [@gnrk](https://community.homey.app/u/gnrk)\
**Post date:** [March 15, 2019, 11:28am UTC](https://community.homey.app/t/homey-unresponsive-after-12-hours-in-v2/8826/63 "2019-03-15T11:28:06Z")

</div>

I am also experiencing some issues around the MQTT broker. Homey needs restart occasionally and after 2.05 I have found the broker “paused” i n Homey as well.

---

<div class="post-metadata">

**Author:** ![Tb1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tb1/32/8934_2.png) [@Tb1](https://community.homey.app/u/Tb1)\
**Post date:** [March 21, 2019, 5:55am UTC](https://community.homey.app/t/homey-unresponsive-after-12-hours-in-v2/8826/64 "2019-03-21T05:55:45Z")

</div>

I wonder how long time Athom needs to fix the “leek” It starts to get really annoying.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Somhorst](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_somhorst/32/184_2.png) [@Jeroen\_Somhorst](https://community.homey.app/u/Jeroen_Somhorst)\
**Post date:** [March 21, 2019, 6:18am UTC](https://community.homey.app/t/homey-unresponsive-after-12-hours-in-v2/8826/65 "2019-03-21T06:18:55Z")

</div>

Maybe it’s a mqtt broker issue and not a homey core issue?

---

<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:** [March 21, 2019, 6:30am UTC](https://community.homey.app/t/homey-unresponsive-after-12-hours-in-v2/8826/66 "2019-03-21T06:30:32Z")

</div>

Finding a memory leak is like finding a tiny needle in a massively huge hay stack, incredibly difficult to find the main cause, so how long it takes really depends **if** they can find the leak, or maybe even multiple leaks.

---

<div class="post-metadata">

**Author:** ![Martin\_H](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_h/32/7964_2.png) [@Martin\_H](https://community.homey.app/u/Martin_H)\
**Post date:** [May 6, 2019, 9:32am UTC](https://community.homey.app/t/homey-unresponsive-after-12-hours-in-v2/8826/67 "2019-05-06T09:32:55Z")

</div>

If I restart the wireless weather sensor app every night the memory is below 120mb all the time and I don’t lose connection to homey and do not need to restart homey every night

---

<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:** [May 6, 2019, 11:07am UTC](https://community.homey.app/t/homey-unresponsive-after-12-hours-in-v2/8826/68 "2019-05-06T11:07:21Z")

</div>

Did you deselect all discover-able brands from devices you don’t have from the list?  
It’s recommended by the creator…

I am also running the app and i don’t have any problem with it. In my list only “cresta” is selected.

[Previous page](https://community.homey.app/t/homey-unresponsive-after-12-hours-in-v2/8826.md?page=3)
