If everything is unavailable all the time that’s a bug. In that case check your region.
Do not disturb switches should always be available. The repeat/shuffle switches are only available when the media player is playing certain media that support them.
If you don’t use them, you can either disable the entity in HA or in the config.
Hey on another reboot after update to 104.1 the dnd became available. I did have them all disabled but was seeing all these log entries about it was unable to update entity as it is disabled. Having 13 echos, 3 shows, 3 subs, 4 fire tv and all the wha groups, and stereo pairs theres alot of these switches.
Managed to get the timer and reminder sensors working and now I want to show them on the UI (I have a wall mounted tablet). Anyone got any suggestions on the best Lovelace card to use? I like the Entities card as it shows the countdown although it doesn’t say what the timer is for (if you’ve named it). Also, it always shows even if there is no timer (or reminder) set as they always show as unavailable. Any way to show this only when there’s an active timer/reminder? Thanks
i wrote a script which I exposed to alexa in order to ask which timer are active.
I have 6 echos collected in a group before.
Perhaps it can push you into the right direction:
question_open_reminder:
sequence:
- service: alexa_media.update_last_called
- delay: '00:00:01'
- service: notify.alexa_media
data_template:
target: '{{states.sensor.last_called_alexa.state}}'
data:
type: tts
message: >
{%if states | selectattr('entity_id','in',state_attr('group.all_alexa_sensors','entity_id')) | selectattr('state','eq','unavailable') | list | count | int == 18 %}
There is no timer, alarm or reminder set
{% else %}
{%- for entity_id in states.group.all_alexa_sensors.attributes.entity_id if states(entity_id) != 'unavailable' -%}
{% if loop.first %} the following times are set {% elif loop.last %} and {% else %} , {% endif -%}
{{ state_attr(entity_id,'friendly_name') + ' in ' }} {{( (as_timestamp(states(entity_id)) - as_timestamp(now())) / 60) |int }} Minutes
{%- endfor %}
{% endif %}
By the way: my wife likes to get the minutes left and not the time of getting valid
Thanks Pirol_62 I like your script and I’ll have to give it a crack as it is pretty cool. It’s not quite what I’m looking for though as this (I presume) will get alexa to announce all active timers etc when you ask. I want to be able to walk past the tablet and see the timers set and the remaining time without having to ask.
I’m currently putting in some logic to skip creation of illogical switches or to hide them when you can’t use them.
In that vein, would people want timers/alarms/notifications to be hidden from the UI if there isn’t any detected? You would still be able to access them in scripts.
I’d love to have a lovelace card that could show all active timers and reminders and show the card only when they’re active. I’ve partially managed this with the following
It works pretty well but only shows the timer or reminder that’s due next and not the detail of it. It would be great to have it show all active reminders and timers with the details pulled from the code. I can see that the timer/reminder info is there but no idea how to grab it and put it into a card.
Just some thoughts for the much cleverer people than me out there to consider
My issue was with the cookie that I exported and saved to /tmp per the instructions on github. I found that I had to make a cookie for https://pitangui.amazon.com instead of alexa.amazon.com
Hi, I learned something new this morning.
We started to use one of our echos as alarm clock in the morning.
That worked but it was much too quiet even I set he volume level during the night to .6
Google teached me, that there is an additional volume level for alarms and reminders.
And yes, that was set to .2.
The question is: Does the api expose this alarm volume level in order to get it under control in HA?
You can find it under devices>sounds>alarms, timer and reminders
Good find. It’s in a rest-api untethered to the websockets. We can probably expose it but refreshing data from it will be delayed. Where do you think we should put it in HA for interaction purposes? The existing volume controls would only hit the main volume. We could spawn a notifications media player but people are already saying we create too many entities. It’d be easy to expose as another media_player attribute like notification_volume but the question is how would people easily interact with it.
Hi, the trouble is, that if the alarm has been triggered with a lower or higher volume level then the general volume, the different volume will be kept as general.
So in the first step, it would be helpful to have an additional attribute with this alarm volume level available.
That gives the information that there is a second volume level which may be different to the one we’re working with and may have an influence on this.
Is it possible to create an automation that starts an alexa routine? If yes, can someomne redirect me to a guide or docs about it?
EDIT: Ok i found it, but now the question is: how to stop a routine from an automation? Is it only needed to turn off the media player or is there any command to stop only the routine?
I need to run various skills automatically and so i am forced to use Alexa routines as now they can enable skills…
But then i noticed the routine is triggered succesfully if i try it in the services UI, but it doesn’t start when in an automation… Where is the error?
- alias: 'Nessuno a casa'
trigger:
platform: state
entity_id: group.presenze
from: 'home'
to: 'not_home'
condition:
condition: state
entity_id: sun.sun
state: above_horizon
action:
- service: media_player.play_media
data:
entity_id: media_player.echo_plus
media_content_type: routine
media_content_id: "Caccia i ladri"
- service: notify.mobile_app_sm_g955f
data:
message: 'Nessuno a casa. Attivata skill'