MarkBryanMilligan / LanternPowerMonitor

The Lantern Power Monitor is a Raspberry Pi service, Java Web Service, and Android application that allow you to monitor every electrical breaker in your house, regardless of how many panels or breakers you have.
GNU General Public License v3.0
80 stars 26 forks source link

Multi Phase Solar Systems not calculating correct #30

Open tomilein85 opened 2 years ago

tomilein85 commented 2 years ago

I have configured a multiphase (3 1pole Breakers) solar in the app, but only the first is shown in the usage diagram of the day and taken into account for usage calculation. Of course this is again an issue with european 3 phase systems, but you will have the same issue with multiple solar systems at one place.

MarkBryanMilligan commented 2 years ago

The only way to monitor 3-phase currently is to put one hub on each phase so that the voltage that is monitored by the 12V input of the hub matches the phase that all of the CTs are on. (i.e. you need three hubs) If you use one hub and put CTs on a different phase (solar or otherwise), you might get a reading as the current flow will overlap the out of phase voltage and the aggregated P=IV calculations will give a (very wrong) number.

The way to fix this is to enhance the configuration to allow a way to specify the phase for each breaker. Then the hub service would need to take the phase into consideration when calculating the power, offsetting the voltage reading by 120 or 240 degrees. The most time consuming part is the UI enhancement in the app. Are you using Android?

Also, regarding that last part

you will have the same issue with multiple solar systems at one place

That's not true. The "Total Solar" calculation is guaranteed to be the summation of all breakers marked as being solar, regardless of how many there are or where they're located. If you hit the breaker dropdown and look at all three of your solar breakers, the summation of the kWh total for each breaker will match the "Total Solar" that's shown at the top of the app. Now, two of those three readings will be lower than the third because of the phase issues, but there's nothing wrong with the way it's all being added up.

tomilein85 commented 2 years ago

Hi Mark,

funny thing the main problem solved itself the next day (even if the numbers are not 100% correct due to phase offset). If you take a look at these two images, you get the feeling what was going wrong on the 17. ,starting with the 18. everything seems now to be fine (to give a bit of background information, I have sensors on the mains line to each floor and the solar is also connected to one of the floors (so possible enhancement would be to able to subtract the solar from the total usages, but also no problem if not, since I am going to feed the data via MQTT to openhab and forward it to the influxdb [so I can do there the math things]).

Thanks

Regards, Thomas [image: Screenshot_20220621-055512.png][image: Screenshot_20220621-055521.png]

MarkBryanMilligan @.***> schrieb am Sa., 18. Juni 2022, 15:33:

The only way to monitor 3-phase currently is to put one hub on each phase so that the voltage that is monitored by the 12V input of the hub matches the phase that all of the CTs are on. (i.e. you need three hubs) If you use one hub and put CTs on a different phase (solar or otherwise), you might get a reading as the current flow will overlap the out of phase voltage and the aggregated P=IV calculations will give a (very wrong) number.

The way to fix this is to enhance the configuration to allow a way to specify the phase for each breaker. Then the hub service would need to take the phase into consideration when calculating the power, offsetting the voltage reading by 120 or 240 degrees. The most time consuming part is the UI enhancement in the app. Are you using Android?

— Reply to this email directly, view it on GitHub https://github.com/MarkBryanMilligan/LanternPowerMonitor/issues/30#issuecomment-1159466143, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQOE53STZ2CAQI4TMKXJGXTVPXF3XANCNFSM5ZEF3E2Q . You are receiving this because you authored the thread.Message ID: @.***>