Issue with GivTCP sensor data and HomeAssistant/Predbat

Hi
I am a happy user of HA with Predbat controlling my 13.5AIO. A few days ago, I noticed that my predicted load in the Predbat plan was lower than expected and this got steadily worse.

This morning, my predicted load figures were laughable, so I looked in the logs and saw lots of messages of the form "Historical day x has no data". I immediately checked a few of the GivTCP sensors defined in my apps.yaml and from the HA side, they appeared to be functioning normally i.e. I could see sensible graphs for battery load, house load etc. I checked that my apps.yaml file had not changed - and it had not done so for many months

Whilst browsing apps.yaml, I came across the "ge_cloud_data" entry which was set to false - this was as expected since I have been using my HA and GivTCP locally for a year or more. I had however previously used the cloud data since I did have the API configured.

I enabled the cloud data and when PredBat restarted, the expected load was back as expected. I therefore suspect there is an issue in how predbat is collecting the GivTCP data - or how GivTCP is presenting the data.

Ideally, I would like to figure this out and revert back to locally provided GivTCP data, but can manage for now on the cloud provided data.

I have no idea where to start looking for the solution to this problem

Any thoughts

Hi, yes there is a running thread on the "second year live on predbat.." discussion

Its the latest givtcp update that has caused the issue

Weasel There is a fault in GivTCP 3.4 where it’s not presenting load_energy_today_kwh correctly to HA. A number of people have reported this.

It comes from Mark trying to fix a bug in GivTCP 3 whereby some of the daily sensors do not reset to zero precisely at midnight which causes problems in the Energy dashboard. The fix isn’t working right for whatever reason.

There was a new version of GivTCP dev 3.4.16 released last night that might fix the problem, certainly my load energy sensor went down to zero after install, but I’d suggest you either restore back to an older GivTCP version OR use the GivEnergy cloud data as a workaround.

Thanks - I am happy using the cloud data for now. I had also noticed that my {geserial2} value was in uppercase whilst my HA sensors were in lower case and wondered whether that might be the root of the problem.

Weasel I had also noticed that my {geserial2} value was in uppercase whilst my HA sensors were in lower case

Someone else had a similar configuration and I advised them to change it to lower case to match the HA sensor name. I updated the documentation to say to use lower case but I think predbat copes with it in upper case

geoffreycoan I too think that it copes with either case because it has been working fine for over a year.

I will revisit this once I have a newer version of GivTCP installed, but for now I have other issues

Now I have switched to cloud data, I am having fewer errors and little or no gaps in my historical data.
This confirms that every cloud has a silver lining.

I installed GivTCP dev 3.4.17 tonight and it looks like it might have fixed the load today energy sensor issue.

The sensor on both of my inverters changed to what I could see on the BBC basic inverter app, and then at midnight reset to zero correctly

Thanks. I eagerly await its release

Fingers crossed. My HA / automations keep crashing every few days even though I've reverted to 3.3