Default intents for Assist such as HassTurnOn and HassTurnOff are great if your not creating your own custom sentences. The problem is some of us would like full control over these sentences as sometimes even after creating your own the default intents can interfere.
The default intent “What is” always overrides my custom intents. I’d really like to be able to turn default intents off, or have HA check my custom intents first.
2 Likes
My case is that blinds support close-tilt, but not close, but I want to say close. HA intent says “Closed” but nothing happens. Not sure why but alexa voice command works properly. Trying to find work around to close and have HA intent close-tilt.
Now when we are adding custom sentences, the builtin intent is expanded with these sentences. So it can by small configuration like expand: false or replace: true so the builtin sentences will not be expanded but replaced. Then you can easy replace it with empty array.
First use case for me - I’m using at most 50% of available voice commands, so there is no need to search in what I don’t use.
Second use case is current HA situation: Dev tools > Assit with sentence “set temperature to 22” and you will see matched intent HassLightSet. And with more intents there will be higher possibility for collisions.
So with this relative small option you give great power to users tune intents.
1 Like