# Homey pronounces numbers as time **URL:** \ **Category:** Flows\ **Created:** [September 25, 2020, 10:24am UTC](https://community.homey.app/t/homey-pronounces-numbers-as-time/35036 "2020-09-25T10:24:54Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Paul\_Kessels](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paul_kessels/32/3750_2.png) [@Paul\_Kessels](https://community.homey.app/u/Paul_Kessels)\ **Post date:** [September 25, 2020, 10:24am UTC](https://community.homey.app/t/homey-pronounces-numbers-as-time/35036/1 "2020-09-25T10:24:54Z")
I have a flow that calculates the energy usage at the end of the day and then mentions the amount out loud: “Today you spent Euro on electricity and Euro on gas.” Where and are number values. However, Homey pronounces the numbers as time values. For example if is having the value 2.10, it will say “10 minutes past 2 Euro”. Is there a simple way to let Homey say “2 comma 10” instead. Or do I have to make it to different variables, one for the decimals? ---
**Author:** ![danone](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/danone/32/115743_2.png) [@danone](https://community.homey.app/u/danone)\ **Post date:** [September 25, 2020, 11:16am UTC](https://community.homey.app/t/homey-pronounces-numbers-as-time/35036/2 "2020-09-25T11:16:38Z")
Strange. Are you using a tag I guess for your number values? Because I’ve just done a test with the following results: - “Hello, 2.10” where homey says “Hello, two point one zero” - “Hello, 2:10” where homey says “Hello, two ten” - “Hello, 2,10” where homey says “Hello, two comma ten” ---
**Author:** ![Paul\_Kessels](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paul_kessels/32/3750_2.png) [@Paul\_Kessels](https://community.homey.app/u/Paul_Kessels)\ **Post date:** [September 25, 2020, 11:26am UTC](https://community.homey.app/t/homey-pronounces-numbers-as-time/35036/3 "2020-09-25T11:26:04Z")
Ah, I discovered what is wrong. Homey says it correctly. But it is google that does it wrong (through the Google TTS app). Must be a bug in that app.