jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-17 14:26:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Paulus Schoutsen 2018-08-20 16:20:34 +02:00
commit cec178bdce
20 changed files with 527 additions and 62 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
_config.yml
View File

@ -141,14 +141,14 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 75
current_patch_version: 3
date_released: 2018-08-09
current_minor_version: 76
current_patch_version: 1
date_released: 2018-08-19
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.
# Major release:
patch_version_notes: "#release-0753---august-9"
patch_version_notes: "#release-0761---august-19"
# Minor release (Example #release-0431---april-25):
# Date we moved to Discourse for comments

7
source/_addons/bluetooth_bcm43xx.markdown
View File

@ -9,13 +9,14 @@ sharing: true
footer: true
---
Start this add-on to activate the BCM43xx Bluetooth chipset.
Start this add-on to activate the BCM43xx Bluetooth chipset in the old ResinOS based builds. If you first installed Hass.io after mid July 2018 then you will have a HassOS based system.
You can identify the base of your system by looking in the System tab of the Hass.io menu.
<p class='note warning'>
This is not required on HassOS based Hass.io installs and should not be installed.
This is not required on the new HassOS based Hass.io installs and should not be installed.
</p>
Supported platforms:
- Raspberry Pi 3

4
source/_components/climate.ecobee.markdown
View File

@ -245,7 +245,9 @@ canceled.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. Else targets all.
| `hold_mode` | no | 'temp', 'home', 'away', 'sleep', etc., None
| `hold_mode` | no | `temp`, `home`, `away`, `sleep`, `None`, `smart1`, `smart2`, etc.
NOTE: If you create custom hold modes (also known as "Comfort Settings") on your ecobee.com dashboard, their hold_modes are `smart1`, `smart2`, `smart3`, etc. The number for each custom mode should match the mode's icon on your ecobee.com dashboard. Also note that the mode numbers/icons in the ecobee mobile app *may not match* the numbers/icons from the ecobee.com web dashboard. The ones on the website are the ones you shoud use to determine the correct `smartX` hold_mode IDs.
### {% linkable_title Service `set_temperature` %}

4
source/_components/dyson.markdown
View File

@ -27,9 +27,9 @@ dyson:
language: YOUR_DYSON_ACCOUNT_LANGUGAGE
devices:
- device_id: DEVICE_ID_1 # eg. Serial number: XXX-XX-XXXXXXXX
device_ip: DEVICE_ID_1
device_ip: DEVICE_IP_1
- device_id: DEVICE_ID_2
device_ip: DEVICE_ID_2
device_ip: DEVICE_IP_2
```
Configuration variables:

7
source/_components/http.markdown
View File

@ -69,7 +69,7 @@ trusted_proxies:
required: false
type: string, list
use_x_forwarded_for:
description: "Enable parsing of the `X-Forwarded-For` header, passing on the client's correct IP address in proxied setups. You **must** also whitelist trusted proxies using the `trusted_proxies` setting below for this to work. Non-whitelisted requests with this header will be considered IP spoofing attacks, and the header will, therefore, be ignored."
description: "Enable parsing of the `X-Forwarded-For` header, passing on the client's correct IP address in proxied setups. You **must** also whitelist trusted proxies using the `trusted_proxies` setting above for this to work. Non-whitelisted requests with this header will be considered IP spoofing attacks, and the header will, therefore, be ignored."
required: false
type: boolean
default: false
@ -87,6 +87,11 @@ login_attempts_threshold:
required: false
type: integer
default: -1
ssl_profile:
description: The [Mozilla SSL profile](https://wiki.mozilla.org/Security/Server_Side_TLS) to use. Only lower if you are experiencing integrations causing SSL handshake errors.
required: false
type: string
default: modern
{% endconfiguration %}
The sample below shows a configuration entry with possible values:

28
source/_components/lutron_caseta.markdown
View File

@ -25,9 +25,9 @@ The currently supported Caseta devices are:
- Scenes as Home Assistant [scenes](/components/scene.lutron_caseta/)
- Lutron shades as Home Assistant [covers](/components/cover.lutron_caseta/)
When configured, the `lutron_caseta` component will automatically discover the currently supported devices as setup in the Lutron Smart Bridge. The name assigned in the Lutron mobile app will be used to form the `entity_id` used in Home Assistant. e.g., a dimmer called 'Bedroom Lamp' becomes `light.bedroom_lamp` in Home Assistant.
When configured, the `lutron_caseta` component will automatically discover the currently supported devices as setup in the Lutron Smart Bridge. The name assigned in the Lutron mobile app will be used to form the `entity_id` used in Home Assistant. e.g., a dimmer called 'Lamp' in a room called 'Bedroom' becomes `light.bedroom_lamp` in Home Assistant.
To use Lutron Caseta devices in your installation, you must first log in to your Lutron account and generate a certificate that allows Home Assistant to connect to your bridge. This can be accomplished by downloading and executing [this script](/assets/get_lutron_cert.zip), which will generate three files: caseta.key, caseta.crt, caseta-bridge.crt when you run it. See the instructions at the top of the script for more information.
To use Lutron Caseta devices in your installation, you must first log in to your Lutron account and generate a certificate that allows Home Assistant to connect to your bridge. This can be accomplished by downloading and executing [get_lutron_cert.py](https://github.com/gurumitts/pylutron-caseta/blob/master/get_lutron_cert.py), which will generate three files: caseta.key, caseta.crt, caseta-bridge.crt when you run it. See the instructions at the top of the script for more information.
Once you have the three necessary files, place them in your configuration directory and add the following to your `configuration.yaml`:
@ -40,12 +40,24 @@ lutron_caseta:
ca_certs: caseta-bridge.crt
```
Configuration variables:
- **host** (*Required*): The IP address of the Lutron Smart Bridge.
- **keyfile** (*Required*): The private key that Home Assistant will use to authenticate to the bridge.
- **certfile** (*Required*): The certificate chain that Home Assistant will use to authenticate to the bridge.
- **ca_certs** (*Required*): The list of certificate authorities (usually only one) that Home Assistant will expect when connecting to the bridge.
{% configuration %}
host:
required: true
description: The IP address of the Lutron Smart Bridge.
type: string
keyfile:
required: true
description: The private key that Home Assistant will use to authenticate to the bridge.
type: string
certfile:
required: true
description: The certificate chain that Home Assistant will use to authenticate to the bridge.
type: string
ca_certs:
required: true
description: The list of certificate authorities (usually only one) that Home Assistant will expect when connecting to the bridge.
type: string
{% endconfiguration %}
<p class='note'>
It is recommended to assign a static IP address to your Lutron Smart Bridge. This ensures that it won't change IP address, so you won't have to change the `host` if it reboots and comes up with a different IP address.

1
source/_components/media_player.panasonic_viera.markdown
View File

@ -29,6 +29,7 @@ Currently known supported models:
- TX-P42STW50
- TX-P50GT30Y
- TX-P50GT60E
- TH-32ES500
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/blob/next/source/_components/media_player.panasonic_viera.markdown).

23
source/_components/panel_custom.markdown
View File

@ -12,29 +12,34 @@ ha_category: Front end
ha_release: 0.26
---
The `panel_custom` support allows you to add additional panels to your Home Assistant frontend. The panels are listed in the sidebar if wished and can be highly customized.
The `panel_custom` support allows you to add additional panels to your Home Assistant frontend. The panels are listed in the sidebar if wished and can be highly customized. See the developer documentation on [instructions how to build your own panels](https://developers.home-assistant.io/docs/en/frontend_creating_custom_panels.html).
To enable customized panels in your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry for https://github.com/home-assistant/example-custom-config/blob/master/panels/hello_world.html
# Example configuration.yaml entry
panel_custom:
- name: todomvc
- name: my-panel
sidebar_title: TodoMVC
sidebar_icon: mdi:work
url_path: my-todomvc
webcomponent_path: /home/hass/hello.html
js_url: /local/my-panel.js
config:
who: world
```
<p class='note'>
Store your custom panels in `<config>/www` to make them available in the frontend at the path `/local`.
</p>
Configuration variables:
- **name** (*Optional*): Name of the panel.
- **name** (*Required*): Name of the web component that renders your panel.
- **sidebar_title** (*Optional*): Friendly title for the panel in the sidebar. Omitting it means no sidebar entry (but still accessible through the URL).
- **sidebar_icon** (*Optional*): Icon for entry. Pick an icon that you can find on [materialdesignicons.com](https://materialdesignicons.com/) to use for your input and prefix the name with `mdi:`. For example `mdi:car`, `mdi:ambulance`, or `mdi:motorbike`.
- **url_path** (*Optional*): The URL your panel will be available on. If omitted will default to the panel name.
- **webcomponent_path** (*Optional*): The path to your component. If omitted will default to `<config dir>/panels/<component name>.html`
- **url_path** (*Optional*): The URL your panel will be available on in the frontend. If omitted will default to the panel name.
- **js_url** (*Required*): The URL that contains the JavaScript of your panel.
- **config** (*Optional*): Configuration to be passed into your web component when being instantiated.
- **embed_iframe** (*Optional*): Set to `true` to embed panel in iframe. This is necessary if the panel is panel is using the React framework or if it contains conflicting web components.
- **trust_external_script** (*Optional*): By default the user has to confirm before loading a script from an external source. Setting this to `true` will omit this confirmation.
- **webcomponent_path** (*Optional* *DEPRECATED*): The HTML path to your component. If omitted will default to `<config dir>/panels/<component name>.html`

28
source/_components/sensor.mold_indicator.markdown
View File

@ -27,12 +27,28 @@ sensor:
calibration_factor: 2.0
```
Configuration variables:
- **indoor_temp_sensor** (*Required*): The entity ID of the indoor temperature sensor.
- **indoor_humidity_sensor** (*Required*): The entity ID of the indoor humidity sensor.
- **outdoor_temp_sensor** (*Required*): The entity ID of the outdoor temperature sensor.
- **calibration_factor** (*Required*): Needs to be calibrated to the critical point in the room.
{% configuration %}
name:
description: The name of the sensor.
required: false
type: string
indoor_temp_sensor:
description: The entity ID of the indoor temperature sensor.
required: true
type: string
indoor_humidity_sensor:
description: The entity ID of the indoor humidity sensor.
required: true
type: string
outdoor_temp_sensor:
description: The entity ID of the outdoor temperature sensor.
required: true
type: string
calibration_factor:
description: Needs to be calibrated to the critical point in the room.
required: true
type: float
{% endconfiguration %}
In this case, the weather forecast temperature sensor is used for the outside temperature.

33
source/_components/sensor.worldtidesinfo.markdown
View File

@ -14,6 +14,12 @@ ha_release: 0.52
The `worldtidesinfo` sensor platform uses details from [World Tides](https://www.worldtides.info/) to provide information about the prediction for the tides for any location in the world.
## {% linkable_title Setup %}
Get your API key from your account at [https://www.worldtides.info/](https://www.worldtides.info/).
## {% linkable_title Configuration %}
To use this sensor, add the following to your `configuration.yaml` file:
```yaml
@ -23,10 +29,25 @@ sensor:
api_key: YOUR_API_KEY
```
Configuration variables:
- **api_key** (*Required*): Your API key for https://www.worldtides.info/.
- **name** (*Optional*): Name to use in the frontend.
- **latitude** (*Optional*): Latitude of the location to display the tides. Defaults to the latitude in your `configuration.yaml` file.
- **longitude** (*Optional*): Longitude of the location to display the tides. Defaults to the longitude in your `configuration.yaml` file.
{% configuration %}
api_key:
description: Your API key.
required: true
type: string
name:
description: Name to use in the frontend.
required: false
type: string
default: WorldTidesInfo
latitude:
description: Latitude of the location to display the tides.
required: false
type: float
default: "The latitude in your `configuration.yaml` file."
longitude:
description: Longitude of the location to display the tides.
required: false
type: float
default: "The longitude in your `configuration.yaml` file."
{% endconfiguration %}

3
source/_docs/configuration/basic.markdown
View File

@ -20,6 +20,9 @@ homeassistant:
unit_system: metric
time_zone: America/Los_Angeles
name: Home
whitelist_external_dirs:
- /usr/var/dumping-ground
- /tmp
```
Configuration variables:

2
source/_docs/ecosystem/appdaemon.markdown
View File

@ -107,4 +107,4 @@ Of course, if I wanted to make this App or its predecessor reusable, I would hav
In addition, Apps can write to `AppDaemon`'s log files, and there is a system of constraints that allows you to control when and under what circumstances Apps and callbacks are active to keep the logic clean and simple.
For full installation instructions, see the [AppDaemon Project Documentation pages](http://appdaemon.readthedocs.io/en/stable/).
For full installation instructions, see the [AppDaemon Project Documentation pages](http://appdaemon.readthedocs.io/en/stable/). If you're using Hassbian, then the [Hassbian scripts](https://github.com/home-assistant/hassbian-scripts/blob/dev/docs/appdaemon.md) make it easy to install.

14
source/_docs/ecosystem/backup/backup_github.markdown
View File

@ -42,27 +42,29 @@ $ sudo apt-get update
$ sudo apt-get install git
```
### {% linkable_title Step 2: Creating %} `.gitignore`
### {% linkable_title Step 2: Creating `.gitignore` %}
<p class='note warning'>
Before creating and pushing your Home Assistant configuration to GitHub, please make sure to follow the `secrets.yaml` best practice mentioned above and scrub your configuration for any passwords or sensitive information.
</p>
Creating a `.gitignore` file in your repository will tell git which files NOT to push to the GitHub server. This should be used to prevent publishing sensitive files to the public. It should contain a list of filenames and pattern matches. This list should include at least your `secrets.yaml` file, device configuration files, and the Home Assistant database/directory structure. The `.gitignore` file should be placed in your Home Assistant directory.
Creating a `.gitignore` file in your repository will tell git which files NOT to push to the GitHub server. This should be used to prevent publishing sensitive files to the public. It should contain a list of filenames and pattern matches. This list should include at least your `secrets.yaml` file, device configuration files, and the Home Assistant database/directory structure. The `.gitignore` file should be placed in the root of your Home Assistant configuration directory: `<config dir/.gitignore`.
Here is an example that will include your `.gitignore` file, a `scenes` directory, and all .yaml files except for `secrets.yaml` and `known_devices.yaml`. All other files will be excluded.
`.gitignore`
Here is an example that will ignore everything but your YAML configuration.
```bash
# Example .gitignore file for your config dir
*
!*.yaml
!scenes
!.gitignore
secrets.yaml
known_devices.yaml
```
<p class='note'>
You might read this guide too late and accidentally already have your secrets published. It is not enough to just remove them with a new commit. Git is a version control system and keeps history. You need to delete your repository and start a new one. Also change all passwords and revoke the API keys that were public.
</p>
More information on the layout of the file can be found in the [.gitignore manual](https://git-scm.com/docs/gitignore).
### {% linkable_title Step 3: Preparing your Home Assistant directory for GitHub %}

4
source/_docs/ecosystem/hadashboard.markdown
View File

@ -37,6 +37,4 @@ HADashboard is a modular, skinnable dashboard for [Home Assistant](/) that is in
Glassic Theme
</p>
For full installation instructions see the HADashboard section in the [AppDaemon Project Documentation](http://appdaemon.readthedocs.io/en/stable/DASHBOARD_INSTALL.html)
For full installation instructions see the HADashboard section in the [AppDaemon Project Documentation](http://appdaemon.readthedocs.io/en/stable/DASHBOARD_INSTALL.html). If you're using Hassbian, then the [Hassbian scripts](https://github.com/home-assistant/hassbian-scripts/blob/dev/docs/appdaemon.md) make it easy to install AppDaemon.

12
source/_docs/mqtt/broker.markdown
View File

@ -14,7 +14,7 @@ The MQTT component needs you to run an MQTT broker for Home Assistant to connect
### {% linkable_title Embedded broker %}
Home Assistant contains an embedded MQTT broker. If no broker configuration is given, the [HBMQTT broker](https://pypi.python.org/pypi/hbmqtt) is started and Home Assistant connects to it. Embedded broker default configuration:
Home Assistant contains an embedded MQTT broker called [HBMQTT](https://pypi.python.org/pypi/hbmqtt). If you don't have an MQTT broker, you can configure this one to be used. If configured, Home Assistant will automatically connect to it.
| Setting | Value |
| -------------- | ----- |
@ -22,17 +22,19 @@ Home Assistant contains an embedded MQTT broker. If no broker configuration is g
| Port | 1883 |
| Protocol | 3.1.1 |
| User | homeassistant |
| Password | no default value |
| Password | _password set under mqtt settings_ |
| Websocket port | 8080 |
Since release 0.76, the embedded broker does not use your [API password](/components/http/) as the default password. The MQTT component will fail to set up if you have API password configured, but don't have MQTT password configured as in the following example.
```yaml
# Example configuration.yaml entry
mqtt:
password: YOUR_MQTT_PASSWORD
password: hello
```
<p class='note'>
Before release 0.76, the embedded broker would use your API password as a password to the MQTT user. This is no longer the case.
</p>
<p class='note warning'>
There is [an issue](https://github.com/beerfactory/hbmqtt/issues/62) with the HBMQTT broker and the WebSocket connection that is causing a memory leak. If you experience this issue, consider using another broker like Mosquitto.
</p>

2
source/_docs/scripts/conditions.markdown
View File

@ -163,7 +163,7 @@ The template condition will test if the [given template][template] renders a val
```yaml
condition:
condition: template
value_template: '{% raw %}{{ states.device_tracker.iphone.attributes.battery > 50 }}{% endraw %}'
value_template: "{% raw %}{{ state_attr('device_tracker.iphone', 'battery') > 50 }}{% endraw %}"
```
Within an automation, template conditions also have access to the `trigger` variable as [described here][automation-templating].

392
source/_posts/2018-08-17-release-76.markdown Normal file
View File

@ -0,0 +1,392 @@
---
layout: post
title: "0.76: Auth almost done, FleetGo, PJLink, RMV public transport"
description: "The boys and girls in our virtual HQ have been working hard on creating yet another great release."
date: 2018-08-17 00:01:00
date_formatted: "August 17, 2018"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Release-Notes
og_image: /images/blog/2018-08-0.76/components.png
---
<p class='note'>
This release has a migration, initial startup can take ~20 minutes (depends on size DB)
</p>
This release includes a database migration to allow us to store context in the database. This will make it possible in the future to introduce attribution. For example, we'll be able to say which user opened the garage door or which automation triggered the party mode at 3am.
<a href='/components/#version/0.76'><img src='/images/blog/2018-08-0.76/components.png' style='border: 0;box-shadow: none;'></a>
The auth system is entering release candidate status 🎉. If nothing major is found, it will be enabled by default starting the next release (0.77) with backwards compatability modus turned on. If you want to get ahead of the pack, you can already easily enable it now:
```yaml
homeassistant:
# add this part
auth_providers:
- type: homeassistant
# uncomment this to enable backwards compatible API password support
# - type: legacy_api_password
```
For iOS users, your frontend should be a lot faster. We had an issue that forced us to serve the frontend in compatability mode, which is slower. We haven't been able to solve [the issue](https://bugs.webkit.org/show_bug.cgi?id=174629), but found a workaround. Race on 🏎.
Warning. If you are using the internal MQTT broker, we've had to make a change how the password is set. In the past it would automatically start the broker with the user `homeassistant` and a password equal to the API password. This is no longer the case and you need to configure it yourself now:
```yaml
mqtt:
password: mypass
```
## {% linkable_title New Platforms %}
- deCONZ - support for power plugs ([@Kane610] - [#15752]) ([deconz docs]) ([light.deconz docs]) ([switch.deconz docs]) (breaking change) (new-platform)
- RitAssist / FleetGO support ([@depl0y] - [#15780]) ([device_tracker docs]) (new-platform)
- Add support for OpenUV binary sensors and sensors ([@bachya] - [#15769]) ([openuv docs]) ([binary_sensor.openuv docs]) ([sensor.openuv docs]) (new-platform)
- Add Enphase Envoy component ([@jesserizzo] - [#15081]) ([sensor.enphase_envoy docs]) (new-platform)
- Add media_player.dlna_dmr component ([@StevenLooman] - [#14749]) ([media_player.dlna_dmr docs]) (new-platform)
- Add PJLink media player platform ([@benoitlouy] - [#15083]) ([media_player.pjlink docs]) (new-platform)
- Add RMV public transport sensor ([@cgtobi] - [#15814]) ([sensor.rmvtransport docs]) (new-platform)
## {% linkable_title New Features %}
- Add and restore context in recorder ([@balloob] - [#15859]) (new-feature)
## {% linkable_title Release 0.76.1 - August 19 %}
- No longer show "Store login" on each login when using API password ([@balloob])
- Add forgiving add column ([@balloob] - [#16057])
- Tuya fix login problem and add login platform param ([@huangyupeng] - [#16058]) ([tuya docs])
- Add notify platforms to loaded components ([@balloob] - [#16063]) ([notify docs])
- Column syntax fix + Add a file if migration in progress ([@balloob] - [#16061])
[#16057]: https://github.com/home-assistant/home-assistant/pull/16057
[#16058]: https://github.com/home-assistant/home-assistant/pull/16058
[#16061]: https://github.com/home-assistant/home-assistant/pull/16061
[#16063]: https://github.com/home-assistant/home-assistant/pull/16063
[@balloob]: https://github.com/balloob
[@huangyupeng]: https://github.com/huangyupeng
[notify docs]: /components/notify/
[tuya docs]: /components/tuya/
## {% linkable_title If you need help... %}
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
## {% linkable_title Reporting Issues %}
Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
<!--more-->
## {% linkable_title Breaking Changes %}
- Keenetic NDMS: user needs to have access to the TelNet interface ([@foxel] - [#15511]) ([device_tracker docs]) (breaking change)
- openweathermap: wind speed is now correctly in km/h (fixes #15710) ([@fabaff] - [#15740]) ([weather.openweathermap docs]) (breaking change)
- Remove Telstra notifiy component: This API has been decomissioned on the 31st of May 2018 by Telstra ([@dgomes] - [#15757]) ([notify docs]) (breaking change)
- deCONZ - support for power plugs. Power plugs that are of type "On/Off plug-in unit" and "Smart plug" (Osram and Innr among others) will now be switches instead of lights. Entities will be found as switch.entity_id instead of light.entity_id. ([@Kane610] - [#15752]) ([deconz docs]) ([light.deconz docs]) ([switch.deconz docs]) (breaking change) (new-platform)
- HTTP: Make sure use_x_forward_for and trusted_proxies must be configured together ([@awarecan] - [#15804]) ([http docs]) (breaking change)
- Velbus: Breaking changes include auto-discovery support so that you don't need to specify modules manually anymore in the configuration file, but just load the velbus component which will automatically load the switch and binary_sensor platforms. In addition, the fan and light platforms are removed since these should be modeled with template platform based on velbus switches. ([@thomasdelaet] - [#13742]) ([velbus docs]) ([binary_sensor.velbus docs]) ([switch.velbus docs]) (breaking change)
- Facebox: Events are no longer fired when a face is taught, as these are unnecessary and the info they convey is already in the logs. ([@robmarkcole] - [#15439]) ([image_processing.facebox docs]) (breaking change)
- AMCrest switch: Fix for multiple camera switches naming of entity. May change switch entity_id. Please check your automation and update the identity-id if you have previously assigned a name to your camera as it appends the name of the camera to the switch id. ([@rafale77] - [#14028]) ([switch.amcrest docs]) (breaking change)
- MQTT embedded broker will no longer rely on HTTP API password to automatically configure itself. You need to set own password. ([@awarecan] - [#15929]) ([mqtt docs]) (breaking change) (beta fix)
- Remove remote.API from core.Config. Might break custom components if they rely on hass.config.api ([@awarecan] - [#15951]) ([http docs]) (breaking change) (beta fix)
## {% linkable_title Beta Fixes %}
- Upgrade pymysensors to 0.17.0 ([@MartinHjelmare] - [#15942]) ([mysensors docs]) (beta fix)
- Deprecate remote.api ([@balloob] - [#15955]) (beta fix)
- Added error handling for sense API timeouts ([@kbickar] - [#15789]) ([sensor.sense docs]) (beta fix)
- Add context to login flow ([@awarecan] - [#15914]) ([auth docs]) (beta fix)
- MQTT embedded broker has to set its own password. ([@awarecan] - [#15929]) ([mqtt docs]) (breaking change) (beta fix)
- Fix issue when reading worxlandroid pin code ([@GotoCode] - [#15930]) ([sensor.worxlandroid docs]) (beta fix)
- remove-phantomjs-from-docker ([@vrih] - [#15936]) (beta fix)
- Remove remote.API from core.Config ([@awarecan] - [#15951]) ([http docs]) (breaking change) (beta fix)
- Allow picking intermediate Mozilla cert profile ([@balloob] - [#15957]) ([http docs]) (beta fix)
- Use JWT for access tokens ([@balloob] - [#15972]) ([auth docs]) ([http docs]) ([websocket_api docs]) (beta fix)
- Pin crypto ([@balloob] - [#15978]) (beta fix)
- Teak mqtt error message for 0.76 release ([@awarecan] - [#15983]) ([mqtt docs]) (beta fix)
- Fix 0.76 beta2 hassio token issue ([@awarecan] - [#15987]) ([hassio docs]) (beta fix)
- Fix mysensors connection task blocking setup ([@MartinHjelmare] - [#15938]) ([mysensors docs]) (beta fix)
- Fix Nest async from sync ([@balloob] - [#15997]) ([nest docs]) (beta fix)
## {% linkable_title All changes %}
- Add kodi unique id based on discovery ([@rytilahti] - [#15093]) ([media_player.kodi docs])
- Better handling of Yi camera being disconnected ([@bachya] - [#15754]) ([camera.yi docs])
- Decouple login flow view and data entry flow view ([@awarecan] - [#15715]) ([auth docs])
- Fixed NDMS for latest firmware ([@foxel] - [#15511]) ([device_tracker docs]) (breaking change)
- Add disallow_untyped_calls to mypy check. ([@andrey-git] - [#15661]) ([persistent_notification docs])
- Update pyozw to 0.4.9 ([@turbokongen] - [#15758]) ([zwave docs])
- Convert wind speed to km/h (fixes #15710) ([@fabaff] - [#15740]) ([weather.openweathermap docs]) (breaking change)
- Round precipitation forecast to 1 decimal place ([@priiduonu] - [#15759]) ([weather.openweathermap docs])
- Add a "Reviewed by Hound" badge ([@salbertson] - [#15767])
- Upgrade Mastodon.py to 1.3.1 ([@fabaff] - [#15766]) ([notify docs])
- This component API has been decomissioned on the 31st of May 2018 by Telstra ([@dgomes] - [#15757]) ([notify docs]) (breaking change)
- Fix docstrings ([@fabaff] - [#15770])
- Update pynetgear to 0.4.1 (bugfixes) ([@MatMaul] - [#15768]) ([device_tracker docs])
- Opensky altitude ([@ioangogo] - [#15273]) ([sensor.opensky docs])
- Expose internal states and fixed on/off state of Dyson Fans ([@soraxas] - [#15716]) ([fan.dyson docs])
- deCONZ - support for power plugs ([@Kane610] - [#15752]) ([deconz docs]) ([light.deconz docs]) ([switch.deconz docs]) (breaking change) (new-platform)
- Add support for STATES of vacuums ([@cnrd] - [#15573]) ([vacuum docs]) ([vacuum.xiaomi_miio docs])
- Add support for STATE_AUTO of generic_thermostat ([@niklaswa] - [#15678]) ([climate.generic_thermostat docs])
- Revert "Add support for STATE_AUTO of generic_thermostat (#15678)" ([@awarecan] - [#15783]) ([climate.generic_thermostat docs])
- RitAssist / FleetGO support ([@depl0y] - [#15780]) ([device_tracker docs]) (new-platform)
- Add support for OpenUV binary sensors and sensors ([@bachya] - [#15769]) ([openuv docs]) ([binary_sensor.openuv docs]) ([sensor.openuv docs]) (new-platform)
- Update pymediaroom to 0.6.4 ([@dgomes] - [#15786]) ([media_player.mediaroom docs])
- Add Enphase Envoy component ([@jesserizzo] - [#15081]) ([sensor.enphase_envoy docs]) (new-platform)
- Vacuum component: start_pause to individual start and pause commands. ([@cnrd] - [#15751]) ([vacuum docs])
- Make sure use_x_forward_for and trusted_proxies must config together ([@awarecan] - [#15804]) ([http docs]) (breaking change)
- Upgrade voluptuous-serialize to 2.0.0 ([@awarecan] - [#15763]) ([config docs])
- Upgrade pylint to 2.1.0 ([@scop] - [#15811]) ([binary_sensor.bayesian docs]) ([binary_sensor.threshold docs]) ([calendar.todoist docs]) ([light.group docs]) ([sensor.min_max docs]) ([sensor.statistics docs])
- Upgrade pytest to 3.7.1 and pytest-timeout to 1.3.1 ([@scop] - [#15809])
- Add support for 2 Tahoma IO awning covers ([@fucm] - [#15660]) ([tahoma docs]) ([cover.tahoma docs])
- Velbus auto-discovery ([@thomasdelaet] - [#13742]) ([velbus docs]) ([binary_sensor.velbus docs]) ([switch.velbus docs]) (breaking change)
- Upgrade youtube_dl to 2018.08.04 ([@fabaff] - [#15837]) ([media_extractor docs])
- Add media_player.dlna_dmr component ([@StevenLooman] - [#14749]) ([media_player.dlna_dmr docs]) (new-platform)
- Remove 'volume' from return dict ([@mattwing] - [#15842]) ([sensor.alpha_vantage docs])
- Upgrade shodan to 1.9.0 ([@fabaff] - [#15839]) ([sensor.shodan docs])
- Add max_gps_accuracy option to Google Maps ([@PrimusNZ] - [#15833]) ([device_tracker docs])
- Fix bt_home_hub_5 device tracker ([@ahobsonsayers] - [#15096]) ([device_tracker docs])
- Change to call_service async_stop non-blocking to allow service call finish ([@awarecan] - [#15803])
- Try to fix coveralls unstable result ([@awarecan] - [#15800])
- Add different pop 012501 ID ([@turbokongen] - [#15838]) ([zwave docs])
- Fix error when Series missing 'episodeFileCount' or 'episodeCount' ([@psike] - [#15824]) ([sensor.sonarr docs])
- Add facebox auth ([@robmarkcole] - [#15439]) ([image_processing.facebox docs]) (breaking change)
- Upgrade holidays to 0.9.6 ([@fabaff] - [#15831]) ([binary_sensor.workday docs])
- Upgrade pysnmp to 4.4.5 ([@fabaff] - [#15854]) ([device_tracker docs]) ([sensor.snmp docs]) ([switch.snmp docs])
- Fix HomeKit test ([@cdce8p] - [#15860])
- Do not make internet connection during tests ([@balloob] - [#15858])
- Upgrade pylint to 2.1.1 ([@scop] - [#15872])
- Upgrade asynctest to 0.12.2 ([@fabaff] - [#15869])
- Upgrade Sphinx to 1.7.6 ([@fabaff] - [#15868])
- Upgrade requests_mock to 1.5.2 ([@fabaff] - [#15867])
- Update based upon forum post ([@DubhAd] - [#15876]) ([device_tracker docs])
- Upgrade netdisco to 2.0.0 ([@fabaff] - [#15885])
- Follow changes to netdisco, separating DLNA into DLNA_DMS and DLNA_DMR ([@StevenLooman] - [#15877]) ([media_player.dlna_dmr docs])
- Upgrade pylast to 2.4.0 ([@fabaff] - [#15886]) ([sensor.lastfm docs])
- Add auth/authorize endpoint ([@balloob] - [#15887])
- Upgrade locationsharinglib to 2.0.11 ([@fabaff] - [#15902]) ([device_tracker docs])
- Refactor data entry flow ([@awarecan] - [#15883])
- Add HomematicIP Cloud smoke detector device ([@mxworm] - [#15621]) ([binary_sensor.homematicip_cloud docs])
- Fix for multiple camera switches naming of entity ([@rafale77] - [#14028]) ([switch.amcrest docs]) (breaking change)
- Add realtime true/false switch for Waze ([@mountainsandcode] - [#15228]) ([sensor.waze_travel_time docs])
- Add PJLink media player platform ([@benoitlouy] - [#15083]) ([media_player.pjlink docs]) (new-platform)
- Some typing related fixes ([@scop] - [#15899])
- Update August component to use py-august:0.6.0 ([@snjoetw] - [#15916]) ([august docs])
- Misc cleanups ([@scop] - [#15907]) ([device_tracker docs]) ([sensor.irish_rail_transport docs])
- Update radiotherm to 1.4.1 ([@craftyguy] - [#15910]) ([climate.radiotherm docs])
- Fix bug in translations upload script ([@armills] - [#15922])
- Add and restore context in recorder ([@balloob] - [#15859]) (new-feature)
- Add IndieAuth 4.2.2 redirect uri at client id ([@balloob] - [#15911]) ([auth docs])
- deCONZ - Add support for sirens ([@Kane610] - [#15896]) ([deconz docs]) ([switch.deconz docs])
- Add RMV public transport sensor ([@cgtobi] - [#15814]) ([sensor.rmvtransport docs]) (new-platform)
- :pencil2: Corrects typo in code comments ([@frenck] - [#15923]) ([binary_sensor.homematicip_cloud docs])
- Upgrade pymysensors to 0.17.0 ([@MartinHjelmare] - [#15942]) ([mysensors docs]) (beta fix)
- Deprecate remote.api ([@balloob] - [#15955]) (beta fix)
- Added error handling for sense API timeouts ([@kbickar] - [#15789]) ([sensor.sense docs]) (beta fix)
- Add context to login flow ([@awarecan] - [#15914]) ([auth docs]) (beta fix)
- MQTT embedded broker has to set its own password. ([@awarecan] - [#15929]) ([mqtt docs]) (breaking change) (beta fix)
- Fix issue when reading worxlandroid pin code ([@GotoCode] - [#15930]) ([sensor.worxlandroid docs]) (beta fix)
- remove-phantomjs-from-docker ([@vrih] - [#15936]) (beta fix)
- Remove remote.API from core.Config ([@awarecan] - [#15951]) ([http docs]) (breaking change) (beta fix)
- Allow picking intermediate Mozilla cert profile ([@balloob] - [#15957]) ([http docs]) (beta fix)
- Use JWT for access tokens ([@balloob] - [#15972]) ([auth docs]) ([http docs]) ([websocket_api docs]) (beta fix)
- Pin crypto ([@balloob] - [#15978]) (beta fix)
- Teak mqtt error message for 0.76 release ([@awarecan] - [#15983]) ([mqtt docs]) (beta fix)
- Fix 0.76 beta2 hassio token issue ([@awarecan] - [#15987]) ([hassio docs]) (beta fix)
- Fix mysensors connection task blocking setup ([@MartinHjelmare] - [#15938]) ([mysensors docs]) (beta fix)
- Fix Nest async from sync ([@balloob] - [#15997]) ([nest docs]) (beta fix)
[#13742]: https://github.com/home-assistant/home-assistant/pull/13742
[#14028]: https://github.com/home-assistant/home-assistant/pull/14028
[#14749]: https://github.com/home-assistant/home-assistant/pull/14749
[#15081]: https://github.com/home-assistant/home-assistant/pull/15081
[#15083]: https://github.com/home-assistant/home-assistant/pull/15083
[#15093]: https://github.com/home-assistant/home-assistant/pull/15093
[#15096]: https://github.com/home-assistant/home-assistant/pull/15096
[#15228]: https://github.com/home-assistant/home-assistant/pull/15228
[#15273]: https://github.com/home-assistant/home-assistant/pull/15273
[#15439]: https://github.com/home-assistant/home-assistant/pull/15439
[#15511]: https://github.com/home-assistant/home-assistant/pull/15511
[#15573]: https://github.com/home-assistant/home-assistant/pull/15573
[#15621]: https://github.com/home-assistant/home-assistant/pull/15621
[#15660]: https://github.com/home-assistant/home-assistant/pull/15660
[#15661]: https://github.com/home-assistant/home-assistant/pull/15661
[#15678]: https://github.com/home-assistant/home-assistant/pull/15678
[#15715]: https://github.com/home-assistant/home-assistant/pull/15715
[#15716]: https://github.com/home-assistant/home-assistant/pull/15716
[#15740]: https://github.com/home-assistant/home-assistant/pull/15740
[#15751]: https://github.com/home-assistant/home-assistant/pull/15751
[#15752]: https://github.com/home-assistant/home-assistant/pull/15752
[#15754]: https://github.com/home-assistant/home-assistant/pull/15754
[#15757]: https://github.com/home-assistant/home-assistant/pull/15757
[#15758]: https://github.com/home-assistant/home-assistant/pull/15758
[#15759]: https://github.com/home-assistant/home-assistant/pull/15759
[#15763]: https://github.com/home-assistant/home-assistant/pull/15763
[#15766]: https://github.com/home-assistant/home-assistant/pull/15766
[#15767]: https://github.com/home-assistant/home-assistant/pull/15767
[#15768]: https://github.com/home-assistant/home-assistant/pull/15768
[#15769]: https://github.com/home-assistant/home-assistant/pull/15769
[#15770]: https://github.com/home-assistant/home-assistant/pull/15770
[#15780]: https://github.com/home-assistant/home-assistant/pull/15780
[#15783]: https://github.com/home-assistant/home-assistant/pull/15783
[#15786]: https://github.com/home-assistant/home-assistant/pull/15786
[#15789]: https://github.com/home-assistant/home-assistant/pull/15789
[#15800]: https://github.com/home-assistant/home-assistant/pull/15800
[#15803]: https://github.com/home-assistant/home-assistant/pull/15803
[#15804]: https://github.com/home-assistant/home-assistant/pull/15804
[#15809]: https://github.com/home-assistant/home-assistant/pull/15809
[#15811]: https://github.com/home-assistant/home-assistant/pull/15811
[#15814]: https://github.com/home-assistant/home-assistant/pull/15814
[#15824]: https://github.com/home-assistant/home-assistant/pull/15824
[#15831]: https://github.com/home-assistant/home-assistant/pull/15831
[#15833]: https://github.com/home-assistant/home-assistant/pull/15833
[#15837]: https://github.com/home-assistant/home-assistant/pull/15837
[#15838]: https://github.com/home-assistant/home-assistant/pull/15838
[#15839]: https://github.com/home-assistant/home-assistant/pull/15839
[#15842]: https://github.com/home-assistant/home-assistant/pull/15842
[#15854]: https://github.com/home-assistant/home-assistant/pull/15854
[#15858]: https://github.com/home-assistant/home-assistant/pull/15858
[#15859]: https://github.com/home-assistant/home-assistant/pull/15859
[#15860]: https://github.com/home-assistant/home-assistant/pull/15860
[#15867]: https://github.com/home-assistant/home-assistant/pull/15867
[#15868]: https://github.com/home-assistant/home-assistant/pull/15868
[#15869]: https://github.com/home-assistant/home-assistant/pull/15869
[#15872]: https://github.com/home-assistant/home-assistant/pull/15872
[#15876]: https://github.com/home-assistant/home-assistant/pull/15876
[#15877]: https://github.com/home-assistant/home-assistant/pull/15877
[#15883]: https://github.com/home-assistant/home-assistant/pull/15883
[#15885]: https://github.com/home-assistant/home-assistant/pull/15885
[#15886]: https://github.com/home-assistant/home-assistant/pull/15886
[#15887]: https://github.com/home-assistant/home-assistant/pull/15887
[#15896]: https://github.com/home-assistant/home-assistant/pull/15896
[#15899]: https://github.com/home-assistant/home-assistant/pull/15899
[#15902]: https://github.com/home-assistant/home-assistant/pull/15902
[#15907]: https://github.com/home-assistant/home-assistant/pull/15907
[#15910]: https://github.com/home-assistant/home-assistant/pull/15910
[#15911]: https://github.com/home-assistant/home-assistant/pull/15911
[#15914]: https://github.com/home-assistant/home-assistant/pull/15914
[#15916]: https://github.com/home-assistant/home-assistant/pull/15916
[#15922]: https://github.com/home-assistant/home-assistant/pull/15922
[#15923]: https://github.com/home-assistant/home-assistant/pull/15923
[#15929]: https://github.com/home-assistant/home-assistant/pull/15929
[#15930]: https://github.com/home-assistant/home-assistant/pull/15930
[#15936]: https://github.com/home-assistant/home-assistant/pull/15936
[#15938]: https://github.com/home-assistant/home-assistant/pull/15938
[#15942]: https://github.com/home-assistant/home-assistant/pull/15942
[#15951]: https://github.com/home-assistant/home-assistant/pull/15951
[#15955]: https://github.com/home-assistant/home-assistant/pull/15955
[#15957]: https://github.com/home-assistant/home-assistant/pull/15957
[#15972]: https://github.com/home-assistant/home-assistant/pull/15972
[#15978]: https://github.com/home-assistant/home-assistant/pull/15978
[#15983]: https://github.com/home-assistant/home-assistant/pull/15983
[#15987]: https://github.com/home-assistant/home-assistant/pull/15987
[#15997]: https://github.com/home-assistant/home-assistant/pull/15997
[@DubhAd]: https://github.com/DubhAd
[@GotoCode]: https://github.com/GotoCode
[@Kane610]: https://github.com/Kane610
[@MartinHjelmare]: https://github.com/MartinHjelmare
[@MatMaul]: https://github.com/MatMaul
[@PrimusNZ]: https://github.com/PrimusNZ
[@StevenLooman]: https://github.com/StevenLooman
[@ahobsonsayers]: https://github.com/ahobsonsayers
[@andrey-git]: https://github.com/andrey-git
[@armills]: https://github.com/armills
[@awarecan]: https://github.com/awarecan
[@bachya]: https://github.com/bachya
[@balloob]: https://github.com/balloob
[@benoitlouy]: https://github.com/benoitlouy
[@cdce8p]: https://github.com/cdce8p
[@cgtobi]: https://github.com/cgtobi
[@cnrd]: https://github.com/cnrd
[@craftyguy]: https://github.com/craftyguy
[@depl0y]: https://github.com/depl0y
[@dgomes]: https://github.com/dgomes
[@fabaff]: https://github.com/fabaff
[@foxel]: https://github.com/foxel
[@frenck]: https://github.com/frenck
[@fucm]: https://github.com/fucm
[@ioangogo]: https://github.com/ioangogo
[@jesserizzo]: https://github.com/jesserizzo
[@kbickar]: https://github.com/kbickar
[@mattwing]: https://github.com/mattwing
[@mountainsandcode]: https://github.com/mountainsandcode
[@mxworm]: https://github.com/mxworm
[@niklaswa]: https://github.com/niklaswa
[@priiduonu]: https://github.com/priiduonu
[@psike]: https://github.com/psike
[@rafale77]: https://github.com/rafale77
[@robmarkcole]: https://github.com/robmarkcole
[@rytilahti]: https://github.com/rytilahti
[@salbertson]: https://github.com/salbertson
[@scop]: https://github.com/scop
[@snjoetw]: https://github.com/snjoetw
[@soraxas]: https://github.com/soraxas
[@thomasdelaet]: https://github.com/thomasdelaet
[@turbokongen]: https://github.com/turbokongen
[@vrih]: https://github.com/vrih
[august docs]: /components/august/
[auth docs]: /components/auth/
[binary_sensor.bayesian docs]: /components/binary_sensor.bayesian/
[binary_sensor.homematicip_cloud docs]: /components/binary_sensor.homematicip_cloud/
[binary_sensor.openuv docs]: /components/binary_sensor.openuv/
[binary_sensor.threshold docs]: /components/binary_sensor.threshold/
[binary_sensor.velbus docs]: /components/binary_sensor.velbus/
[binary_sensor.workday docs]: /components/binary_sensor.workday/
[calendar.todoist docs]: /components/calendar.todoist/
[camera.yi docs]: /components/camera.yi/
[climate.generic_thermostat docs]: /components/climate.generic_thermostat/
[climate.radiotherm docs]: /components/climate.radiotherm/
[config docs]: /components/config/
[cover.tahoma docs]: /components/cover.tahoma/
[deconz docs]: /components/deconz/
[device_tracker docs]: /components/device_tracker/
[fan.dyson docs]: /components/fan.dyson/
[fan.velbus docs]: /components/fan.velbus/
[hassio docs]: /components/hassio/
[http docs]: /components/http/
[image_processing.facebox docs]: /components/image_processing.facebox/
[light.deconz docs]: /components/light.deconz/
[light.group docs]: /components/light.group/
[light.velbus docs]: /components/light.velbus/
[media_extractor docs]: /components/media_extractor/
[media_player.dlna_dmr docs]: /components/media_player.dlna_dmr/
[media_player.kodi docs]: /components/media_player.kodi/
[media_player.mediaroom docs]: /components/media_player.mediaroom/
[media_player.pjlink docs]: /components/media_player.pjlink/
[mqtt docs]: /components/mqtt/
[mysensors docs]: /components/mysensors/
[nest docs]: /components/nest/
[notify docs]: /components/notify/
[onboarding docs]: /components/onboarding/
[openuv docs]: /components/openuv/
[persistent_notification docs]: /components/persistent_notification/
[sensor.alpha_vantage docs]: /components/sensor.alpha_vantage/
[sensor.enphase_envoy docs]: /components/sensor.enphase_envoy/
[sensor.irish_rail_transport docs]: /components/sensor.irish_rail_transport/
[sensor.lastfm docs]: /components/sensor.lastfm/
[sensor.min_max docs]: /components/sensor.min_max/
[sensor.opensky docs]: /components/sensor.opensky/
[sensor.openuv docs]: /components/sensor.openuv/
[sensor.rmvtransport docs]: /components/sensor.rmvtransport/
[sensor.sense docs]: /components/sensor.sense/
[sensor.shodan docs]: /components/sensor.shodan/
[sensor.snmp docs]: /components/sensor.snmp/
[sensor.sonarr docs]: /components/sensor.sonarr/
[sensor.statistics docs]: /components/sensor.statistics/
[sensor.waze_travel_time docs]: /components/sensor.waze_travel_time/
[sensor.worxlandroid docs]: /components/sensor.worxlandroid/
[switch.amcrest docs]: /components/switch.amcrest/
[switch.deconz docs]: /components/switch.deconz/
[switch.snmp docs]: /components/switch.snmp/
[switch.velbus docs]: /components/switch.velbus/
[tahoma docs]: /components/tahoma/
[vacuum docs]: /components/vacuum/
[vacuum.demo docs]: /components/vacuum.demo/
[vacuum.xiaomi_miio docs]: /components/vacuum.xiaomi_miio/
[velbus docs]: /components/velbus/
[weather.openweathermap docs]: /components/weather.openweathermap/
[websocket_api docs]: /components/websocket_api/
[zwave docs]: /components/zwave/

BIN
source/assets/get_lutron_cert.zip
View File

Binary file not shown.

BIN
source/images/blog/2018-08-0.76/components.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 40 KiB

17
source/lovelace/index.markdown
View File

@ -130,18 +130,23 @@ This is the very very early version aimed at gathering feedback. Discussion and
## {% linkable_title FAQ %}
### I am running Firefox but, custom cards like gauge-card look bad or don't load at all. How do I fix this?
### {% linkable_title I am running Firefox but, custom cards like gauge-card look bad or don't load at all. How do I fix this? %}
This is probably because your version of Firefox doesn't have custom components supported or enabled. Please set to `true` in your `about:config` the following settings: `dom.webcomponents.customelements.enabled` and `dom.webcomponents.shadowdom.enabled`
### Custom components don't load on my IOS device?
### {% linkable_title Custom cards don't load on my iOS device? %}
This is because for IOS devices by default javascript served is `es5`. You can allow custom components to load by forcing `javascript_version: latest` in your `configuration.yaml` under `frontend:`.
Home Assistant comes with two versions of the frontend. A compatability mode for older devices and a modern mode. The custom cards need to target one mode and usually choose the modern mode. Before Home Assistant 0.76, we had an issue in the automation and script editor that prevented modern iOS and Mac devices running Safari from using the modern mode.
> Note: Enabling `latest` on IOS could cause automation and script editor to crash.
If you can, resolve this issue by upgrading to Home Assistant 0.76 or later. If you are on an older version and don't mind that the automation and script editor don't work on iOS devices, you can force the new version via the configuration:
### I would like to add an image to my card, but I do not know where to put them.
```yaml
frontend:
javascript_version: latest
```
### {% linkable_title I would like to add an image to my card, but I do not know where to put them. %}
Given examples refer to `/local/example_image.jpg`. That means you should have `www` directory next to your HA `configuration.yaml`. An image kept in `HA_configuration_dir/www/example_image.jpg` will be shown after refreshing Lovelace page.
> Note: Remember to restart Home Assistant right after creating `www` directory. Otherwise, HA will not know that you created this directory.
Restart Home Assistant after creating the `www` directory. Otherwise, HA will not know that you created this directory.