API Telegram
The ADA P1 Meter provides electricity meter readings in the classic Telegram format. This format is a structured text output used by most European smart meters (e.g., DSMR standard), where each line contains a specific measured value.
The Telegram format is ideal for users who already use data processing tools (e.g., DSMR logger, OpenDatalogger, Python or Node.js parsers), or who simply prefer human-readable text output.
Endpoint
Telegram-formatted data is available at:
http://okosvillanyora.local:8989/telegram
Also available via IP:
http://192.168.x.x:8989/telegram
Data Refresh Rate
The Telegram output is updated every 10 seconds, and returns the latest measurement values at each request.
Example Telegram Output
/AUX5440252420024796
0-0:1.0.0(250329112720W)
0-0:42.0.0(AUX1020320024796)
0-0:96.1.0(440252420024796)
0-0:96.14.0(0002)
0-0:96.50.68(ON)
0-0:17.0.0(24.000*kW)
1-0:1.8.0(008323.570*kWh)
1-0:1.8.1(004043.669*kWh)
1-0:1.8.2(004279.901*kWh)
1-0:1.8.3(000000.000*kWh)
1-0:1.8.4(000000.000*kWh)
1-0:2.8.0(000000.001*kWh)
1-0:2.8.1(000000.001*kWh)
1-0:2.8.2(000000.000*kWh)
1-0:2.8.3(000000.000*kWh)
1-0:2.8.4(000000.000*kWh)
1-0:3.8.0(000000.807*kvarh)
1-0:4.8.0(002595.725*kvarh)
1-0:5.8.0(000000.807*kvarh)
1-0:6.8.0(000000.000*kvarh)
1-0:7.8.0(000000.000*kvarh)
1-0:8.8.0(002595.725*kvarh)
1-0:15.8.0(008323.571*kWh)
1-0:32.7.0(223.7*V)
1-0:31.7.0(006*A)
1-0:33.7.0(0.947)
1-0:14.7.0(49.99*Hz)
1-0:1.7.0(01.307*kW)
1-0:2.7.0(00.000*kW)
1-0:5.7.0(00.000*kvar)
1-0:6.7.0(00.000*kvar)
1-0:7.7.0(00.000*kvar)
1-0:8.7.0(00.324*kvar)
1-0:31.4.0(200*A)
0-0:98.1.0(250301000000W)(007453.019*kWh)(003657.588*kWh)(003795.431*kWh)(000000.001*kWh)(000000.001*kWh)(000000.000*kWh)(000000.802*kvarh)(002355.831*kvarh)(000000.802*kvarh)(000000.000*kvarh)(000000.000*kvarh)(002355.831*kvarh)(007453.020*kWh)(07.284*kW)(07.284*kW)(05.608*kW)(00.000*kW)(00.000*kW)(00.000*kW)
0-0:96.13.0()
!E819
About the Format
Each line in the Telegram output uses standard OBIS codes to define the type of data. For example:
0-0:1.0.0
→ timestamp (date and time)0-0:42.0.0
→ COSEM logical device name0-0:96.1.0
→ meter serial number (device ID)0-0:96.14.0
→ currently active tariff0-0:96.50.68
→ breaker status0-0:17.0.0
→ breaker limiter threshold (kW)0-0:98.1.0
→ end-of-month stored billing data0-0:96.13.0
→ message text (max 1024 characters)1-0:1.8.0
→ total active imported energy (all tariffs)1-0:1.8.1
→ imported energy for tariff T11-0:1.8.2
→ imported energy for tariff T21-0:1.8.3
→ imported energy for tariff T31-0:1.8.4
→ imported energy for tariff T41-0:2.8.0
→ total active exported energy (feed-in)1-0:2.8.1
→ exported energy for tariff T11-0:2.8.2
→ exported energy for tariff T21-0:2.8.3
→ exported energy for tariff T31-0:2.8.4
→ exported energy for tariff T41-0:15.8.0
→ absolute total active energy (|+A| + |-A|)1-0:3.8.0
→ positive reactive energy (Q+)1-0:4.8.0
→ negative reactive energy (Q-)1-0:5.8.0
→ reactive energy, import inductive (QI)1-0:6.8.0
→ reactive energy, import capacitive (QII)1-0:7.8.0
→ reactive energy, export inductive (QIII)1-0:8.8.0
→ reactive energy, export capacitive (QIV)1-0:1.7.0
→ instantaneous consumption (active import power)1-0:2.7.0
→ instantaneous feed-in (active export power)1-0:5.7.0
→ reactive power (QI, import inductive)1-0:6.7.0
→ reactive power (QII, import capacitive)1-0:7.7.0
→ reactive power (QIII, export inductive)1-0:8.7.0
→ reactive power (QIV, export capacitive)1-0:31.7.0
→ current (I) in phase L1 (A)1-0:51.7.0
→ current (I) in phase L2 (A)1-0:71.7.0
→ current (I) in phase L3 (A)1-0:32.7.0
→ voltage (U) in phase L1 (V)1-0:52.7.0
→ voltage (U) in phase L2 (V)1-0:72.7.0
→ voltage (U) in phase L3 (V)1-0:13.7.0
→ power factor (CosPhi, total)1-0:33.7.0
→ power factor (CosPhi, L1)1-0:53.7.0
→ power factor (CosPhi, L2)1-0:73.7.0
→ power factor (CosPhi, L3)1-0:14.7.0
→ frequency (Hz)1-0:31.4.0
→ current limit threshold for L11-0:51.4.0
→ current limit threshold for L21-0:71.4.0
→ current limit threshold for L3
These codes can easily be interpreted by automated systems using regular expressions or most DSMR parser libraries.
Use Cases
- Text-based logging (e.g., to SD card)
- Local parsing using shell/Python scripts
- Forwarding to MQTT for server-side logging or analysis
- Integration with DSMR-based systems
The Telegram format is not only backward compatible but also easy to integrate into any automation or data acquisition system.