I have tried to add another action step to âturn onâ the media player, and I can hear them doing the âboinkâ sound, as they indicate that they are readyâŚ
But what am I missing here ? It should have been so simple
It should be entity_id: not entity:
Also when did you create the www folder in your installation? Have you restarted HA after creating it?
Here is my automation:
I followed the notes above.
Created www folder in /config/
Restarted Core
Created new automation in the UI. Saved. Clicked ârun actionsâ. Sometimes the Home speaker goes boink, so I know something is happening.
But the file never plays.
If I copy the content_idâs URL into a browser page, the track will play.
Whatâs wrong?
Sorry, trying again. I tried putting single backticks around it but it doesnât maintain the format⌠also tried âpreformattted textâ which inserts 3 backticks â that didnât work either.
Iâm not able to get the sound to play with my automation, but if I go to the Media Browser and play the sounds from âall.speakersâ, it works perfectly. When I try to replicate the behaviour in an automation, I just get the âboinkâ on sound from the Google speakers, but the audio doesnât play. My log shows that the speakers have been changed to âidleâ.
When I play the audio directly from the Media Browser, it shows âplayingâ, then changed to âidleâ in the logs.
If I enter the URL for the target sound, it gives me an ERR_SSL_PROTOCOL_ERROR. Maybe Iâm not entering it properly? Iâve tried with http and https.
Solved: After digging around, I found that I have to change the content id to: âmedia-source://media_source/local/filename.mp3â. I also changed content type to music.
For Sonos the file that worked for me was with 44100Hz bit rate, high bit rate did not work. I also placed a delay of 4sec for a 4 sec doorbell ring mp3 file, to avoid chopping of audio by next Sonos command. Files was placed under www folder: