power-flow-card-plus
power-flow-card-plus copied to clipboard
Main value in "Individual" does not respond to decimal value (v0.2.0-beta).
Describe the bug
Installed version: v0.2.0-beta Main value in "Individual" does not respond to decimal value (a period is displayed instead of a comma).
To Reproduce Steps to reproduce the behavior:
- Create Individual with same entity for main and secondary
- Try changing decimal values for both
- Main value does not respond to decimal value
Expected behavior A clear and concise description of what you expected to happen.
Smartphone + Desktop :
- Device: [all]
- Browser [all]
Additional context Add any other context about the problem here.
Please make sure all of this applies and check the checkboxes, by writing "X" inside of them.
-
[x] I understand that this is a channel for reporting bugs, not a support forum (If you need help configuring the card, go to: Discussions).
-
[x] I have the latest beta version of the card installed.
-
[x] I have cleared my browser cache after installing, updating and configuring the card.
-
[x] The issue is not related to the UI-Editor not being rendered: "s.entries is not a function". This is a known bug, and is caused by Card Mod. Check the warning this readme section for more information on how to fix it.
Can you tell me the raw state of the entities shown in the developer tools for these entities? Seems like they are just very large numbers, because the other entities are respecting the commas
Thanks for the feedback and support. Installed version: v0.2.0
What I noticed today: if I leave Unit empty, comma is displayed and decimal works. With Unit value it doesn't work, (I see a point) see for yourself.
I hope this helps
not sure, but #560 might've also fixed this. I'll merge it for 0.2.1, we'll see if it fixes the issue
Thanks, let's wait and see.
Just released version 0.2.1, can you confirm the issue is now fixed?
Unfortunately the problem still exists.
Hi, I have similar issue with 0.2.2 now. For me 380m³ is shown instead of 0.38m³ even though clicking on the value I get the correct value. Perhaps the source issue is the same...
I have also found this issue:
Problem is still not solved.