Warmwater set target temperature

[jumahrauf]

Hello,
I am using 2024.10.5-Beta with luxtronik firmware V3.90.1.

Actually I am not able to set the warmwater target temperature.
Where can I see in a log what the current problem is?

[rhammen]

Settings --> System --> Logs.
Then, using the search-bar at the top of the page, search for "luxtronik"

[jumahrauf]

Logger: py.warnings
Quelle: custom_components/luxtronik2/coordinator.py:121
Integration: Luxtronik
Erstmals aufgetreten: 6. Oktober 2024 um 20:03:47 (2 Vorkommnisse)
Zuletzt protokolliert: 10:20:07

/config/custom_components/luxtronik2/coordinator.py:121: RuntimeWarning: coroutine 'DataUpdateCoordinator.async_request_refresh' was never awaited self.async_request_refresh()

[blue-bean]

In my case (SWCV92H3) with firmware 3.90.1 the target temperature is 49° and the coverage temperatur of the heat pump is shown as 75° (at the control panel). In HA the target temperature is then shown with 75°.
Maybe the wrong parameter ID is used?
In the list of parameters there exist
2: Celsius("ID_Einst_BWS_akt", True),
and
105: Celsius("ID_Soll_BWS_akt", True),

The fixed 75° for the coverage temperature seems to be a bug in the 3.90.1. Usally this value should be the same as the target temperatur.

Attached the temperatures in the control panel - with 3.90.1 the second one is shown with 75°, in HA then the hot water target temperature is then shown with 75° without possibility to change (the target temperature in the panel - the first one - is still 49°). If you want to change the target temperature you change the first one, the second one change automatically to the same temperature.

[rhammen]

When I create a "Entities Card" tile for "DHW Target"on a dashboard, and modify its value, I can observe that the value is changed on the heatpump.
So for me setting the temperature still works OK.
I am using firmware V3.79.

Note: I do also get the warning " /config/custom_components/luxtronik2/coordinator.py:121: RuntimeWarning: coroutine 'DataUpdateCoordinator.async_request_refresh' was never awaited self.async_request_refresh() ", but as I said, the value is still correctly changed on the heatpump. So the warning does not mean it does not work.

This, combined with the post by @blue-bean suggests that the problem that the may be in the 3.90.1 firmware and not in this luxtronik integration.

Or are you suggesting that starting with V3.90.1 the luxtronik behavior changed, and that starting with that version the water temperature should be changed by changing
105: Celsius("ID_Soll_BWS_akt", True),
instead of
2: Celsius("ID_Einst_BWS_akt", True) ?
Did you try writing parameter 105: Celsius("ID_Soll_BWS_akt", True), and does that change the hot water temperature on the heatpump?

[blue-bean]

Did you try writing parameter 105: Celsius("ID_Soll_BWS_akt", True), and does that change the hot water temperature on the heatpump?

No, i don't know how to do this.
Did you try to set hot target temperature by 105: Celsius("ID_Soll_BWS_akt", True) using firmware 3.79?

[jumahrauf]

seems like with firmware 3.90 the accessability is kind of limited.
could somebody check i he can set the sensor "luxtronik_331009_0996_dhw_target_temperature"?

[blue-bean]

seems like with firmware 3.90 the accessability is kind of limited.

Not 3.90.0, but 3.90.1

[jumahrauf]

@blue-bean got now the same phanomenon with the target Temperaturen. I turned of the whole heatpump and after 5 minutes turned it one again. Target temperaturen was then set to 75°C

Did you add a new sensor according to the discussion you linked?

[blue-bean]

No, i downgraded to 3.90.0 and reported this behaviour to AIT.

[jumahrauf]

Do you have a Link for the 3.90 Firmware?

[rhammen]

Did you try writing parameter 105: Celsius("ID_Soll_BWS_akt", True), and does that change the hot water temperature on the heatpump?
Did you try to set hot target temperature by 105: Celsius("ID_Soll_BWS_akt", True) using firmware 3.79?

I have changed (see below) "ID_Soll_BWS_akt" from within HA, but this does not result in a change of the "DHW target" entity (="ID_Einst_BWS_akt").
Note: I am using FW 3.79.
Changing "ID_Einst_BWS_akt" in the same way does result in a change of "DHW target" entity , so the procedure to write values to the Luxtronik seems to work OK.

No, i don't know how to do this.

Go to Developer Tools-->Actions

Action = Luxtronik: write
Action Data =
parameter: ID_Soll_BWS_akt
value: <desired target temperature, e.g. 50>

[Kars-de-Jong]

I just investigated this too, it looks like we should use ID_Soll_BWS_akt instead of ID_Einst_BWS_akt to set the target temperature.

ID_Einst_BWS_akt is not normally settable by the user, it is the temperature that can be reached by using the compressor only. I bet that if you set ID_Einst_BWS_akt to 50 and ID_Soll_BWS_akt to 58 and then heat using the second heat source, it will go up to 58.

So I guess the integration should be modified to set and read ID_Soll_BWS_akt only, and leave ID_Einst_BWS_akt alone (or maybe display it as a separate entity).

I have always wondered why the target temperature displayed in the RBE or on the heat pump did not match with the settting in Home Assistant, this explains it.

[blue-bean]

Go to Developer Tools-->Actions

Action = Luxtronik: write Action Data = parameter: ID_Soll_BWS_akt value: <desired target temperature, e.g. 50>

I've tested this with my system (HA 2024.9.3, Luxtronik integration 2024.09.30, firmware WP: 3.90.0-12065):
setting ID_Soll_BWS_akt changes the value of the target temperature correctly in the control panel of the WP. No problems.

[rhammen]

@Kars-de-Jong @blue-bean
Ok, based on your comments I understood I tested something slightly different than you did.
So I now modified again ID_Soll_BWS_akt from within HA, and I checked the temperature settings on the heatpump.
Indeed, the first value "Wunschwert" changes to the value I set for ID_Soll_BWS_akt .
I noticed however that on the heatpump, I cannot set both values to different temperatures. When I change one, and press OK, the other temperature also changes. This is also what blue-bean mentioned.
This begs the question: if you change only ID_Soll_BWS_akt (from within HA), does the heatpump indeed use this temperature as the target Hot Water temperature? Or does it use the temperature from ID_Einst_BWS_akt?
I will test this overnight, and report back on what happens at my system (FW 3.79).
Can you confirm that with the Firmware versions you are using, only changing ID_Soll_BWS_akt from HA, and no changes on the Heatpump itself, indeed results in the heatpump warming the water to ID_Soll_BWS_akt ?

[blue-bean]

I can confirm (HA 2024.9.3, Luxtronik integration 2024.09.30, firmware WP: 3.90.0-12065) that changing ID_Soll_BWS_akt from HA results in an identically change of the ID_Einst_BWS_akt value - and the heatpump warming the water to ID_Soll_BWS_akt.
This should also works with 3.90.1 firmware but there the ID_Einst_BWS_akt value seems to be fixed at 75° (see above, maybe an error, i've wrote to the AIT support).

[rhammen]

Results of my test with FW3.79
I set ID_Soll_BWS_akt = 51 from HA.
ID_Einst_BWS_akt is then NOT automatically changed, and remained at 53.
On the heatpump, the top temperature is 51 and the bottom temperature is 53.
The water is heated to 53, so to ID_Einst_BWS_akt.

So with FW3.79, still ID_Einst_BWS_akt needs to be used (as does the 2024.10.5-Beta luxtronik integration)
This means any change in the integration to use ID_Soll_BWS_akt instead of the currently used ID_Einst_BWS_akt should be firmware version dependant (>= .90)

[Kars-de-Jong]

OK, after all your observations I think what we should do is set both values to the same value, which is what happens when you change the temperature using the heat pump menu.

ID_Soll_BWS_akt should be set because that is shown on the display, and maybe FW versions >= 90 only look at that value to determine the target.
ID_Einst_BWS_akt should be set because that is what is used as the actual target temperature (at least for older firmware).

Based on the documentation: ID_Einst_BWS_akt is the temperature that heat pump will try to reach. If it is set lower than ID_Soll_BWS_akt, it will stop when that value has been reached. If it is set higher or equal to ID_Soll_BWS_akt, the compressor will try to reach that temperature. I think ID_Einst_BWS_akt should never be set higher than ID_Soll_BWS_akt.

The English manual says this about it:

NOTICE
If a domestic hot water temperature is set which cannot be attained, the heat pump will initially switch to “Error high pressure”. This is followed by a self-resetting fault (If heating is required, this will also be operated). After 2 hours have passed, the domestic hot water preparation starts again. Nevertheless, the program of the heating and heat pump regulator automatically lowers the setpoint value for this by an initial 1 °C. If this setpoint temperature cannot be attained either, the process is repeated until a temperature can be attained.
The set desired value remains unaffected and is displayed unchanged.

So the set point that is lowered automatically by the controller is ID_Einst_BWS_akt, and this also explains the observed behaviour. It also suggests however that it will try to reach the temperature setpoint using the second heat source if needed.

[blue-bean]

New luxtronik firmware v.3.90.2-12457 by Apha Innotec.
Here again the ID_Soll_BWS_akt has to be used to change the target temperature for hot water.
ID_Einst_BWS_akt has the same value as ID_Soll_BWS_akt after update (in my case both values are 49°).
Then i've increased ID_Soll_BWS_akt at the WP to 50°. At this moment the value for ID_Einst_BWS_akt ("Deckung WP") stayed at 49°, but changed after next hot water preparation to the temperature which is reached using the WP (in this case 50°).
After that i decreased the value of ID_Soll_BWS_akt to 49° this value was reached after next hot water preparation. The value ID_Einst_BWS_akt stays at 50°.

[jumahrauf]

I can confirm this behaviour. Right now I am using luxtronik firmware v.3.90.2-12457 with BenPru release 2024.9.30

[jumahrauf]

@blue-bean : can we somehome exchange some experiences with the newest firmware?

[stefanovich1]

HA: 2024.11.3
Integration: 2024.11.15-Beta
Luxtronik: V3.90.2

No response for ID_Einst_BWS_akt
"Deckung Wärmepumpe" is fixed at 75°C and cannot be changed.
Neither via HA nor via Interface at Heatpump

Correct response for ID_Soll_BWS_akt
TBWsoll is adjusted as demanded

[narendrak17]

Yes, I have similar behaviour as Stefan but the integration version is stable one. (2024.9.30)

Coverage HP (ID_Einst_BWS_akt) is stuck at 75°C and can not be changed.

[hakit-de]

Confirm after update to Luxtronik: V3.90.2.

[Mehli12]

Confirm after update to Luxtronik: V3.90.2.

Means Luxtronik 3.90.2 works wirth lates stable Luxtronik 2024.11.15 and HA 2024.12.3?

[hakit-de]

Confirm after update to Luxtronik: V3.90.2.

Means Luxtronik 3.90.2 works wirth lates stable Luxtronik 2024.11.15 and HA 2024.12.3?

No, after updating the luxtronik to 3.90.2 I have the same issue. Setting hotting water results in Coverage HP (ID_Einst_BWS_akt) is stuck at 75°C.

HA 2024-11-2
Integration: 2024.9.30
Luxtronik: V3.90.2.

Using Luxtronik: write ID_Soll_BWS_akt to a value works as expected(Using integraiton of Bouni)

I guess its a combination of V3.90.2 and 2024.9.30 integration.

[blue-bean]

Because changes in this repository seems to take a long time, i've changed in my setting (luxtronik software 3.90.2, HA 2024.12.3, luxtronik 2024.09.30) the relevant definitions in const.py, number_entities_predefined.py and water_heater.py, using P0105 insteat of P0002 for hot water target temperature.
All works fine, changing the target temperature in HA gives the correct change in the WP control unit and the correct temperature after heating up.

[AJediIAm]

Because changes in this repository seems to take a long time, i've changed in my setting (luxtronik software 3.90.2, HA 2024.12.3, luxtronik 2024.09.30) the relevant definitions in const.py, number_entities_predefined.py and water_heater.py, using P0105 insteat of P0002 for hot water target temperature. All works fine, changing the target temperature in HA gives the correct change in the WP control unit and the correct temperature after heating up.

Can you make a pull request?
If you are not familiar with git, you can edit the files directly in the browser. This is what I normally do.
Others can test the changes to confirm they work. This saves BenPru some time.

[IllegalDuke]

Hello,

one point is missing in this discussion. You are talking about, that "ID_Einst_BWS_akt is the temperature that heat pump will try to reach."

But this is not fully correct.

When Smart Grid is enabled, then the heatpump will try to reach a higer temperature. This will only be shown in the ID_WEB_Einst_BWS_akt.

In my example, when I set smart grid to 4 (increased temperature working mode), then the temperatures will look like this:

ID_Einst_BWS_akt = 52,5°C
ID_Soll_BWS_akt =52,5°C
ID_WEB_Einst_BWS_akt = 57,5°C

Then the heatpump will heat the hot water to 57,5°C as described in the Luxtronik manual in the section "Smart Grid".

57,5°C because I have the following settings in my heatpump under smart grid:

Here plus 5K is set for increase of heating water and warm water.
For smart grid state 2, the heating water will be reduced by -14K in my case.

Here is a chart from the entities - I switched from smart grid 2 to smart grid 4 and back:

ID_Einst_BWS_akt = Luxtronik Parm Einst BWS akt
ID_WEB_Einst_BWS_akt = Luxtronik Web Einst BWS akt
luxtronik_260621_0275_flow_out_temperature_target = Heiz Rücklauf Soll Temperatur

Please consider this, when updating this repository. I think it is really relevant to show the real target temperature for hot water somewhere.

Thank you.

[blue-bean]

@IllegalDuke
Thank you. It's correct that the discussion here concerns the standard temperature for warm water.
By the way: do you know the code for ID_WEB_Einst_BWS_akt so we can define it in the integration? Have you some additional changes that you can share?

PS: which Luxtronik version do you use ? And how do you have realized switching the IN5 and IN6?

[IllegalDuke]

Sorry for the long text and thank you for your help :-)

@blue-bean

Right now I am using Luxtronik version V3.86.1. Because 3.87 had some bugs and I didn't try newer ones..

What code exactly do you mean? I just know:
TCP command 3004 - "get calculated":

Number	Internal ID	Internal Text	category	conversion	unit	type	notes	translation
18	ID_WEB_Einst_BWS_akt	Text_BW_Soll	temperature	10	°C			Warmwasser-Soll
31	ID_WEB_EVUin	Text_EVU	input					EVU
185	ID_WEB_HZIO_EVU2	Text_EVU2	input					EVU 2

EVU is the Input 5 at the Luxtronik PCB (for my heat pump according manual)
EVU2 is the Input 6 at the Luxtronik PCB (for my heat pump according manual)

manual: https://mw.ait-group.net/files/docs/EN/A0220/83055400.pdf
Page 38:

And the function of Smart Grid is explained on page 36 and 37:

Standard is EVU at Input5 and Smart Grid deactivated (standard for my north bavarian region "Oberfranken" ❤).

With my photovoltaik installed I searched a way to easily buffer some energy in my hot water tank and my floor heating.
I first wanted to adjust values up and down by ioBroker (now HomeAssistant), but the AIT contact had the proposal to use the feature Smart Grid.
So I attached the Luxtronik Input 5 and 6 to my KNX actuator (MDT AKU-B2UP.03) and the original EVU-contact to one of the binary inputs of this actuator. I parametrized this actuator that it will set the Input5 and Input 6 to EVU state when EVU contact is triggered. If no EVU ist demanded, it will work with my photovoltaik and heat up the warm water and floor heating when enough sun is shining.

Normally you would use Smart Grid states 1 = EVU 3 = normal and 4 = increased.

I am using all 4 states of smart grid to press as much energy as possible into the heat pump.
I achieved this by increasing the target heating curve for floor heating water tank by 14K (attention: not the MK1 heating curve!) and set Smart Grid state 2 = decreased as my normal level with the value decrease heating = -14K.

So, normally state 2 is active. When PV is producing more energy, I will fire Smart grid state 3 to heat up the floor heating water more and with that I am increasing the indoor target temperatures of my room thermostats by 0.5K.

When even more energy is available, I will fire Smart grid state 4 and with that a heating of water is started and the hot water will be overheated by 5K.

You can set this by adjusting these parameters in your Luxtronik - see manual page 62:

The result of PV-Energy-Use is this: (without battery, just the use of Smart Grid with my heatpump!)

Further values which are important from my point of view for visualization purposes and control logics are:

Group calculations - 3004:

Number	Internal ID	Internal Text	category	conversion	unit	type	notes	translation
17	ID_WEB_Temperatur_TBW	Text_BW_Ist	temperature	10	°C			Warmwasser-Ist
18	ID_WEB_Einst_BWS_akt	Text_BW_Soll	temperature	10	°C			Warmwasser-Soll
21	ID_WEB_Temperatur_TFB1	Text_MK1_Vorlauf	temperature	10	°C			Mischkreis1-Vorlauf
22	ID_WEB_Sollwert_TVL_MK1	Text_MK1VL_Soll	temperature	10	°C			Mischkreis1 VL-Soll
31	ID_WEB_EVUin	Text_EVU	input					EVU
38	ID_WEB_BUPout	Text_BUP	output					BUP
39	ID_WEB_HUPout	Text_HUP	output					HUP
40	ID_WEB_MA1out	Text_Mischer1Auf	output					Mischer 1 Auf
41	ID_WEB_MZ1out	Text_Mischer1Zu	output					Mischer 1 Zu
43	ID_WEB_VBOout	Text_Ventil_BOSUP	output					Ventil.-BOSUP
44	ID_WEB_VD1out	Text_Verdichter1	output					Verdichter 1
46	ID_WEB_ZIPout	Text_ZIP_AUSGANG	output					ZIP
47	ID_WEB_ZUPout	Text_ZUP	output					ZUP
48	ID_WEB_ZW1out	Text_ZWE1	output					ZWE 1
185	ID_WEB_HZIO_EVU2	Text_EVU2	input					EVU 2

Group parameters - 3003:

Number	Internal ID	Internal Text	conversion	Notes
3	ID_Ba_Hz_akt
4	ID_Ba_Bw_akt

These two parameters are used to set the mode of operation of the heat pump heating circuit and warm water, possible values are "Automatic", "Second heatsource", "Party", "Holidays", "Off". Are they already implemented? On the first sight i couldn't find them... or are they somewhere hidden?

It would be perfect, if all these parameters in the two tables could be implemented, because then I could reuse my heat pump chart and I think that these values are important for others out there, too:

[karlNAPP-design]

@IllegalDuke

Amazing picture from your heat pump card!!!
Do you have it like this in Homeassistant? If yes how have you realized this? Never seen something like this in Homeassistant?

Thanks for your answer.

[IllegalDuke]

@karlNAPP-design
I used this overview in IOBroker and now I am implementing this in Homeassistant.
I am using a panel card and added state labels and state icons.