# MQTT Hub/Gateway **URL:** \ **Category:** Apps\ **Created:** [January 14, 2019, 6:59pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766 "2019-01-14T18:59:50Z")\ **Posts on this page:** 20\ **Page:** 64
**Author:** ![Mikael](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mikael/32/4128_2.png) [@Mikael](https://community.homey.app/u/Mikael)\ **Post date:** [April 26, 2024, 6:19am UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1278 "2024-04-26T06:19:29Z")
Need to ask. I want to remove the app and do a fresh restart but i got a lot of sensors for the app and wounder if I delete the app will that remove all devices / Sensors that are connected to the app as i want them all to be deleted to. ---
**Author:** ![Zimo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/zimo/32/16621_2.png) [@Zimo](https://community.homey.app/u/Zimo)\ **Post date:** [April 26, 2024, 7:34am UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1279 "2024-04-26T07:34:34Z")
App is only collecting sensors data from Homey and publish them to MQTT client - so uninstallation of app will not remove any devices. If your app is causing high CPU load - I’d start by uninstalling app + uninstalling MQTT client - then try beta if it changes anything for you… Are you using external MQTT broker or that internal from Menno? I decided for external Mosquitto, because with older Homey it was too heavy load for it. I do not know how it is with current one, but I use MQTT also for messages from devices out of Homey network and I use Influx for storing historical data, so why to push Homey to edge… ---
**Author:** ![Mikael](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mikael/32/4128_2.png) [@Mikael](https://community.homey.app/u/Mikael)\ **Post date:** [April 26, 2024, 7:57am UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1280 "2024-04-26T07:57:35Z")
Ok i have uninstalled the both apps from homey but all the sensors that was connected to the apps is still in Homey and i want to do a fresh start as it was ovher 1500 sensors connected to the apps and that i think was the problem from the beginning. After i removed the apps i also restarted the homey but the sensors is still in Homey ? ---
**Author:** ![Mikael](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mikael/32/4128_2.png) [@Mikael](https://community.homey.app/u/Mikael)\ **Post date:** [April 26, 2024, 8:20am UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1281 "2024-04-26T08:20:35Z")
I installed the Mqtt Hub app in homey and direct it crashed? Installed this one to try - [https://homey.app/sv-se/app/nl.hdg.mqtt/MQTT-Hub/test/](https://homey.app/sv-se/app/nl.hdg.mqtt/MQTT-Hub/test/) And no different from this one that give me tha same issues - [https://homey.app/en-se/app/nl.hdg.mqtt/MQTT-Hub/](https://homey.app/en-se/app/nl.hdg.mqtt/MQTT-Hub/) I am stuck and dont know what to do. ---
**Author:** ![Zimo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/zimo/32/16621_2.png) [@Zimo](https://community.homey.app/u/Zimo)\ **Post date:** [April 26, 2024, 8:35am UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1282 "2024-04-26T08:35:24Z")
I started with this article - [Node Red: A widget based dashboard working with Homey trough MQTT - Apps - Homey Community Forum](https://community.homey.app/t/node-red-a-widget-based-dashboard-working-with-homey-trough-mqtt/18798) this helped me lot setting up whole MQTT (although you do not have to use Node-red) ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [April 26, 2024, 1:15pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1283 "2024-04-26T13:15:16Z")
Here’s my tutorial if you’re interested. > [@MQTT Hub/Gateway](https://community.homey.app/t/mqtt-hub-gateway/6766/1175): > > Yes, MQTT Hub & MQTT Client on Homey, and MQTT Broker on Homey, or HA, or Synology NAS, or even (not preferrable) a cloud service f.i. I just made a step-by-step Tutorial: [[TUTORIAL][PRO] How to integrate Home Assistant with Homey](https://community.homey.app/t/tutorial-pro-how-to-integrate-home-assistant-with-homey/92641) by the way . > [@Mikael](#): > > I installed the Mqtt Hub app in homey and direct it crashed? It’s a pity Homey and/or apps can’t be started in safe mode. Because when MQTT Hub crashes @ Pro23, it wants to sync more devices than the app limits for CPU usage allows. > [@Mikael](#): > > 1500 sensors I think that’s a very high number Now, when you lower the amount of devices to sync, the app shouldn’t crash at startup anylonger, at some point. However, I don’t know if you still could disable a bunch of devices per app config? > ![Screenshot_20240426-152218_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/2/f2bb6048d24f53abd29a33df7a57f9338c66df5e.jpeg) . Also try to (temporary) disable “Home Assistant discovery” > ![Screenshot_20240426-152428_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/f/7f152603a21c4a00987a7de46144f70cc18d2f8f.jpeg) Now restart MQTT Hub app, if it doesn’t crash, you could enable the “HA discovery” after 15 minutes or such. ---
**Author:** ![JeroenD](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroend/32/14297_2.png) [@JeroenD](https://community.homey.app/u/JeroenD)\ **Post date:** [April 27, 2024, 3:09pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1284 "2024-04-27T15:09:00Z")
The data of variable aren’t published to mqtt unfortunately. Is there an other way to publish variables to MQTT? ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [April 27, 2024, 5:24pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1285 "2024-04-27T17:24:42Z")
_ **EDITED** _ april 30… AFAIK this is only possible with flows at the moment. First I created a text variable called ‘Seizoen’ With four flows, I update the var with the right season name; example of one of those: > ![Screenshot from 2024-04-30 15-33-30](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/0/303db3a86a08a659874a3ab128c0cb9b9d5e55b7.png) - Then, with this flow, I send the changed value to a custom (anything you like) MQTT topic with this MQTT Client card: > ![Screenshot from 2024-04-30 15-34-53](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/6/a6f8b1799917667e12cb25444e61fafda37eb347.png) - First test run the flow, to have the MQTT Client card creating the topic - Then check if it actually works: does it appear in MQTT Explorer? Something like this: > ![Screenshot from 2024-04-30 14-52-01](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/4/14dd1e48067f7a809f6fdb30bc2378a184a27b0a.png) If true, 1. Edit configuration.yaml and add this line (_don’t enter any leading spaces_) ```auto mqtt: !include mqtt.yaml ``` To compare, it should look something like this, when putting it to the other ‘!include’ lines ![Screenshot from 2024-04-30 15-23-49](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/2/92660064ec7e7c3c1f1fcb45491a4ef99e54357a.png) 1. Create a mqtt.yaml file in the same folder as the config yaml And enter this: ```auto sensor: # custom sensor, gets updated by Homey var 'seizoen' - name: varHmy_Seizoen state_topic: 'homey/variabelen/seizoen' force_update: true value_template: > {{ value.split(',')[0] }} ``` - _ **Make sure the `state_topic` is exactly the same as you used in the MQTT Client flow card** _ - - At `- name`, you can of course enter your own preferred name 1. Reload all yaml files, or just restart HA - Now the sensor should be present as MQTT _ **entity** _ (you will not find it as _device_!) > ![Screenshot from 2024-04-30 15-14-43](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/e/eeb9e560af8036e4ca0ecf5fec8bb46363906161.png) - View of the MQTT sensor value in HA: ![Screenshot_20240427-182722_Home Assistant](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/e/feedfd145e88b5bdb8932453a3b00e39270f947a.jpeg) ---
**Author:** ![JeroenD](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroend/32/14297_2.png) [@JeroenD](https://community.homey.app/u/JeroenD)\ **Post date:** [April 27, 2024, 5:42pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1286 "2024-04-27T17:42:24Z")
Thank you. I’ll try it that way. ---
**Author:** ![JeroenD](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroend/32/14297_2.png) [@JeroenD](https://community.homey.app/u/JeroenD)\ **Post date:** [April 30, 2024, 11:14am UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1287 "2024-04-30T11:14:52Z")
I don’t get it to work. Home Assistant doesn’t see the massages. Do i need to change the topic or the Qos? After installing mqtt on Home Assistant i didn’t change the setting. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [April 30, 2024, 1:42pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1288 "2024-04-30T13:42:56Z")
Owwwww, my bad Jeroen! 🫣 😊 It’s a bit more complicated as what I remembered I edited my initial reply! . > [@JeroenD](#): > > or the Qos? I like QoS 1 _MQTT Quality of Service (QoS) is an agreement between the message sender and receiver that defines the level of delivery guarantee for a specific message. MQTT provides three levels of QoS:_ - _At most once (QoS 0)_ - _At least once (QoS 1)_ - _Exactly once (QoS 2)_ [Source](https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels/) ---
**Author:** ![B3rt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/b3rt/32/9435_2.png) [@B3rt](https://community.homey.app/u/B3rt)\ **Post date:** [April 30, 2024, 8:01pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1289 "2024-04-30T20:01:29Z")
Is this app stil developed or even supported?!? If so where to report problems, in github nothing is happening… Here a crash ID ec73588c-63de-476e-8d83-de24b43e7fa0 The app keeps constantly crashing, after 7 or 8 tries it finally keeps running… When it is not developed or supported anymore is there someone who want to continue debugging an improving this app? The app itself is one of the best apps idea’s for Homey, I would be great if it was improved or even a official part of Homey itself… ---
**Author:** ![SvenRhein](https://avatars.discourse-cdn.com/v4/letter/s/e495f1/32.png) [@SvenRhein](https://community.homey.app/u/SvenRhein)\ **Post date:** [May 18, 2024, 9:43am UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1290 "2024-05-18T09:43:09Z")
same here: mqtt hub app keeps constantly crashing report =\> cf561424-c85d-4127-84c6-d166d5b23c58 ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [May 18, 2024, 12:21pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1291 "2024-05-18T12:21:55Z")
Users affected by the CPU limit issue can give some likes for this PR 😄 > > > Hi Harrie, > > I added app settings for send delay to be able to set individual d…elay and created this pull request for. > > The reason for this change is: > HomeyPro23 is processing messages so fast that the MqttClient app CPU usage is hitting 100% and gets stopped due to CPU warnings. MqttHub gets stopped due to Memory warning. > This delay makes both apps much more stable on HP23. I use 100ms delay now and got no stopped apps since this change. > > I changed the app settings page (new field at the end under "Performance" header). > The setting is passed creating the MessageQueue instance. So the new setting is read on app start. > I also added the app events for memwarn and cpuwarn and the handler functions. But it seems these events are not called anymore on HP23. I left the code to get a debug log if Athom is answering my comment on Slack and hopefully add these events for HP23. > > I forgot to uncheck the .gitignore file (Homey-CLI added the /.homeybuild/) and ./vscode/ folder (I added debug options for HP23). > You can ignore/revert these changes. > > I hope the fix is in your interest and you can add it to your branch and publish a new test version. > Many thanks in advance. > > Ronny ---
**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\ **Post date:** [May 20, 2024, 2:44pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1292 "2024-05-20T14:44:44Z")
I’d like to see a version where the default is not to add new devices to the published devices. ---
**Author:** ![Marco\_Bannink](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marco_bannink/32/33852_2.png) [@Marco\_Bannink](https://community.homey.app/u/Marco_Bannink)\ **Post date:** [May 23, 2024, 1:12pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1293 "2024-05-23T13:12:10Z")
Hi, I got an Tasmota based temperature sensor, which is broadcasting the temperature via MQTT. Via MQTT explorer i can see the temperature. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/f/cf8edc86b77a4daa7e18d34c63f965a79a61d9a8.png) I tried to configure an MQTT hub device to show this temperature. This keeps showing 0. I tried the following: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/3/73894a9ee90a0686e665570882517b2e87371509.png) Obviously i am doing something wrong 🙂 This is only my 2nd mqtt device, so still learning 🙂 Any suggestions? ---
**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\ **Post date:** [May 23, 2024, 2:39pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1294 "2024-05-23T14:39:45Z")
Looks like the stateTopic should be ”SensorZonBoiler/SENSOR” and valueTemplate ”Temperature” to pick the correct value from the json. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [May 23, 2024, 2:47pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1295 "2024-05-23T14:47:39Z")
Additionally: to test stuff to see if you got the topic & message right, you can use this MQTT Client flow trigger ![Screenshot_20240523-164559_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/0/b09cc5c34255362bf39581ad8efd04c85f27c028.jpeg) . Also be aware of the fact a `t` is not the same as a `T` ---
**Author:** ![Marco\_Bannink](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marco_bannink/32/33852_2.png) [@Marco\_Bannink](https://community.homey.app/u/Marco_Bannink)\ **Post date:** [May 24, 2024, 7:51pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1296 "2024-05-24T19:51:39Z")
Thanks for the tip, wasn’t aware of that card yet 🙂 The card is not triggering for SensorZonBoiler or SensorZonBoiler/SENSOR though. But i can see the messages coming in for these topics in the log of the mqtt broker app on homey:crazy\_face: Let me read in on mqtt further 🙂 ---
**Author:** ![HarriedeGroot](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/harriedegroot/32/56160_2.png) [@HarriedeGroot](https://community.homey.app/u/HarriedeGroot)\ **Post date:** [May 26, 2024, 6:02pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/1297 "2024-05-26T18:02:52Z")
Dear Community, I’ve been contacted through various channels—this forum, GitHub, and personally via WhatsApp, Slack, e-mail and even the Homey Helpdesk—regarding the status of the MQTT Hub app. I want to provide some context why I have been quiet lately. Regrettably, events during a freelance project for Athom have led me to reassess my involvement with the company. Athom presented me with a difficult ultimatum during this project, resulting in financial setbacks. Also, a few weeks ago, the Homey helpdesk asked for changes to the MQTT Hub App, which I agreed to, requesting compensation and necessary resources. However, they declined to provide either, only suggesting to make it open source (which it already is). These events have made it challenging for me to maintain my previous level of engagement and resulted in the loss of all goodwill towards Athom. Regarding the app, it’s important to note that my Homey is gathering dust in the closet, and I no longer use Homey or the MQTT Hub app myself. Thus, any time I invest yields no personal benefit. Moreover, the app is not (anymore) accepted by Homey in its current state, making it difficult for me to push updates. This is why there’s still a beta version; attempts to push it live in the past were rejected. This is also the reason why I didn’t put time into merging existing pull requests. I want to assure you that my intention is not to disparage Athom or cause any negativity. Hence, my prolonged silence and absence of responses on GitHub and this forum. Considering these events in the past and my current circumstances, I don’t have plans to transfer the app to another developer. My focus is elsewhere, and without adequate resources and compensation, it’s not feasible for me to invest the necessary time and energy into maintaining the app. Ofcourse the app itself won’t go anywhere and can just be used in the current state for now and in the future. Thank you for your understanding. Harrie [Previous page](https://community.homey.app/t/mqtt-hub-gateway/6766.md?page=63) [Next page](https://community.homey.app/t/mqtt-hub-gateway/6766.md?page=65)