AIO on FW v8 Randomly going off-line

Hi everyone. I’m looking for advice / help.
I have an AIO & Gateway, installed November last year.
AIO Software Version D0.609-A0.609
Battery Firmware Version 8
Gateway Version A0.005
On doing an update in January the Battery Firmware went from 7 to 8. After this, the battery started to drop off line, seemingly at random. After support from the installers, who consulted with GE, they were able to revert the Battery Firmware to 6. All was stable for a couple of months.
Last week I decided to check the inverter web page and it stated an update was available, which I then ran. Again it updated the Battery Firmware to 8. Again, every 1 or 2 days, the battery is dropping off line. I have to manually recycle the CB and press the power button to bring it back online. Each drop off-line is accompanied in the log with a “BMS Communication Fail”.
Is there a way to fix this without downgrading the Battery Firmware?
If not, is it possible to do the downgrade myself? (My installer is being a bit slow at responding this time).
Why hasn’t the latest firmware (v8) been fixed? Or, could this be a symptom of some other hardware / firmware / software issue in my system?
Thanks for any info and advice.

Mine goes off line all the time 5 mins online 5 mins off line rinse and repeat, it still seems to be sending data to cloud though as my charts and other data seem fine.

I has a similar experience but it seems like it was just the comms going offline so the app and portal could not communicate with the AIO. I found that going directly to the IP address of the battery and gateway I could restart the comms which brought everything back to life without restarting the battery or gateway. I asked GE to investigate and now the problem seems to have gone away. Not clear if they changed anything or just debugged.

Hopeful In the end I contacted GivEnergy Support directly - they were excellent and very quickly downgraded the battery firmware from v8 to v6 and I've had no problems since. Waiting for V9 to come out before I try again.

biggles621 If you are having the comms issue there is a specific fix for this that I can attest works quite well but it will need to be requested when the system is online, facebook is quite a quick method to get it applied if you run into this issue again.

Hopeful They may have applied the comms dropout fix, I got to the point where I was losing comms daily and it was driving me nuts til Paul applied a fix for it and its been faultless since.

Jellybaby Thanks, whatever they did it does seem to have worked

Great you had it fixed (I also have it but have not been too fussed - I actually think its more a account to cloud issue rather than a battery to server issue as my API's are still moving when its offline on dashboard)

But for information I have moved onto 9 and can confirm the issue hasn't been fixed within that.

I have an AIO on Ethernet NOT WiFi and in the portal the dot is green, however this is what is says at 11:32

Last Online Time
2024-04-12 10:06:42

The Gateway is always Yellow and at 11:32 it says

Last Online Time
2024-04-12 10:06:27

I have not had the comms update. Should I request it or is it rolled into the latest FW

DreadorUK For me the Portal and App could not reach the AIO but it carried on doing whatever it had been told to before the comms went down. It weird because you could always reach the gateway or battery from the IP address so it wasnt a local "network" problem but without restarting the comms from the Ip address device menu (which is not, as far as I can tell, the same as restarting from the portal/app option) it would not come back online.

Hopeful It was a software issue evident by one piece of firmware sorting it but it wasn't intended on that use but whatever works lol

Daveb01 Last online is always out of whack, ignore status of Gateway its just the inverter and portal getting updates on info that you want to keep as that means its still able to be accessed via home or away mode on the app and via brower.

If the portal stops getting updates its likely the comms have gone, if you don't have that issue leave it as is.