Allow Setting Value of Group-Object with Sending Changed Converted Value Only

[cornelius-koepp]

Will check based on changed value after conversion.

Calling valueModifiedSend(value, type) with different values will only send, if value represented in given dpt is not the same.

[thelsing]

Is there any reason that you marked this PR as draft? Do you still want to change something?

[mumpf]

In my opinion the forceSend argument should not be there, because there is already the value method, which clearly sends a value.

But if you add forceSend, it should be handled together with Uninitialized.

[cornelius-koepp]

because there is already the value method, which clearly sends a value.

The value(..)-method should be preferred when the knowlege of object value changed is not relevant.

forceSend [...] should be handled together with Uninitialized.

By handling the same way as Uninitialized, there would be no feeback of object value change and no advantage in comparison to value(..).

[cornelius-koepp]

Is there any reason that you marked this PR as draft? Do you still want to change something?

Yes, the 'draft' state was intended, to have the room for optimizations, feedback (for this hopefully generically usable extension of public group-object-api) and further testing. Optimization and feedback seen yesterday.

[cornelius-koepp]

Replaced by #272 with checking for update only.