Predbat Conflicts

[danmoo117]

Hi all, I've recently noticed in the metrics tab that I'm getting several control conflicts every day. I'm not sure when this started but it could have been around the time givtcp_rest was reworked a few releases back.

It's worth noting I have GivTCP and MQTT setup and these entities are set in the apps.yaml, however, it's my understanding that givtcp_rest is the primary controller if set, which it is. I'm sure I read that GivTCP + MQTT entities should remain set as a failover, which is why I haven't commented them out.

I thought these conflicts might be related to some hard set values on the GivEnergy Hybrid Inverter (gen 1), but when looking at these settings via gvenergy.cloud I can't see these.

I've troubleshooted with ChatGPT but it's not assisted very well. Any ideas how I can fix this? Thanks.

Here are some screenshots.

Predbat Conflicts

Givenergy Cloud Logs

GivEnergy Cloud Settings

[gcoan]

my guess is that these are transient errors communicating to the inverter from givtcp (would be interesting to see what is in the givtcp log) and when these occur a zero time gets written. The AC charge end time flips from 05:30 to 00:00 and back again within a minute, indicating to me that Predbat gets a bad value and retries.

Are you on the latest givtcp version? 3.6 is out in beta now somight be worth trying that to see if it reduces the errors

Looking at my own log I see 6 errors, idle end time isn't supported by the inverter so where these come from, I don't know

Not particularly worried about them in my case