this work around might work, but Emoncms is not the only listener of the data.
I would like to avoid this kind of detour in all MQTT listeners.
Furthermore, the source is an Arduino.
I’m already struggling there not to lose any precision.
@nchaveiro, the ‘digit precision’ viewed versus stored confused me as well. Are the space constraints that big? At the pages Input, Feeds or Graps (moving over a graph or downloading a CSV output) there seems to be lots of space to have extra decimals . Maybe a lot less on a smartphone, but certainly not on a widescreen.
The workaround of @Paul to work with a dashboard helps, but providing enough decimals on the other pages seems better to me.