diff --git a/CODEOWNERS b/CODEOWNERS index b480dab71eb..8ec4169cf5b 100644 --- a/CODEOWNERS +++ b/CODEOWNERS @@ -27,7 +27,6 @@ source/_integrations/alert.markdown @home-assistant/core source/_integrations/alexa.markdown @home-assistant/cloud @ochlocracy source/_integrations/alexa.smart_home.markdown @home-assistant/cloud @ochlocracy source/_integrations/almond.markdown @gcampax @balloob -source/_integrations/alpha_vantage.markdown @fabaff source/_integrations/ambee.markdown @frenck source/_integrations/amberelectric.markdown @madpilot source/_integrations/ambiclimate.markdown @danielhiversen @@ -41,7 +40,6 @@ source/_integrations/apple_tv.markdown @postlund source/_integrations/apprise.markdown @caronc source/_integrations/aprs.markdown @PhilRW source/_integrations/arcam_fmj.markdown @elupus -source/_integrations/arest.markdown @fabaff source/_integrations/arris_tg2492lg.markdown @vanbalken source/_integrations/aseko_pool_live.markdown @milanmeu source/_integrations/asuswrt.markdown @kennedyshead @ollo69 @@ -64,7 +62,6 @@ source/_integrations/backup.markdown @home-assistant/core source/_integrations/balboa.markdown @garbled1 source/_integrations/beewi_smartclim.markdown @alemuro source/_integrations/binary_sensor.markdown @home-assistant/core -source/_integrations/bitcoin.markdown @fabaff source/_integrations/bizkaibus.markdown @UgaitzEtxebarria source/_integrations/blebox.markdown @bbx-a @bbx-jp source/_integrations/blink.markdown @fronzbot @@ -136,7 +133,6 @@ source/_integrations/dsmr.markdown @Robbie1221 @frenck source/_integrations/dsmr_reader.markdown @depl0y source/_integrations/dunehd.markdown @bieniu source/_integrations/dwd_weather_warnings.markdown @runningman84 @stephan192 @Hummel95 -source/_integrations/dweet.markdown @fabaff source/_integrations/dynalite.markdown @ziv1234 source/_integrations/ecobee.markdown @marthoc source/_integrations/econet.markdown @vangorra @w1ll1am23 @@ -183,7 +179,6 @@ source/_integrations/fjaraskupan.markdown @elupus source/_integrations/flick_electric.markdown @ZephireNZ source/_integrations/flipr.markdown @cnico source/_integrations/flo.markdown @dmulcahey -source/_integrations/flock.markdown @fabaff source/_integrations/flume.markdown @ChrisMandich @bdraco source/_integrations/flunearyou.markdown @bachya source/_integrations/flux_led.markdown @icemanch @bdraco @@ -195,6 +190,7 @@ source/_integrations/freebox.markdown @hacf-fr @Quentame source/_integrations/freedompro.markdown @stefano055415 source/_integrations/fritz.markdown @mammuth @AaronDavidSchneider @chemelli74 @mib1185 source/_integrations/fritzbox.markdown @mib1185 @flabbamann +source/_integrations/fritzbox_callmonitor.markdown @cdce8p source/_integrations/fronius.markdown @nielstron @farmio source/_integrations/frontend.markdown @home-assistant/frontend source/_integrations/garages_amsterdam.markdown @klaasnicolaas @@ -209,8 +205,7 @@ source/_integrations/geonetnz_quakes.markdown @exxamalte source/_integrations/geonetnz_volcano.markdown @exxamalte source/_integrations/gios.markdown @bieniu source/_integrations/github.markdown @timmo001 @ludeeus -source/_integrations/gitter.markdown @fabaff -source/_integrations/glances.markdown @fabaff @engrbm87 +source/_integrations/glances.markdown @engrbm87 source/_integrations/goalzero.markdown @tkdrob source/_integrations/gogogate2.markdown @vangorra @bdraco source/_integrations/goodwe.markdown @mletenay @starkillerOG @@ -261,7 +256,7 @@ source/_integrations/ign_sismologia.markdown @exxamalte source/_integrations/image.markdown @home-assistant/core source/_integrations/image_processing.markdown @home-assistant/core source/_integrations/incomfort.markdown @zxdavb -source/_integrations/influxdb.markdown @fabaff @mdegat01 +source/_integrations/influxdb.markdown @mdegat01 source/_integrations/input_boolean.markdown @home-assistant/core source/_integrations/input_button.markdown @home-assistant/core source/_integrations/input_datetime.markdown @home-assistant/core @@ -303,6 +298,7 @@ source/_integrations/launch_library.markdown @ludeeus @DurgNomis-drol source/_integrations/lcn.markdown @alengwenus source/_integrations/lg_netcast.markdown @Drafteed source/_integrations/life360.markdown @pnbruckner +source/_integrations/lifx.markdown @Djelibeybi source/_integrations/light.markdown @home-assistant/core source/_integrations/linux_battery.markdown @fabaff source/_integrations/litejet.markdown @joncar @@ -322,6 +318,7 @@ source/_integrations/lyric.markdown @timmo001 source/_integrations/mastodon.markdown @fabaff source/_integrations/matrix.markdown @tinloaf source/_integrations/mazda.markdown @bdr99 +source/_integrations/meater.markdown @Sotolotl @emontnemery source/_integrations/media_player.markdown @home-assistant/core source/_integrations/media_source.markdown @hunterjm source/_integrations/mediaroom.markdown @dgomes @@ -348,7 +345,6 @@ source/_integrations/monoprice.markdown @etsinko @OnFreund source/_integrations/moon.markdown @fabaff @frenck source/_integrations/motion_blinds.markdown @starkillerOG source/_integrations/motioneye.markdown @dermotduffy -source/_integrations/mpd.markdown @fabaff source/_integrations/mqtt.markdown @emontnemery source/_integrations/msteams.markdown @peroyvind source/_integrations/mullvad.markdown @meichthys @@ -376,7 +372,6 @@ source/_integrations/nilu.markdown @hfurubotten source/_integrations/nina.markdown @DeerMaximum source/_integrations/nissan_leaf.markdown @filcole source/_integrations/nmbs.markdown @thibmaek -source/_integrations/no_ip.markdown @fabaff source/_integrations/noaa_tides.markdown @jdelaney72 source/_integrations/notify.markdown @home-assistant/core source/_integrations/notify_events.markdown @matrozov @papajojo @@ -416,7 +411,7 @@ source/_integrations/panel_iframe.markdown @home-assistant/frontend source/_integrations/peco.markdown @IceBotYT source/_integrations/persistent_notification.markdown @home-assistant/core source/_integrations/philips_js.markdown @elupus -source/_integrations/pi_hole.markdown @fabaff @johnluetke @shenxn +source/_integrations/pi_hole.markdown @johnluetke @shenxn source/_integrations/picnic.markdown @corneyl source/_integrations/pilight.markdown @trekky12 source/_integrations/plaato.markdown @JohNan @@ -434,10 +429,11 @@ source/_integrations/proxmoxve.markdown @jhollowe @Corbeno source/_integrations/ps4.markdown @ktnrg45 source/_integrations/pure_energie.markdown @klaasnicolaas source/_integrations/push.markdown @dgomes -source/_integrations/pvoutput.markdown @fabaff @frenck +source/_integrations/pvoutput.markdown @frenck source/_integrations/pvpc_hourly_pricing.markdown @azogue source/_integrations/qbittorrent.markdown @geoffreylagaisse source/_integrations/qld_bushfire.markdown @exxamalte +source/_integrations/qnap_qsw.markdown @Noltari source/_integrations/quantum_gateway.markdown @cisasteelersfan source/_integrations/qvr_pro.markdown @oblogic7 source/_integrations/qwikswitch.markdown @kellerza @@ -470,6 +466,7 @@ source/_integrations/rpi_power.markdown @shenxn @swetoast source/_integrations/rss_feed_template.markdown @home-assistant/core source/_integrations/rtsp_to_webrtc.markdown @allenporter source/_integrations/ruckus_unleashed.markdown @gabe565 +source/_integrations/sabnzbd.markdown @shaiu source/_integrations/safe_mode.markdown @home-assistant/core source/_integrations/saj.markdown @fredericvl source/_integrations/samsungtv.markdown @chemelli74 @epenet @@ -486,6 +483,7 @@ source/_integrations/senseme.markdown @mikelawrence @bdraco source/_integrations/sensibo.markdown @andrey-git @gjohansson-ST source/_integrations/sensor.markdown @home-assistant/core source/_integrations/sentry.markdown @dcramer @frenck +source/_integrations/senz.markdown @milanmeu source/_integrations/serial.markdown @fabaff source/_integrations/seven_segments.markdown @fabaff source/_integrations/sharkiq.markdown @JeffResc @funkybunch @AritroSaha10 @@ -504,6 +502,7 @@ source/_integrations/sky_hub.markdown @rogerselwyn source/_integrations/slack.markdown @bachya source/_integrations/sleepiq.markdown @mfugate1 @kbickar source/_integrations/slide.markdown @ualex73 +source/_integrations/slimproto.markdown @marcelveldt source/_integrations/sma.markdown @kellerza @rklomp source/_integrations/smappee.markdown @bsmappee source/_integrations/smart_meter_texas.markdown @grahamwetzler @@ -512,7 +511,6 @@ source/_integrations/smarttub.markdown @mdz source/_integrations/smarty.markdown @z0mbieprocess source/_integrations/smhi.markdown @gjohansson-ST source/_integrations/sms.markdown @ocalvo -source/_integrations/smtp.markdown @fabaff source/_integrations/solaredge.markdown @frenck source/_integrations/solaredge_local.markdown @drobtravels @scheric source/_integrations/solarlog.markdown @Ernst79 @@ -527,11 +525,12 @@ source/_integrations/speedtestdotnet.markdown @rohankapoorcom @engrbm87 source/_integrations/spider.markdown @peternijssen source/_integrations/splunk.markdown @Bre77 source/_integrations/spotify.markdown @frenck -source/_integrations/sql.markdown @dgomes +source/_integrations/sql.markdown @dgomes @gjohansson-ST source/_integrations/squeezebox.markdown @rajlaud source/_integrations/srp_energy.markdown @briglx source/_integrations/starline.markdown @anonym-tsk source/_integrations/statistics.markdown @fabaff @ThomDietrich +source/_integrations/steam_online.markdown @tkdrob source/_integrations/steamist.markdown @bdraco source/_integrations/stiebel_eltron.markdown @fucm source/_integrations/stookalert.markdown @fwestenberg @frenck @@ -553,7 +552,6 @@ source/_integrations/syncthing.markdown @zhulik source/_integrations/syncthru.markdown @nielstron source/_integrations/synology_dsm.markdown @hacf-fr @Quentame @mib1185 source/_integrations/synology_srm.markdown @aerialls -source/_integrations/syslog.markdown @fabaff source/_integrations/system_bridge.markdown @timmo001 source/_integrations/tado.markdown @michaelarnauts @north3221 source/_integrations/tag.markdown @balloob @dmulcahey @@ -561,7 +559,7 @@ source/_integrations/tailscale.markdown @frenck source/_integrations/tankerkoenig.markdown @guillempages @mib1185 source/_integrations/tapsaff.markdown @bazwilliams source/_integrations/tasmota.markdown @emontnemery -source/_integrations/tautulli.markdown @ludeeus +source/_integrations/tautulli.markdown @ludeeus @tkdrob source/_integrations/tellduslive.markdown @fredrike source/_integrations/template.markdown @PhracturedBlue @tetienne @home-assistant/core source/_integrations/tesla_wall_connector.markdown @einarhauks @@ -576,14 +574,15 @@ source/_integrations/todoist.markdown @boralyl source/_integrations/tolo.markdown @MatthiasLohr source/_integrations/tomorrowio.markdown @raman325 source/_integrations/totalconnect.markdown @austinmroczek -source/_integrations/tplink.markdown @rytilahti @thegardenmonkey +source/_integrations/tplink.markdown @rytilahti @thegardenmonkey @bdraco source/_integrations/traccar.markdown @ludeeus source/_integrations/tractive.markdown @Danielhiversen @zhulik @bieniu +source/_integrations/trafikverket_ferry.markdown @gjohansson-ST source/_integrations/trafikverket_train.markdown @endor-force @gjohansson-ST source/_integrations/trafikverket_weatherstation.markdown @endor-force @gjohansson-ST source/_integrations/transmission.markdown @engrbm87 @JPHutchins source/_integrations/tts.markdown @pvizeli -source/_integrations/tuya.markdown @Tuya @zlinoliver @METISU @frenck +source/_integrations/tuya.markdown @Tuya @zlinoliver @frenck source/_integrations/twentemilieu.markdown @frenck source/_integrations/twinkly.markdown @dr1rrb @Robbie1221 source/_integrations/unifi.markdown @Kane610 @@ -593,7 +592,6 @@ source/_integrations/upb.markdown @gwww source/_integrations/upc_connect.markdown @pvizeli @fabaff source/_integrations/upcloud.markdown @scop source/_integrations/update.markdown @home-assistant/core -source/_integrations/updater.markdown @home-assistant/core source/_integrations/upnp.markdown @StevenLooman @ehendrix23 source/_integrations/uptime.markdown @frenck source/_integrations/uptimerobot.markdown @ludeeus @chemelli74 @@ -608,7 +606,7 @@ source/_integrations/venstar.markdown @garbled1 source/_integrations/vera.markdown @pavoni source/_integrations/verisure.markdown @frenck source/_integrations/versasense.markdown @flamm3blemuff1n -source/_integrations/version.markdown @fabaff @ludeeus +source/_integrations/version.markdown @ludeeus source/_integrations/vesync.markdown @markperdue @webdjoe @thegardenmonkey source/_integrations/vicare.markdown @oischinger source/_integrations/vilfo.markdown @ManneW diff --git a/Gemfile b/Gemfile index d6c78680e5d..3ed26dab7a3 100644 --- a/Gemfile +++ b/Gemfile @@ -20,7 +20,7 @@ group :jekyll_plugins do end gem 'sinatra', '2.2.0' -gem 'nokogiri', '1.13.4' +gem 'nokogiri', '1.13.6' # Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem # and associated library diff --git a/Gemfile.lock b/Gemfile.lock index 0fd98868c3c..887b6f3aa0e 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -70,10 +70,10 @@ GEM multi_json (1.15.0) mustermann (1.1.1) ruby2_keywords (~> 0.0.1) - nokogiri (1.13.4) + nokogiri (1.13.6) mini_portile2 (~> 2.8.0) racc (~> 1.4) - nokogiri (1.13.4-x64-mingw32) + nokogiri (1.13.6-x64-mingw32) racc (~> 1.4) pathutil (0.16.2) forwardable-extended (~> 2.6) @@ -123,7 +123,7 @@ DEPENDENCIES jekyll-paginate (= 1.1.0) jekyll-sitemap (= 1.4.0) jekyll-toc (= 0.17.1) - nokogiri (= 1.13.4) + nokogiri (= 1.13.6) rake (= 13.0.6) sass-globbing (= 1.1.5) sassc (= 2.1.0) diff --git a/_config.yml b/_config.yml index 54e41a025db..5aaa9940891 100644 --- a/_config.yml +++ b/_config.yml @@ -106,9 +106,9 @@ social: # Home Assistant release details current_major_version: 2022 -current_minor_version: 4 -current_patch_version: 7 -date_released: 2022-04-24 +current_minor_version: 5 +current_patch_version: 3 +date_released: 2022-05-08 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/package-lock.json b/package-lock.json index 3e770565c4d..f478799330b 100644 --- a/package-lock.json +++ b/package-lock.json @@ -16,7 +16,7 @@ "remark-stringify": "^10.0.2", "textlint": "^12.1.1", "textlint-rule-common-misspellings": "^1.0.1", - "textlint-rule-terminology": "^2.1.5" + "textlint-rule-terminology": "^3.0.0" } }, "node_modules/@azu/format-text": { @@ -5251,9 +5251,9 @@ } }, "node_modules/textlint-rule-terminology": { - "version": "2.1.5", - "resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-2.1.5.tgz", - "integrity": "sha512-VW+ea4ByLPddSUqoFkVVJF8zWnO8kqKwvC681wGFAjI4CYz9WhjEQH1ikhoEHXnd5AFXNArcjyoa8hoihrXy0w==", + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-3.0.0.tgz", + "integrity": "sha512-ySHbdLcA9Mdbbbc/Wkts3f8CVvY2Nsy3r21NH4bK785jhdpZozG771WDR7d7L5nNnFBeH7MmS0IcscfMpxMyvQ==", "dev": true, "dependencies": { "lodash": "^4.17.15", @@ -5261,7 +5261,7 @@ "textlint-rule-helper": "^2.1.1" }, "engines": { - "node": ">=8.9" + "node": ">=14" } }, "node_modules/textlint-rule-terminology/node_modules/@textlint/ast-node-types": { @@ -9831,9 +9831,9 @@ } }, "textlint-rule-terminology": { - "version": "2.1.5", - "resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-2.1.5.tgz", - "integrity": "sha512-VW+ea4ByLPddSUqoFkVVJF8zWnO8kqKwvC681wGFAjI4CYz9WhjEQH1ikhoEHXnd5AFXNArcjyoa8hoihrXy0w==", + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/textlint-rule-terminology/-/textlint-rule-terminology-3.0.0.tgz", + "integrity": "sha512-ySHbdLcA9Mdbbbc/Wkts3f8CVvY2Nsy3r21NH4bK785jhdpZozG771WDR7d7L5nNnFBeH7MmS0IcscfMpxMyvQ==", "dev": true, "requires": { "lodash": "^4.17.15", diff --git a/package.json b/package.json index ce0201c0e65..a46241b34e6 100644 --- a/package.json +++ b/package.json @@ -12,7 +12,7 @@ "remark-stringify": "^10.0.2", "textlint": "^12.1.1", "textlint-rule-common-misspellings": "^1.0.1", - "textlint-rule-terminology": "^2.1.5" + "textlint-rule-terminology": "^3.0.0" }, "resolutions": { "minimist": ">=1.2.5" diff --git a/plugins/my.rb b/plugins/my.rb index 55008e058b4..5588bc275e9 100644 --- a/plugins/my.rb +++ b/plugins/my.rb @@ -85,6 +85,7 @@ module Jekyll # Default title used for in-line text DEFAULT_TITLES = { + "automations" => "Automations & Scenes", "blueprint_import" => "Import Blueprint", "cloud" => "Home Assistant Cloud", "config_energy" => "Energy Configuration", @@ -92,7 +93,7 @@ module Jekyll "config_mqtt" => "MQTT Configuration", "config_zha" => "ZHA Configuration", "config_zwave_js" => "Z-Wave JS Configuration", - "config" => "Configuration", + "config" => "Settings", "developer_events" => "Events", "developer_services" => "Services", "developer_states" => "States", diff --git a/source/_dashboards/markdown.markdown b/source/_dashboards/markdown.markdown index 42fe092b7b2..7b178acce8a 100644 --- a/source/_dashboards/markdown.markdown +++ b/source/_dashboards/markdown.markdown @@ -103,7 +103,7 @@ content: | ## Icons -You can also use [materialdesignicons.com](https://materialdesignicons.com/) icons in the `content` of the card. +You can use [materialdesignicons.com](https://materialdesignicons.com/) icons in the `content` of the card. For example: @@ -116,3 +116,25 @@ content: | ``` {% endraw %} + + +## ha-alert + +You can also use our [\`ha-alert\`](https://design.home-assistant.io/#components/ha-alert) component in the Markdown card. + +Example: + +

+Screenshot of the ha-alert elements in a markdown card +Screenshot of the ha-alert elements in a markdown card. +

+ +```yaml +type: markdown +content: | + This is an error alert — check it out! + This is a warning alert — check it out! + This is an info alert — check it out! + This is a success alert — check it out! + This is an alert with a title +``` diff --git a/source/_docs/automation/troubleshooting.markdown b/source/_docs/automation/troubleshooting.markdown index 062aa8b6c60..c03c13aca1b 100644 --- a/source/_docs/automation/troubleshooting.markdown +++ b/source/_docs/automation/troubleshooting.markdown @@ -3,7 +3,7 @@ title: "Troubleshooting Automations" description: "Tips on how to troubleshoot your automations." --- -When an automation is run, all steps are recorded and a trace is made. From the UI choose **Configuration** which is located in the sidebar, then click on **Automation** to go to the automation editor or click this button directly: {% my automations badge %} +When an automation is run, all steps are recorded and a trace is made. From the UI choose **Settings** which is located in the sidebar, then click on **Automations & Scenes** to go to the automation editor or click this button directly: {% my automations badge %} Click on the clock icon next to an automation to enter the debugging screen. Alternatively, click on **Show trace** directly from a Logbook automation entry. diff --git a/source/_docs/blueprint/selectors.markdown b/source/_docs/blueprint/selectors.markdown index 016b769b6b9..41a4614269b 100644 --- a/source/_docs/blueprint/selectors.markdown +++ b/source/_docs/blueprint/selectors.markdown @@ -34,6 +34,7 @@ The following selectors are currently available: - [RGB color selector](#rgb-color-selector) - [Select selector](#select-selector) - [Target selector](#target-selector) +- [Template selector](#template-selector) - [Text selector](#text-selector) - [Theme selector](#theme-selector) - [Time selector](#time-selector) diff --git a/source/_docs/blueprint/tutorial.markdown b/source/_docs/blueprint/tutorial.markdown index 97bef2a2254..c9305a29e89 100644 --- a/source/_docs/blueprint/tutorial.markdown +++ b/source/_docs/blueprint/tutorial.markdown @@ -230,7 +230,7 @@ For this tutorial, we're going to share it on GitHub Gists. This is a good optio - Content is the content of the blueprint file. - Click the "Create Gist" button -You can now copy the URL of your new Gist and share it with other people. They can import it by going to **Configuration**, **Blueprints** and clicking on the blue "Import Blueprint" button. +You can now copy the URL of your new Gist and share it with other people. They can import it by going to **Settings** -> **Automations & Scenes** -> **Blueprints** and clicking on the blue "Import Blueprint" button. ### Share on the Blueprint Exchange diff --git a/source/_docs/configuration.markdown b/source/_docs/configuration.markdown index c13d24ea61a..f957db59958 100644 --- a/source/_docs/configuration.markdown +++ b/source/_docs/configuration.markdown @@ -3,7 +3,7 @@ title: "Configuration.yaml" description: "Configuring Home Assistant via text files." --- -While you can configure most of Home Assistant directly from the user interface under {% my config title="Configuration" %}, some parts need you to edit `configuration.yaml`. This file contains integrations to be loaded along with their configurations. Throughout the documentation you will find snippets that you can add to your configuration file to enable specific functionality. +While you can configure most of Home Assistant directly from the user interface under {% my config %}, some parts need you to edit `configuration.yaml`. This file contains integrations to be loaded along with their configurations. Throughout the documentation you will find snippets that you can add to your configuration file to enable specific functionality. If you run into trouble while configuring Home Assistant, refer to the [configuration troubleshooting page](/docs/configuration/troubleshooting/) and the [`configuration.yaml` examples](/examples/#example-configurationyaml). diff --git a/source/_docs/configuration/splitting_configuration.markdown b/source/_docs/configuration/splitting_configuration.markdown index 83c1cb41dab..8fb85cc92ee 100644 --- a/source/_docs/configuration/splitting_configuration.markdown +++ b/source/_docs/configuration/splitting_configuration.markdown @@ -205,7 +205,7 @@ This will allow you to `!include` files with `.yml` extensions from within the ` - `!include_dir_merge_list` will return the content of a directory as a list by merging all files (which should contain a list) into 1 big list. - `!include_dir_merge_named` will return the content of a directory as a dictionary by loading each file and merging it into 1 big dictionary. -These work recursively. As an example using `!include_dir_* automation`, will include all 6 files shown below: +These work recursively. As an example using `!include_dir_list automation`, will include all 6 files shown below: ```bash . diff --git a/source/_docs/configuration/templating.markdown b/source/_docs/configuration/templating.markdown index 7d72fd79f3f..c8c15ef65b6 100644 --- a/source/_docs/configuration/templating.markdown +++ b/source/_docs/configuration/templating.markdown @@ -72,7 +72,7 @@ Not supported in [limited templates](#limited-templates). - Iterating `states` will yield each state sorted alphabetically by entity ID. - Iterating `states.domain` will yield each state of that domain sorted alphabetically by entity ID. - `states.sensor.temperature` returns the state object for `sensor.temperature` (avoid when possible, see note below). -- `states('device_tracker.paulus')` will return the state string (not the object) of the given entity or `unknown` if it doesn't exist. +- `states('device_tracker.paulus')` will return the state string (not the object) of the given entity, `unknown` if it doesn't exist, `unavailable` if the object exists but is not yet available. - `is_state('device_tracker.paulus', 'home')` will test if the given entity is the specified state. - `state_attr('device_tracker.paulus', 'battery')` will return the value of the attribute or None if it doesn't exist. - `is_state_attr('device_tracker.paulus', 'battery', 40)` will test if the given entity attribute is the specified state (in this case, a numeric value). Note that the attribute can be `None` and you want to check if it is `None`, you need to use `state_attr('sensor.my_sensor', 'attr') == None`. @@ -119,6 +119,10 @@ Other state examples: Paulus is at {{ states('device_tracker.paulus') }}. {% endif %} +#check sensor.train_departure_time state +{% if states('sensor.train_departure_time') in ("unavailable", "unknown") %} + {{ ... }} + {% set state = states('sensor.temperature') %}{{ state | float + 1 if is_number(state) else "invalid temperature" }} {% set state = states('sensor.temperature') %}{{ (state | float * 10) | round(2) if is_number(state)}} diff --git a/source/_docs/locked_out.md b/source/_docs/locked_out.md index 42f78743768..adc333073c3 100644 --- a/source/_docs/locked_out.md +++ b/source/_docs/locked_out.md @@ -34,7 +34,7 @@ If you are running Home Assistant in a container, you can use the command line i #### To reset a user's password, as an administrator via the web interface 1. Confirm that you have "Advanced Mode" activated on your "Profile" page. -2. Click "Configuration" in the sidebar. +2. Click "Settings" in the sidebar. 3. Scroll down to "Users", and click in to that section. 4. Click on the user, this should bring up a dialog box. 5. At the bottom of the dialog box, click "Change Password". @@ -45,7 +45,7 @@ If you are running Home Assistant in a container, you can use the command line i #### To delete a user, as an administrator via the web interface -1. Click "Configuration" in the sidebar. +1. Click "Settings" in the sidebar. 2. Scroll down to "Users", and click in to that section. 3. Click on the user, this should bring up a dialog box. 4. At the bottom of the dialog box, click "Delete User". diff --git a/source/_docs/scene/editor.markdown b/source/_docs/scene/editor.markdown index 20e96d664e8..06d2f3eb431 100644 --- a/source/_docs/scene/editor.markdown +++ b/source/_docs/scene/editor.markdown @@ -5,7 +5,7 @@ description: "Instructions on how to use the scenes editor." In Home Assistant 0.102 we introduced the first version of our scene editor. If you just created a new configuration with Home Assistant, then you're all set! Go to the UI and enjoy. -From the UI choose **Configuration** which is located in the sidebar, then click on **Scenes** to go to the scene editor. Press the **Add Scene** button in the lower right corner to get started. +From the UI choose **Settings** which is located in the sidebar, then click on **Automations & Scenes** to go to the scene editor. Press the **Add Scene** button in the lower right corner to get started. Choose a meaningful name for your scene. diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown index 49f374a47a5..f810a2fb70e 100644 --- a/source/_docs/scripts/conditions.markdown +++ b/source/_docs/scripts/conditions.markdown @@ -388,7 +388,7 @@ The sunset/sunrise conditions do not work in locations inside the polar circles, In those cases it is advised to use conditions evaluating the solar elevation instead of the before/after sunset/sunrise conditions. -This is an example of 1 hour offset after sunset: +This is an example of 1 hour offset before sunset: ```yaml condition: condition: sun diff --git a/source/_docs/z-wave/controllers.markdown b/source/_docs/z-wave/controllers.markdown index d445791e7f4..7557429ce4f 100644 --- a/source/_docs/z-wave/controllers.markdown +++ b/source/_docs/z-wave/controllers.markdown @@ -8,9 +8,12 @@ description: "Extended instructions how to setup Z-Wave." You need to have a compatible Z-Wave stick or module installed. The following devices have been confirmed to work with Z-Wave JS: - 700 series controllers - - Aeotec Z-Stick 7 - - Zooz ZST10 700 - - Silicon Labs SLUSB7000A + - Aeotec Z-Stick 7 USB stick (ZWA010) + - Aeotec Z-Pi 7 Raspberry Pi HAT/Shield (ZWA025) + - Silicon Labs UZB-7 USB Stick (Silabs SLUSB7000A / SLUSB001A) + - Zooz S2 Stick 700 (ZST10 700) + - ZWave.me RaZberry 7 (ZME_RAZBERRY7) + - ZWave.me RaZberry 7 Pro (ZMEERAZBERRY7_ANT or ZMEURAZBERRY7_ANT) - 500 series controllers - Aeotec Z-Stick Gen5 (see note below) diff --git a/source/_examples/notify.mqtt.markdown b/source/_examples/notify.mqtt.markdown index 527f9e1622b..57cf2af9c2c 100644 --- a/source/_examples/notify.mqtt.markdown +++ b/source/_examples/notify.mqtt.markdown @@ -29,7 +29,7 @@ The same will work for automations. ### REST API -Using the [REST API](https://developers.home-assistant.io/docs/api/rest/ to send a message to a given topic. +Using the [REST API](https://developers.home-assistant.io/docs/api/rest/) to send a message to a given topic. ```bash $ curl -X POST \ diff --git a/source/_includes/asides/dashboards_navigation.html b/source/_includes/asides/dashboards_navigation.html index ef9bdfdcf4d..52cc8d44da3 100644 --- a/source/_includes/asides/dashboards_navigation.html +++ b/source/_includes/asides/dashboards_navigation.html @@ -49,7 +49,7 @@
  • {% active_link /dashboards/actions/ Actions %}
  • Developing Custom Cards diff --git a/source/_includes/common-tasks/update.md b/source/_includes/common-tasks/update.md index 4c1f5c307b8..934d853901f 100644 --- a/source/_includes/common-tasks/update.md +++ b/source/_includes/common-tasks/update.md @@ -20,7 +20,7 @@ To update Home Assistant Core when you run Home Assistant {{ page.installation_n content: | 1. Open your Home Assistant UI - 2. Navigate to the Configuration panel + 2. Navigate to the Settings panel 3. On the top you will be presented with an update notification _If you do not see that notification you can click the overflow menu in the top right and select "Check for updates"._ diff --git a/source/_includes/installation/container.md b/source/_includes/installation/container.md index b8264db83e7..d09649d36f0 100644 --- a/source/_includes/installation/container.md +++ b/source/_includes/installation/container.md @@ -34,7 +34,7 @@ Once the Home Assistant Container is running Home Assistant should be accessible If you change the configuration you have to restart the server. To do that you have 3 options. -1. In your Home Assistant UI go to the **Configuration** panel -> **Server management** and click the "Restart" button. +1. In your Home Assistant UI go to the **Settings** -> **System** and click the "Restart" button. 2. You can go to the **Developer Tools** -> **Services**, select the service `homeassistant.restart` and click "Call Service". 3. Restart it from a terminal. diff --git a/source/_integrations/aemet.markdown b/source/_integrations/aemet.markdown index 9a2c7c818d8..0f1a8e8fc76 100644 --- a/source/_integrations/aemet.markdown +++ b/source/_integrations/aemet.markdown @@ -26,7 +26,7 @@ The AEMET OpenData service is completely free but is limited to the Spanish terr ## Configuration -To add AEMET OpenData integration go to **Configuration** >> **Devices & Services** and find the integration in the list. +To add AEMET OpenData integration go to **Settings** -> **Devices & Services** and find the integration in the list. {% configuration_basic %} API Key: diff --git a/source/_integrations/airly.markdown b/source/_integrations/airly.markdown index 07d294287d7..b237471a8a0 100644 --- a/source/_integrations/airly.markdown +++ b/source/_integrations/airly.markdown @@ -11,6 +11,7 @@ ha_codeowners: ha_domain: airly ha_quality_scale: platinum ha_platforms: + - diagnostics - sensor ha_integration_type: integration --- diff --git a/source/_integrations/alpha_vantage.markdown b/source/_integrations/alpha_vantage.markdown index d86b9b291b9..940f0aadddf 100644 --- a/source/_integrations/alpha_vantage.markdown +++ b/source/_integrations/alpha_vantage.markdown @@ -5,8 +5,6 @@ ha_category: - Finance ha_iot_class: Cloud Polling ha_release: '0.60' -ha_codeowners: - - '@fabaff' ha_domain: alpha_vantage ha_platforms: - sensor diff --git a/source/_integrations/arest.markdown b/source/_integrations/arest.markdown index f472bbd4c7f..6a6acc2fbff 100644 --- a/source/_integrations/arest.markdown +++ b/source/_integrations/arest.markdown @@ -8,8 +8,6 @@ ha_category: - Switch ha_iot_class: Local Polling ha_release: 0.9 -ha_codeowners: - - '@fabaff' ha_domain: arest ha_platforms: - binary_sensor diff --git a/source/_integrations/backup.markdown b/source/_integrations/backup.markdown index e50a8067f0f..d88272c2b6f 100644 --- a/source/_integrations/backup.markdown +++ b/source/_integrations/backup.markdown @@ -28,7 +28,7 @@ backup: ``` You need to restart Home Assistant after you add this configuration. -When it has started up again you will find a new "Backup" entry in the main menu (**Configuration** -> **Backup**). +When it has started up again you will find a new "Backup" entry in the main menu (**Settings** -> **System** -> **Backup**). The backup files are stored in a new "backups" subdirectory in the root of your configuration directory. diff --git a/source/_integrations/bitcoin.markdown b/source/_integrations/bitcoin.markdown index fa08ddbacea..0726e020e31 100644 --- a/source/_integrations/bitcoin.markdown +++ b/source/_integrations/bitcoin.markdown @@ -5,8 +5,6 @@ ha_category: - Finance ha_release: pre 0.7 ha_iot_class: Cloud Polling -ha_codeowners: - - '@fabaff' ha_domain: bitcoin ha_platforms: - sensor diff --git a/source/_integrations/bmw_connected_drive.markdown b/source/_integrations/bmw_connected_drive.markdown index 0115df68bca..c5d9a32266b 100644 --- a/source/_integrations/bmw_connected_drive.markdown +++ b/source/_integrations/bmw_connected_drive.markdown @@ -47,7 +47,7 @@ This integration provides the following platforms: ## Configuration -Enable the `BMW Connected Drive` integration via **Configuration** > **Devices & Services**. +Enable the `BMW Connected Drive` integration via **Settings** -> **Devices & Services**.
    diff --git a/source/_integrations/calendar.markdown b/source/_integrations/calendar.markdown index a02f29f2701..07313232c45 100644 --- a/source/_integrations/calendar.markdown +++ b/source/_integrations/calendar.markdown @@ -56,4 +56,4 @@ automation: {{ trigger.calendar_event.start }} mode: single ``` -{% endraw %} \ No newline at end of file +{% endraw %} diff --git a/source/_integrations/camera.markdown b/source/_integrations/camera.markdown index 6015564b965..bc701a974f6 100644 --- a/source/_integrations/camera.markdown +++ b/source/_integrations/camera.markdown @@ -10,6 +10,8 @@ ha_domain: camera ha_codeowners: - '@home-assistant/core' ha_integration_type: integration +ha_platforms: + - diagnostics --- The camera integration allows you to use IP cameras with Home Assistant. diff --git a/source/_integrations/cloud.markdown b/source/_integrations/cloud.markdown index 50049ebaa0f..0bbb6dfec19 100644 --- a/source/_integrations/cloud.markdown +++ b/source/_integrations/cloud.markdown @@ -29,7 +29,7 @@ cloud: Documentation of further configuration possibilities are located at [NabuCasa](https://www.nabucasa.com/config/) -Once activated, go to the configuration panel in Home Assistant and create an account and log in. If you are not seeing the **Configuration** panel, make sure you have the following option enabled in your `configuration.yaml` file. +Once activated, go to the configuration panel in Home Assistant and create an account and log in. If you are not seeing the **Settings** panel, make sure you have the following option enabled in your `configuration.yaml` file. ```yaml config: diff --git a/source/_integrations/control4.markdown b/source/_integrations/control4.markdown index a3911698c2d..3be1a943158 100644 --- a/source/_integrations/control4.markdown +++ b/source/_integrations/control4.markdown @@ -25,7 +25,7 @@ Before setting up, you should assign a static IP address/DHCP reservation on you ## Options -The Control4 integration offers additional options in **Configuration** -> **Devices & Services** -> **Control4** -> **Options**: +The Control4 integration offers additional options in **Settings** -> **Devices & Services** -> **Control4** -> **Options**: {% configuration %} Seconds between updates: diff --git a/source/_integrations/dexcom.markdown b/source/_integrations/dexcom.markdown index 6ba69fbc91f..a7c638db8be 100644 --- a/source/_integrations/dexcom.markdown +++ b/source/_integrations/dexcom.markdown @@ -32,7 +32,7 @@ There are two Dexcom Share servers, `US` for United States customers, and `OUS` ### Unit of measurement -The integrations allows both `mg/dL` and `mmol/l` units of measurement for blood glucose values. To change your preferred unit of measurement, go to **Configuration** >> **Devices & Services** in the UI, and click `OPTIONS`. +The integrations allows both `mg/dL` and `mmol/l` units of measurement for blood glucose values. To change your preferred unit of measurement, go to **Settings** -> **Devices & Services** in the UI, and click `OPTIONS`. ## Sensor diff --git a/source/_integrations/dlna_dmr.markdown b/source/_integrations/dlna_dmr.markdown index 910dce6ec28..46359f3953f 100644 --- a/source/_integrations/dlna_dmr.markdown +++ b/source/_integrations/dlna_dmr.markdown @@ -24,7 +24,7 @@ Please note that some devices, such as Samsung TVs, are rather picky about the s ## Options -Options for DLNA DMR devices can be set going to **Configuration** -> **Devices & Services** -> **DLNA Digital Media Renderer** -> **Configuration**. +Options for DLNA DMR devices can be set going to **Settings** -> **Devices & Services** -> **DLNA Digital Media Renderer** -> **Configuration**. {% configuration_basic %} Event listener port: diff --git a/source/_integrations/dnsip.markdown b/source/_integrations/dnsip.markdown index 5c07c548463..c17f06b4dff 100644 --- a/source/_integrations/dnsip.markdown +++ b/source/_integrations/dnsip.markdown @@ -14,7 +14,7 @@ ha_codeowners: ha_integration_type: integration --- -The DNS IP integration will expose an IP address, fetched via DNS resolution, as its value. It provides both IPv4 and IPv6 lookup as separate sensors depending on accessibility to resolvers. +The DNS IP integration will expose an IP address, fetched via DNS resolution (every 2 minutes), as its value. It provides both IPv4 and IPv6 lookup as separate sensors depending on accessibility to resolvers. 1. When you enable the integration with the default value, it will query the [OpenDNS](https://www.opendns.com/) nameservers with the hostname `myip.opendns.com`, which will resolve to your external/public IP address. 2. If you specify a `hostname`, a regular DNS lookup will be performed, providing you the IP the hostname resolves to. diff --git a/source/_integrations/dsmr.markdown b/source/_integrations/dsmr.markdown index 89139177c6d..f02a957a377 100644 --- a/source/_integrations/dsmr.markdown +++ b/source/_integrations/dsmr.markdown @@ -39,7 +39,7 @@ A sensor platform for Belgian, Dutch, Luxembourg and Swedish Smart Meters which ### Options -To configure options for DSMR integration go to **Configuration** >> **Devices & Services** and press **Options** on the DSMR card. +To configure options for DSMR integration go to **Settings** -> **Devices & Services** and press **Options** on the DSMR card. #### Time between updates diff --git a/source/_integrations/dweet.markdown b/source/_integrations/dweet.markdown index 05c8241279c..ae46a45aeab 100644 --- a/source/_integrations/dweet.markdown +++ b/source/_integrations/dweet.markdown @@ -6,8 +6,6 @@ ha_category: - Sensor ha_release: 0.19 ha_iot_class: Cloud Polling -ha_codeowners: - - '@fabaff' ha_domain: dweet ha_platforms: - sensor diff --git a/source/_integrations/eafm.md b/source/_integrations/eafm.md index 552f283f5ef..af581ecaa35 100644 --- a/source/_integrations/eafm.md +++ b/source/_integrations/eafm.md @@ -21,7 +21,7 @@ The UK Environment Agency Flood Monitoring only provides data for England - Nort ## Configuration -Home Assistant offers the flood monitoring integration through **Configuration** -> **Devices & Services** -> **Environment Agency Flood Gauges**. +Home Assistant offers the flood monitoring integration through **Settings** -> **Devices & Services** -> **Environment Agency Flood Gauges**. You will be prompted to select a monitoring station. You can find the name of nearby monitoring stations on the Flood information service [website](https://flood-warning-information.service.gov.uk/river-and-sea-levels). diff --git a/source/_integrations/ecobee.markdown b/source/_integrations/ecobee.markdown index 65e44616067..2892f0dd9d6 100644 --- a/source/_integrations/ecobee.markdown +++ b/source/_integrations/ecobee.markdown @@ -53,7 +53,7 @@ Your new application will now appear on the left. Upon clicking on the applicati ## Configuration -1. In the **Configuration** > **Devices & Services** menu, click **+** and then select "ecobee" from the pop-up menu. +1. In the **Settings** -> **Devices & Services** menu, click **+** and then select "ecobee" from the pop-up menu. 2. In the pop-up box, enter the API key you obtained from ecobee's [developer portal](https://ecobee.com/developers). 3. In the next pop-up box, you will be presented with a unique four-character PIN code which you will need to authorize in the [ecobee consumer portal](https://www.ecobee.com/consumerportal/index.html). You can do this by logging in, selecting **My Apps** from the hamburger menu, clicking **Add Application** on the left, entering the PIN code from Home Assistant, clicking **Validate** and then **Add Application** in the bottom right. 4. After authorizing the app with ecobee, return to Home Assistant and click **Submit**. If the authorization was successful, a configuration entry will be created and your thermostats and sensors will be available in Home Assistant. @@ -80,7 +80,7 @@ api_key:

    -You must [restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. After restarting, navigate to the **Configuration** > **Devices & Services** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the app according to the above **Automatic Configuration**, starting at step 2. +You must [restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. After restarting, navigate to the **Settings** -> **Devices & Services** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the app according to the above **Automatic Configuration**, starting at step 2. ## Notifications diff --git a/source/_integrations/fido.markdown b/source/_integrations/fido.markdown index 8f78295d18f..e3f47fb8499 100644 --- a/source/_integrations/fido.markdown +++ b/source/_integrations/fido.markdown @@ -79,7 +79,7 @@ monitored_variables: description: Talk time used talk_limit: description: Talk time limit - talt_remaining: + talk_remaining: description: Talk time remaining other_talk_used: description: Other talk time used (It could be international calls) diff --git a/source/_integrations/flock.markdown b/source/_integrations/flock.markdown index e72b8d850b6..cb3ce746853 100644 --- a/source/_integrations/flock.markdown +++ b/source/_integrations/flock.markdown @@ -5,8 +5,6 @@ ha_category: - Notifications ha_iot_class: Cloud Push ha_release: 0.71 -ha_codeowners: - - '@fabaff' ha_domain: flock ha_platforms: - notify diff --git a/source/_integrations/flume.markdown b/source/_integrations/flume.markdown index 7015d533c3a..e4bc3e347c8 100644 --- a/source/_integrations/flume.markdown +++ b/source/_integrations/flume.markdown @@ -26,7 +26,7 @@ You can find your Client ID and Client Secret under "API Access" on the [setting The Flume API access is available to Flume Insight users only, which may require a paid subscription. -To add `Flume` to your installation, go to **Configuration** >> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Flume**. +To add `Flume` to your installation, go to **Settings** -> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Flume**. ## Configuration for Binary Sensor diff --git a/source/_integrations/freebox.markdown b/source/_integrations/freebox.markdown index a7b4419d720..726b948f89e 100644 --- a/source/_integrations/freebox.markdown +++ b/source/_integrations/freebox.markdown @@ -38,7 +38,7 @@ Please consult the [API documentation](https://dev.freebox.fr/sdk/os/) for more ### Via the frontend -Menu: **Configuration** -> **Devices & Services**. Search for "Freebox", add your host and port, click submit. +Menu: **Settings** -> **Devices & Services**. Search for "Freebox", add your host and port, click submit. If you add the integration for the first time, follow the instructions in the [Initial setup](#initial-setup) section. diff --git a/source/_integrations/fritz.markdown b/source/_integrations/fritz.markdown index 4681184992a..a745f451373 100644 --- a/source/_integrations/fritz.markdown +++ b/source/_integrations/fritz.markdown @@ -5,6 +5,7 @@ ha_category: - Binary Sensor - Presence Detection - Sensor + - Updates ha_release: '0.10' ha_domain: fritz ha_config_flow: true diff --git a/source/_integrations/fritzbox_callmonitor.markdown b/source/_integrations/fritzbox_callmonitor.markdown index de9f139f2fa..414a570bda2 100644 --- a/source/_integrations/fritzbox_callmonitor.markdown +++ b/source/_integrations/fritzbox_callmonitor.markdown @@ -10,6 +10,8 @@ ha_config_flow: true ha_platforms: - sensor ha_integration_type: integration +ha_codeowners: + - '@cdce8p' --- The `fritzbox_callmonitor` sensor monitors the call monitor exposed by [AVM FRITZ!Box](https://avm.de/produkte/fritzbox/) routers on TCP port 1012. It will assume the values `idle`, `ringing`, `dialing` or `talking` with the phone numbers involved contained in the state attributes. diff --git a/source/_integrations/gios.markdown b/source/_integrations/gios.markdown index d0d071b6c23..212da2a4fce 100644 --- a/source/_integrations/gios.markdown +++ b/source/_integrations/gios.markdown @@ -11,6 +11,7 @@ ha_codeowners: ha_domain: gios ha_quality_scale: platinum ha_platforms: + - diagnostics - sensor ha_integration_type: integration --- diff --git a/source/_integrations/gitter.markdown b/source/_integrations/gitter.markdown index b2c1679358c..9675f778c9b 100644 --- a/source/_integrations/gitter.markdown +++ b/source/_integrations/gitter.markdown @@ -5,8 +5,6 @@ ha_category: - Sensor ha_iot_class: Cloud Polling ha_release: 0.47 -ha_codeowners: - - '@fabaff' ha_domain: gitter ha_platforms: - sensor diff --git a/source/_integrations/glances.markdown b/source/_integrations/glances.markdown index 009b1fcf347..53f37a6e4e2 100644 --- a/source/_integrations/glances.markdown +++ b/source/_integrations/glances.markdown @@ -7,7 +7,6 @@ ha_iot_class: Local Polling ha_release: 0.7.3 ha_config_flow: true ha_codeowners: - - '@fabaff' - '@engrbm87' ha_domain: glances ha_platforms: diff --git a/source/_integrations/group.markdown b/source/_integrations/group.markdown index 0c06a82c27e..b5bfe129e59 100644 --- a/source/_integrations/group.markdown +++ b/source/_integrations/group.markdown @@ -56,6 +56,18 @@ Some groups, like the binary sensors and lights, allow you set the "All entities - Otherwise, the group state is `unknown` if at least one group member is `unknown` or `unavailable`. - Otherwise, the group state is `on`. +## Managing groups + +To edit a group, **{% my helpers title="Settings -> Devices & Services -> Helpers" %}**. Find and select the group from the list. + +![Group members](/images/integrations/group/Group_settings.png) + +### Group options + +To add or remove entities from an existing group, click on `Group options`, all the existing entities are listed in the `members` section where you add and remove entities. + +![Group members](/images/integrations/group/Group_members.png) + ## YAML Configuration Alternatlively, this integration can be configured and set up manually via YAML diff --git a/source/_integrations/harmony.markdown b/source/_integrations/harmony.markdown index ad4a91bb75a..63dcb918c82 100644 --- a/source/_integrations/harmony.markdown +++ b/source/_integrations/harmony.markdown @@ -35,7 +35,7 @@ Supported units: **Note:** Depending on the firmware, you may need to enable XMPP for this integration to work. From your Harmony app, go to: **Menu** > **Harmony Setup** > **Add/Edit Devices & Activities** > **Remote & Hub** > **Enable XMPP**. -Once the Logitech Harmony Hub has been configured, the default activity and duration in seconds between sending commands to a device can be adjusted in the settings via **Configuration** >> **Devices & Services** >> **Your Logitech Harmony Hub** +Once the Logitech Harmony Hub has been configured, the default activity and duration in seconds between sending commands to a device can be adjusted in the settings via **Settings** -> **Devices & Services** >> **Your Logitech Harmony Hub** ### Configuration file diff --git a/source/_integrations/homekit.markdown b/source/_integrations/homekit.markdown index 8ca27ee9851..bc44cc01835 100644 --- a/source/_integrations/homekit.markdown +++ b/source/_integrations/homekit.markdown @@ -313,7 +313,7 @@ The HomeKit Accessory Protocol Specification only allows a maximum of 150 unique ### Multiple HomeKit instances -If you create a HomeKit integration via the UI (i.e., **Configuration** >> **Devices & Services**), it must be configured via the UI **only**. While the UI only offers limited configuration options at the moment, any attempt to configure a HomeKit instance created in the UI via the `configuration.yaml` file will result in another instance of HomeKit running on a different port. +If you create a HomeKit integration via the UI (i.e., **Settings** -> **Devices & Services**), it must be configured via the UI **only**. While the UI only offers limited configuration options at the moment, any attempt to configure a HomeKit instance created in the UI via the `configuration.yaml` file will result in another instance of HomeKit running on a different port. It is recommended to only edit a HomeKit instance in the UI that was created in the UI, and likewise, only edit a HomeKit instance in YAML that was created in YAML. @@ -636,7 +636,7 @@ Ensure that the [`ffmpeg`](/integrations/ffmpeg) integration is configured corre #### Camera streaming is unstable or slow -If your camera supports native H.264 streams, Home Assistant can avoid converting the video stream, which is an expensive operation. To enable native H.264 streaming when configured via YAML, change the `video_codec` to `copy`. To allow native H.264 streaming when setting up HomeKit via the UI, go to **Configuration** >> **Devices & Services** in the UI, click **Options** for your HomeKit Bridge, and check the box for your camera on the `Cameras that support native H.264 streams` screen. +If your camera supports native H.264 streams, Home Assistant can avoid converting the video stream, which is an expensive operation. To enable native H.264 streaming when configured via YAML, change the `video_codec` to `copy`. To allow native H.264 streaming when setting up HomeKit via the UI, go to **Settings** -> **Devices & Services** in the UI, click **Options** for your HomeKit Bridge, and check the box for your camera on the `Cameras that support native H.264 streams` screen. #### Multiple camera streams diff --git a/source/_integrations/ifttt.markdown b/source/_integrations/ifttt.markdown index dd93693c497..f09114a7786 100644 --- a/source/_integrations/ifttt.markdown +++ b/source/_integrations/ifttt.markdown @@ -62,11 +62,7 @@ ifttt: ``` `key` is your API key which can be obtained by viewing the **Settings** of the [Webhooks applet](https://ifttt.com/services/maker_webhooks/settings). It's the last part of the URL (e.g., https://maker.ifttt.com/use/MYAPIKEY) you will find under **My Applets** > **Webhooks** > **Settings**. - -

    - -Property screen of the Maker Channel -

    +![Property screen of the Maker Channel.](/images/integrations/ifttt/finding_key.png) Once you have added your key to your `configuration.yaml` file, restart your Home Assistant instance. This will load up the IFTTT integration and make a service available to trigger events in IFTTT. @@ -88,18 +84,29 @@ ifttt: ### Testing your trigger -You can use **Developer Tools** to test your [Webhooks](https://ifttt.com/maker_webhooks) trigger. To do this, open the Home Assistant sidebar, click on Developer Tools, and then the **Services** tab. Fill in the following values: +You can use **Developer Tools** to test your [Webhooks](https://ifttt.com/maker_webhooks) trigger. To do this, open the Home Assistant sidebar, click on **Developer Tools** -> **Services** tab. Select `IFTTT: Trigger` as the service and fill in the following values: -Field | Value ------ | ----- -domain | `ifttt` -service | `trigger` -Service Data | `{"event": "EventName", "value1": "Hello World"}` +{% configuration_basic %} +event: + description: The name of the event to send. + required: true + type: string +value1: + description: Generic field to send data via the event. + required: false + type: string +value2: + description: Generic field to send data via the event. + required: false + type: string +value3: + description: Generic field to send data via the event. + required: false + type: string +{% endconfiguration_basic %} -

    - When your screen looks like this, click the 'call service' button. -

    +![Testing service.](/images/integrations/ifttt/testing_service.png) By default, the trigger is sent to all the API keys from `configuration.yaml`. If you want to send the trigger to a specific key use the `target` field: @@ -112,19 +119,22 @@ Service Data | `{"event": "EventName", "value1": "Hello World", "target": "YOUR_ The `target` field can contain a single key name or a list of key names. -### Setting up a recipe +### Setting up an applet -Press the *New applet* button and search for *Webhooks*. +Press the *Create* button and *Add* on **If This**. Search for *Webhooks*. +![Create applet.](/images/integrations/ifttt/create_applet.png) -

    - -Choose "Webhooks" as service. -

    +Choose *Webhooks* service. +![Choose "Webhooks" service.](/images/integrations/ifttt/setup_service.png) + +Select *Receive a web request*. +![Receive a web request.](/images/integrations/ifttt/choose_webhook_trigger.png) -

    - You need to setup a unique trigger for each event you sent to IFTTT. -

    +![You need to setup a unique trigger for each event you sent to IFTTT.](/images/integrations/ifttt/setup_trigger.png) + +Add the *Then That* action. The below example sends a notification to the IFTTT mobile app and adds `value1` to the message: +![Example notification "then that" action.](/images/integrations/ifttt/setup_then_that.png) {% raw %} diff --git a/source/_integrations/influxdb.markdown b/source/_integrations/influxdb.markdown index 76c658993f0..3de3fb49b69 100644 --- a/source/_integrations/influxdb.markdown +++ b/source/_integrations/influxdb.markdown @@ -7,7 +7,6 @@ ha_category: ha_release: 0.9 ha_iot_class: Local Push ha_codeowners: - - '@fabaff' - '@mdegat01' ha_domain: influxdb ha_platforms: diff --git a/source/_integrations/input_datetime.markdown b/source/_integrations/input_datetime.markdown index 10908815993..4241c099b67 100644 --- a/source/_integrations/input_datetime.markdown +++ b/source/_integrations/input_datetime.markdown @@ -16,7 +16,7 @@ The `input_datetime` integration allows the user to define date and time values that can be controlled via the frontend and can be used within automations and templates. -The preferred way to configure input datetime is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the **Date and/or time** option. +The preferred way to configure input datetime is via the user interface at **Settings** -> **Devices & Services** -> **Helpers**. Click the add button and then choose the **Date and/or time** option. To be able to add **Helpers** via the user interface you should have `default_config:` in your `configuration.yaml`, it should already be there by default unless you removed it. If you removed `default_config:` from your configuration, you must add `input_datetime:` to your `configuration.yaml` first, then you can use the UI. diff --git a/source/_integrations/input_number.markdown b/source/_integrations/input_number.markdown index 9aacd388246..89e532a27d9 100644 --- a/source/_integrations/input_number.markdown +++ b/source/_integrations/input_number.markdown @@ -14,7 +14,7 @@ ha_integration_type: helper The `input_number` integration allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. The frontend can display a slider, or a numeric input box. Changes to the slider or numeric input box generate state events. These state events can be utilized as `automation` triggers as well. -The preferred way to configure an input number is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the **Number** option. +The preferred way to configure an input number is via the user interface at **Settings** -> **Devices & Services** -> **Helpers**. Click the add button and then choose the **Number** option. To be able to add **Helpers** via the user interface you should have `default_config:` in your `configuration.yaml`, it should already be there by default unless you removed it. If you removed `default_config:` from you configuration, you must add `input_number:` to your `configuration.yaml` first, then you can use the UI. diff --git a/source/_integrations/input_select.markdown b/source/_integrations/input_select.markdown index e3fe4aa8810..838e64596be 100644 --- a/source/_integrations/input_select.markdown +++ b/source/_integrations/input_select.markdown @@ -14,7 +14,7 @@ ha_integration_type: helper The `input_select` integration allows the user to define a list of values that can be selected via the frontend and can be used within conditions of an automation. When a user selects a new item, a state transition event is generated. This state event can be used in an `automation` trigger. -The preferred way to configure an input select is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the **Dropdown** option. +The preferred way to configure an input select is via the user interface at **Settings** -> **Devices & Services** -> **Helpers**. Click the add button and then choose the **Dropdown** option. To be able to add **Helpers** via the user interface you should have `default_config:` in your `configuration.yaml`, it should already be there by default unless you removed it. If you removed `default_config:` from you configuration, you must add `input_select:` to your `configuration.yaml` first, then you can use the UI. diff --git a/source/_integrations/input_text.markdown b/source/_integrations/input_text.markdown index d60ad5984a8..a78dd86a278 100644 --- a/source/_integrations/input_text.markdown +++ b/source/_integrations/input_text.markdown @@ -14,7 +14,7 @@ ha_integration_type: helper The `input_text` integration allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. Changes to the value stored in the text box generate state events. These state events can be utilized as `automation` triggers as well. It can also be configured in password mode (obscured text). -The preferred way to configure an input text is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the **Text** option. +The preferred way to configure an input text is via the user interface at **Settings** -> **Devices & Services** -> **Helpers**. Click the add button and then choose the **Text** option. To be able to add **Helpers** via the user interface you should have `default_config:` in your `configuration.yaml`, it should already be there by default unless you removed it. If you removed `default_config:` from you configuration, you must add `input_text:` to your `configuration.yaml` first, then you can use the UI. diff --git a/source/_integrations/insteon.markdown b/source/_integrations/insteon.markdown index f2e73cfb2c1..8be1102e7f8 100644 --- a/source/_integrations/insteon.markdown +++ b/source/_integrations/insteon.markdown @@ -23,6 +23,7 @@ ha_platforms: - light - switch ha_integration_type: integration +ha_dhcp: true ---

    The Insteon company has shut down and turned off their cloud as of April 2022.

    diff --git a/source/_integrations/intellifire.markdown b/source/_integrations/intellifire.markdown index 3ccfb8ce402..e1a5979ecc1 100644 --- a/source/_integrations/intellifire.markdown +++ b/source/_integrations/intellifire.markdown @@ -88,4 +88,3 @@ In some cases, this will restore control to the fireplace, but if it doesn't you #### Power Cycle The sure fire way to reset the IFT module is to just power-cycle it. This will work just about every time. - diff --git a/source/_integrations/keenetic_ndms2.markdown b/source/_integrations/keenetic_ndms2.markdown index 3c14b1be03d..643fcad6ada 100644 --- a/source/_integrations/keenetic_ndms2.markdown +++ b/source/_integrations/keenetic_ndms2.markdown @@ -21,4 +21,4 @@ Router running NDMS firmware versions 2.05 and up. It uses telnet connection so ## Configuration -To add Keenetic router to your installation, go to **Configuration** >> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Keenetic NDMS2 Router**. +To add Keenetic router to your installation, go to **Settings** -> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Keenetic NDMS2 Router**. diff --git a/source/_integrations/knx.markdown b/source/_integrations/knx.markdown index 245199b6142..69199908f58 100644 --- a/source/_integrations/knx.markdown +++ b/source/_integrations/knx.markdown @@ -23,7 +23,7 @@ ha_codeowners: - '@farmio' - '@marvin-w' ha_domain: knx -ha_quality_scale: silver +ha_quality_scale: platinum ha_platforms: - binary_sensor - button diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown index b4589d49c98..60dfc682ee6 100644 --- a/source/_integrations/konnected.markdown +++ b/source/_integrations/konnected.markdown @@ -48,7 +48,7 @@ Konnected devices communicate with Home Assistant over your local LAN -- there i ### Web Interface -Starting with 0.106.0 Home Assistant requires UI based configuration of Konnected via **Configuration** -> **Devices & Services** in the Home Assistant (web) frontend. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list. +Starting with 0.106.0 Home Assistant requires UI based configuration of Konnected via **Settings** -> **Devices & Services** in the Home Assistant (web) frontend. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list. Selecting one of these discovered panels will guide you through connecting and configuring the panel. If your panel was discovered via SSDP, you shouldn't need any information to complete configuration - simply confirm that the information displayed is correct. If the UI prompts you for IP/Port, you'll need to enter it. IP/Port info can be found using the Konnected mobile app. @@ -56,15 +56,15 @@ Selecting one of these discovered panels will guide you through connecting and c If you have an existing `configuration.yaml` completing the UI configuration will do a one time import of the settings contained in `configuration.yaml`. Once the import creates a **Configured** integration the Konnected section of the `configuration.yaml` is no longer used - it is recommended to remove the `konnected` section of `configuration.yaml` and after the import occurs. Any future changes to settings should occur via the settings provided in the Home Assistant web interface. -If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Devices & Services** -> **Configured** and repeat the UI configuration for that device. +If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Settings** -> **Devices & Services** -> **Configured** and repeat the UI configuration for that device.
    -Once configuration is completed you'll see a Konnected.io entry in **Configuration** -> **Devices & Services** => **Configured**. If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings, you'll need to utilize the settings UI to configure zone behavior. +Once configuration is completed you'll see a Konnected.io entry in **Settings** -> **Devices & Services** -> **Configured**. If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings, you'll need to utilize the settings UI to configure zone behavior. #### Using Settings UI to Configure Zone Behavior -The settings for each panel can be accessed by selecting the entry in **Configuration** -> **Devices & Services** => **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure these settings at any time and once completed the settings will be immediately applied. +The settings for each panel can be accessed by selecting the entry in **Settings** -> **Devices & Services** -> **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure these settings at any time and once completed the settings will be immediately applied. The settings UI starts by having you configure the general behavior of each zone. You need to specify `Disabled`, `Binary Sensor`, `Digital Sensor`, or `Switchable Output` for each zone. After that, you'll be prompted, for each zone that is not disabled, to configure details of the zones' behavior. All zones will allow entry of a Name. Additional fields depend on how you configured the general behavior of the zone. **Note some zones do not support all behaviors. The UI will reflect specific options available to each zone.** @@ -310,7 +310,7 @@ konnected: ## Unique IDs and the Entity Registry -Beginning in Home Assistant release 0.90, unique IDs are generated for each sensor or switch entity. This enables end users to modify the entity names and entity IDs through the Home Assistant UI at **Configuration** -> **Entities**. +Beginning in Home Assistant release 0.90, unique IDs are generated for each sensor or switch entity. This enables end users to modify the entity names and entity IDs through the Home Assistant UI at **Settings** -> **Devices & Services** -> **Entities**. Unique IDs are internally generated as follows: diff --git a/source/_integrations/lifx.markdown b/source/_integrations/lifx.markdown index c97d022da0b..be8803f50d7 100644 --- a/source/_integrations/lifx.markdown +++ b/source/_integrations/lifx.markdown @@ -11,6 +11,8 @@ ha_homekit: true ha_platforms: - light ha_integration_type: integration +ha_codeowners: + - '@Djelibeybi' --- The `lifx` integration allows you to integrate your [LIFX](https://www.lifx.com) bulbs into Home Assistant. diff --git a/source/_integrations/meater.markdown b/source/_integrations/meater.markdown index 561efe67c25..4c94f85c073 100644 --- a/source/_integrations/meater.markdown +++ b/source/_integrations/meater.markdown @@ -1,5 +1,5 @@ --- -title: Meater Smart Meat Thermometer +title: Meater description: Instructions on how to integrate the Meater Temperature Probe within Home Assistant. ha_category: - Sensor @@ -8,7 +8,11 @@ ha_iot_class: Cloud Polling ha_config_flow: true ha_codeowners: - '@Sotolotl' + - '@emontnemery' ha_domain: meater +ha_platforms: + - sensor +ha_integration_type: integration --- The Meater Smart Meat Thermometer integration allows for communicating with the [Meater Temperature Probe](https://meater.com/) from Apption Labs. @@ -25,4 +29,4 @@ Devices will only be returned from the Meater Cloud API after the following crit - Device must be seen by the Meater Cloud. Ensure you've completed a cook while connected to Meater Cloud. - The Meater app or Block must have an active Bluetooth connection with the device. -- The Meater app or Block must have an active Meater Cloud connection. \ No newline at end of file +- The Meater app or Block must have an active Meater Cloud connection. diff --git a/source/_integrations/meteo_france.markdown b/source/_integrations/meteo_france.markdown index 9beffc76a5e..8d20f88deb8 100644 --- a/source/_integrations/meteo_france.markdown +++ b/source/_integrations/meteo_france.markdown @@ -34,7 +34,7 @@ It displays the current weather along with a 5 days forecast and create sensors, To be used with the weather dashboard card to access current condition, today and next four days forecast. -The weather platform can be configured in the frontend to decide if the forecast is given daily (default) or hourly. To change the setting go in **Configuration** -> **Devices & Services**, click on the city name in **Météo-France** box and click on **Options**. You can update the `Forecast mode` by choosing between `daily` or `hourly`. +The weather platform can be configured in the frontend to decide if the forecast is given daily (default) or hourly. To change the setting go in **Settings** -> **Devices & Services**, click on the city name in **Météo-France** box and click on **Options**. You can update the `Forecast mode` by choosing between `daily` or `hourly`. ## Sensor platforms @@ -59,7 +59,7 @@ All the following sensors will be created : Warning: The probability entities data are not always provided by the API. They are added only if available. -To enable an entity disabled by default, go in **Configuration** -> **Devices & Services**, click on the city name in **Météo-France** and then the **X entities** link. You will have the list of the enabled entities. Here click the filter button and select **Show disable entities**. The disabled entities will be visible in the list, select the one you want to enable and click the **Enable Selected** button. +To enable an entity disabled by default, go in **Settings** -> **Devices & Services**, click on the city name in **Météo-France** and then the **X entities** link. You will have the list of the enabled entities. Here click the filter button and select **Show disable entities**. The disabled entities will be visible in the list, select the one you want to enable and click the **Enable Selected** button. ### About `next_rain` condition sensor diff --git a/source/_integrations/motion_blinds.markdown b/source/_integrations/motion_blinds.markdown index db456dcfed4..4ab0ab089e5 100644 --- a/source/_integrations/motion_blinds.markdown +++ b/source/_integrations/motion_blinds.markdown @@ -25,6 +25,7 @@ Additionally the following brands have been reported to also work with this inte - [Bloc Blinds](https://www.blocblinds.com/) - [Brel Home](https://www.brel-home.nl/) - [3 Day Blinds](https://www.3dayblinds.com/) +- [Diaz](https://www.diaz.be/en/) - [Dooya](http://www.dooya.com/) - [Gaviota](https://www.gaviotagroup.com/en/) - [Havana Shade](https://havanashade.com/) diff --git a/source/_integrations/mpd.markdown b/source/_integrations/mpd.markdown index 62d747328aa..d69fbfc48eb 100644 --- a/source/_integrations/mpd.markdown +++ b/source/_integrations/mpd.markdown @@ -5,8 +5,6 @@ ha_category: - Media Player ha_release: pre 0.7 ha_iot_class: Local Polling -ha_codeowners: - - '@fabaff' ha_domain: mpd ha_platforms: - media_player diff --git a/source/_integrations/mystrom.markdown b/source/_integrations/mystrom.markdown index 1bed3d00751..78a63696eab 100644 --- a/source/_integrations/mystrom.markdown +++ b/source/_integrations/mystrom.markdown @@ -26,7 +26,6 @@ There is currently support for the following device types within Home Assistant: - [Setup of myStrom Buttons](#setup-of-mystrom-buttons) - [Switch](#switch) - [Setup](#setup) - - [Get the current power consumption](#get-the-current-power-consumption) ## Light @@ -158,7 +157,7 @@ If you have set [`login_attempts_threshold`](/integrations/http/) and forget to ## Switch -The `mystrom` switch platform allows you to control the state of your [myStrom](https://mystrom.ch/en/) switches. The built-in sensor is measuring the power consumption while the switch is on. +The `mystrom` switch platform allows you to control the state of your [myStrom](https://mystrom.ch/en/) switches. ### Setup @@ -188,23 +187,3 @@ name: type: string default: myStrom Switch {% endconfiguration %} - - -### Get the current power consumption - -The switch is measuring the current power consumption. To expose this as a sensor use a [`template` sensor](/integrations/template). - -{% raw %} - -```yaml -# Example configuration.yaml entry -sensor: - - platform: template - sensors: - power: - friendly_name: "Current Power" - unit_of_measurement: "W" - value_template: "{{ state_attr('switch.office', 'current_power_w') }}" -``` - -{% endraw %} diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown index d96fad2ae3e..5335c2a6e60 100644 --- a/source/_integrations/nest.markdown +++ b/source/_integrations/nest.markdown @@ -465,7 +465,7 @@ This feature is enabled by the following permissions: - For general trouble with the SDM API OAuth authorization flow with Google, see [Troubleshooting](https://developers.google.com/nest/device-access/authorize#troubleshooting). -- Check **Configuration** then **Logs** to see if there are any error messages or misconfigurations then see the error messages below. +- Check **Settings** -> **System** -> **Logs** to see if there are any error messages or misconfigurations then see the error messages below. - *Reauthentication required often*: If you are getting logged out every 7 days, this means an OAuth Consent Screen misconfiugration or your authentication token was revoked by Google for some other reason. diff --git a/source/_integrations/netatmo.markdown b/source/_integrations/netatmo.markdown index 158e25f9ac5..583ceac0598 100644 --- a/source/_integrations/netatmo.markdown +++ b/source/_integrations/netatmo.markdown @@ -244,7 +244,7 @@ client_secret: **After the `client_id` and `client_secret` are added to your `configuration.yaml` you must restart Home Assistant and then enable Netatmo through the integrations page.** -Menu: **Configuration** -> **Devices & Services**. +Menu: **Settings** -> **Devices & Services**. Click on the `+` sign to add an integration and click on **Netatmo**. After completing the configuration flow, the Netatmo integration will be available. diff --git a/source/_integrations/nfandroidtv.markdown b/source/_integrations/nfandroidtv.markdown index be030f30add..d038b2baa71 100644 --- a/source/_integrations/nfandroidtv.markdown +++ b/source/_integrations/nfandroidtv.markdown @@ -139,7 +139,7 @@ data: duration: 4 position: "bottom-left" fontsize: "medium" - transparency: "80%" + transparency: "75%" color: "teal" interrupt: 0 ``` diff --git a/source/_integrations/no_ip.markdown b/source/_integrations/no_ip.markdown index ca64b636e41..040c40b5dbb 100644 --- a/source/_integrations/no_ip.markdown +++ b/source/_integrations/no_ip.markdown @@ -5,8 +5,6 @@ ha_category: - Network ha_iot_class: Cloud Polling ha_release: 0.57 -ha_codeowners: - - '@fabaff' ha_domain: no_ip ha_integration_type: integration --- diff --git a/source/_integrations/onvif.markdown b/source/_integrations/onvif.markdown index 663afbf7ddf..24ae0535fb2 100644 --- a/source/_integrations/onvif.markdown +++ b/source/_integrations/onvif.markdown @@ -13,6 +13,7 @@ ha_platforms: - binary_sensor - button - camera + - diagnostics - sensor ha_integration_type: integration --- diff --git a/source/_integrations/pi_hole.markdown b/source/_integrations/pi_hole.markdown index 5dc54da18bb..338db2ba5d8 100644 --- a/source/_integrations/pi_hole.markdown +++ b/source/_integrations/pi_hole.markdown @@ -10,7 +10,6 @@ ha_iot_class: Local Polling ha_config_flow: true ha_release: 0.28 ha_codeowners: - - '@fabaff' - '@johnluetke' - '@shenxn' ha_domain: pi_hole diff --git a/source/_integrations/plex.markdown b/source/_integrations/plex.markdown index cdaea375535..2f0c5e21c66 100644 --- a/source/_integrations/plex.markdown +++ b/source/_integrations/plex.markdown @@ -376,5 +376,5 @@ Refresh a Plex library to scan for new and updated media. ## Notes -- The Plex integration supports multiple Plex servers. Additional connections can be configured under **Configuration** > **Devices & Services**. +- The Plex integration supports multiple Plex servers. Additional connections can be configured under **Settings** -> **Devices & Services**. - Movies must be located under the 'Movies' section in a Plex library to properly view the 'playing' state. diff --git a/source/_integrations/pvoutput.markdown b/source/_integrations/pvoutput.markdown index dd47223ca7c..34eee9326e0 100644 --- a/source/_integrations/pvoutput.markdown +++ b/source/_integrations/pvoutput.markdown @@ -6,7 +6,6 @@ ha_category: ha_release: 0.33 ha_iot_class: Cloud Polling ha_codeowners: - - '@fabaff' - '@frenck' ha_config_flow: true ha_domain: pvoutput diff --git a/source/_integrations/rfxtrx.markdown b/source/_integrations/rfxtrx.markdown index 2c15afbd84c..8bd0cc0aa70 100644 --- a/source/_integrations/rfxtrx.markdown +++ b/source/_integrations/rfxtrx.markdown @@ -88,7 +88,7 @@ connection: &rfxtrx ## Settings options -To configure options for RFXtrx integration go to **Configuration** >> **Devices & Services** and press **Options** on the RFXtrx card. +To configure options for RFXtrx integration go to **Settings** -> **Devices & Services** and press **Options** on the RFXtrx card. diff --git a/source/_integrations/roon.markdown b/source/_integrations/roon.markdown index 98d142a4f7c..9538f330fe5 100644 --- a/source/_integrations/roon.markdown +++ b/source/_integrations/roon.markdown @@ -20,7 +20,7 @@ This integration uses Roon Core, a Roon application that runs on a machine on yo ## Configuration -1. From the Home Assistant front-end, navigate to **Configuration** then **Integrations**. Under **Set up a new integration** locate 'Roon' and click **Configure**. +1. From the Home Assistant front-end, navigate to **Settings** -> **Devices & Services**. Under **Set up a new integration** locate 'Roon' and click **Configure**. 2. Home Assistant will then try to find your Roon Core - if it is successful it will display `Authorize HomeAssistant in Roon`. Click **Submit** and skip to step 4 3. If your Roon Core is not automatically found you can enter the `Hostname` or `IP address` for the Roon Core machine when requested and click **Submit**. 4. Home Assistant will then contact your Roon Core and ask to be authorized. You will need to enable this extension in the Room Application. Go to **Settings** and then **Extensions**, there you will see an entry for Home Assistant with a button next to it. Click **Enable**. diff --git a/source/_integrations/ruckus_unleashed.markdown b/source/_integrations/ruckus_unleashed.markdown index 2a4f894d972..123a19354f9 100644 --- a/source/_integrations/ruckus_unleashed.markdown +++ b/source/_integrations/ruckus_unleashed.markdown @@ -22,7 +22,7 @@ There is currently support for the following device types within Home Assistant: ## Configuration -To add a Ruckus Unleashed device to your installation, go to **Configuration** -> **Devices & Services**, click the `+` button, then select **Ruckus** from the list of integrations. +To add a Ruckus Unleashed device to your installation, go to **Settings** -> **Devices & Services**, click the `+` button, then select **Ruckus** from the list of integrations. It is required to configure the IP address of your **master access point**. See the section Access Points on the management web interface. And perhaps consider to set a preferred master (Admin & Services>System>System Info>Preferred master). diff --git a/source/_integrations/sabnzbd.markdown b/source/_integrations/sabnzbd.markdown index 06909e16744..196b956e733 100644 --- a/source/_integrations/sabnzbd.markdown +++ b/source/_integrations/sabnzbd.markdown @@ -13,6 +13,9 @@ ha_domain: sabnzbd ha_platforms: - sensor ha_integration_type: integration +ha_codeowners: + - '@shaiu' +ha_config_flow: true --- The `sabnzbd` integration will allow you to monitor and control your downloads with [SABnzbd](https://sabnzbd.org) from within Home Assistant and setup automations based on the information. diff --git a/source/_integrations/screenlogic.markdown b/source/_integrations/screenlogic.markdown index 0d21e5852ee..1b8b7922b30 100644 --- a/source/_integrations/screenlogic.markdown +++ b/source/_integrations/screenlogic.markdown @@ -32,7 +32,7 @@ The Pentair ScreenLogic integration allows you to integrate your Pentair Intelli ## Options -ScreenLogic options are set via **Configuration** -> **Devices & Services** -> **Pentair ScreenLogic** -> **Options**. +ScreenLogic options are set via **Settings** -> **Devices & Services** -> **Pentair ScreenLogic** -> **Options**. * Seconds between scans - How many seconds between each polling of the ScreenLogic gateway. diff --git a/source/_integrations/sensibo.markdown b/source/_integrations/sensibo.markdown index ec35e006bd2..7412ad23e02 100644 --- a/source/_integrations/sensibo.markdown +++ b/source/_integrations/sensibo.markdown @@ -8,6 +8,7 @@ ha_category: - Number - Select - Sensor + - Updates ha_release: 0.44 ha_iot_class: Cloud Polling ha_config_flow: true @@ -22,6 +23,7 @@ ha_platforms: - number - select - sensor + - update ha_homekit: true ha_dhcp: true ha_integration_type: integration diff --git a/source/_integrations/sensor.markdown b/source/_integrations/sensor.markdown index 059a725325f..6f9b315f67a 100644 --- a/source/_integrations/sensor.markdown +++ b/source/_integrations/sensor.markdown @@ -22,17 +22,18 @@ The type of data a sensor returns impacts how it is displayed in the frontend. T - **None**: Generic sensor. This is the default and doesn't need to be set. - **apparent_power**: Apparent power in VA. - **aqi**: Air Quality Index -- **battery**: Percentage of battery that is left. +- **battery**: Percentage of battery that is left - **carbon_dioxide**: Carbon Dioxide in CO2 (Smoke) - **carbon_monoxide**: Carbon Monoxide in CO (Gas CNG/LPG) -- **current**: Current in A. -- **date**: Date string (ISO 8601). -- **energy**: Energy in Wh, kWh or MWh. -- **frequency**: Frequency in Hz, kHz, MHz or GHz. -- **gas**: Gasvolume in m³ or ft³. -- **humidity**: Percentage of humidity in the air. -- **illuminance**: The current light level in lx or lm. -- **monetary**: The monetary value. +- **current**: Current in A +- **date**: Date string (ISO 8601) +- **duration**: Duration in days, hours, minutes or seconds +- **energy**: Energy in Wh, kWh or MWh +- **frequency**: Frequency in Hz, kHz, MHz or GHz +- **gas**: Gasvolume in m³ or ft³ +- **humidity**: Percentage of humidity in the air +- **illuminance**: The current light level in lx or lm +- **monetary**: The monetary value - **nitrogen_dioxide**: Concentration of Nitrogen Dioxide in µg/m³ - **nitrogen_monoxide**: Concentration of Nitrogen Monoxide in µg/m³ - **nitrous_oxide**: Concentration of Nitrous Oxide in µg/m³ @@ -40,16 +41,16 @@ The type of data a sensor returns impacts how it is displayed in the frontend. T - **pm1**: Concentration of particulate matter less than 1 micrometer in µg/m³ - **pm10**: Concentration of particulate matter less than 10 micrometers in µg/m³ - **pm25**: Concentration of particulate matter less than 2.5 micrometers in µg/m³ -- **power_factor**: Power factor in %. -- **power**: Power in W or kW. -- **pressure**: Pressure in hPa or mbar. -- **reactive_power**: Reactive power in var. -- **signal_strength**: Signal strength in dB or dBm. +- **power_factor**: Power factor in % +- **power**: Power in W or kW +- **pressure**: Pressure in hPa or mbar +- **reactive_power**: Reactive power in var +- **signal_strength**: Signal strength in dB or dBm - **sulphur_dioxide**: Concentration of sulphur dioxide in µg/m³ -- **temperature**: Temperature in °C or °F. -- **timestamp**: Datetime object or timestamp string (ISO 8601). -- **volatile_organic_compounds**: Concentration of volatile organic compounds in µg/m³. -- **voltage**: Voltage in V. +- **temperature**: Temperature in °C or °F +- **timestamp**: Datetime object or timestamp string (ISO 8601) +- **volatile_organic_compounds**: Concentration of volatile organic compounds in µg/m³ +- **voltage**: Voltage in V

    diff --git a/source/_integrations/sentry.markdown b/source/_integrations/sentry.markdown index 1d09b3a5dd6..4c98a49c63f 100644 --- a/source/_integrations/sentry.markdown +++ b/source/_integrations/sentry.markdown @@ -46,6 +46,6 @@ The Sentry integration provides settings to: - Ability to send out events originating from third-party Python packages. - Enable performance tracing and tune the tracing sample rate used. -To change the settings go in **Configuration** -> **Devices & Services**, find the already installed **Sentry** box and click on **Options**. +To change the settings go in **Settings** -> **Devices & Services**, find the already installed **Sentry** box and click on **Options**. After changing Sentry settings, you'll need to restart Home Assistant in order to make them effective. diff --git a/source/_integrations/senz.markdown b/source/_integrations/senz.markdown index 35754ca6505..501052f90b6 100644 --- a/source/_integrations/senz.markdown +++ b/source/_integrations/senz.markdown @@ -11,6 +11,7 @@ ha_codeowners: ha_domain: senz ha_platforms: - climate +ha_integration_type: integration --- The SENZ integration allows you to control and monitor your nVent RAYCHEM SENZ-WIFI thermostats. diff --git a/source/_integrations/slimproto.markdown b/source/_integrations/slimproto.markdown index 2b6b4147efa..1ece1666b79 100644 --- a/source/_integrations/slimproto.markdown +++ b/source/_integrations/slimproto.markdown @@ -1,5 +1,5 @@ --- -title: SlimProto (Squeezebox Players) +title: SlimProto (Squeezebox players) description: Instructions on how to integrate a SlimProto-based player (e.g., Squeezebox) into Home Assistant without the need for a media server. ha_category: - Media Player @@ -7,10 +7,11 @@ ha_release: 2022.5 ha_iot_class: Local Push ha_domain: slimproto ha_codeowners: - - "@marcelveldt" + - '@marcelveldt' ha_config_flow: true ha_platforms: - media_player +ha_integration_type: integration --- The SlimProto integration allows you to control a [Squeezebox](https://en.wikipedia.org/wiki/Squeezebox_%28network_music_player%29) music player directly from Home Assistant, without the need for an external Media Server such as Logitech Media Server. This lets you control Squeezebox hardware like the Classic, Transporter, Duet, Boom, Radio, and Touch and software players like [Squeezelite](https://github.com/ralph-irving/squeezelite), [PiCorePlayer](https://www.picoreplayer.org/) or [Max2Play](https://www.max2play.com/en/). For the real DIY enthusiast, [there even is a player for the ESP32](https://github.com/sle118/squeezelite-esp32). diff --git a/source/_integrations/smtp.markdown b/source/_integrations/smtp.markdown index cda7a604723..f9e5f1391cf 100644 --- a/source/_integrations/smtp.markdown +++ b/source/_integrations/smtp.markdown @@ -5,8 +5,6 @@ ha_category: - Notifications ha_iot_class: Cloud Push ha_release: pre 0.7 -ha_codeowners: - - '@fabaff' ha_domain: smtp ha_platforms: - notify diff --git a/source/_integrations/somfy_mylink.markdown b/source/_integrations/somfy_mylink.markdown index 7cc8c2c4d21..1ab9db32507 100644 --- a/source/_integrations/somfy_mylink.markdown +++ b/source/_integrations/somfy_mylink.markdown @@ -18,4 +18,4 @@ The `Somfy MyLink` integration is used as an interface to a compatible Somfy MyL {% include integrations/config_flow.md %} -If any of your devices are reversed, they can be adjusted in **Configuration** >> **Devices & Services** >> **Somfy MyLink** >> `Options`. +If any of your devices are reversed, they can be adjusted in **Settings** -> **Devices & Services** -> **Somfy MyLink** >> `Options`. diff --git a/source/_integrations/sonos.markdown b/source/_integrations/sonos.markdown index c135337b912..3b881e641b8 100644 --- a/source/_integrations/sonos.markdown +++ b/source/_integrations/sonos.markdown @@ -225,7 +225,7 @@ condition: # Coordinator - condition: template value_template: > - {{ state_attr( trigger.entity_id , 'sonos_group')[0] == trigger.entity_id }} + {{ state_attr( trigger.entity_id , 'group_members')[0] == trigger.entity_id }} # Going from queue to queue - condition: template value_template: > diff --git a/source/_integrations/squeezebox.markdown b/source/_integrations/squeezebox.markdown index ff4c0802baa..1d47aaf0ae8 100644 --- a/source/_integrations/squeezebox.markdown +++ b/source/_integrations/squeezebox.markdown @@ -1,5 +1,5 @@ --- -title: Logitech Squeezebox +title: Squeezebox (Logitech Media Server) description: Instructions on how to integrate a Logitech Squeezebox player into Home Assistant. ha_category: - Media Player diff --git a/source/_integrations/steam_online.markdown b/source/_integrations/steam_online.markdown index f6e2ebe3b28..0d38d35ab06 100644 --- a/source/_integrations/steam_online.markdown +++ b/source/_integrations/steam_online.markdown @@ -12,6 +12,9 @@ ha_platforms: ha_codeowners: - '@tkdrob' ha_integration_type: integration +ha_codeowners: + - '@tkdrob' +ha_config_flow: true --- The Steam integration will allow you to track the online status of public [Steam](https://steamcommunity.com) accounts. diff --git a/source/_integrations/subaru.markdown b/source/_integrations/subaru.markdown index 2bb77496934..00ad90bf91c 100644 --- a/source/_integrations/subaru.markdown +++ b/source/_integrations/subaru.markdown @@ -70,7 +70,7 @@ The current lock status is always unknown due to the fact that the Subaru API do Subaru integration options are set via: -**Configuration** -> **Devices & Services** -> **Subaru** -> **Options**. +**Settings** -> **Devices & Services** -> **Subaru** -> **Options**. - **Enable vehicle polling *[Default: off]*:** When enabled, vehicle polling will send a remote command to your vehicle every 2 hours to obtain new sensor data. This involves "waking" your vehicle and requesting that it send new data to Subaru servers. Without vehicle polling, new sensor data is only received when the vehicle automatically pushes data (normally after engine shutdown). This option only applies to Gen 2 vehicles with Security Plus subscriptions because it uses a "locate" command to request the data. diff --git a/source/_integrations/syslog.markdown b/source/_integrations/syslog.markdown index e282e25dfb6..2a8b5853c3c 100644 --- a/source/_integrations/syslog.markdown +++ b/source/_integrations/syslog.markdown @@ -5,8 +5,6 @@ ha_category: - Notifications ha_release: pre 0.7 ha_iot_class: Local Push -ha_codeowners: - - '@fabaff' ha_domain: syslog ha_platforms: - notify diff --git a/source/_integrations/system_health.markdown b/source/_integrations/system_health.markdown index 725ee51a3e4..87ddc4c1943 100644 --- a/source/_integrations/system_health.markdown +++ b/source/_integrations/system_health.markdown @@ -18,6 +18,6 @@ This integration is by default enabled, unless you've disabled or removed the [` system_health: ``` -System Health integration data can be viewed at **Configuration** -> **Info**. +System Health integration data can be viewed at **Settings** -> **System** -> **System Health**. Data includes information about your system architecture, operating system and version, Home Assistant installation type and version, Python version, frontend version, the number of [Dashboards](/dashboards/dashboards/) and [Views](/dashboards/views/) you have, and more. diff --git a/source/_integrations/system_log.markdown b/source/_integrations/system_log.markdown index 39db628938f..b2e4889099e 100644 --- a/source/_integrations/system_log.markdown +++ b/source/_integrations/system_log.markdown @@ -9,7 +9,7 @@ ha_domain: system_log ha_integration_type: integration --- -The `system_log` integration stores information about all logged errors and warnings in Home Assistant. To view your logs, navigate to **Configuration** -> **Settings** -> **Logs**. In order to not overload Home Assistant with log data, only the 50 last errors and warnings will be stored. Older entries are automatically discarded from the log. It is possible to change the number of stored log entries using the parameter `max_entries`. +The `system_log` integration stores information about all logged errors and warnings in Home Assistant. To view your logs, navigate to **Settings** -> **System** -> **Logs**. In order to not overload Home Assistant with log data, only the 50 last errors and warnings will be stored. Older entries are automatically discarded from the log. It is possible to change the number of stored log entries using the parameter `max_entries`. ## Configuration diff --git a/source/_integrations/tellduslive.markdown b/source/_integrations/tellduslive.markdown index 6b942285ec0..31629cc905e 100644 --- a/source/_integrations/tellduslive.markdown +++ b/source/_integrations/tellduslive.markdown @@ -49,10 +49,4 @@ scan_interval: default: 60 {% endconfiguration %} -

    - -It is only possible to configure the `scan_interval` when setting up the device. If the polling interval needs to be changed after the device is configured it must be changed manually by changing `"scan_interval": 60,` for the device in the file `.storage/core.config_entries`. - -
    - The integration will offer configuration through the Home Assistant user interface where it will let you associate it with your Telldus Live account. diff --git a/source/_integrations/tellstick.markdown b/source/_integrations/tellstick.markdown index 501be004a24..84b8cad4c61 100644 --- a/source/_integrations/tellstick.markdown +++ b/source/_integrations/tellstick.markdown @@ -175,4 +175,4 @@ switch: - platform: tellstick ``` -[tellstick-gateway]: https://telldus.com/produkt/z-wave-gateway-tellstick-znet-lite-ver-2/ +[tellstick-gateway]: https://telldus.com diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown index 2f11a431118..6bc9842a832 100644 --- a/source/_integrations/tplink.markdown +++ b/source/_integrations/tplink.markdown @@ -12,6 +12,7 @@ ha_config_flow: true ha_codeowners: - '@rytilahti' - '@thegardenmonkey' + - '@bdraco' ha_domain: tplink ha_platforms: - diagnostics diff --git a/source/_integrations/tractive.markdown b/source/_integrations/tractive.markdown index 09f98daa0bf..43b5295a5f9 100644 --- a/source/_integrations/tractive.markdown +++ b/source/_integrations/tractive.markdown @@ -14,6 +14,7 @@ ha_domain: tractive ha_platforms: - binary_sensor - device_tracker + - diagnostics - sensor - switch ha_integration_type: integration diff --git a/source/_integrations/tradfri.markdown b/source/_integrations/tradfri.markdown index 2a53507bec2..f5ff6b91448 100644 --- a/source/_integrations/tradfri.markdown +++ b/source/_integrations/tradfri.markdown @@ -57,4 +57,4 @@ Please make sure you have `autoconf` installed (`$ sudo apt-get install autoconf ## Known limitations - The TRÅDFRI Shortcut button, Remotes and motion sensor only send information about their battery status, no events, to Home Assistant and thus can't be used to automate with. If you want to automate with these devices, you need to use something like [ZHA](/integrations/zha/). -- The groups you find in the app are not imported into Home Assistant as they are known to cause stability issues. We recommend that you use the native [light groups](/integrations/light.group/) instead. \ No newline at end of file +- The groups you find in the app are not imported into Home Assistant as they are known to cause stability issues. We recommend that you use the native [light groups](/integrations/light.group/) instead. diff --git a/source/_integrations/tuya.markdown b/source/_integrations/tuya.markdown index f84fd554d47..b7fa1a7f1f2 100644 --- a/source/_integrations/tuya.markdown +++ b/source/_integrations/tuya.markdown @@ -23,7 +23,6 @@ ha_domain: tuya ha_codeowners: - '@Tuya' - '@zlinoliver' - - '@METISU' - '@frenck' ha_platforms: - alarm_control_panel diff --git a/source/_integrations/version.markdown b/source/_integrations/version.markdown index bea539baad4..db6b36af93b 100644 --- a/source/_integrations/version.markdown +++ b/source/_integrations/version.markdown @@ -8,7 +8,6 @@ ha_iot_class: Local Push ha_release: 0.52 ha_quality_scale: internal ha_codeowners: - - '@fabaff' - '@ludeeus' ha_domain: version ha_platforms: diff --git a/source/_integrations/vicare.markdown b/source/_integrations/vicare.markdown index 8d5caf2ead2..30e82e7d36d 100644 --- a/source/_integrations/vicare.markdown +++ b/source/_integrations/vicare.markdown @@ -13,6 +13,7 @@ ha_platforms: - binary_sensor - button - climate + - diagnostics - sensor - water_heater ha_dhcp: true diff --git a/source/_integrations/xiaomi_aqara.markdown b/source/_integrations/xiaomi_aqara.markdown index f8fb0a39609..c32acde7777 100644 --- a/source/_integrations/xiaomi_aqara.markdown +++ b/source/_integrations/xiaomi_aqara.markdown @@ -66,7 +66,7 @@ Please note, there are two versions of the hub: v1 and v2. v1 can be used with H Follow the setup process using your phone and Mi-Home app. From here you will be able to retrieve the key (password) from within the app following [this tutorial](https://www.domoticz.com/wiki/Xiaomi_Gateway_(Aqara)#Adding_the_Xiaomi_Gateway_to_Domoticz). -To enable {{ page.title }} in your installation, go to **Configuration** in the sidebar, then click **Devices & Services**. Xiaomi Aqara gateways should be discovered automatically and should show up in the overview. Hit configure and go through the steps to specify the optional settings. If your aqara gateway does not show up automatically, click the + icon in the lower right. Then search for "xiaomi_aqara" and enter the setup. Multiple gateways can be configured by simply repeating the setup multiple times. +To enable {{ page.title }} in your installation, go to **Settings** -> **Devices & Services**. Xiaomi Aqara gateways should be discovered automatically and should show up in the overview. Hit configure and go through the steps to specify the optional settings. If your aqara gateway does not show up automatically, click the + icon in the lower right. Then search for "xiaomi_aqara" and enter the setup. Multiple gateways can be configured by simply repeating the setup multiple times. {% configuration %} interface: diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown index ef5968dcbc8..4e56625875a 100644 --- a/source/_integrations/xiaomi_miio.markdown +++ b/source/_integrations/xiaomi_miio.markdown @@ -26,6 +26,7 @@ ha_platforms: - binary_sensor - button - device_tracker + - diagnostics - fan - humidifier - light diff --git a/source/_integrations/yamaha_musiccast.markdown b/source/_integrations/yamaha_musiccast.markdown index a601a7a425c..6ab154fc491 100644 --- a/source/_integrations/yamaha_musiccast.markdown +++ b/source/_integrations/yamaha_musiccast.markdown @@ -15,6 +15,7 @@ ha_platforms: - media_player - number - select + - switch ha_integration_type: integration --- diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index c5edc1d5e88..3c5cccacd37 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -31,6 +31,7 @@ ha_platforms: - climate - cover - device_tracker + - diagnostics - fan - light - lock @@ -423,7 +424,7 @@ When reporting issues, please provide the following information in addition to i 1. Debug logs for the issue, see [debug logging](#debug-logging) 2. Model of Zigbee radio being used 3. If issue is related to a specific Zigbee device, provide device Zigbee signature. Signature is available at -**Configuration** -> **Devices & Services** -> **Zigbee Home Automation** (click **Configure**) -> **Devices** (pick your device) -> **Zigbee Device Signature** +**Settings** -> **Devices & Services** -> **Zigbee Home Automation** (click **Configure**) -> **Devices** (pick your device) -> **Zigbee Device Signature** ### Debug logging diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown index cb1425dcb5d..19c4c935cf5 100644 --- a/source/_integrations/zwave_js.markdown +++ b/source/_integrations/zwave_js.markdown @@ -39,6 +39,7 @@ ha_platforms: - siren - switch ha_integration_type: integration +ha_zeroconf: true --- This integration allows you to control a Z-Wave network via the [Z-Wave JS](https://zwave-js.github.io/node-zwave-js/#/) driver. This is our recommended Z-Wave integration for Home Assistant. If you're migrating from the deprecated `zwave`, see [our migration instructions](#migrating-from-previous-z-wave-implementations). @@ -859,7 +860,7 @@ If the interview is complete, then the device does not yet have a device file fo When trying to determine why something isn't working as you expect, or when reporting an issue with the integration, it is helpful to know what Z-Wave JS sees as the current state of your Z-Wave network. To get a dump of your current network state, follow the menu: -{% my integrations title="**Configuration** -> **Devices & Services**" %} -> **Z-Wave JS** -> **...** -> **Download diagnostics** +{% my integrations title="**Settings** -> **Devices & Services**" %} -> **Z-Wave JS** -> **...** -> **Download diagnostics** ### Interference issues diff --git a/source/_posts/2022-05-04-release-20225.markdown b/source/_posts/2022-05-04-release-20225.markdown new file mode 100644 index 00000000000..2e1e9b9f9c7 --- /dev/null +++ b/source/_posts/2022-05-04-release-20225.markdown @@ -0,0 +1,1523 @@ +--- +layout: post +title: "2022.5: Streamlining settings" +description: "Streamlining the settings menu, an Insteon control panel, lots of new features for automations and scripts, and much more!" +date: 2022-05-04 00:00:00 +date_formatted: "May 04, 2022" +author: Franck Nijhof +author_twitter: frenck +comments: true +categories: +- Release-Notes +- Core +og_image: /images/blog/2022-05/social.png +--- + + + +Home Assistant Core 2022.5! + +And, as often said: "All things seem possible in May!". Well, possibilities +we have for you this last month of spring. + +The most visible thing this release is the next iteration of the settings menu, +of which the result, to me personally, makes tons of sense. It took me a bit +to get used to, but honestly I like it! 🤩 + +Meanwhile, at [Nabu Casa], they released annual subscriptions for Home Assistant +Cloud worldwide (except for Canada, the UK, and the EU, they will follow soon with +local currency support). + +I'm also very excited to present you with a whole lot of new powerful +automations and scripts features! Some for the UI, but there are some real +game changers in there that our YAML community will love! 🤖 + +Enjoy the release! + +../Frenck + +[Nabu Casa]: https://www.nabucasa.com/ + + + +- [Reorganized settings menu](#reorganized-settings-menu) +- [Find entities even quicker than before](#find-entities-even-quicker-than-before) +- [New automation & script features](#new-automation--script-features) + - [If-then](#if-then) + - [Calendar trigger](#calendar-trigger) + - [For each](#for-each) + - [Disable any trigger, condition, or action](#disable-any-trigger-condition-or-action) + - [Continue on error](#continue-on-error) + - [Stopping a script or automation](#stopping-a-script-or-automation) + - [Parallelizing actions](#parallelizing-actions) + - [Using a single state trigger for multiple entities](#using-a-single-state-trigger-for-multiple-entities) + - [Trigger on not matching to/from states](#trigger-on-not-matching-tofrom-states) + - [Shorthand notation for logical conditions](#shorthand-notation-for-logical-conditions) +- [Gauge card segment colors](#gauge-card-segment-colors) +- [Database optimizations](#database-optimizations) +- [Update entity updates](#update-entity-updates) +- [Insteon control panel](#insteon-control-panel) +- [Template selector](#template-selector) +- [Other noteworthy changes](#other-noteworthy-changes) +- [New Integrations](#new-integrations) +- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui) +- [Release 2022.5.1 - May 5](#release-202251---may-5) +- [Release 2022.5.2 - May 6](#release-202252---may-6) +- [Release 2022.5.3 - May 8](#release-202253---may-8) +- [Need help? Join the community!](#need-help-join-the-community) +- [Breaking Changes](#breaking-changes) +- [Farewell to the following](#farewell-to-the-following) +- [All changes](#all-changes) + + +## Reorganized settings menu + +A couple of releases ago, we started reorganizing the configuration menu, and +this release is bringing the next big step in that reorganization. + +The goal is to have everything in a single logical place, and after user tests +and many discussions in frontend and UX channels, this is what the menu +now looks like: + +Screenshot showing the new configuration menu structure + +Most notably, it's been renamed from "Configuration" to "Settings", and we have a +brand new "System" submenu (shown on the right in the above screenshot). + +Are you running Home Assistant OS? The Supervisor has been fully merged into +the settings menu to provide a seamless/unified experience. It removes +weirdness like having a network section in one menu and the Supervisor section. + +Blueprints moved to the automations & scenes section, and by popular request: +Helpers have moved to the devices & services page. + +YAML configuration tools have a new home in the developer tools, a more +logical place for YAML configuration checks and reloading. + +You might notice some of the new menu items are fairly empty. For those menus, +like "Storage" and "Hardware", we have more content planned soon! + +Just to be sure, we have added a list of changes to the breaking changes section; +please check those out in case you are missing something. + +## Find entities even quicker than before + +Looking to access that one entity quickly? But it isn't on your dashboard? + +The [Quick Bar](/docs/tools/quick-bar/) helps with that; just press `e` anywhere +you are in Home Assistant. This release adds a quick search button to the +dashboards as well, so you can look up and access any entity you need, +even when it is not on your current dashboard. + +Screenshot showing the new quick search button + +To conserve space, the search is not shown on mobile devices; but is available +via the overflow menu (the three dots in the top right). + +## New automation & script features + +This release is packed with new automation & script features! Some have been +added to the UI, and others are advanced features that are only available when +using YAML. + +One thing almost all these changes have in common: They have been requested +and voted for by the community in our [Feature Requests] forum. + +[Feature Requests]: https://community.home-assistant.io/c/feature-requests/13 + +### If-then + +When we introduced the [Choose action](/docs/scripts/#choose-a-group-of-actions), +our goal was to provide a structure that allowed for other action sequences +selectively based on conditions. + +While this structure is very flexible and extensive, there was still a desire +for an if-then(-else) structure that is small, simple, compact, and clean. +This release brings you just that. + +The new if-then action is available via YAML and via the UI using automations +and scripts editors. + +Screenshot showing If-then + +{% details "If-then example in YAML" %} + +If YAML automations are more your thing, this is how you can use the new +if-then action in your automations and scripts. + +```yaml +actions: + - if: + - alias: "If no one is home" + condition: state + entity_id: zone.home + state: 0 + then: + - alias: "Then start cleaning already!" + service: vacuum.start + target: + area_id: living_room + # The `else` is fully optional and can be omitted + else: + - service: notify.notify + data: + message: "Skipped cleaning, someone is home!" +``` + +Note that that `if` also supports a shorthand condition template (if that +is more your style), for example: + +{% raw %} + +```yaml +actions: + - if: "{{ states('zone.home') == 0 }}" + then: + - alias: "Then start cleaning already!" + service: vacuum.start + target: + area_id: living_room +``` + +{% endraw %} + +{% enddetails %} + +[More information can be found in the scripts documentation](/docs/scripts/#if-then). + +### Calendar trigger + +[@allenporter] gave the [Calendar] integration (and the [Google Calendars] +integration) lots of love. In the process, a new Calendar trigger was added, +which is available for use in your automations. + +

    +Screenshot showing the new calendar trigger in the UI +The new calendar trigger is available in the automation editor. +

    + +This brand new trigger is slightly more flexible than the (previously only +other option) state trigger. It is available for automations in YAML as well, +and the trigger provides [lots of trigger variables](/docs/automation/templating/#calendar) +you can use in your templates. + +{% details "Calendar trigger example in YAML" %} + +The calendar trigger is, of course, also available in YAML. This automation +example shows the use of the trigger and some of the variables it provides. + +{% raw %} + +```yaml +automation: + trigger: + - platform: calendar + event: start + entity_id: calendar.personal + action: + - service: persistent_notification.create + data: + message: >- + Event {{ trigger.calendar_event.summary }} @ + {{ trigger.calendar_event.start }} +``` + +{% endraw %} + +{% enddetails %} + +[More information can be found in the Calendar integration documentation](/integrations/calendar/#automation). + +[@allenporter]: https://github.com/allenporter +[Calendar]: /integrations/calendar/ +[Google Calendars]: /integrations/google + +### For each + +We had several options available to repeat a [group of actions]. For example, +repeating based on a count, while a condition passes, or until a condition +passes. + +These are very powerful, but repeating a sequence for each item in a list +was also requested and voted for. This release adds: For each. + +This is an advanced feature and is only available for use in automations written +manually in YAML. Here is an example that sends out two notifications in +different languages: + +{% raw %} + +```yaml +repeat: + for_each: + - language: English + message: Hello World + - language: Dutch + message: Hallo Wereld + sequence: + - service: notify.phone + data: + title: "Message in {{ repeat.item.language }}" + message: "{{ repeat.item.message }}!" +``` + +{% endraw %} + +Each item in the list will be run against a sequence of actions, and the item +is available as a variable you can use in your templates. The items you can +provide to `for_each` can be mappings, lists of just strings, and even complex +templates that provide a list as a result. + +[More information can be found in the scripts documentation](/docs/scripts/#for-each). + +[group of actions]: /docs/scripts/#repeat-a-group-of-actions + +### Disable any trigger, condition, or action + +Sometimes, you may want to disable a specific trigger, action, or condition, +whether this is for testing, a temporary workaround, or any other reason. + +In YAML, you'd comment out parts of your automation, but if you wanted +to do that in the UI, the only option you have is to delete it from the +automation or script. + +In this release, we added support for disabling a trigger, action, or condition; +without the need for removing it or commenting it out! A disabled trigger +won't fire, a disabled condition always passes, and a disabled action is +skipped. + +Screenshot showing a disabled condition in a UI automation + +{% details "Disabled example in YAML" %} + +If YAML automations are more your thing, this disabled feature is still +helpful. While, of course, you can still comment parts out easily; using +this feature will make disabled parts still show up in automation and +script debug traces. + +Every trigger, condition, and action now has an `enabled` parameter. Which +you can set to `false` to disable that section. For example: + +```yaml +# Example automation with a disabled trigger +automation: + trigger: + # This trigger will not trigger, as it is disabled. + # This automation does not run when the sun is set. + - enabled: false + platform: sun + event: sunset + + # This trigger will fire, as it is not disabled. + - platform: time + at: "15:32:00" +``` + +{% enddetails %} + +More information can be found in the disabled [Triggers], [Conditions], +and [Actions] documentation. + +[Actions]: /docs/scripts/#disabling-an-action +[Conditions]: /docs/scripts/conditions#disabling-a-condition +[Triggers]: /docs/automation/trigger/#disabling-a-trigger + +### Continue on error + +An automation runs a sequence of actions. One of the questions we +often see/read/get is: "If one of the actions fails, why does the whole +automation stop?" + +Good question! To answer this, we have added: Continue on error. + +It allows specific steps in an automation or script sequence to fail +without interrupting the rest of the sequence. + +This advanced feature is currently only available for automations and scripts +written in YAML. The following example shows an automation action that will +always run the second action, even if the first action fails with an error: + +```yaml +action: + - alias: "If this one fails..." + continue_on_error: true + service: notify.super_unreliable_service_provider + data: + message: "I'm going to error out..." + + - alias: "This one will still run!" + service: persistent_notification.create + data: + title: "Hi there!" + message: "I'm fine..." +``` + +[More information can be found in the scripts documentation](/docs/scripts/#continuing-on-error). + +### Stopping a script or automation + +You can now stop a script or automation halfway using the Stop action. +Combined with the previously mentioned new If-then action, this can be used +to stop an automation or script conditionally. + +For example, this can be helpful if you want just part of an automation to +run when you are home and run it at full when you are away. + +This feature is available both via the UI and YAML. + +Screenshot showing the new stop action + +{% details "Stop example in YAML" %} + +When writing YAML automations or scripts, this is how the Stop action looks: + +```yaml +action: + - stop: "Stop right here!" + # Optionally mark it as an unexpected error + error: true +``` + +{% enddetails %} + +[More information can be found in the scripts documentation](/docs/scripts/#stopping-a-script-sequence) + +### Parallelizing actions + +This release introduces a highly advanced feature that provides a way to +parallelize actions. + +By default, all actions in Home Assistant run sequentially. This means the +next action is only started after the current action has been completed. + +Running in serial is not always needed, for example, if the sequence of actions +doesn’t rely on each other and order doesn’t matter. For those cases, the +parallel action can be used to run the actions in the sequence in parallel, +meaning all the actions are started simultaneously. + +```yaml +automation: + - trigger: + - platform: state + entity_id: binary_sensor.motion + to: "on" + action: + - parallel: + - service: notify.person1 + data: + message: "These messages are sent at the same time!" + - service: notify.person2 + data: + message: "These messages are sent at the same time!" +``` + +This feature is partly available via the UI; however, as said: This is quite +a powerful and advanced feature, and it comes with caveats. Be sure to check +out the [script documentation on parallelizing actions](/docs/scripts/#parallelizing-actions) +before deciding to use it. + +### Using a single state trigger for multiple entities + +If you write automations in YAML, you are probably already aware of the +ability to trigger on multiple entities in a single trigger; it has been +around for quite some time. + +And now also available in the UI. A small addition that might help you cut +down the length of your UI-managed automations. + +Screenshot showing multiple entites in a single trigger from the UI. + +### Trigger on not matching to/from states + +This is a YAML only feature we have added to the state triggers: Triggering +on not matching to/from states. Yes, you read that correctly. When it **not** +matches it triggers. + +Instead of `from`, you can now use `not_from` and instead of `to`, you can now +use `not_to`. This example trigger will only trigger if the state was previously +not "unavailable" or "unknown": + +```yaml +trigger: + - platform: state + entity_id: light.living_room + not_from: + - "unavailable" + - "unknown" + to: "on" +``` + +[More information can be found on the state condition documentation](/docs/scripts/conditions#state-condition). + +### Shorthand notation for logical conditions + +A neat little YAML feature [@thomasloven] added can make your YAML-based +automations and scripts looks significantly cleaner. + +Logical conditions (also known as `and`, `or`, `not`) now have a shorthand +notation. Some example pseudo code to show them all: + +```yaml +or: + - + - and: + - + - + - not: + - +``` + +In the above ``, of course, needs to be replaced with an actual +condition, but the short new syntax of `or`, `and`, and `not` is clearly visible. + +[More information can be found on the condition documentation](/docs/scripts/conditions#logical-conditions). + +[@thomasloven]: https://github.com/thomasloven + +## Gauge card segment colors + +An excellent addition by [@Netzwerkfehler] is the ability to freely define the +number of segments, and their colors, of the gauge card! + +

    +Screenshot of the gauge card with multiple colored segments. +Screenshot of the gauge card with multiple colored segments. +

    + +Helpful if you'd like to define upper and lower sensor +limits on your gauge, as shown in the example above. The configuration example +used for the above screenshot can be found in the [Gauge Card documentation]. + +[@Netzwerkfehler]: https://github.com/Netzwerkfehler +[Gauge Card documentation]: /dashboards/gauge/#examples + +## Database optimizations + +The last release focused on reducing the size of the database and optimizing +the writing of data to the database. + +While there are some additional optimizations in this release to further reduce +the amount of data that needs to be written, in this release, we focused on how +often data is read from the database and optimizing its scale for larger setups. + +This release is for you if you have many sensors generating statistics, as +compiling statistics now takes 30-100x less time. + +Are you using the [History Stats] integration? The number of database queries +needed for most sensors with a fixed start time is 99% less. + +We have made additional improvements to the history APIs to speed up retrieving +from the database, reducing API response times by 15-35% on average. + +Finally, we have reduced the memory used during database migrations to smooth +future migrations and are now automatically repacking your database once a +month to keep things tidy. + +[History Stats]: /integrations/history_stats + +## Update entity updates + +In the [previous release, we introduced update entities][update-entities]. +It was a well-received concept, and we added a couple of improvements to it. + +Almost all feedback we got involved "Skipping an update"-related functionality. +Can I unskip an update? How to see which updates I have skipped? + +To help with these, we added a dedicated settings menu for updates. It provides +an overview of all pending updates and provides the ability to view updates +you have previously skipped. + +Screenshot showing the new updates page in the settings menu + +Skipped updates can now be "unskipped" again too! This works in the same way +as skipping an update but can also be done in automations using this new +{% my developer_call_service service="service" %}. + +Two new integrations have implemented update entities this release: + +- [Sensibo], done by [@gjohansson-ST] +- [AVM FRITZ!Box Tools], done by [@Mask3007] + +And finally, if you'd like to receive update notifications: The +["Update notifications" Blueprint][update-notify] by [@mdegat01] has been +getting quite some attention in the community this month! + +[@gjohansson-ST]: https://github.com/gjohansson-ST +[@Mask3007]: https://github.com/Mask3007 +[@mdegat01]: https://github.com/mdegat01 +[AVM FRITZ!Box Tools]: /integrations/fritz +[Sensibo]: /integrations/sensibo +[update-entities]: /blog/2022/04/06/release-20224/#introducing-update-entities +[update-notify]: https://community.home-assistant.io/t/update-notifications-core-os-addons-hacs-etc/409161 + +## Insteon control panel + +In case you have missed it, the US smart home company Insteon went out of +business and shut down its cloud services. + +[Read more about it in our dedicated blog post][insteon-blog]. + +As Home Assistant works with Insteon locally, we have seen quite a few new +users joining our community; so: + +👋 Hello, dear Insteon user. We have a new control panel for you! + +

    +Screenshot showing the new Insteon control panel +The new Insteon control panel allows you to manage your Insteon devices. +

    + +This new control panel allows you to manage your Insteon device from +Home Assistant directly, just like you would have done previously with +the Insteon application. + +Thanks for you hard work on this [Tom Harris]! + +[Tom Harris]: https://github.com/teharris1 +[insteon-blog]: /blog/2022/04/19/for-insteon-users/ + +## Template selector + +A new [selector] is added: The [Template selector]. + +This new selector can be used in, for example, Blueprints, scripts fields, or +in a (custom) integration. It provides a nice code editor with Jinja syntax +highlighting and entity auto-completion. + +We have deployed it in the automations and scripts editor too! So, you +now get this editor when editing your template conditions or wait for template +actions in the UI. + +Screenshot showing the template editor + +[selector]: /docs/blueprint/selectors/ +[Template selector]: /docs/blueprint/selectors/#template-selector + +## Other noteworthy changes + +There is much more juice in this release; here are some of the other +noteworthy changes this release: + +- Every script now automatically gets a unique ID, which means you can edit + their name, icon and assign them to areas straight from the UI! + Thanks, [@frenck]! +- If you run the Z-Wave JS server manually in, for example, a Docker container, + it will now be automatically discovered on your network. Thanks [@raman325]! +- Template entities now have a `this` variable available, which is a reference + to the state of the template entity itself. Awesome work [@akloeckner] and + [@emontnemery]! +- Running Home Assistant Core or Container? [@frenck] added the + {% my developer_call_service service="backup.create" %} service to the + [backup] integration allowing you to create an automation to create backups + on a schedule. +- [@sisimomo] added Markdown support to Blueprint input descriptions, allowing + you to add links to, for example, documentation in your Blueprints. +- The [Shelly] integration now supports authentication for the second generation + devices, thanks [@thecode]! +- [State conditions] with multiple entities can now also match if any of the + entities match the condition (instead of all), thanks [@frenck]! +- [Sonos] now has a favorites sensor so that you can access and use your + favorites in your automations, scripts, and templates. Thanks [@jjlawren]! +- [@dmulcahey] added support for configuring the power-on state of devices + that have this configuration option to [ZHA]. Nice! +- Sensors now have a new device class available: "duration". Thanks, [@bdraco]! +- The output of [Media Selector] can now be directly used with play media + service calls in your Blueprints. Awesome, [@emontnemery]! +- [@raman325] added frontend support for Sirens, so you can actually turn one + on from the UI. 🚨 Alarming news [@raman325]! +- [@frenck] added a persons attribute to zones, which indicates who is + currently in a zone. +- When customizing the device class / "Show as" of an entity in the UI, you can + now set it to nothing/empty as well. Thanks, [@zsarnett]! +- [@rdfurman] Added support to the [Honeywell] Total Connect Comfort (US) + integration for outdoor sensors. Awesome! +- [Philips TV] now provides a switch to turn on/off the "Ambilight+Hue" syncing + (if your TV model supports that). Thanks, [@bramstroker]! + +[@akloeckner]: https://github.com/akloeckner +[@bdraco]: https://github.com/bdraco +[@bramstroker]: https://github.com/bramstroker +[@dmulcahey]: https://github.com/dmulcahey +[@emontnemery]: https://github.com/emontnemery +[@frenck]: https://github.com/frenck +[@jjlawren]: https://github.com/jjlawren +[@raman325]: https://github.com/raman325 +[@rdfurman]: https://github.com/rdfurman +[@sisimomo]: https://github.com/sisimomo +[@thecode]: https://github.com/thecode +[@zsarnett]: https://github.com/zsarnett +[backup]: /integrations/backup +[Honeywell]: /integrations/honeywell +[Media Selector]: /docs/blueprint/selectors/#media-selector +[Philips TV]: /integrations/philips_js +[Shelly]: /integrations/shelly +[Sonos]: /integrations/sonos +[State conditions]: /docs/scripts/conditions#state-condition +[ZHA]: /integrations/zha + +## New Integrations + +We welcome the following new integrations this release: + +- [Meater], added by[@Sotolotl] +- [QNAP QSW], added by [@Noltari] +- [SENZ], added by [@milanmeu] +- [SlimProto (Squeezebox Players)], added by [@marcelveldt] +- [Trafikverket Ferry], added by [@gjohansson-ST] + +[@marcelveldt]: https://github.com/marcelveldt +[@milanmeu]: https://github.com/milanmeu +[@Noltari]: https://github.com/Noltari +[@Sotolotl]: https://github.com/Sotolotl +[@gjohansson-ST]: https://github.com/gjohansson-ST +[Meater]: /integrations/meater +[QNAP QSW]: /integrations/qnap_qsw +[SENZ]: /integrations/senz +[SlimProto (Squeezebox Players)]: /integrations/slimproto +[Trafikverket Ferry]: /integrations/trafikverket_ferry + + +## Integrations now available to set up from the UI + +The following integrations are now available via the Home Assistant UI: + +- [SABnzbd], done by [@shaiu] +- [SQL], done by [@gjohansson-ST] +- [Steam], done by [@tkdrob] +- [Tautulli], done by [@tkdrob] + +[@gjohansson-ST]: https://github.com/gjohansson-ST +[@shaiu]: https://github.com/shaiu +[@tkdrob]: https://github.com/tkdrob +[SABnzbd]: /integrations/sabnzbd +[SQL]: /integrations/sql +[Steam]: /integrations/steam_online +[Tautulli]: /integrations/tautulli + +## Release 2022.5.1 - May 5 + +- fix reading of battery messages ([@2Fake] - [#70659]) ([devolo_home_control docs]) +- Only test for EncryptedBridge in Samsung J/H models ([@epenet] - [#71291]) ([samsungtv docs]) +- Ensure rachio retries setup later when cloud service is broken ([@bdraco] - [#71300]) ([rachio docs]) +- Fix lutron caseta occupancy sensors ([@bdraco] - [#71309]) ([lutron_caseta docs]) +- Update aioairzone to v0.4.3 ([@Noltari] - [#71312]) ([airzone docs]) +- Fix apple tv warning ([@balloob] - [#71321]) ([apple_tv docs]) +- Fix Meater ([@emontnemery] - [#71324]) ([meater docs]) +- Bump numpy to 1.21.6 ([@pvizeli] - [#71325]) ([opencv docs]) ([tensorflow docs]) ([trend docs]) ([iqvia docs]) ([compensation docs]) +- Only lookup unknown Google Cast models once ([@emontnemery] - [#71348]) ([cast docs]) +- Bump library version ([@bieniu] - [#71349]) ([nam docs]) +- Ignore loading system entity category ([@balloob] - [#71361]) +- Fix importing blueprints ([@balloob] - [#71365]) ([blueprint docs]) +- Add unique ids to sensors ([@shaiu] - [#71367]) ([sabnzbd docs]) +- Bump pychromecast to 12.1.1 ([@balloob] - [#71377]) ([cast docs]) + +[#70659]: https://github.com/home-assistant/core/pull/70659 +[#71291]: https://github.com/home-assistant/core/pull/71291 +[#71300]: https://github.com/home-assistant/core/pull/71300 +[#71309]: https://github.com/home-assistant/core/pull/71309 +[#71312]: https://github.com/home-assistant/core/pull/71312 +[#71321]: https://github.com/home-assistant/core/pull/71321 +[#71324]: https://github.com/home-assistant/core/pull/71324 +[#71325]: https://github.com/home-assistant/core/pull/71325 +[#71348]: https://github.com/home-assistant/core/pull/71348 +[#71349]: https://github.com/home-assistant/core/pull/71349 +[#71361]: https://github.com/home-assistant/core/pull/71361 +[#71365]: https://github.com/home-assistant/core/pull/71365 +[#71367]: https://github.com/home-assistant/core/pull/71367 +[#71377]: https://github.com/home-assistant/core/pull/71377 +[@2Fake]: https://github.com/2Fake +[@Noltari]: https://github.com/Noltari +[@balloob]: https://github.com/balloob +[@bdraco]: https://github.com/bdraco +[@bieniu]: https://github.com/bieniu +[@emontnemery]: https://github.com/emontnemery +[@epenet]: https://github.com/epenet +[@pvizeli]: https://github.com/pvizeli +[@shaiu]: https://github.com/shaiu +[airzone docs]: /integrations/airzone/ +[apple_tv docs]: /integrations/apple_tv/ +[blueprint docs]: /integrations/blueprint/ +[cast docs]: /integrations/cast/ +[compensation docs]: /integrations/compensation/ +[devolo_home_control docs]: /integrations/devolo_home_control/ +[iqvia docs]: /integrations/iqvia/ +[lutron_caseta docs]: /integrations/lutron_caseta/ +[meater docs]: /integrations/meater/ +[nam docs]: /integrations/nam/ +[opencv docs]: /integrations/opencv/ +[rachio docs]: /integrations/rachio/ +[sabnzbd docs]: /integrations/sabnzbd/ +[samsungtv docs]: /integrations/samsungtv/ +[tensorflow docs]: /integrations/tensorflow/ +[trend docs]: /integrations/trend/ + +## Release 2022.5.2 - May 6 + +- Upgrade glances_api to 0.3.5 ([@difelice] - [#71243]) ([glances docs]) +- Fix Canary camera stream blocking call ([@0bmay] - [#71369]) ([canary docs]) +- Update Zigpy attribute cache for switch devices that do not report state ([@dmulcahey] - [#71417]) ([zha docs]) +- Stringify enums in selectors ([@balloob] - [#71441]) ([blueprint docs]) + +[#71243]: https://github.com/home-assistant/core/pull/71243 +[#71369]: https://github.com/home-assistant/core/pull/71369 +[#71417]: https://github.com/home-assistant/core/pull/71417 +[#71441]: https://github.com/home-assistant/core/pull/71441 +[@0bmay]: https://github.com/0bmay +[@balloob]: https://github.com/balloob +[@difelice]: https://github.com/difelice +[@dmulcahey]: https://github.com/dmulcahey +[blueprint docs]: /integrations/blueprint/ +[canary docs]: /integrations/canary/ +[glances docs]: /integrations/glances/ +[zha docs]: /integrations/zha/ + +## Release 2022.5.3 - May 8 + +- Move flexit climate to HVAC action ([@balloob] - [#71443]) ([flexit docs]) +- Fix display of multiline queries in sql config flow ([@bdraco] - [#71450]) ([sql docs]) +- Ensure sql sensors keep working after using the options flow ([@bdraco] - [#71453]) ([sql docs]) +- Fix rgb conversion in fibaro light ([@rappenze] - [#71476]) ([fibaro docs]) +- Revert usage of Fibaro Client V5 as it has too many errors ([@rappenze] - [#71477]) ([fibaro docs]) +- Update py-canary to 0.5.2 ([@0bmay] - [#71489]) ([canary docs]) +- bump total_connect_client to 2022.5 ([@austinmroczek] - [#71493]) ([totalconnect docs]) +- Add timeout ([@bieniu] - [#71499]) ([brother docs]) +- Add Ukraine Alarm integration ([@PaulAnnekov] - [#71501]) ([ukraine_alarm docs]) (new-integration) +- fix speed sensor wrong number ([@shaiu] - [#71502]) ([sabnzbd docs]) +- Bump frontend to 20220504.1 ([@balloob] - [#71504]) ([frontend docs]) +- Fix other enums in helpers ([@balloob] - [#71505]) + +[#71443]: https://github.com/home-assistant/core/pull/71443 +[#71450]: https://github.com/home-assistant/core/pull/71450 +[#71453]: https://github.com/home-assistant/core/pull/71453 +[#71476]: https://github.com/home-assistant/core/pull/71476 +[#71477]: https://github.com/home-assistant/core/pull/71477 +[#71489]: https://github.com/home-assistant/core/pull/71489 +[#71493]: https://github.com/home-assistant/core/pull/71493 +[#71499]: https://github.com/home-assistant/core/pull/71499 +[#71501]: https://github.com/home-assistant/core/pull/71501 +[#71502]: https://github.com/home-assistant/core/pull/71502 +[#71504]: https://github.com/home-assistant/core/pull/71504 +[#71505]: https://github.com/home-assistant/core/pull/71505 +[@0bmay]: https://github.com/0bmay +[@PaulAnnekov]: https://github.com/PaulAnnekov +[@austinmroczek]: https://github.com/austinmroczek +[@balloob]: https://github.com/balloob +[@bdraco]: https://github.com/bdraco +[@bieniu]: https://github.com/bieniu +[@rappenze]: https://github.com/rappenze +[@shaiu]: https://github.com/shaiu +[brother docs]: /integrations/brother/ +[canary docs]: /integrations/canary/ +[fibaro docs]: /integrations/fibaro/ +[flexit docs]: /integrations/flexit/ +[frontend docs]: /integrations/frontend/ +[sabnzbd docs]: /integrations/sabnzbd/ +[sql docs]: /integrations/sql/ +[totalconnect docs]: /integrations/totalconnect/ +[ukraine_alarm docs]: /integrations/ukraine_alarm/ +**** +## Need help? Join the community! + +Home Assistant has a great community of users who are all more than willing +to help each other out. So, join us! + +Our very active [Discord chat server](/join-chat) is an excellent place to be +at, and don't forget to join our amazing [forums](https://community.home-assistant.io/). + +Found a bug or issue? Please report it in our [issue tracker](https://github.com/home-assistant/core/issues), +to get it fixed! Or, check [our help page](/help) for guidance for more +places you can go. + +Are you more into email? [Sign-up for our Building the Open Home Newsletter](/newsletter) +to get the latest news about features, things happening in our community and +other news about building an Open Home; straight into your inbox. + +## Breaking Changes + +Below is a listing of the breaking change for this release, per subject or +integration. Click on one of those to read more about the breaking change +for that specific item. + +{% details "Configuration Menu" %} + +This release contains several changes to the configuration menu. These are the +most important changes. + +- The `Configuration` menu has been renamed to `Settings`. +- `Helpers` moved to `Devices & Services`. +- `Blueprints` moved to `Automations & Scenes`. +- `Areas` is now grouped with `Zones. +- Dashboard `Resources` moved to overflow menu*. +- A brand new `System` menu housing all system-related settings: + + - The `Restart` button is available in the `System` menu. + - New `Updates` menu, which also now provides the ability to join or leave + the beta channel from the overflow menu*. + - All logs moved to `Logs` (Supervisor, audio, etc). + - `Backups` moved from the Supervisor/Main menu to here. + - `Network` now has all network related settings previously in the General + settings and Supervisor. + - `Storage` provides information about used space, eMMC Lifetime, and also + provides the `Move datadisk` feature in the overflow menu*. + - `Hardware` now has the `Reboot` and `Restart Host` controls, + `Available Hardware` is available in the overflow menu*. + - `System Health` moved to its own menu item in the system menu. + - Processor and memory usage was moved into the new `System Health` menu. + - The integration list with timings, previously shown in the `About` menu, is + moved into the new `System Health` menu. + +Additionally, the developers tools has a brand new `YAML` tab, which contains +the buttons and tools to reload and check your YAML configuration. This was +previously known as "Server Controls", but now moved to the developer tools. + +\* The overflow menu is the menu you see when you click on the three vertical + dots in the top right of your screen. + +{% enddetails %} + +{% details "AVM FRITZ!Box Call Monitor" %} + +The previously deprecated YAML configuration of the AVM FRITZ!Box Call Monitor +integration has been removed. + +AVM FRITZ!Box Call Monitor is now configured via the UI, any existing YAML +configuration has been imported in previous releases and can now be safely +removed from your YAML configuration files. + +([@cdce8p] - [#70829]) ([documentation](/integrations/fritzbox_callmonitor)) + +[@cdce8p]: https://github.com/cdce8p +[#70829]: https://github.com/home-assistant/core/pull/70829 + +{% enddetails %} + +{% details "AVM FRITZ!Box Tools" %} + +The binary sensor entity showing that an update is available for the FRITZ!Box +firmware has been deprecated and will be removed in Home Assistant 2022.7. + +The AVM FRITZ!Box Tools integration now provides an `update` entity as a +replacement. + +([@Mask3007] - [#70096]) ([documentation](/integrations/fritz)) + +[@Mask3007]: https://github.com/Mask3007 +[#70096]: https://github.com/home-assistant/core/pull/70096 + +{% enddetails %} + +{% details "BMW Connected Drive" %} + +All `bmw_connected_drive.*` services are removed (deprecated since 2022.2). +Please use the new button entities with the `button.press` service instead. + +([@rikroe] - [#69808]) ([documentation](/integrations/bmw_connected_drive)) + +[@rikroe]: https://github.com/rikroe +[#69808]: https://github.com/home-assistant/core/pull/69808 + +--- + +The `button.