SolaX Modbus TCP automation through the Collector
Automations that change export limits, battery modes or wallbox behavior need a trusted local runtime. SolaxMonitor uses the Collector for that control path.
Why Modbus needs local runtime
Modbus TCP is designed for local networks. It is powerful, fast and usually not built to be exposed safely on the public internet.
The Collector gives SolaxMonitor a local, authenticated and always-on process that can evaluate rules and apply commands when your inverter supports them.
Local control surface
Commands are prepared from inside the home network instead of from an exposed public port.
Export and battery modes
Support workflows such as zero export, feed-in priority and battery charge/discharge behavior.
State restore
Automation rules can snapshot settings and restore them after a tariff window ends.
Safety-first product path
Cloud-only accounts remain read-only; writes require Collector capability and user configuration.
Automation use cases
Modbus automation lets solar owners respond to negative prices, high export value, cheap charging windows and EV charging rules without watching charts all day.
The exact register support depends on inverter generation, firmware, dongle and local network access, so SolaxMonitor treats automation as a capability that must be verified.
What SolaxMonitor can coordinate
Collector-powered rules are designed for real energy decisions:
- Stop or limit grid export during negative spot prices.
- Prefer solar export when the feed-in price is attractive.
- Charge or discharge the battery around tariff windows.
- Coordinate wallbox behavior with inverter and battery state.
Frequently Asked Questions
Is Modbus automation available in SolaX Cloud mode?
No. Cloud data is read-only for this purpose. Modbus writes require a local Collector path.
Is Modbus TCP safe?
It can be safe when kept inside the LAN and controlled by a trusted process. It should not be exposed directly to the internet.
Will every SolaX inverter support every rule?
No. Support depends on model, firmware, dongle and enabled Modbus access. SolaxMonitor exposes only the controls it can verify.
Why not run automation only on the server?
A server on the internet cannot reach private LAN devices directly and should not require users to expose Modbus ports publicly.
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