Fredrik Öhrström

Can you post a link to wmbusmeters.org where your telegram is decoded? Then we can take a look at the contents together.

energy spelling error fixed.

A link like this, but for your telegram: https://wmbusmeters.org/analyze/a444c5146025750200047ac20000202f2f046d2e26c62a040643160000041310f0050001fd1700426cbf2c4406570e00008401061f160000840206f6150000840306f5150000840406f3150000840506ea150000840606bf1500008407065214000084080692120000840906c5100000840a06570e0000840b06ca0b0000840c06da090000840d06ca080000840e06c8080000840f06c608000003fd0c05010002fd0b2111

ah that is only part of the telegram. use logtelegrams=true or --logtelegrams to get an easy to find telegram= line.

I pasted a header in front of your tpl data to make a fake telegram, but it is good enough to look at the contents. https://wmbusmeters.org/analyze/a944C5144404752100047AC10000202F2F046D102A14360406FB0600000413D54D010001FD1700426CFF2C4406D6020000C40106FB060000C40206FB060000C40306A8060000C40406CE050000C40506E4040000C40606D6020000C4070619010000C4080604000000C4090600000000C40A0600000000C40B0600000000C40C0600000000C40D0600000000C40E0600000000C40F06000000002F2F2F2F2F03FD0C05010002FD0B0111

I can see that you have a storage nr 31 which is not decoded, this is easily fixed by changing 2,30 to 2,31 in the driver file. Or 2,129 if...

Yep, that is working. As you can see all content is decoded except storage 31. Do you understand the meaning of these semi monthly measurements? Do we count months back...

I.e. if target_date is 2023-12-31 (using storage nr 1) then the value using storage nr 3 would be measured on the date 2023-10-31 ?

Do you have an answer to this question? I.e. if target_date is 2023-12-31 (using storage nr 1) then the value using storage nr 3 would be measured on the date...

Ok, I think we should rename the field to "target_3_kwh" for the kwh at storage nr 3. No subtracting 1 from the storage nr, this only confuses the user. target_1_kwh...