M-Bus Parser (Wired & Wireless)

Examples

Choose Wired or Wireless to decode an example. Public test keys and TLS sessions are included when available.

Mode 5 · AES-CBCDecrypted readings · no authentication

Mode 7 · AES-CBCSynthetic header example · verification unavailable

Mode 10 · AES-CCMAuthenticated readings

Mode 13 · TLSAuthenticated readings · includes test session

UnencryptedNo key needed

TLS session · mode 13

Decode complete TLS 1.2 application records with exported session keys. Session data stays in this page and is cleared on reload. For AFL captures, first reassemble and remove the AFL framing. TLS handshakes are not supported.

Use TLS session

Import session JSON Session Cipher suite Direction Encryption key (hex) Fixed nonce salt (hex) First record counter (decimal)

Use the key and salt for the selected direction. The counter counts TLS records, including encrypted handshake records. Repeating a decode does not advance it. TLS session output supports JSON, YAML, Table, CSV, and Diagram.

Session JSON fields

{
  "name": "Meter session",
  "cipher_suite": "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256",
  "direction": "client_to_server",
  "key_hex": "",
  "fixed_iv_hex": "",
  "sequence_number": "0"
}

Help

Accepts wired and wireless frames. If neither matches, tries application-layer data (starting with CI) or bare DIF/VIF records.

Enter the key supplied with the meter. Leave empty to inspect the telegram headers.

Keys stay in this browser tab and are excluded from share links and reports.

Online M-Bus Parser