Growatt inverter using Grott - Datalogger un-sets its Server IP every 10 minutes

Third party integrations
1

Hi All, first post so please be kind :slight_smile:

I have been using HomeAssistant for a while and have managed to find everything I need online, but this one has me stumped even after lots of searching.

I have a Growatt Inverter (SPH3~6k TL BL) with a datalogger (ShineWIFI-S) setup with Grott add-on (Beta branch 2.8 v0.1.7). HA is 2024.3.3 running on HA OS 12.1.

This has been working successfully for months without any issues until I went away last week and came home to it not working. The immediate suspect was the wi-fi datalogger, mine has a habit of losing the Wi-Fi every now and again, so reconnected that and it’s working OK sending data to Growatts Servers but not Grott.

Investigation showed that the datalogger server IP wasn’t set, so went into Growatt web site and re-set the server IP of the datalogger to my internal 192.168.1.19 address for the Grott server. Bingo, all worked, no problem.

10 minutes later it stopped. This now happens completely consistently, set the IP and the datalogger uses it for 10 mins (exactly, I have it set to 1min updates and it always sends 10 to Grott, can see them in the logs) then it ignores the IP and reverts to sending data direct to the Growatt cloud servers.

I have tried resetting the datalogger dongle completely, gone into local mode on it and set the IP directly using the local app. Everything works for 10 mins and then reverts.

I can see that in grott IP mode the data is getting looped through Grott to Growatt-Cloud and growatt is getting the updates, can see these in the growatt website.

Have tried all the basics, reboot HA, install latest Grott, uninstall Grott, re-install Grott.

Any thoughts? Anyone experienced anything similar?

1 Like
2

Found the solution, it’s an Australian issue, they opened a new server a few weeks ago and if it doesn’t get data then it re-sets the server IP to default. Grott doesn’t recognise the new server yet.
If you are in australia and you’re getting this set the Grott setting ggrowattip to 47.91.92.81 (the new Au server) you can only see this setting under Grott “Show unused optional configuration items”

More info in this post Shinewifi-x problem - URL resetting to default - data not flowing through GROTT ¡ Issue #542 ¡ johanmeijer/grott ¡ GitHub

2 Likes
3

@Ramshaw you legend! I’ve been struggling with this for about 2 weeks and was about to flash the ShineWifi module.
Such an easy fix in the end, thanks!!!

4

Nice work, thanks for posting it!

That IP address didn’t work for me, but I did a packet capture and found out that it was talking to 3.24.103.55, which has been working now for about 15 minutes.

Thanks again!

5

Excellent find! I had the same problem in Germany. I configured the IP server.growatt.com is resolving to for me. We’ll see if it works. If all fails I will enable the gblockcmd option.

6

Hi Andreas,
So you manipulated to grott.ini from the old IP address to “server.growatt.com” ?

7

As I said, I put in the IP that server.growatt.com resolves to (from my location). I’ve read that using a DNS name is not fully supported in Grott yet.

1 Like
8

I just did the changes for me as it wasn’t working the last few days.

Step 1: On windows I used the command line to ping ‘server.growatt.com’. There I got the IP adress which was the same that I got in the network tab from Firefox.
Step 2: I use the Grott add-on and in the advanced settings under configuration (which is the same as grott.ini) I put the above ip in the field ‘ggrowattip’.
Step 3: Then I went to server.growatt.com where I put the internal IP of my server in the data logger settings (like explained here Rerouting Growatt Wifi TCPIP data via your Grott Server ¡ johanmeijer/grott Wiki ¡ GitHub ).

Now it’s working again.

1 Like