HTTP Report Templates
The Content-Type header should indicate the encoding of the file, e.g:
-
Content-Type: text/plain; charset = utf-8
-
Content-Type: text/plain; charset = iso-8859-1
Note
The files received with the 'application/octet-stream' Content-Type are treated as text encoded in ISO-8859-1.
This report contains value data in M-Bus raw format used when installation of a new meter is completed. This information can be useful to add meters when installation process is completed. This report sends a meter data report HTTP POST to an HTTP server. On execution of this report, one HTTP POST with all meter values in the body will be sent to the HTTP server.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_ installreport_<time>_<report-id>.csv.
The body contains rows. Each row contains the origin of the value and the actual value for a specific time.
Table 251. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
|
Product serial number |
1 |
|
The device (meter) secondary address |
2 |
|
The date/time of this value. Format: YYYY-MM-DD hh:mm:ss |
3 |
|
The M-Bus telegram number from which this record is taken |
4 |
|
M-Bus raw data, starting with M-Bus CField. Stop character and checksum of the M-Bus telegram is excluded. |
Example of body contents |
---|
|
This report contains event information sent from the product. Example of events are firmware updated and rebooted unexpectedly. This report sends an event report using HTTP POST to an HTTP server.On execution of this report, one post with event information is sent to the HTTP Server.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_eventreport_<time>_<report-id>.csv.
The body contains a column header line and key value pairs of information.
Table 253. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed value indicating column information line. |
1 |
key |
Fixed value |
2 |
value |
Fixed value |
Table 254. Value line definition
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
|
Key name Can be one of the following: time serial-number event module-revision sw-version prepaid-infoavailable prepaid-credits prepaid-currency prepaid-expiredate |
1 |
<value> |
Value |
This report contains log information sent from the product. On execution of this report, one post with log information is sent to the HTTP Server. The HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_logreport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 at 2020-09-01 01:00:00:
0006123456_logreport_20200901010000_3006.csv.
The body contains a column header line and log information lines.
The log level can be changed using configuration key common.syslog.level.
Table 256. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed value indicating column information line. |
1 |
serial-number |
Fixed value |
2 |
created |
Fixed value |
3 |
level |
Fixed value |
4 |
message |
Fixed value |
Table 257. Value line definition
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
|
Serial number of the product |
1 |
|
The date/time for this log information line. Format: YYYY-MM-DD hh:mm:ss |
2 |
|
The level of this log line. Available levels are: -2 = Debug -1 = Unknown 0 = Info 1 = Warning 2 = Error 3 = Critical 4 = Fatal 5 = Unhandled exception 6 = Event 7 = Network event 8 = Display text (only CMi2120) |
3 |
|
Log information message in clear text. |
This report contains status information sent from the product. Example of status information is cell information, signal quality etc. On execution of this report, one post with status information is sent to the HTTP Server. The HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_statusreport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 at 2020-09-01 01:00:00:
0006123456_statusreport_20200901010000_3007.csv.
The body contains a column header line and key value pairs of information.
Table 259. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed value indicating column information line. |
1 |
key |
Fixed value |
2 |
value |
Fixed value |
Table 260. Value line definition
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
|
Key name Can be one of the following: time serial-number name part-number imei imsi hw-version sw-version boot-time internal-temperature internal-voltage rssi gprs-available operator cell apn ip simid prepaid-infoavailable prepaid-credits prepaid-currency prepaid-expiredate |
1 |
|
Value |
Example of body contents |
---|
|
This report contains value data in decoded format, i.e. the data is sent in clear text and no knowledge of how to decode M-Bus information is needed. This report sends a meter data report file to an HTTP server. On execution of this report, one body with values for all product connected meters will be sent to the HTTP Server. The HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 at 2020-09-01 01:00:00:
0006123456_valuereport_20200901010000_3101.csv.
The body contains one column header line for each device, followed by one or more value data lines. Each column header line describes the contents of the following value data lines.
To distinguish column header lines and value data lines, look for “serial-number“ at the beginning of each line.
Table 262. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
serial-number |
Fixed field |
1 |
device-identification |
Fixed field |
2 |
created |
Fixed field |
3 |
value-data-count |
Fixed field |
4 |
Manufacturer |
Fixed field |
5..n |
|
Value description information. This information describes the exact contents of this column. Depending on meter, one or more value description columns are added. The value description contains 6 fields delimited with comma. These fields provide the exact meaning of the contents of this column. The 6 fields are: Description Unit Function Tariff Sub unit Storage number Please see Report Template Reference Information for complete description of these fields. |
Example of first line in body with column headers |
---|
|
Example of value data lines |
---|
|
Example of body with all contents |
---|
|
This report contains value data in M-Bus raw format. This report sends a meter data report file to an HTTP server. On execution of this report, one file with all meter values will be sent to the HTTP Server. The HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 at 2020-09-01 01:00:00:
0006123456_valuereport_20200901010000_3102.csv.
The body contains rows. Each row contains the origin of the value and the actual value for a specific time.
Table 264. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
|
Product serial number |
1 |
|
The device (meter) secondary address |
2 |
|
The date/time of this value. Format: YYYY-MM-DD hh:mm:ss |
3 |
|
The M-Bus telegram number from which this record is taken |
4 |
|
M-Bus raw data, starting with M-Bus C-Field. Stop character and checksum of the M-Bus telegram is excluded. |
Example of body contents |
---|
|
This report contains value data in M-Bus raw format. This report sends a meter data report post to an HTTP server. On execution of this report, one file per device (per meter) will be sent to the HTTP Server. HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_<device-identification>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 and for device with secondary address 00112233 at 2020-09-01 01:00:00:
0006123456_00112233_valuereport_20200901010000_3103.csv.
The body contains rows. Each row contains the origin of the value and the actual value for a specific time.
Table 267. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
|
Product serial number |
1 |
|
The device (meter) secondary address |
2 |
|
The date/time of this value. Format: YYYY-MM-DD hh:mm:ss |
3 |
|
The M-Bus telegram number from which this record is taken |
4 |
|
M-Bus raw data, starting with M-Bus C-Field. Stop character and checksum of the M-Bus telegram is excluded. |
Example of body contents |
---|
|
This report contains value data in decoded format, i.e. the data is sent in clear text and no knowledge of how to decode M-Bus information is needed. This report sends a meter data report post to an HTTP server. On execution of this report, one post per device (per meter) will be sent to the HTTP Server. HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_<device-identification>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 and for device with secondary address 00112233 at 2020-09-01 01:00:00:
0006123456_00112233_valuereport_20200901010000_3104.csv.
The body contains one column header line and one or more value data lines. Each column header in the first line of a file describes the contents of the value data lines.
Table 269. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
serial-number |
Fixed field |
1 |
device-identification |
Fixed field |
2 |
created |
Fixed field |
3 |
value-data-count |
Fixed field |
4..n |
|
Value description information. This information describes the exact contents of this column. Depending on meter, one or more value description columns are added. The value description contains 6 fields delimited with comma. These fields provide the exact meaning of the contents of this column. The 6 fields are: Description Unit Function Tariff Sub unit Storage number Please see Report Template Reference Information for complete description of these fields. |
Example of first line in body with column headers |
---|
|
Example of value data lines |
---|
|
Example of body with all contents |
---|
|
This report contains value data in decoded format, i.e. the data is sent in clear text and no knowledge of how to decode M-Bus information is needed. This report sends a meter data report file to an HTTP server. On execution of this report, one post per device (per meter) will be sent to the HTTP Server. HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_<device-identification>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 and for device with secondary address 00112233 at 2020-09-01 01:00:00:
0006123456_00112233_valuereport_20200901010000_3105.csv.
The body contains one column header line and one or more value data lines. Each column header in the first line of a file describes the contents of the value data lines.
Table 271. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed field indicating column header information line. |
1 |
serial-number |
Fixed field |
2 |
device-identification |
Fixed field |
3 |
created |
Fixed field |
4 |
value-data-count |
Fixed field |
5..n |
|
Value description information. This information describes the exact contents of this column. Depending on meter, one or more value description columns are added. The value description contains 6 fields delimited with comma. These fields provide the exact meaning of the contents of this column. The 6 fields are: Description Unit Function Tariff Sub unit Storage number Please see Report Template Reference Information for complete description of these fields. |
Example of first line in body with column headers |
---|
|
Example of value data lines |
---|
|
Example of body with all contents |
---|
|
This report contains value data in M-Bus raw format. This report sends a meter data report post to an HTTP server. On execution of this report, one file per device (per meter) will be sent to the HTTP Server. HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 at 2020-09-01 01:00:00:
0006123456_valuereport_20200901010000_3106.csv.
The body contains one column header line, followed by one or more value data lines. Each column header line describes the contents of the following value data lines.
Table 273. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed field indicating column header information line. |
1 |
serial-number |
Fixed field. Data row contains the CMe/CMi product serial number. |
2 |
device-identification |
Fixed field. Data row contains the M-Bus device secondary address. |
3 |
created |
Fixed field. Data row contains the date/time of the data row. |
4 |
value-data-count |
Fixed field. Data row contains the M-Bus telegram number. 0 = first telegram, 1 = second telegram etc. |
5 |
mbus-raw-value |
M-Bus raw data, starting with M-Bus C-Field. Stop character and checksum of the M-Bus telegram is excluded. |
Example of first line in body with column headers |
---|
|
Example of value data lines |
---|
|
Example of body with all contents |
---|
|
This report contains value data in decoded format, i.e. the data is sent in clear text and no knowledge of how to decode M-Bus information is needed. This report sends a meter data report file to an HTTP server. On execution of this report, one file with values for all product connected meters will be sent to the HTTP Server. HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 at 2020-09-01 01:00:00:
0006123456_valuereport_20200901010000_3108.csv.
The body contains one column header line for each device, followed by one or more value data lines. Each column header line describes the contents of the following value data lines.
Table 275. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed field indicating column header information line. |
1 |
serial-number |
Fixed field |
2 |
device-identification |
Fixed field |
3 |
created |
Fixed field |
4 |
value-data-count |
Fixed field |
5..n |
|
Value description information. This information describes the exact contents of this column. Depending on meter, one or more value description columns are added. The value description contains 6 fields delimited with comma. These fields provide the exact meaning of the contents of this column. The 6 fields are: Description Unit Function Tariff Sub unit Storage number Please see Report Template Reference Information for complete description of these fields. |
Example of first line in body with column headers |
---|
|
Example of value data lines |
---|
|
Example of body with all contents |
---|
|
This report contains value data in decoded format, i.e. the data is sent in clear text and no knowledge of how to decode M-Bus information is needed. This report sends a meter data report file to an HTTP server. On execution of this report, one file per device with values will be sent to the HTTP Server. HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_<device-identification>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 and for device with secondary address 00112233 at 2020-09-01 01:00:00:
0006123456_00112233_valuereport_20200901010000_3109.csv.
The body contains one column header line, followed by one or more value data lines. Each column header line describes the contents of the following value data lines.
Table 277. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed field indicating column header information line. |
1 |
serial-number |
Fixed field. Data row contains the CMe/CMi product serial number. |
2 |
device-identification |
Fixed field. Data row contains the M-Bus device secondary address. |
3 |
created |
Fixed field. Data row contains the date/time of the data row. |
4 |
value-data-count |
Fixed field. Data row contains the M-Bus telegram number. 0 = first telegram, 1 = second telegram etc. |
5 |
manufacturer |
Fixed field. Data row contains the M-Bus device three letter manufacturer code. |
6 |
version |
Fixed field. Data row contains the M-Bus device version. |
7 |
device-type |
Fixed field. Data row contains the M-Bus device type as string. |
8 |
access-number |
Fixed field. Data row contains the M-Bus device access number which is increased by one on every request to the meter. This field can be used to verify that no other M-Bus master has read the device. |
9 |
status |
Fixed field. Data row contains the M-Bus device status field. |
10 |
signature |
Fixed field. Data row contains the the M-Bus device signature field. |
11..n |
|
Value description information. This information describes the exact contents of this column. Depending on meter, one or more value description columns are added. The value description contains 6 fields delimited with comma. These fields provide the exact meaning of the contents of this column. The 6 fields are: Description Unit Function Tariff Sub unit Storage number Please see Report Template Reference Information for complete description of these fields. |
Example of first line in body with column headers |
---|
|
Example of value data lines |
---|
|
Example of body with all contents |
---|
|
This report contains value data in decoded format, i.e. the data is sent in clear text and no knowledge of how to decode M-Bus information is needed. This report sends a meter data report file to an HTTP server. On execution of this report, one file with all values will be sent to the HTTP Server. The HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 at 2020-09-01 01:00:00:
0006123456_valuereport_20200901010000_3110.csv.
The body contains one column header line, followed by one or more value data lines. Each column header line describes the contents of the following value data lines.
Table 279. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed field indicating column header information line. |
1 |
serial-number |
Fixed field. Data row contains the CMe/CMi product serial number. |
2 |
device-identification |
Fixed field. Data row contains the M-Bus device secondary address. |
3 |
created |
Fixed field. Data row contains the date/time of the data row. |
4 |
value-data-count |
Fixed field. Data row contains the M-Bus telegram number. 0 = first telegram, 1 = second telegram etc. |
5 |
manufacturer |
Fixed field. Data row contains the M-Bus device three letter manufacturer code. |
6 |
version |
Fixed field. Data row contains the M-Bus device version. |
7 |
device-type |
Fixed field. Data row contains the M-Bus device type as string. |
8 |
access-number |
Fixed field. Data row contains the M-Bus device access number which is increased by one on every request to the meter. This field can be used to verify that no other M-Bus master has read the device. |
9 |
status |
Fixed field. Data row contains the M-Bus device status field. |
10 |
signature |
Fixed field. Data row contains the M-Bus device signature field. |
11..n |
|
Value description information. This information describes the exact contents of this column. Depending on meter, one or more value description columns are added. The value description contains 6 fields delimited with comma. These fields provide the exact meaning of the contents of this column. These 6 fields are: Unit Description Kind Tariff Sub unit Storage number Please see Report Template Reference Information for complete description of these fields. |
Example of first line in body with column headers |
---|
|
Example of value data lines |
---|
|
Example of body with all contents |
---|
|
This report contains value data in decoded format, i.e. the data is sent in clear text and no knowledge of how to decode M-Bus information is needed. This report sends a meter data report file to an HTTP server. On execution of this report, one file with all values will be sent to the HTTP Server. The HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 at 2020-09-01 01:00:00:
0006123456_valuereport_20200901010000_3111.csv.
The body contains one column header line, followed by one or more value data lines. Each column header line describes the contents of the following value data lines.
Table 281. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed field indicating column header information line. |
1 |
serial-number |
Fixed field. Data row contains the CMe/CMi product serial number. |
2 |
device-identification |
Fixed field. Data row contains the M-Bus device secondary address. |
3 |
created |
Fixed field. Data row contains the date/time of the data row. |
4 |
value-data-count |
Fixed field. Data row contains the M-Bus telegram number. 0 = first telegram, 1 = second telegram etc. |
5 |
manufacturer |
Fixed field. Data row contains the M-Bus device three letter manufacturer code. |
6 |
version |
Fixed field. Data row contains the M-Bus device version. |
7 |
device-type |
Fixed field. Data row contains the M-Bus device type as string. |
8 |
access-number |
Fixed field. Data row contains the M-Bus device access number which is increased by one on every request to the meter. This field can be used to verify that no other M-Bus master has read the device. |
9 |
status |
Fixed field. Data row contains the M-Bus device status field. |
10 |
signature |
Fixed field. Data row contains the the M-Bus device signature field. |
11..n |
|
Value description information. This information describes the exact contents of this column. Depending on meter, one or more value description columns are added. The value description contains 8 fields delimited with comma. These fields provide the exact meaning of the contents of this column. The 8 fields are: Dif Vif Unit Description Kind Tariff Sub unit Storage number Please see Report Template Reference Information for complete description of these fields. |
Example of first line in body with column headers |
---|
|
Example of value data lines |
---|
|
Example of body with all contents |
---|
|
This report contains value data in decoded format, i.e. the data is sent in clear text and no knowledge of how to decode M-Bus information is needed. This report sends a meter data report file to an HTTP server. On execution of this report, one file with all values will be sent to the HTTP Server. The HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 at 2020-09-01 01:00:00:
0006123456_valuereport_20200901010000_3112.csv.
The body contains one column header line, followed by one or more value data lines. Each column header line describes the contents of the following value data lines.
Table 283. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed field indicating column header information line. |
1 |
serial-number |
Fixed field. Data row contains the CMe/CMi product serial number. |
2 |
device-position |
Fixed field. Data row contains a field that describes location or other information for identifying the meter (MOID). |
3 |
device-identification |
Fixed field. Data row contains the M-Bus device secondary address. |
4 |
created |
Fixed field. Data row contains the date/time of the data row. |
5 |
value-data-count |
Fixed field. Data row contains the M-Bus telegram number. 0 = first telegram, 1 = second telegram etc. |
6 |
manufacturer |
Fixed field. Data row contains the M-Bus device three letter manufacturer code. |
7 |
version |
Fixed field. Data row contains the M-Bus device version. |
8 |
device-type |
Fixed field. Data row contains the M-Bus device type as string. |
9 |
access-number |
Fixed field. Data row contains the M-Bus device access number which is increased by one on every request to the meter. This field can be used to verify that no other M-Bus master has read the device. |
10 |
status |
Fixed field. Data row contains the M-Bus device status field. |
11 |
signature |
Fixed field. Data row contains the M-Bus device signature field. |
12..n |
|
Value description information. This information describes the exact contents of this column. Depending on meter, one or more value description columns are added. The value description contains 6 fields delimited with comma. These fields provide the exact meaning of the contents of this column. These 6 fields are: Unit Description Kind Tariff Sub unit Storage number Please see Report Template Reference Information for complete description of these fields. |
Example of first line in body with column headers |
---|
|
Example of value data lines |
---|
|
Example of body with all contents |
---|
|
This report contains value data in decoded format, i.e. the data is sent in clear text and no knowledge of how to decode M-Bus information is needed. This report sends a meter data report file to an HTTP server. On execution of this report, one file with all values will be sent to the HTTP Server. The HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 at 2020-09-01 01:00:00:
0006123456_valuereport_20200901010000_3113.csv.
The body contains one column header line, followed by one or more value data lines. Each column header line describes the contents of the following value data lines.
Table 285. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed field indicating column header information line. |
1 |
serial-number |
Fixed field. Data row contains the CMe/CMi product serial number. |
2 |
device-identification |
Fixed field. Data row contains the M-Bus device secondary address. |
3 |
created |
Fixed field. Data row contains the date/time of the data row. |
4 |
value-data-count |
Fixed field. Data row contains the M-Bus telegram number. 0 = first telegram, 1 = second telegram etc. |
5 |
manufacturer |
Fixed field. Data row contains the M-Bus device three letter manufacturer code. |
6 |
version |
Fixed field. Data row contains the M-Bus device version. |
7 |
device-type |
Fixed field. Data row contains the M-Bus device type as string. |
8 |
access-number |
Fixed field. Data row contains the M-Bus device access number which is increased by one on every request to the meter. This field can be used to verify that no other M-Bus master has read the device. |
9 |
status |
Fixed field. Data row contains the M-Bus device status field. |
10 |
signature |
Fixed field. Data row contains the M-Bus device signature field. |
11..n |
|
Value description information. This information describes the exact contents of this column. Depending on meter, one or more value description columns are added. The value description contains 6 fields delimited with comma. These fields provide the exact meaning of the contents of this column. These 6 fields are: Unit Description Kind Tariff Sub unit Storage number Please see Report Template Reference Information for complete description of these fields. |
Example of first line in body with column headers |
---|
|
Example of value data lines |
---|
|
Example of body with all contents |
---|
|
This report contains value data in decoded format, i.e. the data is sent in clear text and no knowledge of how to decode M-Bus information is needed. This report sends a meter data report file to an HTTP server. On execution of this report, one file with all values will be sent to the HTTP Server. The HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 at 2020-09-01 01:00:00:
0006123456_valuereport_20200901010000_3114.csv.
The body contains one column header line, followed by one or more value data lines. Each column header line describes the contents of the following value data lines.
Table 287. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed field indicating column header information line. |
1 |
serial-number |
Fixed field. Data row contains the CMe/CMi product serial number. |
2 |
device-position |
Fixed field. Data row contains a field that describes location or other information for identifying the meter (MOID). |
3 |
device-identification |
Fixed field. Data row contains the M-Bus device secondary address. |
4 |
created |
Fixed field. Data row contains the date/time of the data row. |
5 |
value-data-count |
Fixed field. Data row contains the M-Bus telegram number. 0 = first telegram, 1 = second telegram etc. |
6 |
manufacturer |
Fixed field. Data row contains the M-Bus device three letter manufacturer code. |
7 |
version |
Fixed field. Data row contains the M-Bus device version. |
8 |
device-type |
Fixed field. Data row contains the M-Bus device type as string. |
9 |
access-number |
Fixed field. Data row contains the M-Bus device access number which is increased by one on every request to the meter. This field can be used to verify that no other M-Bus master has read the device. |
10 |
status |
Fixed field. Data row contains the M-Bus device status field. |
11 |
signature |
Fixed field. Data row contains the M-Bus device signature field. |
12..n |
|
Value description information. This information describes the exact contents of this column. Depending on meter, one or more value description columns are added. The value description contains 6 fields delimited with comma. These fields provide the exact meaning of the contents of this column. These 6 fields are: Unit Description Kind Tariff Sub unit Storage number Please see Report Template Reference Information for complete description of these fields. |
Example of first line in body with column headers |
---|
|
Example of value data lines |
---|
|
Example of body with all contents |
---|
|
This report contains value data in decoded format, i.e. the data is sent in clear text and no knowledge of how to decode M-Bus information is needed. This report sends a meter data report file to an HTTP server. On execution of this report, one file with all values will be sent to the HTTP Server. The HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 at 2020-09-01 01:00:00:
0006123456_valuereport_20200901010000_3115.csv.
The body contains one column header line, followed by one or more value data lines. Each column header line describes the contents of the following value data lines.
Table 289. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed field indicating column header information line. |
1 |
serial-number |
Fixed field. Data row contains the CMe/CMi product serial number. |
2 |
device-position |
Fixed field. Data row contains a field that describes location or other information for identifying the meter (MOID). |
3 |
primary-address |
Fixed field. Data row contains the primary address of the M-Bus device. |
4 |
device-identification |
Fixed field. Data row contains the M-Bus device secondary address. |
5 |
created |
Fixed field. Data row contains the date/time of the data row. |
6 |
value-data-count |
Fixed field. Data row contains the M-Bus telegram number. 0 = first telegram, 1 = second telegram etc. |
7 |
manufacturer |
Fixed field. Data row contains the M-Bus device three letter manufacturer code. |
8 |
version |
Fixed field. Data row contains the M-Bus device version. |
9 |
device-type |
Fixed field. Data row contains the M-Bus device type as string. |
10 |
access-number |
Fixed field. Data row contains the M-Bus device access number which is increased by one on every request to the meter. This field can be used to verify that no other M-Bus master has read the device. |
11 |
status |
Fixed field. Data row contains the M-Bus device status field. |
12 |
signature |
Fixed field. Data row contains the M-Bus device signature field. |
13..n |
|
Value description information. This information describes the exact contents of this column. Depending on meter, one or more value description columns are added. The value description contains 6 fields delimited with comma. These fields provide the exact meaning of the contents of this column. These 6 fields are: Unit Description Kind Tariff Sub unit Storage number Please see Report Template Reference Information for complete description of these fields. |
Example of first line in body with column headers |
---|
|
Example of value data lines |
---|
|
Example of body with all contents |
---|
|
This report contains value data in decoded format, i.e. the data is sent in clear text and no knowledge of how to decode M-Bus information is needed. This report sends a meter data report file to an HTTP server. On execution of this report, one file per device with values will be sent to the HTTP Server. HTTP method used is HTTP POST.
Filename header is filled with a name which can be useful when storing the body contents in a file on a server share. The filename is in the following format:
<serial-number>_<device-identification>_valuereport_<time>_<report-id>.csv.
Example of a file sent from a product with serial number 0006123456 and for device with secondary address 00112233 at 2020-09-01 01:00:00:
0006123456_00112233_valuereport_20200901010000_3116.csv.
The body contains one column header line, followed by one or more value data lines. Each column header line describes the contents of the following value data lines.
Table 291. Column header description
Column index (0 = first column) |
Column contents |
Description |
---|---|---|
0 |
# |
Fixed field indicating column header information line. |
1 |
serial-number |
Fixed field. Data row contains the CMe/CMi product serial number. |
2 |
device-position |
Fixed field. Data row contains a field that describes location or other information for identifying the meter (MOID). |
3 |
primary-address |
Fixed field. Data row contains the primary address of the M-Bus device. |
4 |
device-identification |
Fixed field. Data row contains the M-Bus device secondary address. |
5 |
created |
Fixed field. Data row contains the date/time of the data row. |
6 |
value-data-count |
Fixed field. Data row contains the M-Bus telegram number. 0 = first telegram, 1 = second telegram etc. |
7 |
manufacturer |
Fixed field. Data row contains the M-Bus device three letter manufacturer code. |
8 |
version |
Fixed field. Data row contains the M-Bus device version. |
9 |
device-type |
Fixed field. Data row contains the M-Bus device type as string. |
10 |
access-number |
Fixed field. Data row contains the M-Bus device access number which is increased by one on every request to the meter. This field can be used to verify that no other M-Bus master has read the device. |
11 |
status |
Fixed field. Data row contains the M-Bus device status field. |
12 |
signature |
Fixed field. Data row contains the M-Bus device signature field. |
13..n |
|
Value description information. This information describes the exact contents of this column. Depending on meter, one or more value description columns are added. The value description contains 6 fields delimited with comma. These fields provide the exact meaning of the contents of this column. These 6 fields are: Unit Description Kind Tariff Sub unit Storage number Please see Report Template Reference Information for complete description of these fields. |
Example of first line in body with column headers |
---|
|
Example of value data lines |
---|
|
Example of body with all contents |
---|
|
Comments (0 comments)