hot water

[marplukiwi]

Checklist

• I have installed the latest release (or BETA) version of the integration and home assistant.
• I have prepared DEBUG log output (for technical issues) | In most of the cases of a technical error/issue I would have the need to ask for DEBUG log output of the integration. There is a short tutorial/guide 'How to provide DEBUG log' here
• I confirm it's really an issue | In the case that you want to understand the functionality of a certain feature/sensor Please be so kind and make use if the discussion feature of this repo (and do not create an issue) - TIA

Add a description

Watterkotte Ai1 GEO 5010.5
Hot water setting 45°C
Setpoint switching difference 5 K
If the hot water temperature falls to 39.9 °C, the heat pump starts to heat the water back up to 45 °C.
everything works well so far.
However, as soon as I use the integration for a few days to control the hot water according to the available energy from the photovoltaic system, the watekotte no longer reacts correctly.
I have already had cases where the required hot water temperature is 45 degrees. we use water and then the sensor shows 30 degrees but the waterkotte does not start even though the switching differential is 5 K.
The heating only produces hot water again when, for example, I increase the hot water temperature extremely, for example 60 degrees or when I restart the heating, then it recognizes that the water is only at 30 degrees and starts the hot water preparation again.
It seems as if the control system would get confused over time.

Add your DEBUG log output

No response

[marq24]

When you say:

However, as soon as I use the integration for a few days to control the hot water according to the available energy from the photovoltaic system, the watekotte no longer reacts correctly.

[EDIT] What does the default waterkotte webfrontent (or the device itself) display as 'wkh_temperature_water_setpoint' and the 'sensor.wkh_temperature_water_demand' ? Are this the numbers/values you are setting/adjusting via the this home assistant integration?

If the value in the webfrontend and the integration is identical - then I would not have an idea, how I could help/support... Since then the assumption must be, that the controller on the device have the issue [not create hot water based on the request]... but might be that 5K already quite a large delta [I use 3 here]

[EDITED] I have a EcoTouch Ai1 Geo 5008.5 - and adjusting the number.wkh_temperature_water_setpoint sensor.wkh_temperature_water_demand with a automation based on the available PV production - this works rock-solid over a year now...

Do you have an additional time schedule (for the hot water running) - I do - when the hot water is OFF (cause of schedule) the target temp is here just 10°C - that might be the reason why I do not run into this?

[marplukiwi]

What does the default waterkotte webfrontent (or the device itself) display as 'hot_water_target_temperature' ? Is this the number/value you are setting/adjusting via the this home assistant integration._

Could the problem be that I used wkh_temperature_water_setpoint and not sensor.wkh_temperature_water_demand for the hot water target temperature?
The fact is if i change wkh_temperature_water_setpoint in the home assistant then the correct value also changes in the webfrontend. sensor.wkh_temperature_water_demand is the value when i activate an schedule for hot water then the target temperature is 10°C.
I don't use the schedule for hot water running. The hot Water schedule runs 24/7. If I want to switch the hot water on or off depending on the photovoltaic system, I use select.wkh_enable_warmwater

If the value in the webfrontend and the integration is identical - then I would not have an idea, how I could help/support... Since then the assumption must be, that the controller on the device have the issue [not create hot water based on the request]... but might be that 5K already quite a large delta [I use 3 here]_

5k delta has been the default setting since 2017 and works well. When the schedule is activated (OFF) for warm water then sensor.wkh_temperature_water_demand is 10°C. When warm water is ON then wkh_temperature_water_setpoint and sensor.wkh_temperature_water_demand ist the same.

I have a EcoTouch Ai1 Geo 5008.5 - and adjusting the sensor.wkh_temperature_water_demand with a automation based on the available PV production - this works rock-solid over a year now..._

I mean it is not possible to adjust sensor.wkh_temperature_water_demand it is only possible to adjust wkh_temperature_water_setpoint

Do you have an additional time schedule (for the hot water running) - I do - when the hot water is OFF (cause of schedule) the target temp is here just 10°C - that might be the reason why I do not run into this?_

See my first answer above

[marq24]

Could the problem be that I used wkh_temperature_water_setpoint and not sensor.wkh_temperature_water_demand for the hot water target temperature?

IMHO no - my initial reply was not correct (so I just have made some adjustments) - as you said, you can not write the demand - you only can adjust the setpoint -

The fact is if i change wkh_temperature_water_setpoint in the home assistant then the correct value also changes in the webfrontend.

So, when you make adjustments to the number.wkh_temperature_water_setpoint, then the value change also in the Webfrontent (after a short while) - and will also the value of the sensor.wkh_temperature_water_demand in HA and in the Webfrontent of the Waterkotte going to change? - If this is the case, then there is really nothing the integration code that can be considered as bug.

sensor.wkh_temperature_water_demand is the value when i activate an schedule for hot water then the target temperature is 10°C. I don't use the schedule for hot water running. The hot Water schedule runs 24/7. If I want to switch the hot water on or off depending on the photovoltaic system, I use select.wkh_enable_warmwater

So when you adjust the setpoint, the demand values does not change (after a short period)? At least that's what I read from your sentence above... that 'demand' only change (to 10°C) when you set select.wkh_enable_warmwater to off

I mean it is not possible to adjust sensor.wkh_temperature_water_demand it is only possible to adjust wkh_temperature_water_setpoint

you are right - I have corrected my initial reply...

So what's next? Well - I don't know, if the adjustments in the integration will be reflected 1:1 in the Waterkotte webfrontend, then there is no bug in the integration. But what could be a problem/issue is, that Waterkotte software developers did not thought about the fact, that there might be external manipulations (that frequent)...

I can understand, that this might not be the result you are looking for - since make use of the PV-Überschuss is highly appreciated. I just can repeat that I have an automation here running during the summer period that does exactly do it. But I have a different setup:

• use 3°K as delta
• use a waterkotte schedule that that turn off hot water between 21:00 o'clock and 5:00 o'clock

I make use of automations based on 'https://github.com/InventoCasa/ha-advanced-blueprints/blob/main/PV_Excess_Control/README.md' - but since this blueprint can just toggle a switch ON/FF I have an additional portion:

• added a manual switch (which I have called: 'wkh_hotwater_switch')
• use a pyscript:

@state_trigger("input_boolean.wkh_hotwater_switch == 'on'")
def check_hot_water_temp_on():
    log.debug(f"State ON Trigger test:")
    trig_info = task.wait_until(
                    state_trigger="input_boolean.wkh_hotwater_switch == 'off'",
                    timeout=5
                )
    if trig_info["trigger_type"] == "timeout":
        log.debug(f"State ON Trigger test: - STILL ON")
        service.call('number', 'set_value', entity_id='number.wkh_temperature_water_setpoint', value='59.0')
        pass
    else:
        log.debug(f"State ON Trigger test: CANCLED")
        pass

@state_trigger("input_boolean.wkh_hotwater_switch == 'off'")
def check_hot_water_temp_off():
    log.debug(f"State OFF Trigger test:")
    trig_info = task.wait_until(
                    state_trigger="input_boolean.wkh_hotwater_switch == 'on'",
                    timeout=5
                )
    if trig_info["trigger_type"] == "timeout":
        log.debug(f"State OFF Trigger test: STILL OFF")
        service.call('number', 'set_value', entity_id='number.wkh_temperature_water_setpoint', value='46.0')
        pass
    else:
        log.debug(f"State OFF Trigger test: CANCELED")
        pass

[devfaz]

I have seen the same behavior (wk not heating water any longer if updated frequently). I think your assumption is right and the waterkotte guys didnt expect anyone changing values (at all?) without using the very slow webGUI frequently.

For now I just do no longer change these hot-water-settings frequently - enabling pv-mode in evcc only once a day (in the afternoon at peak-pv) and back to "normal"-mode when evcc is no longer telling me there would be enough power to heat water.

[marq24]

so you use evcc? - I hope you have seen my evcc integration ;-)