Disabled non-verbal confirmations

[jlpouffier]

Describe the feature

Assist is now using non-verbal confirmation for responses of actions impacting devices in the same area of the voice assistant.

OK Nabu, turn off the lights
Beep

We were thinking about making this configurable, but we do not know if there is a real need or not.

Do you want to disable it?

And if yes:

• Should it be per room?
• Per Voice Assistant device?
• Per Pipeline?
• Globally?

Example commands

Not applicable

Use cases

Anything where actions are impacting devices in the same area of the voice assistant.

Anything else?

No response

[mib1185]

There is already a request about this in home-assistant/core#154417

[GR0B]

Yes I want the ability to disable the non-verbal confirmations.
I have configured my all Wyoming devices to fail silently, so if there is a false positive on the wake word they do not create a disruption.

• Having similarly named lights I would like confirmation on which action was taken.
• I have also configured my lights to slowly fade out when switched OFF over 10-20 seconds so the change is less noticeable.
• I also want the notification to be consistent with existing sounds/TTS and still be dynamic (so can not replace beep.mp3 with a TTS wav output)
• And I just outright like the voice of my TTS setup, so use it instead the generic beeps to make the house feel more alive.
• I am also playing with multiple wake words and TTS voices, the confirmation voice to me also confirms which pipeline is confirming.

[GeorgeInDigital]

Yes, I also would appreciate if this feature would be configurable.
I run HA with a local AI to give my home the personality of an english butler. The beep boop signal disrupts this experience.

[mitrokun]

Definitely, mode selection should be done for each device; ideally, it should be tied to WW. This provides the greatest flexibility in configuration.
Per Pipeline is also a satisfactory option and likely simpler to implement.
However, there’s a need for improvement for the other camp as well. Users relying on 'non-verbal confirmations' should be given the ability to assign a system sound in set_conversation_response to ensure consistency. Currently, it’s possible to use the sound playback action, but it depends on the media player’s volume level, unlike the built-in sound.

[Wupp2]

I like the "beep" instead of long answers.
For every device would be perfekt, but for me it would also work for every room.
I would also like to switch it off kompletly because when I switch off the light in the room where I speak, I don't need any response.

PS: Sorry for the bad english. I need some training ;-)

[GR0B]

The "long response" I get is just "Done" spoken in a soft voice which is about the same length as the abrasive beep.

[vasudan]

Per Voice Assistant device?
Per Pipeline?
Globally?

I think it should be per pipeline. That would cover users wanting it per device since they could assign the device to a new pipeline. It would also cover things globally since a user could only have one pipeline making the setting “global”

Should it be per room?

If the setting is this fine-grained then I think it should be by entity so the user can add an Area or a specific device. This provides the most control and covers the use-cases of the other questions. Although, the configuration has more of a chance of confusing users coming from devices that have just an on/off “Brief mode”.

I’m a user that wants to replace all confirmations with a beep, so if this was implemented like this then I would turn off confirmations to every room.

[Slim1399]

Hi,
Per Voice Assistant device.

For devices like lights or shutters, the beep is perfect, but for all devices or controls that will not have visual feedback, such as adjusting the temperature of a heater or air conditioner or the volume of a player, disabling the beep is necessary.