Ebeco Smart Thermostat Automation to Set Temperature Based on Multiple Rules

Hi

I’m rather new with Home Assistant, but already pretty comfortable with everything on the UI. I have a bunch of automations made with lights, switches, motion sensors etc., but not really needed to work with the YAML files too much.

What I have as hardware is a Ebeco smart thermostat controlling my bathroom floorheating. I’ve installed through HACS this module: GitHub - joggs/home_assistant_ebeco: Integration for Ebeco thermostats and the UI side of things is great; I can turn heating on/off and set the temperature. The problem is that on the automations side, the drop down for “Actions” only allows selection of either preset HVAC mode or turn heating on/off and there’s no way to set the temperature.

Goal I’m trying to achieve is to first of all, always turn the floor heating on, after shower to get the wet floor to dry up faster. To eachieve this I have a temperature&humidity sensor in the bathroom and I can trigger the automation based on the measured humidity. If I could only set the target temperature always a few degrees higher for a couple of hours, it’d dry the floor quickly. Later down the line, I had the idea of expanding the automation to take the electricity price into account and heat up the floor more during winter when the electricity is cheap, and take a step back when electricity is expensive.

The Ebeco integration has to have the temperature setting function in it, as it’s possible through the UI so I assume it’s possible to use that function through YAML. Am I right? If so, how is that done? Any help highly appreciated, thanks!

1 Like

First, this isn’t about a Blueprint, so you might get better responses if you take blueprints out of the top and add the tag for climate.

After that the custom integration you picked only has those features and you need more, you will need to bring that up in the Github repo for that integration. Perhaps there are other ways to integrate this that will work, don’t know what’s the best for your equipment and situation, but adding the right tag will get you better information from people that know. I don’t.

Thanks @Sir_Goodenough! Appreciate the input.

I actually did now figure it out on my own.
The difference between all the other automations I’ve been using is that setting the temperature goes through calling a generic service “Climate.Set_Temperature” and then selecting the target device.

For anyone else in the future struggling with this here’s what I did. I have two separate automations running:

  1. Baseline automation for floor heating:
    https://imgpile.com/images/GnWrYL.png
    And for day and night I set up number slider helpers to easily change the target temperature. Those are used in the service call functions as variables: https://imgpile.com/images/GnWV4j.png

  2. Turning on extra heating for two hours after shower


    The temperature setting is put in with the same code on both of these automations which is here:

service: climate.set_temperature
data_template:
  device_id: f93eae0fd244ae0bbf4617992acbd5b2
  temperature: "{{ states('input_number.bathroom_temperature_after_shower') | float }}"

Note: It’s only possible to set variables like the “Bathroom_temperature_after_shower” (at least as of now) with the YAML editing.

So basically now I’m in a situation where I have 3 temperatures depending on the situation. One higher for after shower, “normal” for day time and “low” for night time. And the logic runs smoothly. Next up, I’ll be adding one more variable to the mix which will be affecting at least the daytime temperature based on the electricity price of the day. Maybe I could end up even with a system that takes always the most out of almost free electricity by heating up the bathroom even at night, as of course most of the heat will stay there for a while and this could end up being more economical depeding on the forecasted electricity price for the next day.

1 Like