Watermeter

Gebruikte materialen

Arcus-EDS
KNX-GW-MBUS REG

Maddalena FlowPulse M-Bus Counter

Analoge watermeter

Maddalena MVM – POSITIVE DISPLACEMENT ROTARY PISTON WATER METER

KNX Config

MBus DPT Identifier
The M-Bus was developed for configuration and reading of data from meters and consumption counting devices. The M-Bus is a
bus with a single master that powers and reads out multiple slave devices. Each slave is addressable with an individual ID that is
between 1 and 250. Theoretically up to 250 slave devices could be operated in one M-Bus segment, but the practical number is
determined by the ability of the master to power the devices. The topology is not critical and no termination is required. Maximum
bus length is 4km in theory depending on the baudrate, in practical situations not more than 10m should be aspired for good
noise immunity.
The M-Bus gateway can power up to 3 devices and communicate with them. If only one device is present, this can be addressed
independent of its individual ID with the broadcast ID ( 254 ). This simplifies the configuration of such a minimal system.
Some M-Bus devices can be powered through the M-Bus, others draw current from the internal battery at readout of the data. So
some M-Bus devices only allow a certain number of readings over an amount of time to disburden the internal batteries. The
readout cycles must be choosen accordingly.
Readout of the devices data is initiated by the master by sending a REQ_UD2 ( Request User Data ) telegram. The connected
devices check if they are addressed by comparing their ID and return a RSP_UD ( Respond User Data ) telegram. The RSP_UD
telegram contains up to 252 byte of user data. The user data consists of several data packages each of them beginning with
some identification bytes, the DIF ( Data Information Field ) and the VIF ( Value Information Field ). DIF and VIF can have several
byte, of practical relevance are 1 or 2 byte per field. With 4 byte nearly all data packages can be identified. If a value field
represents a reference value there is usually a date field associated with this value. The information that can be expected in the
DIF and VIF are different with every manufacturer and every device class. Generally the desired informations can be achieved
from the manufacturers. The values for the DIF and VIF must be identified and written into the appropriate fields as strings of
hexadecimal characters.
Water meter
Volume information DIF 04 VIF 13 Data to write into the parameter field: 0413
Reference value DIF 04 VIF 80 13 Data to write into the parameter field: 048013

Electrical Meter
Total consumption DIF 04 VIF 03 Data to write into the parameter field: 0403
Actual consumption DIF 02 VIF 2B Data to write into the parameter field: 022B

Hassio Update

Added offset 16,402 to reflect identical meter value

sensor.yaml

water_consumption_m3:
friendly_name: “Total Water Consumption m3”
unit_of_measurement: ‘m3’
value_template: “{{ (states(‘sensor.waterarcus’)|float / 1000 + 16.402) | round(0) }}”