Short answer: there are two ways to get a Pylontech battery into Home Assistant with Pylon-Monitor, and both are built into the device. If you already run the Mosquitto broker, use MQTT auto-discovery: four fields to fill in, and eleven sensors appear on their own, plus sensors for each battery. If you do not run MQTT, use the REST platform: the device generates the YAML for you, ready to paste. No custom component, no HACS.
Two ways in, both already in the firmware
Search for "Pylontech Home Assistant" and you will find custom components, HACS repositories and YAML copied from forum threads several years old. With Pylon-Monitor there is nothing to install on the Home Assistant side. Both methods read the same data from the battery's Console port, so the choice is not about features. It depends on what you already have running.
Option 1: MQTT auto-discovery (the quick one)
If Home Assistant already runs the Mosquitto broker add-on, as most installs do, use this. Enter the broker's IP address, port, username and password on the device's Settings page and save. About five seconds later, eleven sensors show up under Settings → Devices & Services → MQTT, grouped in one device called Pylon-Monitor. No YAML, no restart, no entities to define by hand.
The eleven sensors are SOC, SOH, voltage, current, power, battery temperature, MOSFET temperature, charge cycles, battery state, cell imbalance and the number of batteries. That last one was added after a customer asked for it: the JSON API always had it, but having it in MQTT saves a separate REST call. With more than one battery, each unit also gets its own sensors (SOC, SOH, cycles, voltage, state), and its model, BMS version and serial number appear as attributes.
There is also an availability topic, backed by an MQTT "last will" message. If the device loses power or WiFi, every sensor turns grey in Home Assistant instead of freezing on its last value. That matters more than it sounds: a frozen SOC that still looks fine is exactly how a low-battery alarm ends up never firing.

The cable that chains your master battery to the first slave must leave LINK PORT 1 on the master — never LINK PORT 0. It plugs into LINK PORT 0 on the slave, and every further battery repeats the same 1 → 0 pattern. Wired the other way round the master never sees the rest of the stack, so Pylon-Monitor reports a single battery no matter how many you own.
Option 2: REST, if you do not use MQTT
No broker? Home Assistant's built-in rest platform can read the device's /api.json every 30 seconds and create six sensors: SOC, SOH, voltage, current, power and state. You do not have to write the YAML. The device's Settings page generates it with your IP address already filled in, and on recent firmware it also includes the access key the API now asks for. Copy it, paste it into configuration.yaml, restart Home Assistant.
configuration.yaml, no changes needed.
Which one to choose
- You already run a Mosquitto broker: MQTT auto-discovery. Quicker to set up, more sensors, and the availability signal on its own makes it worth it.
- No broker, and no wish to install one just for this: REST is fine. A 30-second poll instead of an instant push makes no difference for a battery, its values do not change that fast.
- A large Home Assistant install with dozens of MQTT devices: one more device on the broker costs nothing. Go with MQTT.
Several inverters, several separate stacks? Each stack gets its own Pylon-Monitor, and each one appears as its own device in Home Assistant. A customer with three stacks of eight US2000 asked us exactly that; here is how it works.
What to do with the sensors
New sensors on their own are just numbers on a card. A few automations that make them useful:
- Low battery notification. An automation that fires when SOC drops below a threshold and sends a push notification through the Home Assistant app. Handy if you prefer to keep all your alerts in Home Assistant rather than use the device's own Pushover alarm.
- Watching the cell imbalance. It rarely jumps overnight, but a slow rise over several weeks is exactly what a Home Assistant history graph shows and a quick look at the screen does not.
- A card next to your solar data. If you already track production and consumption in Home Assistant, putting the Pylontech SOC and power on the same dashboard gives you the whole picture in one place.
What these numbers mean, and which ones deserve a real alarm, is covered in our SOC, SOH and cell spread guide.
Quick troubleshooting
- The MQTT line stays red: check the broker IP address and the credentials. A dedicated MQTT user (see the tip above) is the most common fix when a reused Home Assistant login is refused.
- Duplicate entities: MQTT and REST are both set up for the same values. Remove one.
- A sensor shows "unavailable": if it happens exactly when the device loses WiFi or power, that is the availability signal doing its job, not a bug.
- REST sensors stopped after an update: recent firmware versions require the access key on the API. Copy the YAML again from the Settings page; it now contains the key.
Not using Home Assistant?
All of this relies on the same /api.json endpoint and MQTT topics used for Jeedom, Node-RED, Domoticz and openHAB. This guide covers the other platforms.
Tuya / SmartLife
Tuya and SmartLife only talk to Tuya's own cloud, and there is no official Pylontech integration for them. You can still build an unofficial bridge with IFTTT, Make.com or Apilio, using the public URL the device can publish (Settings > Public JSON access > "Enable a real public URL"). The steps are in our Pylontech monitoring guide, and in our answer to a customer who asked.
Frequently asked questions
- Do I need an MQTT broker to use Pylontech in Home Assistant?
- No. If you don't run an MQTT broker, Home Assistant's built-in REST platform can poll the device's JSON API directly and create six sensors — no broker required.
- How many sensors does Pylontech monitoring give me in Home Assistant?
- MQTT auto-discovery creates 11 sensors plus an availability signal. The REST platform creates 6 sensors from the same underlying data. If your pack has more than one Pylontech battery, MQTT also publishes 5 sensors per battery (SOC, SOH, cycles, voltage, state), and the JSON API always exposes a full per-battery breakdown regardless of which integration you use.
- Can I use both MQTT and REST at the same time?
- You can, but you shouldn't for the same values — it creates duplicate entities. Pick MQTT if you have a broker (it covers everything REST does and more); use REST only if you don't.
Pylon-Monitor comes with both: MQTT auto-discovery and the REST YAML generator are on the device, ready the moment you plug it in.
Order now — €64 One-time purchase, €64 total — no VAT, no subscription.