SolaX settings, Modbus and export control through the Collector
A practical hub for SolaX owners searching for inverter settings, WiFi/LAN dongle IP, Modbus TCP, export limit, zero export, battery modes and wallbox automation.
Why settings need local context
Many SolaX questions start as settings questions: where to find the inverter IP, whether Modbus TCP is available, how export limit works, or how battery charge and discharge behavior should be handled.
SolaxMonitor keeps this collector-first because settings and automation decisions need recent local inverter data. A hosted server cannot directly reach a private LAN inverter IP, and public Modbus exposure is not the product direction.
Dongle and local IP
Use the Collector with a stable local path to the SolaX WiFi/LAN dongle or inverter endpoint.
Modbus TCP
Keep Modbus inside the LAN and route supported automation through the local Collector.
Export limit and zero export
Prepare workflows for feed-in limit, zero export and negative-price protection where the installation supports it.
Battery and wallbox
Connect battery charge/discharge behavior and EV/wallbox decisions to live solar, grid and tariff data.
What SolaxMonitor can help with
SolaxMonitor is not a cloud-only remote settings screen. It is a collector-powered monitoring and automation layer for users who want settings decisions to be based on current local data.
Exact capabilities depend on inverter model, dongle, firmware, Modbus access, local network and user configuration. Read-only monitoring is separated from control workflows.
Common SolaX settings searches
This page is for common questions that need a collector-based answer:
- SolaX inverter IP address, WiFi dongle IP and stable LAN access.
- SolaX Modbus TCP, register support and safe local control.
- Export limit, feed-in limit, zero export and negative spot price protection.
- Battery charge/discharge behavior, wallbox coordination and tariff-aware automations.
Frequently Asked Questions
Can SolaxMonitor change SolaX settings?
SolaxMonitor is being built for verified collector-powered workflows where supported by the local SolaX setup. Availability depends on model, firmware, dongle and Modbus access.
Why not control settings directly from the server?
A server cannot directly reach private LAN IP addresses such as 192.168.x.x. Exposing Modbus publicly is not recommended, so SolaxMonitor uses a local Collector.
What is the safest path for export limit automation?
Keep the inverter on the LAN, run the Collector 24/7, verify read data first, then enable supported control rules with clear user limits.
Does this replace SolaxCloud?
For the full SolaxMonitor product, yes: Collector is the primary path. SolaX Cloud can remain useful for limited import or diagnostics.
Explore More Features
Ready to Monitor Your SolaX System?
Start with the Collector now, or join the waitlist for the plug-and-play Collector Box.
Start Free Trial