I did this last month with ~50 devices (from OZW). Wasnāt too painful.
1 Like
do you have your media files stored in the /media share? if so, you need to add the correct path including the media-source bit:
{% set path = 'media-source://media_source/local/sounds/sound_bites/' %}
if using the /config share and storing the files in the www folder, use
{% set path = '/local/sounds/sound_bites/'%}
{% set state = states('input_select.sound_bite') %}
{% set path = '/local/sounds/sound_bites/'%}
{% set sound_bite = state|slugify %}
{% set ext = '.mp3' %}
{{[path,sound_bite,ext]|join}}
try and experiment in the dev tools services
Iām unable to create an automaton thats is streaming media to my Google Nest Hub
What Iām I doing wrong?
3 Likes
Iām curious about āVersionā integration provides the same functionality. Certainly I can see all the information thatās relevant, but it doesnāt seem to include any āis there an update availableā. So do I have to make a template sensor now to accomplish the same thing?
Yes, the media path is correct. Everything worked in 2022.2, but selecting either the TTS or using the browser to find media does not play on the Google Home mini. The same media plays fine if I choose the browser as the media player, so I donāt think the problem is related to the media source.
well, its playing over all of my minis here, but you really need to be sure of the path in the service/script/automation.
On the /media share, there is no actual /local folder, like on the /config share, where the is mapped to /www
during the beta I had a bit of an issue, and wrote up this: Migrating media files from /config/local to /media
Developer Tools ā States:
Can you guess what āentity_idā is displayed here?
In 2022.3 the āEntityā field contains a āfriendly_nameā instead of entity_id.
Surely this field accepts entity_id - but why to show āfriendly_nameā here?
The name is just an attribute - it should be displayed below only.
I do not appreciate this kind of changes. It does not help new people to operate HA easily - it confuses people instead.
And what does the ā*ā mean?
12 Likes
As I said, I can use Google TTS from the media browser and play the audio on my browser, but if I select a mini, it plays the chime to indicate that itās active, but no sound is played. I can stream audio from other sources, so I know itās volume is up and not muted. Just checked the log and see that itās trying to stream from my local deviceās hostname (not the IP address and not the external URL). The google miniās use Googleās DNS, so they donāt know my local hostname.
Switching the internal URL to an IP address resolves this issue.
2022.3.0 breaks my Shelly integration, anyone else? I had to revert.
Ok, so this is the single best added feature over the span of 2 HA products. Itās almost the holly grail for my media casting desires.
Iāve waited almost 5 years, across 2 products (HomeSeer and now Home Assistant) for an easy to use method to cast playlists (Plex in this case) via an automation.
THANK YOU to those who put in the time and effort to make this happen, Iām sure it wasnāt easy.
2 Likes
for me the solution was to remove the old light integration and deinstall the addon in HACS
Plying Sonos favorites via new playmedia-selection in automations and scripts is working good.
But I wonder, why the old way is not working anymore. Didnāt see any deprecation warnings.
- service: media_player.select_source
data:
source: Lieder
target:
entity_id: media_player.sonos_abc
Is it deprecated? Did I miss an info?
Sonos Lieder im Abc: Error executing script. Error for call_service at pos 3: Error calling SonosMediaPlayerEntity.select_source on media_player.sonos_abc: HTTPConnectionPool(host='xx.xx.xx.xx', port=yy): Read timed out. (read timeout=9.5)
And make the images much smaller please! But besides that I like it very much. Already implemented some automations to play radio stations.
Got the same issue with the xiaomi vacuum card.
If you got any idea let me know 
I have observed it too.
Do you have a link to the issue so I can follow up ?