Better Thermostat Extension: Reduce temperature depending on schedule, presence (person in zone) incl. partymode

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

Code on Github

Temporarily sets [Better Thermostat - Entity] to a different temporary [Target temperature] depending on a presence, schedule and partymode.

Sets the configured [Target temperature] at the [Better Thermostat - Entity] when

  • the [Schedule] is currently set to off

or

  • the [Person] is currently not in the [Zone].

Otherwise, the heating temperature set on the Better Thermostat is restored.

To activate the BT even if the [Schedule] is switched off or the [Person] is not in the [Zone], the party mode can be activated via a switch.

After the [Partymode] has been switched on, it is automatically deactivated again after the time period [Duration for Partymode].

Requires Better Thermostat

** Version 1.0, 28.09.2023

1 Like

Hi,

really great blueprint and thanks for that. Is there a chance to add more then one Person into the Blueprint? Because sometimes i go for a walk with the dogs and my wife and kids are still at home. In that case the target temp. will be low.

Kind Regards
Sebbo

That can be done by defining a template sensor and use that instead of one person. Mine looks like:

  template:
  - binary_sensor:
      unique_id: 5ab8c7cb-7db8-4e25-b1f9-80a8ddc4481c
      name: "somebody_home_now"
      icon: mdi:human
      device_class: presence
      state: >
        {{
          states("sensor.user1") == 'Home' or 
          states("sensor.user2") == 'Home'
        }}
    trigger:
      - platform: state
        entity_id: sensor.user1
      - platform: state
        entity_id: sensor.user2

1 Like

Hi,

Beginner’s question. The question may not necessarily belong in this context, but it’s related to the Better Thermostat and heating automation. So my question is: Where is the comfort temperature specified?

Thanks!

Might be a silly question…what is a party mod? How to create a party entity that is required for the template?

When party mode is active, the heating is always switched on - regardless of presence or schedule.

You can create the required helper via Settings / Devices & services / Helpers. A helper of the type Switch is required.

Hello all. This looks great.

I dont know if this is the right place to ask this if anyone can help. Im wanting to get up a thermostat per room.

I current I have a average temp sensor across the whole house which calls for heat and the whole house going to eco when no one it home tracking phones. With 4 thermostat setting the temp for different times of the day. Morning, Day, evening and night temps with a schedule for times it changes each day.

I want to get to the point where I have a son off TRV and temp sensor in the room. Where it looks at the sensor and if its below thermostat settings it calls heating to come on and open the TRV and once it reaches the temp it closes the TRV and no longer calls for heat.

But if 2 rooms are calling for heat and one heats up quicker that room will closes its TRV and all the heat will go to the colder room. Until it at temperature then it will close its TRV and no longer call for heating.

My question is there an easy way to do this with just on Thermostat per room. that remembers the last temp for day, evening,night, morning then will recall it once it gets back to that time of day.

Or if not that will default to a set temp for thats room each day.

I want to above having 4 themostats per room.

Thank you in advance.

Hello all.

i have a Question:

Why do i need to set 2 Entitys for this?


The description for both are the same and i cant save it without setting both entities.

After reading your Code i can find target_bt and target_bt2:

  domain: automation
  #source_url:
  input:
    target_bt2:
      name: Better Thermostat - Entity
      description: Which Better Thermostat is to be controlled (climate, only Better Thermostat devices can be selected here)
      selector:
        entity:
          filter:
          - integration: better_thermostat

    target_bt:
      name: Better Thermostat - Entity
      description: Which Better Thermostat is to be controlled (climate, only Better Thermostat devices can be selected here)
      selector:
        target:
          device:
            integration: better_thermostat
          entity:
            integration: better_thermostat
            domain: climate

but target_bt2 is never used anywhere again, target_bt can be found 4 times in the code.

So for what ist that extra entity?

Regards

Dirk

Tank you! :slightly_smiling_face:

Hi,
I tried this in many ways (via ui and the config yaml) but I can’t get the "some one home"to show up on the blueprint ui. Am I missing something? The sensors themselve work and show up in teh dev tools.