Alexa Actionable Notifications - ResponseNone Event Not Firing

Third party integrations
,
1

Hi all,

Having some trouble with Alexa Actionable Notifications. Specifically, the “ResponseNone” event that is supposed to fire when no response is given to the notification does not fire until another notification is called. This obviously screws up any automation that relies on that event to trigger an action. Has anyone else seen this behavior before and is there a fix? My automations are posted below. Any help is appreciated. Thanks!

Notification Automation

alias: Alexa - Garage Door Left Open Notification
description: >-
  Determines if the garage door has been left open and if no one is home, sends
  a phone notification. If someone is home, creates an Alexa actionable
  notification.
trigger:
  - platform: state
    entity_id:
      - cover.garage_door
    to: open
    for:
      hours: 0
      minutes: 30
      seconds: 0
condition:
  - condition: state
    entity_id: cover.garage_door
    state: open
action:
  - choose:
      - conditions:
          - condition: and
            conditions:
              - condition: not
                conditions:
                  - condition: state
                    entity_id: person.person1
                    state: home
              - condition: not
                conditions:
                  - condition: state
                    entity_id: person.person2
                    state: home
        sequence:
          - service: notify.mobile_app_person1_iphone
            data:
              message: The garage door has been left open, would you like to close it?
      - conditions:
          - condition: or
            conditions:
              - condition: state
                entity_id: person.person1
                state: home
              - condition: state
                entity_id: person.person2
                state: home
        sequence:
          - service: script.activate_alexa_actionable_notification
            data:
              text: >-
                Looks like the garage door has been left open, would you like to
                close it?
              event_id: garage_door_left_open
              alexa_device: media_player.kitchen_echo_show

Action Notification

alias: Alexa - Garage Door Left Open Action
description: Closes the garage door or does nothing based on Alexa response.
trigger:
  - platform: event
    event_type: alexa_actionable_notification
    event_data:
      event_id: garage_door_left_open
      event_response_type: ResponseYes
    id: "yes"
  - platform: event
    event_type: alexa_actionable_notification
    event_data:
      event_id: garage_door_left_open
      event_response_type: ResponseNo
    id: "no"
  - platform: event
    event_type: alexa_actionable_notification
    event_data:
      event_id: garage_door_left_open
      event_response_type: ResponseNone
    id: none
condition: []
action:
  - choose:
      - conditions:
          - condition: trigger
            id: "yes"
        sequence:
          - service: cover.close_cover
            data: {}
            target:
              entity_id: cover.garage_door
      - conditions:
          - condition: trigger
            id: none
        sequence:
          - delay:
              hours: 0
              minutes: 30
              seconds: 0
              milliseconds: 0
          - if:
              - condition: state
                entity_id: cover.garage_door
                state: open
            then:
              - service: automation.trigger
                data:
                  skip_condition: true
                target:
                  entity_id: automation.alexa_garage_door_left_open
      - conditions:
          - condition: trigger
            id: "no"
        sequence: []
mode: single
2

Did you ended up finding a fix for that? Having the same problem using Alexa Actionable Notifications in Node Red

3

Did some more digging and eventually found that the issue is only with the Echo Show devices. Supposedly, they aren’t supported 100% correctly and this is one of the bugs. I found that it works correctly on a normal Echo.

I ended up just creating a boolean for each of my automations that use the “ResponseNone” event and replaced that event with the boolean. It turns on whenever the notification automation is triggered and turns off if I respond to the notification. In the case where I dont respond (a ResponseNone event) the boolean just stays on and if its on for more than 40 seconds, the “ResponseNone” action runs in my action automation, then turns it off at the end. Kind of a weird work around but it seems to work alright.