search

lvogt / ioBroker.wireless-mbus

ioBroker wireless M-Bus adapter
GNU General Public License v2.0
6 stars 4 forks source link

Engelmann SensoStar U - Telegram Parser #205

Closed mlotz3004 closed 1 month ago

mlotz3004 commented 1 month ago

Hi, i just bought a Engelmann SensoStar U heat meter. Invoice says:

BDEE000250 Engelmann Funk-Ultraschall-Wärmezähler, SensoStar U Qp 6,0m²/h TF 5,0 mm, DN 25, BL 150 mm G5/4B mit Einzelverschlüsslung

A Kamstrup and Zenner device is working fine in iobroker with CUL-Stick, so i think the Parser just doesn´t know how to handle the Engelmann.

Log in iobroker: wireless-mbus.0 2024-07-20 18:54:25.536 debug Parser failed to parse telegram from device EFE-xxxxxxxx wireless-mbus.0 2024-07-20 18:54:25.535 error application layer message too short, expected 174, got 147 bytes wireless-mbus.0 2024-07-20 18:54:25.534 debug ad44c5144144254200047a4c009025cce562e58afbbc747e925dd45fb72f1849ac5c68b585e7b8e4b456688b88cdd06653be9627598aaee5a321a8042da9cfb5f3819867caa0adec992a5a3c4fe5a74e32aa9ea38be23075a0a7b5d98096abc5f5e95953792c9e2c1e67547e3939f4bd14ce8ad76121a9a612ea229c4fe9bcd01b0b49d2ef27dad63a85c11ae88ad8764f2432 wireless-mbus.0 2024-07-20 18:54:25.532 debug ad44c5144144254200047a4c009025cce562e58afbbc747e925dd45fb72f1849ac5c68b585e7b8e4b456688b88cdd06653be9627598aaee5a321a8042da9cfb5f3819867caa0adec992a5a3c4fe5a74e32aa9ea38be23075a0a7b5d98096abc5f5e95953792c9e2c1e67547e3939f4bd14ce8ad76121a9a612ea229c4fe9bcd01b0b49d2ef27dad63a85c11ae88ad8764f2432 wireless-mbus.0 2024-07-20 18:54:25.531 debug Found AES key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx wireless-mbus.0 2024-07-20 18:54:25.530 debug CUL: Message received: 00ad44c5144144254200047a4c009025cce562e58afbbc747e925dd45fb72f1849ac5c68b585e7b8e4b456688b88cdd06653be9627598aaee5a321a8042da9cfb5f3819867caa0adec992a5a3c4fe5a74e32aa9ea38be23075a0a7b5d98096abc5f5e95953792c9e2c1e67547e3939f4bd14ce8ad76121a9a612ea229c4fe9bcd01b0b49d2ef27dad63a85c11ae88ad8764f2432ed

Please let me know if additional information is necessary.

lvogt commented 1 month ago

I think wmbusmeters is just more accommodating here, if look at the end of wmbusmeters per byte analysis you'll see something with varlen=87 and the following bytes are much less than 87...

You are missing part of the telegram. My guess is, that you have set the buffer for received telegrams too small in the cul firmware.

mlotz3004 commented 1 month ago

Thank you very much! Indeed there are more people having trouble fetching big telegrams with the nanoCUL. I'll try to increase the Buffer, delete not used functions or switch to a microcontroller with more ram.

Edit: I issued because i didn´t pay attention to https://github.com/wmbusmeters/wmbusmeters-wiki/blob/master/nanoCUL.md

Issue was telegram could not be parsed, since receive buffer on Arduino Nano CUL was too small (just 148 Bytes). That is the maximum you can achieve. Stripping the code makes more work than to change microcontroller. I changed to "Arduino Nano Every" and (after a bumpy setup in an LXC) everything works fine.