I suggest that the card “Start a Flow” be extended to so parameters can be sent to a flow, as tags. Not only would this decrease the number of flows for most people, it would also elevate the Flow, programing paradigm to the exalted Turing complete language, eg it would be possible to write any flo…

Do you have any use cases where “the masses” would need this then, that they couldn’t implement with flows only? As @robertklep suggested, the use of variables will compensate for the lack of it, even though they are global. This would be a bad solution if you’d like to use recursion or trigger flow…

I also doubt, like @Edwin_D , that the “flow language” will suddenly become be Turing Complete just by adding the feature to pass arguments to flows.

Indeed, there is no way with the Start a Flow and the A Flow is Started to pass along arguments. Mainly because all arguments in a actioncard are always mandatory. So, if Athom changes the Start a flow Action card; which arguments types and how many would the have to implement? That is what i did…

I dont really understand this response: You don’t need to write javascript to use HOOP. You just use flowcards of the right argument type. These are the triggers available (and more): [image] Those can be triggered with condition/actioncards: [image] No need for JavaScript at all. And you o…

The simplest use case is where you would like to effect a collection of devices with, for the sake of argument three parameters, let’s say hue, saturation and intensity. As you argue the global parameter is an option, but an ill such. What if you have 10 different scenarios of said parameters with…

As I said to @Edwin_D a language is considered turing complete if it allows for calling recursively with parameters, eq functions. That my friend should be common knowledge among CS scholars.

Yes I have. And I have used it extensively until it broke my whole set up and flows. Groups stopped working and devices left groups etc. It might be stable but that does not mean it is without bugs.

The support for recursion isn’t mandatory for a system to be Turing complete (but hey, I only have about 35 years of experience as a programmer, so what do I know…). FWIW, Homey will stop flows from being recursive, even if they would accept arguments. But this entire discussion has a big XY smell …

You are right, a language does not have to be recursive to be turing complete, there are other options too. but you said you did not believe parameters/arguments to flow would render flows Turing complete. But I just have show one example for it to be true, not all. I am trying to suggest a simple …

Turing Complete with flows!?

Ideas & Suggestions

Edwin_D June 1, 2021, 6:29am 14

Have you seen the [APP] < group > (2.4.2 - Stable)?

Topic		Replies	Views
[REQUEST] Additional options for Flow logic Ideas & Suggestions flow	33	1389	August 1, 2021
Developing flows: tips and best practices Flows flow	22	3133	December 5, 2024
Love and hate my Homey - this should be fixed asap Ideas & Suggestions homey-pro	30	3009	March 2, 2022
[MCP] Generate advanced flows Questions & Help	6	360	December 19, 2025
From Home Assistant to Homey: Why an AI Flow Builder is the Next Frontier Off-Topic homey-pro , advancedflow	25	825	March 17, 2026

Turing Complete with flows!?

Related topics