Too many updates due to float change

[rawmean]

Many of the fields that telemetry streams are floating points and even when we set the interval to seconds or minutes, they do update. Theis did not matter much before but now that we are going to pay for these updates, can you please fix it so they don’t update each time a value at the 10th decimal digit changes? Here is an example:

[Bre77]

I also have this issue, and as you can see with Inside Temp, the actual usable value only has 1 decimal place, the rest is floating point error. I don't think we shouldnt be charged for changes in floating point errors.

[bassmaster187]

They will be charged / sent, even if they didn't change. At least for PackCurrent

[Urkman]

We already had this in another thread...
Some values are send only on change, some values just change their values back and forth and some other values are send over and again without any change...

The whole system is totally unreliable and simply not production ready :(