# \[SOLVED\] MQTT Flows disabled by Homey because they execute too many times

**URL:** <https://community.homey.app/t/solved-mqtt-flows-disabled-by-homey-because-they-execute-too-many-times/26032>\
**Category:** Flows\
**Created:** [February 17, 2020, 9:10pm UTC](https://community.homey.app/t/solved-mqtt-flows-disabled-by-homey-because-they-execute-too-many-times/26032 "2020-02-17T21:10:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![p2baron](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/p2baron/32/7948_2.png) [@p2baron](https://community.homey.app/u/p2baron)\
**Post date:** [February 17, 2020, 9:10pm UTC](https://community.homey.app/t/solved-mqtt-flows-disabled-by-homey-because-they-execute-too-many-times/26032/1 "2020-02-17T21:10:41Z")

</div>

So I have replaced my Siedle intercom with an old industrial phone.  
It has a ESP8266 to communicate to Homey via MQTT.

It is all working fine except Homey keeps disabling my flows. This is strange because I don’t exceed the 10 times a second or 120 times a minute thresholds. The device reports about every minute.

I do have multiple flows listening to the same topic for a different message. Is it possible that Homey somehow sees this as multiple starts?

Anyone else experiencing similar behavior?

I am on 4.0.0-rc6 using both the (excellent) broker and client MQTT app written by Menno van Grinsven

---

<div class="post-metadata">

**Author:** ![p2baron](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/p2baron/32/7948_2.png) [@p2baron](https://community.homey.app/u/p2baron)\
**Post date:** [February 29, 2020, 9:09pm UTC](https://community.homey.app/t/solved-mqtt-flows-disabled-by-homey-because-they-execute-too-many-times/26032/2 "2020-02-29T21:09:21Z")

</div>

I think this was crappy programming on my side. Switched to [homie-esp8266](https://github.com/homieiot/homie-esp8266) (Github) and it seems to be resolved now.  
Closing this topic