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 am renting multiple water meters with Radio 4 module from TECHEM in Germany, and I received AES keys from them to decode the telegrams. Similar to some earlier reporting I also received two AES keys per meter.
The meter send two messages a few seconds apart, both encrypted with the different keys. However, how can I create the correct meter files to distinguish the telegrams from each other? I saw this post with the hint to distinguish by type/version, but they seem to be the same in my case:
left: first shorter message right: longer message received a few seconds later
So both messages differ in length and RSSI, but all other parameters seem to be the same: (telegram) DLL L=36 C=44 (from meter SND_NR) M=5068 (TCH) A=23306862 VER=95 TYPE=37 (Radio converter (meter side)) (driver mkradio4a) DEV=amb8465[00000000] RSSI=-91
and: (telegram) DLL L=56 C=44 (from meter SND_NR) M=5068 (TCH) A=23306862 VER=95 TYPE=37 (Radio converter (meter side)) (driver mkradio4a) DEV=amb8465[00000000] RSSI=-103
My wmbusmeters version: 1.13.1-3
P.S.: driver mkradio4 and mkradio4a are unable to completely decode the longer telegram. The best option seems to be evo868 but still a few bytes are not being decoded (sample message here).
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
Uh oh!
There was an error while loading. Please reload this page.
-
I am renting multiple water meters with Radio 4 module from TECHEM in Germany, and I received AES keys from them to decode the telegrams. Similar to some earlier reporting I also received two AES keys per meter.
The meter send two messages a few seconds apart, both encrypted with the different keys. However, how can I create the correct meter files to distinguish the telegrams from each other? I saw this post with the hint to distinguish by type/version, but they seem to be the same in my case:
left: first shorter message right: longer message received a few seconds later
So both messages differ in length and RSSI, but all other parameters seem to be the same:
(telegram) DLL L=36 C=44 (from meter SND_NR) M=5068 (TCH) A=23306862 VER=95 TYPE=37 (Radio converter (meter side)) (driver mkradio4a) DEV=amb8465[00000000] RSSI=-91
and:
(telegram) DLL L=56 C=44 (from meter SND_NR) M=5068 (TCH) A=23306862 VER=95 TYPE=37 (Radio converter (meter side)) (driver mkradio4a) DEV=amb8465[00000000] RSSI=-103
My wmbusmeters version: 1.13.1-3
P.S.: driver mkradio4 and mkradio4a are unable to completely decode the longer telegram. The best option seems to be evo868 but still a few bytes are not being decoded (sample message here).
Beta Was this translation helpful? Give feedback.
All reactions