Closed Cyberbeni closed 1 month ago
Related #18268, #18012
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.
unstale
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.
Checklist
Describe the issue you are experiencing
My iPhone's region is set to Hungary, which means the decimal separator is a
,
instead of a.
, which results in "Message malformed" error when trying to input a decimal number into anumeric state
field inside an automation.Describe the behavior you expected
Either take into account the decimal separator corresponding to the user's region or allow a larger set of decimal separators in numeric fields (don't know if other regions have anything else besides
.
and,
) Using.
as a separator should probably always work regardless of region, to not accidentally break anything.Steps to reproduce the issue
Described above.
What version of Home Assistant Core has the issue?
2024.1.4
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
iOS HA app, iOS Safari
Which operating system are you using to run this browser?
iOS 17.2.1
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
No response