but it does not work.
When I put one specific climate device as the entity it worked so in principal the sentence does what it should but I guess I am not using the alias correctly.
Yes I did and it understands the alias as long as I put the specific name of one climate entity into the code (the # section). So for testing the alias itself it works but of course i would have to write several automations, one for each climate entity.
If your having issues have a look at the debug part of the voice assistant to check thats hearing you correctly for the climate entity, and test with text input.
I was having an issue with saying “frontroom leds” being heard as “front room leds” and then it wouldn’t match.
Even when I type the command it does not understand that the alias refers to the wall thermostat. The log just shows that the target and everything is empty. So it does not make the connection from the alias to the entity.
hence I wonder whether the syntax in the automation is wrong.
I also tried one of the standard intents:
intents:
HassClimateSetTemperature:
data:
- sentences:
- "(<numeric_value_set>|adjust) <temp> [in <area>] to <temperature>"
- "(<numeric_value_set>|adjust) <area> <temp> to <temperature>"
At the top of the page click “Expose”. You will be presented with a list of entities, click the entity you wish to assign an alias to. Click “+ Add Alias” in the pop-up.