ok that works… 
however next Problem
(for this specific one I can workaround by using the when its “down” card, but if I want to do that mid way or whatever it wouldn’t work…)
I consider it as a Homey standard. 
And appearantly the card makes not clear to the user what to fill in. An example might be included in the card information.
I consider it an “Athom doesn’t know the difference between a percentage and a ratio” situation 
IF the position has changed AND the position is “Unten” THEN …
Now you’re just executing on any position change.
yes that works with them completely down (no need for the position change one then, just unten), but if I would have a flow saying go 50% down and then tilt, there is no way to make it work?
It is a matter of language. 40% is 0,4 but one does not say “I open the window for 0.4” or “I speed up my car to 1”. And 40% in a computer is a text string whilst 0,4 is a number. Athom might introduce percentage fields in the user interface.
It’s a matter of units. Homey’s own documentation states that these capabilities’ units is “%”, so percentage, so the max value should be “100”. Instead, they made the max value “1”.
There’s really a difference between percentages and ratios. Yes, it’s trivial to convert from one to the other, but they are different nonetheless.
IF position has changed AND position is 50% THEN …
?
The app polls the API for events and updates the capabilities based on what has happened since it last polled the events. If you are connecting via Somfy cloud only (not enabled developer mode) then it polls every 30 seconds. If you do have developer mode enabled then the app will use local mode, where it will poll every 3 seconds. So, the trigger will fire when an event request is returned that show the position has changed. Therefore there is a certain amount of chance involved as to when the event fires. However, it should always get the event when it reaches the requested position.
So, as @robertklep says, add an AND card that checks if the position has reach the target. That can be done with a Logic card and the #Position tag:
I don’t understand…
Did you send them to 100% before executing the second flow?
yes I tried that too, and also from middle or whatever.
strangely it also sometimes work as intended, but I cannot understand why sometimes it just stops and tilts…
tried also this version with no big difference:
There is an AND cart like “Lamelles do move”. So maybe you have to wait until they don’t move by using AND “Lamelles do move” is FALSE
this makes so no sense 
little side note: how is there no then card to just stop the whole thing (like in the app control of the lamellas the middle button betweend the arrows)?
When you delete all flows except the first on, and send it to 50%, does the lamelle move to the right position? Because the idea is that the motor knows when to stop.
Ok. Now you have to find out which trigger to use which signals the lamelles have reached the requested position.
As test use the following flow:
WHEN position has changed AND position is 0.5 THEN send a push message “position reached” to Rocky Lonigro.
As polling is involved, it might take a while before you get the message.
Could you go to https://tools.developer.homey.app/tools/devices (you will need to login with your Homey account) and find the Lamellas you are controlling. Then copy the Driver name from the list and paste it here:
Once I know which driver you are using, I will check the code to try and figure out what is happening.
Driver homey:app:com.somfy.tahoma:io_exterior_venetian_blind
