i there, ive just started using dynamic min max values on my gauges, then i discovered that when ever i send a max value at above 1000 it adds a , after the first number

i have trid to format my numbers in all ways i can, but still.
anyway to combat this?
looks silly when the donut has a maxvalue of 1,234 when the actual value is 1234 
Best regards
Karl
If you lock for the payload with a debug node what you see?
Maybe you are using a old version of dashboard with this specific problem I don't know, the case is just for testing purposes I have tried to inject 1234 as number & as string and for me is working well.

For me... crtoss check to ensure what is really the payload or update your dashboard version
Regards
It seems i fucket it up with my own code 
{{value | number:0}} deleting the decimals, had a unwanted effect
will delete decimals before i send value to gauge
Looking for the obvious is sometimes the hardest
Best regards
Karl