Notify Alexa devices using Alexa Media Player

Blueprints Exchange
,
1

Hello Home Assistant forums!

This blueprint is one that I made to slightly simplify the process of sending notifications to Alexa devices while using Alexa Media Player, in a way inspired by Grumblezz’s Notify Mobile Companion Devices script. While the notify service provided by AMP isn’t super complex, I wasn’t aware of some of its functionality (namely the Announce notification type) and wanted a GUI-driven way to quickly set those parameters.

Getting started

First, you need to install Alexa Media Player and make sure it’s working.

Once you’ve done that, click the below button to add the blueprint to your install, then create a script from it. Make sure to give it a memorable name!

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

Alternatively, if you want to see the source before importing it, here is a link to the blueprint on GitHub.

Using the script

image
image1060×743 31.9 KB

The YAML reference is as follows:

  • message - The message that you want to be read out using TTS. If type is announce, you can use Amazon’s flavor of SSML markup in your message.
  • type - One of three values, described below.
    • tts - Alexa will speak using Alexa’s Simon Says skill and will not sync between devices. This does not work with an Alexa Whole House Audio group (WHA). This does allow messages to phone apps which the Announce function does not.
    • announce - This functionality will result in a beep prior to speaking. It can also allow display on Echo Shows/Spots. Whole House Audio groups are supported. It does not appear to sync across devices.
    • push - This will send a mobile push notification to any Alexa apps linked to the target Alexa device.
  • title (optional) - The title to display. Only works with announce and push notifications.
  • devices (optional) - The device(s) to direct the notifications to. These take device IDs, and translates them to entity IDs. If this is not supplied, all Alexa devices will be notified.

Despite what the UI says, there is no response variable support.

Hopefully some of you find this useful! It’s my first blueprint, but I think it has value.

UPDATES

2024.03.7

Fixed a small issue where it would try to include a title when none is supplied, leading to spurious log file messages. Thanks @masterpete!

2024.03.29

Added a description for when you’re first creating a script using this blueprint. Thanks @Tockra and nothra on Github!

8 Likes
2

Hi, thanks for your solution.
Since last update log is showing:

2024-02-22 12:07:30.200 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'title' is undefined when rendering '{{title}}'

I searched for {{title}} in my yamls and only found this here. Do you know about it?

3

Ah! Sorry, didn’t see this post before.

Just did some testing and it seems like that message gets logged when you don’t have a title set. That’s definitely a bug, not sure why that’s happening…

4

Just fixed the issue and pushed an update to it! As I don’t think blueprints have any sort of automatic update capability, you’ll need to go to Settings → Automations & Scenes → Blueprints and re-import the blueprint like so:

image

I don’t think restarting HA from here is a necessary step, but it couldn’t hurt.

1 Like
5

just updated - we will see if it works.

THANKS

6

After I successfully did my alexa media player integration I installed your blueprint and wanted to test it.
The blueprint for Alexa notify has no input:

image
image2610×1366 128 KB

7

There are no configurable inputs during that initial setup; all of the configuration comes when you’re actually using the created script in automations. Once created, the options described in the OP should all show up as expected.

Apologies for not making that clearer; I’d meant to add some text to that screen to explain it but forgot. Whoops…

8

As an update, I just updated the script with a little introduction! It should be a bit clearer that you need to make the script first before you have access to the configuration options. Thanks again for the suggestion!

1 Like