I would like to see a “always” section in the “Then” part of a flow (beside “otherwise”) for actions that needs to be executed always despite the “And” outcome.
Now I am adding duplicate actions for both outcomes.
The way you formulate your question results in the answer “Just delete the AND card”.
So maybe you can share your flow to clarify your question.
Of course there are also different actions based on the “And” outcome.
For example, in a lot of flow’s I have an action that logs to DynamoDB.
Let’s say:
If (motion detected)
And (lux < 200)
Then {
Turn on light
Log to DynamoDB
} Else {
Log to DynamoDB
}
I would like:
If (motion detected)
And (lux < 200)
Then {
Turn on light
} Always {
Log to DynamoDB
}
This is a very simple example, but if I have to update the *Log to DynamoDB" action, I have to make sure I update both actions.
Use advanced flows
Sure, but I can’t from my phone.
I know there are others way’s to accomplish this but my topic was a feature request, not a how-to.
I thought, in this section, I could ask for for features I would like to see added to Homey.
Apparently not.
This section is about discussing new features/ideas/suggestions with other community members. Athom don’t actively follow this forum.
Okay, sorry.
Then the moderator can delete my topic.
Where can I place feature request for Athom?
See the first post of the category: Ideas & Suggestions
Thanks.
@Jamie
Can you delete this topic? I posted in the wrong place.
1 Like
Flow, and especially normal flows, are a simplified programming environment. And it is not even an IF statement as the first part WHEN dictates when the flow starts.
So your request makes normal flows a little bit complexer, as normal flows shall be simple. So it might not be likely Athom will honour your suggestion.
By the way: introducing a concept like “ALWAYS” makes the syntax of the normal flows even more weird, compared to normal programming languages.
START WHEN motion detected
IF lux < 200
THEN Turn on light
ELSE
END
Log to DynamoDB
1 Like
Yeah, but you shouldn’t look at flow’s as code. If I want that kind of control I can use HomeyScript or my own apps. But sometimes (more often then expected) I want a quick solution which I can create/edit from my phone or tablet instead of going to sit behind my laptop and start programming.
I contacted Athom and the forwarded my idea to the development team. (No guarantee of course (probably none)) but hey, I might be lucky.
For a lot of my cases it would make a flow a lot more clean and maintainable.
It could also be a “Finally” section at the end if you want flow’s look like code.
But again, I think flow’s don’t have to look like programming, as a lot of user ain’t programmers.
START WHEN motion detected
IF lux < 200
THEN Turn on light
ELSE
END
FINALLY Log to DynamoDB
But I already got the hint I am at the wrong place.
As long as the syntax and symantics are clear 
Definitely.
But developers tend to look at everything as code (myself included), but as I know from my customers, not everybody does. 
“Uses cases” may be better to communicate with customers.
Exactly, and then is
START WHEN motion detected
IF lux < 200
THEN Turn on light
ELSE
END
FINALLY Log to DynamoDB
a solid use case.
Log what to DynamoDB, though?
Almost everything (state, level, lux, power usage, etc.) for dashboard and statistics.
“Log to DynamoDB” is just one use case. It can also be a MQTT, Pushover or PiP message.
I doubt that this all is information that is kept during the course of executing the different flow cards. You’ll also run into the issue that, for instance, trigger cards can provide tags whose values almost certainly are not stored anywhere (just saying that this feature may require rather big changes to how the flow system is implemented).
I think we’re getting off track, but at the moment a given script runs, I gather those information from variables which where set by other events/scripts.
That’s why I would like this feature, so I have to assign all variables once.
Duplicating an action is also not possible in the phone/tablet app (as I am aware of).
