iu891a-XL and hcae2 Engelmann

[adrianpeiro]

Hi.

First of all, I want to say that iu891a-XL did not work for hcae2 by default.
I tried many third-party programs and none of them could read any telegram.
I contacted the manufacturer and they gave me a new firmware an key to install it through WMBus Gateway Studio.
If that is your problem, contact them. It is a known problem.

The problem I have now is that I don't have the decription Key
I tried the most common ones but they don't work.

If, for example, I send the comand:
wmbusmeters --verbose auto:c1,t1 MyTapWater auto 23513716 00112233445566778899AABBCCDDEEFF

I get:
(meter) created MyTapWater hcae2 23513716 encrypted (meter) used meter template MyTapWater 23513716 auto to match 23513716.M=EFE.V=31.T=08 (meter) started meter 1 (MyTapWater 23513716 auto) identity mode: id R23513716 (meter) MyTapWater(1) hcae2 handling telegram from 23513716.M=EFE.V=31.T=08 (telegram) DLL L=ce C=44 (from meter SND_NR) M=14c5 (EFE) A=23513716 VER=31 TYPE=08 (Heat Cost Allocator) (driver hcae2) DEV=iu891a[00202017] RSSI=-70 (wmbus) WARNING!! decrypted content failed check, did you use the correct decryption key? Permanently ignoring telegrams from id: 23513716 mfct: (EFE) Engelmann Sensor, Germany (0x14c5) type: Heat Cost Allocator (0x08) ver: 0x31 (telegram) TPL CI=7a ACC=95 STS=00 CFG=25c0 (synchronous AES_CBC_IV nb=12 cntn=0 ra=0 hc=0) (meter) newly created meter (MyTapWater 23513716 hcae2) did not handle telegram!
I will try to ask the key to the company who installed it but, do you think it would be possible to run a program to test 32 hex bits to find one that works?
Apart that it could take a lot of time, I'm worried about the message I get:

Permanently ignoring telegrams from id: 23513716

Is that a wmbusmeters to avoid force brute?
Every time I run the command I get the same trace so I'm not sure if it is really ignoring it or if I could really find the Key programing it.

Thanks