I think we stil got some misunderstandings.
You need:
- 1 thing that provides a channel for the rollershutter-item (not connected to any hardware). I use rfxcom-binding (because it’s already used in my installation) with an arbitrary id.
You can use the magic-binding for this virtual device if you don’t have rfxcom running. - 1 rollershutter item connected to this channel via rollershutterposition-profile
- 1 rule that listens to commands to that item and passes up, down, stop, 0, 100 (just like yours). Additionally you need to store the target position so that the event rule below is able to access it. I use metadata for that purpose. In DSL you need something different I guess.
- 1 rule that listens to change-events and sends stop as soon as the stored target position is reached (that’s the key-part!). Afterwards it deletes the stored target value.
In my example 4 posts above I combined the two rules in one rule but that’s a matter of taste.
Don’t get confused by my additional items (item_p, item_s). They’re only necessary because there is no easier way to send raw rf-codes with rfxcom.