Dashboard Chart Metrics Over Time Agg does not show separator for Float/Double values

Hello.
I´m creating my first dashbord on Blynk Console and I have a problem with chart “metrics over time agg”. When I select a dastream with double/float values the chart shows the value without separator of decimals, giving wrong impression for users. In device table everything is fine.
Does anyone have any ideas?
@Dmytro
@Pavlo

Hi,
You have to select the correct Decimals in the chart settings:

1 Like

Hello, @Vitaliy_Veretko
Thanks for your reply.
I already selected the decimals format but still shown incorrect format.
Captura de tela 2025-11-17 093835

Chart in dashboard

Chart in device page

@BuildInnovation Hello. Thanks for report. I will recheck

@BuildInnovation please write org id or user email/id from this acc. I will check in your org. Not reproduced for me

Hi, @Oleksii-QA

The problem occurs in various organizations and in different templates, whenever I have float/double.

Captura de tela 2025-11-28 135923
It should show one decimal place. (26.9 / 24.3)

Dear @BuildInnovation. I know that you are our valued client. But I don’t know in which specific organization this bug is being reproduced. Please send me org id or user name from this org.

Hi, @Oleksii-QA
One suborg hierarchy is Iotiza - Iotiza - Sede
I have one dashboard there.

Need to solve this.

@BuildInnovation everything looks normal to me. Please provide a specific example of this error.

chart2

@Oleksii-QA

Organization Riserva Uno. No separator.

@Oleksii-QA Here you can see how the data appears incorrectly in the dashboard chart, but correctly in the device panel chart. It’s the same datastream.

Dashboard chart

Device console chart

Hello @BuildInnovation . We spent some time doing research. We’ve detected some strange behavior when changing the locale in a user’s profile. I’m not sure, but the bug you’re describing may be related to this. At the very least, when the locale changes, the value in the charts isn’t displayed correctly. We’ll try to fix this bug in the next deployment.

Best regards,
Oleksii

1 Like