...
The Lobaro wMbus Parser is used from device Parsers and available as web API at https://platform.lobaro.com/#/wmbus/parser
wMbus API
Response (Lobaro wMbus JSON)
The following is an example of the parsing result of an encrypted example telegram from the OMS specification:
...
| Expand | ||
|---|---|---|
|
Important fields
| Field | Description |
|---|---|
IsEncrypted | true if the parsed telegram is still encrypted |
| DecryptionFailed | true if the parser tied to decrypt the telegram without success. Can be used in conjunction with IsEncrypted to detect if the telegram was encrypted (see below). |
| PayloadKnown | If the payload of the telegram (related to the CI field) is known to the parser and can be parsed |
| BodyParseError | Error while parsing the payload body |
| FormatSignature | Unique signature of the DifVif structure of all DataRecords. If any DifVif changes, the FormatSignature does change as well. |
Encryption state
| IsEncrypted | DecryptionFailed | Meaning |
|---|---|---|
| true | true | No valid key |
| false | false | Telegram not encrypted |
| true | false | Telegram is encrypted but parser can not decrypt it (e.g. unknown algorithm) |
| false | true | Plain telegram where decryption failed - should not happen |
VifUnit & VifQuantity
There are a many valid combinations of VifUnit & VifQuantity. All possible values are listed below.
...