Open Solar and Battery Monitoring with RS485, Modbus and SunSpec

Why local data matters

Monitoring through a manufacturer's cloud is convenient, but the data then depends on the internet connection, the vendor's servers and the vendor's account terms. Local access means reading the inverter or battery directly over the home network or a serial cable. It keeps working during an internet outage, which is often when an owner most wants to see the battery's state of charge; it allows automations that react in seconds, such as shedding a load when the battery falls below a threshold; and it gives the owner a permanent record that does not disappear if a service is discontinued.

Our guide to smart-home devices that work without the cloud lists which consumer products run locally in Home Assistant. This guide goes one layer down, to the protocols that inverters and batteries actually speak, and is written for owners, installers and engineers who are comfortable with them. The rule throughout is to read first, and to treat writing settings as a separate decision that belongs with the installer and the manufacturer.

RS485 and Modbus RTU basics

RS-485 (opens an external site) is an electrical standard for a twisted-pair bus that carries a differential signal, which tolerates the electrical noise around inverters and long cable runs. Modbus (opens an external site) is the request-and-response protocol most often carried on it: one master, such as a data logger or a computer, polls each slave device by address and reads numbered registers. Modbus RTU is the compact binary form used on serial lines. The figures below come from the Modbus over Serial Line specification (opens an external site), V1.02; the Modbus Organization (opens an external site) publishes the protocol specifications.

The protocol defines how to ask for a register, not what the register means. Register maps, the documents that say which address holds battery voltage or grid power and with what scaling, are specific to each manufacturer unless the device implements SunSpec models. A capable owner with the map can read a device with any Modbus client; without it, the data is just numbers. Battery systems often use a second bus, CAN (opens an external site), between the battery management system and the inverter. That link carries charge and discharge limits and is not a monitoring port to tap into.

Modbus TCP and SunSpec models

Modbus TCP carries the same requests over Ethernet or Wi-Fi, normally on TCP port 502, so a networked inverter or an RS485-to-Ethernet gateway can be read from any computer on the network. Modbus itself provides no protection against unauthorized commands or interception, so a Modbus TCP device belongs on a separate network segment and must never be exposed to the internet.

SunSpec Modbus is the open answer to vendor-specific maps. The SunSpec Alliance (opens an external site) publishes standard information models, blocks of registers with defined meanings for inverters, meters and storage, so a client that understands SunSpec can read compliant equipment from different makers. SunSpec states that all of its specifications are free to download and use, that SunSpec Modbus is referenced in IEEE 1547-2018, and that it interoperates with IEEE 2030.5 and IEEE 1815 (DNP3), the other communication interfaces that standard identifies. A Secure SunSpec Modbus specification is at test status. Where a device supports SunSpec, ask for its implementation note, which states the models and any vendor-specific additions.

Data loggers, pysolarmanv5 and Home Assistant

Many hybrid inverters ship with a Wi-Fi data logger stick that reads the inverter over RS485 and uploads to a cloud service. Loggers made by Solarman (IGEN-Tech) use a proprietary V5 protocol that wraps Modbus RTU frames. The open-source pysolarmanv5 (opens an external site) library, released under the MIT license, talks to these loggers directly on TCP port 8899 and offers synchronous and asynchronous interfaces. Its documentation notes that the Solis S3-WIFI-ST stick is not supported and that some Ethernet loggers speak Modbus TCP natively, without the library.

Home Assistant (opens an external site), the open-source home automation platform, is where most owners bring this data together. The ha-solarman (opens an external site) custom integration, also MIT licensed, is built on the asynchronous pysolarmanv5 and also supports Modbus TCP through ESP-based or Waveshare RS485 bridges. SolarAssistant is a commercial alternative: its software (opens an external site) runs on a Raspberry Pi, works without an internet connection, supports brands including EG4, Sol-Ark, Growatt, Deye and Victron, and publishes data to Home Assistant by automatic discovery and over MQTT (opens an external site), WebSocket or REST.

Whether local polling works alongside a logger's cloud upload depends on the logger and its firmware, so we confirm it on the specific unit. The same RS485 or CAN link to the inverter is also what a battery or vehicle bridge controller uses, a topic covered in our guide on EV batteries and hybrid inverters.

Read-only first, and what not to change

Reading registers changes nothing in the inverter. Writing them can. Many inverters expose writable registers for operating mode, charge limits, export limits, grid profile and protection settings, and a write to the wrong address or with the wrong scaling takes effect immediately. We do not publish register writes, and this guide does not describe them.

Protection settings, the grid profile and export limits are part of what the utility approved. In New York, interconnection under the Standardized Interconnection Requirements (opens an external site) is based on certified equipment with the utility's settings, and a change to the operating mode requires a new application. Changing these settings yourself can breach the interconnection agreement, can affect anti-islanding and the safety functions described in our guide on inverter rapid shutdown, arc-fault and isolation detection, and can void the warranty.

• Use a Modbus client in read-only mode, or an integration that only reads, until the register map is confirmed against the inverter's own display.
• Keep inverters, loggers and gateways on their own VLAN, with no port forwarding from the internet.
• Make operational changes, such as charge schedules, through the manufacturer's documented interface or with the installer.
• Leave grid profile, protection and export settings as commissioned. Changes go through the installer and, where required, the utility.

Restricted ecosystems, as of October 2026

Some major brands have narrowed local access in recent firmware. The facts below are stated as each source gives them, with the manufacturer's stated reason where one exists.

Enphase's technical brief on token access (opens an external site) adds that a self-installer using installer credentials receives 12-hour tokens unless Enphase Support converts the account to owner credentials. Once issued, the token allows data to be read locally; issuing and renewing it requires the Enphase cloud. Home Assistant's Enphase integration (opens an external site) renews the token automatically unless multi-factor authentication is enabled.

For the Powerwall 3, Home Assistant documents the reduced local entities (opens an external site). The open-source pypowerwall (opens an external site) project, under the MIT license, reads more data through Tesla's TEDAPI interface over the gateway's Wi-Fi and describes a wired-LAN mode that uses a registered RSA key. These are community-developed interfaces, not a Tesla-documented local API, and they can change with any firmware update. Tesla's official route is its cloud Fleet API, which, according to pypowerwall, caps the backup reserve at 80 percent.

Authentication on a controllable grid asset is reasonable, and both companies support their customers through their own apps. The open question is narrower: whether authentication has to depend on a vendor cloud account, or could be issued and held locally by the owner.

What open standards require, and what they do not

Public rules already require inverters to communicate, but with the utility. IEEE 1547-2018 identifies three local communication interfaces for distributed energy resources: SunSpec Modbus, IEEE 2030.5 and IEEE 1815. In California, Rule 21 Phase 2 communication requirements took effect on June 22, 2020; as SunSpec summarized them (opens an external site), any solar inverter or energy storage system installed in California must have demonstrated the capability to communicate using IEEE 2030.5 under the Common Smart Inverter Profile.

These are utility-facing requirements. They require communication capability so that utilities and aggregators can monitor and manage equipment; they do not require that the owner be given local access, credentials or a register map. A product can meet them while offering the owner no documented local interface at all.

The case for documented local interfaces

We believe documented local interfaces serve owners and the industry, and we say so on the record. Owners keep their data and automations if a cloud service changes or ends. Installers can integrate inverters, batteries, meters and chargers from different makers, diagnose faults on site without waiting for a support queue, and service systems after a manufacturer exits a market. Utility programs benefit as well: PSEG Long Island's Battery Storage Rewards program (opens an external site) runs enrolled home batteries as a network that relieves strain on the grid on hot summer days, through third-party aggregators that depend on reliable communication with each system. Wider use of home and vehicle batteries as flexible storage, argued in full in our EV battery and hybrid inverter guide, depends on the same open, standard interfaces.

The counterweights are real: an open interface must be secured, manufacturers bear support costs when third-party tools misbehave, and settings that affect the grid must stay under control. A published read-only map with locally issued credentials, plus a documented and authenticated path for the settings an owner may legitimately change, would address both sides. The same argument applies to EV chargers, as our guide on OCPP and charging network lock-in explains.

A buying checklist, and how we set it up

• A published Modbus register map or SunSpec implementation note for the inverter, the battery and the meter.
• Local access that works without a cloud account, or with credentials the owner can renew locally.
• A wired RS485 or Ethernet port, not only Wi-Fi.
• A firmware policy with release notes, so changes to local access are announced.
• An existing Home Assistant integration with a local IoT class, or a documented API.
• For a microinverter array coupled to a hybrid, as described in our guide to AC coupling microinverters to a hybrid inverter, local access to both systems.

Battery data deserves the same openness; our guide to second-life EV batteries as home storage discusses how much depends on the battery management system's own data. On our projects, we specify equipment with documented local interfaces, run shielded twisted-pair RS485 and Ethernet cabling to the inverter location during installation, place the equipment on its own network segment, and set up read-only monitoring in Home Assistant or the owner's preferred platform. Network and controls work is part of our low-voltage services, and electrical work is performed by our licensed partner electricians.