Analyze wmbus or mbus telegrams using wmbusmeters.

Source code https://github.com/weetmuts/wmbusmeters/

The wmbusmeters software acquires utility meter readings through wmbus or plain mbus.
The readings can then be published using MQTT, curled to a REST api,
inserted into a database or stored in a log file. Wiki

This service is identical to running locally: wmbusmeters --analyze=<driver>:<key> <hex>

Telegram:
Driver:
Decryption key: (Logged telegrams by wmbusmeters are usually already decrypted.)
  (No cookies are used. Logs are cleared automatically after 1 month.)

If you are using a browser with web-serial support (Chrome/Edge etc) and you have a wmbus tailored dongle (eg. iu891a,metis,cul,rc1180 and NOT the rtlsdr) then you can run wmbusmeters in your browser: https://wmbusmeters.org/inbrowser/

All drivers for wmbusmeters are now described in xmq files: https://wmbusmeters.org/drivers/
Please help out and write more drivers!

Example telegrams:

Water meter 1 (not encrypted)
Water meter 2 (not encrypted)
Water meter 3 (output from --logtelegrams, which is pre-decrypted if you used a key locally)
Water meter 4 (encrypted but no key!)
Water meter 4 (using key)