No grid reading

Hi, I have an all in one system which has worked perfe tly up until few weeks ago. The issue i gave us the system is no longer calculating the grid readings.
The meters are working and consumption is indicated but not as grid, purely as consumption. My system is connected via ethernel but i suspect the problem is due to communication, not hardware.
The system still automatically charges the battery but will not discharge unless i force a discharge on the app and then adjust the rate in the cloud.
I have tried to update firmware (although the cloud says its up to date), but it fails.
I contacted the installer but they are no longer trading.

Could there be a simple communication error?

Thank you

Is there any digits on the right hand of the 2 meters? This is your grid meter located inside the Gateway

Hi, yes there are digits and they change every few seconds. I have tried unplugging tge ethernet cable from the gateway and doung thus makes no difference, so i presume the gateway is not communicating.
If i unplug the ethernet cable to the aio, i lose all livw data, so that part appears to be working.

ok, on the portal, go to Gateway, remote control
then top right is restart hardware

This will reset the Gateway
Switch bypass on for 10 mins, or youll be in the dark for 2 mins

Hi,

I just did that, i tried it at least 6 times, each time it said

Restart failed, inverter offline. Once it said Restart failed, inverter timeout.

I also tried sending a command, change the battery reserve, this failed.

Doing any of the above to the battery (aio) works perfectly.

The green light is on (on the cloud) and i have no errors or red lights on the unit.

Odd, as i am connected with ethernet, but as i mentioned, when i unplug the gateway ethernet cable, there appears to be no change.

I just realised that around the time this happened, i changed my contract with sky, i still have the same router, was always with sky, but upgraded to a faster contract. I didn’t think anything changed but now im wondering.

I looked at the connections to the router and there are 2 Givenergy connections. But they are not constantly visible. They come and go every few minutes.

Sorry, this is getting more complicated but it feels like progress. I haven’t got anywhere before now.

Thank you for helping, i hope you have an idea what it could be?

Cheers
John

Hi,

I have spent a few days sorting out the broadband, i have put port forwarding in place for the 2 ethernet connections and split the wifi, presuming the dongles need wifi at some point (although i can never see them on my router). I made sure the rule is for the 2 ethernet connections, not wifi.

The situation has not changed. Reading other posts, i have a feeling that the gateway is not communicating with the aio. Possibly due to the dongle being stuck/corrupted.
I have tried updating the gateway dongle using the installer app, it uploads but will not connect. So i was going to update within the WK hotspot but i am unsure exactly which version i should use.

It is currently 206 when viewed on the portal, looking in the hotspot, its a file named 5.02T.04

I have a file ready to load onto the WK hotspot but does anyone know if its the correct update please.

I have an aio 13.5kw with a gateway and a growatt inverter.

The file i have is

V206_GW_Dongle_Parallel

Thank you
John

Hi,
I may have a similar problem with my Gateway and AIO system. Did you find the problem and fix it?

Thanks,
Steve

Hi, i still have the same problem. I think my wifi was updated and it reset any speciak commands. Not realising, i tried to update the dongle firmware. It worked on the aio but crashed during the gateway update.
Now, my gateway is offline, if i try to connent it, it adopts my routers ip address and causes havoc.
If your issue is the same or similar, i would contact the installer. Unfortunately my installer is no longer trading.
My next step, if i get around to it, is to reconfigure the gateway, i believe disconnecting the DHCP in the gateway hotspot may solve it. But i have lost the grid readings, presumably due to the failed dongle update.