# \[APP\]\[Pro\] MQTT Server - Publish Homey Pro's devices as an MQTT server **URL:** \ **Category:** Apps\ **Tags:** app, official, mqtt, homey-pro\ **Created:** [August 4, 2024, 9:36am UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854 "2024-08-04T09:36:29Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![AppStore](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/appstore/32/88202_2.png) [@AppStore](https://community.homey.app/u/AppStore)\ **Post date:** [August 4, 2024, 9:36am UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/1 "2024-08-04T09:36:29Z")
# MQTT Server App This discussion is started to centralize all questions, answers and information around the app. ## Links and information: Regular version: > **[MQTT Server | Homey](https://homey.app/en-us/app/net.weejewel.mqttserver/MQTT-Server/)** > > Publish Homey Pro's devices as an MQTT server. Test version (if available): [MQTT Server | Homey](https://homey.app/a/net.weejewel.mqttserver/test/) ## Report Bugs for this App to the Developer Please use the link in the App Store and follow the community guidelines, the more information provided the faster it can be solved. ## Note: This topic is not actively monitored by the developer. Feel free to ask and discuss anything around the app here! ---
**Author:** ![AppStore](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/appstore/32/88202_2.png) [@AppStore](https://community.homey.app/u/AppStore)\ **Post date:** [August 4, 2024, 9:39am UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/2 "2024-08-04T09:39:30Z")
## Information about the app and how to use it, published in the App Store This app creates a MQTT Server (also called Broker), and publishes Homey Pro’s devices’ state to it. USAGE First, create a new user with a username & password in the app’s Advanced Settings. Then, download any MQTT Client and connect to Homey Pro’s IP address on your LAN. All topics should be visible automatically. To set the status of a device, publish a JSON-strigified value to `homey/devices//capabilities/`. For example, publish `true` to `homey/devices/abc...efg/capabilities/onoff` to turn on a device. NOTES The server also supports the ‘homie’ convention (see [https://homieiot.github.io](https://homieiot.github.io)) for compatibility with 3rd party MQTT clients. ---
**Author:** ![AppStore](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/appstore/32/88202_2.png) [@AppStore](https://community.homey.app/u/AppStore)\ **Post date:** [August 4, 2024, 9:39am UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/3 "2024-08-04T09:39:46Z")
Reserved ---
**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\ **Post date:** [August 3, 2024, 9:46am UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/4 "2024-08-03T09:46:50Z")
I need MQTT protocol also for getting data from my micro solar inverter resp. from a DTU ( **D** ata **T** ransfer **U** nit). An info which I posted just on Slack: > Before the MQTT Server App was released, I used the Broker and the Client App and it worked without any problems. > After the MQTT Server App was released (first without any flow cards), I installed this App, deactivated the MQTT Broker and activated/configured the MQTT Server App. Because there were no flow cards in the Server App available, I still used the MQTT Client App. And this worked also with no problems, the flow wasn’t never deactivated due to much executed. > After Emile added some flow cards for the MQTT Server App, I deactivated the MQTT Client App and rebuild the flow with the new flow cards from the Server App. After this was done it took just some minutes and the flow was deactivated due to much executions. > But as you can see at the screen shots, the flow is a duplicate from the “old” flow with the flow cards from the MQTT Client App. So nothing was changed, just the flow cards were replaced. > > In Short: > > - MQTT Broker + MQTT Client (Flow) = ✅ > - MQTT Server + MQTT Client (Flow) = ✅ > - MQTT Server + Flow = ❌ Additional infos: - Publishing interval micro solar inverter/DTU: 5 seconds - Sum of topics/messages: 15 ---
**Author:** ![Henrik\_Johnsson](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henrik_johnsson/32/13707_2.png) [@Henrik\_Johnsson](https://community.homey.app/u/Henrik_Johnsson)\ **Post date:** [August 3, 2024, 5:28pm UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/5 "2024-08-03T17:28:59Z")
I had to make a new attempt and I can actually see messages coming through to the MQTT Client but for some reason it doesn’t update my virtual device. Not sure what’s happening. Either way I have to retract my previous statements, the official app does work as a broker. When I can do it without upsetting normal operation I will modify my setup to use the cards from the new app. ---
**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\ **Post date:** [August 4, 2024, 9:56am UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/6 "2024-08-04T09:56:18Z")
If you “feed” the virtual device with the flow cards of the MQTT Client App, then you have to modify this flow with the cards of the MQTT Server App, of course. I proceeded as follows: – duplicated the flow with the flow cards from the MQTT Client App and deactivated the duplicated flow immediately – replaced the flow cards with the flow cards from the MQTT Server App – deactivated the MQTT Server App – activated the new flow with the MQTT Server flow cards The “old” flow with the flow cards from the MQTT Server App doesn’t need to be deactivated, because this flow doesn’t work anymore because the MQTT Client App is deactivated. At this point I had already deactivated the MQTT Broker App and the topics were already published via the MQTT Server App. ---
**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:** [August 4, 2024, 2:46pm UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/7 "2024-08-04T14:46:58Z")
The MQTT Client app takes considerable care to only start flows for messages to topics that it knows it will have a positive trigger for. The MQTT Server app starts the flow on _every_ single message that gets published, and will then check if the message is published to a topic that it should trigger on. Which is too late to prevent the flow from being rate limited. Even if a flow only has one trigger topic, if the broker receives enough messages the flow will be rate limited (even if none of those messages are actually published to the trigger topic). ---
**Author:** ![Henrik\_Johnsson](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henrik_johnsson/32/13707_2.png) [@Henrik\_Johnsson](https://community.homey.app/u/Henrik_Johnsson)\ **Post date:** [August 5, 2024, 9:02am UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/8 "2024-08-05T09:02:12Z")
Interesting information on the different trigger behavior. Anyway, I have had it running for a while now with the MQTT Server trigger cards and as far as I can tell it works as expected. In my particular setup the message rate is rather low and the majority are handled so the difference in triggers between this and the MQTT Client app shouldn’t be an issue. I seem to remember Athom having previously dismissed the idea to have MQTT support built in, which is a pity in my mind, but an official app is welcome. ---
**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\ **Post date:** [August 5, 2024, 9:43am UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/9 "2024-08-05T09:43:02Z")
Indeed very interesting. I have just done a test with the MQTT Explorer program. First I activated the MQTT Server app and observed the data traffic in the MQTT Explorer program for approx. 10-15 seconds: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/3/63b5ac9bea66060941074ed420c6689a8ef54180.png) (MQTT Server App) Then I deactivated the MQTT Server App and activated the MQTT Broker App and also observed the data traffic for approx. 10-15 seconds: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/9/99e6c6781e284ea6288fe0e4e1f8f839968977bd.png) (MQTT Broker App) In other words, the MQTT Server App processes a lot more data than just the MQTT Broker app, caused by **homey** and **homie**. I know that the MQTT Server App is a broker, client and hub in one. Are the topics **homey** and **homie** published more or less by the hub of the MQTT Server App? Are these data from all devices in Homey, e.g. to publish the for Home Assistant, @robertklep? ---
**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:** [August 5, 2024, 9:45am UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/10 "2024-08-05T09:45:38Z")
> [@DirkG](#): > > Are the topics **homey** and **homie** published more or less by the hub of the MQTT Server App? Yes. > [@](#): > > Are these data from all devices in Homey, e.g. to publish the for Home Assistant, @robertklep? Yes, although the Homie implementation is not compliant so I don’t know if it actually works with HA. ---
**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:** [August 5, 2024, 10:43am UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/11 "2024-08-05T10:43:54Z")
For a seamless HA integration, the HA Auto discovery is needed. Else you have to add all topics manually to HA 😅 PS: I asked Emile on Slack about this. If the MqttServer should replace the MqttHub in future, the community has to add this functionality to MqttServer (fork+PR). Same for device list/filter… ---
**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:** [August 5, 2024, 11:02am UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/12 "2024-08-05T11:02:08Z")
> [@RonnyW](#): > > For a seamless HA integration, the HA Auto discovery is needed. Else you have to add all topics manually to HA _Or_ proper Homie support. > [@RonnyW](#): > > PS: I asked Emile on Slack about this. You also got an answer 😛 ---
**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\ **Post date:** [August 5, 2024, 4:01pm UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/13 "2024-08-05T16:01:17Z")
> [@RonnyW](#): > > For a seamless HA integration, the HA Auto discovery is needed. Else you have to add all topics manually to HA 😅 HA was just an example, I don’t want to send any topics to HA, so no HA auto discovery needed… 😉 > [@RonnyW](#): > > the community has to add this functionality to MqttServer (fork+PR). Same for device list/filter… I would be interested to know whether Emile would really integrate the PRs and publish the app in the App Store if, for example, HA auto discovery was added. To be honest, I doubt that. Especially when a HA integration is involved. ---
**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:** [August 5, 2024, 4:21pm UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/14 "2024-08-05T16:21:28Z")
Well, he said: ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/d/7d99bfa2cb144ce94d8dd9750fe9281ff83bfb27.png) So I think he will add the PR if anyone is doing it. And HA was only an example for a similar use case where I also had the flow/memory issue. ---
**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\ **Post date:** [August 5, 2024, 4:29pm UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/15 "2024-08-05T16:29:05Z")
I read that, but I still doubt it. ---
**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:** [August 5, 2024, 5:53pm UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/16 "2024-08-05T17:53:01Z")
Same here. ---
**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:** [August 5, 2024, 9:17pm UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/17 "2024-08-05T21:17:39Z")
> [@RonnyW](#): > > So I think he will add the PR if anyone is doing it. Well, I think he actually means: you are free to fork the app, add the functionality needed for HA, and CLI install the app. ---
**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:** [August 10, 2024, 3:01pm UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/18 "2024-08-10T15:01:14Z")
> [@RonnyW](#): > > he said: > > ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/d/7d99bfa2cb144ce94d8dd9750fe9281ff83bfb27.png) Still it’s quite funny because there is this certain Athom app > **[Home Assistant](https://homey.app/nl-nl/app/io.home-assistant/Home-Assistant/)** > > Verbind je Home Assistant-apparaten met Homey he apparently forgot about 🤷‍♂️ In fact, a few days ago it’s updated, to support the (wild guess: South Korean) language ![Screenshot from 2024-08-10 16-55-44](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/6/a6de45d2a237b2021c6d9fcc2e3758b958ebb9a6.png) _This might sound cynical and all, but it’s not meant as such. It’s just funny._ ---
**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:** [August 10, 2024, 3:57pm UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/19 "2024-08-10T15:57:05Z")
> [@Peter\_Kawa](#): > > he apparently forgot about 🤷‍♂️ Nah, that’s just the other way around, from HA to Homey. I guess with the idea to make it easier for people to migrate _from_ HA _to_ Homey. And he doesn’t want to provide a way to make it easier to do that in reverse 😜 ---
**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:** [August 10, 2024, 3:59pm UTC](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854/20 "2024-08-10T15:59:34Z")
No, it’s for both ways, I quote ¨I’m not going to actively build _anything_ for Home Assistant" 🤪 But, the Athom HA app already has been built, fair enough haha [Next page](https://community.homey.app/t/app-pro-mqtt-server-publish-homey-pros-devices-as-an-mqtt-server/113854.md?page=2)