Unprompted Battery Calibration run

Morning
This morning, i noticed that a battery calibration was running, and
the remote control log that the server started it automatically?

Has any one else spotted this on their system, either today or prior. This is a little annoying as we had good solar forecast today. If the battery needed recalibration, should it not be asking the user if and when they want it to proceed?

also noticed that there seem to up upto 10 individual charging/discharging slots on the server remote control page

Yes, mine has done a random battery calibration, although it's not in the logs. I'm right hacked off as it's trying to charge at peak rate... So I've reduced the charge rate to 0w. Not impressed.

FFS, done the same thing again today. 30 minutes before peak tariff, decides to dump itself to the grid.

My AC3 (firmware 3013) did a random calibration last week. No record on the portal. Just decided to fully discharge part way into a charging period. Wouldn't stop charging until it reached 100% so had to throttle the rate back to 1Kw until a cheap(er) Agile price period.

I had this problem as well. When I contacted GE they as usual blamed my the user (me) for using home assistant etc. So I have now severely throttled connectivity from my GE inverter to their cloud the and problem has gone away (I don't use their mobile app or web portal). I would happily disconnect the inverter from internet all together but I believe that would invalidate their warranty.

alfwro
Hi - how does using home asst etc cause this sudden dumping/re-calibration. My system has done it once so far after about a month post installation (6Sept GoLive).

Squid I suspect that they're just blaming it as its their software.

Despite there being no published method of remotely invoking a battery recalibration, and givtcp etc are using published givenergy api's, it's easier to blame someone else's software than say you don't know why it has happened.

Yes I worked in IT my entire career...

There is a theory that because the inverter TCP comms doesn’t do error checking that a command sent via HA can become corrupt on way to the inverter (which simply accepts it as a valid command)
For most registers it will simply do nothing but if it happens to bug on the register that sets off calibrations then it just runs it.

GE are aware it’s a thing and are keen to work out which command it happens with but because it’s so rare it’s really hard to debug.

All Ethernet packets have a CRC in them so you shouldn't see corrupt ones at the application level, they would just go missing. With TCP it should request a re-transmission. If you see corruption at the application layer your network stack is buggy.

I believe the beta firmware versions are using CRC now. It’s modbus not Ethernet.

nophead if you want to read more about it see: https://community.givenergy.cloud/d/2677-command-corruption

hoggy interesting. Does speak to poor software design that creates holes for this to happen through.
Wonder if the CRC enhancements will be part of all the firmware or just the latest kit (gen 3, AIO Etc)?