#20 Dimup Decrease broken

[Tobias]

I have a Dimup rule that shut dim down. (from 80 to 0)
The log correctly tells that the dimup should decrease, but the value is increased then it breaks...

2016-02-07 00:21:29 [ INFO] Object: New value 14.9 for object eltern_ledstrip_b (type: 5.001)
2016-02-07 00:21:38 [ INFO] KnxConnection: write(gad=0/2/22, buf, len=3)
2016-02-07 00:21:38 [ INFO] Object: New value 15.3 for object eltern_ledstrip_b (type: 5.001)
2016-02-07 00:21:47 [ INFO] KnxConnection: write(gad=0/2/22, buf, len=3)
2016-02-07 00:21:47 [ INFO] Object: New value 15.7 for object eltern_ledstrip_b (type: 5.001)
2016-02-07 00:23:26 [ INFO] Action: Execute DimUpAction (decrease)
2016-02-07 00:23:26 [ INFO] KnxConnection: write(gad=0/2/22, buf, len=3)
2016-02-07 00:23:26 [ INFO] Object: New value 31.4 for object eltern_ledstrip_b (type: 5.001)
2016-02-07 00:23:26 [ INFO] Action: Execute DimUpAction
2016-02-07 00:23:27 [ INFO] Object: New value 31.8 for object eltern_ledstrip_b (type: 5.001)
2016-02-07 00:23:28 [ INFO] Action: Abort DimUpAction

my actionlist

          <actionlist type="on-true">                                                                   
            ...
            <action type="dim-up" id="eltern_ledstrip_b" start="0" stop="40" duration="350"/>           
            <action type="dim-up" id="eltern_ledstrip_b" start="80" stop="0" duration="90" delay="450"/>  
            <action type="dim-up" id="eltern_ledstrip_r" start="0" stop="250" duration="800" delay="450"/>    

            <action type="dim-up" id="eltern_ledstrip_g" start="0" stop="200" duration="700" delay="540"/>
            ...
          </actionlist>                                                                                   

Version of LinKNX is running on an OpenWrt (CC 15.05)

root@KNX-Gateway:/etc# linknx --version
linknx 0.0.1.32
- Clickatell SMS gateway enabled
- E-mail gateway enabled (with pthread support)
- LUA scripting support enabled
root@KNX-Gateway:/etc#

[Othmar]

The source code for decrease in DimUP action looks OK. Maybe the two different actions on the same object interfere with each other. Have you verified that a single decrease dim action works OK?
As a workaround you may set a delayed trigger on an internal object and have a separate rule to start the decrease action on change of this internal object.
You may open an issue on the new repository on https://github.com/linknx/linknx and propose a patch if you know how to fix the bug.