Fredrik Öhrström

Indeed! It seems like your meters sends two telegrams, an older format and a new format. I have seen this in some heat cost allocators. Probably to support older data...

Ok, I took a quick look at the telegrams from apt_07_05 and they seem to be encrypted. Most of the databytes change between every telegram. Though perhaps there is some...

Yes, please provide a long and a short telegram from your device. The look like telegram=.... in the debug log.

Thanks, but I need the telegram=|....| when you have used the key. The previous telegram=|| that you posted are still encrypted.

Great work! Yes, the driver format is the new format!

I took your driver here and did some fixes. It now decode everything except 04FF07 and 04FF08. I need to know which unit they use? And if you have an...

Pushed your driver to github. Please test!

I looked at your first driver and there it looks like the forward/return energy is simply kwh. So I added a forced lookup for these from their difvif keys to...

Nice! I added m3c as a new unit, but I did not create a new quantity, so it belongs to Energy. However there are no automatic conversions between this energy...

wmbusmeters maintains the meter state in between telegrams, this is necessary since several meters send multiple different telegrams each containing parts of the total state. In this case you have...