Pylontech Viewer: Every Way to Actually See Your Battery Data

What people actually mean by a "Pylontech viewer"

Search for a Pylontech viewer and you'll find half a dozen different things wearing the same name: a Windows program, a phone app bundled with an inverter, a web page on a local IP, a Home Assistant dashboard. They are not interchangeable. Each one reads a different port on the battery, and — this is the part nobody says out loud — each one therefore shows you a different subset of what the battery actually knows about itself.

This page walks through every realistic way to view Pylontech battery data, what each one genuinely displays, and where each one stops. No option here is dismissed: the laptop route is free and works, and for some people that is the correct answer.

Option 1 — PYLON Console / BatteryView on a laptop

The official route. Pylontech's own Windows software (usually PYLON Console, sometimes shipped as BatteryView) talks to the battery's Console (RS-232) port through an RJ45-to-serial adapter. It is free, it is complete, and it is what an installer uses on commissioning day.

What it shows: essentially everything — SOC, SOH, per-cell voltages, temperatures, cycle count, alarm flags, firmware version, per-module detail across the whole stack.

Where it stops: it only shows you any of that while you are physically sitting in front of the battery with a laptop and the right cable. There is no history, no trend, no alert. In practice most owners run it once at installation and then perhaps once more when something already feels wrong — which is precisely the moment when six months of trend data would have been useful and doesn't exist. If you want the full argument for why that gap matters, the monitoring guide covers it properly.

Option 2 — Your inverter's screen or app

If your Pylontech stack is wired to a Victron, Deye, Sunsynk, Growatt, Sofar, Solis or similar hybrid inverter over CAN or RS485, that inverter already displays battery data — on its own screen, and usually in its own phone app or portal too. For a lot of people this is the viewer they use daily, and for checking "am I charging right now, and how full am I", it is perfectly adequate.

Where it stops is structural, not a matter of a better app: the CAN/RS485 link is a control protocol. It deliberately describes the entire battery stack as one single virtual battery. That means no per-module SOH, no individual cell voltages, no per-module temperatures — not because the inverter's software is lazy, but because the battery never sends those over that link in the first place. The inverter port guide breaks down exactly what each RJ45 socket carries and why the Console port stays free for a second reader.

Option 3 — A permanent web dashboard on your own network

The third option is a small device that stays plugged into the Console port permanently and serves the data as a web page on your local network. Instead of a viewer you launch, it's a viewer that is simply always there: open a browser on any phone or laptop in the house, type the device's local address, and the current state of every battery in the stack is on screen. Nothing to install, no account, no cloud round-trip.

This is what Pylon-Monitor does — that is its entire job, and the screenshot above is the real interface, not a mockup. You can walk through every screen of it here before deciding whether it's the shape of viewer you want.

Because it reads the Console port, it sees the full detail the inverter link can't carry: per-module SOC, SOH, cycles and temperatures across up to 16 chained batteries, plus per-cell voltages. And because it's permanent, it can do the things a laptop session structurally cannot — log a trend, and raise an alarm when a threshold is crossed while nobody is looking.

Option 4 — Build your own viewer from the JSON API

If none of the above is quite your shape, the honest answer is to build it. Any device that exposes the battery state as structured data lets you render it however you like. Pylon-Monitor answers GET /api.json on its local IP with the complete battery state as JSON — SOC, SOH, voltage, current, power, per-cell voltages, temperatures, alarms — with no cloud in the path and no API quota.

From there, a Grafana panel, a Node-RED flow, a wall-mounted tablet page or a five-line shell script are all equally valid viewers. The integrations guide shows the same endpoint feeding Jeedom, Node-RED, Domoticz, openHAB and Grafana, and if Home Assistant is your stack, MQTT auto-discovery puts ten sensors in front of you with no YAML at all.

Every Pylontech viewer, side by side

So which viewer should you use?

• You check the battery once a year and that's fine. Use PYLON Console on a laptop. It costs nothing and shows everything. Genuinely, don't buy hardware for this.
• You just want to know if it's charging. Your inverter's app already does that. Nothing to add.
• You want to catch a problem before it becomes one. You need something permanent — cell imbalance creeping up over weeks is invisible to every once-a-year check, and it's the earliest warning you get. What to actually watch for is here.
• You want the data inside your own system. Go for the JSON/MQTT route and render it wherever your automation already lives.