Skip to main content

API JSON

The ADA P1 Meter provides real-time measurement data in JSON format, which can be easily processed by various external systems and custom-developed solutions.

Endpoint​

JSON data is available on the local network at the following address:

http://okosvillanyora.local:8989/json

If mDNS is not supported on the device, you can also use the IP-based access:

http://<device IP address>:8989/json

Example:

http://192.168.1.123:8989/json

Update Frequency​

The device updates the JSON data every 10 seconds, providing virtually real-time information on current energy consumption and feed-in.

The JSON output is not event-driven, but rather continuously updated and queryable. Each update returns a new, complete data structure.

Sample JSON Output​

{
  "username": "info@greenhess.com",
  "password": "0db27adf04f4d151cc74c4f09de85410",
  "client_id": "D0_EF_76_33_11_24",
  "os_version": "1.2.71",
  "local_ip": "192.168.31.138",
  "timestamp": "250329112610W",
  "cosem_logical_device_name": "AUX1020320024796",
  "meter_serial_number": "440252420024796",
  "current_tariff": "0002",
  "circuit_breaker_status": "ON",
  "limiter_threshold": "24.000",
  "active_import_energy_total": "8323.547",
  "active_import_energy_tariff_1": "4043.669",
  "active_import_energy_tariff_2": "4279.878",
  "active_import_energy_tariff_3": "0.000",
  "active_import_energy_tariff_4": "0.000",
  "active_export_energy_total": "0.001",
  "active_export_energy_tariff_1": "0.001",
  "active_export_energy_tariff_2": "0.000",
  "active_export_energy_tariff_3": "0.000",
  "active_export_energy_tariff_4": "0.000",
  "reactive_import_energy": "0.807",
  "reactive_export_energy": "2595.719",
  "reactive_energy_qi": "0.807",
  "reactive_energy_qii": "0.000",
  "reactive_energy_qiii": "0.000",
  "reactive_energy_qiv": "2595.719",
  "total_active_energy": "8323.548",
  "voltage_phase_l1": "223.900",
  "voltage_phase_l2": "0.000",
  "voltage_phase_l3": "0.000",
  "current_phase_l1": "2.000",
  "current_phase_l2": "0.000",
  "current_phase_l3": "0.000",
  "current_phase_Bl1": "3.202",
  "current_phase_Bl2": "0.000",
  "current_phase_Bl3": "0.000",
  "power_factor": "0.000",
  "power_factor_l1": "0.781",
  "power_factor_l2": "0.000",
  "power_factor_l3": "0.000",
  "frequency": "49.990",
  "instantaneous_power_import": "0.560",
  "instantaneous_power_export": "0.000",
  "instantaneous_reactive_power_qi": "0.000",
  "instantaneous_reactive_power_qii": "0.000",
  "instantaneous_reactive_power_qiii": "0.000",
  "instantaneous_reactive_power_qiv": "0.324",
  "current_limit_l1": "200.000",
  "current_limit_l2": "0.000",
  "current_limit_l3": "0.000"
}

The exact key names and structure may vary depending on the firmware version, but we keep the documentation up to date if any changes occur.

Field NameValue / FormatUnit of MeasurementOBIS CodeSource
usernameinfo@greenhess.com--K
password0db27adf...--K
client_idD0_EF_76_33_11_24--K
os_version1.2.71--K
local_ip192.168.31.138--K
timestamp250329112610Widőbélyeg-M
cosem_logical_device_nameAUX1020320024796COSEM név-M
meter_serial_number440252420024796mérő sorszám-M
current_tariff0002jelenlegi tarifa-M
circuit_breaker_statusONmegszakító állapota-M
limiter_threshold24.000kW0-0:17.0.0M
active_import_energy_total8323.547kWh1-0:1.8.0M
active_import_energy_tariff_14043.669kWh1-0:1.8.1M
active_import_energy_tariff_24279.878kWh1-0:1.8.2M
active_import_energy_tariff_30.000kWh1-0:1.8.3M
active_import_energy_tariff_40.000kWh1-0:1.8.4M
active_export_energy_total0.001kWh1-0:2.8.0M
active_export_energy_tariff_10.001kWh1-0:2.8.1M
active_export_energy_tariff_20.000kWh1-0:2.8.2M
active_export_energy_tariff_30.000kWh1-0:2.8.3M
active_export_energy_tariff_40.000kWh1-0:2.8.4M
reactive_import_energy0.807kvarh1-0:3.8.0M
reactive_export_energy2595.719kvarh1-0:4.8.0M
reactive_energy_qi0.807kvarh1-0:5.8.0M
reactive_energy_qii0.000kvarh1-0:6.8.0M
reactive_energy_qiii0.000kvarh1-0:7.8.0M
reactive_energy_qiv2595.719kvarh1-0:8.8.0M
total_active_energy8323.548kWh1-0:15.8.0M
voltage_phase_l1223.900V1-0:32.7.0M
voltage_phase_l20.000V1-0:52.7.0M
voltage_phase_l30.000V1-0:72.7.0M
current_phase_l12.000A1-0:31.7.0M
current_phase_l20.000A1-0:51.7.0M
current_phase_l30.000A1-0:71.7.0M
current_phase_Bl13.202A-K
current_phase_Bl20.000A-K
current_phase_Bl30.000A-K
power_factor0.000-1-0:13.7.0M
power_factor_l10.781-1-0:33.7.0M
power_factor_l20.000-1-0:53.7.0M
power_factor_l30.000-1-0:73.7.0M
frequency49.990Hz1-0:14.7.0M
instantaneous_power_import0.560kW1-0:1.7.0M
instantaneous_power_export0.000kW1-0:2.7.0M
instantaneous_reactive_power_qi0.000kvar1-0:5.7.0M
instantaneous_reactive_power_qii0.000kvar1-0:6.7.0M
instantaneous_reactive_power_qiii0.000kvar1-0:7.7.0M
instantaneous_reactive_power_qiv0.324kvar1-0:8.7.0M
current_limit_l1200.000A1-0:31.4.0M
current_limit_l20.000A1-0:51.4.0M
current_limit_l30.000A1-0:71.4.0M

Note: In the Source column, the letter M indicates values measured directly by the energy meter, while K refers to values calculated or derived by the system.

Use Cases​

The JSON output is ideal for users who want to:

  • Store measurements in their own InfluxDB database
  • Visualize data using Grafana or other dashboard tools
  • Develop custom analytics software or mobile apps
  • Automate energy usage (based on scripts or rules)
  • Perform offline, local data collection

Data Retrieval Options​

HTTP GET requests can be made from any device, for example using a simple curl command:

curl http://okosvillanyora.local:8989/json

The data can be processed by any system, such as:

  • Python (e.g., requests, pandas)
  • Node.js
  • Bash scripts
  • Local data collection tools

Important Notes​

  • The JSON output contains only the current measurement – it does not include historical data or storage.
  • For long-term analysis, store the data in your own system (InfluxDB, CSV, SQLite, etc.).
  • The JSON output does not require login or authentication within the local network.

Tips for Developers​

  • Schedule data retrieval (e.g., using cron jobs or regular REST calls)
  • Push data to your own server or the cloud
  • Integrate using Python scripts (e.g., pandas, Flask, MQTT bridge, etc.)

The JSON API makes it possible for the ADA P1 Meter to be more than just a simple display – it becomes a true data provider device, easily integratable into any system.