Maybe, Mine also turns on the porch light when it detects motion which is also instant,I would re-add the ring component again and redo the automations to try and track down the delay. How far is your router from the doorbell?
It’s not that far. Maybe less than 10m. RSSI in the app is in the green showing good signal. I contacted Ring support a few months back about something else and they insisted that my wifi was to blame. Seems to be a common answer with them. I have no issues with any other device on my network.
Unfortunately, I don’t think removing the component will do much. Not without removing any Ring specific dependencies that the component installs, and this is beyond my knowledge.
thanks Willy! And thanks for reminding me of the service menu, after all this time with HASS I still find myself setting up yaml lines to test things… 
is there anyway of adjusting the volume through a yaml command?
I’m using the media player as an alarm clock with a mix of tts messages and media but the tts is so much louder than the media it would be good to adjust these levels within the automation
To avoid the cloud server, The Hook up guy set up a simple doorbell but you would have to set up picture seperately…
This is supposed to work but I haven’t had a chance to test it yet:
- service: media_player.volume_set
data:
entity_id:
- media_player.computer_room_dot
- media_player.kitchen_dot
volume_level: 0.9
The volume levels are .1 to 1.
And the player has to be actually playing something for it to work. So call your play_media first then call volume_set.
I am getting lots of errors like this recently. I have VERSION 0.9.5 in the correct folder / sub folder. It has been working without any issues but this evening I am noticing this.
Any ideas?
OK…
I still haven’t been able to successfully change the volume on any Echo yet.
Here is the last iteration of the test script:
test_alexa_volume:
alias: Test Alexa Volume Control
sequence:
- service: media_player.alexa_tts
data_template:
entity_id: media_player.computer_room_dot
message: "Attention!. . . Attention!. . . This is a fairly long message to sample the volume that I'm saying things at. Next I will say the same thing only louder."
- delay: '00:00:10'
- service: media_player.play_media
data:
entity_id: media_player.computer_room_dot
media_content_id: "Silence - 5 seconds"
media_content_type: "AMAZON_MUSIC"
- service: media_player.volume_set
data:
entity_id: media_player.computer_room_dot
volume_level: 0.9
- delay: '00:00:06'
- service: media_player.alexa_tts
data_template:
entity_id: media_player.computer_room_dot
message: "Attention!. . . Attention!. . . This is a fairly long message to sample the volume that I'm saying things at. This should be the same message, only louder. Next it will be softer"
- delay: '00:00:12'
- service: media_player.play_media
data:
entity_id: media_player.computer_room_dot
media_content_id: "Silence - 5 seconds"
media_content_type: "AMAZON_MUSIC"
- service: media_player.volume_set
data:
entity_id: media_player.computer_room_dot
volume_level: 0.1
- delay: '00:00:06'
- service: media_player.alexa_tts
data_template:
entity_id: media_player.computer_room_dot
message: "Attention!. . . Attention!. . . This is a fairly long message to sample the volume that I'm saying things at. This should be the same message, only a lot more quiet."
All three messages are read out at the exact same volume so the volume set calls aren’t taking effect.
Any hints on what I’m doing wrong?
The echo cannot be in idle or standby mode when you try to change the volume
it’s not idle.
In the above script I have a test message play to get a volume baseline. I have it wait 10 seconds for the test message to complete.
Then I have it playing a 5 second blank track, then I immediately give it the volume_set call. Then I delay 6 seconds to allow for the blank track to finish playing then test the volume again with another message.
Then I repeat the process with a different volume level at the other end of the dial.
The volume never changes.
It is probably a timing issue, where the song is not started yet, or it’s not long enough. What happens if you just pause the echo in the middle of a normal song, and then try just sending a service call to change the volume from the developer panel? Does that work?
1 Like
I randomly started getting them as well on .81. They went away after I reconfigured the echo and I have not seen them again yet. If they pop up again, I can look into it.
I finally had a chance to test things and it works fine if you send the commands via the service call while a regular song is playing but when playing shorter stuff (like a 5 second silent track) then the timing issue is horrible.
Then I tried to use it in an automation with various time delays and it still works…kind of.
Sometimes it works. sometimes it doesn’t. And then if you add a TTS command or two into the mix then all bets are off.
It’s pretty unstable to reliably use in an automation. I’m hoping that I can get it reliable enough to at least make the volume reliably go to the max level at the beginning of an automation then I can fiddle with the lower volume stuff later.
Thanks for the help.
1 Like
If you find a silent track that is longer than five seconds, I can help you get something reliable working. Since I have the “prime unlimited” music membership, I don’t know which songs are not available to your membership level. Let me know if you find a longer silent track.
Thanks for the offer but I’ve used up to a 30 second track.
I’m pretty sure the volume up should work consistently enough. Then I can handle the setting the volume back to a “usual” level afterwards with another automation.
I was just playing around with one automation (and script too) setting the volume to different levels using shorter and longer tracks & delays and it just didn’t seem to like that method too much. The timing was a bear to get right in that case. If you let the silent track run and hit the volume in the middle it was OK but then you have to wait till that track times out before you can play a TTS or it will just skip it entirely and move on from there to the next step. then you have to figure out how long the TTS will be to delay long enough so that the next step doesn’t get skipped. It’s doable (I think…) but tedious.
TTS messages should work when a track is playing. I think you are wayy overthinking it. In my version, it starts the silent track and then pauses it right away, adjusts the volume, and plays the TTS message.
Ohhh…I didn’t think about starting then pausing in the automation to do the volume change. I know you mentioned it above but I never put the two together.
tho I did have some problems running a TTS while the silent track was playing. I think… Or maybe it was trying to start another TTS while another one was timing out. 
Time to do some more testing… 
hey justin_144
what exactly do you mean when you say “reconfigured the echo” ?
Thanks
This is really weird, i had to downgrade to 0.80.1 from full backup, then no more errors and Alexa is back
Hi all from Rome, Italy, and thanks everyone for the nice work.
I got this working on Raspberry, Hassbian 4.14.71 and HA 0.81.2.
My Echo is a new one vers.3, arrived two days ago.
The multimedia (radio etc) part works nicely.
The TTS instead is doing something weird: instead of declaring the “message” it gets, it uses it as a command: if I send on the alexa_tts service the message:“what time is it” I get the current time, and not, as I supposed, the phrase spoken. As a side effect, the strings non corresponding to legitimate commands are ignored. Of course this in Italian, as this is the language on Alexa setting.
I am sure I am missing something.
Many thanks again!!!
2 Likes