Help — how to connect devices
How to connect devices and services to HEMS — step-by-step guides. Type a manufacturer, model or keyword, e.g. “supla”, “modbus”, “token”.
Start here
Where to start
The order in which you'll see your first data in the panel fastest.
Adding a Zamel device to your SUPLA account (Wi-Fi and the SUPLA app)
Before HEMS can read a meter, the device must be connected to Wi-Fi and added to your SUPLA account. You do this once — with the SUPLA app on your phone or manually in a browser.
Importing history from SUPLA — archive data step by step
SUPLA Cloud keeps a measurement log of your devices. HEMS fetches it in the background and adds it to charts, balances, reports and ROI — even several years back, depending on your package.
Zamel SUPLA — supported devices and choosing a model
All Zamel SUPLA devices are connected the same way: a personal token from SUPLA Cloud and the channel ID. No ESP32 connector is needed.
Nothing found. Try a shorter word or a manufacturer name.
Ask usGetting started 7
Where to start
The order in which you'll see your first data in the panel fastest.
ESP32 connector: flashing and pairing
The connector is an ESP32 board on your home network that reads devices locally and sends data to HEMS.
QRpassword 1234567890
Connector: CPU and communication speed
About every minute the connector reports its status. The panel shows the last 24 hours — older reports are deleted.
24 hfirmware 0.30+
Connector: what the LED means
The LED on the board shows the connector state. ESP32 boards (E32, W32) have a single-colour, usually blue LED on GPIO2; ESP32-S3 DevKit (S3D) and T-Connect (TCN) have a colour LED. The red LED next to it is just power.
ESP32ESP32-S3
Connector: board comparison (CPU, RAM, memory)
HEMS has firmware images for 7 boards. All have a dual-core 240 MHz CPU and 2.4 GHz Wi-Fi; they differ in chip generation (ESP32 or ESP32-S3), program space, extra PSRAM and connectors.
7 boardsfirmware 0.30.4
Device role in the site balance (primary source)
The dashboard, consumption history and reports take each site quantity from one device. On the device page, in the “Role in the site balance” section, you can see which device is used now and change it.
device page
Checking the first readings
Most drivers are marked “unverified” until someone confirms them on that model.
Meters and sensors 8
Adding a Zamel device to your SUPLA account (Wi-Fi and the SUPLA app)
Before HEMS can read a meter, the device must be connected to Wi-Fi and added to your SUPLA account. You do this once — with the SUPLA app on your phone or manually in a browser.
one-time
Zamel SUPLA — supported devices and choosing a model
All Zamel SUPLA devices are connected the same way: a personal token from SUPLA Cloud and the channel ID. No ESP32 connector is needed.
no connector
Zamel MEW-01 and related electricity meters (SUPLA)
MEW-01, MEW-02, MEW-01/1F and LEW electricity meters are read via SUPLA Cloud — no ESP32 connector is needed. You need a personal token and the meter’s channel number.
testedno connectorhistory importgrid parameters
Zamel LIW-01 and LIW-03 ETH impulse counters (electricity, water, gas, heat)
LIW counts impulses from the meter’s impulse output (or an impulse reader) and turns them into a meter reading. HEMS reads it from SUPLA Cloud every 5 minutes.
no connectorhistory import
Zamel THW-01 temperature and humidity sensor
THW-01 measures temperature and humidity. HEMS reads them from SUPLA Cloud every 5 minutes and can import the history.
no connectorhistory import
SUPLA relay or socket as an actuator
Any switch channel added to SUPLA (relay, socket, light switch, staircase timer) can be an actuator in HEMS. HEMS switches it on and off via SUPLA Cloud, and every command goes through the Command Gateway — with permissions, simulation mode and safety limits.
no connectorcontrol
Shelly — relays, plugs and meters
You can connect Shelly in two ways: locally via an ESP32 connector on the same network (read every 15 s, works without internet) or via Shelly Cloud from the HEMS server (no connector, read every minute or less often). HEMS switches relays and plugs on and off with a command through the Command Gateway.
connector or cloudcontrol
BleBox — switchBox, switchBoxD, meters and sensors
You connect BleBox devices locally via an ESP32 connector on the same network. HEMS reads state, power and temperature and switches relays on and off with a command through the Command Gateway.
connectorcontrol
Historical data 1
Inverters 6
Deye Cloud — installation from the Deye cloud
Reading a Deye installation from Deye Cloud — no connector and no access to the home network. Power every 5 minutes and history import.
no connectorhistory import
Solarman — installation from the Solarman cloud
Reading an installation from the Solarman cloud (inverters with a Solarman logger: Deye, Sofar, Afore and others) — no connector. Power every 5 minutes and history import.
no connectorhistory import
FoxESS Cloud — installation from the FoxESS cloud
Reads a FoxESS inverter from FoxESS Cloud — no connector and no access to the home network. Power every 5 minutes and history import.
no connectorhistory import
Grid export limit (zero export, negative prices)
HEMS can change the grid export limit in the inverter — e.g. 0 W when the sell price is negative, or a fixed limit from the connection conditions. The fast control is done by the inverter itself on its own meter (CT); HEMS only sets the limit.
controlprices
Deye hybrid with storage and string inverters
A typical setup: a Deye hybrid inverter handles PV strings and the energy storage, with string inverters alongside. How to add it so the balance is complete and nothing is counted twice.
connectorbatterybalance
LuxPower / EG4 via Wi-Fi dongle
Reading a LuxPower inverter through its Wi-Fi dongle (connector firmware ≥ 0.28).
Heat pumps 6
Heat recovery unit — readings, speed and ventilation automation
Connect the heat recovery unit via Modbus to the ESP32 connector (RS485 or Modbus TCP on the LAN) or — for Compit controllers — via the iNext cloud. HEMS reads the temperatures of the four air streams, humidity, speed and filter state, and changes speed and intensive ventilation with a command through the Command Gateway.
connector or cloudcontrol
Air conditioner — Daikin, LG, Samsung, Mitsubishi, Intesis gateways and cooling automation
Connect Daikin (Onecta API), LG (ThinQ Connect), Samsung (SmartThings) and Mitsubishi Electric (MELCloud, MELCloud Home) air conditioners through the manufacturer cloud — from the HEMS server, no connector — and units of many brands through an Intesis Modbus RTU gateway and the ESP32 connector. HEMS reads operation, mode, setpoint and room temperature, and switches on/off, changes mode and temperature by command through the Command Gateway.
cloud or connectorcontrol
Rotenso heat pump and Tuya devices
Rotenso and other devices using the Tuya / Smart Life app are read through the Tuya cloud.
Viessmann (ViCare)
Official ViCare API — you log in with the owner's ViCare account, HEMS never sees the password.
Mitsubishi Ecodan (MELCloud and MELCloud Home)
Reading and control through the Mitsubishi cloud, from the HEMS server.
Vaillant via ebusd
Local reading of a Vaillant heat pump through an eBUS adapter and the ebusd service — read-only.
EV chargers 5
go-e charger (Cloud API)
Reading and current limit via the go-e Cloud API, from the HEMS server.
Easee charger
Reading and dynamic current via Easee Cloud, from the HEMS server.
Zaptec charger
Zaptec installation current limit via the Zaptec Cloud API.
Charger via OCPP 1.6J
OCPP chargers connect to a HEMS node on your home network.
Fronius Wattpilot
Wattpilot local API through the connector (firmware ≥ 0.27).
Connection methods 11
Modbus TCP (LAN)
Inverters with an Ethernet/Wi-Fi port and Modbus TCP enabled, meters, EV chargers, heat pumps, Victron GX.
SunSpec (Modbus TCP)
SMA, SolarEdge, Fronius, Kostal, KACO, ABB/FIMER and other SunSpec-compliant inverters.
Solarman V5 logger (Wi-Fi)
Deye, Sofar, Solis, Afore, Megarevo and other inverters with a Solarman Wi-Fi logger (e.g. LSW-3).
Modbus RTU (RS485, wired)
Eastron SDM meters, inverters with an RS485/COM port, JK BMS PB, chargers with RS485.
GoodWe (local UDP)
GoodWe ET/EH/BT/BH hybrids and older ES/EM/ESA/SBP/BP with a Wi-Fi/LAN module.
Local HTTP API
Fronius Solar API, Enphase IQ Gateway, OpenDTU (Hoymiles microinverters), Shelly (meters, relays, plugs), BleBox (switchBox, meters), Pstryk meter, APsystems EZ1.
Storage and BMS: JK, Daly, CAN
JK BMS (Bluetooth), Daly BMS (UART), BMS with CAN output using the Pylontech protocol (Pylontech, Seplos, JK, Daly, Pace…).
Victron VE.Direct (cable)
SmartSolar/BlueSolar MPPT charge controllers, SmartShunt, BMV-70x/71x.
Voltronic / Axpert inverters (UART)
Off-grid and hybrid inverters using the Voltronic protocol (Axpert, EASUN, MPP Solar and derivatives).
EV chargers via OCPP 1.6J
Chargers with OCPP 1.6J: Wallbox, Zaptec Pro, ABB, Alfen, Ekoenergetyka and others.
Manufacturer cloud (no connector)
Deye Cloud, Solarman, FoxESS Cloud, Zamel SUPLA (meters, sensors, relays), Tuya, Viessmann ViCare, Mitsubishi MELCloud, go-e, Easee and Zaptec chargers.
Your device is missing or a guide doesn't match?
Report it
Write to us — we will extend the help and add the driver.