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-15 05:16:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2022-03-15 16:30:03 +01:00
commit e310c352a1
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
75 changed files with 319 additions and 566 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.github/workflows/test.yml vendored
View File

@ -8,7 +8,7 @@ jobs:
runs-on: ubuntu-latest
steps:
- name: Check out files from GitHub
uses: actions/checkout@v2.4.0
uses: actions/checkout@v3.0.0
- name: Setting up Node.js
uses: actions/setup-node@v3.0.0
with:
@ -25,7 +25,7 @@ jobs:
runs-on: ubuntu-latest
steps:
- name: Check out files from GitHub
uses: actions/checkout@v2.4.0
uses: actions/checkout@v3.0.0
- name: Setting up Node.js
uses: actions/setup-node@v3.0.0
with:

4
_config.yml
View File

@ -107,8 +107,8 @@ social:
# Home Assistant release details
current_major_version: 2022
current_minor_version: 03
current_patch_version: 2
date_released: 2022-03-06
current_patch_version: 5
date_released: 2022-03-15
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

2
source/_docs/automation/yaml.markdown
View File

@ -160,6 +160,6 @@ If you want to migrate your manual automations to use the editor, you'll have to
When automations remain visible in the Home Assistant Dashboard, even after having deleted in the YAML file, you have to delete them in the UI.
To delete them completely, go to UI **{% my entities title="Configuration -> Entities" %}** and find the automation in the search field or by scrolling down.
To delete them completely, go to UI **{% my entities title="Configuration -> Devices & Services -> Entities" %}** and find the automation in the search field or by scrolling down.
Check the square box aside of the automation you wish to delete and from the top-right of your screen, select 'REMOVE SELECTED'.

2
source/_docs/configuration/customizing-devices.markdown
View File

@ -117,6 +117,8 @@ Home Assistant offers a service to reload the core configuration while Home Assi
To reload customizations, navigate to Configuration > Server Controls and then press the "Reload Location & Customizations" button. If you don't see this, enable Advanced Mode on your user profile page first.
You can also use the [Quick bar](/docs/tools/quick-bar/#command-palette), and choose "Reload Location & Customizations".
Alternatively, you can reload via service call. Navigate to Developer Tools > Services tab, select `homeassistant.reload_core_config` from the dropdown and press the "Call Service" button.
<div class='note warning'>

2
source/_docs/configuration/templating.markdown
View File

@ -701,7 +701,7 @@ Some examples:
### Regular expressions
- Test `string is match(find, ignorecase=False)` will match the find expression at the beginning of the string using regex.
- Test `string is search(find, ignorecase=True)` will match the find expression anywhere in the string using regex.
- Test `string is search(find, ignorecase=False)` will match the find expression anywhere in the string using regex.
- Filter `string|regex_replace(find='', replace='', ignorecase=False)` will replace the find expression with the replace string using regex.
- Filter `value | regex_findall(find='', ignorecase=False)` will find all regex matches of the find expression in `value` and return the array of matches.
- Filter `value | regex_findall_index(find='', index=0, ignorecase=False)` will do the same as `regex_findall` and return the match at index.

7
source/_includes/asides/about.html
View File

@ -8,6 +8,13 @@
<li><a href='https://demo.home-assistant.io'>Try the online demo</a></li>
<li><a class="twitter-follow-button" href="https://twitter.com/Home_Assistant">Follow Home Assistant on Twitter</a></li>
<li><div class="fb-like" data-href="https://www.facebook.com/homeassistantio/" data-layout="standard" data-action="like" data-size="small" data-show-faces="true" data-share="false"></div></li>
<li>
Subscribe to the Home Assistant Newsletter
<form action="https://services.home-assistant.io/newsletter/signup" method="post" target="_blank">
<input type="email" id="email" name="email" placeholder="Email address" required >
<input type="submit" value="Subscribe">
</form>
</li>
</ul>
</section>
<div id="fb-root"></div>

1
source/_integrations/arest.markdown
View File

@ -1,7 +1,6 @@
---
title: aREST
description: Instructions on how to integrate aREST within Home Assistant.
logo: arest.png
ha_category:
- DIY
- Binary Sensor

6
source/_integrations/august.markdown
View File

@ -54,6 +54,12 @@ There is currently support for the following device types within Home Assistant:
Most devices will need either August Connect Bridge or Doorbell to connect to Home Assistant.
</div>
## Known Issues with battery reporting
The August Wi-Fi Smart Lock (Gen 4) uses different battery technology (lithium-ion) than the other locks. The battery charge value reported by the lock detail API has frequently been reported as incorrect for these models.
Other August locks expect to be powered by AA alkaline (non-rechargeable) batteries. Rechargeable batteries in these locks will result in incorrect reporting of battery charge.
## Known Unsupported Devices
- The Yale Doorman L3

2
source/_integrations/cast.markdown
View File

@ -177,7 +177,7 @@ Mandatory:
Optional:
- `enqueue`: Enqueue only
- `playlist_id`: Play video with `media_id` from this playlist
- `playlist_id`: Play video with `media_id` from this playlist. Note that only providing `playlist_id` but no `media_id` does not work.
#### Example

1
source/_integrations/concord232.markdown
View File

@ -1,7 +1,6 @@
---
title: Concord232
description: Instructions on how to integrate Interlogix/GE Concord4 into Home Assistant.
logo: interlogix.png
ha_category:
- Alarm
- Binary Sensor

1
source/_integrations/denonavr.markdown
View File

@ -81,6 +81,7 @@ Known supported devices:
- Marantz NR1606
- Marantz NR1607
- Marantz NR1710
- Marantz NR1711
- Other Denon AVR receivers (untested)
- Marantz receivers (experimental)

2
source/_integrations/dlna_dms.markdown
View File

@ -31,7 +31,7 @@ The `<media_identifier>` can have one of three forms:
- `path/to/file` or `/path/to/file`: Slash-separated path through the Content Directory. This must refer to a unique media item.
- `:ObjectID`: Colon followed by a server-assigned ID for an object.
- `?query`: Question mark followed by a query string to search for, see [DLNA ContentDirectory SearchCriteria](http://www.upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf) for the syntax. The first result found will be used.
- `?query`: Question mark followed by a query string to search for, see [DLNA ContentDirectory SearchCriteria](https://openconnectivity.org/wp-content/uploads/2015/11/UPnP-av-ContentDirectory-v4-Service.pdf) (part 5.3.16 "A_ARG_TYPE_SearchCriteria" on page 65 and part D.5 "Searching" on page 269) for the syntax. The first result found will be used.
URIs generated while browsing will look like the Object ID form above. However, all three forms will work with the [media_player.play_media](/integrations/media_player/#service-media_playerplay_media) service.

9
source/_integrations/dte_energy_bridge.markdown
View File

@ -15,6 +15,15 @@ A sensor platform for the [DTE](https://www.newlook.dteenergy.com/) Energy Bridg
- If the status LED is on the top, you have a v1.
- If the status LED is on the front, you have a v2.
<div class='note'>
The firmware of the DTE v2 bridges that started shipping circa mid-2020 will not work with this integration.
You can check if your firmware is still supported by trying accessing `http://{ip_address}:8888/zigbee/se/instantaneousdemand`, and see if
you get a response.
</div>
To enable this sensor, add the following lines to your `configuration.yaml` file:
```yaml

1
source/_integrations/enigma2.markdown
View File

@ -1,7 +1,6 @@
---
title: Enigma2 (OpenWebif)
description: Instructions on how to integrate an Enigma2 based box running OpenWebif into Home Assistant.
logo: openwebif.png
ha_category:
- Media Player
ha_release: '0.90'

1
source/_integrations/eq3btsmart.markdown
View File

@ -1,7 +1,6 @@
---
title: EQ3 Bluetooth Smart Thermostats
description: Instructions on how to integrate EQ3 Bluetooth Smart Thermostats into Home Assistant.
logo: eq3.gif
ha_category:
- Climate
ha_iot_class: Local Polling

8
source/_integrations/flux_led.markdown
View File

@ -171,10 +171,10 @@ The following models have been tested.
| 0x97 | Socket | no | |
| 0xA1 | Addressable v1 | no | Supports UCS1903, SM16703, WS2811, WS2812B, SK6812, INK1003, WS2801, LB1914 |
| 0xA2 | Addressable v2 | yes | Supports UCS1903, SM16703, WS2811, WS2811B, SK6812, INK1003, WS2801, WS2815, APA102, TM1914, UCS2904B |
| 0xA3 | Addressable v3 | yes | Supports WS2812B, SM16703, SM16704, WS2811, UCS1903, SK6812, SK6812RGBW, INK1003, UCS2904B |
| 0xA4 | Addressable v4 | no | Supports WS2812B, SM16703, SM16704, WS2811, UCS1903, SK6812, SK6812RGBW, INK1003, UCS2904B |
| 0xA6 | Addressable v6 | yes | Supports WS2812B, SM16703, SM16704, WS2811, UCS1903, SK6812, SK6812RGBW, INK1003, UCS2904B |
| 0xA7 | Addressable v7 | yes | Supports WS2812B, SM16703, SM16704, WS2811, UCS1903, SK6812, SK6812RGBW, INK1003, UCS2904B |
| 0xA3 | Addressable v3 | yes | Supports WS2812B, SM16703, SM16704, WS2811, UCS1903, SK6812, SK6812RGBW (WS2814), INK1003, UCS2904B |
| 0xA4 | Addressable v4 | no | Supports WS2812B, SM16703, SM16704, WS2811, UCS1903, SK6812, SK6812RGBW (WS2814), INK1003, UCS2904B |
| 0xA6 | Addressable v6 | yes | Supports WS2812B, SM16703, SM16704, WS2811, UCS1903, SK6812, SK6812RGBW (WS2814), INK1003, UCS2904B |
| 0xA7 | Addressable v7 | yes | Supports WS2812B, SM16703, SM16704, WS2811, UCS1903, SK6812, SK6812RGBW (WS2814), INK1003, UCS2904B |
| 0xE1 | Ceiling Light CCT | no | |
| 0xE2 | Ceiling Light Assist | no | Auxiliary Switch not supported |

1
source/_integrations/fronius.markdown
View File

@ -22,6 +22,7 @@ The `fronius` integration polls a [Fronius](https://www.fronius.com/) solar inve
## Prerequisites
You will need to either set a static IP on the Fronius device or assign a static DHCP lease for it, or alternatively access it through the local DNS name if your network is properly configured for this.
For Gen24 devices (delivered with Firmware >= 1.14.1) make sure to activate the "Solar API" in the inverters web interface.
{% include integrations/config_flow.md %}

1
source/_integrations/futurenow.markdown
View File

@ -1,7 +1,6 @@
---
title: P5 FutureNow
description: Instructions on how to set up P5 FutureNow relay/dimmer units as lights within Home Assistant.
logo: p5.png
ha_category:
- Light
ha_iot_class: Local Polling

36
source/_integrations/google.markdown
View File

@ -10,17 +10,15 @@ ha_platforms:
- calendar
---
The `google` calendar platform allows you to connect to your
[Google Calendars](https://calendar.google.com) and generate binary sensors.
The sensors created can trigger based on any event on the calendar or only for
matching events. When you first setup this integration it will generate a new
configuration file `google_calendars.yaml` in your configuration directory that will contain information about
all of the calendars you can see.
It also exposes a service to add an event to one of your Google Calendars.
The Google integration allows you to connect to your [Google Calendars](https://calendar.google.com) to Home Assistant. The integration adds calendar entities that are shown on the *Calendar* dashboard, and can be used for automations based on any event, or limited to specific matching criteria.
## Prerequisites
Generate a Client ID and Client Secret on
You need to configure developer credentials to allow Home Assistant to access your Google Account.
{% details "Generate Client ID and Client Secret" %}
This section explains how to generate a Client ID and Client Secret on
[Google Developers Console](https://console.developers.google.com/start/api?id=calendar).
1. First go to the [Google Developers Console](https://console.developers.google.com/start/api?id=calendar)
@ -40,15 +38,8 @@ Generate a Client ID and Client Secret on
1. We need to double check that the "Google Calendar API" has been automatically enabled. To do this, select `Library` from the menu, then search for "Google Calendar API". If it is enabled you will see `API Enabled` with a green tick next to it. If it is not enabled, then enable it.
If you will later be adding more scopes than just the "Google Calendar API" to the OAuth for this application, you will need to delete your token file under your Home Assistant Profile. You will lose your refresh token due to the re-authenticating to add more API access. It's recommended to use different authorizations for different pieces of Google.
{% enddetails %}
## Troubleshooting
If you are trying to switch to a new Google account then you would run into the following error message. Make sure to delete the existing **.google.token** file from your `config` folder and restart Home Assistant to try again.
'oauth2client.client.HttpAccessTokenRefreshError: deleted_client: The OAuth client was deleted'
In case you get an `Authentication code expired, please restart Home-Assistant and try again` error message, switch your timezone to `Etc/GMT` and restart Home Assistant. This should fix the issue and the `google_calendars.yaml` configuration file will be created.
You can then switch back the timezone to your original one and restart Home Assistant again.
## Configuration
@ -89,9 +80,18 @@ calendar_access:
The next time you run or restart Home Assistant, you should find a new notification (the little bell icon in the lower-left corner). Click on that notification it will give you a link and an authentication code. Click on that link to open a Google website where you should enter the code found in the notification (**NOTE**: You may get a message telling you that the API has not been verified and you will need to acknowledge that in order to proceed). This will grant your Home Assistant service `read-only` or `read-write` access (based on configuration) to all the Google Calendars that the account you authenticate with can read.
## Troubleshooting
If you are trying to switch to a new Google account then you would run into the following error message. Make sure to delete the existing **.google.token** file from your `config` folder and restart Home Assistant to try again.
'oauth2client.client.HttpAccessTokenRefreshError: deleted_client: The OAuth client was deleted'
In case you get an `Authentication code expired, please restart Home-Assistant and try again` error message, switch your timezone to `Etc/GMT` and restart Home Assistant. This should fix the issue and the `google_calendars.yaml` configuration file will be created.
You can then switch back the timezone to your original one and restart Home Assistant again.
## Calendar Configuration
With every restart all calendars of the configured Google account will get pulled and added to the `google_calendars.yaml` and preconfigured as a single entity. By setting the 'track' variable to `true` the calendar will get monitored for new events which can be used for automations and its content is shown on the 'Calendar' dashboard.
The integration will discover new calendars and write them into a configuration file `google_calendars.yaml` in your configuration directory. The configuration file can let you control which calendars appear, or set up more elaborate event matching criteria.
A basic entry for a single calendar looks like:
@ -177,7 +177,7 @@ entities:
default: true
{% endconfiguration %}
### Sensor attributes
### Calendar attributes
- **offset_reached**: If set in the event title and parsed out will be `on`/`off` once the offset in the title in minutes is reached. So the title `Very important meeting #Important !!-10` would trigger this attribute to be `on` 10 minutes before the event starts.
- **all_day**: `true`/`false` if this is an all day event. Will be `false` if there is no event found.

1
source/_integrations/gree.markdown
View File

@ -35,6 +35,7 @@ Any Gree Smart device working with the Gree+ app should be supported, including
- Innova
- Cooper & Hunter
- Proklima
- Tadiran
## Climate

1
source/_integrations/greeneye_monitor.markdown
View File

@ -1,7 +1,6 @@
---
title: GreenEye Monitor (GEM)
description: Instructions on how to integrate your GreenEye Monitor within Home Assistant.
logo: brultech.png
ha_category:
- Hub
- Sensor

1
source/_integrations/greenwave.markdown
View File

@ -1,7 +1,6 @@
---
title: Greenwave Reality
description: Instructions on how to set up Greenwave Reality lights within Home Assistant.
logo: greenwavereality.png
ha_category:
- Light
ha_release: 0.61

1
source/_integrations/horizon.markdown
View File

@ -1,7 +1,6 @@
---
title: Unitymedia Horizon HD Recorder
description: Instructions how to integrate the Unitymedia Horizon HD Recorder into Home Assistant.
logo: unitymedia.png
ha_category:
- Media Player
ha_iot_class: Local Polling

1
source/_integrations/iglo.markdown
View File

@ -1,7 +1,6 @@
---
title: iGlo
description: Instructions on how to integrate iGlo lights into Home Assistant.
logo: iglo.png
ha_category:
- Light
ha_iot_class: Local Polling

1
source/_integrations/lirc.markdown
View File

@ -1,7 +1,6 @@
---
title: LIRC
description: Instructions on how to integrate IR remotes with LIRC into Home Assistant.
logo: lirc.gif
ha_category:
- Automation
ha_release: 0.21

1
source/_integrations/lw12wifi.markdown
View File

@ -4,7 +4,6 @@ description: Instructions on how to setup Lagute LW-12 Wifi LED controller withi
ha_category:
- Light
ha_iot_class: Local Polling
logo: lagute.png
ha_release: 0.71
ha_domain: lw12wifi
ha_platforms:

1
source/_integrations/mqtt_room.markdown
View File

@ -21,6 +21,7 @@ To use this device tracker in your installation, add the following to your `conf
sensor:
- platform: mqtt_room
device_id: 123testid
state_topic: "espresense/rooms"
```
{% configuration %}

1
source/_integrations/mythicbeastsdns.markdown
View File

@ -5,7 +5,6 @@ ha_category:
- Network
ha_release: 0.85
ha_iot_class: Cloud Push
logo: mythic_beasts.png
ha_domain: mythicbeastsdns
---

1
source/_integrations/neurio_energy.markdown
View File

@ -1,7 +1,6 @@
---
title: Neurio energy
description: Instructions on how to integrate Neurio within Home Assistant.
logo: neurio.png
ha_category:
- Energy
ha_iot_class: Cloud Polling

1
source/_integrations/nx584.markdown
View File

@ -1,7 +1,6 @@
---
title: NX584
description: Instructions on how to integrate NX584 into Home Assistant.
logo: networx.png
ha_category:
- Alarm
- Binary Sensor

1
source/_integrations/obihai.markdown
View File

@ -1,7 +1,6 @@
---
title: Obihai
description: Instructions on how to integrate your Obihai device into Home Assistant.
logo: obitalk.png
ha_iot_class: Local Polling
ha_category:
- Sensor

1
source/_integrations/qld_bushfire.markdown
View File

@ -1,7 +1,6 @@
---
title: Queensland Bushfire Alert
description: Instructions on how to integrate the Queensland Bushfire Alert feed into Home Assistant.
logo: geo_location.png
ha_category: Geolocation
ha_iot_class: Cloud Polling
ha_release: 0.95

11
source/_integrations/samsungtv.markdown
View File

@ -90,12 +90,9 @@ media_content_type: channel
It's possible to switch between the 2 sources `TV` and `HDMI`.
### Home Assistant Core additional requirements
### Known issues and restrictions
You will need to install the `websocket-client` Python package in your Home Assistant install. This will probably be done with:
#### Subnet/VLAN
```bash
pip3 install websocket-client
```
Remembering to activate your venv if you're using a venv install.
Samsung SmartTV does not allow WebSocket connections across different subnets or VLANs. If your TV is not on the same subnet as Home Assistant this will fail.
It may be possible to bypass this issue by using IP masquerading or a proxy.

18
source/_integrations/tod.markdown
View File

@ -42,19 +42,19 @@ name:
required: true
type: string
before:
description: The absolute local time value or sun event for beginning of the time range.
required: true
type: [string, time]
before_offset:
description: The time offset of the beginning time range.
required: false
type: time
after:
description: The absolute local time value or sun event for ending of the time range.
required: true
type: [string, time]
after_offset:
before_offset:
description: The time offset of the ending time range.
required: false
type: time
after:
description: The absolute local time value or sun event for beginning of the time range.
required: true
type: [string, time]
after_offset:
description: The time offset of the beginning time range.
type: time
required: false
{% endconfiguration %}

41
source/_integrations/waze_travel_time.markdown
View File

@ -20,7 +20,7 @@ The `waze_travel_time` sensor provides travel time from the [Waze](https://www.w
Notes:
- If a unit system is not specified, the integration will use the unit system configured on your Home Assistant instance.
- Origin and Destination can be the address or the GPS coordinates of the location (GPS coordinates has to be separated by a comma). You can also enter an entity id which provides this information in its state, an entity id with latitude and longitude attributes, or zone friendly name (case sensitive).
- Origin and Destination can be the address or the GPS coordinates of the location (GPS coordinates have to be separated by a comma). You can also enter an entity id which provides this information in its state, an entity id with latitude and longitude attributes, or zone friendly name (case sensitive).
- The string inputs for `Substring *` allow you to force the integration to use a particular route or avoid a particular route in its time travel calculation. These inputs are case insensitive matched against the description of the route.
- When using the `Avoid Toll Roads?`, `Avoid Subscription Roads?` and `Avoid Ferries?` options be aware that Waze will sometimes still route you over toll roads or ferries if a valid vignette/subscription is assumed. Default behavior is that Waze will route you over roads having subscription options, so best is to set both `Avoid Toll Roads?` and `Avoid Subscription Roads?` or `Avoid Ferries?` if needed and experiment to ensure the desired outcome.
@ -69,36 +69,37 @@ template:
In this example we use a device_tracker entity ID as the origin and the sensor created above as the destination.
Name: "Me to destination"
Origin: device_tracker.myphone
Destination: sensor.dest_address
Region: "US"
- Name: "Me to some destination"
- Origin: `device_tracker.myphone`
- Destination: `sensor.dest_address`
- Region: "US"
#### Tracking entity to zone friendly name
In this example we are using the entity ID of a zone as the origin and the friendly name of a zone as the destination.
Name: "Home To Eddie's House"
Origin: zone.home
Destination: "Eddies House"
Region: "US"
- Name: "Home to Eddie's house"
- Origin: `zone.home`
- Destination: "Eddies House"
- Region: "US"
#### Tracking entity in Imperial Units
Origin: person.paulus
Destination: "725 5th Ave, New York, NY 10022, USA"
Region: "US"
Units: imperial
Vehicle Type: motorcycle
- Name: "Somewhere in New York"
- Origin: `person.paulus`
- Destination: "725 5th Ave, New York, NY 10022, USA"
- Region: "US"
- Units: "imperial"
- Vehicle Type: "motorcycle"
#### Avoiding toll, subscription
Name: "Westerscheldetunnel"
Origin: 51.330436, 3.802043
Destination: 51.445677, 3.749929
Region: "EU"
Avoid Toll Roads?: True
Avoid Subscription Roads?: True
- Name: "Westerscheldetunnel"
- Origin: "51.330436, 3.802043"
- Destination: "51.445677, 3.749929"
- Region: "EU"
- Avoid Toll Roads: `True`
- Avoid Subscription Roads: `True`
## Using the live map in an iFrame

2
source/_lovelace/alarm-panel.markdown
View File

@ -12,7 +12,7 @@ The Alarm Panel card allows you to arm and disarm your [alarm control panel](/in
Screenshot of the Alarm Panel card.
</p>
To add the Alarm Panel card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Alarm Panel** from the card picker. All options for this card can be configured via the user interface.
To add the Alarm Panel card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Alarm Panel** from the card picker. All options for this card can be configured via the user interface.
Alternatively, the card can be configured using YAML:

4
source/_lovelace/area.markdown
View File

@ -13,7 +13,7 @@ The Area card lets you control and monitor an individual area.
</p>
To add the Area card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Area** from the card picker. All options for this card can be configured via the user interface.
To add the Area card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Area** from the card picker. All options for this card can be configured via the user interface.
Buttons will appear on the card for the entities in the area including fan, light and switch. A motion sensor icon will appear in the top left if a motion sensor is in the area and motion is detected by the motion sensor.
@ -35,7 +35,7 @@ show_camera:
default: false
navigation_path:
required: false
description: link to Lovelace view. For more information about views, see the [view documentation](/lovelace/views/)
description: link to view. For more information about views, see the [view documentation](/lovelace/views/)
type: string
theme:
required: false

2
source/_lovelace/button.markdown
View File

@ -12,7 +12,7 @@ The Button card allows you to add buttons to perform tasks.
Screenshot of three Button Cards.
</p>
To add the Button card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Button** from the card picker. All options for this card can be configured via the user interface.
To add the Button card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Button** from the card picker. All options for this card can be configured via the user interface.
## Card Settings

2
source/_lovelace/calendar.markdown
View File

@ -12,7 +12,7 @@ The Calendar card displays your [calendar](/integrations/#calendar) entities in
Screenshot of the Calendar card.
</p>
To add the Calendar card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Calendar** from the card picker. All options for this card can be configured via the user interface.
To add the Calendar card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Calendar** from the card picker. All options for this card can be configured via the user interface.
## Card Settings

2
source/_lovelace/conditional.markdown
View File

@ -7,7 +7,7 @@ description: The Conditional card displays another card based on entity states.
The Conditional card displays another card based on entity states.
To add the Conditional card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Conditional** from the card picker. All options for this card can be configured via the user interface.
To add the Conditional card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Conditional** from the card picker. All options for this card can be configured via the user interface.
{% configuration %}
type:

2
source/_lovelace/energy.markdown
View File

@ -5,7 +5,7 @@ sidebar_label: Energy Cards
description: "An overview of the energy cards that are available."
---
This is a list of all the cards used in the energy dashboard, you can also place them anywhere you want in your Lovelace dashboard.
This is a list of all the cards used in the energy dashboard, you can also place them anywhere you want in your dashboard.
At the moment there are no configuration options available for these cards, you can configure them on the {% my config_energy title="energy configuration page" %}.

2
source/_lovelace/entities.markdown
View File

@ -7,7 +7,7 @@ description: "The Entities card is the most common type of card. It groups items
The Entities card is the most common type of card. It groups items together into lists. It can be used to display an entity's state or attribute, but also contain buttons, web links, etc.
To add the Entities card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Entities** from the card picker.
To add the Entities card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Entities** from the card picker.
{% configuration %}
type:

2
source/_lovelace/entity.markdown
View File

@ -12,7 +12,7 @@ The Entity card gives you a quick overview of your entity's state.
Screenshot of the Entity card.
</p>
To add the Entity card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Entity** from the card picker.
To add the Entity card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Entity** from the card picker.
{% configuration %}
type:

2
source/_lovelace/gauge.markdown
View File

@ -17,7 +17,7 @@ Screenshot of the Gauge card.
Screenshot of the Gauge card in needle mode.
</p>
To add the Gauge card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Gauge** from the card picker. All options for this card can be configured via the user interface.
To add the Gauge card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Gauge** from the card picker. All options for this card can be configured via the user interface.
Alternatively, the card can be configured using YAML:

2
source/_lovelace/glance.markdown
View File

@ -12,7 +12,7 @@ The Glance card is useful to group multiple sensors in a compact overview. Keep
Screenshot of the Glance card.
</p>
To add the Glance card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Glance** from the card picker.
To add the Glance card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Glance** from the card picker.
{% configuration %}
type:

2
source/_lovelace/grid.markdown
View File

@ -12,7 +12,7 @@ The Grid card allows you to show multiple cards in a grid. It will first fill th
Screenshot of the Grid card.
</p>
To add the Grid card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Grid Card** from the card picker.
To add the Grid card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Grid Card** from the card picker.
{% configuration %}
type:

2
source/_lovelace/history-graph.markdown
View File

@ -17,7 +17,7 @@ Screenshot of the History Graph card, when the sensor has no `unit_of_measuremen
Screenshot of the History Graph card, when the sensor has a `unit_of_measurement` defined.
</p>
To add the History Graph card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **History Graph** from the card picker. All options for this card can be configured via the user interface.
To add the History Graph card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **History Graph** from the card picker. All options for this card can be configured via the user interface.
{% configuration %}
type:

2
source/_lovelace/horizontal-stack.markdown
View File

@ -7,7 +7,7 @@ description: "The Horizontal Stack card allows you to stack together multiple ca
The Horizontal Stack card allows you to stack together multiple cards, so they always sit next to each other in the space of one column.
To add the Horizontal Stack card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Horizontal Stack** from the card picker. All options for this card can be configured via the user interface.
To add the Horizontal Stack card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Horizontal Stack** from the card picker. All options for this card can be configured via the user interface.
{% configuration %}
type:

2
source/_lovelace/humidifier.markdown
View File

@ -12,7 +12,7 @@ The Humidifier card lets you control and monitor humidifiers, dehumidifiers, and
Screenshot of the humidifier card.
</p>
To add the Humidifier card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Humidifier** from the card picker. All options for this card can be configured via the user interface.
To add the Humidifier card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Humidifier** from the card picker. All options for this card can be configured via the user interface.
{% configuration %}
type:

2
source/_lovelace/iframe.markdown
View File

@ -16,7 +16,7 @@ You can't embed sites using HTTP if you are using HTTPS for your Home Assistant.
Windy weather radar as Webpage.
</p>
To add the Webpage card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Webpage** from the card picker. All options for this card can be configured via the user interface.
To add the Webpage card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Webpage** from the card picker. All options for this card can be configured via the user interface.
{% configuration %}
type:

2
source/_lovelace/light.markdown
View File

@ -12,7 +12,7 @@ The Light card allows you to change the brightness of the light.
Screenshot of the Light card.
</p>
To add the Light card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Light** from the card picker. All options for this card can be configured via the user interface.
To add the Light card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Light** from the card picker. All options for this card can be configured via the user interface.
Alternatively, the card can be configured using YAML:

2
source/_lovelace/logbook.markdown
View File

@ -12,7 +12,7 @@ The Logbook card displays entries from the logbook for specific entities.
Screenshot of the Logbook card.
</p>
To add the Logbook card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Logbook** from the card picker.
To add the Logbook card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Logbook** from the card picker.
## Card Settings

2
source/_lovelace/map.markdown
View File

@ -12,7 +12,7 @@ The Map card that allows you to display entities on a map
Screenshot of the map card.
</p>
To add the Map card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Map** from the card picker. All options for this card can be configured via the user interface.
To add the Map card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Map** from the card picker. All options for this card can be configured via the user interface.
{% configuration %}
type:

6
source/_lovelace/markdown.markdown
View File

@ -14,7 +14,7 @@ The renderer uses [Marked.js](https://marked.js.org), which supports [several sp
Screenshot of the Markdown card.
</p>
To add the Markdown card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Markdown** from the card picker.
To add the Markdown card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Markdown** from the card picker.
{% configuration %}
type:
@ -34,7 +34,7 @@ card_size:
required: false
type: integer
default: none
description: The algorithm for placing cards aesthetically in Lovelace may have problems with the Markdown card if it contains templates. You can use this value to help it estimate the height of the card in units of 50 pixels (approximately 3 lines of text in default size). (e.g., `4`)
description: The algorithm for placing cards aesthetically may have problems with the Markdown card if it contains templates. You can use this value to help it estimate the height of the card in units of 50 pixels (approximately 3 lines of text in default size). (e.g., `4`)
entity_id:
required: false
type: [string, list]
@ -55,7 +55,7 @@ type: markdown
content: >
## Lovelace
Starting with Home Assistant 0.72, we're experimenting with a new way of defining your interface. We're calling it the **Lovelace UI**.
Starting with Home Assistant 0.72, we're experimenting with a new way of defining your interface.
```
## Template variables

2
source/_lovelace/media-control.markdown
View File

@ -12,7 +12,7 @@ The Media Control card is used to display [Media Player](/integrations/#media-pl
Screenshot of the Media Control card.
</p>
To add the Media Control card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Media Control** from the card picker.
To add the Media Control card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Media Control** from the card picker.
{% configuration %}
type:

2
source/_lovelace/plant-status.markdown
View File

@ -12,7 +12,7 @@ The Plant Status card is for all the lovely botanists out there.
Screenshot of the plant status card.
</p>
To add the Plant Status card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Plant Status** from the card picker. All options for this card can be configured via the user interface.
To add the Plant Status card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Plant Status** from the card picker. All options for this card can be configured via the user interface.
{% configuration %}
type:

2
source/_lovelace/sensor.markdown
View File

@ -12,7 +12,7 @@ The Sensor card gives you a quick overview of your sensors state with an optiona
Screenshot of the sensor card.
</p>
To add the Sensor card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Sensor** from the card picker. All options for this card can be configured via the user interface.
To add the Sensor card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Sensor** from the card picker. All options for this card can be configured via the user interface.
{% configuration %}
type:

2
source/_lovelace/shopping-list.markdown
View File

@ -14,7 +14,7 @@ Setup of the [Shopping List integration](/integrations/shopping_list/) is requir
Screenshot of the Shopping List card.
</p>
To add the Shopping List card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Shopping List** from the card picker. All options for this card can be configured via the user interface.
To add the Shopping List card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Shopping List** from the card picker. All options for this card can be configured via the user interface.
Alternatively, the card can be configured using YAML:

2
source/_lovelace/sidebar.markdown
View File

@ -10,7 +10,7 @@ The sidebar view has 2 columns, a wide one and a smaller one on the right.
This view doesn't have support for badges.
To change a view to edit mode, or to change the location of a card, enable edit mode:
Click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**.
Click the menu (three dots at the top right of the screen) and then **Edit Dashboard**.
You can set if a card should be placed in the main (left) column of the sidebar column (right), by pressing the arrow right or left arrow in the bar underneath the card.

2
source/_lovelace/statistics-graph.markdown
View File

@ -21,7 +21,7 @@ Screenshot of the Statistics Graph card with none metered entities and `chart_ty
Screenshot of the Statistics Graph card with a metered entity and `chart_type` `bar`.
</p>
To add the Statistics Graph card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Statistics Graph** from the card picker. All options for this card can be configured via the user interface.
To add the Statistics Graph card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Statistics Graph** from the card picker. All options for this card can be configured via the user interface.
{% configuration %}
type:

2
source/_lovelace/thermostat.markdown
View File

@ -12,7 +12,7 @@ The Thermostat card gives control of your [climate](/integrations/#climate) enti
Screenshot of the Thermostat card.
</p>
To add the Thermostat card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Thermostat** from the card picker. All options for this card can be configured via the user interface.
To add the Thermostat card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Thermostat** from the card picker. All options for this card can be configured via the user interface.
{% configuration %}
type:

2
source/_lovelace/vertical-stack.markdown
View File

@ -7,7 +7,7 @@ description: "The Vertical Stack card allows you to group multiple cards so they
The Vertical Stack card allows you to group multiple cards so they always sit in the same column.
To add the Vertical Stack card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Vertical Stack** from the card picker. All options for this card can be configured via the user interface.
To add the Vertical Stack card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Vertical Stack** from the card picker. All options for this card can be configured via the user interface.
{% configuration %}
type:

2
source/_lovelace/weather-forecast.markdown
View File

@ -12,7 +12,7 @@ The Weather Forecast card displays the weather. Very useful to include on interf
Screenshot of the Weather card.
</p>
To add the Weather card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Weather** from the card picker.
To add the Weather card to your user interface, click the menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the "Add Card" button in the bottom right corner and select **Weather** from the card picker.
## Card Settings

136
source/_posts/2022-03-02-release-20223.markdown
View File

@ -50,6 +50,9 @@ Enjoy the release!
- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
- [Release 2022.3.1 - March 3](#release-202231---march-3)
- [Release 2022.3.2 - March 6](#release-202232---march-6)
- [Release 2022.3.3 - March 7](#release-202233---march-7)
- [Release 2022.3.4 - March 11](#release-202234---march-11)
- [Release 2022.3.5 - March 15](#release-202235---march-15)
- [Need help? Join the community!](#need-help-join-the-community)
- [Breaking Changes](#breaking-changes)
- [Updates for custom integration developers](#updates-for-custom-integration-developers)
@ -416,6 +419,139 @@ The following integrations are now available via the Home Assistant UI:
[template docs]: /integrations/template/
[xiaomi_miio docs]: /integrations/xiaomi_miio/
## Release 2022.3.3 - March 7
- Fix false positive MQTT climate deprecation warnings for defaults ([@jbouwh] - [#67661]) ([mqtt docs])
- Fix timezone for growatt lastdataupdate ([@muppet3000] - [#67684]) ([growatt_server docs])
- Fix temperature stepping in Sensibo ([@gjohansson-ST] - [#67737]) ([sensibo docs])
- Prevent polling from recreating an entity after removal ([@bdraco] - [#67750])
- Fix internet access switch for old discovery ([@chemelli74] - [#67777]) ([fritz docs])
- Fix profile name update for Shelly Valve ([@chemelli74] - [#67778]) ([shelly docs])
- Handle fan_modes being set to None in homekit ([@bdraco] - [#67790]) ([homekit docs])
- Catch Elgato connection errors ([@frenck] - [#67799]) ([elgato docs])
- Update frontend to 20220301.1 ([@bramkragten] - [#67812]) ([frontend docs])
- Bump python-miio version to 0.5.11 ([@rytilahti] - [#67824]) ([xiaomi_miio docs])
- Prevent scene from restoring unavailable states ([@bdraco] - [#67836]) ([scene docs])
[#67661]: https://github.com/home-assistant/core/pull/67661
[#67684]: https://github.com/home-assistant/core/pull/67684
[#67737]: https://github.com/home-assistant/core/pull/67737
[#67750]: https://github.com/home-assistant/core/pull/67750
[#67777]: https://github.com/home-assistant/core/pull/67777
[#67778]: https://github.com/home-assistant/core/pull/67778
[#67790]: https://github.com/home-assistant/core/pull/67790
[#67799]: https://github.com/home-assistant/core/pull/67799
[#67812]: https://github.com/home-assistant/core/pull/67812
[#67824]: https://github.com/home-assistant/core/pull/67824
[#67836]: https://github.com/home-assistant/core/pull/67836
[@bdraco]: https://github.com/bdraco
[@bramkragten]: https://github.com/bramkragten
[@chemelli74]: https://github.com/chemelli74
[@frenck]: https://github.com/frenck
[@gjohansson-ST]: https://github.com/gjohansson-ST
[@jbouwh]: https://github.com/jbouwh
[@muppet3000]: https://github.com/muppet3000
[@rytilahti]: https://github.com/rytilahti
[elgato docs]: /integrations/elgato/
[fritz docs]: /integrations/fritz/
[frontend docs]: /integrations/frontend/
[growatt_server docs]: /integrations/growatt_server/
[homekit docs]: /integrations/homekit/
[mqtt docs]: /integrations/mqtt/
[scene docs]: /integrations/scene/
[sensibo docs]: /integrations/sensibo/
[shelly docs]: /integrations/shelly/
[xiaomi_miio docs]: /integrations/xiaomi_miio/
## Release 2022.3.4 - March 11
- Fix discord embed class initialization ([@cheng2wei] - [#67831]) ([discord docs])
- Support playing local "file" media on Kodi ([@rigrig] - [#67832]) ([kodi docs])
- Bump zwave-js-server-python to 0.35.2 ([@raman325] - [#67839]) ([zwave_js docs])
- Add missing callback decorator to sun ([@bdraco] - [#67840]) ([sun docs])
- Fix shelly duo scene restore ([@thecode] - [#67871]) ([shelly docs])
- Make sure blueprint cache is flushed on script reload ([@elupus] - [#67899]) ([script docs])
- Update radios to 0.1.1 ([@frenck] - [#67902]) ([radio_browser docs])
- Correct local import of paho-mqtt ([@emontnemery] - [#67944]) ([mqtt docs])
- Rollback pyinsteon ([@teharris1] - [#67956]) ([insteon docs])
- Bump pysabnzbd to 1.1.1 ([@Shutgun] - [#67971]) ([sabnzbd docs])
- Bump pymediaroom ([@dgomes] - [#68016]) ([mediaroom docs])
[#67831]: https://github.com/home-assistant/core/pull/67831
[#67832]: https://github.com/home-assistant/core/pull/67832
[#67839]: https://github.com/home-assistant/core/pull/67839
[#67840]: https://github.com/home-assistant/core/pull/67840
[#67871]: https://github.com/home-assistant/core/pull/67871
[#67899]: https://github.com/home-assistant/core/pull/67899
[#67902]: https://github.com/home-assistant/core/pull/67902
[#67944]: https://github.com/home-assistant/core/pull/67944
[#67956]: https://github.com/home-assistant/core/pull/67956
[#67971]: https://github.com/home-assistant/core/pull/67971
[#68016]: https://github.com/home-assistant/core/pull/68016
[@Shutgun]: https://github.com/Shutgun
[@bdraco]: https://github.com/bdraco
[@cheng2wei]: https://github.com/cheng2wei
[@dgomes]: https://github.com/dgomes
[@elupus]: https://github.com/elupus
[@emontnemery]: https://github.com/emontnemery
[@frenck]: https://github.com/frenck
[@raman325]: https://github.com/raman325
[@rigrig]: https://github.com/rigrig
[@teharris1]: https://github.com/teharris1
[@thecode]: https://github.com/thecode
[discord docs]: /integrations/discord/
[insteon docs]: /integrations/insteon/
[kodi docs]: /integrations/kodi/
[mediaroom docs]: /integrations/mediaroom/
[mqtt docs]: /integrations/mqtt/
[radio_browser docs]: /integrations/radio_browser/
[sabnzbd docs]: /integrations/sabnzbd/
[script docs]: /integrations/script/
[shelly docs]: /integrations/shelly/
[sun docs]: /integrations/sun/
[zwave_js docs]: /integrations/zwave_js/
## Release 2022.3.5 - March 15
- Fix WebSocketTimeoutException in SamsungTV ([@epenet] - [#68114]) ([samsungtv docs])
- 20220301.2 ([@zsarnett] - [#68130]) ([frontend docs])
- Filter IPv6 addresses from doorbird discovery ([@bdraco] - [#68031]) ([doorbird docs])
- Fix turning amcrest camera on and off ([@flacjacket] - [#68050]) ([amcrest docs])
- Fix Shelly EM/3EM invalid energy value after reboot ([@thecode] - [#68052]) ([shelly docs])
- Default somfy_mylink shade's _attr_is_closed to `None` ([@cthornton] - [#68053]) ([somfy_mylink docs])
- Bump amcrest version to 1.9.7 ([@flacjacket] - [#68055]) ([amcrest docs])
- Bump pyisy to 3.0.5 ([@bdraco] - [#68069]) ([isy994 docs])
- Update home_connect to 0.7.0 ([@BraveChicken1] - [#68089]) ([home_connect docs])
- Fix MQTT false positive deprecation warnings ([@jbouwh] - [#68117]) ([mqtt docs])
[#68031]: https://github.com/home-assistant/core/pull/68031
[#68050]: https://github.com/home-assistant/core/pull/68050
[#68052]: https://github.com/home-assistant/core/pull/68052
[#68053]: https://github.com/home-assistant/core/pull/68053
[#68055]: https://github.com/home-assistant/core/pull/68055
[#68069]: https://github.com/home-assistant/core/pull/68069
[#68089]: https://github.com/home-assistant/core/pull/68089
[#68114]: https://github.com/home-assistant/core/pull/68114
[#68117]: https://github.com/home-assistant/core/pull/68117
[#68130]: https://github.com/home-assistant/core/pull/68130
[@BraveChicken1]: https://github.com/BraveChicken1
[@bdraco]: https://github.com/bdraco
[@cthornton]: https://github.com/cthornton
[@epenet]: https://github.com/epenet
[@flacjacket]: https://github.com/flacjacket
[@jbouwh]: https://github.com/jbouwh
[@thecode]: https://github.com/thecode
[@zsarnett]: https://github.com/zsarnett
[amcrest docs]: /integrations/amcrest/
[doorbird docs]: /integrations/doorbird/
[frontend docs]: /integrations/frontend/
[home_connect docs]: /integrations/home_connect/
[isy994 docs]: /integrations/isy994/
[mqtt docs]: /integrations/mqtt/
[samsungtv docs]: /integrations/samsungtv/
[shelly docs]: /integrations/shelly/
[somfy_mylink docs]: /integrations/somfy_mylink/
## Need help? Join the community!
Home Assistant has a great community of users who are all more than willing

25
source/_posts/2022-03-14-cas-content-trust.markdown Normal file
View File

@ -0,0 +1,25 @@
---
layout: post
title: "Content Trust with Home Assistant & Codenotary CAS"
description: "Ability to verify that the updates which we deliver are the same as the update that you have fetched."
date: 2022-03-14 00:00:00
date_formatted: "March 14, 2022"
author: Pascal Vizeli
author_twitter: pvizeli
comments: true
categories:
- Announcements
---
We started to update how Home Assistant does content trust using [Codenotary CAS](https://cas.codenotary.com/).
With content trust, we can ensure that your system only runs containers/software as released by the original author. The author, in this case, can be the Home Assistant project, but also, for example, an add-on developer. This is an important security aspect, as it protects your instance from running possibly malicious software. Content trust verifies that the software you download, install or upgrade is exactly the same as it was released by its creator and ensures nobody messed with it along the way.
Codenotary CAS is built around a decentralized, cryptographically coherent and verifiable database technology called [immudb](https://github.com/codenotary/immudb). It is used to store all these trusted content signatures.
With immudb we will be able to host parts of the trusted content signatures data ourselves (we don't do this yet). It could even be made available as a Home Assistant add-on that users can install locally. Important to know is that CAS does not upload any user data for verification, it’s all done locally, just the way we like it.
When you install or update part of your system that is signed, it checks the CAS database to ensure that the image has not been revoked (similar to SSL with the CRL) and verifies that the download content, which we deliver over multiple public endpoints, is the same as the update that your system just has downloaded.
While rolling out the new system we ran into some issues which caused users unable to install updates for ~12 hours on March 11; for which we want to apologize. Thanks to the help from Codenotary engineers we were able to get it fixed in a quick and orderly fashion.
Pascal

2
source/getting-started/configuration.markdown
View File

@ -44,7 +44,7 @@ Now let's make a change using the file editor: we are going to change the name,
</div>
- Click the save icon in the top right to commit changes.
- Most changes in `configuration.yaml` require Home Assistant to be restarted to see the changes. You can verify that your changes are acceptable by running a configuration check. Do this by clicking on Configuration in the sidebar, click on "Server Controls" and click on the "CHECK configuration" button. When it's valid, it will show the text "Configuration valid!". In order for the "CHECK configuration" button to be visible, you must enable "Advanced Mode" on your user profile.
- Most changes in `configuration.yaml` require Home Assistant to be restarted to see the changes. You can verify that your changes are acceptable by running a configuration check. Do this by clicking on Configuration in the sidebar, click on "Settings", "Server Controls" and click on the "CHECK configuration" button. When it's valid, it will show the text "Configuration valid!". In order for the "CHECK configuration" button to be visible, you must enable "Advanced Mode" on your user profile.
- Now Restart Home Assistant using the "RESTART" button in the Server management section on the same page.
<p class='img'>

2
source/lovelace/actions.markdown
View File

@ -3,7 +3,7 @@ title: "Actions"
description: "Define what an object does when interacted with."
---
Some Lovelace cards have support for tap actions. These actions define what will happen when you tap or hold on an object within a card.
Some cards have support for tap actions. These actions define what will happen when you tap or hold on an object within a card.
Actions can be enabled on:

2
source/lovelace/badges.markdown
View File

@ -3,7 +3,7 @@ title: "Badges"
description: "Description of the various badges that are available."
---
Badges are widgets that sit at the top of a Lovelace panel, above all the cards.
Badges are widgets that sit at the top of a panel, above all the cards.
## State Label Badge

4
source/lovelace/cards.markdown
View File

@ -1,8 +1,8 @@
---
title: "Cards"
description: "Lovelace cards."
description: "Cards."
---
Cards provide a structure for interfacing with your Lovelace dashboard.
Cards provide a structure for interfacing with your dashboard.
There are several built-in card types, each with their own configuration options. Select a card from the menu to view additional details and the options for that card.

403
source/lovelace/changelog.markdown
View File

@ -1,403 +0,0 @@
---
title: "Lovelace Changelog"
description: "Changelog of the Lovelace UI."
---
## Changes in 0.105.0
* ✨ [entities card]: New `header` special row type (#4496) @balloob
* ✨ [entities card]: New `footer` special row type (#4496) @balloob
* ✨ [entities card]: Add `picture` option to header/footer (#4496) @balloob
* ✨ [entities card]: New `conditional` special row type (#4569) @iantrich
* ✨ [entities card]: Add `buttons` option to header/footer (#4601) @balloob
* ✨ [entities card]: Add `action_name` option for scene/script rows (#4571) @iantrich
* ✨ [entities card]: Add `state_color` option to color active/error/climate icons. Does not change the behavior of lights. Default is now `false` (#4510) @iantrich
* ✨ Update Material Design Icons to v4.8.95 (#4520) @goyney
* 💄 [entities card]: Automatically strip Area name from entities in Lovelace generated/auto mode (#4597) @balloob
* 💄 [entities card]: Fix alignment of header toggle (#4532) @bramkragten
* 💄 [light card]: Align height of card regardless of brightness support (#4582) @iantrich
* 💄 [map card]: Ignore zones when fitting map (#4447) @klejejs
* 💄 [entities card]: Show `Never triggered` when `secondary_info` set to `last-triggered` on an automation row and the automation has never been triggered (#4442) @Mariusthvdb
* 💄 Additional active/error/climate icon domains/states (#4510) @iantrich
* ♿ Close card editor on ESC (#4570) @iantrich
* ♿ Add tabindex to Lovelace elements (#4160) @iantrich
* 🐛 Fix action directive double tab iOS issues (#4639) @bramkragten
* 🐛 [gauge card]: Fix severity toggle (#4600) @iantrich
* 🐛 [Markdown card]: Fix visual editor for when all `content` removed (#4583) @iantrich
* 🐛 [alarm panel card]: Fix preview updates (#4592) @bramkragten
* 🐛 [thermostat card]: Fix display of current/set temperature when at 0 (#4498) @iantrich
* 🐛 [picture glance card]: Fix `camera_view` option in editor (#4495) @iantrich
* 🐛 Fix various card editor switches (#4584) @iantrich
* 🐛 Fix Lovelace reload button on error page (#4557) @bramkragten
* 🚸 [shopping list card]: Show error if integration is not loaded (#4523) @ludeeus
* 🚸 Prompt user to confirm logout (#4501) @iantrich
## Changes in 0.104.0
- ❤️ Add ability to remove Lovelace configuration [#4430](https://github.com/home-assistant/home-assistant-polymer/pull/4430) @bramkragten
- ❤️ Add support to add all device entities to Lovelace [#4356](https://github.com/home-assistant/home-assistant-polymer/pull/4356) @bramkragten
- 📣 Upgrade MDI icons to 4.7.95 [#4341](https://github.com/home-assistant/home-assistant-polymer/pull/4341) @bonanitech
## Changes in 0.101.0
- ❤️ [entities card]: Add actions on rows [#4023](https://github.com/home-assistant/home-assistant-polymer/pull/4023) @iantrich
- ❤️ [entities card]: New `icon` option for title [#4024](https://github.com/home-assistant/home-assistant-polymer/pull/4024) @iantrich
- ❤️ [views]: New `visible` option [#3811](https://github.com/home-assistant/home-assistant-polymer/pull/3811) @iantrich
- ❤️ [views]: Custom badges [#3867](https://github.com/home-assistant/home-assistant-polymer/pull/3867) @iantrich
- ❤️ [views]: New `entity-filter` badge [#3867](https://github.com/home-assistant/home-assistant-polymer/pull/3867) @iantrich
- ❤️ [views]: New `state-label` badge [#3867](https://github.com/home-assistant/home-assistant-polymer/pull/3867) @iantrich
- ❤️ [views]: Add actions to `state-label` badge [#4028](https://github.com/home-assistant/home-assistant-polymer/pull/4028) @iantrich
- ❤️ [shopping list card]: New `theme` option [#4057](https://github.com/home-assistant/home-assistant-polymer/pull/4057) @iantrich
- ❤️ [plant status card]: New `theme` option [#4057](https://github.com/home-assistant/home-assistant-polymer/pull/4057) @iantrich
- ❤️ [Markdown card]: New `theme` option [#4057](https://github.com/home-assistant/home-assistant-polymer/pull/4057) @iantrich
- ❤️ [alarm panel card]: New `theme` option [#4057](https://github.com/home-assistant/home-assistant-polymer/pull/4057) @iantrich
- ❤️ [picture card]: New `theme` option [#4057](https://github.com/home-assistant/home-assistant-polymer/pull/4057) @iantrich
- ❤️ [picture elements card]: New `theme` option [#4057](https://github.com/home-assistant/home-assistant-polymer/pull/4057) @iantrich
- ❤️ [picture elements card]: Add actions to `state-badge` element [#4028](https://github.com/home-assistant/home-assistant-polymer/pull/4028) @iantrich
- ❤️ [picture entity card]: New `theme` option [#4057](https://github.com/home-assistant/home-assistant-polymer/pull/4057) @iantrich
- ❤️ [picture glance card]: New `theme` option [#4057](https://github.com/home-assistant/home-assistant-polymer/pull/4057) @iantrich
- ❤️ [picture glance card]: New `show_state` option for entities [#3937](https://github.com/home-assistant/home-assistant-polymer/pull/3937) @iantrich
- ❤️ [weather forecast card]: New `theme` option [#4057](https://github.com/home-assistant/home-assistant-polymer/pull/4057) @iantrich
- ❤️ [vertical stack card]: New `title` option [#3839](https://github.com/home-assistant/home-assistant-polymer/pull/3839) @iantrich
- ❤️ [horizontal stack card]: New `title` option [#3839](https://github.com/home-assistant/home-assistant-polymer/pull/3839) @iantrich
- ❤️ New `double_tap_action` option [#3879](https://github.com/home-assistant/home-assistant-polymer/pull/3879) @iantrich
- ❤️ New `confirmation` option for actions [#4006](https://github.com/home-assistant/home-assistant-polymer/pull/4006) @iantrich
- ❤️ Theming: New CSS switch style: `switch-checked-color` [#4017](https://github.com/home-assistant/home-assistant-polymer/pull/4017) @iantrich
- ❤️ Theming: New CSS switch style: `switch-unchecked-color` [#4017](https://github.com/home-assistant/home-assistant-polymer/pull/4017) @iantrich
- ❤️ Theming: New CSS switch style: `switch-unchecked-button-color` [#4017](https://github.com/home-assistant/home-assistant-polymer/pull/4017) @iantrich
- ❤️ Theming: New CSS switch style: `switch-unchecked-track-color` [#4017](https://github.com/home-assistant/home-assistant-polymer/pull/4017) @iantrich
- 📣 Upgrade MDI icons to 4.5.95 [#3977](https://github.com/home-assistant/home-assistant-polymer/pull/3977) @bonanitech
- 📣 Display card errors in YAML instead of JSON [#4018](https://github.com/home-assistant/home-assistant-polymer/pull/4018) @iantrich
- ⚠️ revert Lovelace selectable text [#4095](https://github.com/home-assistant/home-assistant-polymer/pull/4095) @iantrich
- 🔧 [alarm panel card]: Visual accessibility changes [#3991](https://github.com/home-assistant/home-assistant-polymer/pull/3991) @mr-awk
- 🔧 [entities card]: Fix media row secondary info [#3957](https://github.com/home-assistant/home-assistant-polymer/pull/3957) @iantrich
- 🔧 [light card]: Fix name wrapping [#3972](https://github.com/home-assistant/home-assistant-polymer/pull/3972) @shbatm
- 🔧 [map card]: Fix zone icon visibility [#4085](https://github.com/home-assistant/home-assistant-polymer/pull/4085) @springstan
- 📣 [Markdown card]: Add default text to card editor [#3960](https://github.com/home-assistant/home-assistant-polymer/pull/3960) @akargl
## Changes in 0.100.0
- ❤️ [picture glance card]: New configuration `tap_action` and `hold_action` for `entities` [#3807](https://github.com/home-assistant/home-assistant-polymer/pull/3807) @iantrich
- ❤️ [entities card]: New configuration `image` for `entities` [#3832](https://github.com/home-assistant/home-assistant-polymer/pull/3832) @iantrich
- ❤️ [entity filter card]: Support for operators in `state_filter` and individual `state_filter` option for `entitites` [#3692](https://github.com/home-assistant/home-assistant-polymer/pull/3692) @iantrich
- ❤️ [light card]: New configuration `icon` [#3771](https://github.com/home-assistant/home-assistant-polymer/pull/3771) @iantrich
- ❤️ [picture entity card]: UI Editor [#3708](https://github.com/home-assistant/home-assistant-polymer/pull/3708) @iantrich
- ❤️ [picture glance card]: UI Editor [#3709](https://github.com/home-assistant/home-assistant-polymer/pull/3709) @iantrich
- ❤️ [history graph card]: UI Editor [#3782](https://github.com/home-assistant/home-assistant-polymer/pull/3782) @iantrich
- ❤️ Add `state_filter` to picture cards [#3791](https://github.com/home-assistant/home-assistant-polymer/pull/3791) @iantrich
- ❤️ Add a setting for vibration [#3813](https://github.com/home-assistant/home-assistant-polymer/pull/3813) @bramkragten
- ❤️ New Action `url` [#3773](https://github.com/home-assistant/home-assistant-polymer/pull/3773) @iantrich
- 📣 Add support for panels to cast [#3796](https://github.com/home-assistant/home-assistant-polymer/pull/3796) @bramkragten
- 📣 Allow for user text selection (Android Chrome not supported) [#3605](https://github.com/home-assistant/home-assistant-polymer/pull/3605) @iantrich
- ⚠️ Switch paper-toggle-button to mwc-switch [#3683](https://github.com/home-assistant/home-assistant-polymer/pull/3683) @iantrich
- 🔧 [map card]: Align background with tiles [#3858](https://github.com/home-assistant/home-assistant-polymer/pull/3858) @bramkragten
- 🔧 [map card]: Fix dark switch for map card editor [#3856](https://github.com/home-assistant/home-assistant-polymer/pull/3856) @bramkragten
- 🔧 [views]: Guard for null badges [#3841](https://github.com/home-assistant/home-assistant-polymer/pull/3841) @bramkragten
## Changes in 0.99.0
- ❤️ [glance card]: New configuration `show_last_changed` for `entities`
- ❤️ [glance card]: New configuration `image` for `entities`
- ❤️ [views]: New configuration `image` for `badges`
- ❤️ [views]: New configuration `icon` for `badges`
- ❤️ [views]: New configuration `name` for `badges`
- 📣 Unused entities: Rewritten into a table view
- 📣 Unused entities: Add entities to Lovelace cards
- 📣 Lovelace background settings moved to theme `--lovelace-background`
- 📣 Haptic feedback support added
- 📣 Vibrate support added
- 📣 MDI icons updated to [4.3.95](https://cdn.materialdesignicons.com/4.3.95/)
- ⚠️ Only allow admins to edit UI configuration
- 🔧 [alarm panel card]: Handle keyboard input
- 🔧 [alarm panel card]: Show `friendly_name` if set
- 🔧 [entities card]: Properly show "unavailable" timestamps
- 🔧 [entity filter card]: Throttle updates for performance
- 🔧 [light card]: Replace jQuery sliders
- 🔧 [light card]: Move brightness below icon
- 🔧 [map card]: Update preview when configuration changes
- 🔧 [Markdown card]: Don't allow SVG by default
- 🔧 Filter null badges
- 🔧 Render an overlay on light cards when the light is unavailable
- 🔧 Break long strings in notifications
## Changes in 0.88.0
- ❤️ Theming: New CSS card style `ha-card-box-shadow` ([#2855](https://github.com/home-assistant/home-assistant-polymer/pull/2855))
- 📣 Disable toast notifications for successful operations ([#2700](https://github.com/home-assistant/home-assistant-polymer/pull/2822))
- 📣 Color Picker: Toggleable between segmented and continuous ([#2806](https://github.com/home-assistant/home-assistant-polymer/pull/2806))
- 🔧 Fix login issue on Firefox ([#2860](https://github.com/home-assistant/home-assistant-polymer/pull/2860))
- 🔧 [light card]: Fix click events ([#2850](https://github.com/home-assistant/home-assistant-polymer/pull/2850))
## Changes in 0.87.0
- ❤️ Theming: New CSS card style `ha-card-border-radius`
- ❤️ Theming: New CSS card style `ha-card-background`
- ❤️ New system-health card in dev-info
- 📣 MDI icons updated to [3.3.92](https://cdn.materialdesignicons.com/3.3.92/)
- 📣 UI Editor: YAML syntax support
- 📣 UI Editor: Line numbers
- 📣 UI Editor: Now supports columns on wide screens
- 📣 Notifications: Indicator updated to show count of pending notifications
- 📣 [thermostat card]: more-info button added
- 📣 [light card]: more-info button added
- 🔧 [thermostat card]: Fix slider
- 🔧 Groups are now togglable
## Changes in 0.86.0
- ❤️ Lovelace is now the default UI for Home Assistant!
- ❤️ New Lovelace [demos](https://demo.home-assistant.io/#/lovelace/0) page
- 🔧 [thermostat card]: Fix sizing
- 🔧 [gauge card]: Fix sizing
- 🔧 [iframe card]: Fix card size
## Changes in 0.85.1
- 🔧 UI Editor: Fix removal of `resources` on save
- 🔧 Auto-gen correctly converts weblink entities to [weblink row]
- 🔧 The [weblink row] opens links in new tabs
## Changes in 0.85.0
- ❤️ [map card]: New configuration `geo_location_sources`
- ❤️ UI Editor for [picture card]
- ❤️ UI Editor for [weather forecast card]
- ❤️ UI Editor for [plant status card]
- ❤️ UI Editor for [media control card]
- ❤️ UI Editor for [iframe card]
- ❤️ UI Editor for [sensor card]
- ❤️ UI Editor for [shopping list card]
- ❤️ UI Editor for [light card]
- ❤️ UI Editor for [gauge card]
- ❤️ UI Editor for [Markdown card]
- ❤️ UI Editor for [alarm panel card]
- ❤️ UI Editor for [thermostat card]
- ❤️ UI Editor for [entity button card]
- ❤️ UI Editor for [map card]
- 📣 [alarm panel card]: Hide keypad if `code_format` attribute is not "Number"
- 📣 [alarm panel card]: Hide code input field if `code_format` attribute is not set
- 🔧 [thermostat card] Step logic updated to match more-info behavior
- 🔧 [weather forecast card] Proper RTL support
- 🔧 [thermostat card] Set minimum height of card
- 🔧 Fix incorrect state display being cached
- 🔧 Fix `service-button` element `service_data` usage
- 🔧 Fix `picture-elements` element positioning to account for card title
- 🔧 Fix undefined [plant status card]/[weather forecast card]
## Changes in 0.84.0
### Breaking Changes
- ⚠️ [views]: Renamed `id` to `path`
- ⚠️ `sensor_data`: `entity` is no longer passed as `entity_id` to service call and must be explicitly set
- ⚠️ [sensor card]: Removed configs `height`, `line_color` and `line_width`
- ⚠️ [gauge card]: Renamed configuration `title` to `name`
- ⚠️ [alarm panel card]: Renamed configuration `title` to `name`
- ⚠️ [glance card]: `tap_action` and `hold_action` configurations changed. See documentation.
- ⚠️ [entity button card]: `tap_action` and `hold_action` configurations changed. See documentation.
- ⚠️ [picture card]: `tap_action` and `hold_action` configurations changed. See documentation.
- ⚠️ [picture elements card]: `tap_action` and `hold_action` configurations for elements changed. See documentation.
- ⚠️ [picture entity card]: `tap_action` and `hold_action` configurations changed. See documentation.
- ⚠️ [picture glance card]: `tap_action` and `hold_action` configurations changed. See documentation.
### All Changes
- ❤️ [weather forecast card]: New configuration `name`
- ❤️ [thermostat card]: New configuration `name`
- ❤️ [plant status card]: New configuration `name`
- ❤️ [picture elements card]: Added `state_image` and `camera_image`
- 📣 [entities card]: Alert entity rows are now displayed as toggles
- 📣 Ability to generate a Lovelace configuration if not present using available entities
- 📣 UI Editor now in Beta with support for adding/removing views/cards
- 🔧 [map card]: Fix `aspect_ratio`
- 🔧 Fix Tap/Hold actions on Windows 10 machines with touchscreens
## Changes in 0.83.0
- ❤️ New card type: `shopping-list`
## Changes in 0.82.0
- ❤️ New card type: `light`
- ❤️ Alpha release of UI Editor
- ❤️ [entities card]: New `theme` option
- ❤️ [gauge card]: New `theme` option
- ❤️ [light card]: New `theme` option
- ❤️ [thermostat card]: New `theme` option
- 🔧 `!secret` and `!include` usage restored for manual editing, but are not supported with the UI editor
## Changes in 0.81.0
- ❤️ New card type: `alarm-panel`
- ❤️ New card type: `thermostat`
- ❤️ New card type: `entity-button`
- ❤️ [glance card]: New `theme` option
- ❤️ [glance card]: New `columns` option
- ❤️ [entity button card]: New `theme` option
- 📣 Long press is now supported
- 📣 Update to allow the use of Custom UI. If you run into issues please disable Custom UI and test before reporting them. If the issue goes away without Custom UI please report this to the Custom UI developer as this is not officially supported.
## Changes in 0.80.0
- ❤️ New card type: `sensor`
- ❤️ New card type: `gauge`
## Changes in 0.77.0
- ❤️ New notification drawer
## Changes in 0.75.0
### Breaking changes
- ⚠️ [glance card]: `turn-on` replaced with `call-service`
### All changes
- ❤️ New card type: `conditional-card` (Drop your [entity filter card] hacks)
- 📣 Add support for CSS imports
- 📣 [picture glance card]: Add support for custom icons
- 📣 [picture entity card]: Supports hiding name and/or state
- ⚠️ [glance card]: `turn-on` replaced with `call-service`
- 📣 [glance card]: Allow selectively empty names
- 📣 [picture elements card]: `state-label` now supports prefix and suffix
- 📣 [entities card]: Row dividers
- 📣 [entities card] and [glance card]: Custom icons support
- 📣 [entities card]: Add call service support to the rows
- 🔧 [entities card]: Climate entities row available again
- 🔧 [entities card]: Automation and vacuum are again toggleable
- 🔧 [entities card]: Weblinks now work
- 🔧 [entities card]: Groups as toggleable entities fix
- 🔧 [entities card]: Fixed toggleable state when entity unavailable
- 🔧 [entities card]: Fix header toggle for entity objects
- 🔧 [history graph card]: Fix cache of image between views
## Changes in 0.74.0
- 📣 [Lovelace card gallery](https://www.awesome-ha.com/)
- 🔧 Async communication improvements
### Views
- 📣 Allow views with badges and no cards
- 📣 Add basic support for `badges` like in old view style
- 🔧 Custom cards now work with `panel: true`
### Cards
- 📣 [picture elements card]: Allow custom elements including custom cards
- 📣 [entities card]: Separate row entity elements, and add `secondary_info`
- 📣 [glance card]: Make column width configurable
- 📣 [glance card]: Entity `tap_action` can now be `toggle` and `turn-on` besides the default of showing the more info dialog
- 📣 [glance card]: Support added to hide `name` or `state`
- 📣 [history graph card]: Support added to override entity names
- 📣 [picture glance card]: Support added to open the more info dialog for cameras and media players.
- 📣 [picture elements card]: Support new element type `image`
- 📣 [picture elements card]: Support new element type `service-icon`
- 🔧 [entity filter card]: Fix edge cases that could make it crash ([supports this new use case](https://github.com/home-assistant/ui-schema/issues/82))
- 🔧 [picture glance card]: Fix crash when the state of entity was unavailable
- 🔧 [picture glance card]: Use custom off states
- 🔧 [picture glance card]: Fixed to work again with [entity filter card]
- 🔧 Removed `text-transform: capitalize;` from card heading
## Changes in 0.73.1
- 📣 Setting Lovelace as default now updates `Overview` button to point to `/lovelace`
- 📣 Allow setting background styles (global and per view)
### Cards
- ❤️ New card type: `map` that allows showing `device_tracker` entities on a map card
- 📣 [entities card] card now support `type: custom:state-card-custom` for the entities list
## Changes in 0.73.0
### Views
- 📣 New button to show unused entities in Lovelace
## Changes in 0.73.0b4
### Cards
- 📣 [picture entity card] allow hiding of infobar using `show_info: false`
- 📣 [picture entity card] now supports `tap_action` parameter allowing you to switch from `on`/`off` to `more-info-dialog`
- 📣 [picture glance card] now supports `navigation_path`
- ⚠️ [picture entity card] renamed `title` to `name`
- ⚠️ [picture elements card] renamed `path` to `navigation_path`
- ⚠️ `camera-preview` card removed, features added to [picture entity card] and [picture glance card]
## Changes in 0.73.0b3
### Views
- 📣 Added panel mode for a view to use the 1st card to fill the whole screen
### Cards
- ❤️ New card: `picture` for triggering navigation and services
- 📣 [picture elements card] now supports `navigation` type
- 📣 [picture entity card] now supports `camera_image`
- 📣 [picture glance card] now supports `camera_image`
- 📣 [picture glance card] now supports `state_image` and `entity` like [picture entity card]
- 📣 [entity filter card] now supports custom name for entities like `glance` and [entities card]
- ⚠️ [entities card] and `glance` custom titles now use `name` not `title`
- ⚠️ [entity filter card] now uses [entities card] as a static list to filter state against
- ⚠️ [entity filter card] uses `state_filter` array instead of `filter` object
- ⚠️ [entity filter card] no longer allows to show all entities or a full domain
- 🔧 Fix wrapping and padding for `service-button` in [picture elements card]
## Changes in 0.73.0b1
### Cards
- ⚠️ `column` renamed to `vertical-stack`
- ⚠️ `row` renamed to `horizontal-stack`
- ⚠️ [picture elements card] renamed `state-badge` to `state-icon`
- ⚠️ [picture elements card] renamed `state-text` to `state-label`
- ⚠️ [picture elements card] moved/renamed `service.data` to `service_data`
- 📣 [picture elements card] new `state-badge` using `ha-state-label-badge`
- 📣 [picture elements card] combined `service.domain` and `service.server` into `service`
- 📣 [entities card] allow custom title just like `glance`
- 📣 [entity filter card] allow auto-hide if empty using `show_empty: false`
- 🔧 Fix card size calculation `horizontal-stack`/`vertical-stack`
## Changes in 0.73.0b0
- 📣 New feature to allow Lovelace to be default for `/`
### Views
- 📣 Now views have deep-links: `/lovelace/3` will link to the tab with id `3`
- ⚠️ `name` renamed `title` to match cards setup
- ⚠️ `tab_icon` renamed `icon` for simplicity
### Cards
- ❤️ New card: [picture elements card]
- ❤️ New card: `column`
- ❤️ New card: `row`
- 📣 `glance` allow custom title for entities - rename your entity only in this card
- 📣 [entities card] toggle button in a header can now be hidden using `show_header_toggle: false`
- ⚠️ `entity-picture` renamed [picture entity card] to be consistent with [picture glance card]
- ⚠️ [entity filter card] removed `card_config` and made `card` property an object
- 🔧 Fix use of groups in [picture entity card]
- 🔧 Fix the title in `glance` to avoid overlapping
## Changes in 0.72.1
### Cards
- 🐞 Bug introduced in `glance` card - titles now overlap
- ❤️ New card: `iframe`
## Changes in 0.72
- ❤️ Initial release of the Lovelace UI
[views]: /lovelace/views/
[alarm panel card]: /lovelace/alarm-panel/
[conditional card]: /lovelace/conditional/
[entities card]: /lovelace/entities/
[entity button card]: /lovelace/entity-button/
[entity filter card]: /lovelace/entity-filter/
[gauge card]: /lovelace/gauge/
[glance card]: /lovelace/glance/
[history graph card]: /lovelace/history-graph/
[horizontal stack card]: /lovelace/horizontal-stack/
[iframe card]: /lovelace/iframe/
[light card]: /lovelace/light/
[map card]: /lovelace/map/
[markdown card]: /lovelace/markdown/
[media control card]: /lovelace/media-control/
[picture elements card]: /lovelace/picture-elements/
[picture entity card]: /lovelace/picture-entity/
[picture glance card]: /lovelace/picture-glance/
[picture card]: /lovelace/picture/
[plant status card]: /lovelace/plant-status/
[sensor card]: /lovelace/sensor/
[shopping list card]: /lovelace/shopping-list/
[thermostat card]: /lovelace/thermostat/
[vertical stack card]: /lovelace/vertical-stack/
[weather forecast card]: /lovelace/weather-forecast/
[weblink row]: /lovelace/entities/#weblink

32
source/lovelace/dashboards.markdown
View File

@ -1,11 +1,11 @@
---
title: "Dashboards"
description: "The Lovelace UI is a powerful and configurable interface for Home Assistant."
description: "A powerful and configurable interface for Home Assistant."
---
You can define multiple dashboards in Lovelace. Each dashboard can be added to the sidebar. This makes it possible to create separate control dashboards for each individual part of your house.
You can define multiple dashboards in Home Assistant. Each dashboard can be added to the sidebar. This makes it possible to create separate control dashboards for each individual part of your house.
You can manage your dashboards via the user interface. Go to **Configuration** -> **Lovelace Dashboards**. Here you can see all defined dashboards and create new ones.
You can manage your dashboards via the user interface. Go to **Configuration** -> **Dashboards**. Here you can see all defined dashboards and create new ones.
## Using YAML for the default dashboard
@ -21,13 +21,13 @@ A good way to start this file is to copy and paste the "Raw configuration" from
- Click `Overview` in your sidebar.
- Click the three dots menu (top-right) and click on `Edit Dashboard`.
- Click the three dots menu again and click on `Raw configuration editor`.
- There you see the configuration for your current Lovelace UI. Copy that into the `<config>/ui-lovelace.yaml` file.
- There you see the configuration for your current dashboard. Copy that into the `<config>/ui-lovelace.yaml` file.
Once you take control of your UI via YAML, the Home Assistant interface for modifying it won't be available anymore and new entities will not automatically be added to your UI.
When you make changes to `ui-lovelace.yaml`, you don't have to restart Home Assistant or refresh the page. Just hit the refresh button in the menu at the top of the UI.
To revert back to using the UI to edit your Lovelace interface, remove the `lovelace` section from your `configuration.yaml` and copy the contents of your `ui-lovelace.yaml` into the raw configuration section of Home Assistant and restart.
To revert back to using the UI to edit your dashboard, remove the `lovelace` section from your `configuration.yaml` and copy the contents of your `ui-lovelace.yaml` into the raw configuration section of Home Assistant and restart.
## Adding more dashboards with YAML
@ -36,7 +36,7 @@ It is also possible to use YAML to define multiple dashboards. Each dashboard wi
```yaml
lovelace:
mode: yaml
# Include external resources only add when mode is yaml, otherwise manage in the resources in the lovelace configuration panel.
# Include external resources only add when mode is yaml, otherwise manage in the resources in the dashboard configuration panel.
resources:
- url: /local/my-custom-card.js
type: module
@ -76,11 +76,11 @@ lovelace:
{% configuration Lovelace %}
mode:
required: true
description: "In what mode should the main Lovelace panel be, `yaml` or `storage` (UI managed)."
description: "In what mode should the main dashboard be, `yaml` or `storage` (UI managed)."
type: string
resources:
required: false
description: "List of resources that should be loaded when you use Lovelace. Only use this when mode is `yaml`. If you change anything here, click the three dots menu (top-right) and click on `Reload resources` for Lovelace to pick up changes without restarting Home Assistant. You can also call `lovelace.reload_resources` service directly."
description: "List of resources that should be loaded. Only use this when mode is `yaml`. If you change anything here, click the three dots menu (top-right) and click on `Reload resources` to pick up changes without restarting Home Assistant. You can also call `lovelace.reload_resources` service directly."
type: list
keys:
url:
@ -93,16 +93,16 @@ resources:
type: string
dashboards:
required: false
description: Additional Lovelace YAML dashboards. The key is used for the URL and should contain a hyphen (`-`)
description: Additional YAML dashboards. The key is used for the URL and should contain a hyphen (`-`)
type: map
keys:
mode:
required: true
description: "The mode of the dashboard, this should always be `yaml`. Dashboards in `storage` mode can be created in the Lovelace configuration panel."
description: "The mode of the dashboard, this should always be `yaml`. Dashboards in `storage` mode can be created in the configuration panel."
type: string
filename:
required: true
description: "The file in your `config` directory where the Lovelace configuration for this panel is."
description: "The file in your `config` directory where the configuration for this panel is."
type: string
title:
required: true
@ -124,7 +124,7 @@ dashboards:
default: false
{% endconfiguration %}
As a super minimal example of a Lovelace dashboard config, here's the bare minimum you will need for it to work:
As a super minimal example of a dashboard config, here's the bare minimum you will need for it to work:
```yaml
title: My Awesome Home
@ -134,9 +134,9 @@ views:
cards:
# The markdown card will render markdown text.
- type: markdown
title: Lovelace
title: Dashboard
content: >
Welcome to your **Lovelace UI**.
Welcome to your **dashboard**.
```
A slightly more advanced example:
@ -188,7 +188,7 @@ views:
# The markdown card will render markdown text.
- type: markdown
title: Lovelace
title: Dashboard
content: >
Welcome to your **Lovelace UI**.
Welcome to your **dashboard**.
```

6
source/lovelace/header-footer.markdown
View File

@ -1,9 +1,9 @@
---
title: "Headers & Footers for Lovelace cards"
description: "Decorate your Lovelace cards with header and footer widgets."
title: "Headers & Footers for dashboard cards"
description: "Decorate your dashboard cards with header and footer widgets."
---
Some Lovelace cards have support for header and footer widgets. These widgets fill up the whole available space in a card.
Some dashboard cards have support for header and footer widgets. These widgets fill up the whole available space in a card.
<p class='img'><img src='/images/lovelace/header-footer/screenshot-picture-buttons.png' alt="Screenshot of an entities card with a picture header.">
Screenshot of an entities card with a picture header and buttons footer.

15
source/lovelace/how-it-works.markdown
View File

@ -1,15 +0,0 @@
---
title: "How Lovelace Works"
description: "Explains how Lovelace works under the hood."
---
The old user interface relied solely on the state machine. This caused trouble as it meant that the state machine was now not only the source for device states, but also for user interface configuration. With Lovelace, we're taking a completely different approach. All user interface configuration will live in a separate file, controlled by the user.
<p class='img'>
<img
src='/images/lovelace/lovelace-ui-comparison.png'
alt='Diagram showing how states no longer contain UI configuration.'>
Visual comparison of old configuration versus new configuration
</p>
<!-- source: https://docs.google.com/drawings/d/1O1o7-wRlnsU1lLgfdtn3s46P5StJjSL5to5RU9SV8zs/edit?usp=sharing -->

14
source/lovelace/index.markdown
View File

@ -1,12 +1,12 @@
---
title: "Lovelace"
description: "Lovelace is a powerful and configurable dashboard for Home Assistant."
title: "Dashboard"
description: "A powerful and configurable dashboard for Home Assistant."
---
Lovelace is the Home Assistant dashboard. It is a fast, customizable and powerful way for users to manage their home using their mobiles and desktops.
The Home Assistant dashboard is a fast, customizable and powerful way for users to manage their home using their mobiles and desktops.
- 29 different cards to place and configure as you like.
- Dashboard Editor: Allows you to manage your Lovelace dashboard by including a live preview when editing cards.
- Dashboard Editor: Allows you to manage your dashboard by including a live preview when editing cards.
- Fast: Using a static configuration allows us to build up the dashboard once.
- Customizable:
- Cards have a number of options which help to configure your data as required.
@ -22,12 +22,12 @@ To start, go to the Home Assistant Overview page, click on the three dots at the
To try it yourself, check out [the demo](https://demo.home-assistant.io).
## Discuss Lovelace
## Discuss dashboard
- Suggestions are welcome in the [frontend repository](https://github.com/home-assistant/frontend/)
- For help with Lovelace, join the `#frontend` channel on [our chat](/join-chat/) or [our forums](https://community.home-assistant.io/c/projects/frontend)
- For help with dashboards, join the `#frontend` channel on [our chat](/join-chat/) or [our forums](https://community.home-assistant.io/c/projects/frontend)
## Additional Lovelace Resources
## Additional Resources
- [Awesome HA](https://www.awesome-ha.com/#lovelace-user-interface)
- [Community Custom Cards](https://github.com/custom-cards)

6
source/lovelace/views.markdown
View File

@ -1,12 +1,12 @@
---
title: "Views"
description: "A Lovelace view is a tab inside a Lovelace dashboard."
description: "A view is a tab inside a dashboard."
---
A View is a tab inside a Lovelace dashboard.
A View is a tab inside a dashboard.
To display cards on the UI you have to define them in views.
You can add a view to your user interface, by clicking the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**.
You can add a view to your user interface, by clicking the menu (three dots at the top right of the screen) and then **Edit Dashboard**.
Click the `+` button in the top menu bar.
<p class="img">