Y-axis tick values ignore number formatting settings
Checklist
- [X] I have updated to the latest available Home Assistant version.
- [X] I have cleared the cache of my browser.
- [X] I have tried a different browser to see if it is related to my browser.
- [x] I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.
Describe the issue you are experiencing
The tick values of the Y axis in the detail charts always use the default number formatting of the language, not the number formatting preference of the user.
The screenshow shows two different values. The user profile has language "English" selected and Number format set to "None". The display of the current value in the top right respects the requested number formatting correctly (no thousand separator) while the Y-axis ignore the number format setting and instead use the default number format from the language.
Describe the behavior you expected
Y-axis tick labels of graphs should be formatted in the same way as the values that are to be represented in the chart itself. That means also using the thousand separators and decimal separators specified in the Number format preference of the user. Also observing the decimal point precision of the value would also solve other bugs.
Steps to reproduce the issue
- In user preferences - set language to English
- Set Number formatting to "None"
- Open detail pop-up for a sensor value that is currently over 1000
What version of Home Assistant Core has the issue?
2024.2.2
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
Firefox 123.0
Which operating system are you using to run this browser?
Ubuntu 23.11
State of relevant entities
No response
Problem-relevant frontend configuration
{
"version": 1,
"minor_version": 1,
"key": "frontend.user_data_165ca83b07d047408b7799e6136fe74e",
"data": {
"language": {
"language": "en",
"number_format": "none",
"time_format": "24",
"date_format": "YMD",
"time_zone": "local",
"first_weekday": "monday"
}
}
}
Javascript errors shown in your browser console/inspector
No response
Additional information
No response
Language = "English". Confirm the issue for "None":
For other formats - seems to be OK:
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Issue still exists in 2024.5.4
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Still active with 2024.8.2