Closed TobiasSt78 closed 1 year ago
This sounds very weird. If you have turned on the compact telegram cache, you should not see this message... Could you please provide a debug log?
Do you have a hint for me how to get a debug file from the adapter?
To turn on debug logging you need to:
Instances
loglevel
appearsinfo
to debug
(adapter will restart!)OK, here comes the debug. I need to delete all objects and restart the adapter, otherwise, it won't get new values. I just changed the AES key in the data below to ensure privacy.
[...]
2023-03-04 17:37:00.390 - error: wireless-mbus.0 (8519) Unsupported CI Field 79, remaining payload is [...]
2023-03-04 17:37:00.391 - debug: wireless-mbus.0 (8519) Parser failed to parse telegram from device KAW-12345678
[...]
Thanks for the log. The manufacturer is decoded as KAW
instead of KAM
- therefore the compact frame cache does not work. I will try to investigate it.
I also edited your post to make it a bit shorter with only the (probably) relevant part of the log.
Thanks a lot. Do you need any further information? I can also share the key if necessary but not in public ;-)
Ok the anwser seems pretty straighforward, Kamstrup also uses KAW
as manufacturer ID (Kamstrup Water seem to be the intention)...
I just removed the manufacturer ID check from the compact telegram handling in 0c2c4ae (v.8.10). Now you should only a "Unknown compact frame format" message a few times after an adapter restart until a full telegram was received.
The new 0.8.10 version works without breaks. Thank you! Great job.
Hello, great adapter but not 100% compatible with Kamstrup FlowIQ2200 water flow meter
I get every minute a error log: "Unsupported CI Field 79, remaining payload is 05099bf700000000190200008a0105f0ffffffffe123fa130000da04000011"
Nevertheless, the adapter works and gets infromation from the water flow meter. I have tested Version 0.8.6 and 0.8.8
My Setup; CUL /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A50285BI-if00-port0 C/T Mode 38100 [X] Cache for compact telegrams.
Cheers, Tobias.