# MQTT client **URL:** \ **Category:** Questions & Help\ **Created:** [October 9, 2019, 3:35am UTC](https://community.homey.app/t/mqtt-client/19021 "2019-10-09T03:35:58Z")\ **Posts on this page:** 6\ **Page:** 1
**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:** [October 9, 2019, 3:35am UTC](https://community.homey.app/t/mqtt-client/19021/1 "2019-10-09T03:35:59Z")
Anyone who knows if this is a bug? My MQTT hub is broadcasting some motion sensors and I need to restart MQTT client ones every hour because the flow with “receive tropic trigger” stop working when I see this message in MQTT client “we are not waiting for this tropic”! After a reboot of the app it works fine. ![homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/8/089f25beb11ca223709a2debd594de3d814eefa1.jpeg) ---
**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:58am UTC](https://community.homey.app/t/mqtt-client/19021/2 "2019-10-09T07:58:36Z")
I think the _“We are not waiting for this topic”_ message is a red herring: it’s printed when a message comes in on a topic for which no trigger exists, which isn’t an error (merely informative). Looking at the log, you have a trigger on `homey/mqtt/$stats/uptime`, but I don’t see any messages coming in for that topic. ---
**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:** [October 9, 2019, 9:33am UTC](https://community.homey.app/t/mqtt-client/19021/3 "2019-10-09T09:33:52Z")
It works fine for a little while but then it just stops working. Do you have any clue what the problem can be? Maybe broker app on homey? ---
**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, 9:43am UTC](https://community.homey.app/t/mqtt-client/19021/4 "2019-10-09T09:43:30Z")
You could try using a separate MQTT client application (for Windows/Mac/Linux) to see if messages are actually coming in. ---
**Author:** ![Marian](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marian/32/11090_2.png) [@Marian](https://community.homey.app/u/Marian)\ **Post date:** [March 28, 2020, 5:16pm UTC](https://community.homey.app/t/mqtt-client/19021/5 "2020-03-28T17:16:55Z")
Hi, how can I set up the certificate for TLS connection of the MQTT client, if the broker is running outside of homey? ---
**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 30, 2020, 11:47am UTC](https://community.homey.app/t/mqtt-client/19021/6 "2020-06-30T11:47:07Z")
The MQTT client seems to stop often, In the log I can not detect anything wrong, but I need to restart the MQTT client app regulary. I also mad a flow to restart the app when crashing, but that flow does not seem to work, there is I think not a real crash reported by Homey of the app. I have 2 crash reports: 660bb4a6-2cb6-4b60-a098-9d1c1188794a 192cae87-5a97-490b-95a5-d9a48984cdee Hub seems to stay working. Mosquitto is running on a Pi and is also used for a node-red dashboard. Hub is configured as a custom one and does not do home assistant discovery.