# Licznik Wody Diehl Aries IS IZAR **URL:** \ **Category:** Home Assistant\ **Tags:** wodomierz, wmbus, diehl, aries-is\ **Created:** [16 Luty 2023 12:37 UTC](https://forum.arturhome.pl/t/licznik-wody-diehl-aries-is-izar/8287 "2023-02-16T12:37:23Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Autor:** ![alecsandes](https://forum.arturhome.pl/user_avatar/forum.arturhome.pl/alecsandes/32/19690_2.png) [@alecsandes](https://forum.arturhome.pl/u/alecsandes)\ **Data wpisu:** [19 Październik 2023 22:10 UTC](https://forum.arturhome.pl/t/licznik-wody-diehl-aries-is-izar/8287/10 "2023-10-19T22:10:25Z")
Hello People, I am desperate to find out where is the issue: I have the water meter: > **[ARIES IS | Diehl Metering](https://www.diehl.com/metering/en/products-solutions/products-services/water-metering/aries-is-at/)** > > ARIES IS is designed to measure the consumption of domestic cold or hot water. > Its integrated radio module enables remote reading of the index and alarms of the meter in mobile mode (walk-by) or fixed network. I have tried 2 ways of reading the telegrams: > running $ rtl\_sdr -f 868.625M -s 1600000 - 2\>/dev/null | rtl\_wmbus -s I get a lot of telegrams like: T1;1;1;2023-10-19 21:58:02.000;102;147;215091CD;0x1944304ccd9150211404a22313001349151047a9a90de3748cbd T1;1;1;2023-10-19 21:58:02.000;144;126;215091CD;0x1944304ccd9150211404a22313001349151047a9a90de3748cbd If I take one telegram [https://wmbusmeters.org/analyze/1944304ccd9150211404a22313001349151047a9a90de3748cbd](https://wmbusmeters.org/analyze/1944304ccd9150211404a22313001349151047a9a90de3748cbd) There is no data decoded in it. Here is the detailed issue > > > Hi @ZeWaren > > I have tagged you in the wmbusmeters github as well and trying h…ere, maybe you will see this and guide me. > > I used this tutorial and setup: https://github.com/zibous/ha-watermeter/blob/master/docs/wmbusmeters-with-rtl-sdr.md (raspberry 4 instead of pi zero) > > I have this meter: > ARIES IS Water meter > https://www.diehl.com/metering/en/products-solutions/products-services/water-metering/aries-is-at/ > IZAR integrated 868 MHz and 434 MHz radio, PRIOS protocol > > When running: > \`rtl\_sdr -f 868.625M -s 1600000 - 2\>/dev/null | rtl\_wmbus -s > \` > I get a lot of: > \`T1;0;0;2023-09-13 22:21:22.000;68;54;FFFFFFFF;0x1944ff26ffffffff9404ffa0608860ffffffff7cffffff7bffff > T1;0;0;2023-09-13 22:21:22.000;38;64;2150912A;0x1944304c2a915021ff04a2731300132ce3a7ff7ca35c79262eff > T1;0;0;2023-09-13 22:21:22.000;100;106;FFFF94FF;0x19ffffffff94ffff1404a22313ff13bbfffffffffffffff035ff > T1;1;1;2023-09-13 22:21:23.000;98;113;214FF95F;0x1944304c5ff94f211404a2231300137a2b5171294f5213d75289 > T1;0;0;2023-09-13 22:21:24.000;25;40;FFFFFFFF;0x19ffff4cffffffff14ffff331300ffff547eb5ffffa571a4ffb3 > T1;0;0;2023-09-13 22:21:26.000;97;141;2150A874;0x19ff304c74a850211404a253140013f3f85ec84eff1a8a291994 > T1;1;1;2023-09-13 22:21:27.000;107;140;215091CD;0x1944304ccd9150211404a253130013494eddbbf85437ee75c3b3 T1;0;0;2023-09-13 22:21:27.000;145;118;215091CD;0x1944304ccd9150211404a253130013494eddbbf85437ee77ffff > \` > When Running: > \`wmbusmeters --format=json auto:t1 MyWater izar '\*' NOKEY\` > I get a lot of: > \`Started auto rtlwmbus\[00000001\] listening on t1 (izar) Decoding PRIOS data failed. Ignoring telegram. {"media":"water","meter":"izar","name":"MyWater","id":"214ff7d6","prefix":"","serial\_number":"000000","total\_m3":0,"last\_month\_total\_m3":0,"last\_month\_measure\_date":"0-00-00","remaining\_battery\_life\_y":0,"current\_alarms":"no\_alarm","previous\_alarms":"no\_alarm","transmit\_period\_s":0,"manufacture\_year":"0","timestamp":"2023-09-13T22:23:49Z","device":"rtlwmbus\[00000001\]","rssi\_dbm":97} > \` > When running: > > \`sudo wmbusmeters --debug --t1 rtlwmbus\` > > I get a lot of: > (\`main) regular reset of rtlwmbus will happen every 82800 seconds (wmbus) no alarm (expected activity) for rtlwmbus (serial) registered regular callback HOT\_PLUG\_DETECTOR(0) every 2 seconds No meters configured. Printing id:s of all telegrams heard! (serial) waiting for stop (serial) received ascii "T1;1;1;2023-09-13 22:24:58.000;105;123;215091CD;0x1944304ccd9150211404a233130013493c3e0e0290df3aaf95bc\<0A\>T1;1;1;2023-09-13 22:24:58.000;141;115;215091CD;0x1944304ccd9 !\[204155722-9746eb5f-ce6b-455d-bda6-2f8f57cf0a21\]x 150211404a233130013493c3e0e0290df3aaf95bc\<0A\>" (rtlwmbus) checkRTLWMBusFrame "T1;1;1;2023-09-13 22:24:58.000;105;123;215091CD;0x1944304ccd9150211404a233130013493c3e0e0290df3aaf95bc\<0A\>T1;1;1;2023-09-13 22:24:58.000;141;115;215091CD;0x1944304ccd9150211404a233130013493c3e0e0290df3aaf95bc\<0A\>" (rtlwmbus) received full frame (meter) no meter handled checking 0 templates. (diehl) preprocess necessary SAP\_PRIOS (diehl) Pre-processing: setting device type to water meter for SAP PRIOS (wmbus) parseDLL @0 26 (wmbus) parseELL @10 16 (wmbus) parseNWL @10 16 (wmbus) parseAFL @10 16 (wmbus) parseTPL @10 16 (diehl) preprocess necessary SAP\_PRIOS (diehl) Pre-processing: setting device type to water meter for SAP PRIOS (wmbus) parseDLL @0 26 (telegram) DLL L=19 C=44 (from meter SND\_NR) M=4c30 (SAP) A=215091cd VER=00 TYPE=07 (Water meter) (driver izar) DEV=rtlwmbus\[00000001\] RSSI=105 (wmbus) parseELL @10 16 (wmbus) parseNWL @10 16 (wmbus) parseAFL @10 16 (wmbus) parseTPL @10 16 (telegram) TPL CI=a2 Received telegram from: 215091cd manufacturer: (SAP) Sappel (0x4c30) type: Water meter (0x07) ver: 0x00 device: rtlwmbus\[00000001\] rssi: 105 dBm driver: izar (wmbus) 000 : 19 length (25 bytes) (wmbus) 001 : 44 dll-c (from meter SND\_NR) (wmbus) 002 : 304c dll-mfct (SAP) (wmbus) 004 : cd915021 dll-id (215091cd) (wmbus) 008 : 00 dll-version (wmbus) 009 : 07 dll-type (Water meter) (wmbus) 010 : a2 tpl-ci-field (Mfct specific) (wmbus) 011 C?: 33130013493C3E0E0290DF3AAF95BC mfct specific (wmbus) telegram from 215091cd ignored by all configured meters! (rtlwmbus) checkRTLWMBusFrame "T1;1;1;2023-09-13 22:24:58.000;141;115;215091CD;0x1944304ccd9150211404a233130013493c3e0e0290df3aaf95bc\<0A\>" (rtlwmbus) received full frame (wmbus) skipping already handled telegram leng=26. \` > > > I was comparing the data what I have with what you posted on your blog: > > \`Decoding a Sappel frame > Let’s look at a full frame received by the antenna of my circuit: > > > 01010101010101010101010101010101010101 0000111101b + 1944304CC697D720D401E2E6A213120013184587BD6EB979401E8B407096h > \` > > I have as a frame (filtered the ones with 19 44 like this > \`\`\` > rtl\_sdr -f 868.625M -s 1600000 - 2\>/dev/null | rtl\_wmbus -s > T1;1;1;2023-09-21 19:32:21.000;101;127;2150A9FA;0x1944304cfaa950211404a2231400134a2c75e61a25bb0d891f7d > > \`\`\` > > If I would compare what is obvious to my eyes: > > Your example: \`1944304CC697D720D401E2E6A213120013184587BD6EB979401E8B4\` > Mine: \`1944304cfaa950211404a2231400134a2c75e61a25bb0d891f7d\` > > I am several chars less > > Can you help me understand what is wrong? and CC1101 with ESP8266 presented here. However, the CC1101 board I sourced is this > **[CC1101 wireless transceiver module + SMA antenna](https://www.sigmanortec.ro/en/cc1101-wireless-transceiver-module-sma-antenna)** > > CC1101 wireless reception transmission module plus SMA antenna compatible with Arduino and other development boards. This module operates it has 433 written on it … but I get the same readings: [00:24:37][D][wmbus:179]: Meter ID [0x2150A86F] RSSI: -86 dBm LQI: 129 Mode: T1 not found in configuration T: 1944304C6FA850211404A2231300131650E0B2A913F17D47099E (26) [00:24:38][D][wmbus:179]: Meter ID [0x2150A9F8] RSSI: -86 dBm LQI: 128 Mode: T1 not found in configuration T: 1944304CF8A950211404A203330013017241955F03ABC73A7840 (26) [00:24:41][D][wmbus:179]: Meter ID [0x216049FD] RSSI: -96 dBm LQI: 132 Mode: T1 not found in configuration T: 1944304CFD4960211404A2731500130D3E27E125F1D92091DC0C (26) [00:24:41][D][wmbus:179]: Meter ID [0x214FD95F] RSSI: -94 dBm LQI: 129 Mode: T1 not found in configuration T: 1944304C5FD94F211404A25313001378544D9642A77F66128E67 (26) [00:24:42][D][wmbus:179]: Meter ID [0x215091DC] RSSI: -81 dBm LQI: 128 Mode: T1 not found in configuration T: 1944304CDC9150211404A2231300135EBE4BB1354343F689C8A6 (26) Here is the link to the wmbusmeters page: [https://wmbusmeters.org/analyze/1944304CDC9150211404A2231300135EBE4BB1354343F689C8A6](https://wmbusmeters.org/analyze/1944304CDC9150211404A2231300135EBE4BB1354343F689C8A6) I don’t know really how to take it further, there are several points which i have doubts: 1. Meter is R3 not R4 as most of the people here: Frequency MHz 868.95 (R3 mode) and 434.47 (R3 mode)\*\* 2. Measuring with a DVB-T with command rtl\_sdr -f 868.625M -s 1600000 - 2\>/dev/null | rtl\_wmbus -s i get a lot of readings Reading with rtl\_sdr -f 868.950M -s 1600000 - 2\>/dev/null | rtl\_wmbus -s I get none … Reading with rtl\_sdr -f 434.47M -s 1600000 - 2\>/dev/null | rtl\_wmbus -s I get none. 1. If the CC1101 board is 433 MHz why can I see the telegrams I receive with rtl\_sdr -f 868.625M -s 1600000 - 2\>/dev/null | rtl\_wmbus -s I am beyond my knowldgeand I haven’t seen somenone facing the same issue --- _[View the full topic](https://forum.arturhome.pl/t/licznik-wody-diehl-aries-is-izar/8287)._