Maybe there is another issue with volumes.
I reset the volume of my echos twice a day to a standard.
What I detect is, that everytime, when I start the automation, the equilizer settings are at 0.
Can it be, that “media_player.volume_set” resets the equilizer settings?
Can anybody confirm that?
Do you receive the notification? If not, the problem might be the condition
Is it possible to activate/deactivate the alarm?
Problem solved… it was an error inside the group.presenze… now it works good.
It’s the same command as in the Alexa app so you can build a routine with it and see if it modifies the equalizer settings. If you have the alexaapi.alexawebsocket log on, your HA will show you the volume commands that the Echo devices are processing. If you see PUSH_EQUALIZER_STATE_CHANGE then yes, it may be linked.
I don’t know if this has been asked/answered in this huge thread but is there a way to get the current volume of the echo devices?
I know that once the volume is changed after a HA restart there is an attribute that gives the “volume_level” but after a HA restart that attribute goes away until the next update from the Echo.
Is there any way to force an update of the volume without changing it? Or is it possible to somehow restore the last known state of the media_player entities after a restart?
I’m trying to use save current volume to be able to restore it after I turn it all the way up for any urgent announcements. If I save the volume_level after restart it says “None” because that attribute doesn’t yet exist.
No. We haven’t found any API access to show the media volume of a device if it’s not playing so until something is played, we can’t determine the volume to populate the field. As for restoring state, in theory HA should save and restore state. No idea why it doesn’t. Perhaps it’s only for non media player entities.
I agree, but how do you stop an echo that’s playing.
media_player.stop doesnt work.
I have to fire off an alexa routine.
I do all my automations in node red.
Have echo on the bathroom, close the door, alexa tells the time, tells a joke, reports the weather and plays a station from tunein. Attempts to do it in node red required, delays between each part that were either to short or too long, using the routine it just flows correctly. And i can stop the radio when the door is open and alexa says, are you going, you cant leaving me with that.
media_pause at least pauses it, but i get you and thats a fair point you mention. I just dont like to hassle through the alexa app, and i want to have as much as possible in one place, but alexa routines have their advantages.
Apparently I wasn’t patient enough because after doing some more testing and waiting around 15 minutes or so all of the volume_level attributes became populated again.
I’m not sure what triggers the update tho since i didn’t do anything with any of the Echos. they just suddenly went from not there to there.
So, I guess it’s not that big of a deal and I came up with a way to work around it by testing if the volume_level exists before restoring it and if it doesn’t just give it a default level at the mid-point so the automation doesn’t fail.
Echo devices are fairly chatty and eventually report their volume as part of that chatter. If you ever look at the websocket logs you’ll see all the messages.
Just noticed that version 2.5.3 is out and one of the changes mentions shopping list changes.
Can we display out Alexa shopping list in HA? I never knew that? Has anyone done this?
Thanks
mb
Unfortunately no. We’re just ignoring a message that includes the word shopping list.
1 Like
Is it possible to send images to the echo show during the notify process ?
Also now that the Fire Sticks can be sent messages from the Alexa app can we send notifications to the full screen just like the amazon app does ?
Thanks in advance
Evening everyone.
Seemingly out of the blue, tts on alexa now starts and ends every message with force unit selection.
So far Ive only tested it on my sonos beam, but it was working fine yesterday and i dont think there were any changes my end.
Anyone else experience this
1 Like
Just came on here to post the same thing. On all notify messages over any one on my echos (mix of dots and shows). Announcements are fine.
Same here. Weirded me out a bit when my house greeted me with that when I got home.
glad its not just me, I changed my router a couple of days ago and things are misbehaving a little.
Probably a change on amazons side
same here just started after updating community plug-in
Yup “force unit selection” is going nuts all over my house
1 Like