home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.62k stars 30.78k forks source link

Sum helper from „Group“ lost unit since last update and graph is not showing correctly #120310

Closed 3gfisch closed 5 days ago

3gfisch commented 4 months ago

The problem

Hi, i had a working sum helper from the group section to sum up my home power usage in watts (PV power + Grid power) both single sensors show up correctly but since the last 1 or 2 updates the unit is missing from my sum and therefore also the graphs look strange. See screenshots. I could not find a setting for the unit so I don’t know how to fix it, also I don’t want to lose data of this sum and make a new one in yaml (running since a year) Thanks a lot

Problem: IMG_0951

Helper configuration: IMG_0952 IMG_0953

The two inputs look ok as far as i can see: IMG_0955 IMG_0954

What version of Home Assistant Core has the issue?

core-2024.6.4

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

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

3gfisch commented 4 months ago

Had still the same problem after the newest update today. But i found a temp fix: in the group option i added an other power sensor (a Shelly which was off) to the sum. Applied it. Then the unit appeared again. Then i removed it again and the unit stayed but after reboot was gone again :( Then i tried to swapped the order of the 2 sensors that the Shelly is first then my sensor which is a sum helper also, but still the unit is gone after reboot :(

Any ideas what i could try or how to debug the problem further? Does it try to make the unit of this helper before the other helper is up and running or something like this? Thanks

3gfisch commented 4 months ago

Still the same bug after the newest update :( is this the right place to post this problem? Thanks

3gfisch commented 4 months ago

Still same bug with Core 2024.7.2 :(

Chilgl0rd commented 3 months ago

It is old issue... more than 6 months, it is annoying :-/ I have the same at any reboot for some Group Sensors (all energy sensors in W). Any update in the group configuration as "Ignore non-numeric" switch rebuild the Group Sensor to expected behavior with the right unit. Most of the Sensors come from ZWaze or Shelly. I may come from device class not set but how it is possible and how to fix it or force ?

home-assistant[bot] commented 3 months ago

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)

3gfisch commented 3 months ago

Found a workaround for me, i renamed the entity *_back and disabled it. Made a new sum with the combine helper and gave it the old entity name. Since its only power and from this energy is integrated with an other helper it looks like my long therm energy statistics still work :) IMG_0984

issue-triage-workflows[bot] commented 1 week ago

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.