In Belgium today, digital water meters are installed that transmit their meter reading via the digital electric meter. This meter reading is also available in the P1 message. Below is a logging of my meter: the water reading can be found at the very bottom at code 0-1:24.2.1.
In Belgium, the quarter-hourly peak is also logged: per quarter-hour the average power is calculated and per month the highest value of these quarter-hour averages is logged: the quarter-hourly peak (in dutch: "kwartuurspits"). This quarter-hourly peak also determines the capacity tariff.
The quarter-hourly value is accumulated and starts from 0 each quarter-hour and rises to the final value during the quarter-hour. This value is certainly useful of tracking to build up any alarms or actions. This value can be read at code 1-0:1.4.0.
The maximum quarter-hour peak of the current month can be found at code 1-0:1.6.0, preceded by the timestamp of the occurrence. Also useful to read out.
The line 0-0:98.1.0 seems to contain the previous months' quarter-hourly spikes, but that doesn't necessarily seem useful to read those out.
Is that possible for you to include these things in the data sent out from the DSMR Parser ? Or can I do this myself ?
In Belgium today, digital water meters are installed that transmit their meter reading via the digital electric meter. This meter reading is also available in the P1 message. Below is a logging of my meter: the water reading can be found at the very bottom at code 0-1:24.2.1.
In Belgium, the quarter-hourly peak is also logged: per quarter-hour the average power is calculated and per month the highest value of these quarter-hour averages is logged: the quarter-hourly peak (in dutch: "kwartuurspits"). This quarter-hourly peak also determines the capacity tariff. The quarter-hourly value is accumulated and starts from 0 each quarter-hour and rises to the final value during the quarter-hour. This value is certainly useful of tracking to build up any alarms or actions. This value can be read at code 1-0:1.4.0. The maximum quarter-hour peak of the current month can be found at code 1-0:1.6.0, preceded by the timestamp of the occurrence. Also useful to read out. The line 0-0:98.1.0 seems to contain the previous months' quarter-hourly spikes, but that doesn't necessarily seem useful to read those out.
Is that possible for you to include these things in the data sent out from the DSMR Parser ? Or can I do this myself ?
Thanks in advance!
/FLU5\253770234_A
0-0:96.1.4(50217) 0-0:96.1.1(3153414731313035343430333031) 0-0:1.0.0(230922172944S) 1-0:1.8.1(000981.942kWh) 1-0:1.8.2(001458.913kWh) 1-0:2.8.1(000000.000kWh) 1-0:2.8.2(000000.000kWh) 0-0:96.14.0(0001) 1-0:1.4.0(00.376kW) 1-0:1.6.0(230911181500S)(03.572kW) 0-0:98.1.0(5)(1-0:1.6.0)(1-0:1.6.0)(230501000000S)(230414001500S)(03.932kW)(230601000000S)(230525183000S)(03.183kW)(230701000000S)(230619181500S)(03.960kW)(230801000000S)(230730183000S)(04.048kW)(230901000000S)(230811151500S)(03.630kW) 1-0:1.7.0(00.086kW) 1-0:2.7.0(00.000kW) 1-0:21.7.0(00.086kW) 1-0:22.7.0(00.000kW) 1-0:32.7.0(224.6V) 1-0:31.7.0(000.97A) 0-0:96.3.10(1) 0-0:17.0.0(999.9kW) 1-0:31.4.0(999A) 0-0:96.13.0() 0-1:24.1.0(007) 0-1:96.1.1(3853455430303030383532373437) 0-1:24.2.1(230922172615S)(00013.207m3) !1D22