Good to know.
@Firmware: The firmware on my machine is new: February 25th 2025.
Could be we have to wait for the next firmware.
There are more new registers in the buffer module:
05 Request type
…
09 Modbus request heating capacity
which I have not included in the binding yet.
If these registers work one could overheat the buffer during times with PV-excess too by using openhab.
Here you find a new version:
https://drive.google.com/file/d/1-vS99PHm0slsco_zDY1SdLOsfkiNavN2/view?usp=sharing
@heatpump: 1016 … 1019 are included
I tested writing 1018 which shows 273.15°C.
It can be written, the value is accepted and persists. I do not know what this register is supposed to do. I will try to find out if the value occurs in the log written on the usb storage.
@buffer 3006 … 3009 are included
3006 shows -0.1°C but…
I tested that 3006 can be written, the value is accepted and persists.
I changed Buffer_Request_Flow_Line_Temperature to 0.5, 2, 34 for different heating cycles. No visible changes!
If you find the time please test this version!
Good morning. I tried testing the new version. But after installing, I get the following error message:
2025-04-18 09:26:45.072 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 1 out of 3 failed when executing request (ModbusReadRequestBlueprint [slaveId=1, functionCode=READ_MULTIPLE_REGISTERS, start=3000, length=10, maxTries=3]). Will try again soon. Error was: net.wimpi.modbus.ModbusSlaveException Error Code = 2 [operation ID 0d3a21fa-36cf-491d-aaab-2afd94c394c4]
2025-04-18 09:26:45.163 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 2 out of 3 failed when executing request (ModbusReadRequestBlueprint [slaveId=1, functionCode=READ_MULTIPLE_REGISTERS, start=3000, length=10, maxTries=3]). Will try again soon. Error was: net.wimpi.modbus.ModbusSlaveException Error Code = 2 [operation ID 0d3a21fa-36cf-491d-aaab-2afd94c394c4]
2025-04-18 09:26:45.242 [ERROR] [rt.modbus.internal.ModbusManagerImpl] - Last try 3 failed when executing request (ModbusReadRequestBlueprint [slaveId=1, functionCode=READ_MULTIPLE_REGISTERS, start=3000, length=10, maxTries=3]). Aborting. Error was: net.wimpi.modbus.ModbusSlaveException Error Code = 2 [operation ID 0d3a21fa-36cf-491d-aaab-2afd94c394c4]
2025-04-18 09:26:45.242 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'modbus:lambda-buffer:ec7ae2e877:LambdaBuff' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Error with read: org.openhab.core.io.transport.modbus.internal.ModbusSlaveErrorResponseExceptionImpl: Slave responded with error=2 (ILLEGAL_DATA_ACCESS)
Maybe you can take a look and see what’s happening.
Happy Easter.
Agio
Does this only happen with the buffer (Modbus registers 3000 …) or with the heatpump (registers 1000 …) too?
My first guess: Did you switch to the new firmware? Might be that in the old firmware only registers 3000 … 3005 are supported.
My lambda has:
V1.1.0 Feb 20 2025
Thanks for the quick reply.
The error only occurs with the buffer registers. Everything seems to be fine with the heat pump.
You’re probably right that it’s due to my old firmware. I’m still on:
V1.0.2 Apr 17 2024
After Easter, I’ll try to get a newer version and test it again.
Greetings
Agio
there is a problem with the buffer channels, i use OH5
2025-04-19 11:43:11.716 [WARN ] [rest.core.internal.item.ItemResource] - Received HTTP PUT request with an invalid item name 'Lambda_Buffer_Buffer_Request_Type'.
Your firmware seems to be V0.0.7.
I suggest changing to the actual firmware before trying to use the newly added registers which were published in the new Modbus document dated 13.2.25.
You just have to write a mail to lambda, they usually update within one working day.
If your OpenHab is on 5.0.0 and Java 21 you could try to use the version compiled with J21. Do you want me to upload it to google drive?
you have to differentiate between “firmware version” and “SW version”, here we were talking about the “SW version” I assume?
SW version for me is V1.0.6 from 17.01.2025
My Environment:
Java Laufzeit
Eclipse Adoptium
21.0.6 (Temurin-21.0.6+7)
openHAB 5.0.0 Build #4565
Yes, please upload a Version for OH5 and JAVA 21, then i can test it again
Hm - no idea.
Do all of the channels of the buffer generate this warning or just
Lambda_Buffer_Buffer_Request_Type, which is one of the new registers?
Are there other errors in the log generated during the start of your openhab system?
Did you erase the old buffer thing and generate a new one?
When generating: Did you link the buffer thing to the modbus bridge?
Still: My SW version is 1.1.0. Could still be that your version 1.0.6 does not support the new registers.
I zipped the version compiled with j21:
https://drive.google.com/file/d/1a_DZbObXIAO_6FZ5NZa9-f_pQ0Dtm1s1/view?usp=sharing
Only this channel throws an error, all other things and channels work
Here ist the startup log of OH:
2025-04-19 18:33:00.873 [INFO ] [org.openhab.core.Activator ] - Starting openHAB 5.0.0 (Build #4565)
2025-04-19 18:33:02.037 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to 'Europe/Vienna'.
2025-04-19 18:33:02.062 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Location set to '48.089071900129085,13.861020576764133'.
2025-04-19 18:33:02.065 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to 'de_AT'.
2025-04-19 18:33:23.780 [INFO ] [.core.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2025-04-19 18:33:38.146 [INFO ] [e.automation.internal.RuleEngineImpl] - Rule engine started.
2025-04-19 18:33:38.865 [INFO ] [rt.modbus.internal.ModbusManagerImpl] - Modbus manager activated
2025-04-19 18:35:28.464 [WARN ] [rest.core.internal.item.ItemResource] - Received HTTP PUT request with an invalid item name 'Lambda_Buffer_Buffer_Request_Type'.
no indication that the address could not be reached
same error with your last version …
It seems that the registers 1015 … 1018 of the heatpump and 3005 … 3009 of the buffer show up in the latest ModBus document and can be accessed with the firmware version 1.1.0 delivered since February. But up to now it seems they are not serviced by the machine.
Here are all the “Heat pump” registers that can be queried without errors. There are also some undocumented registers. All with SW version 1.0.6
Thanks for mentioning the PowerHud Modbus Tester. More reliable than CASModbusScanner I was using up to now!
Do you think I should include these registers in the binding?
They might be interesting for somebody who wants to monitor the inner workings of the inverter but not for everyday users. As long as they are not published in the modbus description they might be subject to changes by lambda.
In my experience, the lambda modbus telegram changes from time to time. I have had the heat pump for about a year now and registers have been added and removed. When these undocumented registers appear in the official documentation, it will be a good time to implement them in your binding too, in my opinion. I will add these undocumented registers manually via the modbus binding until then.
By the way, I have added the register 3005 (Buffer) in OH 4.3.4 manually and there is no error message.
I received the Lambda SW/FW version V1.1.0 yesterday, and the installation of the latest version worked.
I also get the “Buffer Request Type” bad request error when installing via the GUI.
Otherwise, everything seems to be working.
Thank you very much.
Hm - in github they required me to provide an installation by scripts (in openhab-conf). With this it seems to work.
Buffer Request type shows -1 when starting openhab, I can change it to 0.
I will be away until may 3rd, afterwards I will try to solve this.
