@Marksfish wrote:
This AI lark is very clever isn't it?
I'm currently using Grok for free. It will remember your conversations if you sign-in using your email address, and allow you more questions each day (compared with asking questions when not logged in), but not as many as if you pay for a subscription.
For your inverter/logger debugging process, just explain to it EXACTLY what you have, what you are trying to achieve, and what you are currently struggling with, and it will produce a page of what to try next.
If you don't believe it, or don't understand, just tell it and it will correct itself, and explain more clearly, etc
In your debugging process, keep adding to the conversation, as it will remember the previous context, and produce solutions to your current level of progress.
For example, I just asked it about your 10.10.10.4 IP address, and it came back with this lot -
10.10.0.4 is almost certainly the server address the ShineWiLan-X2 is configured to talk to (the Growatt cloud / MQTT endpoint), not the datalogger’s own local IP address on Mark’s home network.
Where the address comes from
The ShineWiLan-X2 has two completely separate IP-related settings:
- Its own local network IP (what Home Assistant needs for Modbus TCP on port 502)
- Normally obtained automatically via DHCP from the home router.
- This is the address that should appear in the router’s client list (often with hostname = the stick’s serial number).
- The remote server address it reports data to
- Default is the domain mqtt.growatt.com (or the equivalent regional Growatt server).
- This can be overridden to a raw IP address in the stick’s advanced configuration.
- 10.10.0.4 is a private (RFC 1918) address, so it is not reachable from the public internet and is not a valid Growatt cloud server. It was almost certainly set manually at some point (previous installer, test, wrong copy-paste, or a leftover static-server setting).
That is why Mark sees the stick “connecting externally to 10.10.0.4” — the stick is trying to push data to that (wrong) server IP.
What it should be
- Local IP of the stick (for Home Assistant): whatever the home router assigns (e.g. 192.168.1.xx or 192.168.0.xx). This must be on the same subnet as Home Assistant and reachable on TCP port 502.
- Server address (for the official Growatt cloud / ShinePhone): the domain mqtt.growatt.com (preferred) or the correct public Growatt server IP for the region. Leave it on the domain unless there is a very specific reason to use a raw IP.
How to change / fix it
Use the ShinePhone app (Bluetooth method is the most reliable):
- Put the ShineWiLan-X2 into Bluetooth mode (short-press the button on the stick until the LED is steady blue).
- Open ShinePhone → go to the plant → configure / manage the datalogger (or “My” → Configure Datalogger and scan/enter the SN + check code).
- Enter Advanced settings (sometimes labelled for professionals / commissioning).
- Open the Server configuration page. You will see the current server domain / IP and port.
- Change it back to the domain mqtt.growatt.com (or leave the domain field active and clear any hardcoded IP). Port is normally 7006 (or the value the app shows by default).
- Save and let the stick reconnect.
You can also view the current server settings on that same page without changing anything.
Alternative / additional checks
- Factory-reset the stick (long-press the button ~6 seconds until the LED turns white). This restores dynamic (DHCP) local IP and clears most network settings, but does not always wipe the server domain/IP — so you may still need to correct the server setting afterwards.
- After correcting the server address, confirm in the router that the stick has a sensible local IP on the home LAN, then use that IP in the SolaX Modbus integration (port 502, slave 1).
Once the server address is fixed, the stick should resume normal cloud reporting, and the local Modbus TCP interface (the one Home Assistant uses) will continue to work independently on the stick’s real LAN IP.
If Mark can tell you the exact screen/page where he sees “10.10.0.4”, or whether it appears in ShinePhone under the datalogger details, that will confirm it is the server field.
