Custom MQTT is used to send meter data to a custom MQTT server. This is useful for integrating the
device with your own IoT platform.
The payload content will be the same one returned by the REST API endpoint meter
(swagger).
InfluxDB is used to send meter data to an InfluxDB time-series database. This is useful for storing
historical data and creating dashboards with tools like Grafana.
The data will be sent in InfluxDB Line Protocol format with all meter values as fields.
A custom integration for Home Assistant that exposes all device channels as native sensors (voltage, current, active/reactive/apparent power, power factor, and energy totals). It uses the device REST API and works fully on the local network, with no cloud dependency.
energyme folder
into your custom_components directory.admin,
password energyme). Active channels are discovered automatically.Full documentation, troubleshooting, and screenshots are available in the integration repository.
The REST API provides comprehensive access to all device functions including meter readings, channel configuration, energy data archives, and system control.
All endpoints require Digest Authentication. The interactive Swagger UI allows you to explore and test API endpoints directly from your browser.
The Modbus TCP server is running on port 502 and provides read-only access to meter values via the standard Modbus protocol. Function Code 03 (Read Holding Registers) is supported. No configuration needed - the server is always available when the device is powered on.
0-3: Unix timestamp (int64)4-7: System uptime in milliseconds (uint64)100-101: Voltage (float32)102-103: Grid frequency (float32)Power and energy values aggregated by channel role. Each role has 18 registers (9 values × 2 registers each).
200-201: Grid active power (float32, W)202-203: Grid reactive power (float32, VAR)204-205: Grid apparent power (float32, VA)206-207: Grid power factor (float32)208-209: Grid active energy imported (float32, Wh)210-211: Grid active energy exported (float32, Wh)212-213: Grid reactive energy imported (float32, VARh)214-215: Grid reactive energy exported (float32, VARh)216-217: Grid apparent energy (float32, VAh)300-301: Load active power (float32, W)302-303: Load reactive power (float32, VAR)304-305: Load apparent power (float32, VA)306-307: Load power factor (float32)308-309: Load active energy imported (float32, Wh)310-311: Load active energy exported (float32, Wh)312-313: Load reactive energy imported (float32, VARh)314-315: Load reactive energy exported (float32, VARh)316-317: Load apparent energy (float32, VAh)400-401: PV active power (float32, W)402-403: PV reactive power (float32, VAR)404-405: PV apparent power (float32, VA)406-407: PV power factor (float32)408-409: PV active energy imported (float32, Wh)410-411: PV active energy exported (float32, Wh)412-413: PV reactive energy imported (float32, VARh)414-415: PV reactive energy exported (float32, VARh)416-417: PV apparent energy (float32, VAh)500-501: Battery active power (float32, W)502-503: Battery reactive power (float32, VAR)504-505: Battery apparent power (float32, VA)506-507: Battery power factor (float32)508-509: Battery active energy imported (float32, Wh)510-511: Battery active energy exported (float32, Wh)512-513: Battery reactive energy imported (float32, VARh)514-515: Battery reactive energy exported (float32, VARh)516-517: Battery apparent energy (float32, VAh)600-601: Inverter active power (float32, W)602-603: Inverter reactive power (float32, VAR)604-605: Inverter apparent power (float32, VA)606-607: Inverter power factor (float32)608-609: Inverter active energy imported (float32, Wh)610-611: Inverter active energy exported (float32, Wh)612-613: Inverter reactive energy imported (float32, VARh)614-615: Inverter reactive energy exported (float32, VARh)616-617: Inverter apparent energy (float32, VAh)For each active channel (0 to N-1, where N is the device's channel count - 16 on PCB v6.1), registers are organized as follows:
+0-1: Current (float32)+2-3: Active power (float32)+4-5: Reactive power (float32)+6-7: Apparent power (float32)+8-9: Power factor (float32)+10-11: Active energy imported (float32)+12-13: Active energy exported (float32)+14-15: Reactive energy imported (float32)+16-17: Reactive energy exported (float32)+18-19: Apparent energy (float32)Examples:
1000-10011100-11011502-1503The device advertises its services via mDNS (Multicast DNS) for easy discovery on your local network. This allows compatible clients and tools to automatically discover the device without needing to know its IP address.
_http._tcpdevice_id: Unique device identifiervendor: Manufacturer namemodel: Product modelversion: Firmware versionpath: Root path (/)auth: Authentication requiredssl: SSL/TLS support status_modbus._tcpdevice_id: Unique device identifiervendor: Manufacturer namemodel: Product modelversion: Firmware versionchannels: Number of available channels (16)