Could you please add parameter **119** as a writable select entity to the integration?

[psstrecker-oss]

Hi @BenPru,

my Alpha Innotec heat pump exposes a writable parameter that is not yet available in the integration.

📌 Parameter details

• Parameter ID: 119
• Luxtronik name: ID_Ba_Sw_akt
• Current value (from diagnostics): "Automatic"
• Type: Select / Enum
• Writable: Yes
• Expected values:
  • 0 = Automatik
  • 1 = Aus

📌 My heat pump

• Model: Alpha Innotec LWD 50A
• Firmware: V2.89.0-12760
• Controller: Luxtronik 2.x
• Connection: UDP (Port 8889)

📌 Why this parameter is needed

This parameter controls the PV operating mode of the heat pump.
It is essential for Home Assistant users who want to integrate PV surplus control or energy‑optimized operation.

📌 Request

Please add parameter 119 (ID_Ba_Sw_akt) as a writable select entity.

Suggested entity:
select.luxtronik_pv_betriebsart

Suggested mapping:
0 = Automatik
1 = Aus

📎 Diagnostics

I have attached the full diagnostics file.
Relevant excerpt:
"119 ID_Ba_Sw_akt": "Automatic"

config_entry-luxtronik2-01K90K4Q90YVMJPHZWWMNMF4F5.json

Thanks a lot for your great work!

[AJediIAm]

Thanks for the nice change request.
I suggest to use the English entity name: "PV Operating Mode"

[psstrecker-oss]

“PV Operating Mode” sounds great.
Thanks for adding support for parameter 119 — this will help a lot with PV‑optimized operation. Much appreciated!

[rhammen]

@psstrecker-oss We currently inherit the parameter 119 from Bouni Luxtronik's library, and it has type PoolMode with the following mapping:

class PoolMode(SelectionBase):
    """PoolMode datatype, converts from an to list of PoolMode codes."""

    measurement_type = "selection"

    codes = {0: "Automatic", 2: "Party", 3: "Holidays", 4: "Off"}

Your suggestion differs from this:
Expected values:

0 = Automatik
1 = Aus

Are you sure your suggested mapping is correct?

[rhammen]

Additionally, there is parameter 881, which is listed as defining the 'Solar Mode':
881: SolarMode("ID_Einst_Solar_akt", True),

Are you sure you have the correct parameter?

[psstrecker-oss]

Thanks for the quick feedback.
I can confirm that Parameter 119 is not PoolMode on my Alpha Innotec heat pump.

The reason is simple:
My system uses the SWT input as PV‑Ready signal, and therefore the controller internally switches Parameter 119 to PV operating mode instead of Pool mode.

This is also why Heatpump24 shows:

0 = Automatik

1 = Aus

These values are read directly from the Luxtronik and match the actual PV mode configuration of the heat pump.

When PV‑Ready is enabled in the AIT controller, Parameter 119 changes its meaning and no longer represents PoolMode.
PoolMode (0/2/3/4) is only used when the SWT input is configured for pool operation, which is not the case here.

So the mapping inherited from Bouni’s library does not apply to AIT systems with PV‑Ready enabled.

Regarding Parameter 881 (SolarMode):
This parameter is for solar thermal systems, not PV. It is unrelated to the SWT/PV‑Ready configuration and therefore not connected to Parameter 119.

Conclusion:
Parameter 119 is correctly interpreted by Heatpump24 as PV operating mode, with values 0/1.
For AIT systems with PV‑Ready enabled, this is the correct mapping.

Sorry for the confusion — I’m still a beginner with all of this and currently rely a lot on Copilot to find solutions.
However, in this case I’m very sure about the details.
I took this information directly from Heatpump24, where the parameter ID is shown explicitly.
And that ID is 119.

Thanks a lot for your efforts, and have a great weekend!

[rhammen]

@psstrecker-oss Can you tell me which luxtronik parameter I can use to determine whether parameter 119 defines PV mode or Pool Mode?

[psstrecker-oss]

Good question — that’s exactly the tricky part here.

As far as I understand from my setup, the behavior of parameter 119 depends on how the SWT input is configured in the controller (pool vs PV-ready). However, I have not yet found a dedicated Luxtronik parameter that explicitly exposes this mode switch.

What I can confirm from my system:

• SWT input is configured for PV-ready
• Parameter 119 behaves as PV operating mode (0 = Automatic, 1 = Off)
• Heatpump24 reflects this correctly

What I cannot reliably answer (yet):

• A specific parameter that indicates whether SWT is in pool mode or PV mode

Maybe possible approaches:

• Check if there is a parameter related to SWT configuration or digital input mode
• Derive it indirectly (e.g. based on available value range of parameter 119 — only 0/1 vs 0/2/3/4)

If it helps, I’m happy to provide additional diagnostics or test specific parameters on my system.

Let me know what would be most useful 🙂

[rhammen]

Derive it indirectly (e.g. based on available value range of parameter 119 — only 0/1 vs 0/2/3/4)

The parameter does not tell the available value range, we can only get the current value.
The problem is that both contain ranges 0, so if 0 is selected, there is no way to know if the selector should use 0/1 or 0/2/3/4....
So I need some other way to detect how the selector should behave.
Without that, the only thing I can do is create a selector that can choose between 0/1/2/3/4:
0 = Automatic
1 = Off (PV mode)
2 = 2nd heat source (Pool mode)
3 = Holidays (Pool mode)
4 = Off (Pool mode)
And then responsibility to select (only) appropriate settings is at the user....
I am not to happy about such an approach.

Check if there is a parameter related to SWT configuration or digital input mode

Exactly :-). Somebody needs to tell me how I can determine if Parameter 119 determines Pool mode or PV mode, I don't know.
Likely this is reverse-engineering; one approach could be:

• download the diagnostics file for this integration
• disabled the PV ready mode in the heatpump
• wait at least 60 seconds
• download again a diagnostics file
• check which parameters/calculations have changed between the 2 diagnostics files, and hope there is one with a name which makes sense...
• re-enable the PV ready mode again.
• (wait 60s, download again a diagnostics file, check again...)

[rhammen]

@psstrecker-oss Are you able to execute the procedure in the previous post, so maybe we can find a way to detect which Mode (PV or Pool) parameter 119 controls?
I have just created pre-release 2026.06.12 that includes the Parameter 119 select entity: "luxtronik2_pv_mode_selector" . I put it under the Heatpump device for now, if it should be somewhere else let me know. The entity is disabled by default, you'll need to enable it manually first.

[psstrecker-oss]

Hi @rhammen,
thanks for the detailed explanation — that makes sense.
As an additional data point from my setup: I’m currently using the SWT (Comfort board) input together with a Shelly 1. I manually enabled PV-ready mode in the Luxtronik controller, and the Shelly switches the SWT input based on PV surplus.
In this configuration, the behavior is as follows:

When the Shelly activates the SWT input, the heat pump switches into PV mode
It heats domestic hot water up to a maximum of ~65°C
It then maintains the temperature with hysteresis as long as the signal is active
Once the Shelly turns off, the system returns to normal operation

So from my perspective, Parameter 119 is clearly acting as a PV mode selector in this setup.
Unfortunately, I’m currently on vacation. Once I’m back (beginning of July), I can run the procedure you described:

toggle PV-ready mode
collect and compare diagnostic files
and share the results with you

Hopefully that helps to identify a parameter or calculation that indicates whether SWT is configured for PV or pool mode.
Let me know if there’s anything specific you’d like me to pay attention to when running the tests 🙂
Best regards

[psstrecker-oss]

@psstrecker-oss Are you able to execute the procedure in the previous post, so maybe we can find a way to detect which Mode (PV or Pool) parameter 119 controls? I have just created pre-release 2026.06.12 that includes the Parameter 119 select entity: "luxtronik2_pv_mode_selector" . I put it under the Heatpump device for now, if it should be somewhere else let me know. The entity is disabled by default, you'll need to enable it manually first.

Hi @rhammen,
I now had a chance to test the new selector in practice.
From my observations on an Alpha Innotec system with PV‑ready enabled:

Parameter 119 behaves exactly as a PV operating mode selector
Available values in this configuration are effectively:

0 = Automatic
1 = Off

Switching between these values works as expected:

Automatic: the SWT input (PV‑ready signal) is evaluated
Off: the SWT input is ignored completely

When setting it to Off, the system runs fully stable and no longer reacts to the external SWT signal. This confirms that the parameter directly controls whether the PV logic is active.
Regarding detection (PV vs Pool mode):
I currently still cannot identify any dedicated Luxtronik parameter that explicitly indicates how the SWT input is configured internally.
However, based on the system behavior:

The interpretation of parameter 119 clearly depends on the internal configuration of the SWT input (pool vs PV‑ready)
This configuration does not appear to be exposed via a readable parameter (at least not an obvious one)

Your concern about ambiguity is therefore valid:

If the current value is 0, it is impossible to distinguish between the two modes using parameter 119 alone

At the moment, I see three possible approaches:

Single combined selector (0–4)
As you suggested, but with clear documentation that only a subset is valid depending on system configuration.

Configuration option in the integration
Let the user explicitly choose:

"SWT = PV‑ready"
"SWT = Pool"

Best‑effort auto‑detection (future)
Via diagnostics comparison (as you proposed), if we find a reliable indicator.

I have attached two diagnostics files (PV‑ready enabled vs. disabled) for comparison, which might help to identify a parameter that reflects the SWT configuration.
As an additional observation: Heatpump24 seems to have introduced an update recently. There, parameter 119 now exposes the following modes even in PV‑Ready configuration:

0 = Automatic
2 = Party
3 = Holidays
4 = Off

This suggests that newer firmware versions may be unifying the handling of parameter 119 across PV and Pool use cases, which could further complicate detection based on value ranges alone.

Sorry for the confusion, but it seems that Alpha Innotec has decided to handle this in a unified way.
In my Alpha Innotec app, under “PV operating mode”, I can still only choose between Automatic and Off.
Most likely, these are the effective modes for PV‑Ready operation, since in this setup the system is simply controlled via a relay that provides a “PV surplus available” signal.

config_entry-luxtronik2-01K90K4Q90YVMJPHZWWMNMF4F5.json
config_entry-luxtronik2-01K90K4Q90YVMJPHZWWMNMF4F5 (1).json

[psstrecker-oss]

@psstrecker-oss Are you able to execute the procedure in the previous post, so maybe we can find a way to detect which Mode (PV or Pool) parameter 119 controls? I have just created pre-release 2026.06.12 that includes the Parameter 119 select entity: "luxtronik2_pv_mode_selector" . I put it under the Heatpump device for now, if it should be somewhere else let me know. The entity is disabled by default, you'll need to enable it manually first.

Hi @rhammen, I now had a chance to test the new selector in practice. From my observations on an Alpha Innotec system with PV‑ready enabled:

Parameter 119 behaves exactly as a PV operating mode selector Available values in this configuration are effectively:

0 = Automatic 1 = Off

Switching between these values works as expected:

Automatic: the SWT input (PV‑ready signal) is evaluated Off: the SWT input is ignored completely

When setting it to Off, the system runs fully stable and no longer reacts to the external SWT signal. This confirms that the parameter directly controls whether the PV logic is active. Regarding detection (PV vs Pool mode): I currently still cannot identify any dedicated Luxtronik parameter that explicitly indicates how the SWT input is configured internally. However, based on the system behavior:

The interpretation of parameter 119 clearly depends on the internal configuration of the SWT input (pool vs PV‑ready) This configuration does not appear to be exposed via a readable parameter (at least not an obvious one)

Your concern about ambiguity is therefore valid:

If the current value is 0, it is impossible to distinguish between the two modes using parameter 119 alone

At the moment, I see three possible approaches:

Single combined selector (0–4) As you suggested, but with clear documentation that only a subset is valid depending on system configuration.

Configuration option in the integration Let the user explicitly choose:

"SWT = PV‑ready" "SWT = Pool"

Best‑effort auto‑detection (future) Via diagnostics comparison (as you proposed), if we find a reliable indicator.

I have attached two diagnostics files (PV‑ready enabled vs. disabled) for comparison, which might help to identify a parameter that reflects the SWT configuration. As an additional observation: Heatpump24 seems to have introduced an update recently. There, parameter 119 now exposes the following modes even in PV‑Ready configuration:

0 = Automatic 2 = Party 3 = Holidays 4 = Off

This suggests that newer firmware versions may be unifying the handling of parameter 119 across PV and Pool use cases, which could further complicate detection based on value ranges alone.

Sorry for the confusion, but it seems that Alpha Innotec has decided to handle this in a unified way. In my Alpha Innotec app, under “PV operating mode”, I can still only choose between Automatic and Off. Most likely, these are the effective modes for PV‑Ready operation, since in this setup the system is simply controlled via a relay that provides a “PV surplus available” signal.

config_entry-luxtronik2-01K90K4Q90YVMJPHZWWMNMF4F5.json config_entry-luxtronik2-01K90K4Q90YVMJPHZWWMNMF4F5 (1).json

I’m currently on vacation until the end of June, so I will only be able to continue testing and further investigation after that.
Best regards