SolarEdge Communication Systems¶
EXPANDING
Communication in a SolarEdge system has two distinct layers: 1. Optimizer-to-inverter — always via power line communication (PLC) on the DC string 2. Inverter-to-cloud — via RS485, Ethernet, Wi-Fi, or cellular
This page covers the inverter-to-cloud path and site communication options.
Communication Options¶
Protocol: Modbus RTU over RS485 serial
Use case: Multi-inverter sites, wired installations, sites without reliable Wi-Fi
Topology: Daisy-chain up to 31 inverters on one RS485 bus
Wiring: - A and B signal wires + ground - Twisted pair, shielded preferred - Maximum 1,000m bus length - Termination resistor (120Ω) required at each end of the chain
Field notes: - Check polarity — A and B are not interchangeable - Ground each shield at one end only to avoid ground loops - Use SolarEdge GO (BT connected) → Communication → RS485 to verify bus status
Use case: Sites with wired LAN available
Setup: Standard RJ45 connection to router/switch
Field notes: - Confirm DHCP is available or configure static IP - Check router firewall — SolarEdge requires outbound access on port 22222 (or cloud endpoint) - Ethernet is most reliable for commercial sites with network infrastructure
Use case: Residential sites with accessible Wi-Fi router
Setup: SolarEdge GO → Communication → Wi-Fi → enter SSID and password
Field notes: - Inverter Wi-Fi range is limited — check signal strength at inverter location - 2.4 GHz networks preferred (better range through walls) - Client must provide Wi-Fi credentials; note them in site documentation - Configure via SolarEdge GO (BT connected) → Communication → Wi-Fi - Wi-Fi reliability issues are common in older homes with weak router placement
Use case: Sites without reliable internet, commercial rooftops, remote locations
Hardware: SolarEdge cellular kit (SIM-based, plugs into inverter communication port)
Carriers: Typically AT&T or T-Mobile depending on kit
Field notes: - Verify cellular signal at the inverter location before installing kit - SIM may require activation via SolarEdge portal - Monthly data usage is minimal — SolarEdge data packets are small - Backup option when Wi-Fi drops or client changes router password
Verifying Communication Status¶
Via SolarEdge GO (Local BT)¶
- Connect to inverter via Bluetooth in GO
- Navigate: Communication settings
- View active communication type and connection status
- Check last successful cloud sync timestamp
Via SolarEdge GO (Fleet / Cloud)¶
- Open GO → Sites → select site
- Check "Last Communication" timestamp in site overview
- If >24h without data: investigate communication path
- Remote view available without going to site for initial triage
Via Legacy SetApp¶
- Connect to inverter via Bluetooth
- Navigate: Maintenance → Communication
- Use on older inverters where GO has limited connectivity
Common Communication Issues¶
| Issue | Possible Cause | Action |
|---|---|---|
| No data for 24+ hours | Wi-Fi password changed, router replaced | Re-enter Wi-Fi credentials via SolarEdge GO (or SetApp on legacy) |
| Intermittent data gaps | Weak Wi-Fi signal | Move router closer or add extender |
| RS485 bus offline | Polarity issue, cable damage, missing terminator | Verify wiring, swap A/B if reversed |
| Cellular no connection | Low signal, SIM issue | Check signal, verify SIM activation |
| Site shows offline but producing | Comms only — not a production issue | Restore comms when convenient |