givTCP v3.0.0 Weird log reading: [CRITICAL] - Function code 86 received. Gracefully handled

[SwiftRR]

givTCP v3.0.0 running on HAOS (on pi4) using HAOS Core: 2024.9.3. I run Predbat v8.4.9. I have a GE AC3.0 inverter with updated firmware which can run Pause controls.

I am receiving the log line below, about every half hour. The CRITICAL line is always followed by Pause mode being set which can be 'disabled'. 'PauseCharge' or 'PauseDischarge'.

I am also receiving regular time-out errors:

.... and self run errors

givTCP seems to recover from each of these glitches, as you can see from the log extracts above

Any idea what is causing these? I am ignoring but something isn't right. Are there bugs?

I have tried running v3.0.1 and v3.0.3 but these are unstable on my setup.

Rob

[PhillWalker]

I am seeing this error regularly too

2024-10-20 15:10:34,463 - Inv2 - read - [INFO ] - Starting watch_plant loop... 2024-10-20 15:10:34,481 - Inv2 - read - [CRITICAL] - Detecting inverter characteristics... 2024-10-20 15:10:34,578 - Inv1 - read - [INFO ] - Starting watch_plant loop... 2024-10-20 15:10:34,590 - Inv1 - read - [CRITICAL] - Detecting inverter characteristics... 2024-10-20 15:10:41,273 - Inv2 - read - [INFO ] - Publishing Home Assistant Discovery messages 2024-10-20 15:10:49,379 - Inv1 - read - [INFO ] - Publishing Home Assistant Discovery messages 2024-10-20 15:12:27,120 - Inv1 - transparent - [CRITICAL] - Function code 86 recieved. Gracefully handled 2024-10-20 15:12:27,130 - Inv1 - write - [INFO ] - Setting battery reserve 100 was a success 2024-10-20 15:15:12,287 - Inv1 - transparent - [CRITICAL] - Function code 86 recieved. Gracefully handled 2024-10-20 15:15:12,315 - Inv1 - write - [INFO ] - Setting battery reserve 100 was a success

v3.0.3, Giv AiO, latest firmwares

[britkat1980]

The critical message is not an error and can be ignored. It’s tracking a fw bug in the inverters which GE are aware of