The second flow will run several times as the position is changing all the time till 80%. Appearantly the first time this flow runs, the AND is already true. Then position is not the actual position but the position the lamellas are sent to. @Adrian_Rockall will find out.
There is also a card “WHEN state has changed”, which might do the job but which states are available? Stopped, started, moving, ……?
Is there a state which indicated the lamellas are at the requested position?
no there is just up down and inactive
do you need any other info @Adrian_Rockall ?
Not sure as the log came in after I went to bed, so will take a look when I get home.
You should have the buttons for Up / Idle / Down
For the Flow trigger occurring straight away, I can only assume that setting the position via the Flow action is triggering the card. As that is a built in capability I can’t see the internal workings and I don’t have any IO blinds to test with. So, could you open the app settings and select the Information Log tab, then enable the lo:
ID: 956319724
so for the below flow i did click square first it started all the way down. went all up
then i clicked circle - it went down 5 cm and stopped.
then i clicked circle again and it went down all the way
and yes I have the buttons, but I cannot find a command for a flow to “use” the stop button?
The card to use the stop button is the set state:
There is a bit too much going on in that log file for me to get a clear picture of a complete cycle as commands are clashing into each other. Could you clear the log and then just get the screen to do one action, say move down or move up, but only do one between clearing the log and sending the log. What I want to see is the last message that comes through at the end of the move.
further i did this: disabled the flow completely and sent the thing all up. then enabled log and send them full down with phone command
log: 956319724
hope with these you can figure it out?
Thanks for your patients and sending the data. Unfortunately, the first two logs still contain a lot of clashing data, presumably because the Flows are still interacting. The third log didn’t show the final messages as I guess you sent it before the last polling event had occurred.
However, I have remembered that there should be a “A command completed” trigger card for the device which passes in to tags, ‘state’ and ‘name’. The state tag is true if the command was successful and the name tag contains the name of the command. Maybe you could try that trigger Card and compare the name tag to see if it is your move command that has completed.
Note: If you have a Tahoma or Connexoon, then you can enable developer mode in your Somfy account and that will give you local access to the box. The polling interval is then 3 seconds.
I just activated dev mode.
I already have that card in there right? so now you mean to add using some of those state green tag:
I run it one more time from full top to full bottom new log: 956319724
That does not look like status of “WHEN command completed”.
Connect the card “WHEN command completed” with the logic card first, only thén you will see the tags from the WHEN card (of course 
).
Command name is text, so the logic card you have chosen can see it.
The other tag is a boolean, so requires a logic card that supports true / false.
You won’t see a value there because it is only available when the Flow is triggered.
so what am I supposed to try now?
did the other log i sent you help in any way?
So add the Command completed trigger and check the command tag is equal to the required value, e.g. “Move Position 100”. I can’t be sure that’s the exact text as I don’t have the same device as you, so maybe log the tag to the time line to see what it is.
Once the correct command is identified, then tilt the screen.
No, the Command Name. You will need to make sure it is the move up / down command that completed and not the tilt.
and I can somehow see that command name when running tests?
For testing, link to the Then card ‘Timeline’ ‘Create a notification with’ and put the Command Name local tag in the box.
Then when the card triggers it will write the text to the time line.
