You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem
Calculations for the self-powered pie-chart seem to be thrown off by VPP events. It seems to include powerwall energy exported to the grid as part of self-powered.
To Reproduce
Please paste a screenshot or steps to reproduce the behavior: below
Screenshots
pwd during the day of a VPP event:
pwd on a normal day without a VPP event:
Host System
xeon e3-1220 v3, 32gb ram, centos 7, pwd running in docker. docker compose v2.27.1, containerd 1.6.33, pwd v4.4.4
Additional context
query probably needs to be updated. i spent about 30min trying to decipher how it worked. please feel free to reach out if you need more details
The text was updated successfully, but these errors were encountered:
Yes, I knew the self-powered chart wouldn't be able to compute VPP events. I'll open this as a bug to address. I suspect the right approach to fix this would be to quantify the data earlier, possibly at time of capture or CQs and attribute it with the VPP event so we can ignore it for consumption purposes. That said, there are smart folks here that may have a better/easier way. :) I won't have time to work on this for a few months, but if anyone wants to jump in with some ideas, please do!
Problem
Calculations for the self-powered pie-chart seem to be thrown off by VPP events. It seems to include powerwall energy exported to the grid as part of self-powered.
To Reproduce
Please paste a screenshot or steps to reproduce the behavior: below
Screenshots
pwd during the day of a VPP event:
pwd on a normal day without a VPP event:
Host System
xeon e3-1220 v3, 32gb ram, centos 7, pwd running in docker. docker compose v2.27.1, containerd 1.6.33, pwd v4.4.4
Additional context
query probably needs to be updated. i spent about 30min trying to decipher how it worked. please feel free to reach out if you need more details
The text was updated successfully, but these errors were encountered: