Input_boolean as an real switch

Good morning community,

Unfortunately, I can’t seem to create a real switch from a helper “input_boolean” – even after extensive Googling.

Could you help me?

What do you mean by a real switch?

sorry…

the original helper entity is : “input_bolean.poolheatpump”
i need for a TermostatHelper: “switch.poolheatpump”

thanks andy

And how do you switch on the heatpump now?

I Need some logic/ Automation between the Thermostat and the real heatpump Switch.

Thats the reason.
Thanks

What sort of Thermostat are you using and can that not switch your heatpump directly?

If not use this its what its for.

okay from the beginning… what i am searching for?
I Wanna have a “switch.wärmepumpeHelper” as a helper..
I want to create a HelperTermostatic and therefore i need a “switch…” which is not existing, because i need after the “heat_output” some more logice BEFORE i take the main output switch.Wärmepumpe"

what is the correct way?

This looks like exactly what the OP is asking for.

You basically have 4 options:

  1. Use a “Template Helper Switch” - Which exposes some other entity / logic as a switch (doesn’t store state itself).
  2. Use a blueprint written by someone else - which likely just wraps a THS.
  3. Use an MQTT switch with both the state and command topic set to the same value - this effectively looks and works like an input helper toggle, but is actually a switch.
  4. Use a third party plugin (some people have created them) which registers as a switch.

I have only ever used options #1 and #3.

Thank you very much for the options, i really appreciate!

Could you give me an example yaml for option1 the TemplateSwitch?

Thanks Andy

tom_l Already posted a direct link to the documentation for it:

It was fun watching you guys playing 20-questions.

Yu send me the link for the Templates, saw that - but i asked yopu about a example snip code

That code is total different… that code swtichs a switch through a binary sensor
I need a switch single

# Example state-based configuration.yaml entry
template:
  - switch:
      - name: PoolHeatPumpHelperSwitch
        state: "{{ is_state('binary_sensor.skylight', 'on') }}"
        turn_on:
          action: switch.turn_on
          target:
            entity_id: switch.PoolHeatPumpHelperSwitch
        turn_off:
          action: switch.turn_off
          target:
            entity_id: switch.PoolHeatPumpHelperSwitch

You said you have an input boolean you want to make a switch. So use that in the template:

template:
  - switch:
      - name: Foobar Switch
        state: "{{ is_state('input_boolean.foobar', 'on') }}"
        turn_on:
          action: input_boolean.turn_on
          target:
            entity_id: input_boolean.foobar
        turn_off:
          action: input_boolean.turn_off
          target:
            entity_id: 'input_boolean.foobar

… i want do delete the input boolean - i dont need that!
i want a single virtuell switch!!

your switch code is triggered by an input_boolean!!!
overall: i need a single switch virtuell

Not possible. You need both or use the third party thermostat linked earlier that can work with input booleans.

Also that is not what you said in your first post.

Emphasis mine.

Hi Tom,
The Generic Thermostat (Helper) doesn’t support input_boolean - thats my problem!
Thats the reason why i need the switch, because i want to use the GenericThermostat.

It might be a language issue, but what tom has provided you with is exactly what you need.
Let me try to explain it in the simplest way possible:

  • You have an input boolean helper, but you need a switch for the Generic Thermostat.
  • The template switch solves that issue for you. It grabs that input boolean & creates a separate switch entity based on the input boolean’s state. You need the input boolean to exist, otherwise the template switch has no source entity.
  • All you need to do is find the new switch entity which was created by the template switch, then use that in your generic thermostat.