Anyone got a Growatt hybrid inverter?

[#1]

I have tried to ask the question on Growatt related Facebook groups and had a zilch response. I'm hoping a forum member has one, uses the app and is a little bit "tech" minded with regards the dataloggers.

Thanks

Mark

[#2]

 Assuming you have digested the material at :

https://growatt.tech/product-category/growatt-hybrid-inverter/

Could you take the next step please.

Tell us what is the internet related problem with the Growatt hybrid inverter ?

[#3]

I'm assuming that the issue is establishing comms between the data logger and inverter ?

Does this YouTube video help ?

Growatt Wifi Setup Tutorial | Reconnect Growatt Inverter To Internet Via The Hotspot | Upvolt Energy 

[#4]

No it isn't, I have the instructions on how to do this and it looks relatively straight forward. I have a new datalogger with uprated functions and know how to add it as a new plant, but want to know if I have to remove the old datalogger from the app. It was set up by my installer so if my new one doesn't do what I want and I need to add the old one back, I would be a bit knackered.

Mark

[#5]

I asked Grok, what I think your question is, and this is what it said -

No, the old data logger does not need to be deleted from the ShinePhone app (or server.growatt.com / OSS) when installing and registering the new one.

Why this works

Growatt data loggers are identified and registered by their unique serial number (SN) + check code. The app/server treats each logger SN independently. You can have multiple loggers listed under the same plant (common in multi-inverter setups, and also possible for sequential testing on one inverter).

• Physically unplug the old logger and plug in the new one.
• Add/register the new logger’s SN (via QR scan or manual entry) in the plant’s Data Logger List.
• Configure its Wi-Fi connection as normal.
• The old logger will simply appear offline (or remain listed) while the new one is active and online.

There is no requirement in the app or Growatt’s systems to delete the previous logger before adding a different one on the same plant/inverter.

Falling back to the old logger

Because the old logger’s registration remains in the account/plant:

1. Unplug the new logger and plug the old one back in.
2. Go to the plant → Data Logger List.
3. Long-press (or select) the old logger entry and choose Configure datalogger (or the equivalent option).
4. Re-enter/reconnect the Wi-Fi details if needed (Standard or Hotspot/AP mode).

It should come back online without having to re-add the SN from scratch. Historical data associated with that logger SN generally stays intact.

When you would delete the old logger

• You want a clean list with only the active logger.
• You are permanently replacing it and no longer need the old entry.
• You encounter a “Datalogger already exists” error for some other reason (usually because the SN is bound to a different account/plant — in that case Growatt support or the previous account holder must unbind it).

Deleting is optional for your fallback scenario and is done via long-press on the logger in the Data Logger List (app) or the equivalent delete option on the web portal.

Practical tips

• Note the old logger’s SN (and check code if visible) before swapping, just in case.
• Only one logger can be physically connected to the inverter’s USB/COM port at a time.
• Ensure the new logger is compatible with the inverter model.
• Use 2.4 GHz Wi-Fi only for configuration.
• If anything gets stuck (e.g., binding issues), Growatt support can release an SN quickly when given the serial number.

You can safely try the new logger while keeping the old registration intact, then swap back if needed.

[#6]

Thank you for that, a bit of relief off my mind should I mess up with the new datalogger😊

Will give it a go tomorrow now (maybe) as I will be working from home.

Mark

[#7]

Crikey, nothing's ever easy is it? (longish post for anyone interested, still with no result though!!)

My original datalogger is RS232, whatever that means and I also have usb socket, allegedly for firmware only! The datalogger is held in place by screws that are almost impossible to access as the installer but the battery almost as close as possible to the underside... Plugged in new datalogger, nothing... Tried again and again, then thought that was £35 down the drain. I tried a usb port on my wife's usb extender, nothing. I messed about for a while, not leds lit up anywhere. I took it apart and thought I would try and connect it via ethernet the next day. In the meantime, I contacted the seller to ask about the faulty goods return policy. Next day, I had managed to borrow a battery pack, small enough fo me to be able to put the whole of the datalogger plug in, as it has a collar around it that interferes with a standard socket. A red light on the back of the board , so I plugged in the lan to the router. Comms through the router and I was able to add it is a wired unit. Not ideal, as I have no ethernet upstairs, although I could possibly have used a powerline adaptor. Obviously it isn't plugged into the inverter, so not going to give me any functions. Went and sat down for a bit to ponder my thoughts. Half hour later, I went back to it and pressed the button, the blue led to pair it via wifi/ bluetooth option became available. I was able to pair again with the router wirelessly, so unplugged the lan to see if it kept connection. It did!! Then the battery pack went dead... I wonder if the datalogger has a small on board battery that had become flat?

An email from the company I bought the datalogger from responded and is sending me a new one, which I will send back if this one is found to work. 

I have gone back to the inverter today to plug in the datalogger and see what happens. Pairs well. Adds to plant well. I can see data passing through the router, so it is obviously doing something, just not what I want it to do. 

Time to sit back and have a think as to if it is still a faulty datalogger, or something i'm doing wrong.

[#8]

---

@Marksfish wrote:

... I wonder if the datalogger has a small on board battery that had become flat?

---

From your description I am assuming that your logger is probably the "ShineWiLan-X2".

That does not contain a battery or capacitor for retaining configuration settings or logged data, but instead is stored in non-volatile EEPROM or flash memory, with enough capacity for a month of logged info.  The logger gets it's power at 5 Volts drawn from the USB connector.

[#9]

It is indeed that datalogger 👍. Very strange how it started working after taking it out of the cover. Maybe a dodgy connection on the button then and my being able to press the button a bit firmer without the rubber cover has created a better connection.

[#10]

---

@Marksfish wrote:

Time to sit back and have a think as to if it is still a faulty datalogger, or something i'm doing wrong.

---

Do you have the ShineWiLan-X2  User Manual and Configuration Guide  to refer to ?

[#11]

@Marksfish  what is the full model number/name of the inverter ?

[#12]

The manual for the datalogger is very basic. It tells how to connect and what some basic led colours mean. Googling gives some info, on the HomeAssistant forum, but I am reluctant to join and the thread is about a year old. No entities are populating in Solax, despite it supporting my inverter. The one question that related to my issue, wasn't answered.

The inverter is the SPH-3600. the manual is pretty extensive and most of the actions related to it are via the cloud. The idea of this datalogger was to try and make the data more local and extra available actions.

[#13]

@Marksfish 

I asked AI to make sense of your question, and to suggest what you can try next -

Mark has installed the Growatt ShineWiLan-X2 datalogger on his SPH-3600 hybrid inverter. It is physically connected (USB), the plant is created in the Growatt ShinePhone / ShineServer cloud, and it has network connectivity via the broadband router (Wi-Fi or LAN). However, when trying to use the SolaX Inverter Modbus custom integration in Home Assistant (the popular HACS component by wills106 that also supports many Growatt models), no entities (sensors, controls, etc.) appear, even though the integration lists support for the inverter.

This is a common local Modbus TCP setup: the ShineWiLan-X2 acts as a Modbus TCP-to-RTU gateway (listening on port 502), allowing Home Assistant to poll the inverter directly over the local network without relying on the Growatt cloud.

Why entities often fail to populate

• The integration connects successfully at the TCP level but cannot correctly identify the inverter type, read the expected registers, or complete the initial scan (so it creates no entities).
• SPH series (including SPH-3600) are supported via the Growatt plugin, but firmware variations, serial number prefixes, optional features (e.g. VPP registers), or polling issues can cause partial or total failure.
• Older ShineLAN-X sticks do not expose Modbus TCP; only the X2 does.
• Network, IP, or basic connection problems can also prevent register reads.

Troubleshooting steps (in order)

1. Confirm the datalogger is the correct model and online
   • It must be a genuine ShineWiLan-X2 (not ShineLAN-X or ShineWiFi-X).
   • Check the LED on the stick (steady/flashing green usually means router connected; other patterns indicate problems — consult the quick-start guide).
   • In ShinePhone / ShineServer, verify the plant shows the inverter online and data is updating (even if slowly).
2. Find and lock the IP address of the ShineWiLan-X2
   • Look in your router’s DHCP client list for a device whose hostname is the stick’s serial number (often something like VWQ0… or similar) or MAC starting with patterns commonly used by these sticks (e.g. f0:24:f9).
   • Set a DHCP reservation so the IP never changes.
   • From a computer on the same network, test connectivity: ping <IP> and preferably a Modbus tool (mbpoll, QModMaster, etc.) to port 502 with slave ID 1.
   • Port 502 should be open. If it is closed, power-cycle the stick (unplug from inverter USB for 30–60 s) and/or reboot the router. Some users report the port only becomes reliably available after a full restart sequence.
3. Home Assistant integration setup (re-do carefully)
   • Install/update the latest SolaX Inverter Modbus via HACS.
   • Add the integration → select Inverter Type = Growatt.
   • Interface = TCP / Ethernet.
   • Enter the stick’s IP, port 502, Modbus address/slave ID usually 1.
   • Leave most optional flags (EPS, Dry Contact, Parallel, VPP, etc.) at defaults unless you know you need them.
   • Give it a clear name and submit.
   • After adding, check the Home Assistant logs (Settings → System → Logs, filter for solax_modbus) for errors such as timeouts, “no response”, “unrecognized inverter”, or specific register failures.
4. Common fixes when connection succeeds but no entities appear
   • Reload / restart: Reload the integration, then fully restart Home Assistant.
   • Power-cycle sequence: Unplug the ShineWiLan-X2 from the inverter USB → wait 30–60 s → plug back in → wait for it to rejoin the network → reload the integration.
   • Firmware / VPP-related issues: Some SPH Gen3 units timeout on newer VPP registers (e.g. 30100) that were added in later integration versions. This can abort the entire poll cycle so zero entities are created. Check the GitHub issues for wills106/homeassistant-solax-modbus (search SPH + VPP or timeouts). Temporary workarounds have included rolling back the integration version or ensuring certain registers are marked to ignore read errors.
   • Serial / model detection: The integration auto-detects based on serial prefix and firmware. Note the first few characters of the inverter serial (visible on the unit or in ShinePhone) — this helps diagnose “unrecognized” cases.
   • Polling interval: Start with the default (~15 s). Avoid very aggressive polling while testing.
   • Network isolation: Ensure Home Assistant and the stick are on the same LAN/subnet with no firewall rules blocking port 502.
5. Additional checks
   • Confirm the stick is firmly seated in the inverter’s USB COM port (triangular mark orientation, locking ring tightened).
   • Try switching the stick between Wi-Fi and LAN if both are available.
   • In the ShinePhone app, look for any advanced/datalogger configuration options related to Modbus or local access (rarely needed, but worth checking).
   • Test with a standalone Modbus client first to prove the stick is answering register reads before involving Home Assistant.

If it still fails

• Post the exact integration version, Home Assistant version, inverter serial prefix, stick serial, IP, and relevant log excerpts (especially any “Modbus Error”, timeout, or “unrecognized” messages) in the Home Assistant Community thread “Growatt Shine WiLan X2 integrated into Home Assistant” or the GitHub repo issues for the integration.
• Many SPH users have it working with the X2 + this integration once the IP is stable and the initial scan succeeds.

The cloud side working while local Modbus entities do not is normal — the two paths are independent. Once the local Modbus path is solid you get much faster (sub-minute) updates and direct control entities. Start with confirming the IP and a clean re-add of the integration; that resolves the majority of “no entities” cases.

[#14]

@Marksfish 

One of many things in the above instructions was regarding firmware versions, so I asked how to do firmware updates -

Yes, firmware updates are possible for both the Growatt SPH-3600 hybrid inverter and the ShineWiLan-X2 datalogger.

1. ShineWiLan-X2 datalogger firmware

This is the easier and more common update.

• Local (Bluetooth): The ShinePhone app (or installer ShineTools app) supports local firmware upgrades over Bluetooth. Put the stick into Bluetooth mode (usually a short press of its button so the LED goes steady blue), connect via the app, and follow any prompted upgrade.
• OTA / remote: Once the stick is online and talking to Growatt’s servers, firmware can be pushed remotely (often via the installer OSS portal or automatically when a newer version is available).
• The stick itself advertises support for “local configuration and firmware upgrade” and “remote configuration and firmware upgrade”.

Updating the datalogger is low-risk and can improve Modbus TCP behaviour or stability.

2. SPH-3600 inverter firmware

The inverter itself can also be updated. There are two main methods:

Local USB method (most common for end users / installers)

1. Obtain the correct firmware package for your exact model and current version from Growatt support, your installer, or an authorised distributor (files are model-specific; wrong files can brick the unit).
2. Format a USB stick as FAT32.
3. Copy the required files (often several: e.g. BCONFIG, YBAA-…, ZDAA_… etc.) to the root of the stick.
4. Power the inverter correctly (follow the exact procedure for your model — usually AC on, DC/battery off or as specified).
5. Remove the ShineWiLan-X2 from the USB port.
6. Insert the USB stick into the inverter’s USB port.
7. The inverter display should show “Programming” (and a red LED may flash). It typically processes multiple files one after another; each ends with “Program OK!”. Do not interrupt power or remove the stick.
8. When finished, remove the stick, re-insert the datalogger, and power-cycle as required. Verify the new FW version on the inverter display (usually under WorkMode / FW Version or similar).

Remote update Possible via Growatt’s OSS / ShineServer portal, but this is normally done by an authorised installer or Growatt support, not end users. A stable internet connection via the datalogger is required, and the process reboots the inverter (so EPS/backup output can drop).

Important caveats

• Always use the exact firmware matching your inverter’s serial / model / current version. Mismatched firmware is a common way to cause serious problems.
• Firmware is not freely downloadable for most users; you normally need to request it from Growatt support, your installer, or a local distributor (provide the inverter serial number).
• Updating is not risk-free. Power interruptions during the process can leave the inverter in a bad state. Follow the official procedure precisely.
• In the context of the SolaX Modbus integration “no entities” issue, a datalogger firmware update is more likely to help than an inverter firmware update (the stick is the Modbus TCP gateway). Inverter firmware differences (especially around VPP registers or protocol variants) can still matter, but changing it should only be done if you have a specific reason and the correct files.

Recommendation: First try updating the ShineWiLan-X2 via the ShinePhone app (Bluetooth or OTA). If entities still do not appear, note the current inverter firmware version (visible on the LCD or in ShinePhone) and contact your installer / Growatt support with the serial numbers of both the inverter and the stick. They can advise whether a specific inverter firmware is recommended for better local Modbus compatibility.

Would you like the typical steps for checking the current firmware versions on either device?