wmbusmeters / wmbusmeters

Read the wired or wireless mbus protocol to acquire utility meter readings.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Add new device- (ALK) Actislink, Poland (0x58b), type: Water meter (0x07) ver: 0x04

rudy2k opened this issue · comments

Type of request

New device support

Meter description

(ALK) Actislink, Poland (0x58b), type: Water meter (0x07) ver: 0x04

Logged telegrams from meter in decrypted format

pi@smartHome:~/wmbusmeters $ wmbusmeters --logtelegrams rtlwmbus[00000001]:t1 alk auto 02581059 NOKEY
Started config rtlwmbus[00000001] listening on t1
(meter) alk: meter detection could not find driver for id: 02581059 mfct: (ALK) Actislink, Poland (0x58b) type: Water meter (0x07) ver: 0x04
(meter) please consider opening an issue at https://github.com/wmbusmeters/wmbusmeters/
(meter) to add support for this unknown mfct,media,version combination
telegram=|2E468B055910580204077A2A005102_0E170250205892633589DF1323CAF936D07EE7B34A2B1B518F68678184359FDE|+37
alk     02581059        2024-04-19 14:41:32
telegram=|2E468B055910580204077A2B005102_F30BF8ADF4E82A33EA41EBA1B078D5E71582DDD344B1086033025CABA1480A2C|+93
alk     02581059        2024-04-19 14:42:28
telegram=|2E468B055910580204077A2C005102_8FCA9DAB63327041F3E5ECF3E4CAE1321107282DD5B3BFE62AB9DDD513D673B0|+148
alk     02581059        2024-04-19 14:43:23
telegram=|2E468B055910580204077A2D005102_AD4EBCFCA3A3218510284B53A8E6EA0E06A1899E065768CE6159DC37E23E863E|+204
alk     02581059        2024-04-19 14:44:19
telegram=|2E468B055910580204077A2E005102_7C21BEC0486C562A0B2CEC73282CB64E0CB424402F32D7BE0CC9E1530FA8A82D|+259
alk     02581059        2024-04-19 14:45:14
telegram=|2E468B055910580204077A2F005102_9E999E4A63ABE8ABCD4762E5FA3C56F13D476FAF7992FC02BC695B620DEC10EC|+315
alk     02581059        2024-04-19 14:46:10

It appears that the data inside the telegram is AES-128 encrypted. According to the OMS standard, the telegram fits into an SND-NR (wM-Bus) frame. The first 15 unencrypted bytes were successfully matched. I'm trying to decipher the rest, but so far no luck. I contacted Actislink and WaterGroup, which deal with these modules, but I have not received a response.

telegram=|2E468B057210030204077A79005102_A170B157175CAB6CBED5102F32BE2BAAA35F7538F36D7A38D6B7C35F8F57EA3B|+2428

alk     02031072        2024-04-22 08:31:06

Water meter showed: 128,597m3 but idk it is same as in telegram.

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46
L-Field C-Field M-Field M-Field A-Field A-Field A-Field A-Field A-Field A-Field CI-Field Acces No. Status Config Config AES-Verify AES-Verify                                                            
Bytes (46) C-field Manu(2/2) Manu(2/1) ID4/4 ID3/4 ID2/4 ID1/4 Ver. Type ShortHeader Acces No. ErrCode NNNNCCRHb BASMMMMMb ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED ENCODED
2E 46 8B 05 72 10 03 02 04 07 7A 79 00 51 02 A1 70 B1 57 17 5C AB 6C BE D5 10 2F 32 BE 2B AA A3 5F 75 38 F3 6D 7A 38 D6 B7 C3 5F 8F 57 EA 3B

This issue is stale because it has been open for 2 month with no activity. Remove stale label or comment or this will be closed in 1 month.