I am looking for any kind of firm evidence that any smart meter operational in the Netherlands supports a DSMR version below 3.0. I am begining to think there is none. The supporting evidence for my claim stems from multiple instances where smart meters exclusively output telegram identifiers starting with /XXX5, contrary to the expected presence of /XXX3 in DSMR verion 2 (e.g. 2.1, 2.2 and 2.31).

I am beginning to suspect that some smart meters in the very early stages (technical tests?) supported v2.1, v2.2 or v2.31, but any smart meter rolled out to actual customers supports v3.0 (or: was updates over the air to support v3.0).

Observations:

Telegram Start Patterns:

Some sample Telegrams (from https://domoticx.com/p1-poort-slimme-meter-hardware/)

/Ene5
/ISK5\
/KFM5
/KFM5KAIFA-METER
/KMP5
/XMX5LG
/XMX5LGF
/XMX5XMXABCE000012345

In no instance I am aware of, there been an encounter with a telegram initiating with /XXX3. Even the Iskra KA6P… [ME382-D1A52 (GSM/GPRS)] smart meter spits out /XXX5 telegrams.

Specific OBIS Codes Absence:

Notably absent codes:

7-0:23.n.0 for gas meter value
0-0:42.0.0 for equipment identifier

Specifications Comparison:

The P1 specifications highlight the evolution of the data readout format across different DSMR versions. Starting from v2.1 to v5.0, notable changes are evident in the format of the data message, particularly in the "Data Readout" section.

P1 Specification Highlights:

v2.1, v2.2, v2.31: Format: /XXX3 Identification CR LF CR LF Data ! CR LF
v3.0: Format: /XXX5 Identification CR LF CR LF Data ! CR LF
v4.0: Format: /XXX5 Identification CR LF CR LF Data ! CRC CR LF
v5.0: Format: /XXX5 Identification CR LF CR LF Data ! CRC CR LF

Request:

Given these observations, it would be beneficial to ascertain the accuracy of the findings and further validate if there are indeed smart meters operational in the Netherlands that support DSMR versions lower than 3.0.

If you think you have found such a smart meter, please respond to this issue with the following info from the smart meter:

brand
model
meter code (for older smart meters: the first 4 characters of the smart meter identifier, which can be found under the largest barcode on your smart meter)
a full P1 telegram, the first line starting starting with / and the last line ending with ! followed by the CRC.

Please also validate your P1 telegram and include:

whether it matches DSMR<3 regex
whether it matches DSMR>=3 regex

Warning: : Please DO share the line starting with 0-0:42.0.0 or 0-0:96.1.1 from you telegram, at included an encoded version of your smart meter code, which identified the smart meter type. However, please replace the 11th character and further with *. The string between the brackets is a hex-encocoded version of your entire smart meter number, not.

Suppose your full smart meter number is E0044123456789012. Then your P1 telegram will have a line reading 0-0:96.1.1(4530303434313233343536373839303132) before you share it, please replace it by 0-0:96.1.1(4530303434***)

Additional Context:

Understanding the support for DSMR < v3.0 could be essential for various purposes, including compatibility assessments and potential implications for systems supporting older DSMR versions, like our twomes-p1-reader-firmware. In particular, it might simply our code somewhat and make it more realistic.

Your contributions and insights into this matter would be highly appreciated.

energietransitie / dsmr-info

Wanted: evidence for any operational smart meter in NL supporting DSMR < v3.0 (P1 telegram should match regex: \/[A-Z]{3}3.* AND NOT \/[A-Z]{3}5.*) #1