Replies: 1 comment 1 reply
-
I like this idea. I don't have a physical parent device, but I use a sensor group to combine all my lighting energy monitors together and track that as a single item in the energy dashboard. Have you considered alternatives to having a parent-child relationship? And if so how do they compare pro/cons vs the approach you are proposing? Some ideas that come to mind are:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I propose adding ability for an energy device to designate another device as its parent, to improve correctness of energy calculations.
Currently if you have a monitor on a circuit, and another monitor reported by a device plugged into that circuit, the device is double counted, leading to wrong graphs and wrong untracked consumption. By denoting the parent the sum could account for the childs reported device when summing them together.
This parent-child relationship would be considered when rendering energy graphs, to visually show child consumption as a subset of the parent, and not in-addition to the parent. (See frontend PR for exact graph details).
Related PRs (already implemented but asked to come here first):
home-assistant/core#132616
home-assistant/frontend#23185
Beta Was this translation helpful? Give feedback.
All reactions