Will a solar monitor read your inverter and BMS?

Collect an exact identity for every device

Write down the manufacturer, full model number, hardware revision and firmware version of the inverter. Do the same for each battery or BMS and each separate charge controller. Two devices with the same brand on the case may speak different protocols; revisions within a product family can also change what a monitor receives.

Use a photo of the label and the manufacturer’s manual as your starting evidence. Keep serial numbers in your private installation record; they do not need to appear in a public support post. For a parallel battery bank, record how many packs are installed and how their monitoring connections are addressed.

Separate the four layers

1. Physical connector

USB, an RJ-style socket or another connector. The shape does not establish its purpose.

2. Electrical interface

For example, RS232 or RS485. Confirm the documented interface and the manufacturer-approved cable.

3. Message protocol

The commands and replies the monitoring software understands.

4. Measurement map

Which fields exist, their units and scaling, and which firmware reports them.

The Modbus serial-line specification distinguishes the protocol from its physical interfaces. “Modbus” still does not supply an inverter’s register map. Similarly, a socket used for battery-to-inverter communication is not automatically an available PC monitoring port.

Do not repurpose a battery communication link or guess a pinout from a matching plug. Identify the documented monitoring connection before attaching an adapter. This worksheet is about selecting a monitoring path, not electrical installation.

Match Sunstead by protocol, then verify the model

Sunstead currently has readers for SRNE Modbus and Voltronic PI30/PI18 inverters; PACE V2.5, JBD UART and JBD UP16S battery protocols; and supported Renogy Modbus devices. Supported USB HID and Bluetooth paths are specific implementations, not blanket support for any USB or Bluetooth energy device.

The supported-devices section lists the product’s current scope. Renogy also publishes separate protocol documents by device category on its developer platform. A controller protocol and a battery protocol are not interchangeable just because both use Modbus.

Sunstead’s automatic discovery looks for matching responses. Detection is useful evidence, but it is not a certification of every model, firmware version or measurement. If a device stays unidentified, retain its exact details and investigate the protocol match before treating it as supported.

Write the readings you actually need

“Works with my inverter” can mean anything from basic solar power to detailed phase measurements. Decide what would make the installation useful before judging it by a connected badge.

For example, an inverter reporting battery voltage may be enough to watch terminal voltage alongside solar production. It does not satisfy a requirement to inspect individual cell readings. That requires a BMS path providing those fields. Keep the requirement precise and the test becomes straightforward.

Accept the connection with observations

1. Confirm the detected identity matches the equipment you intended to connect.
2. Compare available readings with the device’s own display at approximately the same time.
3. Observe an ordinary change in household demand or sunlight and confirm fresh samples continue.
4. Check whether all installed packs you expect to monitor are represented.
5. Confirm each physical device is counted once if both USB and Bluetooth are available.

Record unavailable fields as unavailable. Do not add a second reading of the same physical battery into the bank total. Sunstead flags certain ambiguous duplicate connections, but a clear installation record remains valuable.

Once the monitoring path is established, choose the computer and display using the Raspberry Pi planning guide. If another platform already documents your exact equipment, include it in your software shortlist.