[FEATURE] tag option - scale by script about fuxa HOT 6 OPEN

Hi Greg, the script to directly convert the value received via script is a feature that has been missing for so long, it would be great if you could do a PR with this feature.
I have a question, converting the input value also needs to convert the output value in the opposite way, right?

from fuxa.

I have a question, converting the input value also needs to convert the output value in the opposite way, right?

That short answer is that it could be. It would probably be good to allow the option. Just to make sure we are referring to the same thing:
You mean applying a script to the value AFTER it is returned from the device (the script would be applied in the device.polling/__updateVarsValue)?

Polling receive value from device -> script(value) -> tagValueCompose(scriptOutput) -> fuxa

I didn't require it for my current use case, but I can add it there.

Greg

from fuxa.

Oh to do that, I think we need to allow two scripts per tag. Input scale script and output scale script.... or we could require that each script has two input parameters. One parameter is the value, the other is an indication of read/write.

from fuxa.

Yes, I think that is better the first option (two scripts per tag), have the possibility to bind a script for read and a other script for write.

from fuxa.

OK I've got a bit further, it did end up touching a lot of code. So further testing is needed. Because the scripts are async, I had to await the result. The scripts are applied in device-utils.js tagValueCompose/tagRawCalculator. I chose to make those async. But this meant changes in every plugin to deal with that. Perhaps it would be better to do callScaleScript(...).then in tagValueCompose/tagRawCalculator. That way they would not need to be marked async, and the changes I made in the plugins to handle async tagValueCompose/tagRawCalculator would not be needed.

The script must have the first parameter named "value" of type value. You can add additional parameters to the script, values for those parameters must be filled in in the tag options dialog. This way the same script could be used for many tags, with the parameters used to differentiate. You can use the same script for read/write with different parameters. Parameters are passed to the script as strings, so if you want to use them as numbers a conversion is necessary.

This is what the tag options looks like now:

So far I've only tested with opcua.

from fuxa.

Hi,
Great, I will test it as soon as possible

from fuxa.