Designed & made in France 6K fans on Facebook · Follow us
INTEGRATIONS7 min readBy the Pylon-Monitor teamUpdated

Pylontech with Jeedom, Node-RED, Domoticz and openHAB

Not using Home Assistant? The same JSON endpoint and MQTT topics work in Jeedom, Node-RED, Domoticz, openHAB and anything else that can make an HTTP request.

Short answer: yes, a Pylontech battery can be read by Jeedom, Node-RED, Domoticz, openHAB or Grafana. Pylon-Monitor exposes the battery data as plain JSON at one address on your network, /api.json, and can also publish it over MQTT. Anything that can make an HTTP request or subscribe to an MQTT topic can use it, with no plugin from us and no vendor SDK.

One JSON endpoint for every platform

Home Assistant gets most of the attention, and it has its own guide. Underneath, the mechanism is deliberately simple: one HTTP address, GET /api.json?key=…, with the access key shown in the device's Settings page, and plain JSON in return. Jeedom, Node-RED, Domoticz, openHAB, Grafana, a Python script or a cron job with curl all read exactly the same data.

Pylontech monitoring device JSON API response showing structured battery data
This one JSON response feeds every integration below. Nothing platform-specific on the device side.
Pylontech master battery panel: the RJ45 cable in the CONSOLE port feeds the Pylon-Monitor, while the stack link cable leaves LINK PORT 1 towards the slave battery
On the master battery: CONSOLE goes to the Pylon-Monitor, LINK PORT 1 goes to the slave battery.
The mistake almost everyone makes: LINK PORT 1, not LINK PORT 0
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.

Jeedom

Jeedom does not need a Pylontech plugin. Install the standard JSON plugin from the Jeedom market, point a piece of equipment at http://<device-ip>/api.json?key=<access-key>, and map JSON paths to commands: summary>soc, summary>voltage, summary>state, net>rssi and so on. Polling every 30 to 60 seconds is plenty. A battery does not change fast enough to need more.

Node-RED

Two ways, much like the choice in Home Assistant. Either poll with an http request node (method GET, URL http://<device-ip>/api.json?key=<access-key>, return "a parsed JSON object"), triggered by an inject node on a timer, then read fields such as msg.payload.summary.soc. Or, if MQTT is set up on the device, subscribe to pylon-monitor/state with an MQTT-in node. Updates then arrive as they are published, with no polling loop to manage.

Domoticz

Domoticz has no ready-made sensor type that polls JSON, but the usual workaround is well known: a short script (Python, or Domoticz's own Lua or Blockly events) fetches /api.json on a timer and pushes the values into Dummy/Virtual sensors through Domoticz's API. It takes a few more minutes than Jeedom or Node-RED, but you only do it once. Afterwards the sensors behave like any other Domoticz device, with history graphs and notifications.

openHAB

openHAB's HTTP Binding does this natively. Define a Thing pointing at http://<device-ip>/api.json?key=<access-key> with a refresh interval, then map each channel to a JSON path with a JSONPath transformation to get summary.soc, summary.voltage and so on into separate Items. The generic HTTP binding is enough; no custom binding needed.

Grafana, scripts and everything else

If a tool has a "JSON API" or "HTTP" data source, it can read this endpoint the same way: Grafana's JSON API plugin, Telegraf's HTTP input, a Python script with requests, a shell one-liner with curl | jq. The device does not care what sits on the other end of the request. That also means it does not become useless the day you change home automation platform.

Tuya / SmartLife

Tuya and SmartLife only talk to Tuya's cloud, so the local JSON address is no use to them directly. The device can publish the same JSON at a public HTTPS link (Settings > Public JSON access > "Enable a real public URL"), which IFTTT, Make.com or Apilio can then read and pass on to SmartLife. It is unofficial and you assemble it yourself. The details are in our Pylontech monitoring guide and in our answer to a customer who asked.

Polling or MQTT?

Most of the platforms above poll the JSON API on a timer. It is simple and works everywhere. If your platform also speaks MQTT (Node-RED and Home Assistant do), subscribing to pylon-monitor/state means updates arrive as soon as they are published instead of at the next poll. You also get the retained availability topic, so you know straight away when the device itself is offline instead of guessing from a stale value. That said, polling every 30 to 60 seconds is more than enough for a battery. Nothing here needs sub-second updates.

Same data everywhere. Home Assistant has its own auto-discovery because it is what people ask for most, not because the other platforms are second-class. They all read the same JSON structure and MQTT topics. Once the data is flowing, here is what those fields mean.

Frequently asked questions

Does Pylontech monitoring work with Jeedom?
Yes. The standard JSON plugin available in the Jeedom store can poll the device's /api.json endpoint directly and map fields to commands — no custom Jeedom plugin is needed.
Can I connect a Pylontech battery to Node-RED?
Yes, two ways: poll /api.json with an http request node, or subscribe to the MQTT state topic with an MQTT-in node if MQTT is configured on the device.
Does this work with Domoticz or openHAB too?
Yes. Domoticz typically uses a small script to push values into Dummy/Virtual sensors via its own API; openHAB's built-in HTTP Binding can poll the JSON endpoint directly with no custom binding required.

Pylon-Monitor's JSON API and MQTT topics are open, documented and not tied to any platform: plug it into whatever you already run.

Order now — €64 One-time purchase, €64 total — no VAT, no subscription.

Join 6,000 Pylon-Monitor fans on Facebook

News, firmware updates, real installations and tips: follow the page and ask your questions to the community.

Follow us on Facebook