Add option for RBE functionality

[JarnoHilverts]

Hi all,

This is the first issue I’m opening, hopefully everything is described clearly.

In the last few days, I’ve been working to control the RBE that’s installed in the kitchen using this integration. I’ve managed to do this, but I’m not completely satisfied with the code, so the solution still seems a bit messy.

Parameter 1148 is used to select the desired target temperature from the RBE. I’ve tested this using the service to adjust the temperature by modifying parameter 1148. It’s important that the value is sent without a decimal. Therefore, 21.5 degrees is 215.

Service call:

action: luxtronik2.write
data:
  parameter: Unknown_Parameter_1148
  value: 215

Below is a description of how this has been implemented in the code. Could someone help further develop this to create a pull request, to further implement this functionality into this integration?
Personally, I don't know how the integration handles it when no RBE is connected to the system. Maybe this can be caught somewhere, or someone else can test this.

Files changed:

• Const.py
• Climate.py

In the Const.py file the parameter 1148 needs to be added:

P1148_HEATING_TARGET_TEMP_RBE: Final = "parameters.Unknown_Parameter_1148"

The climate.py file the THERMOSTATS for heating needs to be modified so that the actual desired temperature matches that of the RBE. This was done by commenting out the luxtronik_key_target_temperature. Additionally, the code for writing the target_temperature (parameter 1148) has been modified. Because no decimal number is sent, the value is multiplied by 10. The rest of the code is similar to the code in the water_heater.py:

THERMOSTATS: list[LuxtronikClimateDescription] = [
    LuxtronikClimateDescription(
        key=SensorKey.HEATING,
        hvac_modes=[HVACMode.HEAT, HVACMode.OFF],
        hvac_mode_mapping=HVAC_MODE_MAPPING_HEAT,
        hvac_action_mapping=HVAC_ACTION_MAPPING_HEAT,
        preset_modes=[PRESET_NONE, PRESET_AWAY, PRESET_BOOST],
        supported_features=ClimateEntityFeature.PRESET_MODE
        | ClimateEntityFeature.TURN_OFF  # noqa: W503
        | ClimateEntityFeature.TURN_ON  # noqa: W503
        | ClimateEntityFeature.TARGET_TEMPERATURE,  # noqa: W503
        luxtronik_key=LuxParameter.P0003_MODE_HEATING,
        # luxtronik_key_current_temperature=LuxCalculation.C0227_ROOM_THERMOSTAT_TEMPERATURE,
        luxtronik_key_target_temperature=LuxCalculation.C0228_ROOM_THERMOSTAT_TEMPERATURE_TARGET,
        # luxtronik_key_has_target_temperature=LuxParameter
        luxtronik_key_current_action=LuxCalculation.C0080_STATUS,
        luxtronik_action_active=LuxOperationMode.heating.value,
        # luxtronik_key_target_temperature_high=LuxParameter,
        # luxtronik_key_target_temperature_low=LuxParameter,
        luxtronik_key_correction_factor=LuxParameter.P0980_HEATING_ROOM_TEMPERATURE_IMPACT_FACTOR,
        luxtronik_key_correction_target=LuxParameter.P0001_HEATING_TARGET_CORRECTION,
        icon_by_state=LUX_STATE_ICON_MAP,
        temperature_unit=UnitOfTemperature.CELSIUS,
        visibility=LuxVisibility.V0023_FLOW_IN_TEMPERATURE,
        device_key=DeviceKey.heating,
    ),

async def async_set_temperature(self, **kwargs: Any) -> None:
        """Set new target temperature."""
        value = kwargs.get(ATTR_TEMPERATURE)
        lux_key = LuxParameter.P1148_HEATING_TARGET_TEMP_RBE
        data: LuxtronikCoordinatorData | None = await self.coordinator.async_write(
            lux_key.split(".")[1], int(value * 10)
        )
        self._handle_coordinator_update(data)

Let me know what you think about it!

[AJediIAm]

Hi @JarnoHilverts

Thanks for your contribution. I have an RBE myself so I will test your change once I get back.
Development has been a bit slow but we hope to pick up the pace a bit. Do you need help with creating a pull request? It will ensure you get the credits and be remembered forever as a contributor to this integration.
I can also create the pull requests for you if you want and mention you in the release notes.

[JarnoHilverts]

Hey @AJediIAm,

It's been a while — thank you for your response. I’ve created a pull request. Hopefully, thit will suffice.
Please let me know if everything is in order. Don’t hesitate to reach out if you have any questions.

Best of luck with the testing!

[rhammen]

@JarnoHilverts Can you please test 2025.9.6-Beta, to confirm it (still) works ok after the fixes I applied?

[JarnoHilverts]

@rhammen It’s working for me. Had to delete the integration first, but after that no problems so far.

[AJediIAm]

Closing the issue as it seems to be fixed

[rhammen]

@JarnoHilverts Got a message (but seems deleted on GitHub afterwards) that your Thermostacard showed 0 C, and that you were adapting the code to fix that.
There is no need to adapt the code; you just need to specify the sensor to be used for the Room temperature when setting the integration.
So to check: I think you figured that out now, correct?

[JarnoHilverts]

Correct, figured it out. Just needed to restart the intergration after setting the right sensor.

[wiljums]

seems to be not working for me. even after reloading the integration.

[JarnoHilverts]

After choosing the right sensor, a restart of your homeassisant will help sometimes

[wiljums]

Still doesnt work. I use a RBE and the sensor selected for the current inside temp is sensor.luxtronik_280702_0137_room_thermostat_temperature_2

I cant make that field empty.

[rhammen]

Still doesnt work. I use a RBE and the sensor selected for the current inside temp is sensor.luxtronik_280702_0137_room_thermostat_temperature_2

I cant make that field empty.

You are correct, when you remove the specified "room thermostat" sensor in the integration config by pressing the X, and you don;t choose a new sensor, it does not store that. The integration currently does not support storing an empty sensor field here.
I will have a look if I can fix that in an upcoming improvement, but I believe the thermostat will (try to) use a default temperature sensor when the entry on the options screen is empty, so not sure if the end result would be really different.
Is your goal to not have any current temperature display on the thermostat, or what do you want to achieve? Can you explain why you want that?

If you change the sensor to a different sensor, you currently need to restart HA for it to take effect.
I will also try to see if I can improve that so that no manual restart is needed anymore.