What’s “alex notify”?
its the “alexa media player” intergration that allow you to send a message (notify) to your alexa devices
In what way is the Alexa Media Player integration “failing at startup” unless you include a delay? Are you trying to make it notify you after all integrations have been loaded?
Post the automation you have created.
alias: bondhome started
description: ""
trigger:
- platform: event
event_type: homeassistant_started
- platform: homeassistant
event: start
enabled: false
condition: []
action:
- delay:
hours: 0
minutes: 0
seconds: 10
milliseconds: 0
enabled: false
- data:
data:
method: all
type: announce
target:
- media_player.lounge_echo_dot
- media_player.lounge_tv_cube
- media_player.kitchen_echo_dot
- media_player.spare_echo_dot_dining
- media_player.loung_show_8_2nd_gen
message: Home assistance has started
action: notify.alexa_media
mode: single
This is what I now have but it does not appear to tigger when using the other one it needs the delay I also would like to know if its possible to stop & start an interation on startup and shutdown as my 3d printer more often than not are switch off when HA starts so it waiste time looking for them
As an experiment, try this automation. It should post a persistent notification on startup.
alias: Startup Monitor
description: For testing purposes.
mode: single
trigger:
- platform: event
event_type: homeassistant_started
condition: []
action:
- action: notify.persistent_notification
data:
title: "{{ now().timestamp()|timestamp_custom() }}"
message: Home Assistant started.
It appears that sometimes the Alexa Media integration isn’t immediately available on startup. It’s a custom integration so you will need to check with whoever is maintaining it. It’s my understanding that it has been orphaned by its original author and volunteers are attempting to keep it operational.
EDIT
Correction. condition not conditions .
well thats a big shame! (thanks anyway)
Let me know if the automation I suggested works for you.
If it does then it means that the problem you are encountering (that you need a delay after startup is detected) is due to the Alexa Media integration not being ready immediately after startup.
no that appear to do nothing just did not run as far as i could tell (just gone back to the delay option for now)
sorry just notice the other bit I will try
Are you using the latest version of Home Assistant (2024.8.X) or a previous release?
The “Startup Monitor” example I posted is meant for use with the latest version (because it uses the option name action instead of service).
conditions: []
should be:
condition: []
Assuming you use the latest release, if not you’ll get another error about an action (that can be fixed too).
1 Like
Thank you!
I have corrected the example.
ok this ran
and i saw amessage about alexa starting and others and then finshed startup
am i suppost to see anything else
If the automation executed, it will produce a trace and post a persistent notification.
View the list of automations and find Startup Monitor. The time it executed will appear next to its name. If the time is “Never” then it means the automation didn’t execute on startup.
sorry no it did not!!. it did when i ran it manually (not when i used the restart) (the three dots then run)
I just tested it on my system and confirmed that I got the same result as you; it was not triggered on startup.
That means Home Assistant fails to issue a homeassistant_started event on startup. In other words, it’s not working the way the documentation claims it should work.
It’s a bug.
thats good to know it not me being stupid!!
do i need to do anything about it or is it something that will just get fixed later?