Growatt Modbus is a catch-all term that connects two different worlds: installers integrating inverters with building automation and Home Assistant enthusiasts who want to see production on their own dashboard instead of in the manufacturer's cloud. Both worlds ask the same question—"how do I connect to this?"—and both deserve an honest answer: what is officially documented in the hardware, where the individual buses run, and where the realm of community solutions begins, for which the manufacturer is not responsible. This guide organizes the device communication layer. Growatt based on instructions and catalog cards - without copying register maps that are not covered by public documentation.
What interfaces are actually in devices? Growatt?
Let's start with an inventory, because Growatt Modbus begins with ports. The physical layer is richer than the presence of a "WiFi cube" suggests. MOD/line invertersMID The XH series features USB and RS485 ports as standard, with WiFi/GPRS/4G/RF/LAN connectivity available as options via data loggers. WIT supports RS485 communication with 1-254 addressing, connected "hand-in-hand" in parallel operation. Family SPF exposes the RS485 port next to the dedicated port BMS (CAN/RS485). Smart meters communicate via Modbus-RTU — TPM-CT-G with communication address 1 and bus range up to 200 m. The controller is on top ShineMaster-X: four RS485 buses (up to 500 m), LAN, CAN and cellular modem, with Modbus-RTU, Modbus-TCP and IEC 60870-5-104 protocols - a full set of industrial integration languages, up to 124 devices under one supervisor.
First conclusion: Growatt Modbus exists natively—RTU on serial buses in inverters and meters, TCP in the master controller. Second conclusion: what you see in the application ShinePhone, goes a different route (datalogger → cloud), and local integration is a separate, parallel path via serial ports - both can run simultaneously because they use different interfaces.
Three paths of integration - from official to hobbyist
| Drug | How | Support Status | Ideal for |
|---|---|---|---|
| ShineMaster-X / Industrial Integration | Modbus-TCP and IEC 60870-5-104 up to BMS-a building or SCADA; embedded Web to run | official manufacturer path for C&I facilities | integrators, commercial facilities, dispatch systems |
| Direct RS485 (Modbus RTU) to inverter | serial bus from the unit's RS485 port to the controller/gateway | port documented in manuals; register map requires protocol document from Growatt | building automation, EMS, advanced installers |
| Social integrations (Home Assistant and related) | reading via a cloud account or locally via RS485 gateways/datalogger data capture | Community solutions - no manufacturer support or warranty | smart home enthusiasts, hobby monitoring |
The line of responsibility runs through the middle of this table. Ports and protocols are official; specific register addresses, scaling, and write permissions are not, as the public manuals don't contain them. Therefore, in commercial projects, the Modbus protocol document is obtained through the manufacturer's distribution channel or technical support, and we help our B2B clients with this—guessing registers on a production facility isn't integration, it's gambling.
Home Assistant a Growatt — what to say to an enthusiastic customer?
The Home Assistant community maintains integration with the ecosystem Growatt for years—from reading data via a cloud account to local bridges listening to datalogger communications. A fair framework for the installer is as follows: these are unofficial solutions, developed by the community, working today and may require corrections after firmware or API updates; great for viewing and statistics, not intended to control functions covered by connection conditions (export limit, network settings—these are only changed via official paths, described in our articles about export limits and settings).
Practical architecture for the enthusiast's home looks sensibly like this: the manufacturer's monitoring remains untouched (ShinePhone/Server via datalogger—this is the basis for service and warranty diagnostics), and local readings are added in parallel via RS485 via a Modbus gateway, not instead. This means that playing with the dashboard never cuts off the channel through which we and the manufacturer diagnose the installation—a separation of roles that saves many a service call.
Modbus in installation practice - what to remember about the bus
Growatt Modbus RTU inherits the brand-independent rules of every RS485 bus: twisted-pair wiring with A/B polarity, a branch-free daisy chain, unique device addresses on a shared bus, and reasonable lengths. Growatt provides specifics here: addressing inverters WIT in the range 1–254, counter TPM at address 1, buses ShineMasterand up to 500 m - when designing, stick to the values in the instructions for your configuration exactly. An address conflict on a shared bus manifests itself exactly as a lack of communication - and can take hours to search in the wrong places.
The second rule: one bus, one host. The RS485 port occupied by the meter for the export limit function is not also a free port for reading. Before connecting anything "read-only," check the manual to see which ports the unit has free and what they are assigned to. In lines with a separate port BMS the boundary is hard: the communication bus with the battery belongs to the battery and is not a place for experiments.
Growatt Modbus in a small company - EMS scenario without SCADA
Between the enthusiast's home and the industrial control room, there is a third, increasingly common case: a workshop, processing plant or farm that wants to control its own consumption relative to production – turning on heaters, coolers or chargers when the inverter has a surplus. Growatt Modbus supports this scenario in two ways: a simpler one, via the inverter's potential-free contact (the "surplus" signal without any protocol - the dry contact function is described in a separate article), and a full one, via power reading via RS485 to the PLC or EMS controller, which itself decides on priorities.
Choosing the right path is a matter of complexity: the interface handles one receiver with one rule, the protocol handles arbitrary logic at the expense of an integration project with documentation. In practice, most "intelligent" needs of small companies are limited to two rules at the interface, and Growatt Modbus only enters the arena where decisions require numbers, not the fact of surplus. Start with a simpler one—the protocol won't go anywhere, and it's easier to convince a customer to expand a working system than to improve an overcomplicated one.
From the installer's practice
- From practice: immediately propose a parallel architecture (cloud + local reading) to a client with Home Assistant, with a note in the protocol that local integration is on their side - a clear division of roles saves disputes during the first service request.
- From practice: label each RS485 wire at both ends (from-to, A/B) - buses grow over the years and after the third expansion, no one remembers what is what.
- From practice: when integrating with EMS, request a list of required registers from the EMS provider IN WRITING and compare it with the protocol document - "we will agree on the site" ends with a day of standing around with laptops.
- From practice: after each change to the inverter firmware, check whether the local integration is still reading correctly - and inform the customer about this in advance so that the update does not appear to be a failure.
Frequently asked questions (FAQ)
Czy Growatt Modbus also allows control, not just reading?
Layered: the protocol allows for writing, but which parameters are writable and with what permissions are determined by the protocol document and the unit configuration, and some settings (network, export limits) are additionally protected by a service password. For home integrations, we recommend read-only mode; leave control to official paths and EMS projects maintained in the documentation.
Where can I find a map of registers?
Not in public manuals—which is why we're not reprinting it here. The manufacturer provides the Modbus protocol document through support channels; we help clients who work with us obtain it. Versions circulating on forums can be outdated relative to the firmware—treat them as notes, not documentation.
I prefer not to integrate anything - what am I missing?
Nothing basic: full monitoring, app, and remote diagnostics work via a datalogger without any Modbus. Local integration is an additional layer for those who want to connect inverter data to home automation or facility energy management systems.
The hardware industry opens the path GROWATT Shine Master-4G-X, and basic communication - dataloggers from the category Communication and monitoring. Instructions describing ports and interfaces are published download center Growatt — and in B2B integration projects, our technical department helps in obtaining protocol documentation.
