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
For what it's worth, with a US split phase system, simultaneous import and export is possible. While this has no effect on the overall net values, it can matter if someone is tracking costs, or wants to see a bit more accurate data, during early/late hours or during poor weather.
The lambdas could be made a bit more terse - i.e. something like float l1watts = (l1watts < 0.0) ? 0 : id(houseL1Watts).state; should be valid, I think.
While this is a bit of a Fool's Errand at some level, I was able to maximize my consumption during poor solar conditions by swapping two breakers around to balance the house "idle" loads between phases.
I figured I would post this here as an issue in case someone else comes across it and wants to track things a bit more accurately. Thank you!
The text was updated successfully, but these errors were encountered:
You might be able to help me with my current issue that is potentially related to this. I'm tracking power being pulled from the grid, power being generated by my solar panel with excess going into my batteries, and the total home's load at any given time.
For some reason, my tracked/calculated power imported from the grid starts becoming erratic when solar power starts being generated in the morning and the excess starts going into the batteries. The answer may lie in something you posted here.
For what it's worth, with a US split phase system, simultaneous import and export is possible. While this has no effect on the overall net values, it can matter if someone is tracking costs, or wants to see a bit more accurate data, during early/late hours or during poor weather.
I modified the examples from https://github.com/CircuitSetup/Expandable-6-Channel-ESP32-Energy-Meter/blob/master/Software/ESPHome/6chan_energy_meter_house_solar_ha_kwh.yaml as follows, using values from each phase separately (noting that I use "import" instead of "positive" and "export" instead of "negative" as I find those terms to be a bit more common).
The lambdas could be made a bit more terse - i.e. something like
float l1watts = (l1watts < 0.0) ? 0 : id(houseL1Watts).state;
should be valid, I think.While this is a bit of a Fool's Errand at some level, I was able to maximize my consumption during poor solar conditions by swapping two breakers around to balance the house "idle" loads between phases.
I figured I would post this here as an issue in case someone else comes across it and wants to track things a bit more accurately. Thank you!
The text was updated successfully, but these errors were encountered: