[new binding] Logger LSW for Sofar/Omnik/IE for SolarmanPV based on protocol v5 (iGEN tech)

Piotr_Bojko · March 13, 2023, 10:32pm

Decoded fully one message, @MacBac please advice whether is it ok:

{"ActivePower_Load_Sys"=0 W, "ActivePower_Output_L1N"=0 W, "ActivePower_Output_L2N"=0 W, "ActivePower_Output_R"=0 W, "ActivePower_Output_S"=0 W, "ActivePower_Output_T"=0 W, "ActivePower_PCC_L1N"=0 W, "ActivePower_PCC_L2N"=0 W, "ActivePower_PCC_R"=0 W, "ActivePower_PCC_S"=0 W, "ActivePower_PCC_T"=0 W, "ActivePower_PCC_Total"=0 W, "ActivePower_PV_Ext"=0 W, "ApparentPower_Output_Total"=570 W, "ApparentPower_PCC_Total"=0 W, "Current_Output_L1N"=0 A, "Current_Output_L2N"=0 A, "Current_Output_R"=0.8 A, "Current_Output_S"=0.85 A, "Current_Output_T"=0.79 A, "Current_PCC_L1N"=0 A, "Current_PCC_L2N"=0 A, "Current_PCC_R"=0 A, "Current_PCC_S"=0 A, "Current_PCC_T"=0 A, "GridOutput_Rsvd1"=, "GridOutput_Rsvd2"=, "PowerFactor_Output_R"=0, "PowerFactor_Output_S"=0, "PowerFactor_Output_T"=0, "PowerFactor_PCC_R"=0, "PowerFactor_PCC_S"=0, "PowerFactor_PCC_T"=0, "R_Rsvd1"=, "R_Rsvd2"=, "ReactivePower_Output_R"=0 W, "ReactivePower_Output_S"=0 W, "ReactivePower_Output_T"=0 W, "ReactivePower_Output_Total"=-430 W, "ReactivePower_PCC_R"=0 W, "ReactivePower_PCC_S"=0 W, "ReactivePower_PCC_T"=0 W, "ReactivePower_PCC_Total"=0 W, "S_Rsvd1"=, "T_Rsvd1"=, "T_Rsvd2"=, "Voltage_Line_L1"=0 V, "Voltage_Line_L2"=0 V, "Voltage_Line_L3"=0 V, "Voltage_Phase_L1N"=0 V, "Voltage_Phase_L2N"=0 V, "Voltage_Phase_R"=233.89999389648438 V, "Voltage_Phase_S"=229.6999969482422 V, "Voltage_Phase_T"=233.6999969482422 V, "gridFrequency"=49.98 Hz, "outputActivePower"=310 W, "s_Rsvd2"=}

Do you have battery bank?

MacBac · March 14, 2023, 3:41pm

I don’t have battery. I cannot confirm the parameters above as I don’t monitor them (power, daily and total production only). I can attach what I receive from the kubaceg/sofar_g3_lsw3_logger_reader solution, now (low power). Some values must be divided by 100 or 10.

"ActivePower_Load_Sys":0,"ActivePower_Output_L1N":0,"ActivePower_Output_L2N":0,"ActivePower_Output_R":0,"ActivePower_Output_S":0,"ActivePower_Output_T":0,"ActivePower_Output_Total":49,"ActivePower_PCC_L1N":0,"ActivePower_PCC_L2N":0,"ActivePower_PCC_R":0,"ActivePower_PCC_S":0,"ActivePower_PCC_T":0,"ActivePower_PCC_Total":0,"ActivePower_PV_Ext":0,"ApparentPower_Output_Total":69,"ApparentPower_PCC_Total":0,"Countdown":60,"Current_Output_L1N":0,"Current_Output_L2N":0,"Current_Output_R":98,"Current_Output_S":101,"Current_Output_T":97,"Current_PCC_L1N":0,"Current_PCC_L2N":0,"Current_PCC_R":0,"Current_PCC_S":0,"Current_PCC_T":0,"Current_PV1":76,"Current_PV2":90,"Fault1":0,"Fault10":0,"Fault11":0,"Fault12":0,"Fault13":0,"Fault14":0,"Fault15":0,"Fault16":0,"Fault17":0,"Fault18":0,"Fault19":0,"Fault2":0,"Fault20":0,"Fault21":0,"Fault22":0,"Fault23":0,"Fault24":0,"Fault25":0,"Fault26":0,"Fault27":0,"Fault3":0,"Fault4":0,"Fault5":0,"Fault6":0,"Fault7":0,"Fault8":0,"Fault9":0,"Frequency_Grid":4993,"GenerationTime_Today":631,"GenerationTime_Total":48036,"InsulationResistance":818,"LastTimestamp":1678808323005,"PV_Generation_Today":1000,"PV_Generation_Total":4713,"PowerFactor_Output_R":0,"PowerFactor_Output_S":0,"PowerFactor_Output_T":0,"PowerFactor_PCC_R":0,"PowerFactor_PCC_S":0,"PowerFactor_PCC_T":0,"Power_PV1":23,"Power_PV2":30,"ReactivePower_Output_R":0,"ReactivePower_Output_S":0,"ReactivePower_Output_T":0,"ReactivePower_Output_Total":-44,"ReactivePower_PCC_R":0,"ReactivePower_PCC_S":0,"ReactivePower_PCC_T":0,"ReactivePower_PCC_Total":0,"ServiceTime_Total":54359,"SysState":2,"SysTime_Date":14,"SysTime_Hour":16,"SysTime_Minute":38,"SysTime_Month":3,"SysTime_Second":42,"SysTime_Year":23,"Temp_Rsvd1":0,"Temp_Rsvd2":0,"Temp_Rsvd3":0,"Temperature_Env1":34,"Temperature_Env2":0,"Temperature_HeatSink1":24,"Temperature_HeatSink2":0,"Temperature_HeatSink3":0,"Temperature_HeatSink4":0,"Temperature_HeatSink5":0,"Temperature_HeatSink6":0,"Temperature_Inv1":25,"Temperature_Inv2":0,"Temperature_Inv3":0,"Voltage_Line_L1":0,"Voltage_Line_L2":0,"Voltage_Line_L3":0,"Voltage_PV1":3059,"Voltage_PV2":3387,"Voltage_Phase_L1N":0,"Voltage_Phase_L2N":0,"Voltage_Phase_R":2342,"Voltage_Phase_S":2350,"Voltage_Phase_T":2353

May not match as time is not exactly the same:
Today kWh ~ 10kWh
Total kWh ~ 471kWh
Total Power ~ 0.49kWh

Piotr_Bojko · March 14, 2023, 11:10pm

I have decoded more or less 80 channels for new thing representing new inverter with logges sn23xxx.

This new one has more complex communication scheme (3 request instead of 1 and 4-5 more responses) than original one. It may take some time I scratch new descriptors for the new thing and patch here and there communication.

Straits_PL · March 20, 2023, 9:58am

Hello Piotr!

First of all, I would like to thank you very much for your work, which I have been using successfully for over a year. Recently, I installed a second PV installation also based on the SOFAR inverter and the LSE-3 logger (Ethernet). Unfortunately, I had a problem with connecting the logger to the new inverter (G3 - one phase). The remote firmware update made by the Polish branch of Sofar to ME_0D_2701_5.09 helped with above problems. By the way, they updated me second logger from version ME_08_2701_2.06 to ME_0D_2701_5.09. And it was a big mistake because I lost communication through your binding
Unfortunately, it is not possible to go back to the previous working version of the firmware…

Both loggers have SN starting with 21xxx, but this is more about the firmware, not the HW of the logger I guess…

In openhab log I see 2 entries (different for both loggers).

Unknown response, length 9: A5:17:00:10:45:03:00:A1:02:
Unknown response, length 9: A5:17:00:10:45:03:00:CD:02:

Can I somehow help you get these loggers working?

Piotr_Bojko · March 20, 2023, 3:19pm

@Straits_PL you could ask the support whether they have a modbus registers map for the firmware. Or try to look through the internet.

Maybe switching from ME_08_2701_2.06 to ME_0D_2701_5.09 has changed modbus registers for the inverter. The binding itself asks the logger for a specific registers for given SN - they should match.

Having this - adding a mapping would be fairly easy (, but still tedious).

Piotr_Bojko · March 20, 2023, 10:52pm

Current test builds are here Handle loggers with SN 23xxxx · Issue #1 · ptrbojko/openhab-lsw4inverter-binding · GitHub

Piotr_Bojko · March 24, 2023, 6:27pm

Hello, if anyone want to check the current build against hiw g3 sofar or lsw win sn 23/21? Go ahead https://github.com/ptrbojko/openhab-lsw4inverter-binding/suites/11794469478/artifacts/615392482

Track the issue here - Handle loggers with SN 23xxxx · Issue #1 · ptrbojko/openhab-lsw4inverter-binding · GitHub
You can support me there as well

Piotr_Bojko · April 3, 2023, 10:09pm

Hi all,

I have created a post under third party marketplace. I wish to be soon available straight from the TPM from your openhab instances.

antcan · April 13, 2023, 8:01am

Hi, I have the same problem my firmware is ME_0D_270A_1.08
Channel online is on but everything else is null.
in the log file I have this:

Blockquote
[al.protocolv5.UnknownResponseHandler] - Unknown response, length 9: A5:17:00:10:45:03:00:AE:02:
Blockquote

Have you solved?

Piotr_Bojko · April 13, 2023, 9:26am

Could you elaborate more? Which inverter do you have, what format of serial number does the wifi stick have? Also which version of binding do you use and which thing type?

You can file an issue here for better tracking - GitHub - ptrbojko/openhab-lsw4inverter-binding

Regards,
Piotr

antcan · April 13, 2023, 10:38am

Thanks for your kind response.
Serial number 2106******
inverter 3ph hyd 15000 zss
i tried both things versions with the same result.
I’ll try on github. I’m inexperienced.
Regards, Antonio

antcan · April 13, 2023, 1:53pm

I’m not able

alex_alexandroff22 · April 26, 2023, 7:11am

Same here. Thing online, but everything else NULL
Deye with SN 23…

	10243	2023-04-26 06:50:40.444 [WARN ] [al.protocolv5.UnknownResponseHandler] - Unknown response, length 29: A5:10:00:10:15:00:21:67:8F:CD:F9:02:01:F0:95:0E:00:AE:08:00:00:AF:17:3A:64:06:00:C8:15:
	10263	2023-04-26 06:51:25.450 [WARN ] [al.protocolv5.UnknownResponseHandler] - Unknown response, length 14: A5:01:00:10:47:00:22:67:8F:CD:F9:00:36:15:
	10365	2023-04-26 06:52:10.460 [WARN ] [al.protocolv5.UnknownResponseHandler] - Unknown response, length 29: A5:10:00:10:15:00:23:67:8F:CD:F9:02:01:3C:96:0E:00:F9:08:00:00:AF:17:3A:64:06:00:62:15:
	10728	  at org.openhab.binding.lswlogger.internal.protocolv5.ExtractorsBuilder.lambda$1(ExtractorsBuilder.java:38) ~[?:?]
	10729	  at org.openhab.binding.lswlogger.internal.protocolv5.AbstractDataResponseHandler.lambda$0(AbstractDataResponseHandler.java:46) ~[?:?]
	10731	  at org.openhab.binding.lswlogger.internal.protocolv5.AbstractDataResponseHandler.extract(AbstractDataResponseHandler.java:46) ~[?:?]
	10732	  at org.openhab.binding.lswlogger.internal.protocolv5.AbstractDataResponseHandler.handle(AbstractDataResponseHandler.java:37) ~[?:?]
	10733	  at org.openhab.binding.lswlogger.internal.protocolv5.ResponseDispatcher.accept(ResponseDispatcher.java:32) ~[?:?]
	10734	  at org.openhab.binding.lswlogger.internal.protocolv5.states.ReadingResponseState$ReadingHandler.onRead(ReadingResponseState.java:70) ~[?:?]
	10736	  at org.openhab.binding.lswlogger.internal.protocolv5.states.ReadingResponseState$ReadingHandler.run(ReadingResponseState.java:63) ~[?:?]
	10737	  at org.openhab.binding.lswlogger.internal.protocolv5.states.StateMachine$MetaRunnableWrapper.handle(StateMachine.java:142) ~[?:?]
	10738	  at org.openhab.binding.lswlogger.internal.protocolv5.states.StateMachine.run(StateMachine.java:87) ~[?:?]

Piotr_Bojko · April 27, 2023, 9:38am

I’ve seen your ticket on github - will check in a day or two.

Straits_PL · April 28, 2023, 6:13am

Yes. This was a firmware issue. If you want to fix it, you need to contact support customerservice@solarmanpv.com and ask them to upload the firmware ME_08_2791_2.06 or other appropriate one because in new firmware there is a bug causing incorrect responses on port 8899.

It took me almost 2 months to find someone who knew what I was talking about. Officially, it is impossible to go back to the older version of firmware. It is possible that after my signals they will improve something in the firmware and the new firmware will communicate correctly on port 8899, but there is no certainty.

gratteavecsapatte · April 28, 2023, 8:55am

Hello I think I have the same problem on a WIFI USB datalogger serial number 236******* on a ZCS Azzurro 1PH 5000TLM-V3 inverter

gratteavecsapatte · April 28, 2023, 8:58am

The information about my inverter does not appear and the real-time production information is incorrect and changes randomly every day

gratteavecsapatte · April 28, 2023, 9:00am

I just sent an email with my problem and a screenshot, I hope to get an answer.
I asked them for working firmware.
Fingers crossed.

ramponis · May 4, 2023, 12:09pm

Hi gratteavecsapatte,

I have this version:

Do I need to ask for a firmware upgrade?
Can I ask you what have you sent in the request email to the customer service?

Thank you

fcela · May 14, 2023, 3:22pm

Hi Piotr,

I have installed SOFAR HYD 10KTL-3PH-PRO inverter and Wifi Logger SN23xxx.
I have managed to get only Online (ON) and Operating state (grid connected) from channels till now.
No Active/reactive power is coming into my openhab items.

My Logger module version is LSW3_15_XXXX_1.68.

My debug info when suspend / enabled thing:

and following:
023-05-14 16:38:01.952 [DEBUG] [ernal.protocolv5.states.StateMachine] - Taken state Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Reading system info response]]]]]]] to pr
2023-05-14 16:38:01.953 [DEBUG] [ernal.protocolv5.states.StateMachine] - Entering Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Reading system info response]]]]]]]
2023-05-14 16:38:01.953 [DEBUG] [swlogger.internal.connection.Channel] - Consuming messages, buffers 3 messages 0
2023-05-14 16:38:01.953 [DEBUG] [otocolv5.states.ReadingResponseState] - No message to read, trying to schedule next read or switching to next state
2023-05-14 16:38:01.954 [DEBUG] [ernal.protocolv5.states.StateMachine] - Trying to schedule task in 15 SECONDS during state Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Re]]]
2023-05-14 16:38:01.954 [DEBUG] [ernal.protocolv5.states.StateMachine] - Leaving Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Reading system info response]]]]]]]
2023-05-14 16:38:01.954 [DEBUG] [ernal.protocolv5.states.StateMachine] - Waiting for state to process
2023-05-14 16:38:16.954 [DEBUG] [ernal.protocolv5.states.StateMachine] - Taken state Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Reading system info response]]]]
2023-05-14 16:38:16.955 [DEBUG] [ernal.protocolv5.states.StateMachine] - Entering Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Reading system info response]]]]]]]
2023-05-14 16:38:16.955 [DEBUG] [swlogger.internal.connection.Channel] - Consuming messages, buffers 3 messages 0
2023-05-14 16:38:16.955 [DEBUG] [otocolv5.states.ReadingResponseState] - No message to read, trying to schedule next read or switching to next state
2023-05-14 16:38:16.956 [DEBUG] [ernal.protocolv5.states.StateMachine] - Leaving Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Wrapper [Reading system info response]]]]]]]]
2023-05-14 16:38:16.956 [DEBUG] [ernal.protocolv5.states.StateMachine] - Waiting for state to process
2023-05-14 16:38:16.956 [DEBUG] [ernal.protocolv5.states.StateMachine] - Taken state Sending grid info request to process
2023-05-14 16:38:16.957 [DEBUG] [ernal.protocolv5.states.StateMachine] - Entering Sending grid info request
2023-05-14 16:38:16.957 [DEBUG] [ernal.protocolv5.states.StateMachine] - Leaving Sending grid info request
2023-05-14 16:38:16.958 [DEBUG] [ernal.protocolv5.states.StateMachine] - Waiting for state to process
2023-05-14 16:38:16.958 [DEBUG] [ernal.protocolv5.states.StateMachine] - Taken state Reaidng grid info response to process
2023-05-14 16:38:16.958 [DEBUG] [ernal.protocolv5.states.StateMachine] - Entering Reaidng grid info response
2023-05-14 16:38:16.959 [DEBUG] [swlogger.internal.connection.Channel] - Consuming messages, buffers 3 messages 0
2023-05-14 16:38:16.959 [DEBUG] [otocolv5.states.ReadingResponseState] - No message to read, trying to schedule next read or switching to next state
2023-05-14 16:38:16.959 [DEBUG] [ernal.protocolv5.states.StateMachine] - Trying to schedule task in 15 SECONDS during state Reaidng grid info response
2023-05-14 16:38:16.959 [DEBUG] [ernal.protocolv5.states.StateMachine] - Leaving Reaidng grid info response
2023-05-14 16:38:16.959 [DEBUG] [ernal.protocolv5.states.StateMachine] - Waiting for state to process
2023-05-14 16:38:19.156 [DEBUG] [swlogger.internal.connection.Channel] - Received 29 bytes
2023-05-14 16:38:19.157 [DEBUG] [swlogger.internal.connection.Channel] - Listening for data, buffers 3 messages 1
2023-05-14 16:38:24.837 [DEBUG] [swlogger.internal.connection.Channel] - Received 14 bytes
2023-05-14 16:38:24.838 [DEBUG] [swlogger.internal.connection.Channel] - Listening for data, buffers 2 messages 2
2023-05-14 16:38:31.959 [DEBUG] [ernal.protocolv5.states.StateMachine] - Taken state Wrapper [Reaidng grid info response] to process
2023-05-14 16:38:31.960 [DEBUG] [ernal.protocolv5.states.StateMachine] - Entering Wrapper [Reaidng grid info response]
2023-05-14 16:38:31.960 [DEBUG] [swlogger.internal.connection.Channel] - Consuming messages, buffers 1 messages 2
2023-05-14 16:38:31.960 [DEBUG] [otocolv5.states.ReadingResponseState] - Trying to read a message
2023-05-14 16:38:31.961 [WARN ] [al.protocolv5.UnknownResponseHandler] - Unknown response, length 29: A5:10:00:10:15:00:7F:74:E0:C1:8D:02:01:FC:F8:02:00:41:28:00:00:5E:F9:5D:64:05:00:D5:15:
2023-05-14 16:38:31.961 [DEBUG] [ternal.protocolv5.ResponseDispatcher] - Handler class org.openhab.binding.lswlogger.internal.protocolv5.UnknownResponseHandler matched response
2023-05-14 16:38:31.962 [DEBUG] [otocolv5.states.ReadingResponseState] - Trying to read a message
2023-05-14 16:38:31.962 [WARN ] [al.protocolv5.UnknownResponseHandler] - Unknown response, length 14: A5:01:00:10:47:00:80:74:E0:C1:8D:00:7A:15:
2023-05-14 16:38:31.963 [DEBUG] [ternal.protocolv5.ResponseDispatcher] - Handler class org.openhab.binding.lswlogger.internal.protocolv5.UnknownResponseHandler matched response
2023-05-14 16:38:31.963 [DEBUG] [otocolv5.states.ReadingResponseState] - No message to read, trying to schedule next read or switching to next state
2023-05-14 16:38:31.963 [DEBUG] [ernal.protocolv5.states.StateMachine] - Trying to schedule task in 15 SECONDS during state Wrapper [Reaidng grid info response]
2023-05-14 16:38:31.964 [DEBUG] [ernal.protocolv5.states.StateMachine] - Leaving Wrapper [Reaidng grid info response]
2023-05-14 16:38:31.964 [DEBUG] [ernal.protocolv5.states.StateMachine] - Waiting for state to process
2023-05-14 16:38:46.964 [DEBUG] [ernal.protocolv5.states.StateMachine] - Taken state Wrapper [Wrapper [Reaidng grid info response]] to process
2023-05-14 16:38:46.965 [DEBUG] [ernal.protocolv5.states.StateMachine] - Entering Wrapper [Wrapper [Reaidng grid info response]]
2023-05-14 16:38:46.965 [DEBUG] [swlogger.internal.connection.Channel] - Consuming messages, buffers 3 messages 0
2023-05-14 16:38:46.966 [DEBUG] [otocolv5.states.ReadingResponseState] - No message to read, trying to schedule next read or switching to next state
2023-05-14 16:38:46.966 [DEBUG] [ernal.protocolv5.states.StateMachine] - Trying to schedule task in 15 SECONDS during state Wrapper [Wrapper [Reaidng grid info response]]
2023-05-14 16:38:46.966 [DEBUG] [ernal.protocolv5.states.StateMachine] - Leaving Wrapper [Wrapper [Reaidng grid info response]]
2023-05-14 16:38:46.966 [DEBUG] [ernal.protocolv5.states.StateMachine] - Waiting for state to process
2023-05-14 16:40:43.782 [DEBUG] [ernal.protocolv5.states.StateMachine] - Taken state Wrapper [Wrapper [Wrapper [Reaidng grid info response]]] to process
2023-05-14 16:40:43.783 [DEBUG] [ernal.protocolv5.states.StateMachine] - Entering Wrapper [Wrapper [Wrapper [Reaidng grid info response]]]
2023-05-14 16:40:43.783 [DEBUG] [swlogger.internal.connection.Channel] - Consuming messages, buffers 3 messages 0
2023-05-14 16:40:43.783 [DEBUG] [otocolv5.states.ReadingResponseState] - No message to read, trying to schedule next read or switching to next state
2023-05-14 16:40:43.784 [DEBUG] [ernal.protocolv5.states.StateMachine] - Leaving Wrapper [Wrapper [Wrapper [Reaidng grid info response]]]
2023-05-14 16:40:43.784 [DEBUG] [ernal.protocolv5.states.StateMachine] - Waiting for state to process
2023-05-14 16:40:43.784 [DEBUG] [ernal.protocolv5.states.StateMachine] - Taken state Sending energy totals request to process
2023-05-14 16:40:43.784 [DEBUG] [ernal.protocolv5.states.StateMachine] - Entering Sending energy totals request
2023-05-14 16:40:43.785 [DEBUG] [ernal.protocolv5.states.StateMachine] - Leaving Sending energy totals request
2023-05-14 16:40:43.785 [DEBUG] [ernal.protocolv5.states.StateMachine] - Waiting for state to process
2023-05-14 16:40:43.785 [DEBUG] [ernal.protocolv5.states.StateMachine] - Taken state Reading energy totals response to process
2023-05-14 16:40:43.786 [DEBUG] [ernal.protocolv5.states.StateMachine] - Entering Reading energy totals response
2023-05-14 16:40:43.786 [DEBUG] [swlogger.internal.connection.Channel] - Consuming messages, buffers 3 messages 0
2023-05-14 16:40:43.786 [DEBUG] [otocolv5.states.ReadingResponseState] - No message to read, trying to schedule next read or switching to next state
2023-05-14 16:40:43.787 [DEBUG] [ernal.protocolv5.states.StateMachine] - Trying to schedule task in 15 SECONDS during state Reading energy totals response
2023-05-14 16:40:43.787 [DEBUG] [ernal.protocolv5.states.StateMachine] - Leaving Reading energy totals response
2023-05-14 16:40:43.787 [DEBUG] [ernal.protocolv5.states.StateMachine] - Waiting for state to process
2023-05-14 16:40:45.800 [DEBUG] [swlogger.internal.connection.Channel] - Received 29 bytes
2023-05-14 16:40:45.800 [DEBUG] [swlogger.internal.connection.Channel] - Listening for data, buffers 3 messages 1
2023-05-14 16:40:58.787 [DEBUG] [ernal.protocolv5.states.StateMachine] - Taken state Wrapper [Reading energy totals response] to process
2023-05-14 16:40:58.788 [DEBUG] [ernal.protocolv5.states.StateMachine] - Entering Wrapper [Reading energy totals response]
2023-05-14 16:40:58.788 [DEBUG] [swlogger.internal.connection.Channel] - Consuming messages, buffers 2 messages 1
2023-05-14 16:40:58.788 [DEBUG] [otocolv5.states.ReadingResponseState] - Trying to read a message
2023-05-14 16:40:58.789 [DEBUG] [otocolv5.AbstractDataResponseHandler] - Trying to extract message, length 29 bytes
2023-05-14 16:40:58.789 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.IllegalArgumentException: newPosition > limit: (36 > 29)

   at java.nio.Buffer.createPositionException(Buffer.java:318) ~[?:?]*

   at java.nio.Buffer.position(Buffer.java:293) ~[?:?]*

   at java.nio.ByteBuffer.position(ByteBuffer.java:1094) ~[?:?]*

   at org.openhab.binding.lswlogger.internal.protocolv5.ExtractorsBuilder.lambda$1(ExtractorsBuilder.java:38) ~[?:?]*

   at org.openhab.binding.lswlogger.internal.protocolv5.AbstractDataResponseHandler.lambda$0(AbstractDataResponseHandler.java:46) ~[?:?]*

   at java.util.ArrayList.forEach(ArrayList.java:1541) ~[?:?]*

   at org.openhab.binding.lswlogger.internal.protocolv5.AbstractDataResponseHandler.extract(AbstractDataResponseHandler.java:46) ~[?:?]*

   at org.openhab.binding.lswlogger.internal.protocolv5.AbstractDataResponseHandler.handle(AbstractDataResponseHandler.java:37) ~[?:?]*

   at org.openhab.binding.lswlogger.internal.protocolv5.ResponseDispatcher.accept(ResponseDispatcher.java:32) ~[?:?]*

   at org.openhab.binding.lswlogger.internal.protocolv5.states.ReadingResponseState$ReadingHandler.onRead(ReadingResponseState.java:70) ~[?:?]*

   at org.openhab.binding.lswlogger.internal.connection.Channel.read(Channel.java:124) ~[?:?]*

   at org.openhab.binding.lswlogger.internal.protocolv5.states.ReadingResponseState$ReadingHandler.run(ReadingResponseState.java:63) ~[?:?]*

   at org.openhab.binding.lswlogger.internal.protocolv5.states.StateMachine$MetaRunnableWrapper.handle(StateMachine.java:142) ~[?:?]*

   at org.openhab.binding.lswlogger.internal.protocolv5.states.StateMachine.run(StateMachine.java:87) ~[?:?]*

   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]*

   at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]*

   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]*

   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]*

   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]*

   at java.lang.Thread.run(Thread.java:829) [?:?]*

2023-05-14 16:42:36.894 [DEBUG] [swlogger.internal.connection.Channel] - Received 14 bytes
2023-05-14 16:42:36.894 [DEBUG] [swlogger.internal.connection.Channel] - Listening for data, buffers 2 messages 1
2023-05-14 16:44:36.936 [DEBUG] [swlogger.internal.connection.Channel] - Received 14 bytes
2023-05-14 16:44:36.937 [DEBUG] [swlogger.internal.connection.Channel] - Listening for data, buffers 1 messages 2
2023-05-14 16:45:43.785 [DEBUG] [swlogger.internal.connection.Channel] - Received -1 bytes
2023-05-14 16:45:43.786 [DEBUG] [swlogger.internal.connection.Channel] - Listening for data, buffers 0 messages 3

My logger screen:

Any hint?
Thank you.
Marek.