Please help to read water meter with MBus (configuration Home Assistant)

[Psicrow925]

Dear community

I would like to read my water meter via Mbus.
Since this is a very special project, or I lack the necessary knowledge, I ask you for help.

I use Home Assistant OS on an Intel NUC. The OS is up to date with the latest updates.
To integrate the Mbus data, I use the edge version of wmbusmeters.

wmbusmeters seems to recognize the Mbus master converter.
However, something seems to be misconfigured as I am not receiving any values.

IZAR PORT PULSE MINI Technische Dokumentation.pdf

telegram=|681C1C680801727916071424239507CA01273E|06160000000000000296280101|1616|

Auto driver  : not found!
Best driver  : dme_07 06/08
Using driver : dme_07 06/08
000   : 68 start
001   : 1c length (28 bytes)
002   : 1c length again (28 bytes)
003   : 68 start
004   : 08 dll-c (RSP_UD2)
005   : 01 dll-a primary (1)
006   : 72 tpl-ci (long header)
007   : 79160714 tpl-id (14071679)
011   : 2423 tpl-mfct (HYD)
013   : 95 tpl-version
014   : 07 tpl-type (Water meter)
015   : ca tpl-acc-field
016   : 01 tpl-sts-field (BUSY)
017   : 273e tpl-cfg 3e27 (synchronous SPECIFIC_16_31 )
019   : 06 dif (48 Bit Integer/Binary Instantaneous value)
020   : 16 vif (Volume m³)
021 C!: 000000000000 ("total_m3":0)
027   : 02 dif (16 Bit Integer/Binary Instantaneous value)
028   : 96 vif (Volume m³)
029   : 28 combinable vif (IncrPerInputPulseChannel0)
030 C?: 0101
032   : 16 crc
033   : 16 end

{
    "media":"water",
    "meter":"dme_07",
    "name":"",
    "id":"14071679",
    "total_m3":0,
    "timestamp":"2024-02-01T14:24:09Z"
}


Using: wmbusmeters: 1.14.0-78-g866df74
866df740addf23546c0280cc4930ec259fed2882

(mbus) not enough bytes, partial frame 26 34
(serial) received binary "00"
(mbus) checkMBUSFrame
 "681C1C680801727916071424239507CB01273F0616000000000000"
(mbus) not enough bytes, partial frame 27 34
(serial) received binary "02"
(mbus) checkMBUSFrame
 "681C1C680801727916071424239507CB01273F061600000000000002"
(mbus) not enough bytes, partial frame 28 34
(serial) received binary "96"
(mbus) checkMBUSFrame
 "681C1C680801727916071424239507CB01273F06160000000000000296"
(mbus) not enough bytes, partial frame 29 34
(serial) received binary "28"
(mbus) checkMBUSFrame
 "681C1C680801727916071424239507CB01273F0616000000000000029628"
(mbus) not enough bytes, partial frame 30 34
(serial) received binary "01"
(mbus) checkMBUSFrame
 "681C1C680801727916071424239507CB01273F061600000000000002962801"
(mbus) not enough bytes, partial frame 31 34
(serial) received binary "01"
(mbus) checkMBUSFrame
 "681C1C680801727916071424239507CB01273F06160000000000000296280101"
(mbus) not enough bytes, partial frame 32 34
(serial) received binary "18"
(mbus) checkMBUSFrame
 "681C1C680801727916071424239507CB01273F0616000000000000029628010118"
(mbus) not enough bytes, partial frame 33 34
(serial) received binary "16"
(mbus) checkMBUSFrame
 "681C1C680801727916071424239507CB01273F061600000000000002962801011816"
(mbus) received full frame.
(mbus) parse MBUS DLL @0 34
(mbus)  "681C1C680801727916071424239507CB01273F061600000000000002962801011816"
(wmbus) non-standard security mode 16_31
(diehl) frame N/A
(dvparser) found new format "0616029628" with hash 533a, remembering!
(meter) MyWater: for me? 01,14071679 in 14071679
(meter) MyWater: meter detection did not match the selected driver dme_07! correct driver is: unknown!
(meter) Not printing this warning again for id: 00000000 mfct: (@@@) Unknown (0x00) type: Other (0x00) ver: 0x00
(meter) please consider opening an issue at https://github.com/wmbusmeters/wmbusmeters/
(meter) to add support for this unknown mfct,media,version combination
(meter) MyWater: yes for me
(meter) MyWater(1) dme_07  handling telegram from 14071679
(meter) MyWater 14071679 "681C1C680801727916071424239507CB01273F061600000000000002962801011816"
(mbus) parse MBUS DLL @0 34
(mbus)  "681C1C680801727916071424239507CB01273F061600000000000002962801011816"
(wmbus) non-standard security mode 16_31
(diehl) frame N/A
telegram=|681C1C680801727916071424239507CB01273F|06160000000000000296280101|1816|+4
(meters) trying field info status(Text)[0]...
(meters) trying field info total(Volume)[1]...
(meters) using field info total(Volume)[1] to extract 0616 at offset 21
(meter) Volume total_m3 decoded m3 default m3 value 0 (scale 1)
(dme_07) 000   : 68 start
(dme_07) 001   : 1c length (28 bytes)
(dme_07) 002   : 1c length again (28 bytes)
(dme_07) 003   : 68 start
(dme_07) 033   : 16 end
(dme_07) 032   : 18 crc
(dme_07) 004   : 08 dll-c (RSP_UD2)
(dme_07) 005   : 01 dll-a primary (1)
(dme_07) 006   : 72 tpl-ci (long header)
(dme_07) 007   : 79160714 tpl-id (14071679)
(dme_07) 011   : 2423 tpl-mfct (HYD)
(dme_07) 013   : 95 tpl-version
(dme_07) 014   : 07 tpl-type (Water meter)
(dme_07) 015   : cb tpl-acc-field
(dme_07) 016   : 01 tpl-sts-field (BUSY)
(dme_07) 017   : 273f tpl-cfg 3f27 (synchronous SPECIFIC_16_31 )
(dme_07) 019   : 06 dif (48 Bit Integer/Binary Instantaneous value)
(dme_07) 020   : 16 vif (Volume m³)
(dme_07) 021 C!: 000000000000 ("total_m3":0)
(dme_07) 027   : 02 dif (16 Bit Integer/Binary Instantaneous value)
(dme_07) 028   : 96 vif (Volume m³)
(dme_07) 029   : 28 combinable vif (IncrPerInputPulseChannel0)
(dme_07) 030 C?: 0101
(shell) exec "/bin/sh"
(shell) arg "-c"
(shell) arg "/wmbusmeters/mosquitto_pub.sh "wmbusmeters/$METER_NAME" "$METER_JSON""
(shell) env "METER_ID=14071679"
(shell) env "METER_NAME=MyWater"
(shell) env "METER_TYPE=dme_07"
(shell) env "METER_JSON={"media":"water","meter":"dme_07","name":"MyWater","id":"14071679","total_m3":0,"timestamp":"2024-02-01T14:24:38Z","device":"MAIN","rssi_dbm":0}"
(shell) env "METER_MEDIA=water"
(shell) env "METER_TIMESTAMP=2024-02-01T14:24:38Z"
(shell) env "METER_TIMESTAMP_UTC=2024-02-01T14:24:38Z"
(shell) env "METER_TIMESTAMP_UT=1706797478"
(shell) env "METER_TIMESTAMP_LT=2024-02-01 15:24:38"
(shell) env "METER_STATUS=null"
(shell) env "METER_TOTAL_M3=0"
(shell) env "METER_DEVICE=MAIN"
(shell) env "METER_RSSI_DBM=0"
(shell) waiting for child 250 to complete.
(shell) /bin/sh: return code 0
(mbus) checkMBUSFrame
 ""
(mbus) less than 6 bytes, partial frame

[Psicrow925]

It works now.

It was necessary to write the current meter reading to the Izar Port Pulse Mini.
In addition, the water meter had to be connected to the pulse meter with the green cable instead of the yellow cable.
In addition, the water supplier had to reprogram the water meter so that one pulse equals 0.001m³.

I also had to create a tamplate that divides the value output in HomeAssistant by 1000.

This means that Home Assistant now counts by the liter.

(mbus) received full frame.
(mbus) parse MBUS DLL @0 34
(mbus)  "681C1C6808017279160714242395078C01270106169DD20000000002962801010A16"
(meter) MyWater: for me? p1.M=@@@.V=00.T=00,14071679.M=HYD.V=95.T=07 in 14071679
(meter) MyWater: meter detection did not match the selected driver dme_07! correct driver is: unknown!
(meter) Not printing this warning again for id: 00000000 mfct: (@@@) Unknown (0x00) type: Other (0x00) ver: 0x00
(meter) please consider opening an issue at https://github.com/wmbusmeters/wmbusmeters/
(meter) to add support for this unknown mfct,media,version combination
(meter) MyWater: yes for me
(meter) MyWater(1) dme_07  handling telegram from 14071679.M=HYD.V=95.T=07
(meter) MyWater 14071679.M=HYD.V=95.T=07 "681C1C6808017279160714242395078C01270106169DD20000000002962801010A16"
(mbus) parse MBUS DLL @0 34
(mbus)  "681C1C6808017279160714242395078C01270106169DD20000000002962801010A16"
telegram=|681C1C6808017279160714242395078C012701|06169DD2000000000296280101|0A16|+2941
(meters) trying field info status(Text)[0]...
(meters) trying field info total(Volume)[1]...
(meters) using field info total(Volume)[1] to extract 0616 at offset 21
(meter) Volume total_m3 decoded m3 default m3 value 53917 (scale 1)
(dme_07) 000   : 68 start
(dme_07) 001   : 1c length (28 bytes)
(dme_07) 002   : 1c length again (28 bytes)
(dme_07) 003   : 68 start
(dme_07) 033   : 16 end
(dme_07) 032   : 0A crc
(dme_07) 004   : 08 dll-c (RSP_UD2)
(dme_07) 005   : 01 dll-a primary (1)
(dme_07) 006   : 72 tpl-ci (long header)
(dme_07) 007   : 79160714 tpl-id (14071679)
(dme_07) 011   : 2423 tpl-mfct (HYD)
(dme_07) 013   : 95 tpl-version
(dme_07) 014   : 07 tpl-type (Water meter)
(dme_07) 015   : 8c tpl-acc-field
(dme_07) 016   : 01 tpl-sts-field (BUSY)
(dme_07) 017   : 2701 tpl-cfg 0127 (MFCT_SPECIFIC )
(dme_07) 019   : 06 dif (48 Bit Integer/Binary Instantaneous value)
(dme_07) 020   : 16 vif (Volume m³)
(dme_07) 021 C!: 9DD200000000 ("total_m3":53917)
(dme_07) 027   : 02 dif (16 Bit Integer/Binary Instantaneous value)
(dme_07) 028   : 96 vif (Volume m³)
(dme_07) 029   : 28 combinable vif (IncrPerInputPulseChannel0)
(dme_07) 030 C?: 0101
(shell) exec "/bin/sh"
(shell) arg "-c"
(shell) arg "/wmbusmeters/mosquitto_pub.sh "wmbusmeters/$METER_NAME" "$METER_JSON""
(shell) env "METER_ID=14071679"
(shell) env "METER_NAME=MyWater"
(shell) env "METER_TYPE=dme_07"
(shell) env "METER_JSON={"media":"water","meter":"dme_07","name":"MyWater","id":"14071679","total_m3":53917,"timestamp":"2024-03-08T16:46:09Z","device":"MAIN","rssi_dbm":0}"
(shell) env "METER_MEDIA=water"
(shell) env "METER_TIMESTAMP=2024-03-08T16:46:09Z"
(shell) env "METER_TIMESTAMP_UTC=2024-03-08T16:46:09Z"
(shell) env "METER_TIMESTAMP_UT=1709916369"
(shell) env "METER_TIMESTAMP_LT=2024-03-08 17:46:09"
(shell) env "METER_STATUS=null"
(shell) env "METER_TOTAL_M3=53917"
(shell) env "METER_DEVICE=MAIN"
(shell) env "METER_RSSI_DBM=0"
(shell) waiting for child 543 to complete.
(shell) /bin/sh: return code 0
(mbus) checkMBUSFrame
 ""
(mbus) less than 6 bytes, partial frame

None of the drivers support the Izar Port Pulse Mini correctly, but at least I can track the water consumption.

[weetmuts]

Nice! You can also calculate in wmbusmeters. But the best is of course to make the mbus izar port thingie to write the right value in the message.

You can see in the debug output C! before the total_m3 that wmbusmeters understood the value perfectly
even though its not quite the right driver. This is the beauty of the mbus protocol. It is mostly self desrcibing.
Wmbusmeters adds naming, unit-tracking, and knowledge about storage 0,1,2,3 etc. 0 is usually the current reading.
1 is often at the previous month ending (billing) period etc. Also bits in flags are not selfdescribing either.

(dme_07) 019 : 06 dif (48 Bit Integer/Binary Instantaneous value)
(dme_07) 020 : 16 vif (Volume m³)
(dme_07) 021 C!: 9DD200000000 ("total_m3":53917)

There is on-going work to be able to write the new drivers in a text file that is loaded on startup. For your port pulse mini
it looks like this, save it into a file: myport.xmq

driver {
    name           = myport
    meter_type     = WaterMeter
    default_fields = name,id,total_m3,timestamp
    detect {
        mvt = HYD,95,07
    }
    field {
        name        = total
        quantity    = Volume
        match {
            measurement_type = Instantaneous
            vif_range        = Volume
        }
    }
}

And you can run itfrom the command line like this:
wmbusmeters --format=json 681C1C6808017279160714242395078C012701_06169DD2000000000296280101_0A16 Vatten myport.xmq 14071679 NOKEY

And it will output:
{"media":"water","meter":"myport","name":"Vatten","id":"14071679","total_m3":53917,"timestamp":"2024-03-08T19:15:01Z"}

Of course the ha-addon has no support yet for uploading the xmq files and not all features of are implemented yet.
But its getting there.

Your current setup is perfectly fine, it will print a single warning but thats it. The values are decoded perfectly anyway.