HA script launching Alexa Routine has mysteriously stopped working

Prologue – This is my first time posting in the community, so I’m not sure if this is the right place. Please let me know if I should post elsewhere.

For starters, this has been working via the Alexa Media Integration and legitimately just stopped. And I don’t think anything has changed. I would also like to point out that the automations are firing AND triggering the scripts (evidence being the “last triggered” column in HA), but the script is not interacting with Alexa - I don’t know if there is a way to confirm this; maybe they are interacting with Alexa, but I don’t know how. . . or what’s failing with Alexa. If I remember correctly when I set these up, they were essentially supposed to simulate my saying out loud the Alexa routine phrase, i.e. “Alexa, Good Morning” and “Alexa, Dim the Master Bedroom.”

HA Version: * Installation method: Unsupported third‑party container* Core version: 2025.11.1 * Frontend version: 20251105.0
Alexa Media Player Version: 5.8.2

Has anyone else seen Alexa routines suddenly stop working?

I’m trying to figure out if this is just me, or if something changed recently. My automations are still firing and calling the scripts, but Alexa no longer responds to the routine triggers.

  • Could I be overlooking something simple?
  • Should I try reinstalling the Alexa Media Player integration?
    • If reinstalling is the right move, what’s the current process (it’s been a long time since I set it up)?
      • What would I lose if I disconnect and reconnect the integration — do I risk losing entities, scripts, or routine links?

Any guidance or shared experiences would be really appreciated!


I have an automation that triggers

• When motion is detected in the specified rooms during the time window, on a weekday, and the lockout switch is off → the automation runs the script.
• The script triggers Alexa’s custom routine named “Good Morning.”
• That routine executes whatever steps you defined in the Alexa app (lights, announcements, etc.).
• After running, the lockout switch is set to on, so it won’t run again until midnight resets it.

The automation is the gatekeeper (motion + time + once per day logic), and the script is the executor (actually firing the Alexa routine as if you had said “Alexa, good morning”).

This was working previously, but mysteriously stopped! I need help troubleshooting/fixing it, please!

Good Morning Automation: :arrow_down:

alias: Good Morning
description: >
  Triggers "Alexa 'Good Morning'" script when motion is detected in the great
  room, kitchen, or upstairs kitchen between 7:10 and 7:40 AM, only once per day
  unless manually reset
triggers:
  - entity_id: binary_sensor.great_room
    to: "on"
    for:
      seconds: 1
    trigger: state
  - entity_id: binary_sensor.kitchen
    to: "on"
    for:
      seconds: 1
    trigger: state
  - entity_id: binary_sensor.upstairs_kitchen
    to: "on"
    for:
      seconds: 1
    trigger: state
  - at: "00:00:00"
    trigger: time
conditions: []
actions:
  - choose:
      - conditions:
          - condition: time
            after: "07:10:00"
            before: "07:40:00"
          - condition: state
            entity_id: input_boolean.great_room_sensor
            state: "off"
          - condition: template
            value_template: "{{ now().weekday() < 5 }}"
        sequence:
          - action: script.good_morning
            data: {}
          - target:
              entity_id: input_boolean.great_room_sensor
            action: input_boolean.turn_on
            data: {}
          - data:
              title: Good Morning routine has run
              message: Good Morning Alexa
            action: notify.mobile_app_johns_iphone
            enabled: false
          - data:
              name: Good Morning Automation
              message: Triggered by motion in {{ trigger.entity_id }}
              entity_id: "{{ trigger.entity_id }}"
            action: logbook.log
          - data:
              title: Good Morning Triggered
              message: >-
                The Good Morning routine ran at {{ now().strftime('%I:%M:%S %p')
                }} on {{ now().strftime('%A') }}.
            action: persistent_notification.create
            enabled: false
      - conditions:
          - condition: template
            value_template: "{{ now().hour == 0 and now().minute == 0 }}"
        sequence:
          - target:
              entity_id: input_boolean.great_room_sensor
            action: input_boolean.turn_off
            data: {}
          - data:
              name: Good Morning Automation
              message: Reset input_boolean at midnight
              entity_id: input_boolean.great_room_sensor
            action: logbook.log
mode: single

Good Morning Script: :arrow_down:

alias: good morning
description: Triggers Alexa to say good morning
sequence:
  - alias: say good morning
    sequence:
      - target:
          entity_id: media_player.john_s_echo_show_8_3rd_gen
        data:
          media:
            media_content_id: Good Morning
            media_content_type: routine
            metadata: {}
        action: media_player.play_media

Good Morning Bypass Sensor⬇️

input_boolean.great_room_sensor

I would also like to include a separate automation as reference. This automation also used to work, and Its set up similarly, but also mysteriously stopped: :arrow_down:

alias: Dim Bedroom When TV Turns On (Power-Based)
description: Turns on dimming boolean when TV power draw exceeds threshold
triggers:
  - entity_id: sensor.master_tv_plug_current_consumption
    above: 5
    trigger: numeric_state
actions:
  - target:
      entity_id: input_boolean.master_bedroom_dim
    action: input_boolean.turn_on
  - delay:
      seconds: 5
  - target:
      entity_id: remote.master_bedroom_apple_tv
    data:
      command: menu
    action: remote.send_command
mode: single

The above fires the input_boolean, which fires this script::arrow_down:

sequence:
  - alias: dim the master bedroom
    sequence:
      - target:
          entity_id: media_player.john_s_alexa
        data:
          media:
            media_content_id: dim the master bedroom
            media_content_type: routine
            metadata: {}
        action: media_player.play_media
alias: dim the master bedroom
description: ""

I am having the same issue, I haven’t figured it out yet

Same here, and it appears that Alexa has changed how it views both input booleans and input buttons. For booleans, it used to be on/off, but now alexa recognizes open/closed. For input buttons, Alexa used to see the button push and trigger, but now it says “Select Capability: Person, When human presence detection changes.” There’s no way to trigger the routine any more with a boolean toggle or button push. I’m sharing my experience in hopes it helps someone troubleshoot.

In the mean time, I’ve discovered that routines can be triggered when light switches are turned on, so now, I use a Hue bulb in my basement. When I leave my house, Home Assistant turns on that bulb. Alexa routine is now triggered by that bulb being turned on and subsequently locks my front door. This used to be accomplished with an input button, but I’ve discovered that switches can still be used.

The Alexa Media Player integration is very brittle. Use it at your own risk. I recommend heading to the github page and looking at recent issues.

This is unrelated to Alexa Media Player.

Alexa Media Player allows you to control Alexa from HA.

Alexa Smart Home Skill, Nabu Casa, Matter, or Emulated Hue are what create devices in Alexa that control Home Assistant entities.

Controlling Alexa from HA is precisely what I’m trying to do. Thus, Alexa Media Player.

I have a UltraLoq deadbolt that has WIFI radio for control. Since UltraLoq doesn’t work with Home Assistant, I’ve worked around this by creating an Alexa Routine to lock the deadbolt. That Alexa routine was formerly triggered by an input_button inside Home Assistant. Press the button, and Home Assistant would call up the Alexa Routine, which would then lock the door.

I use Node Red, and the JSON that formerly worked inside of an Action Node for this was as follows:


{
    "entity_id": "media_player.music_show",
    "media_content_id": "Deadbolt",
    "media_content_type": "routine"
}

So, since media_player was actually the entity_id, I’m not sure what your correction is about. It worked great until, from what I can tell, Alexa changed how it sees input_buttons for triggers. Now, pressing the button in Home Assistant isn’t seen as a time stamp, but presence detection, apparently. That’s where I’m stumped.

Unrelated to the question at hand, for those interested, my workaround for the former workaround is this:

  1. Alexa Routine is now triggered by a light bulb being turned on. Whenever that happens, Alexa locks the door.
  2. That light bulb is triggered every time my front door closes. Home Assistant (Node Red) senses the Aqara sensor in the door becoming closed, and turns on a light bulb in the storage portion of my basement where nobody ever is.
  3. Alexa notices the bulb came on, and locks the door.

The bulb has become my replacement of my input_button for the time being, but I’d love to be able to go back to input buttons/booleans the way this ran for years. In reality, I’d love for Home Assistant to work with UltraLoq directly, but that’s another issue altogether.

Genius workaround, thank you! I created an input boolean that I exposed to Alexa, and then created routines to react to it being turned on and off.

Thanks to everyone who responded and offered suggestions.

I wanted to close the loop and share what ultimately resolved the issues I described in the original post.

For the Good Morning routine, the fix ended up being fairly simple: I exposed input_boolean.great_room_sensor to Alexa and updated the Alexa routine so it triggers either when I say “Good Morning” or when that input_boolean turns on. Once I did that, the routine started firing reliably again.

The only odd side effect is that the automation now occasionally feels like it runs twice. There’s a slight stutter—almost as if the script fires first (sending the “Good Morning” phrase to Alexa), and then a few seconds later the Alexa routine triggers again when the input_boolean flips to on. I’m still watching this behavior to confirm what’s happening, but functionally everything is working again. may remove the script all together relying just on the automation and input_boolean to try and avoid the stutter.

As for the master bedroom the solution was the same - simply exposed the input_boolean.master_bedroom_dim and viola. it was working again. Fortunately, since there are no announcements from Alexa when the routine is run, I don’t have the same stutter affect that I experience with good morning. even if there is stutter, once the light dim, they can’t dim again.

I hope this helps anyone else who runs into the same issue.