Migrated stiebel eltron heatpump binding for openHAB

Hogan · June 13, 2017, 7:48pm

hi peter,

current log entrys:

21:44:28.884 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'stiebelheatpump:stiebelHeatPumpLWZ303_5_39:0c083313' has been added.
21:44:29.165 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'stiebelheatpump:stiebelHeatPumpLWZ303_5_39:0c083313' changed from UNINITIALIZED to INITIALIZING
21:44:29.237 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Initializing stiebel heat pump handler 'stiebelheatpump:stiebelHeatPumpLWZ303_5_39:0c083313' with configuration: port '/dev/ttyUSB0', baudRate 115200, refresh 60.0.
21:44:29.672 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Request : Name -> version, Description -> Version information of heat pump firmware , RequestByte -> FD
21:44:29.704 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - set version request : Version information of heat pump firmware
21:44:29.743 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Request : Name -> time, Description -> Date and time information of heat pump , RequestByte -> FC
21:44:29.782 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - set time request : Date and time information of heat pump
21:44:29.823 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Request : Name -> currentValues, Description -> Temperature measurements of the heat pump. , RequestByte -> FB
21:44:29.856 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Request : Name -> operationCounters, Description -> Reads Operation counters of the heat pump. , RequestByte -> 09
21:44:29.901 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Request : Name -> nominalValues, Description -> Reads settings nominal values of the heat pump. , RequestByte -> 17
21:44:30.277 [DEBUG] [atpump.internal.CommunicationService] - Loading version info ...
21:44:30.337 [DEBUG] [atpump.internal.CommunicationService] - Request : Name -> version, Description -> Version information of heat pump firmware , RequestByte -> FD
21:44:30.383 [DEBUG] [atpump.internal.CommunicationService] - Sending start communication
21:44:30.433 [DEBUG] [belheatpump.protocol.SerialConnector] - Send 02
21:44:30.521 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 10
21:44:30.615 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 FE FD (04)10 03
21:44:30.671 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 10
21:44:30.729 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 02
21:44:30.793 [DEBUG] [belheatpump.protocol.SerialConnector] - Send 10
21:44:30.863 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
21:44:30.914 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
21:44:30.967 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received FC
21:44:31.020 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received FD
21:44:31.078 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
21:44:31.139 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received FD
21:44:31.182 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 10
21:44:31.237 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 03
21:44:31.282 [DEBUG] [atpump.internal.CommunicationService] - reached end of response message.
21:44:31.320 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parse bytes: (00)01 00 FC FD (04)01 FD 10 03
21:44:31.421 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value version#version -> 5.09 with pos: 4 , len: 2
21:44:31.477 [DEBUG] [belheatpump.protocol.SerialConnector] - Interrupt serial connection
21:44:31.537 [DEBUG] [belheatpump.protocol.SerialConnector] - Close serial stream
21:44:32.661 [DEBUG] [belheatpump.protocol.SerialConnector] - Disconnected
21:44:32.692 [INFO ] [tpump.handler.stiebelheatpumpHandler] - Heat pump has version 5.09
21:44:32.721 [ERROR] [tpump.handler.stiebelheatpumpHandler] - Thingtype version of heatpump 5.39 is not the same as the heatpump version 5.09
21:44:32.837 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'stiebelheatpump:stiebelHeatPumpLWZ303_5_39:0c083313' changed from INITIALIZING to OFFLINE (CONFIGURATION_ERROR): Error occurred while initializing stiebel heat pump handler!
21:44:39.314 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'stiebelheatpump:stiebelHeatPumpLWZ303_5_09:30a14a92' changed from UNINITIALIZED to REMOVING
21:44:46.448 [INFO ] [smarthome.event.ThingRemovedEvent   ] - Thing 'stiebelheatpump:stiebelHeatPumpLWZ303_5_09:30a14a92' has been removed.

Can you re-submit a 5.09 thing type? Would be perfect!

Thanks a lot!

I would try to get my code in to my github so you can see the source and may join coding

I’m in

BR
Hogan

kreutzer_peter · June 13, 2017, 7:56pm

hi hogan,

no problem…
new version with additional 5.09 uploaded.
BR
peter

hot · June 13, 2017, 8:01pm

Hi Peter, thanks for the new update. I think you missunderstood: Hogan has Version 5.09, I have version 5.39.
So instead of changing 5.09 to 5.39 please keep 5.09 and add 5.39.
I would also like to join coding!

Regards
Holger

hot · June 13, 2017, 8:02pm

damn, you’re too fast

kreutzer_peter · June 13, 2017, 8:02pm

not reallly

Hogan · June 13, 2017, 8:56pm

Ha,

22:55:13.263 [INFO ] [smarthome.event.ThingRemovedEvent   ] - Thing 'stiebelheatpump:stiebelHeatPumpLWZ303_5_39:c7a5f811' has been removed.
22:55:28.825 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3' changed from UNINITIALIZED to INITIALIZING
22:55:28.856 [INFO ] [smarthome.event.ThingAddedEvent     ] - Thing 'stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3' has been added.
22:55:28.891 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Initializing stiebel heat pump handler 'stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3' with configuration: port '/dev/ttyUSB0', baudRate 115200, refresh 60.0.
22:55:29.030 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Request : Name -> version, Description -> Version information of heat pump firmware , RequestByte -> FD
22:55:29.116 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - set version request : Version information of heat pump firmware
22:55:29.164 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Request : Name -> time, Description -> Date and time information of heat pump , RequestByte -> FC
22:55:29.212 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - set time request : Date and time information of heat pump
22:55:29.237 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Request : Name -> currentValues, Description -> Temperature measurements of the heat pump. , RequestByte -> FB
22:55:29.317 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Request : Name -> operationCounters, Description -> Reads Operation counters of the heat pump. , RequestByte -> 09
22:55:29.367 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Request : Name -> nominalValues, Description -> Reads settings nominal values of the heat pump. , RequestByte -> 17
22:55:29.478 [DEBUG] [atpump.internal.CommunicationService] - Loading version info ...
22:55:29.529 [DEBUG] [atpump.internal.CommunicationService] - Request : Name -> version, Description -> Version information of heat pump firmware , RequestByte -> FD
22:55:29.566 [DEBUG] [atpump.internal.CommunicationService] - Sending start communication
22:55:29.609 [DEBUG] [belheatpump.protocol.SerialConnector] - Send 02
22:55:29.653 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 10
22:55:29.700 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 FE FD (04)10 03
22:55:29.755 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 10
22:55:29.787 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 02
22:55:29.824 [DEBUG] [belheatpump.protocol.SerialConnector] - Send 10
22:55:29.859 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:29.892 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:29.929 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received FC
22:55:29.961 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received FD
22:55:29.984 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:30.026 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received FD
22:55:30.064 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 10
22:55:30.075 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 03
22:55:30.142 [DEBUG] [atpump.internal.CommunicationService] - reached end of response message.
22:55:30.168 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parse bytes: (00)01 00 FC FD (04)01 FD 10 03
22:55:30.216 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value version#version -> 5.09 with pos: 4 , len: 2
22:55:30.246 [DEBUG] [belheatpump.protocol.SerialConnector] - Interrupt serial connection
22:55:30.314 [DEBUG] [belheatpump.protocol.SerialConnector] - Close serial stream
22:55:31.422 [DEBUG] [belheatpump.protocol.SerialConnector] - Disconnected
22:55:31.440 [INFO ] [tpump.handler.stiebelheatpumpHandler] - Heat pump has version 5.09
22:55:31.563 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3' changed from INITIALIZING to ONLINE
22:55:37.612 [DEBUG] [atpump.internal.CommunicationService] - Loading Settings
22:55:37.649 [DEBUG] [atpump.internal.CommunicationService] - Loading data for request currentValues ...
22:55:37.671 [DEBUG] [atpump.internal.CommunicationService] - Request : Name -> currentValues, Description -> Temperature measurements of the heat pump. , RequestByte -> FB
22:55:37.701 [DEBUG] [atpump.internal.CommunicationService] - Sending start communication
22:55:37.718 [DEBUG] [belheatpump.protocol.SerialConnector] - Send 02
22:55:38.617 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 10
22:55:38.646 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 FC FB (04)10 03
22:55:48.873 [DEBUG] [atpump.internal.CommunicationService] - retry request!
22:55:48.900 [DEBUG] [atpump.internal.CommunicationService] - Sending start communication
22:55:48.928 [DEBUG] [belheatpump.protocol.SerialConnector] - Send 02
22:55:48.970 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 10
22:55:48.997 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 FC FB (04)10 03
22:55:49.028 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 10
22:55:49.060 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 02
22:55:49.088 [DEBUG] [belheatpump.protocol.SerialConnector] - Send 10
22:55:49.121 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:49.139 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:49.163 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 20
22:55:49.182 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received FB
22:55:49.211 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received FD
22:55:49.231 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received A8
22:55:49.250 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:49.280 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received A5
22:55:49.304 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:49.324 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 13
22:55:49.344 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:49.362 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 0D
22:55:49.382 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:49.402 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 0F
22:55:49.421 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:49.439 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received C7
22:55:49.459 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received FD
22:55:49.478 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received A8
22:55:49.498 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received FD
22:55:49.527 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received A8
22:55:49.547 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:49.576 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 05
22:55:49.594 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:49.613 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 03
22:55:49.633 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:49.663 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:49.687 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 11
22:55:49.706 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:49.734 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 90
22:55:49.756 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:49.783 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 90
22:55:49.805 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:49.831 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:49.860 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:49.893 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 1C
22:55:49.915 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:49.930 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 1C
22:55:49.952 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:49.967 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:49.987 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.005 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received B6
22:55:50.023 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.042 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.060 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.079 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.101 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 03
22:55:50.116 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received CC
22:55:50.136 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 03
22:55:50.156 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received D9
22:55:50.176 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.194 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.214 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.242 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.259 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.279 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.293 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.312 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.330 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.350 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.368 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.389 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received B4
22:55:50.405 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.423 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.443 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.460 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.482 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:50.497 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 02
22:55:50.527 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:50.549 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 09
22:55:50.585 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:50.612 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 06
22:55:50.639 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.671 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received F3
22:55:50.692 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.719 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received F2
22:55:50.750 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.782 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.814 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.846 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:50.870 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 0F
22:55:50.904 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 04
22:55:50.932 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 10
22:55:50.955 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 03
22:55:50.975 [DEBUG] [atpump.internal.CommunicationService] - reached end of response message.
22:55:51.084 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parse bytes: (00)01 00 20 FB (04)FD A8 00 A5 (08)01 13 01 0D (12)01 0F 01 C7 (16)FD A8 FD A8 (20)01 05 01 03 (24)00 00 11 01 (28)90 01 90 00 (32)00 00 1C 00 (36)1C 00 00 00 (40)B6 00 00 00 (44)00 03 CC 03 (48)D9 00 00 00 (52)00 00 00 00 (56)00 00 00 00 (60)B4 00 00 00 (64)00 01 02 01 (68)09 01 06 00 (72)F3 00 F2 00 (76)00 00 00 0F (80)04 10 03
22:55:51.119 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#collectorTemperatur -> -60.0 with pos: 4 , len: 2
22:55:51.156 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#outsideTemperatur -> 16.5 with pos: 6 , len: 2
22:55:51.180 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#flowTemperatur -> 27.5 with pos: 8 , len: 2
22:55:51.218 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#returnTemperatur -> 26.9 with pos: 10 , len: 2
22:55:51.261 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#hotGasTemperatur -> 27.1 with pos: 12 , len: 2
22:55:51.294 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#dHWTemperatur -> 45.5 with pos: 14 , len: 2
22:55:51.324 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#flowHC2Temperatur -> -60.0 with pos: 16 , len: 2
22:55:51.367 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#insideTemperatur -> -60.0 with pos: 18 , len: 2
22:55:51.399 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#evaporatorTemperatur -> 26.1 with pos: 20 , len: 2
22:55:51.431 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#condenserTemperature -> 25.9 with pos: 22 , len: 2
22:55:51.461 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#extractFanSpeed -> -112 with pos: 30 , len: 1
22:55:51.492 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#supplyFanSpeed -> 0 with pos: 31 , len: 1
22:55:51.523 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#exhaustFanSpeed -> 0 with pos: 32 , len: 1
22:55:51.557 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#filteredOutsideTemperatur -> 716.8 with pos: 34 , len: 2
22:55:51.614 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#insideTemperatur has value -60.0
22:55:51.649 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#insideTemperatur with -60.0
22:55:51.707 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#outsideTemperatur has value 16.5
22:55:51.724 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#outsideTemperatur with 16.5
22:55:51.749 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#exhaustFanSpeed has value 0
22:55:51.779 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#exhaustFanSpeed with 0
22:55:51.799 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#filteredOutsideTemperatur has value 716.8
22:55:51.822 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#filteredOutsideTemperatur with 716.8
22:55:51.855 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#condenserTemperature has value 25.9
22:55:51.872 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#condenserTemperature with 25.9
22:55:51.894 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#hotGasTemperatur has value 27.1
22:55:51.923 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#hotGasTemperatur with 27.1
22:55:51.950 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#returnTemperatur has value 26.9
22:55:51.971 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#returnTemperatur with 26.9
22:55:51.998 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#supplyFanSpeed has value 0
22:55:52.019 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#supplyFanSpeed with 0
22:55:52.044 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#evaporatorTemperatur has value 26.1
22:55:52.071 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#evaporatorTemperatur with 26.1
22:55:52.107 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#collectorTemperatur has value -60.0
22:55:52.128 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#collectorTemperatur with -60.0
22:55:52.169 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#flowHC2Temperatur has value -60.0
22:55:52.192 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#flowHC2Temperatur with -60.0
22:55:52.221 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#dHWTemperatur has value 45.5
22:55:52.242 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#dHWTemperatur with 45.5
22:55:52.267 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#flowTemperatur has value 27.5
22:55:52.312 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#flowTemperatur with 27.5
22:55:52.339 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data currentValues#extractFanSpeed has value -112
22:55:52.367 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:currentValues#extractFanSpeed with -112
22:55:53.607 [DEBUG] [atpump.internal.CommunicationService] - Loading Settings
22:55:53.628 [DEBUG] [atpump.internal.CommunicationService] - Loading data for request operationCounters ...
22:55:53.658 [DEBUG] [atpump.internal.CommunicationService] - Request : Name -> operationCounters, Description -> Reads Operation counters of the heat pump. , RequestByte -> 09
22:55:53.671 [DEBUG] [atpump.internal.CommunicationService] - Sending start communication
22:55:53.688 [DEBUG] [belheatpump.protocol.SerialConnector] - Send 02
22:55:53.720 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 10
22:55:53.759 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 0A 09 (04)10 03
22:55:53.782 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 10
22:55:53.802 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 02
22:55:53.823 [DEBUG] [belheatpump.protocol.SerialConnector] - Send 10
22:55:53.856 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:53.876 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:53.897 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 6E
22:55:53.922 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 09
22:55:53.943 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 08
22:55:53.963 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 22
22:55:53.989 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:54.017 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:54.043 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 01
22:55:54.065 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 42
22:55:54.092 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:54.120 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 03
22:55:54.144 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 00
22:55:54.163 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received F4
22:55:54.193 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 10
22:55:54.222 [DEBUG] [ebelheatpump.protocol.ByteStreamPipe] - Received 03
22:55:54.254 [DEBUG] [atpump.internal.CommunicationService] - reached end of response message.
22:55:54.275 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parse bytes: (00)01 00 6E 09 (04)08 22 00 00 (08)01 42 00 03 (12)00 F4 10 03
22:55:54.308 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value operationCounters#compressorA -> 2082 with pos: 4 , len: 2
22:55:54.342 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value operationCounters#compressorB -> 0 with pos: 6 , len: 2
22:55:54.384 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value operationCounters#heatingMode -> 322 with pos: 8 , len: 2
22:55:54.404 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value operationCounters#dHWMode -> 3 with pos: 10 , len: 2
22:55:54.421 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value operationCounters#coolingMode -> 244 with pos: 12 , len: 2
22:55:54.456 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data operationCounters#compressorB has value 0
22:55:54.484 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:operationCounters#compressorB with 0
22:55:54.511 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data operationCounters#dHWMode has value 3
22:55:54.542 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:operationCounters#dHWMode with 3
22:55:54.584 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data operationCounters#compressorA has value 2082
22:55:54.604 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:operationCounters#compressorA with 2082
22:55:54.645 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data operationCounters#heatingMode has value 322
22:55:54.676 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:operationCounters#heatingMode with 322
22:55:54.708 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Data operationCounters#coolingMode has value 244
22:55:54.737 [DEBUG] [tpump.handler.stiebelheatpumpHandler] - Update channel UID stiebelheatpump:stiebelHeatPumpLWZ303_5_09:6e0e17e3:operationCounters#coolingMode with 244
22:55:54.803 [DEBUG] [belheatpump.protocol.SerialConnector] - Interrupt serial connection
22:55:54.830 [DEBUG] [belheatpump.protocol.SerialConnector] - Close serial stream
22:55:55.943 [DEBUG] [belheatpump.protocol.SerialConnector] - Disconnected

very nice!

Thanks Peter!

kreutzer_peter · June 13, 2017, 9:00pm

great,
values seems not all to be correct , but this we gone fine tune from now on
maybe in the FHEM forum we get more infos on how to correctly decode the values

BR
peter

Hogan · June 13, 2017, 9:05pm

well i have the THZ-pm over here. The parsing of the protocol verison is included in the pm-file.
@Holger: v5.39 is working in FHEM so maybe it*s worth a look in the THZ.pm

Unfortunatley the 5.09 isn*t decoded yet…

kreutzer_peter · June 14, 2017, 5:35am

if you are looking into the THZ.pm … if you understand how the change of value is working and could help out to describe thisthatwouldhlep me a lot
to my understanding the way to set parameters hase changed from 2.x to upper versions.
in the older versios all parameter were grouped in registered and when writing 1 parameter the complete register needed to be registered.
For newer versions the parameters can be writen individually

the current code is here

hot · June 14, 2017, 9:43am

Just for the record here a summary of the logs with the 2.06 protocol parser and the 5.39 heatpump:

06:27:39.187 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 FE FD (04)10 03 
06:27:39.208 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parse bytes: (00)01 00 1B FD (04)02 1B 10 03     
06:27:39.208 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value version#version -> 5.39 with pos: 4 , len: 2

06:27:46.247 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 FC FB (04)10 03 
06:27:46.290 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parse bytes: (00)01 00 33 FB (04)FD A8 00 96 (08)01 4F 01 3A (12)01 0F 01 D5 (16)FD A8 FD A8 (20)01 09 01 30 (24)00 00 11 01 (28)0E 01 0E 00 (32)00 00 16 00 (36)26 00 00 00 (40)A3 00 00 00 (44)00 03 EA 03 (48)F8 00 00 00 (52)00 00 00 00 (56)00 00 00 00 (60)83 00 00 00 (64)00 01 3D 01 (68)42 01 11 01 (72)0B 01 1D 00 (76)00 00 00 0F (80)C1 10 03 
06:27:46.291 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#collectorTemperatur -> -60.0 with pos: 4 , len: 2
06:27:46.291 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#outsideTemperatur -> 15.0 with pos: 6 , len: 2
06:27:46.291 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#flowTemperatur -> 33.5 with pos: 8 , len: 2
06:27:46.291 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#returnTemperatur -> 31.4 with pos: 10 , len: 2
06:27:46.292 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#hotGasTemperatur -> 27.1 with pos: 12 , len: 2
06:27:46.292 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#dHWTemperatur -> 46.9 with pos: 14 , len: 2
06:27:46.292 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#flowHC2Temperatur -> -60.0 with pos: 16 , len: 2
06:27:46.292 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#insideTemperatur -> -60.0 with pos: 18 , len: 2
06:27:46.292 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#evaporatorTemperatur -> 26.5 with pos: 20 , len: 2
06:27:46.292 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#condenserTemperature -> 30.4 with pos: 22 , len: 2
06:27:46.293 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#extractFanSpeed -> 14 with pos: 30 , len: 1
06:27:46.293 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#supplyFanSpeed -> 0 with pos: 31 , len: 1
06:27:46.293 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#exhaustFanSpeed -> 0 with pos: 32 , len: 1
06:27:46.293 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#filteredOutsideTemperatur -> 563.2 with pos: 34 , len: 2

06:27:47.515 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 0A 09 (04)10 03
06:27:47.540 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parse bytes: (00)01 00 1B 09 (04)0B 07 00 00 (08)09 80 00 62 (12)02 12 10 03     
06:27:47.540 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value operationCounters#compressorA -> 2823 with pos: 4 , len: 2
06:27:47.540 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value operationCounters#compressorB -> 0 with pos: 6 , len: 2
06:27:47.540 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value operationCounters#heatingMode -> 2432 with pos: 8 , len: 2
06:27:47.540 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value operationCounters#dHWMode -> 98 with pos: 10 , len: 2
06:27:47.541 [DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value operationCounters#coolingMode -> 530 with pos: 12 , len: 2

hot · June 14, 2017, 9:58am

Peter, could you please explain the structure of the thing-types.xml?

How can it distinguish to parse a channel for the different versions?
For example: The value of the “filtered outside temperature” is on position 34 for version 2.06 but on position 39 for version 5.39
How can it read 1-bit values? For example the heatPipeValve, diverterValve, dhwPump, heatingCircuitPump which are all on position 24

Or are these subjects just not yet handled/implemented?

Regards
Holger

kreutzer_peter · June 14, 2017, 11:25am

HI holger,

while moving from OH1 to OH2 i decided to replace the xml structure used to define the decoding and integraded it into the thing type definition. So all is available but not visible

So the former (XML) request has been replaced by channel group and the record definitions are replaced by the channel definition and their propoerties representing the record item.

The full thingtype has this example.

	<channel-group-type id="channelGroupTypeVersion" >
	    <label>Version</label>
	    <description>Version information of heat pump firmware</description>
	    <channels>
	    <!-- at least 1 channel-group with id = version must be included  -->
	        <channel id="version" typeId="version" >
                <properties>
                    <property name="dataType">Status</property>
                    <property name="requestByte">0xfd</property>
                    <property name="position">4</property>
                    <property name="length">2</property>
                    <property name="scale">0.01</property>
                </properties>
            </channel>
	    </channels>
        </channel-group-type>

to my understanding some firmware versions have equal data request and some may change.
if you have requests which is different from version to version we can just add a new channel group for that specific version
E.g.; I assume that version and time request are equial to all and we just define it once and reference it in any supported thing type. I
For channelGroupTypeCurrentValues you may have version specific channel definition requirements , therfore we should define a new channelgroup and references it then in the thing type
keep in mind that there are also channeltypes which are referenced in the channelgroup , which again can reused for all channeld, e.g. temperatur measurement or temperatur settings.

2.yes , the functionality is in and can be used as before. we just store the configuration information in a different file.
Just add the property bitPosition to the channel definition
here is an example in the old xml
<recordDefinition name="HP1Monday" position="8" length="1" scale="1.0" dataType="Settings" min="0" max="1" step="1.0" unit="weekday" bitPosition="7"/>

In the channel definition i do not add all if they are not required. So bitPosition is only used in specific bytes , which i have not yet added.

if you have a running OH1 with that binding and have your own version xml you can easily convert the data.

I am not sure if the way i try to solve it is the right one. we are just in the beginning so we may change it to a more optimal way. lets us know if you have better ways
will do my best do descibe the necessary information inside the thingtype file

BR
peter

kreutzer_peter · June 14, 2017, 11:31am

just to add…

i am planning to implement 2 new feature…

trigger time update from PaperUi with trigger channel.
trigger a general debug read with a trigger channel to get the response in byte format for the known request bytes.

code is already available but need to better understand t odefine the trigger channels

/peter

kreutzer_peter · June 14, 2017, 8:32pm

implemented:

there is now an switch which triggers a dump of responses for following request bytes.
let me know if you see others to by added.
public static byte[] DEBUGBYTES = { (byte) 0x01, (byte) 0x09, (byte) 0x16, (byte) 0x17, (byte) 0xD1, (byte) 0xD2,
(byte) 0xE8, (byte) 0xE9, (byte) 0xF2, (byte) 0xF3, (byte) 0xF4, (byte) 0xF5, (byte) 0xF6, (byte) 0xFB,
(byte) 0xFC, (byte) 0xFD, (byte) 0xFE };
to set the time in the heat pump a new switch which is triggering to set the time of the heat pump to current time

the switches are implemented as advanced channels which can be activated with “show more”

/peter

kreutzer_peter · June 15, 2017, 10:15am

in the meantime some more updates and uploaded new version.

1
I changed the way how the polling of data is structured.
new is that basedon the linked channels the request which contain the item will be dynamically added to a list of request which are periodically polled.
By that a new channel which get activated in paperUI is added automatically to this list

2
finally was able to getthe setting of parameters workingin my heatpump.
So changing slidering paperUI changes parameter in heat pump
I am not sure if the way it is working old firmeware versions (2.06) is the same for new once (5.09 or 5.39)
please verify and let me know if we need to adapt it based on the firmware version

3
added ventilation setting to thingtype

/peter

JohnnyX · June 15, 2017, 6:09pm

Seems to be a misunderstanding: I was referring to these to sites:

Redirecting to Google Groups
Monitoring a Stiebel Eltron LWZ | Robert Penz Blog
And saw that you were already active in this thread. I want to connect my heat pump with this self made CAN-Sub-D9-USB plug.

But how can I figure out whether your binding will work with my heat pump? How can I find the information that you need to answer my question? You mentioned a “mechanism” - which one do you mean?

Thanks & Regards
John

kreutzer_peter · June 15, 2017, 7:51pm

well the CAN interface is not really good documented.
i am not familiar in the CANbus protocol.
will be very challenging to support you , so do not expect a working solution.

concerning the mechanism. it look like also the polling approach is the same for the can bus.
you send a request and get a response with data.
for the rs232 interface if is quiet good info in the www to implement code for openhab.
for canbus interface i didi not really find code and examples
if you have code samples how to read data , let me know
so the anser is that
/peter

kreutzer_peter · June 16, 2017, 7:56am

hi john,

found this link
http://www.juerg5524.ch/list_data.php

According the description the CAN interface should also be available on my heatpump.
Have not found it yet…
In above link there are a bunch of files available with code …

the stieble ISG gateway uses CAN so i thing it should work.
In the link you send you will see that there were statements that thedifference isto big betweeen RS232 and CAN…

/Peter

kreutzer_peter · June 17, 2017, 9:28am

for the once that want to extend thingtype for their own version.
I finally found a way to get access on the channeltype definitions in the initialize methode.
the min. max and steps property will not be anymore required as the same information is already defined on the channeltype information.

also the unit will not be required as this is already covered by the pattern property in the channel definition.
will do some test before i finally submit the code

/Peter

hot · June 17, 2017, 10:04am

Hi Peter,

When I trigger the switch, I get the responses like this:

[INFO ] [atpump.internal.CommunicationService] - Request (00)01 03 0B 07 (04)10 03  received response : (00)01 03 0B 07

Is ist possible to get the responses parsed with the outputs like this:

[DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value operationCounters#compressorA -> 2823 with pos: 4 , len: 2
[DEBUG] [.stiebelheatpump.protocol.DataParser] - Parsed value currentValues#exhaustFanSpeed -> 0 with pos: 32 , len: 1

Nearly all request are retried, do you have an idea which parameter is responsible for a delay before new requests?

09:56:20.661 [INFO ] [atpump.internal.CommunicationService] - Prepare response for request byte %02X
09:56:20.707 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 08 07 (04)10 03
09:56:21.787 [DEBUG] [atpump.internal.CommunicationService] - retry request!
09:56:21.844 [DEBUG] [atpump.internal.CommunicationService] - Sending start communication
09:56:21.957 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 08 07 (04)10 03
09:56:22.034 [DEBUG] [atpump.internal.CommunicationService] - reached end of response message.
09:56:22.073 [INFO ] [atpump.internal.CommunicationService] - Request (00)01 03 0B 07 (04)10 03  received response : (00)01 03 0B 07
09:56:23.302 [INFO ] [atpump.internal.CommunicationService] - Prepare response for request byte %02X
09:56:23.331 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 0A 09 (04)10 03
09:56:24.401 [DEBUG] [atpump.internal.CommunicationService] - retry request!
09:56:24.424 [DEBUG] [atpump.internal.CommunicationService] - Sending start communication
09:56:24.491 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 0A 09 (04)10 03
09:56:24.586 [DEBUG] [atpump.internal.CommunicationService] - reached end of response message.
09:56:24.633 [INFO ] [atpump.internal.CommunicationService] - Request (00)01 00 1C 09 (04)0B 07 00 00 (08)09 80 00 63 (12)02 12 10 08)09 80 00 63 (12)02 12 10 03
09:56:25.864 [INFO ] [atpump.internal.CommunicationService] - Prepare response for request byte %02X
09:56:25.878 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 11 10 (04)10 10 03
09:56:27.007 [DEBUG] [atpump.internal.CommunicationService] - retry request!
09:56:27.030 [DEBUG] [atpump.internal.CommunicationService] - Sending start communication
09:56:27.097 [DEBUG] [belheatpump.protocol.SerialConnector] - Send request message : (00)01 00 11 10 (04)10 10 03
09:56:27.223 [DEBUG] [atpump.internal.CommunicationService] - reached end of response message.
09:56:27.257 [INFO ] [atpump.internal.CommunicationService] - Request (00)01 03 14 10 (04)10 10 03  received response : (00)01 03 14

3. Regarding your last post about channeltype definitions for different heatpump versions, maybe you can post a short example?

Regards
Holger