I’ve setup an input_select in configuration.yaml to allow for me to expose a dropdown list in lovelace to control 5 scenes in my main room. I’ve wired this input_select to an automation that fires when the value changes and executes the appropriate script to set all the lighting and other devices to the appropriate settings. I’m now wrestling with how to expose this to Alexa via Home Assistant Cloud. I’ve successfully exposed the input_select entity to Alexa but can’t seem to get it to respond and set the value.
Configuration.yaml entries;
down_scene:
name: Downstairs Scene Select
options:
- Dinner
- Party
- Night
- Bright
- TV
- None
initial: None
icon: mdi:lightbulb
Well, this explains it. I ended up creating Alexa routines to call the scenes and updated the scenes to set the input_select value to the appropriate value. This keeps everything in sync.
Please consider marking my post (above) with the Solution tag. It will automatically place a check-mark next to the topic’s title which signals to other users that this topic has been resolved? This helps users find answers to similar questions and will spare them the struggle and frustration of attempting to make an input_select visible to Alexa (via NabaCasa).
FWIW, another technique (that I have seen used in other posts) is to create a Template Switch for each option in the input_select. Switches are accessible to Alexa (no routines required but more entities are needed).
I was trying the same. What I did and its maybe a dirty way. I created couple of input_booleans. Add them to Alexa. In Alexa I created some automations that will turn on an input_boolean. Inside HA the automation will trigger and do the job. In same automation it will turn of that specific input_boolean for the next time.