VariablesDevice automatic round?

---

Hello,
i have a variable with the gas price. Its filled external via Node-Red.
The variable value is something like “1.329” via unit is set to "€"
But the output of the VariablesDevices is automatic rounded.

1.329€ is shown as 1.33€ (which meight be ok), but 1.399€ is shown as 1.4€ (1.40€ meight be also ok).
Is this “works a design” or a bug? How can i make shure, that the outbut is as expected x.xx€?

@Raducanu
Maybe this will help you.

@thrusty said in VariablesDevice automatic round?:

Maybe this will help you.

Note, however, if a variable expression is used (e.g. calling the round function with arguments) the expression won’t be executed again when the referenced variables change.

But one step backwards:
Why is the VariableDevice Rounding and cutting off values?
In Variables the value is “1.399”. No calculation, round or else is used in the expression, but the device shows 1.4€

@raducanu said in VariablesDevice automatic round?:

Why is the VariableDevice Rounding and cutting off values?

Actually it is not the implementation of the VariablesDevice cutting off values, but it is the pimatic-mobile-frontend doing this. It has been a general design decision by @sweetpi to format number values into a more readable value.

The package used is “human-format”. Unfortunately, the frontend uses a pretty much outdated version of this and aligning this to the current version will require some refactoring of the front source code. Thus, quite a bit of code for handling “special cases” have been added in the past and so did I. On master there is a tentative fix which formats Euros with 2 fixed decimal places if the amout is less than 1000 Euros. Otherwise, the amount is given in k€ (“kiloeuros”) without decimal places.

This is probably still not what you would like to see it fuel prices where it makes sense to have three decimal places. I’ll will think about this and may come up with a more elaborated solution soon. Generally, I think users need a better way of controlling the rendition of number values in the frontend.

@mwittig
Thank you for the clarification.
To be onest, it’s a cosmetic issue. But whould be fine if i will get fixed someday

@raducanu said in VariablesDevice automatic round?:

To be onest, it’s a cosmetic issue. But whould be fine if i will get fixed someday

No worries. The issue had popped up several times in the past. Generally, I think users want to have more control over the way the frontend renders attribute values. My idea is to introduce a new xAttributeOption item which allows for setting a format override for an attribute. The format option will include multiple formatters and it will be extensible. The first implementation will include the following formatters:

• “raw” - provide value as is,
• “fixed” - print number with a fixed number of “fractionalDigits”,
• “localeString” - which uses Number.toLocaleString() to format localized numbers and currencies
• “uptime” - to print the uptime in a human readable way

All necessary properties (parameters, options) will be provided in a simplified name/value list