Make integration more Google Assistant friendly/compatible

[Anto79-ops]

Before submitting this form

• I have checked that there hasn't been a similar issue submitted in the past

• I have updated the issue title to something relevant and clear to understand the bug I'm facing

Description of the bug

Hello just wanted to mention that the integration is working perfectly fine no issues except when I do a voice command to arm or disarm the system to my Google Assistant speakers the action always works except Google immediately says:

"There was a problem. Please try again later. "

I'm using Nabu Casa to expose my entities to Google Assistant.

I'm not even sure how to obtain logs for this perhaps this is all happening on the Nabu Casa and/or Google side.

Thanks for the integration.

Expected behavior

For the command to work without the audio error message

DEBUG logs

I guess I could try to debug this... If you think it will help

Additional context

No response

[XaF]

I am not entirely sure how this relates to this integration, since we're not doing anything special for Google Assistant.
Does it end up working even if giving an error message ?
It would be good to understand what specifically triggers that error message.

[Anto79-ops]

yes, it works despite giving this message.

I'm not sure either, how to approach this. Maybe I could submit to HA Core issue?

EDIT: might be related to this:

home-assistant/core#37345

BUT I only use one language in, English.

[XaF]

Have you tried setting the arm away delay to 0? In the thread you linked some people say they didn't have the issue when the delay was 0. The issue could be that after issuing the command, the assistant check the state and if it's not the expected state, it says there was an error. If you ask to arm away and a delay kicks in, the alarm state is not "armed away" but "arming", and thus not what the assistant might expect.

[Anto79-ops]

I just noticed this reply....sorry for the late response as I didn't get a notification.

I have this in my config:

arm_away_exit_delay: 0

If this is what you are referring to? If so, then yes, I've had this all along.