![]() It’s possible to play with other apps than the default media receiver. # Play a netradio, with extra metadata provided: service : media_ay_media target : entity_id : media_player.chromecast data : media_content_type : " audio/mp3" media_content_id : " " extra : metadata : metadataType : 3 title : " Radio TILOS" artist : " LIVE" images : - url : " " Casting with other apps You need to set the media_content_id to the media URL and media_content_type to a matching content type. You can play MP3 streams like net radios, FLAC files or videos from your local network with the media_ay_media service, as long as the media is accessible via HTTP(S). ![]() Chromecast devices do not support other protocols like DLNA or playback from an SMB file share. The media needs to be accessible via HTTP(S). As a rule of thumb, if a Chrome browser can play a media file a Chromecast will be able to handle that too. ![]() Using the built in media player app (Default Media Receiver)Ĭhromecasts can play many kinds of modern media (image/audio/video) formats using the built in app Default Media Receiver. Note that the Home Assistant Cloud will not be used if an external_url is configured. This is important when casting TTS or local media sources the cast integration will cast such media from the external_url if configured, otherwise from the Home Assistant Cloud if configured, otherwise from the internal_url. A hostname which can’t be publicly resolved, e.g. This means media URLs must either be specifying the IP-address of the server directly, e.g. Chromecasts generally ignore DNS servers from DHCP and will instead use Google’s DNS servers, 8.8.8.8 and 8.8.4.4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |