231 lines
8.3 KiB
Plaintext
231 lines
8.3 KiB
Plaintext
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<title>Home Assistant Cast - FAQ</title>
|
|
<link rel="icon" href="/images/ha-cast-icon.png" type="image/png" />
|
|
<%= renderTemplate("../../../src/html/_style_base.html.template") %>
|
|
<style>
|
|
body {
|
|
background-color: #e5e5e5;
|
|
}
|
|
</style>
|
|
<meta property="fb:app_id" content="338291289691179" />
|
|
<meta property="og:title" content="FAQ - Home Assistant Cast" />
|
|
<meta property="og:site_name" content="Home Assistant Cast" />
|
|
<meta property="og:url" content="https://cast.home-assistant.io/" />
|
|
<meta property="og:type" content="website" />
|
|
<meta
|
|
property="og:description"
|
|
content="Frequently asked questions about Home Assistant Cast."
|
|
/>
|
|
<meta
|
|
property="og:image"
|
|
content="https://cast.home-assistant.io/images/google-nest-hub.png"
|
|
/>
|
|
<meta name="twitter:card" content="summary_large_image" />
|
|
<meta name="twitter:site" content="@home_assistant" />
|
|
<meta name="twitter:title" content="FAQ - Home Assistant Cast" />
|
|
<meta
|
|
name="twitter:description"
|
|
content="Frequently asked questions about Home Assistant Cast."
|
|
/>
|
|
<meta
|
|
name="twitter:image"
|
|
content="https://cast.home-assistant.io/images/google-nest-hub.png"
|
|
/>
|
|
</head>
|
|
<body>
|
|
<%= renderTemplate("../../../src/html/_js_base.html.template") %>
|
|
<%= renderTemplate("../../../src/html/_script_loader.html.template") %>
|
|
<hc-layout subtitle="FAQ">
|
|
<style>
|
|
a {
|
|
color: var(--primary-color);
|
|
}
|
|
</style>
|
|
<div class="card-content">
|
|
<p><a href="/">« Back to Home Assistant Cast</a></p>
|
|
</div>
|
|
|
|
<div class="section-header">What is Home Assistant Cast?</div>
|
|
<div class="card-content">
|
|
<p>
|
|
Home Assistant Cast allows you to show your Home Assistant data on a
|
|
Chromecast device and allows you to interact with Home Assistant on
|
|
Google Assistant devices with a screen.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="section-header">
|
|
What are the Home Assistant Cast requirements?
|
|
</div>
|
|
<div class="card-content">
|
|
<p>
|
|
Home Assistant Cast requires a Home Assistant installation that is
|
|
accessible via HTTPS (the url starts with "https://").
|
|
</p>
|
|
</div>
|
|
|
|
<div class="section-header">What is Home Assistant?</div>
|
|
<div class="card-content">
|
|
<p>
|
|
Home Assistant is worlds biggest open source home automation platform
|
|
with a focus on privacy and local control. You can install Home
|
|
Assistant for free.
|
|
</p>
|
|
<p>
|
|
<a href="https://www.home-assistant.io" target="_blank"
|
|
>Visit the Home Assistant website.</a
|
|
>
|
|
</p>
|
|
</div>
|
|
|
|
<div class="section-header" id="https">
|
|
Why does my Home Assistant needs to be served using HTTPS?
|
|
</div>
|
|
<div class="card-content">
|
|
<p>
|
|
The Chromecast only works with websites served over HTTPS. This means
|
|
that the Home Assistant Cast app that runs on your Chromecast is
|
|
served over HTTPS. Websites served over HTTPS are restricted on what
|
|
content can be accessed on websites served over HTTP. This is called
|
|
mixed active content (<a
|
|
href="https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content#Mixed_active_content"
|
|
target="_blank"
|
|
>learn more @ MDN</a
|
|
>).
|
|
</p>
|
|
<p>
|
|
The easiest way to get your Home Assistant installation served over
|
|
HTTPS is by signing up for
|
|
<a href="https://www.nabucasa.com" target="_blank"
|
|
>Home Assistant Cloud by Nabu Casa</a
|
|
>.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="section-header" id="https">
|
|
Why does Home Assistant Cast require me to authorize my Home Assistant
|
|
instance?
|
|
</div>
|
|
<div class="card-content">
|
|
<p>
|
|
You're currently looking at the Home Assistant Cast launcher
|
|
application. This is a standalone application to launch Home Assistant
|
|
Cast on your Chromecast. Because Chromecasts do not allow us to log in
|
|
to Home Assistant, we need to supply authentication to it from the
|
|
launcher. This authentication is obtained when you authorize your
|
|
instance. Your authentication credentials will remain in your browser
|
|
and on your Cast device.
|
|
</p>
|
|
<p>
|
|
Your authentication credentials or Home Assistant url are never sent
|
|
to the Cloud. You can validate this behavior in
|
|
<a
|
|
href="https://github.com/home-assistant/frontend/tree/dev/cast"
|
|
target="_blank"
|
|
>the source code</a
|
|
>.
|
|
</p>
|
|
<p>
|
|
The launcher application exists to make it possible to use Home
|
|
Assistant Cast with older versions of Home Assistant.
|
|
</p>
|
|
<p>
|
|
Starting with Home Assistant 0.97, Home Assistant Cast is also built
|
|
into the Lovelace UI as a special entities card row. Since the
|
|
Lovelace UI already has authentication, you will be able to start
|
|
casting right away.
|
|
</p>
|
|
</div>
|
|
|
|
<div class="section-header">What does Home Assistant Cast do?</div>
|
|
<div class="card-content">
|
|
<p>
|
|
Home Assistant Cast is a receiver application for the Chromecast. When
|
|
loaded, it will make a direct connection to your Home Assistant
|
|
instance.
|
|
</p>
|
|
<p>
|
|
Home Assistant Cast is able to render any of your Lovelace views on
|
|
your Chromecast. Things that work in Lovelace in Home Assistant will
|
|
work in Home Assistant Cast:
|
|
</p>
|
|
<ul>
|
|
<li>Render Lovelace views, including custom cards</li>
|
|
<li>
|
|
Real-time data stream will ensure the UI always shows the latest
|
|
state of your house
|
|
</li>
|
|
<li>Navigate between views using navigate actions or weblinks</li>
|
|
<li>
|
|
Instant updates of the casted Lovelace UI when you update your
|
|
Lovelace configuration.
|
|
</li>
|
|
</ul>
|
|
<p>Things that currently do not work:</p>
|
|
<ul>
|
|
<li>
|
|
Live videostreams using the streaming integration
|
|
</li>
|
|
<li>Specifying a view with a single card with "panel: true".</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div class="section-header" id="https">
|
|
How do I change what is shown on my Chromecast?
|
|
</div>
|
|
<div class="card-content">
|
|
<p>
|
|
Home Assistant Cast allows you to show your Lovelace view on your
|
|
Chromecast. So to edit what is shown, you need to edit your Lovelace
|
|
UI.
|
|
</p>
|
|
<p>
|
|
To edit your Lovelace UI, open Home Assistant, click on the three-dot
|
|
menu in the top right and click on "Configure UI".
|
|
</p>
|
|
</div>
|
|
|
|
<div class="section-header" id="browser">
|
|
What browsers are supported?
|
|
</div>
|
|
<div class="card-content">
|
|
<p>
|
|
Chromecast is a technology developed by Google, and is available on:
|
|
</p>
|
|
<ul>
|
|
<li>Google Chrome (all platforms except iOS)</li>
|
|
<li>Microsoft Edge (all platforms except iOS)</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div class="section-header">Why do some custom cards not work?</div>
|
|
<div class="card-content">
|
|
<p>
|
|
Home Assistant needs to be configured to allow Home Assistant Cast to
|
|
load custom cards. Starting with Home Assistant 0.97, this is done
|
|
automatically. If you are on an older version, or have manually
|
|
configured CORS for the HTTP integration, add the following to your
|
|
configuration.yaml file:
|
|
</p>
|
|
<pre>
|
|
http:
|
|
cors_allowed_origins:
|
|
- https://cast.home-assistant.io</pre
|
|
>
|
|
<p>
|
|
Some custom cards rely on things that are only available in the normal
|
|
Home Assistant interface. This requires an update by the custom card
|
|
developer.
|
|
</p>
|
|
<p>
|
|
If you're a custom card developer: the most common mistake is that
|
|
LitElement is extracted from an element that is not available on the
|
|
page.
|
|
</p>
|
|
</div>
|
|
</hc-layout>
|
|
</body>
|
|
</html>
|