Google Assistant : Alarm control panel only works partially in english ... , Not at all in other languages

The problem

I have lot of lights/switches/scripts exposed to Google Assistant (nabucasa) , my GA setup is setup in Dutch language, no secundary english language, all is working fine, except for the “alarm control panel”

if i setup enlglish as second language then i get better responses

SO GA setup in dutch only: if i say Arm the alarm => this stand is not available => not OK disable the alarm => alarm already disabled => ok disable the alarm (if armed) => HA disables the alarm => GA respons => unexpected error … not OK

SO GA setup in dutch and english as secundary: if i say Arm the alarm => i am not sure wich level, say armed home or armed away => OK now! disable the alarm => alarm already disabled => ok disable the alarm (if armed) => HA disables the alarm => GA respons => unexpected error …

its better in english, but still errors

Environment

• Home Assistant Core release with the issue: 112.0
• Last working Home Assistant Core release (if known): None
• Operating environment (OS/Container/Supervised/Core): HassOS
• Integration causing this issue: GA + alarm control panel

Problem-relevant configuration.yaml

 - platform: mqtt
   name: Risco Alarm
   state_topic: "riscopanel/alarm/0/status"
   command_topic: "riscopanel/alarm/0/set"
   payload_disarm: "DISARM" 
   payload_arm_home: "ARM_HOME"
   payload_arm_away: "ARM_AWAY"
   code_arm_required: false

#GA Setup
    alarm_control_panel.risco_alarm:
      name: Alarm
      room: Security 
      aliases:
        - Alarm
        - Risco
        - Beveiliging
        - Security

[dasb00ter]

Still happening. Although weirdly I was able to disable my alarm without error once in awhile

[dasb00ter]

I’m still seeing this behaviour. I’m using English and asking Google home to “set my home alarm to away”. It then asks for me code which I give. The action is performed but Google home warns “that something went wrong”. After reading multiple duplicates I found my way here. Thanks, sorry to repeat what others are saying but it seems the issue gets closed if it becomes stale. I’m on 2022.3.7