WB/Control/PowerLimitation switch back to previous value

[kkeintzel]

If i write into the object "e3dc-rscp.0.WB.WB_0.Control.PowerLimitation" a value (e.g. 6, 10 or 16).
it will be switch back to the previous value, but it will be set correctly to the E3/DC-S10.

config:
iobroker (beta channel) up to date
e3dc-rscp: v1.1.0

iobroker-e3dc-rscp-issue.mp4

thx

[j64bit]

I find the same, also for the other control elements like SunMode.

[git-kick]

As I have no wallbox for testing, I forward this Issue to @ka-vaNu

[kkeintzel]

Following interesting stuff I found:
if you send the value 2times (like a doubleclick) e.g. via VIS-Button >> then it works!

[ka-vaNu]

OK, i'll take it, but i've got insufficient rights to assign it myself

[ka-vaNu]

It looks like a timing problem. My S10E with WB Easy Connect seems to send the EXTERN_DATA_ALG packets in a different order. The value in e3dc-rscp.0.WB.WB_0.EXTERN_DATA_ALG.PowerLimitation shows the value from the wallbox/S10E, the value in e3dc-rscp.0.WB.WB_0.Control.PowerLimitation shows the value set by the user. If the value is set via the app, the value in e3dc-rscp.0.WB.WB_0.Control.PowerLimitation is also set. I can disable this, but then it is no longer synchronous in case of an external update.

What do you think, how should the control-object behave?

[ka-vaNu]

Maybe I should merge the display object and the control object and leave the confirmation to the RSCP packet.

[git-kick]

There are similar cases where we have one RSCP tag for setting a value and another tag for reading the value, e.g. EMS.SET_POWER_VALUEand EMS.SET_POWER.
As the adapter follows the "no processing, just receive+decode or encode+send" policy, I would prefer to keep both tags visible in the object tree.
Otherwise, we will hide all those timing (and other) issues beneath the surface and we will have a hard time reporting and solving them.

[ka-vaNu]

Fix via PR #144, please test and review. The RSCP-Response does not longer update the Object e3dc-rscp.0.WB.WB_0.Control.PowerLimitation and e3dc-rscp.0.WB.WB_0.Control.PowerLimitation. So the timing-issue caused by different versions is fixed.

[kkeintzel]

Many Thx for your perfect job....