The current playing track stops but then nothing happens. When i check the HA logs:
> Error while executing automation automation.zigbee_deurbel. Invalid data for call_service at pos 1: not a valid value for dictionary value @ data['entity_id']
> Error executing script script.sonos_doorbell. Invalid data for call_service at pos 4: not a valid value for dictionary value @ data['entity_id']
I don’t know how to fix the error’s so maby someone can help? I thinks its my code but im not sure. When i go to https://notgoingtotellyou.duckdns.org:8123/local/bell-effect.mp3 I do hear the sound of the mp3 and when I test it without script etc the Sonos device plays the tune:
- service: media_player.play_media
data:
entity_id: media_player.sonos_woonkamer
media_content_id: https://notgoingtotellyou.duckdns.org:8123/local/bell-effect.mp3
media_content_type: music
In what local directory are you punting your mp3 files to play? I made a folder inside the config folder to keep the audio files organized but I can’t get the system to play anything to the Sonos speakers. I’m trying to limit my configuration to local polling as much as possible, and no access from the outside. If I’m not home I access homeassistant through my VPN firewall, so I don’t use duck DNS or SSL on my setup.
You’ll need to create a folder called “www” in the folder where your configuration.yaml lives. And put your mp3 in there. Then you can use this url to link in your script:
I made 2 separate scripts using your example. First to give the MP3 as a variable so I can use the same script for multiple mp3 files (doorbell, burglar alarm and whatever comes to mind). And a second to play the MP3 in all rooms.
finally… rather then call out indiviaully entities, could you have a group?
then every time you add a new Sonos speaker, you can add it to the group and it will flow into this?
You set it in the script so you’re sure that in the following steps you’re talking to the master and not to a slave spreaker. That’s also the reason they are first unjoined and then joined again.
media_player.living_room is a group containing 2 speakers. They are merged by Sonos because they are in the same room.
HomeBee, my use case was slightly different, but my dumbed down solution might help you, if you’re still looking.
I’m running both S1 and S2 Sonos systems in the house so considered adjusting this to serve the file to both an S1 group and an S2 group, but the S1 and S2 grouping speeds seem a bit different and variable depending on what combination of speakers are grouped at the time, so the sync wasn’t ever going to be perfect with the mix of the two systems.
Since that’s the case, I decided not to worry about the sound being sync’ed at all.
My script dumbed down the original and removes the joining of different rooms and just defines the speakers (a mix of S1 and S2) that I want the sound to play on as a comma separated list in the entity_id: each time it is referenced. e.g.
It works well and the sync is only a bit out. The main aim was to hear the door bell in key rooms throughout the house, so job done.
I haven’t had the inclination to test if this might be quicker than joining all the speakers into their S1 and S2 groups and then playing the sound through the two groups, but I wonder if this way each speaker starts playing the chime when it’s ready, rather than waiting for the slowest speaker to group up before playing. Dunno.
