If needed, you can go here for additional instructions: Connect streaming services on the mobile app Log into your streaming service account using your credentials for that specific service.
#Cast to chromecast from android android#
Running without it is not supported by the Home Assistant project, and will cause this integration to be unable to discover to your Cast devices.You can use VidAngel with your basic Chromecast dongle by casting to it from our Apple or Android mobile app.īefore starting the casting process, make sure you have the most updated version of our app on your mobile device and that your mobile device is on the same WIFI as your Chromecast, (see Cast to your TV from the mobile app). When running the Home Assistant Container in Docker, make sure it is running with host network mode. If it is not possible, it’s necessary to either enable mDNS forwarding between the subnets or to configure a list of known hosts. Cast devices and Home Assistant on different subnetsĬast devices can only be automatically discovered if they are on the same subnet as Home Assistant because mDNS packets are not routed across subnets.Īutomatic discovery in setups with cast devices on a different subnet than Home Assistant is not recommended and not supported. The Zeroconf integration has some configuration options which impact mDNS routing. The Google Cast integration relies on the Zeroconf integration for mDNS discovery. If none of the tips in this section helps, the recommended solution is to ensure all cast devices have static IPs assigned to them and configure a list of known hosts. MDNS relies on UDP multicast, which may fail for various reasons. ' cast_youtube_to_my_chromecast' : alias : " Cast YouTube to My Chromecast" sequence : - target : entity_id : media_player.my_chromecast data : media_content_type : cast media_content_id : ' ' service : media_ay_media Troubleshooting automatic discovery With b09w70r2 being the media_id Media parameters Note: Media ID is NOT the 8 digit alphanumeric in the URL, it can be found by right-clicking the playing video. 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. 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: 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 kommentar(er)
