# Flows scripting

**URL:** <https://community.homey.app/t/flows-scripting/9212>\
**Category:** Developers\
**Created:** [February 14, 2019, 10:01pm UTC](https://community.homey.app/t/flows-scripting/9212 "2019-02-14T22:01:29Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![unknown\_error](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/unknown_error/32/9109_2.png) [@unknown\_error](https://community.homey.app/u/unknown_error)\
**Post date:** [February 15, 2019, 9:48pm UTC](https://community.homey.app/t/flows-scripting/9212/21 "2019-02-15T21:48:24Z")

</div>

If the flow editor allows you to script everything then I’d agree. Scripting provides easy, manageable and scalable way to support complex logic flows.  
It makes a little sense to use visual editors to implement complex things.

---

<div class="post-metadata">

**Author:** ![unknown\_error](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/unknown_error/32/9109_2.png) [@unknown\_error](https://community.homey.app/u/unknown_error)\
**Post date:** [February 15, 2019, 9:51pm UTC](https://community.homey.app/t/flows-scripting/9212/22 "2019-02-15T21:51:01Z")

</div>

Glad to hear you think the same.  
So what’s your “final” solution?)

---

<div class="post-metadata">

**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:** [February 15, 2019, 9:57pm UTC](https://community.homey.app/t/flows-scripting/9212/23 "2019-02-15T21:57:12Z")

</div>

I postponed it, have a lot of other things to work on.  
But it’s still on the list!  
Hope a solution will pop up some day.

---

<div class="post-metadata">

**Author:** ![unknown\_error](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/unknown_error/32/9109_2.png) [@unknown\_error](https://community.homey.app/u/unknown_error)\
**Post date:** [February 16, 2019, 12:14am UTC](https://community.homey.app/t/flows-scripting/9212/24 "2019-02-16T00:14:28Z")

</div>

There’s a “Mosquitto MQTT client”, but it doesn’t support Homey v2.  
Is it possible to implement exactly the same functionality in MQTT Hub?  
So we need 2 things:

1. A trigger that gets triggered for a specified topic and contains a “message” token (just a string value).
2. An action that sends a message (a token or a value) to specified MQTT topic.

If we have those 2 things we could add a few special flows to use regular Homey apps.

---

<div class="post-metadata">

**Author:** ![unknown\_error](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/unknown_error/32/9109_2.png) [@unknown\_error](https://community.homey.app/u/unknown_error)\
**Post date:** [February 16, 2019, 12:19am UTC](https://community.homey.app/t/flows-scripting/9212/25 "2019-02-16T00:19:07Z")

</div>

I’ll try to add those 2 things into MQTT Gateway.

---

<div class="post-metadata">

**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:** [February 16, 2019, 1:23am UTC](https://community.homey.app/t/flows-scripting/9212/26 "2019-02-16T01:23:35Z")

</div>

The MQTT Client app has exactly those two flow cards.

---

<div class="post-metadata">

**Author:** ![unknown\_error](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/unknown_error/32/9109_2.png) [@unknown\_error](https://community.homey.app/u/unknown_error)\
**Post date:** [February 16, 2019, 2:13am UTC](https://community.homey.app/t/flows-scripting/9212/27 "2019-02-16T02:13:34Z")

</div>

I’ve seen them in the old MQTT client (“Mosquitto MQTT client”), but didn’t check the new one. Thanks for pointing that out to me.

[Previous page](https://community.homey.app/t/flows-scripting/9212.md?page=1)