-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Telegram Decryption for Engelmann Heat cost allocators HCA E2 failed #820
Comments
I have ordered Engelmann 2 years ago, no one of them I was able to get running with different software. But I got a device specific key for everyone of them. I ordered somewhere else Lorenz then. Got individual keys, everything worked out of the box after weetmuts (THANKS) added some additional changes for further values :-) |
How did you receive these telegrams? It is a bit odd that when wmbusmeters tries to decrypt the telegram Could the telegram have some dll-crc bytes not yet removed? |
Thanks for your comments! |
Ah, then you are not speaking the proper amb8465-m protocol and you get the crc bytes at the end as well. |
The problem is not anymore the receiving of the protocol, but the decoding. Your are right, the AES master key is different and not known. To perform the decoding by your self, you have to change the AES Key to your own (known) key.
… Am 20.03.2023 um 17:40 schrieb Skysurfer-14 ***@***.***>:
I'm planning to buy the same heat cost allocators "HCA E2" from Engelmann. Is there still a problem to receive the protokol? The HCA e2 device will be delivered with the standard Engelmann AES master key. I'm shure that this key will be different from the key above in the first post. Is the Englemann AES master key known here?
—
Reply to this email directly, view it on GitHub <#820 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASLV4AZL3U7L7AXDMWJ53WTW5CB7TANCNFSM6AAAAAAUCU66VY>.
You are receiving this because you authored the thread.
|
Is it possible for me, to change the AES key of the device? |
My understanding is, that it is possible. But you need an opto-head (infrared -reader and -writer) and the device monitor software from Engelmann. For my purpose it is to expensive. If you order new heat cost allocators, you should ask the provider/seller, if he can reprogram the AES-Key for you. Might be the do the service for you.
Let me know, if you find a good way. I’m still interested in it.
… Am 20.03.2023 um 22:21 schrieb Skysurfer-14 ***@***.***>:
Is it possible for me, to change the AES key of the device?
—
Reply to this email directly, view it on GitHub <#820 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASLV4AZCJWHFHNSXVE25WZDW5DC4PANCNFSM6AAAAAAUCU66VY>.
You are receiving this because you authored the thread.
|
Engelmann, the manufacturer of the HCA e2 gives the AES Manufacturer Key not to small customers (like me). But the intermediaries offer reprogramming of the devices at a small extra cost (3,59€ at zaehlershop.com) if you buy the devices there. |
I now have a HCA e2 Heat Cost Allocator here (Radio mode: C-mode OMS 4 Mode 5 with own AES key, Radio time: 7 am - 7 pm daily) and trying to decode the telegrams. This is what I receive:
The tpl-acc-field is incremented on every telegram and tpl-sts-field (ALARM PERMANENT_ERROR) could be active, since the tamper switch is active. |
Very nice! Make a copy of the driver_eursii.cc and to driver_hcae2.cc and change all eurisii references inside to hcae2. Update the addDetection to match your telegram. Now build wmbusmeters with only this driver (speeds things up) then do And start tweaking the internal rules of the driver until you catch all fields. I.e. they become green. A useful shortcut: Please have a go! Let me know if you have any questions. You can do an early pull request and I will help out! |
I'm glad for your help!
|
Great work! You can see that analyze does not find an auto-driver, ie a hardcoded lookup from Try again and auto will point to hcae2 |
Yes, it points now to hcae2. What´s next? |
Hello @weetmuts, is there anything else I need to do to get hcae2 support included in the repository? |
What can i do to make the Engelmann Heat Cost Allocator HCA e2 appears in my wmbusmeters Home Assistant Addon? |
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. |
Issue resolved in #956 |
hcae2 will be part of release 1.14 which is release later today. |
Hi,
I'm using heat cost allocators "HCA E2" from Engelmann Sensors (Manufacturer ID = 14c5). I can receive telegrams (see example below) but I'm struggling to decrypt the data. I'm pretty sure to use the right key (standard key). So I tried to analyze the telegram at you nice web page (https://wmbusmeters.org) and got same result (failed decryption. Wrong key?).
Are there any hints to find my mistake? Or is there anything special to regard with these type of sensors?
Thanks for your great work.
Example: cf44c5145041219029087a4800c025b1ca6bee1bba1e4b791ae0a22869dc66b523192799bc8a8a5a866a87a76450bd978f9a84db9aea4ac67c82f708784e16804eb783a38bc481653f002eed922a21c84ed8e2dc228af45b49822abb382ba798db0a9ea0eb40b5382b682a8e40466a5224137555860d35b56bfa726b17fcf6cb1f2f00ff174974f007bf440a27b6811cd20428c2f039248a8e2abbfec3c3908f580e36519ef1b66ac63f59ac8c5fbe2966ac18ad8b953ff51679db9f78e06c2e0b1d7931c8b6e0c219808adafe4532e816
AES-128 Standard-Key:
00112233445566778899aabbccddeeff
IV:
c5145041219029084848484848484848
The text was updated successfully, but these errors were encountered: