High-voltage Pylontech monitoring: the last gap just closed

The one battery a Pylon-Monitor could not read

Until firmware 2.8, this site carried an admission on its comparison page that cost us sales, and we left it there on purpose: if you owned a high-voltage Pylontech pack — a Force H2 tower, H48050 modules stacked behind a management unit — our box was not for you. Buy the competitor's, we said, we would rather tell you than sell you the wrong thing.

That sentence is gone. Since 8 September 2026, the new generation of Pylon-Monitor reads high-voltage towers, and it reads them the same way it reads everything else: over the Console port, without writing a single byte into your BMS.

Why high voltage was hard, in one table

People assume "high voltage" means a different cable or a different port. It does not. The connector is the same RJ45 Console port, the electrical level is the same RS-232, the speed is the same 115200 baud. What changes is the conversation, and it changes completely.

A firmware that knows only the left-hand column does not fail loudly when it meets the right-hand one. It asks its usual question, gets an answer it cannot parse, and shows you an empty dashboard. That is exactly what every high-voltage owner who plugged in a Pylon-Monitor saw: a device that was plainly alive, connected to a battery that was plainly answering, and nothing on screen.

What the box does now

Firmware 2.8 recognises a high-voltage pack from its very first reply and switches to the right set of questions. There is nothing to configure, no model to pick in a menu, no mode to remember — and it switches back on its own if you move the cable to a low-voltage stack. From there, everything lands where it always did: charge, voltage, current, power and temperatures on the screen and the dashboard, every module in the "your batteries" table, every cell in the cell chart, all of it in the JSON API and in Home Assistant over MQTT.

A high-voltage tower also reports things a low-voltage stack simply does not have, and those get a card of their own: the lowest and highest cell in the whole tower, the lowest and highest module, the charge and discharge limits the management unit is enforcing right now, the charge level expressed in energy as well as in amp-hours, the detailed status fields and the error code.

Two things it will not show you, because your pack does not report them: state of health and cycle count. Those two lines show a dash. We could have filled them with an estimate and nobody would have known — a dash is the honest answer, and on a battery it is the one that matters.

Still read-only, and that is the whole point

The four commands sent to a high-voltage pack are the four that read: pwr, unit, bat, info. Nothing is ever written to your BMS. There is no path — not from your network, not from us, not from anyone — by which anything could reach your battery's port and change a setting.

This is not a missing feature. It is the design decision that makes the risk of installing this box zero: a device that only ever reads cannot alter your pack's behaviour, cannot corrupt a parameter, cannot damage your installation, and cannot put your Pylontech warranty in question. On a 400 V tower that argument is worth more, not less.

Where that leaves the category

Until now, choosing a Pylontech monitor meant trading something away. A cloud box gave you high-voltage support but took your data through someone else's servers and asked for the right to write into your battery. A DIY build gave you independence and cost you a weekend and a soldering iron. A laptop on the Console port gave you everything, once, and no history at all.

With the high-voltage gap closed, Pylon-Monitor is the only one that puts the complete card on the table at once:

• a 1.8" colour TFT screen on the device itself — the number you actually glance at, in the room where the battery is, with no phone in hand;
• a dashboard served by the box, not by a server: it keeps working with the internet down, and it will still be there if we are not;
• a local JSON API and MQTT auto-discovery — Home Assistant finds every sensor by itself, no YAML, no bridge, no account;
• history included, no subscription, no per-month anything;
• read-only firmware, so installing it cannot change or damage anything;
• both battery families, low voltage and high voltage, on one box;
• and a one-off price well under a third of the cloud alternative.

Take any one of those away and there is a competitor who does the rest. Ask for all seven together and the list is one item long. That is what has changed: high voltage was the last row where somebody else could still say "yes" and we had to say "not yet".

The caveat we would rather say ourselves

We do not own a high-voltage pack. This support was written against real console readings from two different management-unit firmwares — a four-module tower and a 120-cell, eight-module one — and both are replayed against the parser every time the firmware is built, including one capture that arrived truncated mid-table, because real readings do. What we cannot claim is field time: no Force H2 has yet been connected to a Pylon-Monitor.

So if you run high voltage and you want a track record rather than a first, the honest answer is still on the comparison page, unchanged. If your management unit answers in a way we have not seen, the box has a discovery page that collects exactly what it says — send it to us and the next firmware speaks your dialect. That loop is how this support came to exist in the first place.

Getting it

High-voltage support needs the new hardware generation, which every unit ordered from 5 September 2026 carries. If you already own a Pylon-Monitor, firmware 2.8 is a free download like every version before it; your device's own update page tells you which of the two files is yours, and picking the wrong one changes nothing — the box checks the file before writing anything and keeps running what it has.

New to all this? The monitoring guide covers what remote Pylontech monitoring is worth in the first place, and the diagnostics guide explains what the numbers mean once you have them.