search

lvogt / ioBroker.wireless-mbus

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

Some telegrams fail to parse #69

Closed copystring closed 2 years ago

copystring commented 2 years ago

Thanks for implementing C MODE. I was waiting for this. So I went to try this. It works with my cold water meter but some messages fail to get parsed. Could you have a look at this?

https://pastebin.com/2tqqd7K6

Thanks

copystring commented 2 years ago

I have to add the telegrams are not encrypted.

lvogt commented 2 years ago

I have only checked it very briefly, but I guess the only thing you have to do is, to activate the "compact frame cache" in the adapter options. After the first "long" telegram has been received the other ones can be parsed too.

copystring commented 2 years ago

Sorry for the late responce. My nanoCUL broke. Now I have a replacement I activated "compact frame cache". But the error remains.

Here's a new log with compact frame cache enabled: https://pastebin.com/vA5GG8rR

copystring commented 2 years ago

Actually. After a while the error disappears. Can it be the right message for compact frame cache appears not right after the start of the adapter? I guess it makes sense because the water meter sends the messages every X seconds. We can close this yeah?

lvogt commented 2 years ago

Yes, as I wrote, the adapter needs to receive a "long" telegram before the compact ones can be decoded (true for every adapter restart btw.)

copystring commented 2 years ago

Makes sense. I forgot about what you wrote :) Thank you!