You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i have an issue where if i type : rtl_sdr -f 868.94M -s 1.6e6 - | rtl_wmbus
i'm able to get my counter (wich is 2141b9e3 IZAR) T1;0;0;2024-05-08 09:57:31.000;79;97;2141B9E3;0x19ff304ce3b941211004a3331100130b4bac4c126b1713e69ee2
but if i type : wmbusmeters --logtelegrams --format=json auto:t1 EAU izar 2141b9e3 NOKEY
i don't get any telegram from it
If i type : wmbusmeters --debug --t1 rtlwmbus:868.94M
i often get the following :
(serial) received ascii "T1;0;0;2024-05-08 10:28:42.000;92;104;2141B9E3;0x1944304ce3b941211004a3231100130b5c8305b94ac4ca3d87ff<0A>"
(rtlwmbus) checkRTLWMBusFrame "T1;0;0;2024-05-08 10:28:42.000;92;104;2141B9E3;0x1944304ce3b941211004a3231100130b5c8305b94ac4ca3d87ff<0A>"
(rtlwmbus) telegram received but incomplete or with errors, since rtl_wmbus reports that CRC checks failed.
(rtlwmbus) error in received message.
and sometimes :
(serial) received ascii "T1;1;1;2024-05-08 10:13:54.000;91;109;2141B9E3;0x1944304ce3b941211004a3031100130b72dd96ef0963798bb5e5<0A>"
(rtlwmbus) checkRTLWMBusFrame "T1;1;1;2024-05-08 10:13:54.000;91;109;2141B9E3;0x1944304ce3b941211004a3031100130b72dd96ef0963798bb5e5<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=2141b9e3 VER=00 TYPE=07 (Water meter) (driver izar) DEV=rtlwmbus[00000001] RSSI=91
(wmbus) parseELL @10 16
(wmbus) parseNWL @10 16
(wmbus) parseAFL @10 16
(wmbus) parseTPL @10 16
(telegram) TPL CI=a3
Received telegram from: 2141b9e3
manufacturer: (SAP) Sappel (0x4c30)
type: Water meter (0x07)
ver: 0x00
device: rtlwmbus[00000001]
rssi: 91 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 : e3b94121 dll-id (2141b9e3)
(wmbus) 008 : 00 dll-version
(wmbus) 009 : 07 dll-type (Water meter)
(wmbus) 010 : a3 tpl-ci-field (Mfct specific)
(wmbus) 011 C?: 031100130B72DD96EF0963798BB5E5 mfct specific
(wmbus) telegram from TODO ignored by all configured meters!
If i type wmbusmeters --debug --t1 rtlwmbus
i don't see my Meter,
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
i live in a flat, in a building, with a lot of counters (Heat, Hot water, and cold water) each one is WMBUS capable.
I am new to all this things and I followed this procedure https://www.youtube.com/watch?v=m5R6sfsGmvE&t=1150s&ab_channel=JournaldeThomas
i have an issue where if i type :
rtl_sdr -f 868.94M -s 1.6e6 - | rtl_wmbus
i'm able to get my counter (wich is 2141b9e3 IZAR)
T1;0;0;2024-05-08 09:57:31.000;79;97;2141B9E3;0x19ff304ce3b941211004a3331100130b4bac4c126b1713e69ee2
but if i type :
wmbusmeters --logtelegrams --format=json auto:t1 EAU izar 2141b9e3 NOKEY
i don't get any telegram from it
If i type :
wmbusmeters --debug --t1 rtlwmbus:868.94M
i often get the following :
and sometimes :
If i type
wmbusmeters --debug --t1 rtlwmbus
i don't see my Meter,
Any idea ?
Beta Was this translation helpful? Give feedback.
All reactions