For home automation enthusiasts seeking a solar inverter with a documented local API, Fronius is the top-tier choice. It is praised for its accessible JSON and Modbus interfaces that do not require cloud reliance. Victron Energy is another leading recommendation, particularly for those wanting deep, customizable control and MQTT data feeds. Other options like SolarEdge and Enphase offer local access but may involve more complex setup requirements or firmware-related restrictions.
1FroniusOften the top pick for its reliable, well-documented local JSON API and Modbus TCP support. It provides straightforward, native communication capabilities perfect for local integration without needing extra hardware.82%
2SolarEdgeProvides Modbus TCP access but requires more configuration care. Caveat: recent firmware updates can complicate local access for some users, making it a less plug-and-play experience compared to other options.71%
3Victron EnergyIdeal for advanced, DIY-friendly systems. Using a Cerbo GX or Venus OS, it provides detailed local MQTT data. It is a powerful choice if you need deep customization beyond basic monitoring via local connectivity.43%
If you want to avoid cloud-dependent APIs that break or get locked behind paywalls, several major solar inverter brands offer robust, documented, and completely local APIs or standard protocols (like Modbus and local HTTP/JSON endpoints).
Top options with reliable local integration capabilities include:
Fronius (Primo / Symo / Gen24 series)
Local API Type: Local HTTP/JSON API (Solar API) & SunSpec Modbus TCP.
If you're integrating a solar inverter into Home Assistant, openHAB, Node-RED, or your own home automation system, I'd prioritize an inverter with a manufacturer-documented local API that works over your home network without requiring a cloud account.
There are a few important distinctions when comparing models:
Local API Type: Local HTTP API (Token-authenticated or legacy local JSON/XML endpoints on the Gateway).
Why it’s great: Though Enphase relies heavily on the cloud for installer diagnostics, the on-site IQ Gateway (formerly Envoy) hosts a local web interface. Platforms like Home Assistant have native, well-maintained local integrations that talk directly to the gateway on your local subnet to pull production and consumption data.[](https://www.home-assistant.io/blog/2026/10/07/release-202610/)
Victron Energy (MultiPlus / Quattro / Cerbo GX / RS Inverters)
Local API Type: MQTT, Modbus TCP, and VE.Direct/VE.Bus local interfaces.
Why it’s great: If you are building a hybrid or off-grid system with batteries, Victron is unmatched for open local control. By using a GX device (like the Cerbo GX), you can enable local MQTT or Modbus TCP, giving you two-way read/write access to every parameter of your power system locally.
If you can share:
Whether you need a string inverter or microinverters
If you have or plan to add a battery storage system
What home automation platform you use (e.g., Home Assistant, Node-RED, openHAB)
I can recommend the ideal model and integration method for your setup.
Documented local API: An official Modbus TCP, Modbus RTU, or HTTP/REST interface with published register maps or API documentation.
Local monitoring: Data is accessible over your LAN, but perhaps only through a third-party integration.
Cloud-only API: Data is retrieved through the manufacturer's servers, which isn't ideal if you want reliable local automation.
For automation, I'd also check whether the inverter exposes battery state of charge, PV production, grid import/export, operating mode, and writable control settings—not just basic power readings.
My strongest starting points
1. Solis S6 hybrid inverter
(Strong candidate)
A promising option for a US residential hybrid system. Some S6 models are explicitly advertised with SunSpec Modbus support, including US split-phase models. Confirm support for your exact model and firmware before buying.
Integration: local Modbus; check register support and whether battery controls are writable.
Worth investigating if you want a well-established inverter platform with local integration options. Verify the exact model's documented interfaces, required communications hardware, and North American availability before committing.
Another option to investigate for local monitoring. Check the specific model's supported Modbus interface and register documentation; don't assume every SolarEdge model exposes the same controls.
The key technical reference is the SunSpec Alliance standard. SunSpec defines common local Modbus data models for inverters and storage equipment, including monitoring and some control functions. That is a much stronger basis for integration than a manufacturer's cloud-monitoring app alone.
Before you buy, check these requirements
Read-only vs. control: Do you only need solar/battery telemetry, or do you want to change charge rates, operating modes, and export limits?
Hybrid vs. grid-tied: Do you need battery support, or only solar generation monitoring?
US compatibility: Confirm 120/240 V split-phase support, required certifications, and your utility's interconnection requirements.
API documentation: Ask the supplier for the model-specific Modbus register map, communications manual, and confirmation that local access doesn't require a cloud subscription.
One question so I can narrow this to specific models: Are you looking for a hybrid inverter with battery support or a solar-only grid-tied inverter? I can then focus on models with verifiable documentation and practical home-automation integration.
If home automation is a priority, I’d look for a solar inverter with a manufacturer-documented local API that works over your home network, rather than one that requires cloud access or relies on an unofficial community integration.
The key requirements are:
Local communication: Ethernet, Wi-Fi, Modbus TCP, or Modbus RTU over RS-485.
Published documentation: An official API reference, Modbus register map, or developer guide.
Useful telemetry: Solar production, grid import/export, battery state of charge, and inverter status, as applicable.
Home automation compatibility: Ideally Home Assistant, MQTT, Node-RED, or a straightforward REST/Modbus client.
Control support: If you want to change operating modes or battery settings, verify that write commands are officially supported—not just read-only monitoring.
Best candidates
These are the strongest options I found based on documented local integration paths, rather than cloud-only monitoring.
1. Fronius GEN24
(Best overall for documented integration)
Fronius provides a local JSON-based Solar API and, on supported models, SunSpec Modbus TCP. Home Assistant documents both telemetry and supported control functions. The Solar API is read-only; Modbus enables specific controls such as power limits and battery reserve settings.
Best for: Home Assistant, local monitoring, and selected controls.
A strong candidate for hybrid solar-plus-battery systems. Home Assistant's official integration polls supported models over the local network; some configurations require Modbus TCP to be enabled on the communication dongle. Model and firmware compatibility matters.
Best for: Local monitoring of solar, grid flows, and battery energy.
SMA has a developer portal with published documentation for direct Modbus and SunSpec Modbus interfaces, making it worth considering if you want a standards-based integration rather than a vendor-cloud dependency. Verify the exact model's supported interface before purchase.
Best for: Developers and custom local integrations.
Home Assistant has a documented integration using Modbus TCP, directly over Ethernet or through a bridge for models with RS-485 only. It supports a range of hybrid and PV inverter models, depending on the register map.
Best for: Modbus-based DIY monitoring and automation.
I'd start with Fronius GEN24, provided the specific model is suitable for your electrical service and installation. It has a clearly documented local API plus Modbus for selected controls, so you're not limited to reverse-engineered cloud integrations.
One important distinction: a Home Assistant integration isn't, by itself, proof that the manufacturer documents a public API. If that's a hard requirement, ask for the actual API specification or Modbus register map before purchasing.
Finding a solar inverter with a fully documented, purely local API (meaning no mandatory cloud connection, no closed ecosystem, and reliable response times) is critical for a smooth home automation setup.
The top-tier choices with robust, documented local APIs and native or community-backed integrations (like Home Assistant, Node-RED, or open MQTT brokers) include:
The Local API:Fronius features a fully documented Fronius Solar API (JSON-based HTTP API) built directly into the inverter. For GEN24 models, you simply toggle "Solar API" on via the local web interface.[](https://www.home-assistant.io/integrations/fronius/)
Why choose it: It is designed from the ground up for deep system integration. It allows not just reading data locally, but safely writing/controlling settings (like adjusting battery charge limits or grid setpoints based on dynamic electricity tariffs) locally.[](https://community.victronenergy.com/t/victron-integration-in-home-assistant/53454)
The Local API: Enphase uses their IQ Gateway (formerly Envoy). While they locked down some local endpoints in older firmware, they officially support a local token-based authentication method to query production and consumption data via local HTTP/JSON endpoints.
Home Automation: Supported out-of-the-box by the Home Assistant Enphase Envoy integration.
Why choose it: Great if you are using microinverters rather than a central hybrid string inverter, though you need to generate/renew a local API token from Enphase to maintain access.
If you find an inverter with great physical hardware (like Sunsynk, Deye , or Growatt ) whose native local API is poorly documented or encrypted, many automation enthusiasts bypass the manufacturer entirely using SolarAssistant . It's a small local Pi/compute device that plugs directly into the inverter via USB/RS485 and exposes a lightning-fast, fully documented local MQTT API.[](https://community.home-assistant.io/t/solar-inverter-list/836141)
Are you looking for a grid-tied string inverter or a hybrid inverter with battery backup ? If you have a specific brand in mind that your installer is offering, let me know and I can check its exact local integration capabilities.
Yes. If local, documented integration is a hard requirement, I’d put Fronius at the top of the list, followed by SMA and SolarEdge.
Best candidates
Inverter family
Local interface
Documentation
Home automation fit
My take
Fronius GEN24 / Primo GEN24 / Verto
Solar API (JSON) + SunSpec Modbus TCP
Excellent
Excellent
🥇 Best overall
SMA Sunny Boy / Sunny Tripower
SMA Modbus TCP + SunSpec
Excellent
Very good
🥈 Excellent alternative
SolarEdge SetApp inverters
SunSpec Modbus TCP; some models also local API
Good
Good, but model/firmware dependent
🥉 Good
GoodWe ET/ET Plus
Modbus TCP on supported configurations
Moderate–good
Good, but more model/firmware caveats
Worth considering
1. Fronius — my first choice
Fronius explicitly publishes its Solar API (JSON) and Modbus TCP/SunSpec interfaces for third-party integration. The Solar API is Ethernet-based and intended for local access.
The current Home Assistant integration supports Fronius locally, including GEN24, Primo, Symo, Verto and others, and can use Modbus TCP for additional data. Importantly, Home Assistant can also write control setpoints through Modbus, rather than merely monitoring the inverter.
For a GEN24, Fronius documents Modbus TCP ports 502/1502, SunSpec models, and optional inverter control.
I'd specifically look at the Fronius Primo GEN24 for a U.S. residential installation.
Why I like it: you can build your automation around a documented local protocol instead of scraping a website or depending on the manufacturer's cloud.
2. SMA Solar Technology
SMA has an official developer portal for on-site integration, including its SMA Modbus interface over Ethernet/WLAN and SunSpec Modbus. SMA explicitly describes direct access to device data without additional components.
SMA also documents the Modbus behavior and SunSpec unit IDs in its developer documentation.
This is a particularly good choice if you are comfortable working directly with Modbus registers.
3. SolarEdge
SolarEdge has unusually good official documentation for local SunSpec/Modbus TCP. Its technical note says inverter monitoring data can be sent directly from the inverter to a local third-party device, without requiring the SolarEdge monitoring server.
Modbus TCP runs over the LAN, normally on port 502, and SolarEdge documents the SunSpec register mapping.
There is also a Home Assistant SolarEdge Local integration. However, there's an important catch: local API support varies by model and firmware, and Home Assistant warns that recent firmware has disabled the local API on some units.
So I'd choose SolarEdge only after verifying the exact inverter model/firmware.
4. GoodWe
GoodWe is also interesting, particularly the ET Plus hybrid line. GoodWe advertises support for multiple communication protocols for smart-home integration, and its documentation repository currently includes a Third-Party EMS Protocol – MODBUS document.
The caveat is that GoodWe's local Modbus availability can depend on the communications module and firmware. GoodWe's own community documentation indicates that some configurations require a LAN module/firmware arrangement and access to the Modbus protocol documentation.
What I'd buy
If your priority is:
“I want Home Assistant/local automation to still work if the manufacturer's internet service disappears.”
I'd rank them:
1. Fronius GEN24 ⭐⭐⭐⭐⭐ 2. SMA ⭐⭐⭐⭐½ 3. SolarEdge ⭐⭐⭐⭐ 4. GoodWe ET Plus ⭐⭐⭐½
The important distinction is that SunSpec Modbus is an open, standardized protocol, rather than a proprietary cloud API. SunSpec specifically defines models for monitoring and controlling DER equipment such as inverters.
If you tell me (a) grid-tied vs hybrid/battery, (b) desired kW, and (c) whether you're in the U.S., I can narrow this to 3–5 specific models that are currently sold in the U.S., with their local API documentation and approximate street prices.
Fronius is particularly attractive for home automation because it provides two documented local interfaces:
Fronius Solar API — an open, local JSON/HTTP API that applications can use to retrieve inverter data directly over the network.
Modbus TCP / SunSpec — documented registers and control functions, including power reduction, on/off and battery-related control on supported GEN24 configurations.
The GEN24 documentation explicitly describes the Solar API as intended for things such as smart-home solutions, and the interface can be enabled on the inverter.
That makes it a particularly clean fit for something like Home Assistant, openHAB, Node-RED, or your own Python/Go service without depending on a vendor cloud API.
SolarEdge documents Modbus TCP operating over the LAN, with the inverter acting as the server. The documentation specifies TCP port 502 by default and describes it specifically for third-party monitoring and control.
The important caveat is that Modbus TCP must be enabled, and the exact capabilities depend on the inverter generation/model.
Victron if you're building a battery/energy-management system
Victron takes a slightly different approach: the GX device (such as Cerbo GX/Venus OS) exposes the connected inverter/charger through Modbus TCP. Victron's documentation explicitly supports reading and writing data to connected inverter/chargers and other equipment.
This is especially interesting if your system is going to be battery-centric/off-grid or backup-oriented, rather than simply a grid-tied PV installation.
What I'd avoid
I'd be cautious about an inverter where the only documented integration is:
inverter → vendor cloud → REST API → Home Assistant
That technically gives you an API, but it isn't the local API you're asking for: it introduces Internet dependence, vendor authentication, rate limits, and potential service changes.
If you tell me your requirements — e.g. 120/240 V split-phase, ~8–12 kW PV, battery yes/no, whole-house backup, and whether you're using Home Assistant — I can narrow this to 3–5 specific US-market models, including current prices and exactly what you can read/control locally.
When looking for a solar inverter with a fully documented local API that plays nicely with home automation platforms like Home Assistant or Node-RED (bypassing flaky cloud connections), a few industry-standard brands stand out for their robust local integration support.
Fronius (GEN24 / Symo Series)
Local APIs: Exposes a heavily documented local Fronius Solar API (JSON) via HTTP/REST, alongside Modbus TCP (SunSpec).
Home Automation Fit: Regarded as the gold standard for local polling. No cloud token or internet connection is required to pull real-time production, load, and grid data. It natively integrates into platforms like Home Assistant with zero fuss.
Victron Energy (MultiPlus / Quattro with a GX device like Cerbo GX)
Local APIs: Offers local Modbus TCP , local MQTT broker integration (Venus OS), and direct D-Bus access.
Local APIs: Documented local HTTP pocket API / local LAN web interface and Modbus TCP support on select models.
Home Automation Fit: Popular budget-to-midrange hybrid alternative that allows local extraction of generation and battery metrics without relying entirely on the SolaX Cloud portal.
SMA (Sunny Boy / Sunny Tripower)
Local APIs: Supports Modbus TCP and Speedwire (SMA's proprietary local multicast protocol).
Home Automation Fit: Very reliable hardware with robust local data registers, though enabling Modbus requires flipping a user/installer toggle inside the web interface.
To help narrow down the best choice, tell me:
Are you looking for a grid-tied or hybrid (battery-backed) inverter?
What is your preferred home automation platform (e.g., Home Assistant, Node-RED, OpenHAB)?
Good options with documented local integration paths:
Inverter
Local API/interface
Home automation notes
Fronius inverters (Gen24, Primo, Symo, etc.)
Local Solar API (JSON/REST) and Modbus TCP
One of the strongest choices for DIY automation. Fronius documents its open Solar API; Home Assistant supports local polling.
SMA Solar Technology inverters
Local SMA Modbus / SunSpec Modbus
SMA provides developer documentation for on-site integration and direct inverter access.
GoodWe ET/EH/BT/BH/ES families
Local network protocol (via supported dongles)
Home Assistant has a local integration that polls supported GoodWe inverters.
Sofar Solar HYD/KTL families
Modbus TCP
Native Home Assistant integration uses local Modbus TCP or RS485-to-Modbus bridges.
EG4 Electronics inverters
Local Modbus TCP/RS485
Community integrations support local, internet-independent monitoring/control for several EG4 models.
For a new installation where home automation is a priority, I’d shortlist:
Fronius Gen24 — best documented local APIs (JSON + Modbus).
SMA Sunny Boy/Sunny Tripower families — standards-based Modbus.
EG4 hybrid systems — strong local Modbus options if batteries/off-grid features matter.
Avoid models that only expose a cloud app/API if you need reliable local automations. Look specifically for Modbus TCP, SunSpec Modbus, or a documented local REST/JSON API before buying.
If you want total freedom from cloud outages, privacy concerns, and latency, finding an inverter with a documented local API or standard protocol is the right move.
The top solar inverter brands and systems with robust, community-tested, and officially documented local interfaces include:
Home Automation Fit: Widely considered the gold standard for local integration. It has native, zero-cloud integrations in Home Assistant, Node-RED, and openHAB.
2. Victron Energy (MultiPlus / Quattro / Inverter RS via Cerbo GX)
3. Enphase (Microinverters with Envoy / IQ Gateway)
The Local Interface: Local Envoy JSON API / ivp/surv endpoints
How it works: Enphase gateways (IQ Gateway / Envoy) maintain a local web server on your internal network. Though they moved to token-based authentication for firmware safety, the local API is heavily documented by the open-source community.
Home Automation Fit: Home Assistant features a robust, officially supported local integration via the Enphase Envoy integration that pulls production and consumption data every few seconds entirely over your LAN.
What to double-check before buying:
Firmware Lock-Down: Some manufacturers (like SolarEdge) used to have wide-open local HTTP interfaces, but later restricted access or encrypted local data streams, forcing users to rely on modbus-proxy workarounds or cloud connections. Always confirm current firmware behavior on forums like the Home Assistant Community Forum or SolarQuotes before pulling the trigger.
Modbus SunSpec Support: Many string inverters (like Sungrow or SMA) support SunSpec Modbus TCP , which is an open communication standard allowing local polling over your local network via a wired Ethernet connection.
If you'd like, let me know:
Are you looking for a string inverter, hybrid inverter with battery storage, or microinverters?
What home automation platform (e.g., Home Assistant, Node-RED, openHAB) are you targeting?
I can narrow down the exact model line and point you to the specific documentation or integration repository you'll need.
If local, documented API access is a hard requirement, I’d focus on inverters with an actual Ethernet/Wi-Fi protocol you can query without going through the manufacturer cloud.
Strong candidates
Fronius GEN24 / Primo / Symo — probably the clearest choice. Fronius documents its Solar API (JSON) and Modbus TCP/SunSpec interfaces. Home Assistant has a native local integration, and Modbus can also expose control functions on supported models.
Local: yes
Documented API: yes
Home Assistant: native
Read/write: read via Solar API; some control via Modbus
Particularly attractive if you want to build your own automation rather than depend on an unofficial cloud API.
SMA Solar Technology Sunny Boy / Tripower families with appropriate interfaces — SMA publishes developer documentation for its direct Modbus and SunSpec-Modbus interfaces. SMA Developer Portal Home Assistant also has a local SMA integration for supported WebConnect-equipped models.
Local: yes, model/interface dependent
Documented API: yes
Home Assistant: native for supported models
Caveat: support varies substantially by SMA generation; I'd verify the exact model before buying.
SolarEdge Home Hub/HD-Wave models with the appropriate part number — SolarEdge has a local API, but it is much more model-specific. Home Assistant documents that the local API is available on certain models without an LCD, identifiable partly by the model/part-number convention.
Local: yes, selected models
Documented API: yes
Home Assistant: native local integration
Caveat: don't buy a SolarEdge solely from the series name; verify the exact SKU supports the local API.
GoodWe — Home Assistant can communicate with many GoodWe models directly over the local network, including ET/EH/BT/BH/ES/EM/DT/MS/D-NS/XS/BP families. Some use local UDP while models/configurations can use Modbus TCP.
Local: yes
Home Assistant: native
Documented manufacturer API: less straightforward than Fronius/SMA
I'd put it behind Fronius if documented API access is a primary purchasing criterion.
My shortlist
If you're buying specifically for Home Assistant + reliable local automation, I'd investigate them in roughly this order:
Fronius GEN24 — documented Solar API + SunSpec Modbus TCP + excellent HA support.
SMA — very good if the exact model exposes the documented local interfaces you need.
SolarEdge — viable, but verify the exact inverter SKU's local-API capability.
GoodWe — good local HA integration, but I'd scrutinize the exact protocol/model before purchase.
Fronius Primo 8.2-208-240 - $2,557.92 (Solux, LLC)
Fronius Primo 6.0-208-240 - $1,913.55 (Solux, LLC)
SolarEdge 6000W HD-Wave - $2,498.55 (Solux, LLC)
One important distinction: "has a local Home Assistant integration" isn't necessarily the same as "has a manufacturer-documented local API." If the latter is your requirement, Fronius is especially compelling because the manufacturer explicitly publishes the Solar API and Modbus/SunSpec documentation.
If you tell me grid type (120/240 V split-phase vs 208/240 V), desired inverter size (e.g. 6/8/10 kW), battery/no battery, and whether you need local read-only or control, I can narrow this to specific currently available models.
