Hi, Just wondering is anyone has an idea why I am seeing different PV readings within PredBat
See attached for the disparity
Note: I'm on a Three Phase 11kw system, so highly likely this is due to the 3ph setup, as this is a little behind in terms of maturity. That said - keen to help address the issues, so all help appreacted
Thanks
Trevor
Spotted once uploaded
So I can see
sensor.givtcp_td2335g007_pv_energy_today_kwh
GivTCP Energy PV Energy Today kWh
Which is displaying the 7.9
but
sensor.predbat_pv_today
PV Today
which looks like is part of the forecasting
Is this correct?
Not ideal they both are called 'PV Today'
TrevorD Is this correct?
https://springfall2008.github.io/batpred/output-data/#solar-forecast-data
As ever - the docs have got there before you. HT @geoffreycoan
TrevorD as @PianSom says, the predbat output sensors are the total forecast for today whereas the givtcp are the total solar generation achieved already today.
I've tried to explain all the sensors in the predbat documentation. Be aware that some of them contain 'actuals for today + forecast to end of plan' not 'forecast to end of today' or 'actuals for today'
If you take a look at the other predbat threads in particular those linked from https://community.givenergy.cloud/d/5411-second-year-live-on-predbat/1 are a useful start point for others that have been through the Predbat journey
Thanks Geoffrey, I had indeed read through all of that and spent time walking through the documentation, but I missed it.
I was focused on the labels rather than the variable names, and as they are not on the same screen, unless you are very observent, its easy to miss.
It would still be clearer if the variables included the word 'forcast' as this would avoid the confustion, but I guess once you know you know, and so no big deal.
It was just something that jumped out at me while I'm working through getting things running and checking the 3 phase setup.
Putting the screenshot together for the post, was what actually made the variable names jump out at me as being different.
Anyway - their not meant to be the same so all good...
TrevorD It would still be clearer if the variables included the word 'forcast' as this would avoid the confustion, but I guess once you know you know, and so no big deal.
Good idea. I have changed the Predbat code to include Forecast in the friendly name. It’ll be incorporated in my next pull request to the core code