This app doesn’t retrieve its own metadata, so if you want the cast interface or media player card to show titles and/or images you will have to provide the data yourself. Media parametersĮxample values to cast BBC Radio 1 alias: "Cast BBC Sounds to My Chromecast" To cast media directly from a configured Plex server, set the fields as documented in the Plex integration and prepend the media_content_id with plex://: 'cast_plex_to_chromecast': playlist_id: Play video with media_id from this playlistĮxample values to cast the item at 'cast_supla_to_my_chromecast':.video/mp4, audio/mp3, image/jpeg, defaults to video/mp4.Įxample 'cast_bubbleupnp_to_my_chromecast':Īlias: "Cast a video to My Chromecast using BubbleUPNP" The BubbleUPNP app has similar functionality to the built in Default Media Receiver app, and can be used as a backup if the default app fails to play the media. To do so, media_content_type should be set to cast, and media_content_id should be a JSON dict with parameters for the app, including the app name. It’s possible to play with other apps than the default media receiver. # Play a netradio, with extra metadata provided: Subtitle: "By Blender Foundation, Licensed under the Creative Commons Attribution license"
#Cast wysiwyg sacn device movie
# Play a movie from the internet, with extra metadata provided: # Play a video file from the local network:Įxtra media metadata (for example title, subtitle, artist or album name) can be passed into the service and that will be shown on the Chromecast display.įor the possible metadata types and values check Google cast documentation > MediaInformation > metadata field. 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.
#Cast wysiwyg sacn device full
The following is a full configuration for a script that starts casting the downstairs tab of the lovelace-cast path (note that entity_id is specified under data and not for the service call): cast_downstairs_on_kitchen:Ĭhromecasts generally ignore DNS servers from DHCP and will instead use Google’s DNS servers, 8.8.8.8 and 8.8.4.4. The dashboard_path is the part of the Lovelace UI URL that follows the defined base_url, typically “lovelace”. A path has to be defined in your Lovelace YAML for each view, as outlined in the views documentation. The service takes the path of a Lovelace view and an entity ID of a Cast device to show the view on. You can use it by adding the Cast entity row to your Lovelace UI, or by calling the cast.show_lovelace_view service. Home Assistant has its own Cast application to show the Home Assistant UI on any Chromecast device. This option is only visible if advanced mode is enabled in your user profile. See the upstream documentation for more information.
If mDNS does not work in your network, the IP addresses of the Cast devices can be manually entered in the configuration as mentioned below. Make sure that your router has this feature enabled. Support for mDNS discovery in your local network is mandatory for automatic discovery.
0 kommentar(er)
