You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The data stream received from the device for the key Betriebswerte_1_HK1 4.
2022-04-17_05:47:24.891 DEV 02
2022-04-17_05:47:24.902 DEV 80
2022-04-17_05:47:24.906 DEV 00
2022-04-17_05:47:24.910 DEV 04
2022-04-17_05:47:24.913 DEV 10
2022-04-17_05:47:24.917 DEV 03
2022-04-17_05:47:24.922 DEV 97
is parsed correctly as
2022-04-17_05:47:24.923 Betriebswerte_1_HK1 4
The data stream received for the key Betriebswerte_2_HK1 2.
2022-04-17_05:47:25.139 DEV 02
2022-04-17_05:47:25.147 DEV 80
2022-04-17_05:47:25.153 DEV 01
2022-04-17_05:47:25.156 DEV 02
2022-04-17_05:47:25.160 DEV 10
2022-04-17_05:47:25.164 DEV 03
2022-04-17_05:47:25.169 DEV 90
results in
Wrong CRC in 100390 (90 vs. 13)
which is not correct.
The reason for this problem is that parsing the second '02' value deletes all previously added data in $tbuf at
I am using https://github.com/mhop/fhem-mirror/blob/master/fhem/contrib/km271.pl to extract log data from a Buderus Logamatic 2107 and have discovered an error in the log data parser when a value is received as 0x02 as shown in the following example:
The data stream received from the device for the key
Betriebswerte_1_HK1 4
.is parsed correctly as
The data stream received for the key
Betriebswerte_2_HK1 2
.results in
which is not correct.
The reason for this problem is that parsing the second '02' value deletes all previously added data in
$tbuf
atfhem-mirror/fhem/contrib/km271.pl
Line 138 in 28c1647
The text was updated successfully, but these errors were encountered: