Virtual Switch - Switch Template example please

[PrayerfulDrop (AaronW)]

Hello all,

I am a n00bie moving from ST->HE->HA. I have been learning a lot surrounding NodeRed and automations. I am now incorporating Alexa and have a need for virtual switches that can be triggered by Alexa and then sent to HA. I have tried using a helper input_boolean_toggle but it is not available as a switch/light or anything useful from a voice command. I have attempted to create a switch template, it shows up in HA and Alexa but the two are not communicating correctly.

Some info:

1. I am using the pay-to-play Cloud Integration for Alexa
2. My goal is to say “Alexa, turn on Doggy Bed Time” and then my NodeRed routine would execute

Current Switch Template located in the configuration.yaml file:

switch:
  - platform: template
    switches:
      doggybedtime:
        friendly_name: Doggy BedTime
        value_template: "{{ is_state('switch.doggy_bedtime','sensore_state','on') }}"
        turn_on:
          service: switch.turn_on
          data:
            entity_id: switch.doggy_bedtime
        turn_off:
          service: switch.turn_off
          data:
            entity_id: switch.doggy_bedtime
        icon_template: mdi:dog

Again I am a n00bie and any and all help is truly appreciated!

[tom_l]

Your value template is incorrect, it should be:

value_template: "{{ is_state('switch.doggy_bedtime','on') }}"

I don’t see why you are using a template switch for an entity that is already in the switch domain though.

You have just duplicated the switch.doggy_bedtime to switch.doggybedtime. How is this going to help with Alexa when the first entity is already a switch?

[PrayerfulDrop (AaronW)]

@tom_l

value_template: "{{ is_state('switch.doggy_bedtime','on') }}"

That is my point. I do not know what I am doing for switch templates. Do you have an example of a simple switch that would become a virtual switch? Also one that would work in lovelace so I can add it to a card?

[tom_l]

I don’t know what you mean by “virtual switch”.

[PrayerfulDrop (AaronW)]

Virtual Switch on other platforms is just a “dummy” switch that can be turned on/off. The template switch looks like to be the same thing. I am trying to create a empty switch that is not connected to anything but is also not the input_boolean_toggle as many reference in the forums. It needs to be a switch for Alexa to do anything with it.

[tom_l]

Create an input boolean. If that is not exposed to Alexa but switches are, then create a template switch to turn the input boolean on/off.

[PrayerfulDrop (AaronW)]

if the input_boolean is input_boolean_doggy_bedtime could you help me with what the configuration.yaml code would looke like for the template switch? This is where I am getting confused is between the template switches and helpers. I do appreciate your responses btw.

[tom_l]

Just replace the services and domains with input_boolean.

switch:
  - platform: template
    switches:
      doggybedtime:
        friendly_name: Doggy BedTime
        value_template: "{{ is_state('input_boolean.doggy_bedtime','on') }}"
        turn_on:
          service: input_boolean.turn_on
          data:
            entity_id: input_boolean.doggy_bedtime
        turn_off:
          service: input_boolean.turn_off
          data:
            entity_id: input_boolean.doggy_bedtime

[ashscott (Ash)]

An input_boolean can be directly exposed to Alexa (at least it can when using NabuCasa, not sure about other methods) so there’s no need for anything other than the input_boolean.

Just have Alexa turn it on and off and trigger from that.

[PrayerfulDrop (AaronW)]

That doesn’t appear to be true. The NabuCasa does not sync helpers (input_boolean) correctly.

[ashscott (Ash)]

It does for me. What about it seems incorrect to you?

[PrayerfulDrop (AaronW)]

Alexa can’t do anything with it. Look at the type in the screen capture. It says other. Alexa responds back that the skill cannot do anything with this device.

[PrayerfulDrop (AaronW)]

Thank you so much for the help! That works like a charm. Maybe you know the answer to this next question…

Template Switch doesn’t allow me to add the switch to other “areas.” When getting the properties of the entity to associate the switch lovelace responds with a message “This entity does not have a unique ID, therefore its settings cannot be managed from the UI.”

Thoughts?

[tom_l]

Currently only discovered entities support areas.

[tixastronauta (Tiago 'Tix' Carvalho)]

Hi tom! Is this still the case in sept 2021? Thanks in advance!

[alfredoperezESP (Alfredo Pérez)]

If you want the to expose a Virtual Switch correctly in alexa, the best option is to create a virtual device from Tuya. You have to create a developer account on https://iot.tuya.com/, after that, create a cloud project (it’s free) and from there create a virtual device. Be sure that you have linked your Tuya Account with home assistant.

This device could be use as an association or trigger, used with automations in HA.