Fredrik Öhrström

> Thank you! I tried the key ... Still the same error, the telegram is received but no decoding. The old brand Izar was created by the company Sappel which...

Does this make sense? https://wmbusmeters.org/analyze/49449344259764131806fa2f780dff5f3500828a0000110007c113ff5d24ff69540400ff2c452304001e36325104720200780000005d00140026005100000000aa8f0000005a0093002a002f046d02090f37537270

Yes manufacturer specific binary blobs inside a wmbus telegram are colored red. Any driver specific decoding that extracts from this blob are then printe below ***.

Wmbusmeters focuses on mbus compliant meter values. For all these it is now possible to write text drivers that can be loaded at runtime. https://github.com/wmbusmeters/wmbusmeters/blob/master/drivers/src/eltako.xmq But if someone cares to...

But the mftct specific blob will still be red even after some parts of it has been decoded. You see the *** as proof that something was extracted.

You have to post a telegram here for us to debug the problem. Use --logtelegrams on command line or logtelegrams=true in config file.

Yes, you can do it like this: rtl_433 -F csv -f 868.95M | tee >(wmbusmeters stdin:rtl433) Now the rtl_433 output is sent to wmbusmeters and continue on the pipe to...

rtl_433 -F csv -f 868.95M | tee >(wmbusmeters stdin:rtl433) | grep othertelegrams

You can also publish mqtt messages using rtl433 and then use mosquitto_sub from wmbusmeters to read these. Check the README. Telegrams can also be pulled in by listening on MQTT...

```shell wmbusmeters 'hex:CMD(/usr/bin/mosquitto_sub -h 192.168.x.x -t rtl_433/device/devices/6/Wireless-MBus/+/data | tr -d "\n" )' ```