Helper Group Sensor ignores precision set in UI
Closed this issue · 3 comments
The problem
When you create a helper in the UI:
- Create Helper
- Group
- Sensor-Group
- Choose your Sensors, for example Humidity Sensors
- set your Type
- Save
Then Edit the precision lets say without any number behind the komma, should display just an INT. That setting gets ignored, in my case still displaying 71.3% instead of 71%
What version of Home Assistant Core has the issue?
core-2024.10.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Helper Group Sensor
Link to integration documentation on our website
https://www.home-assistant.io/integrations/group/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
The rest works as expected - so far :-)
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (group
) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of group
can trigger bot actions by commenting:
@home-assistant close
Closes the issue.@home-assistant rename Awesome new title
Renames the issue.@home-assistant reopen
Reopen the issue.@home-assistant unassign group
Removes the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-information
Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-information
Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
group documentation
group source
(message by IssueLinks)
I gave it a try and it works just as expected using the display precision in the entity options.
Can you provide some more info or even a picture(s)?
Hi @gjohansson-ST
I don't know what fixed it (several reboots in between then and now) but it seems working as expected now. I cannot reproduce it anymore. Nevermind, but thank you for your effort and quick answer, really appreciated!