diff --git a/CODEOWNERS b/CODEOWNERS index 61bdbd84d02..e3e44e5729d 100644 --- a/CODEOWNERS +++ b/CODEOWNERS @@ -151,6 +151,7 @@ source/_integrations/geonetnz_volcano.markdown @exxamalte source/_integrations/gios.markdown @bieniu source/_integrations/gitter.markdown @fabaff source/_integrations/glances.markdown @fabaff @engrbm87 +source/_integrations/goalzero.markdown @tkdrob source/_integrations/gogogate2.markdown @vangorra source/_integrations/google_assistant.markdown @home-assistant/cloud source/_integrations/google_cloud.markdown @lufton @@ -162,6 +163,7 @@ source/_integrations/group.markdown @home-assistant/core source/_integrations/growatt_server.markdown @indykoning source/_integrations/guardian.markdown @bachya source/_integrations/harmony.markdown @ehendrix23 @bramkragten @bdraco +source/_integrations/hdmi_cec.markdown @newAM source/_integrations/heatmiser.markdown @andylockran source/_integrations/heos.markdown @andrewsayre source/_integrations/here_travel_time.markdown @eifinger @@ -186,6 +188,7 @@ source/_integrations/humidifier.markdown @home-assistant/core @Shulyaka source/_integrations/hunterdouglas_powerview.markdown @bdraco source/_integrations/hvv_departures.markdown @vigonotion source/_integrations/hydrawise.markdown @ptcryan +source/_integrations/hyperion.markdown @dermotduffy source/_integrations/iammeter.markdown @lewei50 source/_integrations/iaqualink.markdown @flz source/_integrations/icloud.markdown @Quentame @@ -217,7 +220,7 @@ source/_integrations/keenetic_ndms2.markdown @foxel source/_integrations/kef.markdown @basnijholt source/_integrations/keyboard_remote.markdown @bendavid source/_integrations/knx.markdown @Julius2342 @farmio @marvin-w -source/_integrations/kodi.markdown @OnFreund +source/_integrations/kodi.markdown @OnFreund @cgtobi source/_integrations/konnected.markdown @heythisisnate @kit-klein source/_integrations/lametric.markdown @robbiet480 source/_integrations/launch_library.markdown @ludeeus @@ -228,7 +231,7 @@ source/_integrations/local_ip.markdown @issacg source/_integrations/logger.markdown @home-assistant/core source/_integrations/logi_circle.markdown @evanjd source/_integrations/loopenergy.markdown @pavoni -source/_integrations/luci.markdown @fbradyirl @mzdrale +source/_integrations/luci.markdown @mzdrale source/_integrations/luftdaten.markdown @fabaff source/_integrations/lupusec.markdown @majuss source/_integrations/lutron.markdown @JonGilmore @@ -251,7 +254,7 @@ source/_integrations/min_max.markdown @fabaff source/_integrations/minecraft_server.markdown @elmurato source/_integrations/minio.markdown @tkislan source/_integrations/mobile_app.markdown @robbiet480 -source/_integrations/modbus.markdown @adamchengtkc @janiversen +source/_integrations/modbus.markdown @adamchengtkc @janiversen @vzahradnik source/_integrations/monoprice.markdown @etsinko @OnFreund source/_integrations/moon.markdown @fabaff source/_integrations/mpd.markdown @fabaff @@ -290,6 +293,7 @@ source/_integrations/nzbget.markdown @chriscla source/_integrations/obihai.markdown @dshokouhi source/_integrations/ohmconnect.markdown @robbiet480 source/_integrations/ombi.markdown @larssont +source/_integrations/omnilogic.markdown @oliver84 @djtimca @gentoosu source/_integrations/onboarding.markdown @home-assistant/core source/_integrations/onewire.markdown @garbled1 source/_integrations/onvif.markdown @hunterjm @@ -339,6 +343,7 @@ source/_integrations/raincloud.markdown @vanstinator source/_integrations/rainforest_eagle.markdown @gtdiehl @jcalbert source/_integrations/rainmachine.markdown @bachya source/_integrations/random.markdown @fabaff +source/_integrations/rejseplanen.markdown @DarkFox source/_integrations/repetier.markdown @MTrab source/_integrations/rfxtrx.markdown @danielhiversen @elupus source/_integrations/ring.markdown @balloob @@ -347,6 +352,7 @@ source/_integrations/rmvtransport.markdown @cgtobi source/_integrations/roku.markdown @ctalkington source/_integrations/roomba.markdown @pschmitt @cyr-ius @shenxn source/_integrations/roon.markdown @pavoni +source/_integrations/rpi_power.markdown @shenxn @swetoast source/_integrations/safe_mode.markdown @home-assistant/core source/_integrations/saj.markdown @fredericvl source/_integrations/salt.markdown @bjornorri @@ -389,9 +395,11 @@ source/_integrations/soma.markdown @ratsept source/_integrations/somfy.markdown @tetienne source/_integrations/sonarr.markdown @ctalkington source/_integrations/songpal.markdown @rytilahti @shenxn +source/_integrations/sonos.markdown @cgtobi source/_integrations/spaceapi.markdown @fabaff 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/squeezebox.markdown @rajlaud @@ -411,7 +419,7 @@ source/_integrations/switchbot.markdown @danielhiversen source/_integrations/switcher_kis.markdown @tomerfi source/_integrations/switchmate.markdown @danielhiversen source/_integrations/syncthru.markdown @nielstron -source/_integrations/synology_dsm.markdown @ProtoThis @Quentame +source/_integrations/synology_dsm.markdown @hacf-fr @Quentame source/_integrations/synology_srm.markdown @aerialls source/_integrations/syslog.markdown @fabaff source/_integrations/tado.markdown @michaelarnauts @bdraco diff --git a/Gemfile.lock b/Gemfile.lock index eb6b6400e3b..5ad61fadc5d 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -86,7 +86,7 @@ GEM rb-inotify (0.10.1) ffi (~> 1.0) rexml (3.2.4) - rouge (3.23.0) + rouge (3.24.0) ruby-enum (0.8.0) i18n ruby2_keywords (0.0.2) @@ -109,7 +109,7 @@ GEM tilt (2.0.10) tzinfo (2.0.2) concurrent-ruby (~> 1.0) - tzinfo-data (1.2020.1) + tzinfo-data (1.2020.3) tzinfo (>= 1.0.0) unicode-display_width (1.7.0) diff --git a/_config.yml b/_config.yml index 00b16da8cc7..d5494fa77e9 100644 --- a/_config.yml +++ b/_config.yml @@ -99,9 +99,9 @@ social: # Home Assistant release details current_major_version: 0 -current_minor_version: 115 -current_patch_version: 6 -date_released: 2020-09-30 +current_minor_version: 116 +current_patch_version: 4 +date_released: 2020-10-15 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/package-lock.json b/package-lock.json index 4f49740717a..e9e1574d266 100644 --- a/package-lock.json +++ b/package-lock.json @@ -605,11 +605,14 @@ "integrity": "sha512-KmU+kGi7vG5toUhNdLHHPxyVN1mNGcjMVe1tNDEXT1wU/3oqA96bunElrROWHYw5iNt1QVRaIAtNeMVyzyAdVA==", "dev": true }, - "@types/color-name": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/@types/color-name/-/color-name-1.1.1.tgz", - "integrity": "sha512-rr+OQyAjxze7GgWrSaJwydHStIhHq2lvY3BOC2Mj7KnzI7XK0Uw1TOOdI9lDoajEbSWLiYgoo4f1R51erQfhPQ==", - "dev": true + "@types/mdast": { + "version": "3.0.3", + "resolved": "https://registry.npmjs.org/@types/mdast/-/mdast-3.0.3.tgz", + "integrity": "sha512-SXPBMnFVQg1s00dlMCc/jCdvPqdE4mXaMMCeRlxLDmTAEoegHT53xKtkDnzDTOcmMHUfcjyf36/YYZ6SxRdnsw==", + "dev": true, + "requires": { + "@types/unist": "*" + } }, "@types/unist": { "version": "2.0.3", @@ -648,12 +651,11 @@ "dev": true }, "ansi-styles": { - "version": "4.2.1", - "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.2.1.tgz", - "integrity": "sha512-9VGjrMsG1vePxcSweQsN20KY/c4zN0h9fLjqAbwbPfahM3t+NL+M9HC8xeXG2I8pX5NoamTGNuomEUFI7fcUjA==", + "version": "4.3.0", + "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz", + "integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==", "dev": true, "requires": { - "@types/color-name": "^1.1.1", "color-convert": "^2.0.1" } }, @@ -731,12 +733,6 @@ "integrity": "sha512-L28STB170nwWS63UjtlEOE3dldQApaJXZkOI1uMFfzf3rRuPegHaHesyee+YxQ+W6SvRDQV6UrdOdRiR153wJg==", "dev": true }, - "ccount": { - "version": "1.0.5", - "resolved": "https://registry.npmjs.org/ccount/-/ccount-1.0.5.tgz", - "integrity": "sha512-MOli1W+nfbPLlKEhInaxhRdp7KVLFxLN5ykwzHgLsLI3H3gs5jjFAK4Eoj3OzzcxCtumDaI8onoVDeQyWaNTkw==", - "dev": true - }, "chalk": { "version": "3.0.0", "resolved": "https://registry.npmjs.org/chalk/-/chalk-3.0.0.tgz", @@ -778,9 +774,9 @@ "dev": true }, "chokidar": { - "version": "3.4.1", - "resolved": "https://registry.npmjs.org/chokidar/-/chokidar-3.4.1.tgz", - "integrity": "sha512-TQTJyr2stihpC4Sya9hs2Xh+O2wf+igjL36Y75xx2WdHuiICcn/XJza46Jwt0eT5hVpQOzo3FpY3cj3RVYLX0g==", + "version": "3.4.3", + "resolved": "https://registry.npmjs.org/chokidar/-/chokidar-3.4.3.tgz", + "integrity": "sha512-DtM3g7juCXQxFVSNPNByEC2+NImtBuxQQvWlHunpJIS5Ocr0lG306cC7FCi7cEA0fzmybPUIl4txBIobk1gGOQ==", "dev": true, "requires": { "anymatch": "~3.1.1", @@ -790,7 +786,7 @@ "is-binary-path": "~2.1.0", "is-glob": "~4.0.1", "normalize-path": "~3.0.0", - "readdirp": "~3.4.0" + "readdirp": "~3.5.0" } }, "co": { @@ -1175,12 +1171,6 @@ "integrity": "sha512-eEMa6MKpHFzw38eKm56iNNi6GJ7lf6aLLio7Kr23sJPAECscgRtZvOBYybejWDQ2bM949Y++61PY+udzj5QMLA==", "dev": true }, - "is-alphanumeric": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/is-alphanumeric/-/is-alphanumeric-1.0.0.tgz", - "integrity": "sha1-Spzvcdr0wAHB2B1j0UDPU/1oifQ=", - "dev": true - }, "is-alphanumerical": { "version": "1.0.3", "resolved": "https://registry.npmjs.org/is-alphanumerical/-/is-alphanumerical-1.0.3.tgz", @@ -1351,6 +1341,12 @@ "integrity": "sha512-mrqyZKfX5EhL7hvqcV6WG1yYjnjeuYDzDhhcAAUrq8Po85NBQBJP+ZDUT75qZQ98IkUoBqdkExkukOU7Ts2wrw==", "dev": true }, + "json-parse-even-better-errors": { + "version": "2.3.1", + "resolved": "https://registry.npmjs.org/json-parse-even-better-errors/-/json-parse-even-better-errors-2.3.1.tgz", + "integrity": "sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w==", + "dev": true + }, "json-stable-stringify": { "version": "1.0.1", "resolved": "https://registry.npmjs.org/json-stable-stringify/-/json-stable-stringify-1.0.1.tgz", @@ -1561,15 +1557,6 @@ "integrity": "sha512-WWC0ZuMzCyDHYCasEGs4IPvLyTGftYwh6wIEOULOF0HXcqZlhwRzrK0w2VUlxWA98xnvb/jszw4ZSkJ6ADpM6Q==", "dev": true }, - "markdown-table": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/markdown-table/-/markdown-table-2.0.0.tgz", - "integrity": "sha512-Ezda85ToJUBhM6WGaG6veasyym+Tbs3cMAw/ZhOPqXiYsr0jgocBV3j3nx+4lk47plLlIqjwuTm/ywVI+zjJ/A==", - "dev": true, - "requires": { - "repeat-string": "^1.0.0" - } - }, "md5": { "version": "2.2.1", "resolved": "https://registry.npmjs.org/md5/-/md5-2.2.1.tgz", @@ -1595,40 +1582,30 @@ "integrity": "sha512-vTFXtmbbF3rgnTh3Zl3irso4LtvwUq/jaDvT2D1JqTGAwaipcS7RpTxzi6KjoRqI9n2yuAhzLDAC8xVTF3XYVQ==", "dev": true }, - "mdast-util-compact": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/mdast-util-compact/-/mdast-util-compact-2.0.1.tgz", - "integrity": "sha512-7GlnT24gEwDrdAwEHrU4Vv5lLWrEer4KOkAiKT9nYstsTad7Oc1TwqT2zIMKRdZF7cTuaf+GA1E4Kv7jJh8mPA==", + "mdast-util-from-markdown": { + "version": "0.8.1", + "resolved": "https://registry.npmjs.org/mdast-util-from-markdown/-/mdast-util-from-markdown-0.8.1.tgz", + "integrity": "sha512-qJXNcFcuCSPqUF0Tb0uYcFDIq67qwB3sxo9RPdf9vG8T90ViKnksFqdB/Coq2a7sTnxL/Ify2y7aIQXDkQFH0w==", "dev": true, "requires": { - "unist-util-visit": "^2.0.0" + "@types/mdast": "^3.0.0", + "mdast-util-to-string": "^1.0.0", + "micromark": "~2.10.0", + "parse-entities": "^2.0.0" }, "dependencies": { - "unist-util-is": { - "version": "4.0.2", - "resolved": "https://registry.npmjs.org/unist-util-is/-/unist-util-is-4.0.2.tgz", - "integrity": "sha512-Ofx8uf6haexJwI1gxWMGg6I/dLnF2yE+KibhD3/diOqY2TinLcqHXCV6OI5gFVn3xQqDH+u0M625pfKwIwgBKQ==", - "dev": true - }, - "unist-util-visit": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/unist-util-visit/-/unist-util-visit-2.0.3.tgz", - "integrity": "sha512-iJ4/RczbJMkD0712mGktuGpm/U4By4FfDonL7N/9tATGIF4imikjOuagyMY53tnZq3NP6BcmlrHhEKAfGWjh7Q==", + "parse-entities": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/parse-entities/-/parse-entities-2.0.0.tgz", + "integrity": "sha512-kkywGpCcRYhqQIchaWqZ875wzpS/bMKhz5HnN3p7wveJTkTtyAB/AlnS0f8DFSqYW1T82t6yEAkEcB+A1I3MbQ==", "dev": true, "requires": { - "@types/unist": "^2.0.0", - "unist-util-is": "^4.0.0", - "unist-util-visit-parents": "^3.0.0" - } - }, - "unist-util-visit-parents": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/unist-util-visit-parents/-/unist-util-visit-parents-3.1.0.tgz", - "integrity": "sha512-0g4wbluTF93npyPrp/ymd3tCDTMnP0yo2akFD2FIBAYXq/Sga3lwaU1D8OYKbtpioaI6CkDcQ6fsMnmtzt7htw==", - "dev": true, - "requires": { - "@types/unist": "^2.0.0", - "unist-util-is": "^4.0.0" + "character-entities": "^1.0.0", + "character-entities-legacy": "^1.0.0", + "character-reference-invalid": "^1.0.0", + "is-alphanumerical": "^1.0.0", + "is-decimal": "^1.0.0", + "is-hexadecimal": "^1.0.0" } } } @@ -1642,6 +1619,69 @@ "micromark-extension-frontmatter": "^0.2.0" } }, + "mdast-util-to-markdown": { + "version": "0.5.1", + "resolved": "https://registry.npmjs.org/mdast-util-to-markdown/-/mdast-util-to-markdown-0.5.1.tgz", + "integrity": "sha512-7WS59irdm7lwd8iyfu+kLF+ktfzlvxLJzI/SwysF1EFFGpkU/G60Q61k7xZ420gsMVkXZ3MlcL3bTYCz5QwDeg==", + "dev": true, + "requires": { + "@types/unist": "^2.0.0", + "longest-streak": "^2.0.0", + "mdast-util-to-string": "^1.0.0", + "parse-entities": "^2.0.0", + "repeat-string": "^1.0.0", + "stringify-entities": "^3.0.0", + "zwitch": "^1.0.0" + }, + "dependencies": { + "parse-entities": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/parse-entities/-/parse-entities-2.0.0.tgz", + "integrity": "sha512-kkywGpCcRYhqQIchaWqZ875wzpS/bMKhz5HnN3p7wveJTkTtyAB/AlnS0f8DFSqYW1T82t6yEAkEcB+A1I3MbQ==", + "dev": true, + "requires": { + "character-entities": "^1.0.0", + "character-entities-legacy": "^1.0.0", + "character-reference-invalid": "^1.0.0", + "is-alphanumerical": "^1.0.0", + "is-decimal": "^1.0.0", + "is-hexadecimal": "^1.0.0" + } + } + } + }, + "mdast-util-to-string": { + "version": "1.1.0", + "resolved": "https://registry.npmjs.org/mdast-util-to-string/-/mdast-util-to-string-1.1.0.tgz", + "integrity": "sha512-jVU0Nr2B9X3MU4tSK7JP1CMkSvOj7X5l/GboG1tKRw52lLF1x2Ju92Ms9tNetCcbfX3hzlM73zYo2NKkWSfF/A==", + "dev": true + }, + "micromark": { + "version": "2.10.1", + "resolved": "https://registry.npmjs.org/micromark/-/micromark-2.10.1.tgz", + "integrity": "sha512-fUuVF8sC1X7wsCS29SYQ2ZfIZYbTymp0EYr6sab3idFjigFFjGa5UwoniPlV9tAgntjuapW1t9U+S0yDYeGKHQ==", + "dev": true, + "requires": { + "debug": "^4.0.0", + "parse-entities": "^2.0.0" + }, + "dependencies": { + "parse-entities": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/parse-entities/-/parse-entities-2.0.0.tgz", + "integrity": "sha512-kkywGpCcRYhqQIchaWqZ875wzpS/bMKhz5HnN3p7wveJTkTtyAB/AlnS0f8DFSqYW1T82t6yEAkEcB+A1I3MbQ==", + "dev": true, + "requires": { + "character-entities": "^1.0.0", + "character-entities-legacy": "^1.0.0", + "character-reference-invalid": "^1.0.0", + "is-alphanumerical": "^1.0.0", + "is-decimal": "^1.0.0", + "is-hexadecimal": "^1.0.0" + } + } + } + }, "micromark-extension-frontmatter": { "version": "0.2.2", "resolved": "https://registry.npmjs.org/micromark-extension-frontmatter/-/micromark-extension-frontmatter-0.2.2.tgz", @@ -1996,9 +2036,9 @@ } }, "readdirp": { - "version": "3.4.0", - "resolved": "https://registry.npmjs.org/readdirp/-/readdirp-3.4.0.tgz", - "integrity": "sha512-0xe001vZBnJEK+uKcj8qOhyAKPzIT+gStxWr3LCB0DwcXR5NZJ3IaC+yGnHCYzB/S7ov3m3EEbZI2zeNvX+hGQ==", + "version": "3.5.0", + "resolved": "https://registry.npmjs.org/readdirp/-/readdirp-3.5.0.tgz", + "integrity": "sha512-cMhu7c/8rdhkHXWsY+osBhfSy0JikwpHK/5+imo+LpeasTF8ouErHrlYkwT0++njiyuDvc7OFY5T3ukvZ8qmFQ==", "dev": true, "requires": { "picomatch": "^2.2.1" @@ -2015,24 +2055,24 @@ } }, "remark": { - "version": "12.0.1", - "resolved": "https://registry.npmjs.org/remark/-/remark-12.0.1.tgz", - "integrity": "sha512-gS7HDonkdIaHmmP/+shCPejCEEW+liMp/t/QwmF0Xt47Rpuhl32lLtDV1uKWvGoq+kxr5jSgg5oAIpGuyULjUw==", + "version": "13.0.0", + "resolved": "https://registry.npmjs.org/remark/-/remark-13.0.0.tgz", + "integrity": "sha512-HDz1+IKGtOyWN+QgBiAT0kn+2s6ovOxHyPAFGKVE81VSzJ+mq7RwHFledEvB5F1p4iJvOah/LOKdFuzvRnNLCA==", "dev": true, "requires": { - "remark-parse": "^8.0.0", - "remark-stringify": "^8.0.0", - "unified": "^9.0.0" + "remark-parse": "^9.0.0", + "remark-stringify": "^9.0.0", + "unified": "^9.1.0" } }, "remark-cli": { - "version": "8.0.1", - "resolved": "https://registry.npmjs.org/remark-cli/-/remark-cli-8.0.1.tgz", - "integrity": "sha512-UaYeFI5qUAzkthUd8/MLBQD5OKM6jLN8GRvF6v+KF7xO/i1jQ+X2VqUSQAxWFYxZ8R25gM56GVjeoKOZ0EIr8A==", + "version": "9.0.0", + "resolved": "https://registry.npmjs.org/remark-cli/-/remark-cli-9.0.0.tgz", + "integrity": "sha512-y6kCXdwZoMoh0Wo4Och1tDW50PmMc86gW6GpF08v9d+xUCEJE2wwXdQ+TnTaUamRnfFdU+fE+eNf2PJ53cyq8g==", "dev": true, "requires": { "markdown-extensions": "^1.1.0", - "remark": "^12.0.0", + "remark": "^13.0.0", "unified-args": "^8.0.0" } }, @@ -2047,9 +2087,9 @@ } }, "remark-lint": { - "version": "7.0.1", - "resolved": "https://registry.npmjs.org/remark-lint/-/remark-lint-7.0.1.tgz", - "integrity": "sha512-caZXo3qhuBxzvq9JSJFVQ/ERDq/6TJVgWn0KDwKOIJCGOuLXfQhby5XttUq+Rn7kLbNMtvwfWHJlte14LpaeXQ==", + "version": "8.0.0", + "resolved": "https://registry.npmjs.org/remark-lint/-/remark-lint-8.0.0.tgz", + "integrity": "sha512-ESI8qJQ/TIRjABDnqoFsTiZntu+FRifZ5fJ77yX63eIDijl/arvmDvT+tAf75/Nm5BFL4R2JFUtkHRGVjzYUsg==", "dev": true, "requires": { "remark-message-control": "^6.0.0" @@ -2147,123 +2187,21 @@ } }, "remark-parse": { - "version": "8.0.3", - "resolved": "https://registry.npmjs.org/remark-parse/-/remark-parse-8.0.3.tgz", - "integrity": "sha512-E1K9+QLGgggHxCQtLt++uXltxEprmWzNfg+MxpfHsZlrddKzZ/hZyWHDbK3/Ap8HJQqYJRXP+jHczdL6q6i85Q==", + "version": "9.0.0", + "resolved": "https://registry.npmjs.org/remark-parse/-/remark-parse-9.0.0.tgz", + "integrity": "sha512-geKatMwSzEXKHuzBNU1z676sGcDcFoChMK38TgdHJNAYfFtsfHDQG7MoJAjs6sgYMqyLduCYWDIWZIxiPeafEw==", "dev": true, "requires": { - "ccount": "^1.0.0", - "collapse-white-space": "^1.0.2", - "is-alphabetical": "^1.0.0", - "is-decimal": "^1.0.0", - "is-whitespace-character": "^1.0.0", - "is-word-character": "^1.0.0", - "markdown-escapes": "^1.0.0", - "parse-entities": "^2.0.0", - "repeat-string": "^1.5.4", - "state-toggle": "^1.0.0", - "trim": "0.0.1", - "trim-trailing-lines": "^1.0.0", - "unherit": "^1.0.4", - "unist-util-remove-position": "^2.0.0", - "vfile-location": "^3.0.0", - "xtend": "^4.0.1" - }, - "dependencies": { - "parse-entities": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/parse-entities/-/parse-entities-2.0.0.tgz", - "integrity": "sha512-kkywGpCcRYhqQIchaWqZ875wzpS/bMKhz5HnN3p7wveJTkTtyAB/AlnS0f8DFSqYW1T82t6yEAkEcB+A1I3MbQ==", - "dev": true, - "requires": { - "character-entities": "^1.0.0", - "character-entities-legacy": "^1.0.0", - "character-reference-invalid": "^1.0.0", - "is-alphanumerical": "^1.0.0", - "is-decimal": "^1.0.0", - "is-hexadecimal": "^1.0.0" - } - }, - "unist-util-is": { - "version": "4.0.2", - "resolved": "https://registry.npmjs.org/unist-util-is/-/unist-util-is-4.0.2.tgz", - "integrity": "sha512-Ofx8uf6haexJwI1gxWMGg6I/dLnF2yE+KibhD3/diOqY2TinLcqHXCV6OI5gFVn3xQqDH+u0M625pfKwIwgBKQ==", - "dev": true - }, - "unist-util-remove-position": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/unist-util-remove-position/-/unist-util-remove-position-2.0.1.tgz", - "integrity": "sha512-fDZsLYIe2uT+oGFnuZmy73K6ZxOPG/Qcm+w7jbEjaFcJgbQ6cqjs/eSPzXhsmGpAsWPkqZM9pYjww5QTn3LHMA==", - "dev": true, - "requires": { - "unist-util-visit": "^2.0.0" - } - }, - "unist-util-visit": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/unist-util-visit/-/unist-util-visit-2.0.3.tgz", - "integrity": "sha512-iJ4/RczbJMkD0712mGktuGpm/U4By4FfDonL7N/9tATGIF4imikjOuagyMY53tnZq3NP6BcmlrHhEKAfGWjh7Q==", - "dev": true, - "requires": { - "@types/unist": "^2.0.0", - "unist-util-is": "^4.0.0", - "unist-util-visit-parents": "^3.0.0" - } - }, - "unist-util-visit-parents": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/unist-util-visit-parents/-/unist-util-visit-parents-3.1.0.tgz", - "integrity": "sha512-0g4wbluTF93npyPrp/ymd3tCDTMnP0yo2akFD2FIBAYXq/Sga3lwaU1D8OYKbtpioaI6CkDcQ6fsMnmtzt7htw==", - "dev": true, - "requires": { - "@types/unist": "^2.0.0", - "unist-util-is": "^4.0.0" - } - }, - "vfile-location": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/vfile-location/-/vfile-location-3.0.1.tgz", - "integrity": "sha512-yYBO06eeN/Ki6Kh1QAkgzYpWT1d3Qln+ZCtSbJqFExPl1S3y2qqotJQXoh6qEvl/jDlgpUJolBn3PItVnnZRqQ==", - "dev": true - } + "mdast-util-from-markdown": "^0.8.0" } }, "remark-stringify": { - "version": "8.1.1", - "resolved": "https://registry.npmjs.org/remark-stringify/-/remark-stringify-8.1.1.tgz", - "integrity": "sha512-q4EyPZT3PcA3Eq7vPpT6bIdokXzFGp9i85igjmhRyXWmPs0Y6/d2FYwUNotKAWyLch7g0ASZJn/KHHcHZQ163A==", + "version": "9.0.0", + "resolved": "https://registry.npmjs.org/remark-stringify/-/remark-stringify-9.0.0.tgz", + "integrity": "sha512-8x29DpTbVzEc6Dwb90qhxCtbZ6hmj3BxWWDpMhA+1WM4dOEGH5U5/GFe3Be5Hns5MvPSFAr1e2KSVtKZkK5nUw==", "dev": true, "requires": { - "ccount": "^1.0.0", - "is-alphanumeric": "^1.0.0", - "is-decimal": "^1.0.0", - "is-whitespace-character": "^1.0.0", - "longest-streak": "^2.0.1", - "markdown-escapes": "^1.0.0", - "markdown-table": "^2.0.0", - "mdast-util-compact": "^2.0.0", - "parse-entities": "^2.0.0", - "repeat-string": "^1.5.4", - "state-toggle": "^1.0.0", - "stringify-entities": "^3.0.0", - "unherit": "^1.0.4", - "xtend": "^4.0.1" - }, - "dependencies": { - "parse-entities": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/parse-entities/-/parse-entities-2.0.0.tgz", - "integrity": "sha512-kkywGpCcRYhqQIchaWqZ875wzpS/bMKhz5HnN3p7wveJTkTtyAB/AlnS0f8DFSqYW1T82t6yEAkEcB+A1I3MbQ==", - "dev": true, - "requires": { - "character-entities": "^1.0.0", - "character-entities-legacy": "^1.0.0", - "character-reference-invalid": "^1.0.0", - "is-alphanumerical": "^1.0.0", - "is-decimal": "^1.0.0", - "is-hexadecimal": "^1.0.0" - } - } + "mdast-util-to-markdown": "^0.5.0" } }, "repeat-string": { @@ -2465,9 +2403,9 @@ } }, "supports-color": { - "version": "7.1.0", - "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-7.1.0.tgz", - "integrity": "sha512-oRSIpR8pxT1Wr2FquTNnGet79b3BWljqOuoW/h4oBhxJ/HUbX5nX6JSruTkvXDCFMwDPvsaTTbvMLKZWSy0R5g==", + "version": "7.2.0", + "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-7.2.0.tgz", + "integrity": "sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==", "dev": true, "requires": { "has-flag": "^4.0.0" @@ -2747,9 +2685,9 @@ } }, "unified": { - "version": "9.0.0", - "resolved": "https://registry.npmjs.org/unified/-/unified-9.0.0.tgz", - "integrity": "sha512-ssFo33gljU3PdlWLjNp15Inqb77d6JnJSfyplGJPT/a+fNRNyCBeveBAYJdO5khKdF6WVHa/yYCC7Xl6BDwZUQ==", + "version": "9.2.0", + "resolved": "https://registry.npmjs.org/unified/-/unified-9.2.0.tgz", + "integrity": "sha512-vx2Z0vY+a3YoTj8+pttM3tiJHCwY5UFbYdiWrwBEbHmK8pvsPj2rtAX2BFfgXen8T39CJWblWRDT4L5WGXtDdg==", "dev": true, "requires": { "bail": "^1.0.0", @@ -2802,14 +2740,14 @@ }, "dependencies": { "parse-json": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/parse-json/-/parse-json-5.0.0.tgz", - "integrity": "sha512-OOY5b7PAEFV0E2Fir1KOkxchnZNCdowAJgQ5NuxjpBKTRP3pQhwkrkxqQjeoKJ+fO7bCpmIZaogI4eZGDMEGOw==", + "version": "5.1.0", + "resolved": "https://registry.npmjs.org/parse-json/-/parse-json-5.1.0.tgz", + "integrity": "sha512-+mi/lmVVNKFNVyLXV31ERiy2CY5E1/F6QtJFEzoChPRwwngMNXRDQ9GJ5WdE2Z2P4AujsOi0/+2qHID68KwfIQ==", "dev": true, "requires": { "@babel/code-frame": "^7.0.0", "error-ex": "^1.3.1", - "json-parse-better-errors": "^1.0.1", + "json-parse-even-better-errors": "^2.3.0", "lines-and-columns": "^1.1.6" } } @@ -2841,9 +2779,9 @@ "dev": true }, "unist-util-visit": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/unist-util-visit/-/unist-util-visit-2.0.2.tgz", - "integrity": "sha512-HoHNhGnKj6y+Sq+7ASo2zpVdfdRifhTgX2KTU3B/sO/TTlZchp7E3S4vjRzDJ7L60KmrCPsQkVK3lEF3cz36XQ==", + "version": "2.0.3", + "resolved": "https://registry.npmjs.org/unist-util-visit/-/unist-util-visit-2.0.3.tgz", + "integrity": "sha512-iJ4/RczbJMkD0712mGktuGpm/U4By4FfDonL7N/9tATGIF4imikjOuagyMY53tnZq3NP6BcmlrHhEKAfGWjh7Q==", "dev": true, "requires": { "@types/unist": "^2.0.0", @@ -2852,9 +2790,9 @@ } }, "unist-util-visit-parents": { - "version": "3.0.2", - "resolved": "https://registry.npmjs.org/unist-util-visit-parents/-/unist-util-visit-parents-3.0.2.tgz", - "integrity": "sha512-yJEfuZtzFpQmg1OSCyS9M5NJRrln/9FbYosH3iW0MG402QbdbaB8ZESwUv9RO6nRfLAKvWcMxCwdLWOov36x/g==", + "version": "3.1.0", + "resolved": "https://registry.npmjs.org/unist-util-visit-parents/-/unist-util-visit-parents-3.1.0.tgz", + "integrity": "sha512-0g4wbluTF93npyPrp/ymd3tCDTMnP0yo2akFD2FIBAYXq/Sga3lwaU1D8OYKbtpioaI6CkDcQ6fsMnmtzt7htw==", "dev": true, "requires": { "@types/unist": "^2.0.0", @@ -2862,9 +2800,9 @@ } }, "vfile-location": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/vfile-location/-/vfile-location-3.0.1.tgz", - "integrity": "sha512-yYBO06eeN/Ki6Kh1QAkgzYpWT1d3Qln+ZCtSbJqFExPl1S3y2qqotJQXoh6qEvl/jDlgpUJolBn3PItVnnZRqQ==", + "version": "3.1.0", + "resolved": "https://registry.npmjs.org/vfile-location/-/vfile-location-3.1.0.tgz", + "integrity": "sha512-FCZ4AN9xMcjFIG1oGmZKo61PjwJHRVA+0/tPUP2ul4uIwjGGndIxavEMRpWn5p4xwm/ZsdXp9YNygf1ZyE4x8g==", "dev": true } } @@ -2955,9 +2893,9 @@ } }, "vfile": { - "version": "4.1.1", - "resolved": "https://registry.npmjs.org/vfile/-/vfile-4.1.1.tgz", - "integrity": "sha512-lRjkpyDGjVlBA7cDQhQ+gNcvB1BGaTHYuSOcY3S7OhDmBtnzX95FhtZZDecSTDm6aajFymyve6S5DN4ZHGezdQ==", + "version": "4.2.0", + "resolved": "https://registry.npmjs.org/vfile/-/vfile-4.2.0.tgz", + "integrity": "sha512-a/alcwCvtuc8OX92rqqo7PflxiCgXRFjdyoGVuYV+qbgCb0GgZJRvIgCD4+U/Kl1yhaRsaTwksF88xbPyGsgpw==", "dev": true, "requires": { "@types/unist": "^2.0.0", @@ -3074,6 +3012,12 @@ "resolved": "https://registry.npmjs.org/xtend/-/xtend-4.0.2.tgz", "integrity": "sha512-LKYU1iAXJXUgAXn9URjiu+MWhyUXHsvfp7mcuYm9dSUKK0/CjtrUwFAxD82/mCWbtLsGjFIad0wIsod4zrTAEQ==", "dev": true + }, + "zwitch": { + "version": "1.0.5", + "resolved": "https://registry.npmjs.org/zwitch/-/zwitch-1.0.5.tgz", + "integrity": "sha512-V50KMwwzqJV0NpZIZFwfOD5/lyny3WlSzRiXgA0G7VUnRlqttta1L6UQIHzd6EuBY/cHGfwTIck7w1yH6Q5zUw==", + "dev": true } } } diff --git a/package.json b/package.json index f261532d4bd..2c9d1a4c804 100644 --- a/package.json +++ b/package.json @@ -4,12 +4,12 @@ "version": "1.0.0", "dependencies": {}, "devDependencies": { - "remark-cli": "^8.0.1", + "remark-cli": "^9.0.0", "remark-frontmatter": "^3.0.0", - "remark-lint": "^7.0.1", + "remark-lint": "^8.0.0", "remark-lint-fenced-code-flag": "^2.0.1", "remark-lint-no-shell-dollars": "^2.0.2", - "remark-stringify": "^8.1.1", + "remark-stringify": "^9.0.0", "textlint": "^11.7.6", "textlint-rule-common-misspellings": "^1.0.1", "textlint-rule-terminology": "^2.1.4" diff --git a/sass/custom/_component_page.scss b/sass/custom/_component_page.scss index c52b3dc6107..1b337c6d226 100644 --- a/sass/custom/_component_page.scss +++ b/sass/custom/_component_page.scss @@ -46,6 +46,10 @@ @media only screen and (min-width: $desk-start) { #components-page { .filter-button-group { + .active { + font-weight: bold; + } + .featured { margin: 12px 0; } diff --git a/source/.well-known/microsoft-identity-association.json b/source/.well-known/microsoft-identity-association.json new file mode 100644 index 00000000000..deff752e413 --- /dev/null +++ b/source/.well-known/microsoft-identity-association.json @@ -0,0 +1,7 @@ +{ + "associatedApplications": [ + { + "applicationId": "1fe091a7-b8e9-49a6-b639-b2d65970a310" + } + ] +} diff --git a/source/_cookbook/notify.mqtt.markdown b/source/_cookbook/notify.mqtt.markdown index 00e08139241..6ddb0d6de35 100644 --- a/source/_cookbook/notify.mqtt.markdown +++ b/source/_cookbook/notify.mqtt.markdown @@ -8,7 +8,7 @@ ha_iot_class: Configurable The MQTT notification support is different than the other [notification](/integrations/notify/) platforms. It is a service. This means that you don't have to create a configuration entry but you need to provide more details when calling the service. -**Call Service** section from the service developer tool icon **Developer Tools** allows you to send MQTT messages. Choose *mqtt.publish* from the list of **Available services:** and enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**. +**Call Service** section from **Developer Tools** -> **Services** allows you to send MQTT messages. Choose *mqtt.publish* from the list of **Available services:** and enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**. ```json {"payload": "Test message from HA", "topic": "home/notification", "qos": 0, "retain": 0} diff --git a/source/_docs/automation.markdown b/source/_docs/automation.markdown index 81844501ffd..6294c48f783 100644 --- a/source/_docs/automation.markdown +++ b/source/_docs/automation.markdown @@ -41,4 +41,4 @@ Automation rules interact directly with the internal state of Home Assistant, so State changes can be used as the source of triggers and the current state can be used in conditions. -Actions are all about calling services. To explore the available services open the Services developer tool. Services allow to change anything. For example turn on a light, run a script or enable a scene. Each service has a domain and a name. For example the service `light.turn_on` is capable of turning on any light in your system. Services can be passed parameters to for example tell which device to turn on or what color to use. +Actions are all about calling services. To explore the available services open the **Developer Tools** -> **Services**. Services allow to change anything. For example turn on a light, run a script or enable a scene. Each service has a domain and a name. For example the service `light.turn_on` is capable of turning on any light in your system. Services can be passed parameters to for example tell which device to turn on or what color to use. diff --git a/source/_docs/automation/templating.markdown b/source/_docs/automation/templating.markdown index c990014489a..fbbec6af4e7 100644 --- a/source/_docs/automation/templating.markdown +++ b/source/_docs/automation/templating.markdown @@ -167,6 +167,7 @@ The following tables show the available trigger data per platform. | `trigger.webhook_id` | The webhook ID that was triggered. | `trigger.json` | The JSON data of the request (if it had a JSON content type). | `trigger.data` | The form data of the request (if it had a form data content type). +| `trigger.query` | The URL query parameters of the request (if provided). ### Zone diff --git a/source/_docs/configuration.markdown b/source/_docs/configuration.markdown index 1c51b041608..b3ef7f15199 100644 --- a/source/_docs/configuration.markdown +++ b/source/_docs/configuration.markdown @@ -41,7 +41,7 @@ The most basic is to use SSH to connect to the system (you may need to install t ## Reloading changes You will have to restart Home Assistant for most changes to `configuration.yaml` to take effect. -You can load changes to [automations](/docs/automation/), [core (customize)](/docs/configuration/customizing-devices/), [groups](/integrations/group/), [input_booleans](/integrations/input_boolean/), [input_datetimes](/integrations/input_datetime/), [input_numbers](/integrations/input_number/), [input_selects](/integrations/input_select/), [input_texts](/integrations/input_text/), [persons](/integrations/person/), [scenes](/integrations/scene/), [scripts](/integrations/script/), [timers](/integrations/timer/), and [zones](/integrations/zone/) without restarting. +You can load changes to [automations](/docs/automation/), [core (customize)](/docs/configuration/customizing-devices/), [groups](/integrations/group/), [history stats](/integrations/history_stats/), [HomeKit](/integrations/homekit/), [input_booleans](/integrations/input_boolean/), [input_datetimes](/integrations/input_datetime/), [input_numbers](/integrations/input_number/), [input_selects](/integrations/input_select/), [input_texts](/integrations/input_text/), [MQTT](/integrations/mqtt/), [persons](/integrations/person/), [scenes](/integrations/scene/), [scripts](/integrations/script/), [statistics](/integrations/statistics/), [template sensors](/integrations/template/), [timers](/integrations/timer/), [zones](/integrations/zone/), and more without restarting.
diff --git a/source/_docs/configuration/basic.markdown b/source/_docs/configuration/basic.markdown index 945880ce404..00b72a9e30f 100644 --- a/source/_docs/configuration/basic.markdown +++ b/source/_docs/configuration/basic.markdown @@ -28,7 +28,7 @@ homeassistant: legacy_templates: false ``` -NOTE: You will not be able to edit anything in Configuration -> General in the UI if you are using YAML configuration for any of the following: name, latitude, longitute, elevation, unit_system, temperature_unit, time_zone, external_url, internal_url. +NOTE: You will not be able to edit anything in Configuration -> General in the UI if you are using YAML configuration for any of the following: name, latitude, longitude, elevation, unit_system, temperature_unit, time_zone, external_url, internal_url. {% configuration %} name: diff --git a/source/_docs/configuration/customizing-devices.markdown b/source/_docs/configuration/customizing-devices.markdown index 21f5ec32f87..4058d7e93db 100644 --- a/source/_docs/configuration/customizing-devices.markdown +++ b/source/_docs/configuration/customizing-devices.markdown @@ -20,7 +20,7 @@ By default, all of your devices will be visible and have a default icon determin ### Customization using the UI -Under the *Configuration* menu you'll find the *Customization* menu. If this menu item is not visible, enable advanced mode on your [profile page](/docs/authentication/#your-account-profile) first. When you select an entity to customize, you'll see all the existing attributes listed and you can customize those or select an additional supported attribute ([see below](/docs/configuration/customizing-devices/#possible-values)). You may also need to add the following to your `configuration.yaml` file, depending when you started using Home Assistant: +Under the *Configuration* menu you'll find the *Customizations* menu. If this menu item is not visible, enable advanced mode on your [profile page](/docs/authentication/#your-account-profile) first. When you select an entity to customize, you'll see all the existing attributes listed and you can customize those or select an additional supported attribute ([see below](/docs/configuration/customizing-devices/#possible-values)). You may also need to add the following to your `configuration.yaml` file, depending when you started using Home Assistant: ```yaml homeassistant: @@ -53,7 +53,7 @@ device_class: type: device_class default: None unit_of_measurement: - description: Defines the units of measurement, if any. This will also influence the graphical presentation in the history visualisation as continuous value. Sensors with missing `unit_of_measurement` are showing as discrete values. + description: Defines the units of measurement, if any. This will also influence the graphical presentation in the history visualization as continuous value. Sensors with missing `unit_of_measurement` are showing as discrete values. required: false type: string default: None diff --git a/source/_docs/configuration/templating.markdown b/source/_docs/configuration/templating.markdown index 89d2928c19c..2adfb527848 100644 --- a/source/_docs/configuration/templating.markdown +++ b/source/_docs/configuration/templating.markdown @@ -438,7 +438,7 @@ The following overview contains a couple of options to get the needed values: {% raw %}{{ value_json.tst | timestamp_custom('%Y' True) }}{% endraw %} ``` -To evaluate a response, go to the template developer tool icon template developer tools, create your output in "Template", and check the result. +To evaluate a response, go to **Developer Tools** -> **Template**, create your output in "Template editor", and check the result. {% raw %} ```yaml diff --git a/source/_docs/installation.markdown b/source/_docs/installation.markdown index b378aeecb48..8ba3c999d4b 100644 --- a/source/_docs/installation.markdown +++ b/source/_docs/installation.markdown @@ -61,9 +61,9 @@ If you use these install methods, we assume that you know how to manage and admi **Method**|**You have**|**Recommended for** :-----|:-----|:----- -[Home Assistant Core](/docs/installation/raspberry-pi/)|Any Linux, Python 3.7.1 or later|Those familiar with their operating system +[Home Assistant Core](/docs/installation/raspberry-pi/)|Any Linux, Python 3.8 or later|Those familiar with their operating system [Home Assistant Supervised](https://github.com/home-assistant/supervised-installer) | [Requirements](https://github.com/home-assistant/architecture/blob/master/adr/0014-home-assistant-supervised.md#supported-operating-system-system-dependencies-and-versions) | Those very familiar with their operating system -[venv
(as your user)](/docs/installation/virtualenv/)|Any Python 3.7.1 or later|**Developers** +[venv
(as your user)](/docs/installation/virtualenv/)|Any Python 3.8 or later|**Developers** ## Community provided guides diff --git a/source/_docs/installation/docker.markdown b/source/_docs/installation/docker.markdown index b943b08992f..78d5ec0a1cd 100644 --- a/source/_docs/installation/docker.markdown +++ b/source/_docs/installation/docker.markdown @@ -40,13 +40,19 @@ docker rm home-assistant # remove it from Docker's list of containers docker run -d --name="home-assistant" -v /PATH_TO_YOUR_CONFIG:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/home-assistant:stable # finally, start a new one ``` -### Raspberry Pi 3 (Raspberry Pi OS) +### Raspberry Pi 3/4 (Raspberry Pi OS) +Raspberry Pi 3: ```bash docker run --init -d --name="home-assistant" -e "TZ=America/New_York" -v /PATH_TO_YOUR_CONFIG:/config --net=host homeassistant/raspberrypi3-homeassistant:stable ``` -You need to replace `/PATH_TO_YOUR_CONFIG` with your path to the configuration, for example if you choose your configuration path to be `/home/pi/homeassistant`, then command would be: +Raspberry Pi 4: +```bash +docker run --init -d --name="home-assistant" -e "TZ=America/New_York" -v /PATH_TO_YOUR_CONFIG:/config --net=host homeassistant/raspberrypi4-homeassistant:stable +``` + +You need to replace `/PATH_TO_YOUR_CONFIG` with your path to the configuration. For example, if you choose your configuration path to be `/home/pi/homeassistant`, the command for **Raspberry Pi 3** would be: ```bash docker run --init -d --name="home-assistant" -e "TZ=America/New_York" -v /home/pi/homeassistant:/config --net=host homeassistant/raspberrypi3-homeassistant:stable @@ -224,7 +230,7 @@ device_tracker: If you change the configuration you have to restart the server. To do that you have 2 options. - 1. You can go to the service developer tool icon service developer tools, select the service `homeassistant/restart` and click "Call Service". + 1. You can go to the **Developer Tools** -> **Services**, select the service `homeassistant.restart` and click "Call Service". 2. Or you can restart it from a terminal by running `docker restart home-assistant` ## Docker Compose diff --git a/source/_docs/installation/raspberry-pi.markdown b/source/_docs/installation/raspberry-pi.markdown index 953681088aa..d1781b35e1b 100644 --- a/source/_docs/installation/raspberry-pi.markdown +++ b/source/_docs/installation/raspberry-pi.markdown @@ -5,7 +5,7 @@ description: "Instructions to install Home Assistant Core on a Raspberry Pi runn This installation of Home Assistant Core requires the Raspberry Pi to run [Raspberry Pi OS Lite](https://www.raspberrypi.org/downloads/raspberry-pi-os/). The installation will be installed in a [Virtual Environment](/docs/installation/virtualenv) with minimal overhead. Instructions assume this is a new installation of Raspberry Pi OS Lite. -You must have Python 3.7 or later installed (including the package `python3-dev`) which is *not* the case for Raspberry Pi OS Stretch. +You must have Python 3.8 or later installed (including the package `python3-dev`) which is *not* the case for Raspberry Pi OS and you will need to install Python manually.
Although these installation steps specifically mention a Raspberry Pi, you can go ahead and proceed on any Linux install as well. This guide is also referred to as the "Advanced Guide" for a virtual environment install. @@ -40,7 +40,7 @@ sudo apt-get upgrade -y Install the dependencies. ```bash -sudo apt-get install python3 python3-dev python3-venv python3-pip libffi-dev libssl-dev libtiff-dev autoconf build-essential libopenjp2-7 +sudo apt-get install python3 python3-dev python3-venv python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libopenjp2-7 libtiff5 ``` Add an account for Home Assistant Core called `homeassistant`. @@ -63,7 +63,7 @@ Next up is to create and change to a virtual environment for Home Assistant Core ```bash sudo -u homeassistant -H -s cd /srv/homeassistant -python3 -m venv . +python3.8 -m venv . source bin/activate ``` diff --git a/source/_docs/installation/virtualenv.markdown b/source/_docs/installation/virtualenv.markdown index 1512598c527..3676ecf1b26 100644 --- a/source/_docs/installation/virtualenv.markdown +++ b/source/_docs/installation/virtualenv.markdown @@ -3,15 +3,15 @@ title: "Installation in Python virtual environment" description: "How to install Home Assistant in a Python virtual environment." --- -If you already have Python 3.7 or later installed, you can easily give Home Assistant a spin. +If you already have Python 3.8 or later installed, you can easily give Home Assistant a spin. -It's recommended when installing Python packages that you use a [virtual environment](https://docs.python.org/3.7/library/venv.html#module-venv). This will make sure that your Python installation and Home Assistant installation won't impact one another. The following steps will work on most UNIX like systems. +It's recommended when installing Python packages that you use a [virtual environment](https://docs.python.org/3.8/library/venv.html#module-venv). This will make sure that your Python installation and Home Assistant installation won't impact one another. The following steps will work on most UNIX like systems.
This is a generic guide for running Home Assistant under Python. We recommend to use [our recommended installation guides](/docs/installation/#recommended). The steps below may be shorter but some users find difficulty when applying updates and may run into issues. -Before you begin the guide below, ensure that you have a *so-called standard* build environment that includes things like `make`, `gcc`, `python3`, including Python 3 `setuptools` and `pip` modules. Less obvious is the need to install `openssl-dev` (for opensslv.h), `libffi-dev` (for cffi.h) for things to build later on, `libopenjp2-7` and `libtiff5` needed for the frontend. +Before you begin the guide below, ensure that you have a *so-called standard* build environment that includes things like `make`, `gcc`, `python3`, including Python 3 `setuptools` and `pip` modules. Less obvious is the need to install `libssl-dev` (for opensslv.h), `libffi-dev` (for cffi.h) for things to build later on, `libjpeg-dev`, `zlib1g-dev`, `libopenjp2-7` and `libtiff5` needed for the frontend.
@@ -24,7 +24,7 @@ It should not contain any OS specific instructions. 1. Create a virtual environment in your current directory: ```bash - python3 -m venv homeassistant + python3.8 -m venv homeassistant ``` 2. Open the virtual environment: ```bash @@ -106,7 +106,7 @@ Looking for more advanced guides? Check our [Raspberry Pi OS guide](/docs/instal ### After upgrading Python -If you've upgraded Python (for example, you were running 3.7.1 and now you've installed 3.7.3) then you'll need to build a new virtual environment. Simply rename your existing virtual environment directory: +If you've upgraded Python (for example, you were running 3.8.1 and now you've installed 3.8.6) then you'll need to build a new virtual environment. Simply rename your existing virtual environment directory: ```bash mv homeassistant homeassistant.old diff --git a/source/_docs/mqtt/birth_will.markdown b/source/_docs/mqtt/birth_will.markdown index c4cc9b5d939..eec087abdca 100644 --- a/source/_docs/mqtt/birth_will.markdown +++ b/source/_docs/mqtt/birth_will.markdown @@ -4,7 +4,7 @@ description: "Instructions on how to setup MQTT birth and last will messages wit logo: mqtt.png --- -Home Assistant's MQTT integration supports so-called Birth and Last Will and Testament (LWT) messages. The former is used to send a message after the service has started, and the latter is used to notify other clients about a disconnected client. Please note that the LWT message will be sent both in case of a clean (e.g. Home Asisstant shutting down) and in case of an unclean (e.g. Home Assistant crashing or losing its network connection) disconnect. +Home Assistant's MQTT integration supports so-called Birth and Last Will and Testament (LWT) messages. The former is used to send a message after the service has started, and the latter is used to notify other clients about a disconnected client. Please note that the LWT message will be sent both in case of a clean (e.g. Home Assistant shutting down) and in case of an unclean (e.g. Home Assistant crashing or losing its network connection) disconnect. By default, Home Assistant sends `online` and `offline` to `homeassistant/status`. diff --git a/source/_docs/mqtt/broker.markdown b/source/_docs/mqtt/broker.markdown index da3a79fd2c4..68b1ffa595b 100644 --- a/source/_docs/mqtt/broker.markdown +++ b/source/_docs/mqtt/broker.markdown @@ -16,7 +16,9 @@ The recommended setup method is to use the [Mosquitto MQTT broker add-on](https:
-There is [an issue](https://github.com/rabbitmq/rabbitmq-mqtt/issues/154) with the RabbitMQ MQTT Plugin which break MQTT message retention. Don't use the RabbitMQ MQTT plugin, instead use another broker like Mosquitto. +Neither ActiveMQ MQTT broker nor the RabbitMQ MQTT Plugin are supported, use a known working broker like Mosquitto instead. +There are [at least two](https://issues.apache.org/jira/browse/AMQ-6360) [issues](https://issues.apache.org/jira/browse/AMQ-6575) with the ActiveMQ MQTT broker which break MQTT message retention. +There is [an issue](https://github.com/rabbitmq/rabbitmq-mqtt/issues/154) with the RabbitMQ MQTT Plugin which breaks MQTT message retention.
diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown index f1c8043a63d..3c9b06c52dc 100644 --- a/source/_docs/scripts.markdown +++ b/source/_docs/scripts.markdown @@ -64,6 +64,8 @@ Scripts may also use a shortcut syntax for activating scenes instead of calling The variable command allows you to set/override variables that will be accessible by templates in actions after it. +{% raw %} + ```yaml - variables: entities: light.kitchen, light.living_room @@ -75,6 +77,8 @@ The variable command allows you to set/override variables that will be accessibl brightness: "{{ brightness }}" ``` +{% endraw %} + ## Test a Condition While executing a script you can add a condition to stop further execution. When a condition does not return `true`, the script will stop executing. There are many different conditions which are documented at the [conditions page]. diff --git a/source/_docs/z-wave.markdown b/source/_docs/z-wave.markdown index a76eed6860d..9dffc7e31d7 100644 --- a/source/_docs/z-wave.markdown +++ b/source/_docs/z-wave.markdown @@ -19,7 +19,7 @@ The Z-Wave standard was improved with Z-Wave Plus, and if you only use Z-Wave pl ## What do you need to use Z-Wave -There are 2 basic things you'll need to use Z-Wave, a Z-Wave [controller](/docs/z-wave/controllers/) and one or more [devices](/docs/z-wave/devices/). +There are 2 basic things you'll need to use Z-Wave, a Z-Wave [controller](/docs/z-wave/controllers/) and one or more [devices](/docs/z-wave/devices/). ### Regional differences @@ -33,6 +33,6 @@ You can get more information on the [available services](/docs/z-wave/services/) ## Instant status updates -When you toggle a switch or control a light locally you may find that it takes some time for that to be reflected in Home Assistant. That's because Lutron had patents on the status updates using the *Hail* command class, the traditional way of allowing devices to tell the controller that something happened locally. The same result can be achieved through the *Association* command class, or *Central Scene* command class (though, *Central Scene* isn't [fully supported](https://github.com/OpenZWave/open-zwave/pull/1125) in OpenZWave). +When you toggle a switch or control a light locally you may find that it takes some time for that to be reflected in Home Assistant. That's because Lutron had patents on the status updates using the *Hail* command class, the traditional way of allowing devices to tell the controller that something happened locally. The same result can be achieved through the *Association* command class, or *Central Scene* command class (though, *Central Scene* isn't [fully supported](https://github.com/OpenZWave/open-zwave/pull/1125) in OpenZWave). If you search [the Z-Wave products database](https://products.z-wavealliance.org/) for your product and it lists one of those in the **Controlled** command classes (not the **Supported** command classes), then your device will be able to report state changes when they happen. If it doesn't then updates may either happen eventually, or you may need to (carefully) [enable polling](/docs/z-wave/control-panel/#entities-of-this-node). diff --git a/source/_docs/z-wave/adding.markdown b/source/_docs/z-wave/adding.markdown index 6347e5051e8..72becdec805 100644 --- a/source/_docs/z-wave/adding.markdown +++ b/source/_docs/z-wave/adding.markdown @@ -3,6 +3,10 @@ title: "Z-Wave Devices - Adding and Removing" description: "How to add and remove Z-Wave devices." --- +## Recommendation before adding any devices + +Z-Wave devices behave as a mesh and can store network relationship details on the device itself. This means used devices or even brand new devices could already be enrolled in another network, for example, a test network for a brand new device or a previous network for devices that aren't new. This could cause headaches when you're attempting to add/enrol the device to your network. It is recommended that if possible, perform a factory reset AND device perform exclusion or disenroll for the device you're attempting to add to Home Assistant. Steps can found further below on this page under "Removing Devices". + ## Adding Non-Secure Devices To add (include) a non-secure Z-Wave [device](/docs/z-wave/devices/) to your system: @@ -38,7 +42,8 @@ Each individual value in the defined key can be anywhere from 0x00 to 0xFF. Defi ### Network Key -An easy script to generate a random key: +An easy Linux script to generate a random key: +(remember you can run this in Home Assistant OS or Supervised, you can use the Terminal Add-on) ```bash cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g' -e 's/, $//' @@ -77,10 +82,10 @@ Secure devices require additional bandwidth, and too many secure devices can slo To remove (exclude) a Z-Wave device from your system: -1. Go to the Z-Wave control panel in the Home Assistant frontend +1. Go to the Z-Wave control panel in the Home Assistant frontend. (Home Assistant > Configuration > Integrations > Z-Wave > Configure) 2. Click the **Remove Node** button in the *Z-Wave Network Management* card - this will place the controller in exclusion mode 3. Activate your device to be excluded by following the instructions provided with the device -4. The device will now be removed, but that won't show until you restart Home Assistant +4. The device should now be removed, but that won't show until you restart Home Assistant. Look for a confirmation signal on the device if available, or confirm on the Home Assistant logs. 5. Run a *Heal Network* so all the other nodes learn about its removal If your device isn't responding to this process, possibly because you've factory reset it or it has failed, you can remove it using **Remove Failed Node**. This only works for devices marked as `"is_failed": true`, but you can trick the system into thinking that this the case: diff --git a/source/_docs/z-wave/devices.markdown b/source/_docs/z-wave/devices.markdown index d982a2e6204..2a629c2d7e6 100644 --- a/source/_docs/z-wave/devices.markdown +++ b/source/_docs/z-wave/devices.markdown @@ -38,7 +38,7 @@ From 2 April 2017 all newly approved Z-Wave devices will have to support the Sec Your Z-Wave mesh network is built with the devices that are mains powered (whether directly, or via a USB adapter), these relay traffic for other nodes, building the network. These devices are always awake and you can query them, or send configuration changes, at any time. -Battery powered devices spend most of their time asleep, unable to relay traffic, to be queried, or receive changes. Changes sent while a device is asleep will be queued and sent the next time the device wakes. Details of the default wake interval, and how to manually wake the device (if supported) will be detailed in the devices's manual. Some battery powered devices (primarily locks and thermostats) support beaming (the *Beam* command class) that allows them to be remotely woken. This does require that all devices in the network responsible for relaying the commands between the controller and the device also support beaming. +Battery powered devices spend most of their time asleep, unable to relay traffic, to be queried, or receive changes. Changes sent while a device is asleep will be queued and sent the next time the device wakes. Details of the default wake interval, and how to manually wake the device (if supported) will be detailed in the device's manual. Some battery powered devices (primarily locks and thermostats) support beaming (the *Beam* command class) that allows them to be remotely woken. This does require that all devices in the network responsible for relaying the commands between the controller and the device also support beaming.
@@ -56,7 +56,7 @@ As long as your device lists Hail or Association in its Controlled Command Class Where a device doesn't send updates on status changes to the controller, you can work around this by using a thing called Polling. That causes the controller to ask the device to provide an update on all its sensors and states. This will cause a lot of traffic on the network, and if you poll too many devices too quickly, you can effectively break your Z-Wave network. Polling should only be used where there is no other choice, and you should use as large a polling interval as possible. Ideally you should replace the device. -For example, with `polling_interval=60000` (which is the default) if you have 10 devices that are being polled at every interval, and each polling takes one secound (request/response round trip), then it will take 10 seconds to complete the polling list. This only leaves 50 seconds left for normal traffic. The more devices you poll, and the shorter the interval, the less bandwidth that's available for normal traffic. +For example, with `polling_interval=60000` (which is the default) if you have 10 devices that are being polled at every interval, and each polling takes one second (request/response round trip), then it will take 10 seconds to complete the polling list. This only leaves 50 seconds left for normal traffic. The more devices you poll, and the shorter the interval, the less bandwidth that's available for normal traffic. Polling needs to be enabled per device, you can control this through the *polling intensity* (interval) of the device. See the [Node Management](/docs/z-wave/control-panel#z-wave-node-management) documentation for details. diff --git a/source/_faq/connection-error.markdown b/source/_faq/connection-error.markdown index ba007cdd559..d31169ca76d 100644 --- a/source/_faq/connection-error.markdown +++ b/source/_faq/connection-error.markdown @@ -10,4 +10,4 @@ It can happen that you get a traceback that notify you about connection issues w ConnectionRefusedError: [Errno 111] Connection refused ``` -The chance is very high that this is not a bug but an issue with the service/daemon itself. Check your network (DNS, DHCP, uplink, etc.) first and make sure that Home Assistant and the service are poperly configured. Keep in mind that webservices can be down. +The chance is very high that this is not a bug but an issue with the service/daemon itself. Check your network (DNS, DHCP, uplink, etc.) first and make sure that Home Assistant and the service are properly configured. Keep in mind that webservices can be down. diff --git a/source/_faq/dependencies.markdown b/source/_faq/dependencies.markdown index 99b5e249c0b..89ca55b8cad 100644 --- a/source/_faq/dependencies.markdown +++ b/source/_faq/dependencies.markdown @@ -4,5 +4,5 @@ description: "Dependencies" ha_category: Usage --- -The dependencies which are used by Home Assistant are stored in the folder `deps` of the [configuration folder](/docs/configuration/) directory. After an [upgrade](/docs/installation/updating/) the dependences will be upgraded as well. +The dependencies which are used by Home Assistant are stored in the folder `deps` of the [configuration folder](/docs/configuration/) directory. After an [upgrade](/docs/installation/updating/) the dependencies will be upgraded as well. diff --git a/source/_faq/missing-documentation.markdown b/source/_faq/missing-documentation.markdown index 3c5e89e033f..07b00a89b61 100644 --- a/source/_faq/missing-documentation.markdown +++ b/source/_faq/missing-documentation.markdown @@ -4,6 +4,6 @@ description: "The documentation is missing or outdated" ha_category: Documentation --- -Home Assistant is a FAST moving open source project. This means occasionally the official documentation will not be 100% current or complete. Since this is an open source volunteer project, we would encourage anyone who finds gaps in the documentation to click the `edit this page on Github` link in the top right and submit any corrections/enhancements they may find useful. +Home Assistant is a FAST moving open source project. This means occasionally the official documentation will not be 100% current or complete. Since this is an open source volunteer project, we would encourage anyone who finds gaps in the documentation to click the `edit this page on Github` link in the top right and submit any corrections/enhancements they may find useful. A step-by-step guide on how to contribute to the documentation can be found [here](https://community.home-assistant.io/t/editing-the-documentation-and-creating-a-pull-request-on-github/9573). In the absence of information, many users find it beneficial to look at other people's configurations to find examples of what they want to accomplish in their own configurations. The easiest way to find these configurations is through this [GitHub search](https://github.com/search?q=topic%3Ahome-assistant-config&type=Repositories). diff --git a/source/_faq/release.markdown b/source/_faq/release.markdown index efd71b3bb34..7594987153b 100644 --- a/source/_faq/release.markdown +++ b/source/_faq/release.markdown @@ -1,12 +1,9 @@ --- title: "Releases" -description: "Releases" +description: "Home Assistant release schedule" ha_category: Common --- -The current release cycle is three weeks. This allows for two weeks of development time and 1 week of beta testing and fixing. Releases usually occur on a Wednesday. There is no fixed time of day when the release will happen because that depends on the person who is finishing the release, it could therefore be Tuesday or Thursday depending on your timezone when its available for you. If there was no announcement made in the previous release notes or on another communication channel then the release will happen. +New versions of Home Assistant are released every three weeks on a Wednesday. The exact dates can be seen in the upcoming events calendar on the [Home Assistant Developers](https://developers.home-assistant.io/) website. -Beta's are normally released on the 2nd Wednesday after the last major release. Please subscribe to the Beta Channel on the [Home Assistant Discord server](https://discord.gg/RMC8WkX) for help running beta versions. -When a beta release is in progress, the release notes for it can be found under [Beta Release Notes](https://rc.home-assistant.io/latest-release-notes/). - -The release schedule is published in the upcoming events calender on the [Home Assistant Developers](https://developers.home-assistant.io/) website. +The third week of our release schedule is primarily focused on beta testing. Users who participate in the beta can view the changelog under [beta release notes](https://rc.home-assistant.io/latest-release-notes/) and get help in the `#beta` channel of [Home Assistant's Discord server](/join-chat). Testers are also encouraged to [report issues on GitHub](/help/#bugs-feature-requests-and-alike). diff --git a/source/_includes/asides/cloud_navigation.html b/source/_includes/asides/cloud_navigation.html index 48ca4058146..b4d936c0579 100644 --- a/source/_includes/asides/cloud_navigation.html +++ b/source/_includes/asides/cloud_navigation.html @@ -1,20 +1,22 @@
-

About Home Assistant

-
    -
  • - The Home Assistant Cloud is a cloud-based service provided to supporters of the Home Assistant project. -
    • -
  • - {% active_link /cloud/ Introduction %} -
    • -
  • - {% active_link /cloud/alexa/ Amazon Alexa %} -
    • -
  • - {% active_link /cloud/google_assistant/ Google Assistant %} -
    • -
  • - {% active_link /cloud/troubleshooting/ Troubleshooting %} -
    • -
-
+
+

About Home Assistant

+
    +
  • + The Home Assistant Cloud is a cloud-based service provided to supporters of the Home Assistant project. +
    • +
  • + {% active_link /cloud/ Introduction %} +
    • +
  • + {% active_link /cloud/alexa/ Amazon Alexa %} +
    • +
  • + {% active_link /cloud/google_assistant/ Google Assistant %} +
    • +
  • + {% active_link /cloud/troubleshooting/ Troubleshooting %} +
    • +
+
+ diff --git a/source/_includes/asides/conference_navigation.html b/source/_includes/asides/conference_navigation.html new file mode 100644 index 00000000000..ad1535ea2cd --- /dev/null +++ b/source/_includes/asides/conference_navigation.html @@ -0,0 +1,36 @@ +
+
+

Details

+
    +
  • + When: Sunday, December 13, 2020
    + Where: online
    + Cost: free
    +
    • +
+
+ +
+

Contact

+ +
+ +
+

Sponsors

+ +
+ +
diff --git a/source/_includes/asides/hassio_navigation.html b/source/_includes/asides/hassio_navigation.html index dd294ffeaf5..0981ec681b2 100644 --- a/source/_includes/asides/hassio_navigation.html +++ b/source/_includes/asides/hassio_navigation.html @@ -9,6 +9,7 @@
  • {% active_link /addons/ Available add-ons %}
  • {% active_link /hassio/installing_third_party_addons/ Installing third-party add-ons %}
  • {% active_link /hassio/hassos_faq/ Home Assistant OS FAQ %}
    • +
  • {% active_link /hassio/haos_common_tasks/ Home Assistant OS Common tasks %}
    • diff --git a/source/_includes/asides/lovelace_navigation.html b/source/_includes/asides/lovelace_navigation.html index d0cbced919c..aed65885265 100644 --- a/source/_includes/asides/lovelace_navigation.html +++ b/source/_includes/asides/lovelace_navigation.html @@ -12,7 +12,6 @@

    Advanced

      -
    • {% active_link /lovelace/how-it-works/ How it works %}
    • {% active_link /lovelace/header-footer/ Headers & Footers %}
    • {% active_link /lovelace/dashboards-and-views/ Dashboards & Views %} diff --git a/source/_includes/site/sidebar.html b/source/_includes/site/sidebar.html index 4edbe4468d7..1c77a198122 100644 --- a/source/_includes/site/sidebar.html +++ b/source/_includes/site/sidebar.html @@ -1,23 +1,26 @@
      {% assign url_parts = page.url | split: '/' %} - {% if url_parts[1] == 'integrations' %} + {% assign root = url_parts[1] %} + {% if root == 'integrations' %} {% include asides/component_navigation.html %} - {% elsif url_parts[1] == 'cookbook' %} + {% elsif root == 'cookbook' %} {% include asides/cookbook_navigation.html %} - {% elsif url_parts[1] == 'lovelace' %} + {% elsif root == 'lovelace' %} {% include asides/lovelace_navigation.html %} - {% elsif url_parts[1] == 'developers' or url_parts[1] == 'help' %} + {% elsif root == 'developers' or root == 'help' %} {% include asides/help_navigation.html %} - {% elsif url_parts[1] == 'getting-started' %} + {% elsif root == 'getting-started' %} {% include asides/getting_started_navigation.html %} - {% elsif url_parts[1] == 'docs' %} + {% elsif root == 'docs' %} {% include asides/docs_navigation.html %} - {% elsif url_parts[1] == 'faq' %} + {% elsif root == 'faq' %} {% include asides/faq_navigation.html %} - {% elsif url_parts[1] == 'hassio' or url_parts[1] == 'addons' %} + {% elsif root == 'hassio' or root == 'addons' %} {% include asides/hassio_navigation.html %} - {% elsif url_parts[1] == 'cloud' %} + {% elsif root == 'cloud' %} {% include asides/cloud_navigation.html %} + {% elsif root == 'conference' %} + {% include asides/conference_navigation.html %} {% else %} {% include asides/about.html %} diff --git a/source/_integrations/agent_dvr.markdown b/source/_integrations/agent_dvr.markdown index 5016c7064bd..8ab9d33deff 100644 --- a/source/_integrations/agent_dvr.markdown +++ b/source/_integrations/agent_dvr.markdown @@ -6,7 +6,7 @@ ha_category: - Alarm ha_config_flow: true ha_release: '0.110' -ha_iot_class: Local Pull +ha_iot_class: Local Polling ha_codeowners: - '@ispysoftware' ha_domain: agent_dvr diff --git a/source/_integrations/alarm_control_panel.template.markdown b/source/_integrations/alarm_control_panel.template.markdown index c12d0a12eb0..40f96d10c73 100644 --- a/source/_integrations/alarm_control_panel.template.markdown +++ b/source/_integrations/alarm_control_panel.template.markdown @@ -73,7 +73,7 @@ panels: type: string default: Template Alarm Control Panel unique_id: - description: An ID that uniquely identifies this alarm control panel. Set this to an unique value to allow customisation trough the UI. + description: An ID that uniquely identifies this alarm control panel. Set this to a unique value to allow customization through the UI. required: false type: string value_template: @@ -96,11 +96,13 @@ panels: description: Defines an action to run when the alarm is armed to night mode. required: false type: action + code_arm_required: + description: If true, the code is required to arm the alarm. + required: false + type: boolean + default: false {% endconfiguration %} - - - ## Considerations If you are using the state of a integration that takes extra time to load, the Template Alarm Control Panel may get an `unknown` state during startup. This results in error messages in your log file until that integration has completed loading. If you use `is_state()` function in your template, you can avoid this situation. @@ -109,4 +111,4 @@ For example, you would replace {% raw %}`{{ states.switch.source.state == 'on' } ### Working without entities -If you use a template that depends on the current time or some other non-deterministic result not sourced from entities, the template won't repeatedly update but will only update when the state of a referenced entity updates. For ways to deal with this issue, see [Working without entities](/integrations/binary_sensor.template/#working-without-entities) in the Template Binary Sensor integration. \ No newline at end of file +If you use a template that depends on the current time or some other non-deterministic result not sourced from entities, the template won't repeatedly update but will only update when the state of a referenced entity updates. For ways to deal with this issue, see [Working without entities](/integrations/binary_sensor.template/#working-without-entities) in the Template Binary Sensor integration. diff --git a/source/_integrations/alarmdecoder.markdown b/source/_integrations/alarmdecoder.markdown index 4c954b405ad..f07b85ed7d6 100644 --- a/source/_integrations/alarmdecoder.markdown +++ b/source/_integrations/alarmdecoder.markdown @@ -9,7 +9,8 @@ ha_release: 0.43 ha_iot_class: Local Push ha_domain: alarmdecoder ha_codeowners: - - "@ajschmidt8" + - '@ajschmidt8' +ha_config_flow: true --- The `alarmdecoder` integration will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and its sensors to provide Home Assistant with rich information about their homes. Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Nu Tech Software Solutions, known as the AlarmDecoder. The AlarmDecoder devices provide a serial, TCP/IP socket or USB interface to the alarm panel, where it emulates an alarm keypad. @@ -37,7 +38,7 @@ You will be prompted to select a protocol (i.e. `socket` or `serial`). Depending - **path** - the path to the AlarmDecoder device (i.e. `/dev/ttyUSB0`) - **baud rate** - the baud rate of the AlarmDecoder device (i.e. `115200`) -## Configuration +## Settings Once AlarmDecoder has been set up according to the instructions above, the arming settings and zones can be configured by selecting _Options_ on the _AlarmDecoder_ card on the **Configuration -> Integrations** page. @@ -195,4 +196,3 @@ The `chr(4)` and `chr(5)` sequences below are equivalent to pressing the Sta | `alarm_arm_away` | `chr(5)` + `chr(5)` + `chr(5)` | | `alarm_arm_night` (`alt_night_mode` = `false`, default) | `chr(4)` + `chr(4)` + `chr(4)` | | `alarm_arm_night` (`alt_night_mode` = `true`) | `*9` + `code` | - diff --git a/source/_integrations/alert.markdown b/source/_integrations/alert.markdown index 6675feff744..de89f3a3ff6 100644 --- a/source/_integrations/alert.markdown +++ b/source/_integrations/alert.markdown @@ -15,8 +15,15 @@ remind you of this by sending you repeating notifications at customizable intervals. This is also used for low battery sensors, water leak sensors, or any condition that may need your attention. -Alerts will add an entity to the front end only when they are firing. -This entity allows you to silence an alert until it is resolved. +Alerts will add an entity to the front end. +This entity allows you to silence an alert until it is resolved and has three +possible states: + +State | Description +-|- +`idle` | The condition for the alert is false. +`on` | The condition for the alert is true. +`off` | The condition for the alert is true but it was acknowledged. ### Basic Example @@ -80,15 +87,15 @@ skip_first: default: false message: description: > - A message to be sent after an alert transitions from `off` to `on` + A message to be sent after an alert transitions from `idle` to `on` with [template](/docs/configuration/templating/) support. required: false type: template done_message: description: > - A message sent after an alert transitions from `on` to `off` with + A message sent after an alert transitions from `on` or `off` to `idle` with [template](/docs/configuration/templating/) support. Is only sent if an alert notification - was sent for transitioning from `off` to `on`. + was sent for transitioning from `idle` to `on`. required: false type: template notifiers: diff --git a/source/_integrations/amazon_polly.markdown b/source/_integrations/amazon_polly.markdown index 12edea9dba1..910fc8b517c 100644 --- a/source/_integrations/amazon_polly.markdown +++ b/source/_integrations/amazon_polly.markdown @@ -5,6 +5,7 @@ ha_category: - Text-to-speech ha_release: 0.37 ha_domain: amazon_polly +ha_iot_class: Cloud Push --- The `amazon_polly` text-to-speech platform that works with [Amazon Polly](https://aws.amazon.com/polly/) to create the spoken output. diff --git a/source/_integrations/apache_kafka.markdown b/source/_integrations/apache_kafka.markdown index eec80011b59..d93abf50bfa 100644 --- a/source/_integrations/apache_kafka.markdown +++ b/source/_integrations/apache_kafka.markdown @@ -7,6 +7,7 @@ ha_release: 0.97 ha_codeowners: - '@bachya' ha_domain: apache_kafka +ha_iot_class: Local Push --- The `apache_kafka` integration sends all state changes to a diff --git a/source/_integrations/apns.markdown b/source/_integrations/apns.markdown index d32bcca86a4..7793c30c050 100644 --- a/source/_integrations/apns.markdown +++ b/source/_integrations/apns.markdown @@ -4,6 +4,7 @@ description: Instructions on how to add APNS notifications to Home Assistant. ha_category: - Notifications ha_release: 0.31 +ha_iot_class: Cloud Push ha_domain: apns --- diff --git a/source/_integrations/auth.markdown b/source/_integrations/auth.markdown index 2d3f7e9bf7c..9fc051c74eb 100644 --- a/source/_integrations/auth.markdown +++ b/source/_integrations/auth.markdown @@ -4,6 +4,7 @@ description: This integration is responsible for providing the authentication en ha_category: - Other ha_release: 0.73 +ha_iot_class: ~ ha_quality_scale: internal ha_codeowners: - '@home-assistant/core' diff --git a/source/_integrations/automation.markdown b/source/_integrations/automation.markdown index dfd6a7de19c..1b43f7cf5d5 100644 --- a/source/_integrations/automation.markdown +++ b/source/_integrations/automation.markdown @@ -98,7 +98,7 @@ This service disables the automation's triggers, and optionally stops any curren Service data attribute | Optional | Description -|-|- `entity_id` | no | Entity ID of automation to turn on. Can be a list. `none` or `all` are also accepted. -`stop_actions` | yes | Stop any currently active actions (defaults to true.) +`stop_actions` | yes | Stop any currently active actions (defaults to true). ### `automation.toggle` @@ -111,3 +111,12 @@ Service data attribute | Optional | Description ### `automation.reload` This service reloads all automations, stopping any currently active actions in all of them. + +### `automation.trigger` + +This service will trigger the action of an automation. By default it bypasses any conditions, though that can be changed via the `skip_condition` attribute. + +Service data attribute | Optional | Description +-|-|- +`entity_id` | no | Entity ID of automation to trigger. Can be a list. `none` or `all` are also accepted. +`skip_condition` | yes | Whether or not the condition will be skipped (defaults to true). diff --git a/source/_integrations/aws.markdown b/source/_integrations/aws.markdown index 1b7e0a76b3b..f640b0c9211 100644 --- a/source/_integrations/aws.markdown +++ b/source/_integrations/aws.markdown @@ -3,6 +3,7 @@ title: Amazon Web Services (AWS) description: Instructions on how to integrate Amazon Web Services with Home Assistant. ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: '0.91' ha_codeowners: - '@awarecan' diff --git a/source/_integrations/azure_service_bus.markdown b/source/_integrations/azure_service_bus.markdown index 0509c735a21..c432d0da757 100644 --- a/source/_integrations/azure_service_bus.markdown +++ b/source/_integrations/azure_service_bus.markdown @@ -3,6 +3,7 @@ title: Azure Service Bus description: Setup for Azure Service Bus integration ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: 0.102 ha_codeowners: - '@hfurubotten' diff --git a/source/_integrations/binary_sensor.template.markdown b/source/_integrations/binary_sensor.template.markdown index 957f7db9173..abdc0b82fab 100644 --- a/source/_integrations/binary_sensor.template.markdown +++ b/source/_integrations/binary_sensor.template.markdown @@ -48,7 +48,7 @@ sensors: required: false type: string unique_id: - description: An ID that uniquely identifies this binary sensor. Set this to an unique value to allow customisation through the UI. + description: An ID that uniquely identifies this binary sensor. Set this to a unique value to allow customization through the UI. required: false type: string device_class: @@ -321,12 +321,11 @@ binary_sensor: ``` {% endraw %} - If the template accesses every state on the system, a rate limit of one update per minute is applied. If the template accesses all states under a specific domain, a rate limit of one update per second is applied. If the template only accesses specific states, receives update events for specifically referenced entities, or the `homeassistant.update_entity` service is used, no rate limit is applied. ### Working without entities -The `template` sensors are not limited to use attributes from other entities but can also work with [Home Assistant's template extensions](/docs/configuration/templating/#home-assistant-template-extensions). If the template includes some non-deterministic property such as time in its calculation, the result will not continually update, but will only update when some entity referenced by the template updates. +The `template` sensors are not limited to use attributes from other entities but can also work with [Home Assistant's template extensions](/docs/configuration/templating/#home-assistant-template-extensions). If the template includes some non-deterministic property such as time in its calculation, the result will not continually update, but will only update when some entity referenced by the template updates. There's a couple of options to manage this issue. This first example creates a `sensor.time` from the [Time & Date](/integrations/time_date/) component which updates every minute, and the binary sensor is triggered by this updating. The binary sensor returns true if in the first half of the hour: diff --git a/source/_integrations/browser.markdown b/source/_integrations/browser.markdown index 9c95044764f..d465b0b749a 100644 --- a/source/_integrations/browser.markdown +++ b/source/_integrations/browser.markdown @@ -4,6 +4,7 @@ description: Instructions on how to setup the browser integration with Home Assi ha_category: - Utility ha_release: pre 0.7 +ha_iot_class: ~ ha_quality_scale: internal ha_domain: browser --- diff --git a/source/_integrations/camera.markdown b/source/_integrations/camera.markdown index ab1382f388c..f6acec3ae43 100644 --- a/source/_integrations/camera.markdown +++ b/source/_integrations/camera.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: 0.7 ha_quality_scale: internal ha_domain: camera +ha_iot_class: ~ --- The camera integration allows you to use IP cameras with Home Assistant. diff --git a/source/_integrations/cast.markdown b/source/_integrations/cast.markdown index 41c59ee2a4e..02743ba4d2a 100644 --- a/source/_integrations/cast.markdown +++ b/source/_integrations/cast.markdown @@ -26,11 +26,11 @@ Home Assistant has its own Cast application to show the Home Assistant UI on any cast_downstairs_on_kitchen: alias: Show Downstairs on kitchen sequence: - - data: - dashboard_path: lovelace - entity_id: media_player.kitchen - view_path: downstairs - service: cast.show_lovelace_view + - data: + dashboard_path: lovelace + entity_id: media_player.kitchen + view_path: downstairs + service: cast.show_lovelace_view ```
      @@ -53,15 +53,15 @@ Optional: 'cast_youtube_to_my_chromecast': alias: Cast YouTube to My Chromecast sequence: - - data: - entity_id: media_player.my_chromecast - media_content_type: cast - media_content_id: ' - { - "app_name": "youtube", - "media_id": "dQw4w9WgXcQ" - }' - service: media_player.play_media + - data: + entity_id: media_player.my_chromecast + media_content_type: cast + media_content_id: ' + { + "app_name": "youtube", + "media_id": "dQw4w9WgXcQ" + }' + service: media_player.play_media ``` ### [Supla](https://www.supla.fi/) @@ -78,15 +78,15 @@ Optional: 'cast_supla_to_my_chromecast': alias: Cast supla to My Chromecast sequence: - - data: - entity_id: media_player.my_chromecast - media_content_type: cast - media_content_id: ' - { - "app_name": "supla", - "media_id": "3601824" - }' - service: media_player.play_media + - data: + entity_id: media_player.my_chromecast + media_content_type: cast + media_content_id: ' + { + "app_name": "supla", + "media_id": "3601824" + }' + service: media_player.play_media ``` ### Plex diff --git a/source/_integrations/circuit.markdown b/source/_integrations/circuit.markdown index 40497336b01..de5207be029 100644 --- a/source/_integrations/circuit.markdown +++ b/source/_integrations/circuit.markdown @@ -3,6 +3,7 @@ title: Unify Circuit description: Instructions on how to send a notification to a Unify Circuit Conversation. ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: 0.111 ha_codeowners: - '@braam' diff --git a/source/_integrations/cisco_webex_teams.markdown b/source/_integrations/cisco_webex_teams.markdown index 6d137842a8d..3c304a532b4 100644 --- a/source/_integrations/cisco_webex_teams.markdown +++ b/source/_integrations/cisco_webex_teams.markdown @@ -3,6 +3,7 @@ title: Cisco Webex Teams description: Instructions on how to add Cisco Webex Teams notifications to Home Assistant. ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: '0.40' ha_codeowners: - '@fbradyirl' diff --git a/source/_integrations/clickatell.markdown b/source/_integrations/clickatell.markdown index d6d71322489..23fde3a578a 100644 --- a/source/_integrations/clickatell.markdown +++ b/source/_integrations/clickatell.markdown @@ -3,6 +3,7 @@ title: Clickatell description: Instructions on how to add Clickatell notifications to Home Assistant. ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: 0.56 ha_domain: clickatell --- diff --git a/source/_integrations/clicksend_tts.markdown b/source/_integrations/clicksend_tts.markdown index c41db4bd76a..1268ffb9b02 100644 --- a/source/_integrations/clicksend_tts.markdown +++ b/source/_integrations/clicksend_tts.markdown @@ -3,6 +3,7 @@ title: ClickSend TTS description: Instructions on how to add ClickSend text-to-speech (TTS) notifications to Home Assistant. ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: 0.55 ha_domain: clicksend_tts --- diff --git a/source/_integrations/climate.markdown b/source/_integrations/climate.markdown index 439665258d9..fcd446e2626 100644 --- a/source/_integrations/climate.markdown +++ b/source/_integrations/climate.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: 0.19 ha_quality_scale: internal ha_domain: climate +ha_iot_class: ~ --- The Climate integration allows you to control and monitor HVAC (heating, ventilating, and air conditioning) devices and thermostats. @@ -77,9 +78,9 @@ Set target temperature of climate device | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `entity_id` | yes | String or list of strings that define the entity ID(s) of climate device(s) to control. To target all climate devices, use `all`. -| `temperature` | no | New target temperature for climate device (commonly referred to as a *setpoint*). Do not use if `hvac_mode` is `heat_cool`. -| `target_temp_high` | yes | The highest temperature that the climate device will allow. Required if `hvac_mode` is `heat_cool`. -| `target_temp_low` | yes | The lowest temperature that the climate device will allow. Required if `hvac_mode` is `heat_cool`. +| `temperature` | yes | New target temperature for climate device (commonly referred to as a *setpoint*). Do not use if `hvac_mode` is `heat_cool`. +| `target_temp_high` | yes | The highest temperature that the climate device will allow. Required if `hvac_mode` is `heat_cool`. Required together with `target_temp_low`. +| `target_temp_low` | yes | The lowest temperature that the climate device will allow. Required if `hvac_mode` is `heat_cool`. Required together with `target_temp_high`. | `hvac_mode` | yes | HVAC mode to set the climate device to. This defaults to current HVAC mode if not set, or set incorrectly. #### Automation examples diff --git a/source/_integrations/command_line.markdown b/source/_integrations/command_line.markdown index 01da8be49f4..2d58016c048 100644 --- a/source/_integrations/command_line.markdown +++ b/source/_integrations/command_line.markdown @@ -136,3 +136,13 @@ binary_sensor: payload_on: 'active' payload_off: 'inactive' ``` + +## Services + +Available services: `reload`. + +### Service `command_line.reload` + +Reload all `command_line` entities. + +This service takes no service data attributes. diff --git a/source/_integrations/concord232.markdown b/source/_integrations/concord232.markdown index 34ad9f193ab..eb9096cf930 100644 --- a/source/_integrations/concord232.markdown +++ b/source/_integrations/concord232.markdown @@ -5,7 +5,9 @@ logo: interlogix.png ha_category: - Alarm - Binary Sensor +ha_iot_class: Local Polling ha_release: 0.31 +ha_iot_class: Local Polling ha_domain: concord232 --- diff --git a/source/_integrations/config.markdown b/source/_integrations/config.markdown index 26f1f8a16f0..52e9604fffe 100644 --- a/source/_integrations/config.markdown +++ b/source/_integrations/config.markdown @@ -44,11 +44,11 @@ This section enables you to control Home Assistant from within Home Assistant. C This section enables you to associate users with their device tracker entities using the person component. -### Entity Registry +### Entities This section enables you to override the name, change the entity ID or disable an entity in Home Assistant. -### Area Registry +### Areas This section enables you to organize entities to physical areas of your home. @@ -64,6 +64,6 @@ Similar to the automation editor, this section enables you to create and modify This section enables you to control your Z-Wave network and devices from within Home Assistant. You can add and remove devices, as well as change device specific configuration variables. -### Customization +### Customizations This section enables you to customize entities within Home Assistant. Use this to set friendly names, change icons, and modify other attributes. diff --git a/source/_integrations/counter.markdown b/source/_integrations/counter.markdown index 2aafbf0812c..ecc0c41d53f 100644 --- a/source/_integrations/counter.markdown +++ b/source/_integrations/counter.markdown @@ -68,7 +68,7 @@ Pick an icon that you can find on [materialdesignicons.com](https://materialdesi ### Restore State -This integration will automatically restore the state it had prior to Home Assistant stopping as long as you your entity has `restore` set to `true` which is the default. To disable this feature, set `restore` to `false`. +This integration will automatically restore the state it had prior to Home Assistant stopping as long as your entity has `restore` set to `true`, which is the default. To disable this feature, set `restore` to `false`. If `restore` is set to `false`, the `initial` value will only be used when no previous state is found or when the counter is reset. @@ -76,7 +76,7 @@ If `restore` is set to `false`, the `initial` value will only be used when no pr Available services: `increment`, `decrement`, `reset` and `configure`. -#### Service `counter.increment` +### Service `counter.increment` Increments the counter with 1 or the given value for the steps. @@ -84,7 +84,7 @@ Increments the counter with 1 or the given value for the steps. | ---------------------- | -------- | ----------- | | `entity_id` | no | Name of the entity to take action, e.g., `counter.my_custom_counter`. | -#### Service `counter.decrement` +### Service `counter.decrement` Decrements the counter with 1 or the given value for the steps. @@ -92,7 +92,7 @@ Decrements the counter with 1 or the given value for the steps. | ---------------------- | -------- | ----------- | | `entity_id` | no | Name of the entity to take action, e.g., `counter.my_custom_counter`. | -#### Service `counter.reset` +### Service `counter.reset` With this service the counter is reset to its initial value. @@ -100,7 +100,7 @@ With this service the counter is reset to its initial value. | ---------------------- | -------- | ----------- | | `entity_id` | no | Name of the entity to take action, e.g., `counter.my_custom_counter`. | -#### Service `counter.configure` +### Service `counter.configure` With this service the properties of the counter can be changed while running. diff --git a/source/_integrations/cover.markdown b/source/_integrations/cover.markdown index 344ef566838..c8300a17fde 100644 --- a/source/_integrations/cover.markdown +++ b/source/_integrations/cover.markdown @@ -8,6 +8,7 @@ ha_quality_scale: internal ha_codeowners: - '@home-assistant/core' ha_domain: cover +ha_iot_class: ~ --- Home Assistant can give you an interface to control covers such as rollershutters, blinds, and garage doors. diff --git a/source/_integrations/cover.template.markdown b/source/_integrations/cover.template.markdown index bd03dc05ffe..c7b0c16507b 100644 --- a/source/_integrations/cover.template.markdown +++ b/source/_integrations/cover.template.markdown @@ -50,7 +50,7 @@ cover: required: false type: string unique_id: - description: An ID that uniquely identifies this cover. Set this to an unique value to allow customisation trough the UI. + description: An ID that uniquely identifies this cover. Set this to a unique value to allow customization through the UI. required: false type: string value_template: @@ -65,6 +65,10 @@ cover: description: Defines a template to specify which icon to use. required: false type: template + entity_picture_template: + description: Defines a template for the entity picture of the cover. + required: false + type: template availability_template: description: Defines a template to get the `available` state of the component. If the template returns `true`, the device is `available`. If the template returns any other value, the device will be `unavailable`. If `availability_template` is not configured, the component will always be `available`. required: false diff --git a/source/_integrations/daikin.markdown b/source/_integrations/daikin.markdown index 109bf1e5179..d574e3b7dd6 100644 --- a/source/_integrations/daikin.markdown +++ b/source/_integrations/daikin.markdown @@ -24,12 +24,17 @@ There is currently support for the following device types within Home Assistant: ## Supported hardware -- The European versions of the Wifi Controller Unit (BRP069A41, 42, 43, 45), which is powered by the [Daikin Online Controller](https://play.google.com/store/apps/details?id=eu.daikin.remoapp) application. The new version of WiFi Controller Unit BRP069Bxx also confirmed to work, tested and working devices are the BRP069B41 and BRP069B45. -- The Australian version of the Daikin Wifi Controller Unit BRP072A42. Confirmed working on a Daikin Cora Series Reverse Cycle Split System Air Conditioner 2.5kW Cooling FTXM25QVMA with operation mode, temp, fan swing (3d, horizontal, vertical) which is powered by the [Daikin Mobile Controller](https://itunes.apple.com/au/app/daikin-mobile-controller/id917168708?mt=8) ([Android version](https://play.google.com/store/apps/details?id=eu.daikin.remoapp)) application. - - BRP072Cxx based units (including Zena devices) need to provide the API-key found on a sticker under the front cover during setup. -- The Australian version of the Daikin Wifi Controller for **AirBase** units (BRP15B61), which is powered by the [Daikin Airbase](https://play.google.com/store/apps/details?id=au.com.daikin.airbase) application. -- SKYFi based units (using the SKYFi app). These devices need to provide the password found on a sticker under the front cover during setup. +- The European versions of the Wifi Controller Unit (BRP069A41, 42, 43, 45), which is powered by the [Daikin Online Controller](https://play.google.com/store/apps/details?id=eu.daikin.remoapp) application. The new version of WiFi Controller Unit BRP069Bxx is also confirmed to work, tested and working devices are the BRP069B41 and BRP069B45. +- The Australian version of the Daikin Wifi Controller Unit BRP072A42, which is operated by the [Daikin Mobile Controller](https://itunes.apple.com/au/app/daikin-mobile-controller/id917168708?mt=8) ([Android version](https://play.google.com/store/apps/details?id=eu.daikin.remoapp)) application. Confirmed working on a Daikin Cora Series Reverse Cycle Split System Air Conditioner 2.5kW Cooling FTXM25QVMA with operation mode, temp, fan swing (3d, horizontal, vertical). + - BRP072Cxx based units (including Zena devices)*. +- The Australian version of the Daikin Wifi Controller for **AirBase** units (BRP15B61), which is operated by the [Daikin Airbase](https://play.google.com/store/apps/details?id=au.com.daikin.airbase) application. +- **SKYFi** based units, which is operated by the SKYFi application*. +
      + +* The integration for BRP072Cxx and SKYFi based units need API-key / password respectively. The API-key/password can be found on a sticker under the front cover. The other models are auto detected and the API-key and password field must be left empty. + +
      ## Configuration diff --git a/source/_integrations/datadog.markdown b/source/_integrations/datadog.markdown index c961445c118..fc5bf585adf 100644 --- a/source/_integrations/datadog.markdown +++ b/source/_integrations/datadog.markdown @@ -3,6 +3,7 @@ title: Datadog description: Send data and events to Datadog. ha_category: - History +ha_iot_class: Local Push ha_release: 0.45 ha_domain: datadog --- diff --git a/source/_integrations/default_config.markdown b/source/_integrations/default_config.markdown index 964678a5a86..4236c7e36c2 100644 --- a/source/_integrations/default_config.markdown +++ b/source/_integrations/default_config.markdown @@ -5,35 +5,36 @@ ha_category: - Other ha_release: 0.88 ha_domain: default_config +ha_iot_class: Calculated --- This integration is a meta-component and configures a default set of integrations for Home Assistant to load. The integrations that will be loaded are: -- [Automation](/integrations/automation/) -- [Home Assistant Cloud](/integrations/cloud/) -- [Configuration](/integrations/config/) -- [Frontend](/integrations/frontend/) -- [History](/integrations/history/) -- [Image](/integrations/image/) -- [Input boolean](/integrations/input_boolean) -- [Input datetime](/integrations/input_datetime) -- [Input number](/integrations/input_number) -- [Input select](/integrations/input_select) -- [Input text](/integrations/input_text) -- [Logbook](/integrations/logbook/) -- [Map](/integrations/map/) -- [Media Source](/integrations/media_source/) -- [Mobile App Support](/integrations/mobile_app/) -- [Person](/integrations/person/) -- [Scene](/integrations/scene/) -- [Scripts](/integrations/script/) -- [Simple Service Discovery Protocol (SSDP)](/integrations/ssdp/) -- [Sun](/integrations/sun/) -- [System Health](/integrations/system_health/) -- [Tag](/integrations/tag/) -- [Updater](/integrations/updater/) -- [Zero-configuration networking (zeroconf)](/integrations/zeroconf/) -- [Zone](/integrations/zone) +- [Automation](/integrations/automation/) (`automation`) +- [Home Assistant Cloud](/integrations/cloud/) (`cloud`) +- [Configuration](/integrations/config/) (`config`) +- [Frontend](/integrations/frontend/) (`frontend`) +- [History](/integrations/history/) (`history`) +- [Image](/integrations/image/) (`image`) +- [Input boolean](/integrations/input_boolean/) (`input_boolean`) +- [Input datetime](/integrations/input_datetime/) (`input_datetime`) +- [Input number](/integrations/input_number/) (`input_number`) +- [Input select](/integrations/input_select/) (`input_select`) +- [Input text](/integrations/input_text/) (`input_text`) +- [Logbook](/integrations/logbook/) (`logbook`) +- [Map](/integrations/map/) (`map`) +- [Media Source](/integrations/media_source/) (`media_source`) +- [Mobile App Support](/integrations/mobile_app/) (`mobile_app`) +- [Person](/integrations/person/) (`person`) +- [Scene](/integrations/scene/) (`scene`) +- [Scripts](/integrations/script/) (`script`) +- [Simple Service Discovery Protocol (SSDP)](/integrations/ssdp/) (`ssdp`) +- [Sun](/integrations/sun/) (`sun`) +- [System Health](/integrations/system_health/) (`system_health`) +- [Tag](/integrations/tag/) (`tag`) +- [Updater](/integrations/updater/) (`updater`) +- [Zero-configuration networking (zeroconf)](/integrations/zeroconf/) (`zeroconf`) +- [Zone](/integrations/zone/) (`zone`) ## Configuration diff --git a/source/_integrations/demo.markdown b/source/_integrations/demo.markdown index 714074607ce..824323274a8 100644 --- a/source/_integrations/demo.markdown +++ b/source/_integrations/demo.markdown @@ -8,6 +8,7 @@ ha_quality_scale: internal ha_codeowners: - '@home-assistant/core' ha_domain: demo +ha_iot_class: Calculated --- The `demo` platform allows you to use integrations which are providing a demo of their implementation. The demo entities are dummies but show you how the actual platform looks like. This way you can run own demonstration instance like the online [Home Assistant demo](/demo/)but combined with your own real/functional platforms. diff --git a/source/_integrations/denonavr.markdown b/source/_integrations/denonavr.markdown index ed24723bf80..eadf88edef6 100644 --- a/source/_integrations/denonavr.markdown +++ b/source/_integrations/denonavr.markdown @@ -97,7 +97,7 @@ A few notes: - The `denonavr` platform supports some additional functionalities like album covers, custom input source names and auto discovery. - Marantz receivers seem to a have quite a similar interface. Thus if you own one, give it a try. - To remotely power on Marantz receivers with Home Assistant, the Auto-Standby feature must be enabled in the receiver's settings. -- Sound mode: The command to set a specific sound mode is different from the value of the current sound mode reported by the receiver (sound_mode_raw). There is a key-value structure (sound_mode_dict) that matches the raw sound mode to one of the possible commands to set a sound mode (for instance {'MUSIC':['PLII MUSIC']}. If you get a "Not able to match sound mode" warning, please open an issue on the [denonavr library](https://github.com/scarface-4711/denonavr), stating which raw sound mode could not be matched so it can be added to the matching dictionary. You can find the current raw sound mode under "Development Tools/States" in the front panel. +- Sound mode: The command to set a specific sound mode is different from the value of the current sound mode reported by the receiver (sound_mode_raw). There is a key-value structure (sound_mode_dict) that matches the raw sound mode to one of the possible commands to set a sound mode (for instance {'MUSIC':['PLII MUSIC']}. If you get a "Not able to match sound mode" warning, please open an issue on the [denonavr library](https://github.com/scarface-4711/denonavr), stating which raw sound mode could not be matched so it can be added to the matching dictionary. You can find the current raw sound mode under **Developer Tools** -> **States**. #### Service `denonavr.get_command` diff --git a/source/_integrations/derivative.markdown b/source/_integrations/derivative.markdown index 841503eaf34..8177b716b67 100644 --- a/source/_integrations/derivative.markdown +++ b/source/_integrations/derivative.markdown @@ -6,7 +6,7 @@ ha_category: - Energy - Sensor ha_release: 0.105 -ha_iot_class: Local Push +ha_iot_class: Calculated logo: derivative.png ha_qa_scale: internal ha_codeowners: diff --git a/source/_integrations/device_sun_light_trigger.markdown b/source/_integrations/device_sun_light_trigger.markdown index 6ff8ccde1d2..f9cec7f9b27 100644 --- a/source/_integrations/device_sun_light_trigger.markdown +++ b/source/_integrations/device_sun_light_trigger.markdown @@ -3,6 +3,9 @@ title: Presence-based Lights description: Instructions on how to automate your lights with Home Assistant. ha_category: - Automation + - Light + - Presence Detection +ha_iot_class: Calculated ha_release: pre 0.7 ha_quality_scale: internal ha_domain: device_sun_light_trigger diff --git a/source/_integrations/dialogflow.markdown b/source/_integrations/dialogflow.markdown index 5d363ae54eb..88cd7f1904d 100644 --- a/source/_integrations/dialogflow.markdown +++ b/source/_integrations/dialogflow.markdown @@ -35,21 +35,21 @@ To use this integration, you should define a conversation (intent) in Dialogflow To get the webhook URL, go to the integrations page in the configuration screen and find "Dialogflow". Click on "configure". Follow the instructions on the screen. -- [Login](https://console.dialogflow.com/) with your Google account -- Click on "Create Agent" -- Select name, language (if you are planning to use Google Actions check their [supported languages](https://support.google.com/assistant/answer/7108196?hl=en)) and time zone -- Click "Save" -- Now go to "Fulfillment" (in the left menu) +- [Login](https://console.dialogflow.com/) with your Google account. +- Click on "Create Agent". +- Select name, language (if you are planning to use Google Actions check their [supported languages](https://support.google.com/assistant/answer/7108196?hl=en)) and time zone. +- Click "Save". +- Now go to "Fulfillment" (in the left menu). - Enable Webhook and set your Dialogflow webhook URL as the endpoint, e.g., `https://myhome.duckdns.org/api/webhook/800b4cb4d27d078a8871656a90854a292651b20635685f8ea23ddb7a09e8b417` -- Click "Save" -- Create a new intent -- Below "User says" write one phrase that you, the user, will tell Dialogflow, e.g., `What is the temperature at home?` -- In "Action" set some key (this will be the bind with Home Assistant configuration), e.g.,: GetTemperature -- In "Response" set "Cannot connect to Home Assistant or it is taking to long" (fall back response) -- At the end of the page, click on "Fulfillment" and check "Use webhook" -- Click "Save" -- On the top right, where is written "Try it now...", write, or say, the phrase you have previously defined and hit enter -- Dialogflow has send a request to your Home Assistant server +- Click "Save". +- Create a new intent. +- Below "User says" type one phrase that you, the user, will say to Dialogflow, e.g., `What is the temperature at home?`. +- In "Action" enter an action name. This should match the name of an IntentScript within your Home Assistant configuration, e.g., in the example below "Temperature". +- In "Response" enter "Cannot connect to Home Assistant or it is taking to long" (fall back response). +- At the bottom of the page, expand "Fulfillment" and check "Use webhook". +- Click "Save". +- At the top right of the screen where it says "Try it now...", type, or say, the phrase you have previously defined and hit enter. +- Dialogflow will now send a request to your Home Assistant server and display the response.
      diff --git a/source/_integrations/dlib_face_detect.markdown b/source/_integrations/dlib_face_detect.markdown index 6703775b199..a29cacefde0 100644 --- a/source/_integrations/dlib_face_detect.markdown +++ b/source/_integrations/dlib_face_detect.markdown @@ -3,6 +3,7 @@ title: Dlib Face Detect description: Instructions on how to integrate Dlib Face Detect into Home Assistant. ha_category: - Image Processing +ha_iot_class: Local Push ha_release: 0.44 ha_domain: dlib_face_detect --- diff --git a/source/_integrations/dlib_face_identify.markdown b/source/_integrations/dlib_face_identify.markdown index bab93409aad..9d64e4e450d 100644 --- a/source/_integrations/dlib_face_identify.markdown +++ b/source/_integrations/dlib_face_identify.markdown @@ -3,6 +3,7 @@ title: Dlib Face Identify description: Instructions on how to integrate Dlib Face Identify into Home Assistant. ha_category: - Image Processing +ha_iot_class: Local Push ha_release: 0.44 ha_domain: dlib_face_identify --- diff --git a/source/_integrations/dsmr.markdown b/source/_integrations/dsmr.markdown index 89e7f7d3a50..f1b89b1b40d 100644 --- a/source/_integrations/dsmr.markdown +++ b/source/_integrations/dsmr.markdown @@ -15,7 +15,7 @@ A sensor platform for Dutch Smart Meters which comply to DSMR (Dutch Smart Meter - Currently support DSMR V2.2, V3, V4, V5 and V5 Belgian through the [dsmr_parser](https://github.com/ndokter/dsmr_parser) module by Nigel Dokter. - For official information about DSMR refer to: [DSMR Document](https://www.netbeheernederland.nl/dossiers/slimme-meter-15) -- For official information about the P1 port refer to: +- For official information about the P1 port refer to: [P1 Companion Standard](https://www.netbeheernederland.nl/_upload/Files/Slimme_meter_15_a727fce1f1.pdf) - For unofficial hardware connection examples refer to: [Domoticx](http://domoticx.com/p1-poort-slimme-meter-hardware/)

      @@ -35,13 +35,13 @@ This integration is known to work for: USB serial converters: - Cheap (Banggood/ebay) Generic PL2303 -- -- -- +- [Smartmeter Webshop](https://sites.google.com/site/nta8130p1smartmeter/webshop) +- [SOS Solutions](https://www.sossolutions.nl/slimme-meter-kabel) +- [AliExpress](https://nl.aliexpress.com/item/32945187155.html) Serial to network proxies: -- ser2net - +- [ser2net](http://ser2net.sourceforge.net) DIY solutions (ESP8266 based): diff --git a/source/_integrations/dwd_weather_warnings.markdown b/source/_integrations/dwd_weather_warnings.markdown index cb1bd1c88b8..f5f8a08635a 100644 --- a/source/_integrations/dwd_weather_warnings.markdown +++ b/source/_integrations/dwd_weather_warnings.markdown @@ -1,5 +1,5 @@ --- -title: Deutsche Wetter Dienst (DWD) Weather Warnings +title: Deutscher Wetterdienst (DWD) Weather Warnings description: Instructions on how to integrate Deutsche Wetter Dienst weather warnings into Home Assistant. ha_category: - Weather diff --git a/source/_integrations/edl21.markdown b/source/_integrations/edl21.markdown index a154f36e026..469634a26a0 100644 --- a/source/_integrations/edl21.markdown +++ b/source/_integrations/edl21.markdown @@ -3,6 +3,7 @@ title: EDL21 description: Instructions on how to integrate SML-based EDL21 smart meters into Home Assistant. ha_category: - Sensor +ha_iot_class: Local Push ha_release: 0.107 ha_domain: edl21 ha_codeowners: diff --git a/source/_integrations/elkm1.markdown b/source/_integrations/elkm1.markdown index 6fd7eb3495c..43d25ae5434 100644 --- a/source/_integrations/elkm1.markdown +++ b/source/_integrations/elkm1.markdown @@ -31,8 +31,89 @@ There is currently support for the following device types within Home Assistant: - **Sensor** - Elk-M1 counters, keypads, panel, settings, and zones are represented as `sensor` entities. - **Switch** - Elk-M1 outputs are represented as `switch` entities. -If you would like your `alarm_control_panel` devices to keep track of the user whose code was last used to change the status of that partition (via the attributes `changed_by` and `changed_by_id`) you must configure your Elk's global setting location 35, “System Log Data Update” transmission, so that the M1 sends the updated partition status whenever it changes. (It may work anyway if you have exactly one area configured and do not have that setting enabled.) +## ElkM1 Configuration and Version +In order for the ElkM1 integration to work to its fullest with Home Assistant the +ElkM1 panel must be configured correctly. This section describes the configuration +required on the ElkM1 panel. + +### ElkM1 Version + +ElkM1 should be running: + +- Version 4.6.8, or +- Version 5.2.0 or higher. + +Force arm away and stay are available in 5.3.0 or higher. + +Many features will work with lower versions of the ElkM1. Check the "ElkM1 RS232 Protocol" manual for details. + +### Global Setting 35 + +The ElkM1 integration tracks the user number and name of the last user name to +arm or disarm the panel. The `changed_by` and `changed_by_id` attributes of +the `alarm_control_panel` hold those two attributes. + +On the ElkM1 panel Global Setting 35, "Transmit Event Log" must be +enabled for this to fully work. + +Note that without Global Setting 35 set and in a single area system, +`changed_by` and `changed_by_id` are updated when a user enters a valid +code on a physical keypad. + +### Global Setting 36 — 40 + +If you are using the features below then these respective global options +should be enabled: + +| Option # | Option Name | Description | +| ---------------------- | -------- | ----------- | +| 36 | Transmit Zone Changes | If you are using Zones this allows Home Assistant to track the status of the Zones. +| 37 | Transmit Output Changes | If you are using Outputs this allows Home Assistant to track the status of the Outputs. +| 38 | Transmit Automation Task Changes | If you are using ElkM1 Tasks this allows Home Assistant to track the status of the Tasks. +| 39 | Transmit Light Changes | If you are using ElkM1 Lights this allows Home Assistant to track the status of the lights. +| 40 | Transmit Keypad Changes | Oddly, this option tracks keypad changes and alarm status. If you are wishing to track keypresses on ElkM1 keypad or if you are wishing to track the armed, disarmed, and alarm state of the ElkM1 then this option should be set. + +## System Trouble Status + +The ElkM1 is able to report general system trouble statuses. This is +reported using the `system_trouble_status` attribute of the +panel sensor (often named `sensor.elkm1`) in Home Assistant. + +The format of the `system_trouble_status` attribute is a comma separated list +of the active troubles. Only active trouble statuses are in the list. +If the trouble is for a zone then `zone ` is appended to the trouble name. + +For example, if zone 42 wireless sensor lost communication with the panel then +`system_trouble_status` would be "Lost Transmitter zone 42". If in addition there +was an AC failure then `system_trouble_status` would be the string +"AC Fail, Lost Transmitter zone 42". + +The complete list of trouble statuses are: + +- AC Fail +- Box Tamper (zone is part of status) +- Fail To Communicate +- EEProm Memory Error +- Low Battery Control +- Transmitter Low Battery (zone is part of status) +- Over Current +- Telephone Fault +- Output 2 +- Missing Keypad +- Zone Expander +- Output Expander +- ELKRP Remote Access +- Common Area Not Armed +- Flash Memory Error +- Security Alert (zone is part of status) +- Serial Port Expander +- Lost Transmitter (zone is part of status) +- GE Smoke CleanMe +- Ethernet +- Display Message In Keypad Line 1 +- Display Message In Keypad Line 2 +- Fire (zone is part of status) ## Configuration @@ -319,3 +400,56 @@ elkm1: thermostat: enabled: false ``` + +## Services + +Besides the standard Home Assistant services for Climate, Light, Scene, Sensor, +and Switch the ElkM1 integration offers these additional services: + +- `elkm1.alarm_arm_home_instant` +- `elkm1.alarm_arm_night_instant` +- `elkm1.alarm_arm_vacation` +- `elkm1.alarm_display_message` +- `elkm1.speak_phrase` +- `elkm1.speak_word` + +### Services `elkm1.alarm_arm_home_instant`, `elkm1.alarm_arm_night_instant`, and `elkm1.alarm_arm_vacation` + +Arms the ElkM1 area in "home instant", "night instant", or "vacation" modes +respectively. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | yes | ElkM1 area which to arm. +| `code` | no | Alarm code to arm the system (4 or 6 digits). + +### Service `elkm1.alarm_display_message` + +Display text on an area's keypads. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | yes | ElkM1 area which to display the message. +| `clear` | yes | 0=clear message, 1=clear message with * key, 2=Display until timeout; default 2 +| `beep` | yes | 0=no beep, 1=beep; default 0 +| `timeout` | yes | Time to display message, 0=forever, max 65535, default 0 +| `line1` | yes | Up to 16 characters of text (truncated if too long). Default blank. +| `line2` | yes | Up to 16 characters of text (truncated if too long). Default blank. + +### Service `elkm1.speak_phrase` + +Speak a phrase. The list of phrases is defined in the ElkM1 ASCII Protocol documentation. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `phrase` | no | Phrase to speak. +| `prefix` | yes | Prefix to identify panel when multiple panels configured. + +### Service `elkm1.speak_word` + +Speak a word. The list of words is defined in the ElkM1 ASCII Protocol documentation. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `word` | no | Word to speak. +| `prefix` | yes | Prefix to identify panel when multiple panels configured. diff --git a/source/_integrations/emoncms_history.markdown b/source/_integrations/emoncms_history.markdown index 6f8c626bae3..ca21304b1ea 100644 --- a/source/_integrations/emoncms_history.markdown +++ b/source/_integrations/emoncms_history.markdown @@ -3,6 +3,7 @@ title: Emoncms History description: Instructions on how to integrate Emoncms history into Home Assistant. ha_category: - History +ha_iot_class: Local Polling ha_release: 0.31 ha_domain: emoncms_history --- diff --git a/source/_integrations/facebox.markdown b/source/_integrations/facebox.markdown index f6fb9632396..8bea4a1c80c 100644 --- a/source/_integrations/facebox.markdown +++ b/source/_integrations/facebox.markdown @@ -3,6 +3,7 @@ title: Facebox description: Detect and recognize faces with Facebox. ha_category: - Image Processing +ha_iot_class: Local Push ha_release: 0.7 ha_domain: facebox --- diff --git a/source/_integrations/fan.template.markdown b/source/_integrations/fan.template.markdown index dfade983c16..aef26db1021 100644 --- a/source/_integrations/fan.template.markdown +++ b/source/_integrations/fan.template.markdown @@ -64,7 +64,7 @@ fan: required: false type: string unique_id: - description: An ID that uniquely identifies this fan. Set this to an unique value to allow customisation trough the UI. + description: An ID that uniquely identifies this fan. Set this to a unique value to allow customization through the UI. required: false type: string value_template: diff --git a/source/_integrations/ffmpeg_motion.markdown b/source/_integrations/ffmpeg_motion.markdown index 3d4ccdabcc7..8624719c982 100644 --- a/source/_integrations/ffmpeg_motion.markdown +++ b/source/_integrations/ffmpeg_motion.markdown @@ -3,6 +3,7 @@ title: FFmpeg Motion description: Instructions on how to integrate an FFmpeg-based motion binary sensor ha_category: - Image Processing +ha_iot_class: Calculated ha_release: 0.27 ha_domain: ffmpeg_motion --- diff --git a/source/_integrations/ffmpeg_noise.markdown b/source/_integrations/ffmpeg_noise.markdown index 4a0166f4cf8..e95160e3d81 100644 --- a/source/_integrations/ffmpeg_noise.markdown +++ b/source/_integrations/ffmpeg_noise.markdown @@ -3,6 +3,7 @@ title: FFmpeg Noise description: Instructions on how to integrate an FFmpeg-based noise binary sensor ha_category: - Image Processing +ha_iot_class: Calculated ha_release: 0.27 ha_domain: ffmpeg_noise --- diff --git a/source/_integrations/fibaro.markdown b/source/_integrations/fibaro.markdown index 9279449322b..139836ad766 100644 --- a/source/_integrations/fibaro.markdown +++ b/source/_integrations/fibaro.markdown @@ -88,4 +88,4 @@ device_config: ### Using Z-Wave devices in automation -If you want to use a Z-Wave device from the Fibaro controller in Home Assistant automation, you'll need the entity id. In the Home Assistant UI you'll find all entities listed under the service developer tool icon icon of the Developer Tools section. Look for entities that contain 'fibaro_id' in their attributes, and you'll find the entity id on the left. +If you want to use a Z-Wave device from the Fibaro controller in Home Assistant automation, you'll need the entity id. In the Home Assistant UI you'll find all entities listed under **Developer Tools** -> **States**. Look for entities that contain 'fibaro_id' in their attributes, and you'll find the entity id on the left. diff --git a/source/_integrations/flo.markdown b/source/_integrations/flo.markdown index c8027192faa..2e40276eaa8 100644 --- a/source/_integrations/flo.markdown +++ b/source/_integrations/flo.markdown @@ -1,7 +1,6 @@ --- title: Flo description: Instructions on how to integrate Flo by Moen into Home Assistant. -ha_release: 0.115 ha_category: - Binary Sensor - Sensor @@ -10,6 +9,8 @@ ha_config_flow: true ha_codeowners: - '@dmulcahey' ha_domain: flo +ha_iot_class: Cloud Polling +ha_release: 0.115 --- The `flo` integration integrates diff --git a/source/_integrations/flock.markdown b/source/_integrations/flock.markdown index 07978084b99..6cb8b342114 100644 --- a/source/_integrations/flock.markdown +++ b/source/_integrations/flock.markdown @@ -3,6 +3,7 @@ title: Flock description: Instructions on how to add Flock notifications to Home Assistant. ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: 0.71 ha_codeowners: - '@fabaff' diff --git a/source/_integrations/flux.markdown b/source/_integrations/flux.markdown index c6bcb3f9050..ad8fb6ca687 100644 --- a/source/_integrations/flux.markdown +++ b/source/_integrations/flux.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: 0.21 ha_quality_scale: internal ha_domain: flux +ha_iot_class: Calculated --- The `flux` switch platform will change the temperature of your lights similar to the way flux works on your computer, using circadian rhythm. They will be bright during the day, and gradually fade to a red/orange at night. The `flux` switch restores its last state after startup. diff --git a/source/_integrations/free_mobile.markdown b/source/_integrations/free_mobile.markdown index 47a3e4b786f..a091a6139d3 100644 --- a/source/_integrations/free_mobile.markdown +++ b/source/_integrations/free_mobile.markdown @@ -4,6 +4,7 @@ description: Instructions on how to add user notifications to Home Assistant. ha_category: - Notifications ha_release: 0.11 +ha_iot_class: Cloud Push ha_domain: free_mobile --- diff --git a/source/_integrations/freedns.markdown b/source/_integrations/freedns.markdown index 7e03d2edcb0..5af50b0bfe9 100644 --- a/source/_integrations/freedns.markdown +++ b/source/_integrations/freedns.markdown @@ -3,6 +3,7 @@ title: FreeDNS description: Keep your DNS record up to date with FreeDNS. ha_category: - Network +ha_iot_class: Cloud Push ha_release: 0.67 ha_domain: freedns --- diff --git a/source/_integrations/futurenow.markdown b/source/_integrations/futurenow.markdown index ed726961d70..488ec4f4e09 100644 --- a/source/_integrations/futurenow.markdown +++ b/source/_integrations/futurenow.markdown @@ -4,6 +4,7 @@ description: Instructions on how to set up P5 FutureNow relay/dimmer units as li logo: p5.png ha_category: - Light +ha_iot_class: Local Polling ha_release: 0.75 ha_domain: futurenow --- diff --git a/source/_integrations/garadget.markdown b/source/_integrations/garadget.markdown index d9bfcaef045..be4a1501fe7 100644 --- a/source/_integrations/garadget.markdown +++ b/source/_integrations/garadget.markdown @@ -134,4 +134,7 @@ cover: state_topic: "garadget/device_name/status" payload_open: "open" payload_close: "close" + value_template: "{{ value_json.status }}" ``` + +Replace device_name with the name of the device provided when configuring garadget. diff --git a/source/_integrations/geo_location.markdown b/source/_integrations/geo_location.markdown index 9ac2f85b2d3..cffd62c9c0a 100644 --- a/source/_integrations/geo_location.markdown +++ b/source/_integrations/geo_location.markdown @@ -6,6 +6,7 @@ ha_category: logo: geo_location.png ha_release: 0.78 ha_domain: geo_location +ha_iot_class: ~ --- Geolocation aware entities are typically related to events in the real world in the vicinity of Home Assistant's location, like for example weather events, bush fires or earthquakes. diff --git a/source/_integrations/gntp.markdown b/source/_integrations/gntp.markdown index d2781d7a9ee..c5df8cd0fd5 100644 --- a/source/_integrations/gntp.markdown +++ b/source/_integrations/gntp.markdown @@ -3,6 +3,7 @@ title: Growl (GnGNTP) description: Instructions for adding GNTP/Growl notifications to Home Assistant. ha_category: - Notifications +ha_iot_class: Local Push ha_release: 0.16 ha_domain: gntp --- diff --git a/source/_integrations/goalfeed.markdown b/source/_integrations/goalfeed.markdown index 43c19f889b2..7ce57a62bdc 100644 --- a/source/_integrations/goalfeed.markdown +++ b/source/_integrations/goalfeed.markdown @@ -4,6 +4,7 @@ description: Instructions on how to setup Goalfeed events within Home Assistant. logo: goalfeed.png ha_category: - Other +ha_iot_class: Cloud Push ha_release: 0.63 ha_domain: goalfeed --- diff --git a/source/_integrations/goalzero.markdown b/source/_integrations/goalzero.markdown index eaf73c6c369..b8e30648e1a 100644 --- a/source/_integrations/goalzero.markdown +++ b/source/_integrations/goalzero.markdown @@ -1,23 +1,24 @@ ---- -title: GoalZero -description: Instructions on how to integrate Goal Zero Yeti with Home Assistant -ha_category: - - Energy -ha_release: 0.116 -ha_config_flow: true -ha_domain: goalzero -ha_codeowners: - - '@tkdrob' ---- - -This `goalzero` integration pulls data from a Wifi enabled Goal Zero Yeti. - -## Configuration - -Go to the integrations page in your configuration and click on new integration -> Goal Zero Yeti. - -## Integration Entities - -Each added configuration entry will create the following sensors: - -`v12PortStatus`, `usbPortStatus`, `acPortStatus`, `backlight`, `app_online`, `isCharging` +--- +title: Goal Zero Yeti +description: Instructions on how to integrate Goal Zero Yeti with Home Assistant +ha_category: + - Energy +ha_iot_class: Local Polling +ha_release: 0.116 +ha_config_flow: true +ha_domain: goalzero +ha_codeowners: + - '@tkdrob' +--- + +This `goalzero` integration pulls data from a Wifi enabled Goal Zero Yeti. + +## Configuration + +Go to the integrations page in your configuration and click on new integration -> Goal Zero Yeti. + +## Integration Entities + +Each added configuration entry will create the following sensors: + +`v12PortStatus`, `usbPortStatus`, `acPortStatus`, `backlight`, `app_online`, `isCharging` diff --git a/source/_integrations/google_assistant.markdown b/source/_integrations/google_assistant.markdown index 47dd2a41866..d38ccb076d2 100644 --- a/source/_integrations/google_assistant.markdown +++ b/source/_integrations/google_assistant.markdown @@ -29,7 +29,7 @@ To use Google Assistant, your Home Assistant configuration has to be [externally

      -You will need to create a service account [Create Service account key](https://console.cloud.google.com/apis/credentials/serviceaccountkey) which allows you to update devices without unlinking and relinking an account (see [below](#troubleshooting-the-request_sync-service)). If you don't provide the service account, the `google_assistant.request_sync` service is not exposed. It is recommended to set up this configuration key as it also allows the usage of the following command, "Ok Google, sync my devices". Once you have set up this component, you will need to call this service (or command) each time you add a new device in Home Assistant that you wish to control via the Google Assistant integration. See Step 2 after the note for more details. +You will need to create a service account [Create Service account key](https://console.cloud.google.com/apis/credentials/serviceaccountkey) which allows you to update devices without unlinking and relinking an account (see [below](#troubleshooting)). If you don't provide the service account, the `google_assistant.request_sync` service is not exposed. It is recommended to set up this configuration key as it also allows the usage of the following command, "Ok Google, sync my devices". Once you have set up this component, you will need to call this service (or command) each time you add a new device in Home Assistant that you wish to control via the Google Assistant integration. See Step 2 after the note for more details. 1. Create a new project in the [Actions on Google console](https://console.actions.google.com/). 1. Click `New Project` and give your project a name. @@ -253,6 +253,8 @@ The `request_sync` service may fail with a 404 if the `project_id` of the HomeGr 4. Once you begin to create a new `service_account` in the [Google Cloud API Console], ensure you select the project created in [Actions on Google console] by verifying the `project_id`. 5. Enable HomeGraph API to the new project. +Verify that the Google Assistant is available on `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant` If it is working it should return `405: Method Not Allowed` when opened in a browser or via curl. + #### 403 errors on request sync The `request_sync` service may fail with a 403 if the HomeGraph API is not enabled. Go to [Google API Console](https://console.cloud.google.com/apis/api/homegraph.googleapis.com/overview) and verify that HomeGraph API is enabled for your project. diff --git a/source/_integrations/google_cloud.markdown b/source/_integrations/google_cloud.markdown index da8dadfe234..25043f7967e 100644 --- a/source/_integrations/google_cloud.markdown +++ b/source/_integrations/google_cloud.markdown @@ -3,6 +3,7 @@ title: Google Cloud Platform description: Google Cloud Platform integration. ha_category: Text-to-speech ha_release: 0.95 +ha_iot_class: Cloud Push ha_codeowners: - '@lufton' ha_domain: google_cloud diff --git a/source/_integrations/google_pubsub.markdown b/source/_integrations/google_pubsub.markdown index 9fa3a821c12..58512256a91 100644 --- a/source/_integrations/google_pubsub.markdown +++ b/source/_integrations/google_pubsub.markdown @@ -4,6 +4,7 @@ description: Setup for Google Pub/Sub integration ha_category: - History ha_release: 0.88 +ha_iot_class: Cloud Push ha_domain: google_pubsub --- diff --git a/source/_integrations/google_translate.markdown b/source/_integrations/google_translate.markdown index b3bfd55ed7e..41dc6705cf2 100644 --- a/source/_integrations/google_translate.markdown +++ b/source/_integrations/google_translate.markdown @@ -4,6 +4,7 @@ description: Instructions on how to setup Google Translate Text-to-Speech with H ha_category: - Text-to-speech ha_release: 0.35 +ha_iot_class: Cloud Push ha_codeowners: - '@awarecan' ha_domain: google_translate diff --git a/source/_integrations/graphite.markdown b/source/_integrations/graphite.markdown index 2ba430893f6..d758b1fb425 100644 --- a/source/_integrations/graphite.markdown +++ b/source/_integrations/graphite.markdown @@ -6,6 +6,7 @@ ha_category: - History ha_release: 0.13 ha_domain: graphite +ha_iot_class: Local Push --- The `graphite` integration records all events and state changes and feeds the data to a [graphite](http://graphite.wikidot.com/) instance. diff --git a/source/_integrations/group.markdown b/source/_integrations/group.markdown index 0d38cfa24a5..ae2a8744e1b 100644 --- a/source/_integrations/group.markdown +++ b/source/_integrations/group.markdown @@ -73,6 +73,7 @@ The system can calculate group state with entities from the following domains: * lock * media_player * person +* plant * remote * switch * vacuum diff --git a/source/_integrations/guardian.markdown b/source/_integrations/guardian.markdown index 33f422735e7..e33f507fc6b 100644 --- a/source/_integrations/guardian.markdown +++ b/source/_integrations/guardian.markdown @@ -1,6 +1,7 @@ --- title: Elexa Guardian description: Instructions on how to integrate SimpliSafe into Home Assistant. +ha_iot_class: Local Polling ha_release: '0.111' ha_category: - Binary Sensor diff --git a/source/_integrations/hangouts.markdown b/source/_integrations/hangouts.markdown index b550738840b..6ca273dc3ce 100644 --- a/source/_integrations/hangouts.markdown +++ b/source/_integrations/hangouts.markdown @@ -291,7 +291,7 @@ default_conversations: ### Finding the conversation ID -The conversations has to be precreated, the conversation id can be obtained from the `hangouts.conversations` entity, this can be found in with the states developer tool that is shown as this icon in the side bar. Using your web browsers search tool to find the `hangouts.conversations` entity. You will find something like below. +The conversations has to be precreated, the conversation id can be obtained from the `hangouts.conversations` entity, this can be found in **Developer Tools** -> **States**. Using your web browsers search tool to find the `hangouts.conversations` entity. You will find something like below. ```json 0: { diff --git a/source/_integrations/hikvisioncam.markdown b/source/_integrations/hikvisioncam.markdown index 178a21c9683..53a06ee335c 100644 --- a/source/_integrations/hikvisioncam.markdown +++ b/source/_integrations/hikvisioncam.markdown @@ -3,6 +3,7 @@ title: Hikvision description: Instructions on how to integrate Hikvision camera switches into Home Assistant. ha_category: - Switch +ha_iot_class: Local Polling ha_release: pre 0.7 ha_codeowners: - '@fbradyirl' diff --git a/source/_integrations/history.markdown b/source/_integrations/history.markdown index de4092d0c65..9dd71394246 100644 --- a/source/_integrations/history.markdown +++ b/source/_integrations/history.markdown @@ -8,6 +8,7 @@ ha_quality_scale: internal ha_codeowners: - '@home-assistant/core' ha_domain: history +ha_iot_class: ~ --- The `history` integration will track everything that is going on within Home diff --git a/source/_integrations/homematic.markdown b/source/_integrations/homematic.markdown index 807159be471..2bd51136f71 100644 --- a/source/_integrations/homematic.markdown +++ b/source/_integrations/homematic.markdown @@ -210,7 +210,7 @@ sensor: - platform: template sensors: bedroom_valve: - value_template: '{% raw %}{{ state_attr('climate.leq123456', 'Valve') }}{% endraw %}' + value_template: "{% raw %}{{ state_attr('climate.leq123456', 'valve') }}{% endraw %}" entity_id: climate.leq123456 friendly_name: 'Bedroom valve' ``` diff --git a/source/_integrations/huawei_lte.markdown b/source/_integrations/huawei_lte.markdown index 013d9ee98f9..51ae3cd0172 100644 --- a/source/_integrations/huawei_lte.markdown +++ b/source/_integrations/huawei_lte.markdown @@ -25,7 +25,7 @@ There is currently support for the following platforms within Home Assistant: - Notifications - via SMS - Sensors - device, network, signal, SMS count, traffic, and battery information - Switch - mobile data on/off -- Binary sensor - mobile and Wi-Fi connection status +- Binary sensor - mobile and Wi-Fi connection status, SMS storage full/not ## Configuration diff --git a/source/_integrations/huawei_router.markdown b/source/_integrations/huawei_router.markdown index b3860dd84dc..26667ae4fa9 100644 --- a/source/_integrations/huawei_router.markdown +++ b/source/_integrations/huawei_router.markdown @@ -33,7 +33,7 @@ host: required: true type: string username: - description: The username to login into the router (the same used trough the router's web interface). + description: The username to login into the router (the same used through the router's web interface). required: true type: string password: diff --git a/source/_integrations/humidifier.markdown b/source/_integrations/humidifier.markdown index 4b993191b8a..1ee39e3e2a0 100644 --- a/source/_integrations/humidifier.markdown +++ b/source/_integrations/humidifier.markdown @@ -9,6 +9,7 @@ ha_quality_scale: internal ha_codeowners: - '@home-assistant/core' - '@Shulyaka' +ha_iot_class: ~ --- The `humidifier` integration is built for the controlling and monitoring of humidifiers, dehumidifiers, and hygrostat devices. diff --git a/source/_integrations/hyperion.markdown b/source/_integrations/hyperion.markdown index 2f77266979d..490a1a7fc5b 100644 --- a/source/_integrations/hyperion.markdown +++ b/source/_integrations/hyperion.markdown @@ -6,10 +6,12 @@ ha_category: ha_release: 0.7.6 ha_iot_class: Local Push ha_domain: hyperion +ha_codeowners: + - '@dermotduffy' --- The `hyperion` platform allows you to integrate your -[Hyperion](https://hyperion-project.org/wiki) into Home Assistant. Hyperion is +[Hyperion](https://docs.hyperion-project.org/) into Home Assistant. Hyperion is an open source Ambilight implementation which runs on many platforms. NOTE: [Hyperion-NG](https://github.com/hyperion-project/hyperion.ng) is diff --git a/source/_integrations/ialarm.markdown b/source/_integrations/ialarm.markdown index e66a83f9415..c79b39f264a 100644 --- a/source/_integrations/ialarm.markdown +++ b/source/_integrations/ialarm.markdown @@ -4,6 +4,7 @@ description: Instructions on how to integrate iAlarms alarms into Home Assistant logo: antifurto365-ialarm.png ha_category: - Alarm +ha_iot_class: Local Polling ha_release: '0.60' ha_domain: ialarm --- diff --git a/source/_integrations/image.markdown b/source/_integrations/image.markdown index 31b64915468..7ec9b7f9c7f 100644 --- a/source/_integrations/image.markdown +++ b/source/_integrations/image.markdown @@ -7,6 +7,7 @@ ha_release: 0.115 ha_codeowners: - '@home-assistant/core' ha_domain: image +ha_quality_scale: internal --- The Image integration allows Home Assistant to handle image assets in Home Assistant, for example, diff --git a/source/_integrations/imap.markdown b/source/_integrations/imap.markdown index 69ab4df1c7d..75faa86a979 100644 --- a/source/_integrations/imap.markdown +++ b/source/_integrations/imap.markdown @@ -62,6 +62,17 @@ charset: type: string {% endconfiguration %} +### Gmail with App Password + +If you’re going to use Gmail, it’s always good practice to create a [App Password](https://support.google.com/mail/answer/185833?hl=en). + +1. Go to your [Google Account](https://myaccount.google.com/) +2. Select **Security** +3. Under “Signing in to Google” select **App Passwords** +4. Sign in to your Account, and create a new App Password for Gmail. + +You can now use this as your password for Gmail, in your configuration. + ### Configuring IMAP Searches By default, this integration will count unread emails. By configuring the search string, you can count other results, for example: @@ -81,6 +92,8 @@ sensor: username: YOUR_USERNAME password: YOUR_PASSWORD search: FROM , SUBJECT + # Or use X-GM-RAW search-term like this, to find unread emails from the last 7 days in your inbox + # search: "X-GM-RAW 'in: inbox newer_than:7d is:unread'" # Example configuration.yaml entry for Office 365 sensor: diff --git a/source/_integrations/incomfort.markdown b/source/_integrations/incomfort.markdown index fd5065aabd2..13304ee7f59 100644 --- a/source/_integrations/incomfort.markdown +++ b/source/_integrations/incomfort.markdown @@ -86,11 +86,11 @@ host: required: true type: string username: - description: The username of the Lan2RF gateway, if any. + description: "The username of the Lan2RF gateway, if any. Most likely: `admin`." required: inclusive type: string password: - description: The password of the Lan2RF gateway, if any. + description: "The password of the Lan2RF gateway, if any. Most likely: `intergas`." required: inclusive type: string {% endconfiguration %} diff --git a/source/_integrations/insteon.markdown b/source/_integrations/insteon.markdown index a6928543e7b..4fedce8b697 100644 --- a/source/_integrations/insteon.markdown +++ b/source/_integrations/insteon.markdown @@ -48,7 +48,7 @@ In order for a device to be discovered, it must be linked to the INSTEON Modem a ## Linking Devices to the INSTEON Modem -In order for any two Insteon devices to talk with one another, they must be linked. For an overview of device linking, please read the Insteon page on [understanding linking]. The Insteon Modem module supports All-Linking through [Development Tools] service calls. The following services are available: +In order for any two Insteon devices to talk with one another, they must be linked. For an overview of device linking, please read the Insteon page on [understanding linking]. The Insteon Modem module supports All-Linking through [Developer Tools] service calls. The following services are available: - **insteon.add_all_link**: Puts the Insteon Modem (IM) into All-Linking mode. The IM can be set as a controller or a responder. If the IM is a controller, put the IM into linking mode then press the SET button on the device. If the IM is a responder, press the SET button on the device then put the IM into linking mode. - **insteon.delete_all_link**: Tells the Insteon Modem (IM) to remove an All-Link record from the All-Link Database of the IM and a device. Once the IM is set to delete the link, press the SET button on the corresponding device to complete the process. @@ -59,7 +59,7 @@ In order for any two Insteon devices to talk with one another, they must be link If you are looking for more advanced options, you can use the [insteon_tools] command-line tool that is distributed with the [pyinsteon] Python module. Please see the documentation on the [pyinsteon] GitHub site. Alternatively, you can download [HouseLinc], which runs on any Windows PC, or you can use [Insteon Terminal] which is open source and runs on most platforms. SmartHome no longer supports HouseLinc, but it still works. Insteon Terminal is a very useful tool but please read the disclaimers carefully, they are important. [understanding linking]: https://www.insteon.com/support-knowledgebase/2015/1/28/understanding-linking -[Development Tools]: /docs/tools/dev-tools/ +[Developer Tools]: /docs/tools/dev-tools/ [HouseLinc]: https://www.smarthome.com/houselinc.html [Insteon Terminal]: https://github.com/pfrommerd/insteon-terminal [insteon_tools]: https://github.com/pyinsteon/pyinsteon @@ -285,7 +285,7 @@ In order for a device to be discovered, it must be linked to the INSTEON Modem a ### Linking Devices to the INSTEON Modem -In order for any two Insteon devices to talk with one another, they must be linked. For an overview of device linking, please read the Insteon page on [understanding linking]. The Insteon Modem module supports All-Linking through [Development Tools] service calls. The following services are available: +In order for any two Insteon devices to talk with one another, they must be linked. For an overview of device linking, please read the Insteon page on [understanding linking]. The Insteon Modem module supports All-Linking through [Developer Tools] service calls. The following services are available: - **insteon.add_all_link**: Puts the Insteon Modem (IM) into All-Linking mode. The IM can be set as a controller or a responder. If the IM is a controller, put the IM into linking mode then press the SET button on the device. If the IM is a responder, press the SET button on the device then put the IM into linking mode. - **insteon.delete_all_link**: Tells the Insteon Modem (IM) to remove an All-Link record from the All-Link Database of the IM and a device. Once the IM is set to delete the link, press the SET button on the corresponding device to complete the process. @@ -296,7 +296,7 @@ In order for any two Insteon devices to talk with one another, they must be link If you are looking for more advanced options, you can use the [insteon_tools] command line tool that is distributed with the [pyinsteon] Python module. Please see the documentation on the [pyinsteon] GitHub site. Alternatively, you can download [HouseLinc] which runs on any Windows PC, or you can use [Insteon Terminal] which is open source and runs on most platforms. SmartHome no longer supports HouseLinc, but it still works. Insteon Terminal is a very useful tool but please read the disclaimers carefully, they are important. [understanding linking]: https://www.insteon.com/support-knowledgebase/2015/1/28/understanding-linking -[Development Tools]: /docs/tools/dev-tools/ +[Developer Tools]: /docs/tools/dev-tools/ [HouseLinc]: https://www.smarthome.com/houselinc.html [Insteon Terminal]: https://github.com/pfrommerd/insteon-terminal [insteon_tools]: https://github.com/pyinsteon/pyinsteon diff --git a/source/_integrations/joaoapps_join.markdown b/source/_integrations/joaoapps_join.markdown index f438c181ba3..baff143eb71 100644 --- a/source/_integrations/joaoapps_join.markdown +++ b/source/_integrations/joaoapps_join.markdown @@ -4,6 +4,7 @@ description: Instructions for how to integrate the Join by Joaoapps service with ha_category: - Hub - Notifications +ha_iot_class: Cloud Push ha_release: 0.24 ha_domain: joaoapps_join --- diff --git a/source/_integrations/keba.markdown b/source/_integrations/keba.markdown index 6f7c9b1f17c..f036811b0aa 100644 --- a/source/_integrations/keba.markdown +++ b/source/_integrations/keba.markdown @@ -6,6 +6,7 @@ ha_category: - Lock - Sensor - Notifications +ha_iot_class: Local Polling ha_release: 0.98 ha_codeowners: - '@dannerph' diff --git a/source/_integrations/knx.markdown b/source/_integrations/knx.markdown index 1bc5b270d95..1706e237c06 100644 --- a/source/_integrations/knx.markdown +++ b/source/_integrations/knx.markdown @@ -19,6 +19,7 @@ ha_codeowners: - '@farmio' - '@marvin-w' ha_domain: knx +ha_quality_scale: silver --- The [KNX](https://www.knx.org) integration for Home Assistant allows you to connect to KNX/IP devices. @@ -285,6 +286,11 @@ reset_after: description: Reset back to OFF state after specified milliseconds. required: false type: integer +ignore_internal_state: + description: If set to true the update callbacks are always executed regardless of the current binary sensor state. If some of your automations are triggered multiple times make sure this setting is False. + required: false + type: boolean + default: True context_timeout: description: The time in seconds between multiple identical telegram payloads would count towards the internal counter that is used for automations. Ex. You have automations in place that trigger your lights on button press and another set of lights if you click that button twice. This setting defines the time that a second button press would count toward, so if you set this 3.0 you can take up to 3 seconds in order to trigger the second button press. Maximum value is 10.0. required: false @@ -411,8 +417,8 @@ knx: `setpoint_shift_mode` allows the two following DPTs to be used: -- DPT6.002 (for 1 byte signed integer) -- DPT9.002 (for 2 byte float) +- DPT6002 (for 1 byte signed integer) +- DPT9002 (for 2 byte float) Example: diff --git a/source/_integrations/kodi.markdown b/source/_integrations/kodi.markdown index c8daef3b3a6..dfe5c051b9f 100644 --- a/source/_integrations/kodi.markdown +++ b/source/_integrations/kodi.markdown @@ -8,6 +8,7 @@ ha_release: pre 0.7 ha_iot_class: Local Push ha_codeowners: - '@OnFreund' + - '@cgtobi' ha_domain: kodi ha_config_flow: true --- @@ -35,7 +36,34 @@ If you do not remove it, your configuration will be imported with the following ### Turning On/Off -You can customize your turn on and off actions through automations. Simply use the relevant Kodi device triggers and your automation will be called to perform the `turn_on` or `turn_off` sequence. +You can customize your turn on and off actions through automations. Simply use the relevant Kodi device triggers and your automation will be called to perform the `turn_on` or `turn_off` sequence; see the [Kodi turn on/off samples](#kodi-turn-onoff-samples) section for scripts that can be used. + +These automations can be configured through the UI (see [Device Triggers](/automation/trigger/#device-triggers) for automations). If you prefer YAML, you'll need to get the device ID from the UI automation editor. Automations would be of the form: + +```yaml +automation: + - id: kodi_turn_on + alias: "Kodi: turn on" + trigger: + - platform: device + device_id: !secret kodi_device_id + domain: kodi + entity_id: media_player.kodi + type: turn_on + action: + - service: script.kodi_turn_on + + - id: kodi_turn_off + alias: "Kodi: turn off" + trigger: + - platform: device + device_id: !secret kodi_device_id + domain: kodi + entity_id: media_player.kodi + type: turn_off + action: + - service: script.kodi_turn_off +``` ### Services @@ -74,17 +102,16 @@ result: ### Kodi turn on/off samples -With the `turn_on_action` and `turn_off_action` parameters you can run any combination of Home Assistant actions to turn on/off your Kodi instance. Here are a few examples of this usage, including the **migration instructions for the old `turn_off_action` list of options**. +The following scripts can be used in automations for turning on/off your Kodi instance; see [Turning on/off](#turning-onoff). You could also simply use these sequences directly in the automations without creating scripts. #### Turn on Kodi with Wake on LAN With this configuration, when calling `media_player/turn_on` on the Kodi device, a _magic packet_ will be sent to the specified MAC address. To use this service, first you need to configuration the [`wake_on_lan`](/integrations/wake_on_lan) integration in Home Assistant, which is achieved simply by adding `wake_on_lan:` to your `configuration.yaml`. ```yaml -media_player: - - platform: kodi - host: 192.168.0.123 - turn_on_action: +script: + turn_on_kodi_with_wol: + sequence: - service: wake_on_lan.send_magic_packet data: mac: aa:bb:cc:dd:ee:ff @@ -95,69 +122,64 @@ media_player: Here are the equivalent ways to configure each of the old options to turn off Kodi (`quit`, `hibernate`, `suspend`, `reboot`, or `shutdown`): -- **Quit** method (before was `turn_off_action: quit`) +- **Quit** method ```yaml -media_player: - - platform: kodi - host: 192.168.0.123 - turn_off_action: - service: kodi.call_method - data: - entity_id: media_player.kodi - method: Application.Quit +script: + kodi_quit: + sequence: + - service: kodi.call_method + data: + entity_id: media_player.kodi + method: Application.Quit ``` -- **Hibernate** method (before was `turn_off_action: hibernate`) +- **Hibernate** method ```yaml -media_player: - - platform: kodi - host: 192.168.0.123 - turn_off_action: - service: kodi.call_method - data: - entity_id: media_player.kodi - method: System.Hibernate +script: + kodi_hibernate: + sequence: + - service: kodi.call_method + data: + entity_id: media_player.kodi + method: System.Hibernate ``` -- **Suspend** method (before was `turn_off_action: suspend`) +- **Suspend** method ```yaml -media_player: - - platform: kodi - host: 192.168.0.123 - turn_off_action: - service: kodi.call_method - data: - entity_id: media_player.kodi - method: System.Suspend +script: + kodi_suspend: + sequence: + - service: kodi.call_method + data: + entity_id: media_player.kodi + method: System.Suspend ``` -- **Reboot** method (before was `turn_off_action: reboot`) +- **Reboot** method ```yaml -media_player: - - platform: kodi - host: 192.168.0.123 - turn_off_action: - service: kodi.call_method - data: - entity_id: media_player.kodi - method: System.Reboot +script: + kodi_reboot: + sequence: + - service: kodi.call_method + data: + entity_id: media_player.kodi + method: System.Reboot ``` -- **Shutdown** method (before was `turn_off_action: shutdown`) +- **Shutdown** method ```yaml -media_player: - - platform: kodi - host: 192.168.0.123 - turn_off_action: - service: kodi.call_method - data: - entity_id: media_player.kodi - method: System.Shutdown +script: + kodi_shutdown: + sequence: + - service: kodi.call_method + data: + entity_id: media_player.kodi + method: System.Shutdown ``` #### Turn on and off the TV with the Kodi JSON-CEC Add-on @@ -165,28 +187,29 @@ media_player: For Kodi devices running 24/7 attached to a CEC capable TV (OSMC / OpenElec and systems alike running in Rasperry Pi's, for example), this configuration enables the optimal way to turn on/off the attached TV from Home Assistant while Kodi is always active and ready: ```yaml -media_player: - - platform: kodi - host: 192.168.0.123 - turn_on_action: - service: kodi.call_method - data: - entity_id: media_player.kodi - method: Addons.ExecuteAddon - addonid: script.json-cec - params: - command: activate - turn_off_action: - - service: media_player.media_stop - data: - entity_id: media_player.kodi +script: + turn_on_kodi_with_cec: + sequence: - service: kodi.call_method data: entity_id: media_player.kodi method: Addons.ExecuteAddon addonid: script.json-cec params: - command: standby + command: activate + + turn_off_kodi_with_cec: + sequence: + - service: media_player.media_stop + data: + entity_id: media_player.kodi + - service: kodi.call_method + data: + entity_id: media_player.kodi + method: Addons.ExecuteAddon + addonid: script.json-cec + params: + command: standby ```
      diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown index ff429c1d3fb..3f853699c9b 100644 --- a/source/_integrations/konnected.markdown +++ b/source/_integrations/konnected.markdown @@ -6,6 +6,7 @@ ha_category: - Binary Sensor - Switch - Sensor +ha_iot_class: Local Polling ha_release: '0.70' ha_codeowners: - '@heythisisnate' @@ -304,7 +305,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 on the _Entity Registry_ page (under _Configuration_). +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**. Unique IDs are internally generated as follows: diff --git a/source/_integrations/lametric.markdown b/source/_integrations/lametric.markdown index 99b74bcf626..baa2dc72c3f 100644 --- a/source/_integrations/lametric.markdown +++ b/source/_integrations/lametric.markdown @@ -5,6 +5,7 @@ logo: lametric.png ha_category: - Hub - Notifications +ha_iot_class: Cloud Push ha_release: 0.49 ha_codeowners: - '@robbiet480' @@ -68,27 +69,26 @@ lifetime: type: integer default: 10 icon: - description: An icon or animation. + description: An icon or animation. List of all icons available at [https://developer.lametric.com/icons](https://developer.lametric.com/icons). Note that icons always begin with "i" while animations begin with "a". This is part of the name, you can't just use the number! required: false type: string cycles: - description: Defines how often the notification is displayed. + description: Defines how long the notification will be displayed. Set to 0 to require manual dismissal required: false type: integer default: 1 priority: - description: Defines the priority of the notification. + description: Defines the priority of the notification. Allowed values are info, warning, and critical required: false type: string default: warning icon_type: - description: Defines the nature of notification. + description: Defines the nature of notification. Allowed values are none, info, and alert required: false type: string default: info {% endconfiguration %} -Check out the list of all icons at [https://developer.lametric.com/icons](https://developer.lametric.com/icons). Note that icons always begin with "i" while animations begin with "a". This is part of the name, you can't just use the number! ## Examples diff --git a/source/_integrations/lannouncer.markdown b/source/_integrations/lannouncer.markdown index 464ee1d6e14..9f0661c0c33 100644 --- a/source/_integrations/lannouncer.markdown +++ b/source/_integrations/lannouncer.markdown @@ -1,9 +1,9 @@ --- title: LANnouncer description: Instructions on how to add Lannouncer notifications to Home Assistant. -logo: lannouncer.png ha_category: - Notifications +ha_iot_class: Local Push ha_release: 0.36 ha_domain: lannouncer --- diff --git a/source/_integrations/lifx_cloud.markdown b/source/_integrations/lifx_cloud.markdown index 992047dd37f..f587f6f9c76 100644 --- a/source/_integrations/lifx_cloud.markdown +++ b/source/_integrations/lifx_cloud.markdown @@ -4,6 +4,7 @@ description: Instructions on using native LIFX scenes with Home Assistant. logo: lifx.png ha_category: - Scene +ha_iot_class: Cloud Push ha_release: 0.43 ha_domain: lifx_cloud --- diff --git a/source/_integrations/light.markdown b/source/_integrations/light.markdown index bc739ce0243..85b9bad2729 100644 --- a/source/_integrations/light.markdown +++ b/source/_integrations/light.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: pre 0.7 ha_quality_scale: internal ha_domain: light +ha_iot_class: ~ --- This integration allows you to track and control various light bulbs. Read the integration documentation for your particular light hardware to learn how to enable it. diff --git a/source/_integrations/light.template.markdown b/source/_integrations/light.template.markdown index 3b2741af6d0..43499135117 100644 --- a/source/_integrations/light.template.markdown +++ b/source/_integrations/light.template.markdown @@ -71,7 +71,7 @@ light: required: false type: string unique_id: - description: An ID that uniquely identifies this light. Set this to an unique value to allow customisation trough the UI. + description: An ID that uniquely identifies this light. Set this to a unique value to allow customization through the UI. required: false type: string value_template: diff --git a/source/_integrations/linksys_smart.markdown b/source/_integrations/linksys_smart.markdown index b0adf43f163..b778958999d 100644 --- a/source/_integrations/linksys_smart.markdown +++ b/source/_integrations/linksys_smart.markdown @@ -3,6 +3,7 @@ title: Linksys Smart Wi-Fi description: Instructions on how to integrate Linksys Smart Wi-Fi Router into Home Assistant. ha_category: - Presence Detection +ha_iot_class: Local Polling ha_release: 0.48 ha_domain: linksys_smart --- diff --git a/source/_integrations/llamalab_automate.markdown b/source/_integrations/llamalab_automate.markdown index 8d1541628f8..c7f5c0f373d 100644 --- a/source/_integrations/llamalab_automate.markdown +++ b/source/_integrations/llamalab_automate.markdown @@ -3,6 +3,7 @@ title: LlamaLab Automate description: Instructions on how to add user notifications to Home Assistant. ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: 0.27 ha_domain: llamalab_automate --- diff --git a/source/_integrations/lock.markdown b/source/_integrations/lock.markdown index 187ce2f915f..e71041f2e0a 100644 --- a/source/_integrations/lock.markdown +++ b/source/_integrations/lock.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: 0.9 ha_quality_scale: internal ha_domain: lock +ha_iot_class: ~ --- Keeps track which locks are in your environment, their state and allows you to control them. diff --git a/source/_integrations/lock.template.markdown b/source/_integrations/lock.template.markdown index 50aadb136db..e245016fa18 100644 --- a/source/_integrations/lock.template.markdown +++ b/source/_integrations/lock.template.markdown @@ -48,7 +48,7 @@ lock: type: string default: Template Lock unique_id: - description: An ID that uniquely identifies this lock. Set this to an unique value to allow customisation trough the UI. + description: An ID that uniquely identifies this lock. Set this to a unique value to allow customization through the UI. required: false type: string value_template: diff --git a/source/_integrations/logentries.markdown b/source/_integrations/logentries.markdown index ab62a2148df..629438d1706 100644 --- a/source/_integrations/logentries.markdown +++ b/source/_integrations/logentries.markdown @@ -3,6 +3,7 @@ title: Logentries description: Send events to Logentries. ha_category: - History +ha_iot_class: Cloud Push ha_release: 0.13 ha_domain: logentries --- diff --git a/source/_integrations/luci.markdown b/source/_integrations/luci.markdown index fdcf6f2f5c4..f5399378eaf 100644 --- a/source/_integrations/luci.markdown +++ b/source/_integrations/luci.markdown @@ -3,9 +3,9 @@ title: OpenWRT (luci) description: Instructions on how to integrate OpenWRT routers into Home Assistant. ha_category: - Presence Detection +ha_iot_class: Local Polling ha_release: pre 0.7 ha_codeowners: - - '@fbradyirl' - '@mzdrale' ha_domain: luci --- diff --git a/source/_integrations/mailbox.markdown b/source/_integrations/mailbox.markdown index b59f062feb1..3b84906b810 100644 --- a/source/_integrations/mailbox.markdown +++ b/source/_integrations/mailbox.markdown @@ -3,6 +3,7 @@ title: Mailbox description: Instructions on how to setup your mailboxes with Home Assistant. ha_release: 0.51 ha_domain: mailbox +ha_iot_class: ~ --- Mailboxes provide a list of messages with short information about each. Mailbox messages appear on a separate panel in the frontend. diff --git a/source/_integrations/mailgun.markdown b/source/_integrations/mailgun.markdown index f2ec994c4ea..c282c8110ad 100644 --- a/source/_integrations/mailgun.markdown +++ b/source/_integrations/mailgun.markdown @@ -3,6 +3,7 @@ title: Mailgun description: Instructions on how to add Mailgun mail notifications to Home Assistant. ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: 0.38 ha_config_flow: true ha_domain: mailgun diff --git a/source/_integrations/manual.markdown b/source/_integrations/manual.markdown index a554c13a7cf..4d5975299f5 100644 --- a/source/_integrations/manual.markdown +++ b/source/_integrations/manual.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: 0.7.6 ha_quality_scale: internal ha_domain: manual +ha_iot_class: Calculated --- The `manual` alarm control panel platform enables you to create an alarm system in Home Assistant. diff --git a/source/_integrations/manual_mqtt.markdown b/source/_integrations/manual_mqtt.markdown index 89e89943fed..d3ed51d97c7 100644 --- a/source/_integrations/manual_mqtt.markdown +++ b/source/_integrations/manual_mqtt.markdown @@ -5,6 +5,7 @@ ha_category: - Alarm ha_release: '0.50' ha_domain: manual_mqtt +ha_iot_class: Local Push --- The `mqtt` platform extends the [manual alarm](/integrations/manual) by adding support for MQTT control of the alarm by a remote device. It can be used to create external keypads which simply change the state of the manual alarm in Home Assistant. diff --git a/source/_integrations/map.markdown b/source/_integrations/map.markdown index 33c096743c6..144f0c3c01c 100644 --- a/source/_integrations/map.markdown +++ b/source/_integrations/map.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: 0.56 ha_quality_scale: internal ha_domain: map +ha_iot_class: ~ --- This offers a map on the frontend to display the location of tracked devices. To set up tracked devices, look at the [device tracker](/integrations/device_tracker/) documentation. This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually: @@ -20,5 +21,7 @@ Devices that are currently at home won't show on the map.
      -This map always shows the location of all tracked devices. If you want to hide certain entities, you should look into the [Map Card](/lovelace/map). + +This map always shows the location of all tracked devices. If you want to hide certain entities, you should look into the [Map Card](/lovelace/map/). +
      diff --git a/source/_integrations/marytts.markdown b/source/_integrations/marytts.markdown index 35d81918e57..03272640728 100644 --- a/source/_integrations/marytts.markdown +++ b/source/_integrations/marytts.markdown @@ -3,6 +3,7 @@ title: MaryTTS description: Instructions on how to setup MaryTTS with Home Assistant. ha_category: - Text-to-speech +ha_iot_class: Local Push ha_release: 0.43 ha_domain: marytts --- diff --git a/source/_integrations/mastodon.markdown b/source/_integrations/mastodon.markdown index 78f20c7ba38..814adfc5f9a 100644 --- a/source/_integrations/mastodon.markdown +++ b/source/_integrations/mastodon.markdown @@ -7,6 +7,7 @@ ha_release: 0.67 ha_codeowners: - '@fabaff' ha_domain: mastodon +ha_iot_class: Cloud Push --- The `mastodon` platform uses [Mastodon](https://joinmastodon.org/) to deliver notifications from Home Assistant. diff --git a/source/_integrations/matrix.markdown b/source/_integrations/matrix.markdown index 879becaea1c..b446f03f6f7 100644 --- a/source/_integrations/matrix.markdown +++ b/source/_integrations/matrix.markdown @@ -4,6 +4,7 @@ description: Matrix chatbot support ha_category: - Hub - Notifications +ha_iot_class: Cloud Push ha_release: 0.69 ha_codeowners: - '@tinloaf' diff --git a/source/_integrations/media_extractor.markdown b/source/_integrations/media_extractor.markdown index 223b517f2ab..9e9625cd436 100644 --- a/source/_integrations/media_extractor.markdown +++ b/source/_integrations/media_extractor.markdown @@ -3,6 +3,7 @@ title: Media Extractor description: Instructions on how to integrate the Media Extractor into Home Assistant. ha_category: - Media Player +ha_iot_class: Calculated ha_release: 0.49 ha_quality_scale: internal ha_domain: media_extractor @@ -11,7 +12,7 @@ ha_domain: media_extractor The `media_extractor` integration gets a stream URL and sends it to a media player entity. This integration can extract entity specific streams if configured accordingly.
      -Media extractor doesn't transcode streams, it just tries to find stream that match requested query. +Media extractor doesn't transcode streams, it just tries to find a stream that matches the requested query.
      To use the media extractor service in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_integrations/media_player.markdown b/source/_integrations/media_player.markdown index b1c452759f4..7865f52c905 100644 --- a/source/_integrations/media_player.markdown +++ b/source/_integrations/media_player.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: 0.7 ha_quality_scale: internal ha_domain: media_player +ha_iot_class: ~ --- Interacts with media players on your network. diff --git a/source/_integrations/media_source.markdown b/source/_integrations/media_source.markdown index c1f0b5b2470..e51c108f659 100644 --- a/source/_integrations/media_source.markdown +++ b/source/_integrations/media_source.markdown @@ -24,20 +24,21 @@ media_source: ## Local Media -By default, a local media source is configured which Home Assistant looks for -media to show in the media browser. +By default, the integration by default looks for media in a specified folder. +If other `media_dirs` are not declared you need to use `/media/local` path for +example in companion app notification. For Home Assistant OS, Supervised and Container users, this folder is by default -configured on path `/media`. +configured in the path `/media`. -Home Assistant OS and Supervised users can access this folder using, +Home Assistant OS and Supervised users can access this folder by using, for example, the Samba add-on. Users of Home Assistant Container can mount a volume of their choice to `/media`. If you are a Home Assistant Core user, the default directory called is called -`media` under the configuration path (where you `configuration.yaml` is). +`media` under the configuration path (where your `configuration.yaml` is located). -Files served from `media` are protected by the Home Assistant authentication +Files served from `media` are protected by Home Assistant authentication unlike those served from `www`. ## Using custom or additional media folders @@ -45,7 +46,7 @@ unlike those served from `www`. It is also possible to set up custom and additional media directories. To do so, you'll need to adjust the [core configuration][basic-configuration]. -This example adds two media folders to Home Assistant: +This example makes two different folders available to the integration: ```yaml # Example configuration.yaml @@ -55,4 +56,18 @@ homeassistant: recording: /mnt/recordings ``` +## Playing media from a Media Source + +To play media from a media source via a service call, use the uri scheme `media-source://media_source//`. +Default `media_dir`is `local`. + +Example: +```yaml +service: media_player.play_media +data: + entity_id: media_player.living_room_tv + media_content_type: video/mp4 + media_content_id: media-source://media_source/local/videos/favourites/Epic Sax Guy 10 Hours.mp4 +``` + [basic-configuration]: /docs/configuration/basic/#media_dirs diff --git a/source/_integrations/meraki.markdown b/source/_integrations/meraki.markdown index 2659c91a794..93240e61236 100644 --- a/source/_integrations/meraki.markdown +++ b/source/_integrations/meraki.markdown @@ -3,6 +3,7 @@ title: Meraki description: Instructions on how to integrate Meraki-based presence detection into Home Assistant. ha_category: - Presence Detection +ha_iot_class: Cloud Polling ha_release: '0.60' ha_domain: meraki --- diff --git a/source/_integrations/message_bird.markdown b/source/_integrations/message_bird.markdown index 9650a58fb9b..4f66eb89d70 100644 --- a/source/_integrations/message_bird.markdown +++ b/source/_integrations/message_bird.markdown @@ -3,6 +3,7 @@ title: MessageBird description: Instructions on how to add user notifications to Home Assistant. ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: 0.16 ha_domain: message_bird --- diff --git a/source/_integrations/microsoft.markdown b/source/_integrations/microsoft.markdown index 8768d3d4281..a3110154cf1 100644 --- a/source/_integrations/microsoft.markdown +++ b/source/_integrations/microsoft.markdown @@ -3,6 +3,7 @@ title: Microsoft Text-to-Speech (TTS) description: Instructions on how to set up Microsoft Text-to-Speech with Home Assistant. ha_category: - Text-to-speech +ha_iot_class: Cloud Push ha_release: 0.57 ha_domain: microsoft --- diff --git a/source/_integrations/microsoft_face.markdown b/source/_integrations/microsoft_face.markdown index 21661f1b54b..7fcd2884fb5 100644 --- a/source/_integrations/microsoft_face.markdown +++ b/source/_integrations/microsoft_face.markdown @@ -3,6 +3,7 @@ title: Microsoft Face description: Instructions on how to integrate Microsoft Face integration into Home Assistant. ha_category: - Image Processing +ha_iot_class: Cloud Push ha_release: 0.37 ha_domain: microsoft_face --- diff --git a/source/_integrations/microsoft_face_detect.markdown b/source/_integrations/microsoft_face_detect.markdown index 55147bcedc4..fd2b3791745 100644 --- a/source/_integrations/microsoft_face_detect.markdown +++ b/source/_integrations/microsoft_face_detect.markdown @@ -3,6 +3,7 @@ title: Microsoft Face Detect description: Instructions on how to integrate Microsoft Face Detect into Home Assistant. ha_category: - Image Processing +ha_iot_class: Cloud Push ha_release: 0.38 ha_domain: microsoft_face_detect --- diff --git a/source/_integrations/microsoft_face_identify.markdown b/source/_integrations/microsoft_face_identify.markdown index 7612453d49d..2f208f231d7 100644 --- a/source/_integrations/microsoft_face_identify.markdown +++ b/source/_integrations/microsoft_face_identify.markdown @@ -3,6 +3,7 @@ title: Microsoft Face Identify description: Instructions on how to integrate Microsoft Face Identify into Home Assistant. ha_category: - Image Processing +ha_iot_class: Cloud Push ha_release: 0.37 ha_domain: microsoft_face_identify --- @@ -37,7 +38,7 @@ image_processing: {% configuration %} group: - description: Micrsoft face group to detect person from it. + description: Microsoft face group to detect person from it. required: true type: string confidence: diff --git a/source/_integrations/modbus.markdown b/source/_integrations/modbus.markdown index 04227e20582..31156b59df8 100644 --- a/source/_integrations/modbus.markdown +++ b/source/_integrations/modbus.markdown @@ -8,6 +8,7 @@ ha_iot_class: Local Polling ha_codeowners: - '@adamchengtkc' - '@janiversen' + - '@vzahradnik' ha_domain: modbus --- diff --git a/source/_integrations/mycroft.markdown b/source/_integrations/mycroft.markdown index 02e95a70676..8454252030f 100644 --- a/source/_integrations/mycroft.markdown +++ b/source/_integrations/mycroft.markdown @@ -4,6 +4,7 @@ description: Instructions on how to setup Mycroft AI within Home Assistant. ha_category: - Voice - Notifications +ha_iot_class: Local Push ha_release: 0.53 ha_domain: mycroft --- diff --git a/source/_integrations/namecheapdns.markdown b/source/_integrations/namecheapdns.markdown index e22d5fa6586..74adfafd222 100644 --- a/source/_integrations/namecheapdns.markdown +++ b/source/_integrations/namecheapdns.markdown @@ -3,6 +3,7 @@ title: Namecheap FreeDNS description: Keep your namecheap dynamic DNS up to date ha_category: - Network +ha_iot_class: Cloud Push ha_release: 0.56 ha_domain: namecheapdns --- diff --git a/source/_integrations/netatmo.markdown b/source/_integrations/netatmo.markdown index 2b5dd22a347..bce847fba75 100644 --- a/source/_integrations/netatmo.markdown +++ b/source/_integrations/netatmo.markdown @@ -29,57 +29,18 @@ There is currently support for the following device types within Home Assistant: ## Configuration -To enable the Netatmo component, add the following lines to your `configuration.yaml`: - -```yaml -# Example configuration.yaml entry -netatmo: - client_id: YOUR_CLIENT_ID - client_secret: YOUR_CLIENT_SECRET -``` - -{% configuration %} -client_id: - description: The `client id` from your Netatmo app. - required: true - type: string -client_secret: - description: The `client secret` from your Netatmo app. - required: true - type: string -{% endconfiguration %} - -**After the client_id and client_secret is added to your `configuration.yaml` you must enable Netatmo through the integrations page.** - Menu: **Configuration** -> **Integrations**. +Click on the `+` sign to add an integration and click on **Netatmo**. +After completing the configuration flow, the Netatmo integration will be available. + ### Extra configuration of the integration Configuration of Netatmo public weather stations is offered from the front end. Enter the Netatmo integration and press the cogwheel. In the dialog, it is possible to create, edit and remove public weather sensors. For each area a unique name has to be set along with an area to be covered and whether to display average or maximum values. -To edit an existing area simply enter its name and follow the dialog. - -### Get API and Secret Key - -To get your API credentials, you have to declare a new application in the [Netatmo Developer Page](https://dev.netatmo.com/). Sign in using your username and password from your regular Netatmo account. -Open the [app creator](https://dev.netatmo.com/apps/createanapp#form) form. - -

      - -

      -You have to fill the form, but only two fields are required: Name and Description. It doesn't really matter what you put into those. Just write something that make sense to you. To submit your new app, click on create at the bottom of the form. - -

      - -

      - -That's it. You can copy and paste your new `client id` and `client secret` in your Home Assistant configuration file just as described above, in the configuration example. - -

      - -

      +To edit an existing area, enter its name and follow the dialog. ## Camera @@ -239,6 +200,40 @@ Example: {% endraw %} +## Development / Testing with your own client ID + +To enable the Netatmo component with your own development credentials, you have +to declare a new application in the [Netatmo Developer Page](https://dev.netatmo.com/). + +Sign in using your username and password from your regular Netatmo account. + +Next, add the following lines to your `configuration.yaml`: + +```yaml +# Example configuration.yaml entry +netatmo: + client_id: YOUR_CLIENT_ID + client_secret: YOUR_CLIENT_SECRET +``` + +{% configuration %} +client_id: + description: The `client id` from your Netatmo app. + required: true + type: string +client_secret: + description: The `client secret` from your Netatmo app. + required: true + type: string +{% endconfiguration %} + +**After the client_id and client_secret is added to your `configuration.yaml` you must enable Netatmo through the integrations page.** + +Menu: **Configuration** -> **Integrations**. + +Click on the `+` sign to add an integration and click on **Netatmo**. +After completing the configuration flow, the Netatmo integration will be available. + ## Troubleshooting ### Light diff --git a/source/_integrations/nfandroidtv.markdown b/source/_integrations/nfandroidtv.markdown index 8cccf7d3fa5..7155117591a 100644 --- a/source/_integrations/nfandroidtv.markdown +++ b/source/_integrations/nfandroidtv.markdown @@ -5,6 +5,7 @@ ha_category: - Notifications ha_release: 0.32 ha_domain: nfandroidtv +ha_iot_class: Local Push --- Notification platform for [Notifications for Android TV](https://play.google.com/store/apps/details?id=de.cyberdream.androidtv.notifications.google) and [Notifications for FireTV](https://play.google.com/store/apps/details?id=de.cyberdream.firenotifications.google). You can use this plarform to send notifications to your Android TV device. An overlay with the message content will appear for a configurable amount of seconds and then disapper again. Sending images (e.g., security cam) is supported too. diff --git a/source/_integrations/nightscout.markdown b/source/_integrations/nightscout.markdown index 3f4f8dbfe66..402a8349bfc 100644 --- a/source/_integrations/nightscout.markdown +++ b/source/_integrations/nightscout.markdown @@ -18,18 +18,18 @@ The Nightscout integration allows you to view your CGM data from [Nightscout](ht To add `Nightscout` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Nightscout**. -Then just input your server address in the `URL` field. For example: +Then input your server address in the `URL` field. For example: - `https://localhost:5423` - `https://your-app-name.herokuapp.com` -If your Nightscout instance requires authentication for API access, then also input the API Key in the configuration form. +If your Nightscout instance requires authentication for API access, you are also required to input the API Key in the configuration form. ### Sensor -If you have a sensor session running, and once you have enabled the Nightscout integration, you should see a `sensor.blood_glucose` entity. +If you have a sensor session running, and you have enabled the Nightscout integration, you should see a `sensor.blood_glucose` entity. -It's icon changes to indicate the direction or trend, of the glucose readings. +The icon changes to indicate the direction or trend, of the glucose readings. The state is the last reading from Nightscout, and you can see other information about the reading in the sensor's attributes. ### Example Automation diff --git a/source/_integrations/notify_events.markdown b/source/_integrations/notify_events.markdown index 049c7cd7cec..57ce3c87998 100644 --- a/source/_integrations/notify_events.markdown +++ b/source/_integrations/notify_events.markdown @@ -8,6 +8,7 @@ ha_domain: notify_events ha_codeowners: - '@matrozov' - '@papajojo' +ha_iot_class: Cloud Push --- ## Description diff --git a/source/_integrations/omnilogic.markdown b/source/_integrations/omnilogic.markdown index 751009c47e3..b1824176510 100644 --- a/source/_integrations/omnilogic.markdown +++ b/source/_integrations/omnilogic.markdown @@ -1,5 +1,5 @@ --- -title: Hayward OmniLogic +title: Hayward Omnilogic description: Instructions on how to configure Hayward OmniLogic integration. ha_category: - Sensor @@ -8,12 +8,12 @@ ha_iot_class: Cloud Polling ha_config_flow: true ha_codeowners: - '@oliver84' + - '@djtimca' + - '@gentoosu' ha_domain: omnilogic --- -OmniLogic by [Hayward](https://www.hayward-pool.com/shop/en/pools/omnilogic-i-auomni--1) - -Elite automation for fully featured new pool and spas. OmniLogic® brings backyard control to the forefront of pool technology. Enjoy the luxuries of full automation from the most intuitive app with effortless upgrades to always keep your backyard on the cutting edge. +[Hayward OmniLogic](https://www.hayward-pool.com/shop/en/pools/omnilogic-i-auomni--1) smart pool and spa technology control. There is currently support for the following device types within Home Assistant: diff --git a/source/_integrations/onboarding.markdown b/source/_integrations/onboarding.markdown index 81e5bc85ef3..233bac7e327 100644 --- a/source/_integrations/onboarding.markdown +++ b/source/_integrations/onboarding.markdown @@ -8,6 +8,7 @@ ha_quality_scale: internal ha_codeowners: - '@home-assistant/core' ha_domain: onboarding +ha_iot_class: ~ --- This integration creates the endpoints for the onboarding that is built into Home Assistant. There are no configuration options for this integration directly. diff --git a/source/_integrations/openalpr_cloud.markdown b/source/_integrations/openalpr_cloud.markdown index bc134b3ae3c..15c236f06d2 100644 --- a/source/_integrations/openalpr_cloud.markdown +++ b/source/_integrations/openalpr_cloud.markdown @@ -3,6 +3,7 @@ title: OpenALPR Cloud description: Instructions on how to integrate licences plates with OpenALPR cloud into Home Assistant. ha_category: - Image Processing +ha_iot_class: Cloud Push ha_release: 0.36 ha_domain: openalpr_cloud --- diff --git a/source/_integrations/openalpr_local.markdown b/source/_integrations/openalpr_local.markdown index 97785dda34d..29e84c73638 100644 --- a/source/_integrations/openalpr_local.markdown +++ b/source/_integrations/openalpr_local.markdown @@ -3,6 +3,7 @@ title: OpenALPR Local description: Instructions on how to integrate licences plates with OpenALPR local into Home Assistant. ha_category: - Image Processing +ha_iot_class: Local Push ha_release: 0.36 ha_domain: openalpr_local --- diff --git a/source/_integrations/opencv.markdown b/source/_integrations/opencv.markdown index 468fc4528f3..e22621450c2 100644 --- a/source/_integrations/opencv.markdown +++ b/source/_integrations/opencv.markdown @@ -3,6 +3,7 @@ title: OpenCV description: Instructions on how to integrate OpenCV image processing into Home Assistant. ha_category: - Image Processing +ha_iot_class: Local Push ha_release: 0.47 ha_domain: opencv --- diff --git a/source/_integrations/opengarage.markdown b/source/_integrations/opengarage.markdown index cf8ca7d16f1..59fb42a55fb 100644 --- a/source/_integrations/opengarage.markdown +++ b/source/_integrations/opengarage.markdown @@ -3,6 +3,7 @@ title: OpenGarage description: Instructions on how to integrate OpenGarage.io covers within Home Assistant. ha_category: - DIY +ha_iot_class: Local Polling ha_release: 0.44 ha_domain: opengarage ha_codeowners: diff --git a/source/_integrations/openuv.markdown b/source/_integrations/openuv.markdown index e08d6a37cbb..17b4a89ffb6 100644 --- a/source/_integrations/openuv.markdown +++ b/source/_integrations/openuv.markdown @@ -39,7 +39,17 @@ the `update_protection_data` services). To configure the `openuv` integration, navigate to **Configuration** -> **Integrations** in the Home Assistant UI. -## The Fitzpatrick Scale +## Sensors + +| Name | Type | Value | +|------|------|-------| +| Current Ozone Level | Sensor | ozone level in du (Dobson Units) | +| Current UV Index | Sensor | UV Index (numerical value) | +| Current UV Level | Sensor | UV Level (as literal) | +| Max UV Index | Sensor | max UV Index for the day (at solar noon) | +| Protection Window | Binary Sensor | 'On' when protection window is needed | + +### The Fitzpatrick Scale The approximate number of minutes of a particular skin type can be exposed to the sun before burning/tanning starts is based on the @@ -51,6 +61,15 @@ decision making. They should not replace analysis, advice or diagnosis from a trained medical professional.
      +OpenUV integration provide sensors for safe exposure time (in minutes) based on skin type: + +- Skin Type 1 Safe Exposure Time +- Skin Type 2 Safe Exposure Time +- Skin Type 3 Safe Exposure Time +- Skin Type 4 Safe Exposure Time +- Skin Type 5 Safe Exposure Time +- Skin Type 6 Safe Exposure Time + ## Services ### `openuv.update_data` diff --git a/source/_integrations/orvibo.markdown b/source/_integrations/orvibo.markdown index ebf9b0cd1e5..350050b97a0 100644 --- a/source/_integrations/orvibo.markdown +++ b/source/_integrations/orvibo.markdown @@ -3,6 +3,7 @@ title: Orvibo description: Instructions on how to integrate Orvibo sockets within Home Assistant. ha_category: - Switch +ha_iot_class: Local Push ha_release: 0.8 ha_domain: orvibo --- diff --git a/source/_integrations/owntracks.markdown b/source/_integrations/owntracks.markdown index dcacab1c88c..d96ab5185a9 100644 --- a/source/_integrations/owntracks.markdown +++ b/source/_integrations/owntracks.markdown @@ -3,6 +3,7 @@ title: OwnTracks description: Instructions on how to use Owntracks to track devices in Home Assistant. ha_category: - Presence Detection +ha_iot_class: Local Push ha_release: 0.7.4 ha_config_flow: true ha_domain: owntracks diff --git a/source/_integrations/persistent_notification.markdown b/source/_integrations/persistent_notification.markdown index a78a94b4327..518ca5af459 100644 --- a/source/_integrations/persistent_notification.markdown +++ b/source/_integrations/persistent_notification.markdown @@ -3,6 +3,7 @@ title: Persistent Notification description: Instructions on how to integrate persistent notifications into Home Assistant. ha_category: - Other +ha_iot_class: Local Push ha_release: 0.23 ha_quality_scale: internal ha_codeowners: diff --git a/source/_integrations/person.markdown b/source/_integrations/person.markdown index 25026b259d6..cf86970e7ec 100644 --- a/source/_integrations/person.markdown +++ b/source/_integrations/person.markdown @@ -6,23 +6,24 @@ ha_category: ha_release: 0.88 ha_quality_scale: internal ha_domain: person +ha_iot_class: Calculated --- The `person` integration allows connecting [device tracker](/integrations/device_tracker/) entities to one or more person entities. The state updates of a connected device tracker will set the state of the person. When multiple device trackers are used, the state of person will be determined in this order: -1. If there are stationary trackers (non-GPS trackers, e.g., a router or Bluetooth device tracker) presenting the status `home`, the tracker most recently updated will be used. +1. If there are stationary trackers (non-GPS trackers, e.g., a router or Bluetooth device tracker) presenting the state `home`, the tracker most recently updated will be used. 2. If there are trackers of type `gps`, then the most recently updated tracker will be used. -3. Otherwise, the latest tracker with status `not_home` will be used. +3. Otherwise, the latest tracker with state `not_home` will be used. Let's say, for example, that you have three trackers: `tracker_gps`, `tracker_router` and `tracker_ble`. -1. You're at home, all three devices show status `home` - status of your Person entity will be `home` with source `tracker_router` or `tracker_ble`, whichever was most recently updated. -2. You just left home. `tracker_gps` shows status `not_home`, but the other two trackers show status `home` (they may not have yet updated due to their `consider_home` setting see [device_tracker](/integrations/device_tracker/#configuring-a-device_tracker-platform)). Since the stationary trackers have priority, you are considered `home`. -3. After some time, both stationary trackers show status `not_home`. Now your Person entity has status 'not_home' with source `tracker_gps`. -4. While you are away from home, your Home Assistant instance is restarted. Until the `tracker_gps` receives an update, your status will be determined by the stationary trackers, since they will have the most recent update after a restart. Obviously, the status will be `not_home`. -5. Then you're going into a zone you have defined as `zone1`, `tracker_gps` sends an update, and now your status is `zone1` with source `tracker_gps`. -6. You've returned home and your mobile device has connected to the router, but `tracker_gps` hasn't updated yet. Your status will be `home` with source `tracker_router`. -7. After the `tracker_gps` update occurs, your status will still be `home` with source `tracker_router` or `tracker_ble`, whichever has the most recent update. +1. You're at home, all three devices show state `home` - the state of your Person entity will be `home` with source `tracker_router` or `tracker_ble`, whichever was most recently updated. +2. You just left home. `tracker_gps` shows state `not_home`, but the other two trackers show state `home` (they may not have yet updated due to their `consider_home` setting see [device_tracker](/integrations/device_tracker/#configuring-a-device_tracker-platform)). Since the stationary trackers have priority, you are considered `home`. +3. After some time, both stationary trackers show state `not_home`. Now your Person entity has state 'not_home' with source `tracker_gps`. +4. While you are away from home, your Home Assistant instance is restarted. Until the `tracker_gps` receives an update, your status will be determined by the stationary trackers, since they will have the most recent update after a restart. Obviously, the state will be `not_home`. +5. Then you're going into a zone you have defined as `zone1`, `tracker_gps` sends an update, and now your state is `zone1` with source `tracker_gps`. +6. You've returned home and your mobile device has connected to the router, but `tracker_gps` hasn't updated yet. Your state will be `home` with source `tracker_router`. +7. After the `tracker_gps` update occurs, your state will still be `home` with source `tracker_router` or `tracker_ble`, whichever has the most recent update. In short, when you're at home, your position is determined first by stationary trackers (if any) and then by GPS. When you're outside your home, your position is determined firstly by GPS and then by stationary trackers. diff --git a/source/_integrations/picotts.markdown b/source/_integrations/picotts.markdown index 9c55c8bb32a..b926724ae69 100644 --- a/source/_integrations/picotts.markdown +++ b/source/_integrations/picotts.markdown @@ -3,6 +3,7 @@ title: Pico TTS description: Instructions on how to setup Pico Text-to-Speech with Home Assistant. ha_category: - Text-to-speech +ha_iot_class: Local Push ha_release: 0.36 ha_domain: picotts --- diff --git a/source/_integrations/plant.markdown b/source/_integrations/plant.markdown index 4202260abe6..b2584de4c90 100644 --- a/source/_integrations/plant.markdown +++ b/source/_integrations/plant.markdown @@ -3,6 +3,7 @@ title: Plant Monitor description: Instructions on how to setup plant monitoring with Home Assistant. ha_category: - Environment +ha_iot_class: Calculated ha_release: 0.44 ha_quality_scale: internal ha_codeowners: diff --git a/source/_integrations/plex.markdown b/source/_integrations/plex.markdown index b3c99dc18d4..86ce2486850 100644 --- a/source/_integrations/plex.markdown +++ b/source/_integrations/plex.markdown @@ -64,7 +64,7 @@ The Plex media player platform will create Media Player entities for each connec By default, the Plex integration will create Media Player entities for all local, managed, and shared users on the Plex server. To customize which users or client types to monitor, adjust the "*Monitored users*", "*Ignore new managed/shared users*", and "*Ignore Plex Web clients*" options described under [Integration Options](#integration-options). -### Service `play_media` +### Service `media_player.play_media` Plays a song, album, artist, playlist, TV show/season/episode, movie, or video on a connected client. @@ -233,7 +233,7 @@ Refresh a Plex library to scan for new and updated media. | `server_name` | No | Name of Plex server to use if multiple servers configured. | "My Plex Server" | | `library_name` | Yes | Name of Plex library to update. | "TV Shows" | -### Service 'plex.scan_for_clients' +### Service `plex.scan_for_clients` Scan for new controllable Plex clients. This may be necessary in scripts or automations which control a Plex `media_player` entity, but where the underlying device must be turned on first. diff --git a/source/_integrations/prowl.markdown b/source/_integrations/prowl.markdown index fd567c9221c..7b088d4509d 100644 --- a/source/_integrations/prowl.markdown +++ b/source/_integrations/prowl.markdown @@ -4,6 +4,7 @@ description: Instructions on how to add Prowl notifications to Home Assistant. ha_category: - Notifications ha_release: 0.52 +ha_iot_class: Cloud Push ha_domain: prowl --- diff --git a/source/_integrations/proximity.markdown b/source/_integrations/proximity.markdown index e214d2ee66b..e362de727b8 100644 --- a/source/_integrations/proximity.markdown +++ b/source/_integrations/proximity.markdown @@ -3,9 +3,11 @@ title: Proximity description: Instructions on how to setup Proximity monitoring within Home Assistant. ha_category: - Automation + - Presence Detection ha_release: 0.13 ha_quality_scale: internal ha_domain: proximity +ha_iot_class: ~ --- The `proximity` integration allows you to monitor the proximity of devices to a particular [zone](/integrations/zone/) and the direction of travel. The result is an entity created in Home Assistant which maintains the proximity data. diff --git a/source/_integrations/pushsafer.markdown b/source/_integrations/pushsafer.markdown index ac7a4a7f070..3ba9c0ef65f 100644 --- a/source/_integrations/pushsafer.markdown +++ b/source/_integrations/pushsafer.markdown @@ -4,7 +4,9 @@ description: Instructions on how to add Pushsafer notifications to Home Assistan logo: pushsafer.png ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: 0.39 +ha_iot_class: Cloud Push ha_domain: pushsafer --- diff --git a/source/_integrations/python_script.markdown b/source/_integrations/python_script.markdown index ae7737083de..b68a073cb9c 100644 --- a/source/_integrations/python_script.markdown +++ b/source/_integrations/python_script.markdown @@ -90,3 +90,13 @@ turn_on_light: ``` For more examples, visit the [Scripts section](https://community.home-assistant.io/c/projects/scripts) in our forum. + +## Services + +Available services: `reload`. + +### Service `python_script.reload` + +Reload all available python_scripts from the `/python_scripts` folder. Use this when creating a new Python script and you're not restarting Home Assistant. + +This service takes no service data attributes. diff --git a/source/_integrations/qrcode.markdown b/source/_integrations/qrcode.markdown index c5315c4c796..b9778e1ff7c 100644 --- a/source/_integrations/qrcode.markdown +++ b/source/_integrations/qrcode.markdown @@ -3,6 +3,7 @@ title: QR Code description: Instructions on how to integrate QR Code Recognition into Home Assistant. ha_category: - Image Processing +ha_iot_class: Calculated ha_release: 0.87 ha_domain: qrcode --- diff --git a/source/_integrations/quantum_gateway.markdown b/source/_integrations/quantum_gateway.markdown index 09ddb63a763..4d84b2c9da4 100644 --- a/source/_integrations/quantum_gateway.markdown +++ b/source/_integrations/quantum_gateway.markdown @@ -3,6 +3,7 @@ title: Quantum Gateway description: Instructions on how to integrate Quantum Gateways into Home Assistant. ha_category: - Presence Detection +ha_iot_class: Local Polling ha_release: 0.81 ha_codeowners: - '@cisasteelersfan' diff --git a/source/_integrations/qvr_pro.markdown b/source/_integrations/qvr_pro.markdown index 9a957e762b4..9b6110a7529 100644 --- a/source/_integrations/qvr_pro.markdown +++ b/source/_integrations/qvr_pro.markdown @@ -4,6 +4,7 @@ description: Instructions on how to integrate QVR Pro within Home Assistant. logo: qvr_pro.png ha_category: - Camera +ha_iot_class: Local Polling ha_release: 0.107 ha_domain: qvr_pro ha_codeowners: diff --git a/source/_integrations/qwikswitch.markdown b/source/_integrations/qwikswitch.markdown index 4d835c3da51..1f211ef27d1 100644 --- a/source/_integrations/qwikswitch.markdown +++ b/source/_integrations/qwikswitch.markdown @@ -7,6 +7,7 @@ ha_category: - Light - Sensor - Switch +ha_iot_class: Local Push ha_release: '0.20' ha_codeowners: - '@kellerza' diff --git a/source/_integrations/recorder.markdown b/source/_integrations/recorder.markdown index 51f469a782a..4dd09cc587d 100644 --- a/source/_integrations/recorder.markdown +++ b/source/_integrations/recorder.markdown @@ -12,7 +12,7 @@ The `recorder` integration is responsible for storing details in a database, whi
      -This integration constantly saves data. If you use the default configuration, the data will be saved on the media Home Assistant is installed on. In case of Raspberry Pi with an SD card, it might affect your system's reaction time and life expectancy of the storage medium (the SD card). It is therefore recommended to store the data elsewhere (e.g., another system) or limit the amount of stored data (e.g., by excluding devices). +This integration constantly saves data. If you use the default configuration, the data will be saved on the media Home Assistant is installed on. In case of Raspberry Pi with an SD card, it might affect your system's reaction time and life expectancy of the storage medium (the SD card). It is therefore recommended to set the [commit_interval](/integrations/recorder#commit_interval) to higher value, e.g. 30s, limit the amount of stored data (e.g., by excluding devices) or store the data elsewhere (e.g., another system).
      @@ -214,19 +214,22 @@ Note that purging will not immediately decrease disk space usage but it will sig ## Custom database engines -| Database engine | `db_url` | -| :----------------------------- | :------------------------------------------------------------------------------------------- | -| SQLite | `sqlite:////PATH/TO/DB_NAME` | -| MariaDB (omit pymysql) | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | -| MySQL | `mysql://SERVER_IP/DB_NAME?charset=utf8` | -| MySQL | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | -| MariaDB | `mysql+pymysql://SERVER_IP/DB_NAME?charset=utf8` | -| MariaDB | `mysql+pymysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | -| PostgreSQL | `postgresql://SERVER_IP/DB_NAME` | -| PostgreSQL | `postgresql://user:password@SERVER_IP/DB_NAME` | -| PostgreSQL (Socket) | `postgresql://@/DB_NAME` | -| PostgreSQL (Custom socket dir) | `postgresql://@/DB_NAME?host=/path/to/dir` | -| MS SQL Server | `mssql+pyodbc://username:password@SERVER_IP/DB_NAME?charset=utf8;DRIVER={DRIVER};Port=1433;` | +| Database engine | `db_url` | +| :----------------------------- | :----------------------------------------------------------------------------------------------------- | +| SQLite | `sqlite:////PATH/TO/DB_NAME` | +| MariaDB (omit pymysql) | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | +| MariaDB (omit pymysql, Socket) | `mysql://user:password@SERVER_IP/DB_NAME?unix_socket=/var/run/mysqld/mysqld.sock&charset=utf8` | +| MySQL | `mysql://SERVER_IP/DB_NAME?charset=utf8` | +| MySQL | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | +| MySQL (Socket) | `mysql://user:password@localhost/DB_NAME?unix_socket=/var/run/mysqld/mysqld.sock&charset=utf8` | +| MariaDB | `mysql+pymysql://SERVER_IP/DB_NAME?charset=utf8` | +| MariaDB | `mysql+pymysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | +| MariaDB (Socket) | `mysql+pymysql://user:password@localhost/DB_NAME?unix_socket=/var/run/mysqld/mysqld.sock&charset=utf8` | +| PostgreSQL | `postgresql://SERVER_IP/DB_NAME` | +| PostgreSQL | `postgresql://user:password@SERVER_IP/DB_NAME` | +| PostgreSQL (Socket) | `postgresql://@/DB_NAME` | +| PostgreSQL (Custom socket dir) | `postgresql://@/DB_NAME?host=/path/to/dir` | +| MS SQL Server | `mssql+pyodbc://username:password@SERVER_IP/DB_NAME?charset=utf8;DRIVER={DRIVER};Port=1433;` |
      diff --git a/source/_integrations/rejseplanen.markdown b/source/_integrations/rejseplanen.markdown index 59ae9051978..42a52de42d1 100644 --- a/source/_integrations/rejseplanen.markdown +++ b/source/_integrations/rejseplanen.markdown @@ -6,6 +6,8 @@ ha_category: ha_iot_class: Cloud Polling ha_release: 0.88 ha_domain: rejseplanen +ha_codeowners: + - '@DarkFox' --- The `rejseplanen` sensor will provide you with travel details for Danish public transport, using timetable data from [Rejseplanen](https://www.rejseplanen.dk/). diff --git a/source/_integrations/remember_the_milk.markdown b/source/_integrations/remember_the_milk.markdown index 5e679cc75b0..5409b5d7094 100644 --- a/source/_integrations/remember_the_milk.markdown +++ b/source/_integrations/remember_the_milk.markdown @@ -3,6 +3,7 @@ title: Remember The Milk description: Instructions on how to use Remember The Milk with Home Assistant. ha_category: - Calendar +ha_iot_class: Cloud Push ha_release: 0.57 ha_domain: remember_the_milk --- diff --git a/source/_integrations/remote.markdown b/source/_integrations/remote.markdown index 169aa9abe45..64a60050b07 100644 --- a/source/_integrations/remote.markdown +++ b/source/_integrations/remote.markdown @@ -3,6 +3,7 @@ title: Remote description: Instructions on how to setup your remotes with Home Assistant. ha_release: 0.34 ha_domain: remote +ha_iot_class: ~ --- Keeps track which remotes are in your environment, their state and allows you to control them. diff --git a/source/_integrations/rfxtrx.markdown b/source/_integrations/rfxtrx.markdown index d20d2af88f6..f04b0df0c2e 100644 --- a/source/_integrations/rfxtrx.markdown +++ b/source/_integrations/rfxtrx.markdown @@ -8,6 +8,7 @@ ha_category: - Switch - Binary Sensor - Sensor +ha_iot_class: Local Push ha_release: pre 0.7 ha_config_flow: true ha_codeowners: diff --git a/source/_integrations/ring.markdown b/source/_integrations/ring.markdown index f09a6f942fe..d6b7a3c5db3 100644 --- a/source/_integrations/ring.markdown +++ b/source/_integrations/ring.markdown @@ -56,11 +56,17 @@ downloader: download_dir: downloads ``` -Then you can use the following `action` in your automation (this will save the video file under `/downloads/ring_/`): +Then you can use the following automation, with the entities from your system, which will save the video file under `/downloads/ring_/`: {% raw %} ```yaml -action: +automation: + alias: 'Save the video when the doorbell is pushed' + trigger: + - platform: state + entity_id: binary_sensor.front_doorbell_ding + to: 'on' + action: - service: downloader.download_file data: url: "{{ state_attr('camera.front_door', 'video_url') }}" diff --git a/source/_integrations/rocketchat.markdown b/source/_integrations/rocketchat.markdown index f035e9ceb78..d48474ba696 100644 --- a/source/_integrations/rocketchat.markdown +++ b/source/_integrations/rocketchat.markdown @@ -3,6 +3,7 @@ title: Rocket.Chat description: Instructions on how to add Rocket.Chat notifications to Home Assistant. ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: 0.56 ha_domain: rocketchat --- diff --git a/source/_integrations/roomba.markdown b/source/_integrations/roomba.markdown index e49507045db..213ca18c20f 100644 --- a/source/_integrations/roomba.markdown +++ b/source/_integrations/roomba.markdown @@ -95,3 +95,15 @@ roomba: ### Retrieving your credentials Please refer to [here](https://github.com/NickWaterton/Roomba980-Python#how-to-get-your-usernameblid-and-password) or [here](https://github.com/koalazak/dorita980#how-to-get-your-usernameblid-and-password) to retrieve both the BLID (username) and the password. + +For Home Assistant Container, the following command retrieves the BLID (username) and password: + +```shell +docker exec -it CONTAINER_NAME_OR_ID python -c 'import roomba.entry_points; roomba.entry_points.password()' ROOMBA_IP +``` + +
      + +The command to retrieve the credentials does not need any additional software to be installed because it uses the built-in [roombapy](https://github.com/pschmitt/roombapy) package and [password](https://github.com/pschmitt/roombapy/blob/1.6.1/roomba/entry_points.py#L20) funciton deployed with Home Assistant. + +
      diff --git a/source/_integrations/route53.markdown b/source/_integrations/route53.markdown index 320eed6390f..f1533f61c7a 100644 --- a/source/_integrations/route53.markdown +++ b/source/_integrations/route53.markdown @@ -3,6 +3,7 @@ title: AWS Route53 description: Automatically update your AWS Route53 DNS records. ha_category: - Network +ha_iot_class: Cloud Push ha_release: 0.81 ha_domain: route53 --- diff --git a/source/_integrations/rss_feed_template.markdown b/source/_integrations/rss_feed_template.markdown index 869fde85757..a09ce42f236 100644 --- a/source/_integrations/rss_feed_template.markdown +++ b/source/_integrations/rss_feed_template.markdown @@ -3,6 +3,7 @@ title: RSS Feed Template description: Use this integration to generate RSS feeds showing your latest data. ha_category: - Front End +ha_iot_class: Local Push ha_release: 0.44 ha_quality_scale: internal ha_domain: rss_feed_template diff --git a/source/_integrations/scene.markdown b/source/_integrations/scene.markdown index 0d3d9e8f969..2824d8691be 100644 --- a/source/_integrations/scene.markdown +++ b/source/_integrations/scene.markdown @@ -8,6 +8,7 @@ ha_quality_scale: internal ha_codeowners: - '@home-assistant/core' ha_domain: scene +ha_iot_class: ~ --- You can create scenes that capture the states you want certain entities to be. For example, a scene can specify that light A should be turned on and light B should be bright red. diff --git a/source/_integrations/script.markdown b/source/_integrations/script.markdown index fccf5159f32..6f66996e916 100644 --- a/source/_integrations/script.markdown +++ b/source/_integrations/script.markdown @@ -8,6 +8,7 @@ ha_quality_scale: internal ha_codeowners: - '@home-assistant/core' ha_domain: script +ha_iot_class: ~ --- The `script` integration allows users to specify a sequence of actions to be executed by Home Assistant. These are run when you turn the script on. The script integration will create an entity for each script and allow them to be controlled via services. diff --git a/source/_integrations/search.markdown b/source/_integrations/search.markdown index f27d6df2ee7..c81b823715e 100644 --- a/source/_integrations/search.markdown +++ b/source/_integrations/search.markdown @@ -1,8 +1,10 @@ --- title: Search description: Internal search module for Home Assistant. -ha_category: [] +ha_category: + - Other ha_release: 0.105 +ha_quality_scale: internal ha_codeowners: - '@home-assistant/core' ha_domain: search @@ -16,7 +18,9 @@ This means it can be searched as a graph. This integration allows the internals of Home Assistant to search for relations between things like areas, devices, entities, configuration entries, -scenes, scripts and automations. +[scenes](/integrations/scene/), [scripts](/integrations/script/) and [automations](/integrations/automation/). + +Currently these relations are displayed on the "Related" tab in more info dialogs, and on Device info pages. The search integration is automatically loaded with the Home Assistant frontend and does not need to be configured separately. diff --git a/source/_integrations/sensor.command_line.markdown b/source/_integrations/sensor.command_line.markdown index a31622ff16d..9340514a380 100644 --- a/source/_integrations/sensor.command_line.markdown +++ b/source/_integrations/sensor.command_line.markdown @@ -10,7 +10,7 @@ ha_domain: command_line --- -The `command_line` sensor platform that issues specific commands to get data. This might become our most powerful platform as it allows anyone to integrate any type of sensor into Home Assistant that can get data from the command line. +The `command_line` sensor platform simply issues specific commands to get its data. This makes it a very powerful platform as it allows anyone to integrate any type of sensor into Home Assistant that can get data from the command line. ## Configuration @@ -134,7 +134,7 @@ sensor: ### Read value out of a remote text file -If you own a devices which are storing values in text files which are accessible over HTTP then you can use the same approach as shown in the previous section. Instead of looking at the JSON response we directly grab the sensor's value. +If you own devices which are storing values in text files which are accessible over HTTP then you can use the same approach as shown in the previous section. Instead of looking at the JSON response we directly grab the sensor's value. ```yaml sensor: @@ -147,7 +147,7 @@ sensor: The example is doing the same as the [aREST sensor](/integrations/arest#sensor) but with an external Python script. It should give you an idea about interfacing with devices which are exposing a RESTful API. -The one-line script to retrieve a value is shown below. Of course would it be possible to use this directly in the `configuration.yaml` file but need extra care about the quotation marks. +The one-line script to retrieve a value is shown below. Of course it would be possible to use this directly in the `configuration.yaml` file but need extra care about the quotation marks. ```bash python3 -c "import requests; print(requests.get('http://10.0.0.48/analog/2').json()['return_value'])" @@ -175,7 +175,7 @@ sensor: ### Usage of templating in `command:` -[Templates](/docs/configuration/templating/) are supported in the `command:` configuration variable. This could be used if you want to include the state of a specific sensor as an argument to your external script. +[Templates](/docs/configuration/templating/) are supported in the `command` configuration variable. This could be used if you want to include the state of a specific sensor as an argument to your external script. {% raw %} @@ -192,7 +192,7 @@ sensor: ### Usage of JSON attributes in command output -The example shows how you can retrieve multiple values with one sensor (where the additional are attributes) by using `value_json` and `json_attributes`. +The example shows how you can retrieve multiple values with one sensor (where the additional values are attributes) by using `value_json` and `json_attributes`. {% raw %} diff --git a/source/_integrations/sensor.markdown b/source/_integrations/sensor.markdown index 7cd81e0b05f..4706216365c 100644 --- a/source/_integrations/sensor.markdown +++ b/source/_integrations/sensor.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: 0.7 ha_quality_scale: internal ha_domain: sensor +ha_iot_class: ~ --- Sensors are gathering information about states and conditions. diff --git a/source/_integrations/shelly.markdown b/source/_integrations/shelly.markdown index c19049ebdb9..4f24a4a203f 100644 --- a/source/_integrations/shelly.markdown +++ b/source/_integrations/shelly.markdown @@ -2,6 +2,9 @@ title: Shelly description: Integrate Shelly devices ha_category: + - Cover + - Light + - Sensor - Switch ha_release: 0.115 ha_codeowners: diff --git a/source/_integrations/shiftr.markdown b/source/_integrations/shiftr.markdown index ed40227b0cc..8531b54e77a 100644 --- a/source/_integrations/shiftr.markdown +++ b/source/_integrations/shiftr.markdown @@ -3,6 +3,7 @@ title: shiftr.io description: Transfer events to Shiftr.io. ha_category: - History +ha_iot_class: Cloud Push ha_release: 0.48 ha_codeowners: - '@fabaff' diff --git a/source/_integrations/shopping_list.markdown b/source/_integrations/shopping_list.markdown index 95e71e2c26f..2e852ab46db 100644 --- a/source/_integrations/shopping_list.markdown +++ b/source/_integrations/shopping_list.markdown @@ -10,7 +10,10 @@ ha_iot_class: Local Push ha_domain: shopping_list --- -The `shopping_list` integration allows you to keep track of shopping list items. Includes the ability to add items via your voice using the sentence "Add eggs to my shopping list". +The `shopping_list` integration allows you to keep track of shopping list items. + +Your shopping list will be accessible from the sidebar, and you can optionally add the [Shopping List card](/lovelace/shopping-list/) to your Lovelace dashboard. With the [Conversation integration](/integrations/conversation/) you can add items to your shopping list using voice commands like "Add eggs to my shopping list." + ## Configuration - GUI @@ -18,11 +21,6 @@ From the Home Assistant front page go to **Configuration** and then select **Int Use the plus button in the bottom right to add a new integration called **Shopping List**. -In the popup: -- Submit - -The success dialog will appear or an error will be displayed in the popup. - ## Configuration - Manual ```yaml @@ -32,16 +30,16 @@ shopping_list: ## Services -You can add or remove items on your shopping list by using the following services. +You can add or remove items from your shopping list by using the following services. ### Service `shopping_list.add_item` | Service data attribute | Optional | Description | |------------------------|----------|--------------------------------------------------------| -| `name` | no | Name of the item to add. Example: "Beer" | +| `name` | no | Name of the item to add. Example: "Milk" | ### Service `shopping_list.complete_item` | Service data attribute | Optional | Description | |------------------------|----------|--------------------------------------------------------| -| `name` | no | Name of the item to mark as completed. Example: "Beer" | +| `name` | no | Name of the item to mark as completed. Example: "Milk" | diff --git a/source/_integrations/signal_messenger.markdown b/source/_integrations/signal_messenger.markdown index 34dae8603f9..e2946faa972 100644 --- a/source/_integrations/signal_messenger.markdown +++ b/source/_integrations/signal_messenger.markdown @@ -3,6 +3,7 @@ title: Signal Messenger description: Instructions on how to integrate Signal Messenger within Home Assistant. ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: 0.104 ha_codeowners: - '@bbernhard' diff --git a/source/_integrations/sinch.markdown b/source/_integrations/sinch.markdown index 206c9fc3f11..81f5a0ceb3a 100644 --- a/source/_integrations/sinch.markdown +++ b/source/_integrations/sinch.markdown @@ -7,6 +7,7 @@ ha_release: 0.101 ha_codeowners: - '@bendikrb' ha_domain: sinch +ha_iot_class: Cloud Push --- The `sinch` platform uses [Sinch](https://www.sinch.com/products/messaging/sms/) to deliver notifications from Home Assistant. diff --git a/source/_integrations/slack.markdown b/source/_integrations/slack.markdown index f8fa9ab15ab..bd495b18f53 100644 --- a/source/_integrations/slack.markdown +++ b/source/_integrations/slack.markdown @@ -5,6 +5,7 @@ ha_category: - Notifications ha_release: pre 0.7 ha_domain: slack +ha_iot_class: Cloud Push --- The `slack` platform allows you to deliver notifications from Home Assistant to [Slack](https://slack.com/). diff --git a/source/_integrations/smarty.markdown b/source/_integrations/smarty.markdown index 4cc73ca5691..576c7c436e7 100644 --- a/source/_integrations/smarty.markdown +++ b/source/_integrations/smarty.markdown @@ -5,6 +5,7 @@ ha_category: - Hub - Fan - Sensor +ha_iot_class: Local Polling ha_release: 0.95 ha_codeowners: - '@z0mbieprocess' diff --git a/source/_integrations/smtp.markdown b/source/_integrations/smtp.markdown index f7764beac59..4cb747c2bbf 100644 --- a/source/_integrations/smtp.markdown +++ b/source/_integrations/smtp.markdown @@ -3,6 +3,7 @@ title: SMTP description: Instructions on how to add e-mail notifications to Home Assistant. ha_category: - Notifications +ha_iot_class: Cloud Push ha_release: pre 0.7 ha_codeowners: - '@fabaff' diff --git a/source/_integrations/snips.markdown b/source/_integrations/snips.markdown index 94d6824105a..0390657c49c 100644 --- a/source/_integrations/snips.markdown +++ b/source/_integrations/snips.markdown @@ -5,6 +5,7 @@ ha_category: - Voice ha_release: 0.48 ha_domain: snips +ha_iot_class: Local Push ---
      diff --git a/source/_integrations/solaredge.markdown b/source/_integrations/solaredge.markdown index 8e4aadd2648..b75f010fdd9 100644 --- a/source/_integrations/solaredge.markdown +++ b/source/_integrations/solaredge.markdown @@ -13,7 +13,7 @@ The `solaredge` platform uses the [SolarEdge Monitoring API](https://www.solared
      -The SolarEdge Monitoring API has a daily rate limit of 300 requests. In order to stay under this limit, and alow for some additional requests, the `solaredge` platform will update the site overview every 10 minutes. +The SolarEdge Monitoring API has a daily rate limit of 300 requests. In order to stay under this limit, and alow for some additional requests, the `solaredge` platform will update the site overview every 15 minutes.
      @@ -56,7 +56,7 @@ In case you would like to convert the values for example to kWh instead of the d {% raw %} ```yaml # Example configuration.yaml entry for template platform -sensors: +sensor: platform: template sensors: solaredge_energy_this_year_template: diff --git a/source/_integrations/sonos.markdown b/source/_integrations/sonos.markdown index 9d495b04917..175630c8ce4 100644 --- a/source/_integrations/sonos.markdown +++ b/source/_integrations/sonos.markdown @@ -8,6 +8,8 @@ ha_release: 0.7.3 ha_iot_class: Local Push ha_config_flow: true ha_domain: sonos +ha_codeowners: + - '@cgtobi' --- The `sonos` integration allows you to control your [Sonos](https://www.sonos.com) wireless speakers from Home Assistant. It also works with IKEA Symfonisk speakers. diff --git a/source/_integrations/splunk.markdown b/source/_integrations/splunk.markdown index ebebf567b05..6a680d058d3 100644 --- a/source/_integrations/splunk.markdown +++ b/source/_integrations/splunk.markdown @@ -3,8 +3,11 @@ title: Splunk description: Record events in Splunk. ha_category: - History +ha_iot_class: Local Push ha_release: 0.13 ha_domain: splunk +ha_codeowners: + - '@Bre77' --- The `splunk` integration makes it possible to log all state changes to an external [Splunk](https://splunk.com/) database using Splunk's HTTP Event Collector (HEC) feature. You can either use this alone, or with the Home Assistant for Splunk [app](https://github.com/miniconfig/splunk-homeassistant). Since the HEC feature is new to Splunk, you will need to use at least version 6.3. diff --git a/source/_integrations/ssdp.markdown b/source/_integrations/ssdp.markdown index b08e1d2bb72..856a6621e45 100644 --- a/source/_integrations/ssdp.markdown +++ b/source/_integrations/ssdp.markdown @@ -3,6 +3,7 @@ title: Simple Service Discovery Protocol (SSDP) description: Discover integrations on the network using the SSDP protocol. ha_category: - Network +ha_iot_class: Local Push ha_release: 0.94 ha_domain: ssdp --- diff --git a/source/_integrations/statistics.markdown b/source/_integrations/statistics.markdown index e2948782569..484a706f82a 100644 --- a/source/_integrations/statistics.markdown +++ b/source/_integrations/statistics.markdown @@ -51,7 +51,7 @@ sampling_size: default: 20 type: integer max_age: - description: Maximum age of measurements. Setting this to a time interval will cause older values to be discarded. + description: Maximum age of measurements. Setting this to a time interval will cause older values to be discarded. Please note that you might have to increase the [sampling_size](/integrations/statistics#sampling_size) parameter. If you e.g., have a sensor value updated every second you will, by default, only get a max_age of 20s. required: false type: time precision: diff --git a/source/_integrations/statsd.markdown b/source/_integrations/statsd.markdown index 0082e2033b4..b682ebbe124 100644 --- a/source/_integrations/statsd.markdown +++ b/source/_integrations/statsd.markdown @@ -3,6 +3,7 @@ title: StatsD description: Record events in StatsD. ha_category: - History +ha_iot_class: Local Push ha_release: 0.12 ha_domain: statsd --- diff --git a/source/_integrations/switch.markdown b/source/_integrations/switch.markdown index 46b5bae9f4d..d8807493f82 100644 --- a/source/_integrations/switch.markdown +++ b/source/_integrations/switch.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: 0.7 ha_quality_scale: internal ha_domain: switch +ha_iot_class: ~ --- Keeps track which switches are in your environment, their state and allows you to control them. diff --git a/source/_integrations/switch.template.markdown b/source/_integrations/switch.template.markdown index 7f02ce20fdd..76d76a60359 100644 --- a/source/_integrations/switch.template.markdown +++ b/source/_integrations/switch.template.markdown @@ -51,7 +51,7 @@ switch: required: false type: string unique_id: - description: An ID that uniquely identifies this switch. Set this to an unique value to allow customisation trough the UI. + description: An ID that uniquely identifies this switch. Set this to a unique value to allow customization through the UI. required: false type: string value_template: diff --git a/source/_integrations/synology_chat.markdown b/source/_integrations/synology_chat.markdown index 3c4f45fecd6..e7a022cb11f 100644 --- a/source/_integrations/synology_chat.markdown +++ b/source/_integrations/synology_chat.markdown @@ -1,6 +1,7 @@ --- title: Synology Chat description: Instructions on how to add a Synology Chat Bot notifications to Home Assistant. +ha_iot_class: Cloud Push ha_release: 0.65 ha_category: - Notifications diff --git a/source/_integrations/synology_srm.markdown b/source/_integrations/synology_srm.markdown index ea44c7be09d..7fd66488383 100644 --- a/source/_integrations/synology_srm.markdown +++ b/source/_integrations/synology_srm.markdown @@ -3,6 +3,7 @@ title: Synology SRM description: Instructions on how to integrate Synology SRM routers into Home Assistant. ha_category: - Presence Detection +ha_iot_class: Local Polling ha_release: 0.87 ha_codeowners: - '@aerialls' diff --git a/source/_integrations/system_health.markdown b/source/_integrations/system_health.markdown index 549ea17b106..844d579e082 100644 --- a/source/_integrations/system_health.markdown +++ b/source/_integrations/system_health.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: 0.87 ha_quality_scale: internal ha_domain: system_health +ha_iot_class: ~ --- The System Health integration provides an API to offer information on the system and its components. It also allows to run diagnostic tools to diagnose problems. @@ -17,4 +18,6 @@ This integration is by default enabled, unless you've disabled or removed the [` system_health: ``` -System Health integration data can be viewed in Configuration -> General Configuration, on the "Info" tab. +System Health integration data can be viewed at **Configuration** -> **Info**. + +Data includes information about your system architecture, operating system and version, Home Assistant installation type and version, Python version, frontend version, the number of [Lovelace Dashboards and Views](/lovelace/dashboards-and-views/) you have, and more. diff --git a/source/_integrations/tag.markdown b/source/_integrations/tag.markdown index c8b46db8bf6..6e629a3c25b 100644 --- a/source/_integrations/tag.markdown +++ b/source/_integrations/tag.markdown @@ -8,6 +8,8 @@ ha_codeowners: - '@balloob' - '@dmulcahey' ha_domain: tag +ha_quality_scale: internal +ha_iot_class: ~ ---

      diff --git a/source/_integrations/telegram.markdown b/source/_integrations/telegram.markdown index 3d945dcf3fd..15bb3c56193 100644 --- a/source/_integrations/telegram.markdown +++ b/source/_integrations/telegram.markdown @@ -8,7 +8,7 @@ ha_iot_class: Cloud Polling ha_domain: telegram --- -The `telegram` platform uses [Telegram](https://web.telegram.org) to deliver notifications from Home Assistant to your Android device, your Windows phone, or your iOS device. +The `telegram` platform uses [Telegram](https://www.telegram.org) to deliver notifications from Home Assistant to your Telegram application(s). ## Setup @@ -16,7 +16,7 @@ The requirements are: - You need a [Telegram bot](https://core.telegram.org/bots). Please follow those [instructions](https://core.telegram.org/bots#6-botfather) to create one and get the token for your bot. Keep in mind that bots are not allowed to contact users. You need to make the first contact with your user. Meaning that you need to send a message to the bot from your user. - You need to configure a [Telegram bot in Home Assistant](/integrations/telegram_bot) and define there your API key and the allowed chat ids to interact with. -- The `chat_id` of an allowed user. +- The `chat_id` of an allowed user or group to which the bot is added. **Method 1:** You can get your `chat_id` by sending any message to the [GetIDs bot](https://t.me/getidsbot). @@ -76,14 +76,20 @@ telegram_bot: - platform: polling api_key: YOUR_API_KEY allowed_chat_ids: - - CHAT_ID_1 - - CHAT_ID_2 + - CHAT_ID_1 # example: 123456789 for the chat_id of a user + - CHAT_ID_2 # example: -987654321 for the chat_id of a group - CHAT_ID_3 # Example configuration.yaml entry for the notifier notify: - - name: NOTIFIER_NAME - platform: telegram + - platform: telegram + name: NOTIFIER_NAME + chat_id: CHAT_ID_1 + + # It is possible to add multiple notifiers by using another chat_id + # the example belows shows an additional notifier which sends messages to the bot which is added to a group + - platform: telegram + name: NOTIFIER_NAME_OF_GROUP chat_id: CHAT_ID_2 ``` @@ -98,7 +104,7 @@ name: default: notify type: string chat_id: - description: The chat ID of your user. + description: The chat ID of the users or group required: true type: integer {% endconfiguration %} @@ -152,7 +158,7 @@ action: photo: - url: http://192.168.1.28/camera.jpg username: admin - password: secrete + password: secret - file: /tmp/picture.jpg caption: Picture Title xy - url: http://somebla.ie/video.png @@ -228,7 +234,7 @@ action: video: - url: http://192.168.1.28/camera.mp4 username: admin - password: secrete + password: secret - file: /tmp/video.mp4 caption: Video Title xy - url: http://somebla.ie/video.mp4 diff --git a/source/_integrations/telegram_bot.markdown b/source/_integrations/telegram_bot.markdown index 85811b11b07..0015661cf42 100644 --- a/source/_integrations/telegram_bot.markdown +++ b/source/_integrations/telegram_bot.markdown @@ -48,7 +48,7 @@ Send a photo. | `target` | yes | An array of pre-authorized chat_ids or user_ids to send the notification to. Defaults to the first allowed chat_id. | | `disable_notification` | yes | True/false for send the message silently. iOS users and web users will not receive a notification, Android users will receive a notification with no sound. Defaults to False. | | `verify_ssl` | yes | True/false for checking the SSL certificate of the server for HTTPS URLs. Defaults to True. | -| 'timeout' | yes | Timeout for send photo. Will help with timeout errors (poor internet connection, etc) | +| `timeout` | yes | Timeout for send photo. Will help with timeout errors (poor internet connection, etc) | | `keyboard` | yes | List of rows of commands, comma-separated, to make a custom keyboard. `[]` to reset to no custom keyboard. Example: `["/command1, /command2", "/command3"]` | | `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` | @@ -67,7 +67,7 @@ Send a video. | `target` | yes | An array of pre-authorized chat_ids or user_ids to send the notification to. Defaults to the first allowed chat_id. | | `disable_notification` | yes | True/false to send the message silently. iOS users and web users will not receive a notification. Android users will receive a notification with no sound. Defaults to False. | | `verify_ssl` | yes | True/false for checking the SSL certificate of the server for HTTPS URLs. Defaults to True. | -| 'timeout' | yes | Timeout for send video. Will help with timeout errors (poor internet connection, etc) | +| `timeout` | yes | Timeout for send video. Will help with timeout errors (poor internet connection, etc) | | `keyboard` | yes | List of rows of commands, comma-separated, to make a custom keyboard. `[]` to reset to no custom keyboard. Example: `["/command1, /command2", "/command3"]` | | `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` | @@ -86,7 +86,7 @@ Send a document. | `target` | yes | An array of pre-authorized chat_ids or user_ids to send the notification to. Defaults to the first allowed chat_id. | | `disable_notification` | yes | True/false for send the message silently. iOS users and web users will not receive a notification, Android users will receive a notification with no sound. Defaults to False. | | `verify_ssl` | yes | True/false for checking the SSL certificate of the server for HTTPS URLs. Defaults to True. | -| 'timeout' | yes | Timeout for send document. Will help with timeout errors (poor internet connection, etc) | +| `timeout` | yes | Timeout for send document. Will help with timeout errors (poor internet connection, etc) | | `keyboard` | yes | List of rows of commands, comma-separated, to make a custom keyboard. `[]` to reset to no custom keyboard. Example: `["/command1, /command2", "/command3"]` | | `inline_keyboard` | yes | List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data. Example: `["/button1, /button2", "/button3"]` or `[[["Text btn1", "/button1"], ["Text btn2", "/button2"]], [["Text btn3", "/button3"]]]` | @@ -167,7 +167,7 @@ Remove the bot from the chat group where it was added. |---------------------------|----------|--------------------------------------------------| | `chat_id` | no | The chat_id from where to remove the bot. | -## `telegram` notification platform +## Telegram notification platform The [`telegram` notification platform](/integrations/telegram) requires the `telegram_bot` integration to work with, and it's designed to generate a customized shortcut (`notify.USERNAME`) to send notifications (messages, photos, documents and locations) to a particular `chat_id` with the old syntax, allowing backward compatibility. @@ -175,8 +175,8 @@ The required YAML configuration now reduces to: ```yaml notify: - - name: NOTIFIER_NAME - platform: telegram + - platform: telegram + name: NOTIFIER_NAME chat_id: USER_CHAT_ID ``` @@ -423,4 +423,4 @@ Telegram callbacks also support arguments and commands the same way as normal me {% endraw %} -In this case, having a callback with `/repeat 1 2 3` with pop a notification saying `I repeat: [1, 2, 3]` +In this case, having a callback with `/repeat 1 2 3` will pop a notification saying `I repeat: [1, 2, 3]` diff --git a/source/_integrations/telegram_broadcast.markdown b/source/_integrations/telegram_broadcast.markdown index 0e3f9c0d865..a73824f85cc 100644 --- a/source/_integrations/telegram_broadcast.markdown +++ b/source/_integrations/telegram_broadcast.markdown @@ -7,7 +7,9 @@ ha_release: 0.48 ha_domain: telegram_bot --- -Telegram implementation to support **sending messages only**. Your Home Assistant instance does not have to be exposed to the Internet and there is no polling to receive messages sent to the bot. +Telegram implementation to support **sending messages only**. Your Home Assistant instance does not have to be exposed to the internet and there is no polling to receive messages or commands sent to the bot. + +Information on how to send a message via the service `telegram_bot.send_message` can be found [here](/integrations/telegram_bot/#service-telegram_botsend_message). ## Configuration @@ -19,13 +21,13 @@ telegram_bot: - platform: broadcast api_key: YOUR_API_KEY allowed_chat_ids: - - 12345 - - 67890 + - 123456789 # example id of a user + - -987654321 # example id of a group, starts with a - ``` {% configuration %} allowed_chat_ids: - description: A list of users in the `user_id` Telegram format that are authorized to interact with the webhook. + description: A list of ids representing the users and group chats to which messages can be send. Default the message will be send to the first alllowed chat_id. By using the `target` service data attribute the message can be send to other chat_ids from the list. required: true type: list api_key: diff --git a/source/_integrations/telegram_polling.markdown b/source/_integrations/telegram_polling.markdown index 58081ec887d..befcd63fd03 100644 --- a/source/_integrations/telegram_polling.markdown +++ b/source/_integrations/telegram_polling.markdown @@ -4,12 +4,14 @@ description: "Telegram polling support" ha_category: - Notifications ha_release: 0.42 +ha_iot_class: Cloud Polling ha_domain: telegram_bot --- Telegram chatbot polling implementation. -One of two bot implementations supported by Telegram. Your Home Assistant does not have to be exposed to the internet. +This is one of two bot implementations supported by Telegram. Your Home Assistant instance does not have to be exposed to the internet. +The other implementation method is [Telegram webhooks](/integrations/telegram_webhooks/), described by Telegram as the preferred implementation but requires your Home Assistant instance to be exposed to the internet. ## Configuration @@ -21,13 +23,13 @@ telegram_bot: - platform: polling api_key: YOUR_API_KEY allowed_chat_ids: - - 12345 - - 67890 + - 123456789 # example id of a user + - -987654321 # example id of a group, starts with a - ``` {% configuration %} allowed_chat_ids: - description: A list of users in the `user_id` Telegram format that are authorized to interact with the webhook. + description: A list of ids representing the users and group chats that are authorized to interact with the bot. required: true type: list api_key: diff --git a/source/_integrations/telegram_webhooks.markdown b/source/_integrations/telegram_webhooks.markdown index 269ebd22990..4d9857f35aa 100644 --- a/source/_integrations/telegram_webhooks.markdown +++ b/source/_integrations/telegram_webhooks.markdown @@ -4,14 +4,16 @@ description: "Telegram webhooks support" ha_category: - Notifications ha_release: 0.42 +ha_iot_class: Cloud Push ha_domain: telegram_bot --- Telegram chatbot webhooks implementation as described in the Telegram [documentation](https://core.telegram.org/bots/webhooks). -Using Telegrams `setWebhook` method your bot's webhook URL should be set to `https://:/api/telegram_webhooks`. +By default this integration sets your bot's webhook URL automatically to `https:///api/telegram_webhooks` with the external_url of your Home Assistant [configuration](/docs/configuration/basic/) using Telegrams `setWebhook` method. This is one of two bot implementations supported by Telegram. Described by Telegram as the preferred implementation but requires your Home Assistant instance to be exposed to the internet. +The other implementation method is [Telegram polling](/integrations/telegram_polling/), for which your Home Assistant instance does not have to be exposed to the internet. ## Configuration @@ -22,15 +24,14 @@ To integrate this into Home Assistant, add the following section to your `config telegram_bot: - platform: webhooks api_key: YOUR_API_KEY - parse_mode: html allowed_chat_ids: - - 12345 - - 67890 + - 123456789 # example id of a user + - -987654321 # example id of a group, starts with a - ``` {% configuration %} allowed_chat_ids: - description: A list of ids representing the users and group chats that are authorized to interact with the webhook. + description: A list of ids representing the users and group chats that are authorized to interact with the bot. required: true type: list api_key: @@ -72,10 +73,11 @@ The configuration sample below shows how an entry can look like: telegram_bot: - platform: webhooks api_key: YOUR_API_KEY + parse_mode: html trusted_networks: - 149.154.160.0/20 - 91.108.4.0/22 allowed_chat_ids: - - 12345 - - 67890 + - 123456789 # example id of a user + - -987654321 # example id of a group, starts with a - ``` diff --git a/source/_integrations/template.markdown b/source/_integrations/template.markdown index 63dd72d78c9..b9f6abfb0bb 100644 --- a/source/_integrations/template.markdown +++ b/source/_integrations/template.markdown @@ -51,7 +51,7 @@ sensor: required: false type: template unique_id: - description: An ID that uniquely identifies this sensor. Set this to an unique value to allow customisation through the UI. + description: An ID that uniquely identifies this sensor. Set this to a unique value to allow customization through the UI. required: false type: string unit_of_measurement: diff --git a/source/_integrations/thingspeak.markdown b/source/_integrations/thingspeak.markdown index 07b362f543f..5ad9962e4a9 100644 --- a/source/_integrations/thingspeak.markdown +++ b/source/_integrations/thingspeak.markdown @@ -3,6 +3,7 @@ title: ThingSpeak description: Record one entity in ThingSpeak ha_category: - History +ha_iot_class: Cloud Push ha_release: 0.32 ha_domain: thingspeak --- diff --git a/source/_integrations/threshold.markdown b/source/_integrations/threshold.markdown index 1f15ad925af..4157085a22e 100644 --- a/source/_integrations/threshold.markdown +++ b/source/_integrations/threshold.markdown @@ -60,3 +60,24 @@ name: type: string default: Threshold {% endconfiguration %} + +## Examples + +### Is the temperature rising or falling + +The hysteresis parameter can be used in this use-case to avoid frequent state changes around the maximum or the minimum of a temperature curve. We also have to utilize the [derivative sensor](/integrations/derivative/) for this use-case: + +```yaml +sensor: + - platform: derivative # will be positive for rising temperatures and negative for falling temperatures + source: sensor.temperature + unit_time: min + name: temperature derivative + time_window: 00:05:00 +binary_sensor: + - platform: threshold # will switch state not at 0°C/min but 0.1°C/min or -0.1°C/min depending on the current state of the sensor, respectively + entity_id: sensor.temperature_derivative + upper: 0 + hysteresis: 0.1 # sensor + name: temperature rising +``` diff --git a/source/_integrations/time_date.markdown b/source/_integrations/time_date.markdown index 656078cd769..2a16c5974eb 100644 --- a/source/_integrations/time_date.markdown +++ b/source/_integrations/time_date.markdown @@ -29,8 +29,42 @@ sensor: - 'beat' ``` -- **display_options** array (*Required*): The option to display. The types *date_time*, *date_time_utc*, *time_date*, and *date_time_iso* shows the date and the time. The other types just the time or the date. *beat* shows the [Swatch Internet Time](https://www.swatch.com/en_us/internet-time). + +{% configuration %} +display_options: + description: The option to display. The types *date_time*, *date_time_utc*, *time_date*, and *date_time_iso* shows the date and the time. The other types just the time or the date. *beat* shows the [Swatch Internet Time](https://www.swatch.com/en_us/internet-time). + required: true + type: list +{% endconfiguration %} + + +Sensors including the time update every minute, the date sensor updates each day at midnight, and the beat sensor updates with each beat (86.4 seconds).

      + +# Producing your own custom time and date sensor + +Whilst there are a number of `display_options` exposed by this sensor, they cannot hope to satisfy everyone, and large parts of the world will find that their local display conventions are not included. + +The following can be used to create a time and date sensor whose output can be properly customised to use your own preferred formatting, specified in the call to timestamp_custom() using standard [Python datetime formatting](https://docs.python.org/3.8/library/datetime.html#strftime-and-strptime-behavior). + +{% raw %} + +```yaml +sensor: + # Minimal configuration of the standard time and date sensor + - platform: time_date + display_options: + - 'date_time_iso' + # Build on the standard sensor to produce one that can be customized + - platform: template + sensors: + time_formatted: + friendly_name: "Date and time" + value_template: "{{ as_timestamp(states('sensor.date_time_iso')) | timestamp_custom('%A %B %-m, %I:%M %p') }}" + icon_template: mdi:calendar-clock +``` + +{% endraw %} diff --git a/source/_integrations/timer.markdown b/source/_integrations/timer.markdown index 8fb0f2f93ff..dd7cf7eb4a7 100644 --- a/source/_integrations/timer.markdown +++ b/source/_integrations/timer.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: 0.57 ha_quality_scale: internal ha_domain: timer +ha_iot_class: Calculated --- The `timer` integration aims to simplify automations based on (dynamic) durations. diff --git a/source/_integrations/tomato.markdown b/source/_integrations/tomato.markdown index 4927bfa9a60..3297946a74b 100644 --- a/source/_integrations/tomato.markdown +++ b/source/_integrations/tomato.markdown @@ -5,6 +5,7 @@ ha_category: - Presence Detection ha_release: pre 0.7 ha_domain: tomato +ha_iot_class: Local Polling --- The `tomato` device tracker integration allows one to tracker devices which are diff --git a/source/_integrations/traccar.markdown b/source/_integrations/traccar.markdown index 5c218a3331d..f37e025cc89 100644 --- a/source/_integrations/traccar.markdown +++ b/source/_integrations/traccar.markdown @@ -159,7 +159,7 @@ device_tracker: monitored_conditions: ['alarm', 'mycomputedattribute'] ``` -The parameter `event` allows you to import events from the traccar platform (https://www.traccar.org/documentation/events/) and fire them in your Home Assistant. It accepts a list of events to be monitored and imported and each event must be listed in lowercase snakecase. The events will be fired with the same event name defined in the abovementioned list preceded by the prefix `traccar_`. For example if you need to import the Traccar events `deviceOverspeed` and `deviceFuelDrop` in Home Assistant, you need to fill the `event` parameter with: +The parameter `event` allows you to import events from the traccar platform (https://www.traccar.org/documentation/events/) and fire them in your Home Assistant. It accepts a list of events to be monitored and imported and each event must be listed in lowercase snakecase. The events will be fired with the same event name defined in the aforementioned list preceded by the prefix `traccar_`. For example if you need to import the Traccar events `deviceOverspeed` and `deviceFuelDrop` in Home Assistant, you need to fill the `event` parameter with: ```yaml device_tracker: diff --git a/source/_integrations/transport_nsw.markdown b/source/_integrations/transport_nsw.markdown index 0b2f540dd3f..6989b0673d2 100644 --- a/source/_integrations/transport_nsw.markdown +++ b/source/_integrations/transport_nsw.markdown @@ -16,7 +16,7 @@ Prerequisite is a free API key from [Transport NSW](https://opendata.transport.n In order to find your stop id, use the [Transport NSW stop finder](https://transportnsw.info/stop#/) and search for your stop. The URL will contain the stop id as a number. -You may also try going to Google maps and clicking on any bus/train/ferry stop. The pop up window shows the stop ID underneath the station name. For train stations the easist way to get a stop id for a platform is through [Transport NSW Info](https://transportnsw.info/). +You may also try going to Google maps and clicking on any bus/train/ferry stop. The pop up window shows the stop ID underneath the station name. For train stations the easiest way to get a stop id for a platform is through [Transport NSW Info](https://transportnsw.info/). As a default the sensor picks up the next mode of transport leaving from a stop id. @@ -81,7 +81,7 @@ sensor: api_key: 'YOUR API KEY' ``` -The sensor returns n/a if no stop event is found within the next 24h. A `template` sensor can help building a more meaninful string. +The sensor returns n/a if no stop event is found within the next 24h. A `template` sensor can help building a more meaningful string. {% raw %} ```yaml diff --git a/source/_integrations/tts.markdown b/source/_integrations/tts.markdown index 9c679491bda..a2082bd6225 100644 --- a/source/_integrations/tts.markdown +++ b/source/_integrations/tts.markdown @@ -4,6 +4,7 @@ description: Instructions on how to set up Text-to-Speech (TTS) with Home Assist ha_category: - Text-to-speech ha_release: 0.35 +ha_iot_class: ~ ha_codeowners: - '@pvizeli' ha_domain: tts diff --git a/source/_integrations/twilio.markdown b/source/_integrations/twilio.markdown index fb6b5ef2153..a05b77e9b0e 100644 --- a/source/_integrations/twilio.markdown +++ b/source/_integrations/twilio.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: '0.40' ha_config_flow: true ha_domain: twilio +ha_iot_class: Cloud Push --- The `twilio` integration enables the sending of notifications via SMS and the creation of calls with [Twilio](https://twilio.com). diff --git a/source/_integrations/twilio_call.markdown b/source/_integrations/twilio_call.markdown index 5c1465798cb..b97d0334c5e 100644 --- a/source/_integrations/twilio_call.markdown +++ b/source/_integrations/twilio_call.markdown @@ -5,6 +5,7 @@ ha_category: - Notifications ha_release: 0.37 ha_domain: twilio_call +ha_iot_class: Cloud Push --- The `twilio_call` notification platform enables sending notifications via Voice, powered by [Twilio](https://twilio.com). diff --git a/source/_integrations/ubus.markdown b/source/_integrations/ubus.markdown index 7533e2d83f8..d93fee29ed7 100644 --- a/source/_integrations/ubus.markdown +++ b/source/_integrations/ubus.markdown @@ -4,6 +4,7 @@ description: Instructions on how to integrate OpenWRT routers into Home Assistan ha_category: - Presence Detection ha_release: 0.7.6 +ha_iot_class: Local Polling ha_domain: ubus --- diff --git a/source/_integrations/unifi.markdown b/source/_integrations/unifi.markdown index cd6a391d155..29994694455 100644 --- a/source/_integrations/unifi.markdown +++ b/source/_integrations/unifi.markdown @@ -15,7 +15,7 @@ ha_codeowners: ha_domain: unifi --- -[UniFi](https://unifi-sdn.ubnt.com/) by [Ubiquiti Networks, inc.](https://www.ubnt.com/) is a software that binds gateways, switches and wireless access points together with one graphical front end. +[UniFi](https://www.ui.com/software/) by [Ubiquiti Networks, inc.](https://www.ui.com/) is a software that binds gateways, switches and wireless access points together with one graphical front end. There is currently support for the following device types within Home Assistant: @@ -49,7 +49,7 @@ It is recommended that you run the UniFi controller in a dedicated virtual machi ## Presence detection -This platform allows you to detect presence by looking at devices connected to a [Ubiquiti](https://ubnt.com/) [UniFi](https://www.ubnt.com/enterprise/#unifi) controller. +This platform allows you to detect presence by looking at devices connected to a [Ubiquiti](https://ui.com/) [UniFi](https://unifi-network.ui.com/) controller. ### Troubleshooting and Time Synchronization diff --git a/source/_integrations/unifi_direct.markdown b/source/_integrations/unifi_direct.markdown index 3ef9e66a648..a6cc41a851e 100644 --- a/source/_integrations/unifi_direct.markdown +++ b/source/_integrations/unifi_direct.markdown @@ -8,7 +8,7 @@ ha_release: 0.59 ha_domain: unifi_direct --- -This platform allows you to detect presence by looking at devices connected to a [UniFi AP](https://www.ubnt.com/products/#unifi). This device tracker differs form [Ubiquiti UniFi WAP](/integrations/unifi) because it doesn't require the UniFi controller software. +This platform allows you to detect presence by looking at devices connected to a [UniFi AP](https://www.ui.com/products/#unifi). This device tracker differs form [Ubiquiti UniFi WAP](/integrations/unifi) because it doesn't require the UniFi controller software. To use this device tracker in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_integrations/unifiled.markdown b/source/_integrations/unifiled.markdown index b57c78c1b88..1622fd4550e 100644 --- a/source/_integrations/unifiled.markdown +++ b/source/_integrations/unifiled.markdown @@ -10,7 +10,7 @@ ha_codeowners: ha_domain: unifiled --- -[UniFi LED](https://unifi-led.ui.com/) by [Ubiquiti Networks, inc.](https://www.ubnt.com/) is a system of controller managed LED light panels and dimmers. +[UniFi LED](https://unifi-led.ui.com/) by [Ubiquiti Networks, inc.](https://www.ui.com/) is a system of controller managed LED light panels and dimmers. There is currently support for the following device type within Home Assistant: diff --git a/source/_integrations/universal.markdown b/source/_integrations/universal.markdown index 8bbec5a864d..36696398265 100644 --- a/source/_integrations/universal.markdown +++ b/source/_integrations/universal.markdown @@ -3,6 +3,7 @@ title: Universal Media Player description: Instructions on how to create a universal media player in Home Assistant. ha_category: - Media Player +ha_iot_class: Calculated ha_release: 0.11 ha_quality_scale: internal ha_domain: universal @@ -50,7 +51,7 @@ name: type: string children: description: Ordered list of child media players this entity will control. - required: true + required: false type: list state_template: description: "A [template](/topics/templating/) can be specified to render the state of the media player. This way, the state could depend on entities different from media players, like switches or input booleans." diff --git a/source/_integrations/uvc.markdown b/source/_integrations/uvc.markdown index c4abba9f5f0..e82151781b6 100644 --- a/source/_integrations/uvc.markdown +++ b/source/_integrations/uvc.markdown @@ -8,9 +8,9 @@ ha_iot_class: Local Polling ha_domain: uvc --- -The `uvc` camera platform allows you to integrate [UniFi Video Camera (UVC)](https://www.ubnt.com/products/#unifivideo) into Home Assistant. +The `uvc` camera platform allows you to integrate [UniFi Video Camera (UVC)](https://www.ui.com/products/#unifivideo) into Home Assistant. -The platform connects to the UniFi NVR software and automatically discovers/adds any camera connected to the NVR. +The platform connects to the [UniFi NVR software](https://www.ui.com/download/unifi-video) and automatically discovers/adds any camera connected to the NVR. ### Setup diff --git a/source/_integrations/vacuum.markdown b/source/_integrations/vacuum.markdown index 6d11b4c6705..28a29896d57 100644 --- a/source/_integrations/vacuum.markdown +++ b/source/_integrations/vacuum.markdown @@ -3,6 +3,7 @@ title: Vacuum description: Instructions on how to setup and use vacuum's in Home Assistant. ha_release: 0.51 ha_domain: vacuum +ha_iot_class: ~ --- The `vacuum` integration enables the ability to control home cleaning robots within Home Assistant. diff --git a/source/_integrations/vacuum.template.markdown b/source/_integrations/vacuum.template.markdown index 8ad670f3e3a..812d1930048 100644 --- a/source/_integrations/vacuum.template.markdown +++ b/source/_integrations/vacuum.template.markdown @@ -40,7 +40,7 @@ vacuum: required: false type: string unique_id: - description: An ID that uniquely identifies this vacuum. Set this to an unique value to allow customisation trough the UI. + description: An ID that uniquely identifies this vacuum. Set this to a unique value to allow customization through the UI. required: false type: string value_template: diff --git a/source/_integrations/vera.markdown b/source/_integrations/vera.markdown index 5c7f94f139a..044a548a4e8 100644 --- a/source/_integrations/vera.markdown +++ b/source/_integrations/vera.markdown @@ -55,7 +55,7 @@ You can find the Vera device id either via the advanced properties of the device ### Using Z-Wave devices in automation -If you want to use a Z-Wave device from the Vera controller in Home Assistant automation, you'll need the entity id. In the Home Assistant UI you'll find all entities listed under the service developer tool icon icon of the Developer Tools section. Look for entities that contain 'Vera Device Id' in their attributes, and you'll find the entity id on the left. +If you want to use a Z-Wave device from the Vera controller in Home Assistant automation, you'll need the entity id. In the Home Assistant UI you'll find all entities listed under **Developer Tools** -> **States**. Look for entities that contain 'Vera Device Id' in their attributes, and you'll find the entity id on the left. ### Sensor diff --git a/source/_integrations/verisure.markdown b/source/_integrations/verisure.markdown index 17df9010d4f..d47b132bd48 100644 --- a/source/_integrations/verisure.markdown +++ b/source/_integrations/verisure.markdown @@ -80,7 +80,7 @@ mouse: type: boolean default: true door_window: - description: Set to `true` to show mouse detectors, `false` to disable. + description: Set to `true` to show doors and windows, `false` to disable. required: false type: boolean default: true diff --git a/source/_integrations/voicerss.markdown b/source/_integrations/voicerss.markdown index 8d059c7ef68..d48f4e62b24 100644 --- a/source/_integrations/voicerss.markdown +++ b/source/_integrations/voicerss.markdown @@ -3,6 +3,7 @@ title: VoiceRSS description: Instructions on how to setup VoiceRSS TTS with Home Assistant. ha_category: - Text-to-speech +ha_iot_class: Cloud Push ha_release: 0.35 ha_domain: voicerss --- diff --git a/source/_integrations/volvooncall.markdown b/source/_integrations/volvooncall.markdown index 9e2df55ae5c..379ba07b74b 100644 --- a/source/_integrations/volvooncall.markdown +++ b/source/_integrations/volvooncall.markdown @@ -64,7 +64,7 @@ mutable: default: true type: boolean name: - description: "Make it possible to provide a name for the vehicles. Note: Use all lower case letters when inputing your VIN number." + description: "Make it possible to provide a name for the vehicles. Note: Use all lower case letters when inputting your VIN number." required: false type: string resources: diff --git a/source/_integrations/water_heater.markdown b/source/_integrations/water_heater.markdown index 99705da7977..dfd39b17689 100644 --- a/source/_integrations/water_heater.markdown +++ b/source/_integrations/water_heater.markdown @@ -3,6 +3,7 @@ title: Water Heater description: Instructions on how to setup water heater devices within Home Assistant. ha_release: 0.81 ha_domain: water_heater +ha_iot_class: ~ --- The `water_heater` integration is built for the controlling and monitoring of hot water heaters. @@ -23,7 +24,7 @@ Available services: `water_heater.set_temperature`, `water_heater.turn_away_mode
      -Not all water heater services may be available for your platform. Be sure to check the available services Home Assistant has enabled by checking service developer tool icon **Services**. +Not all water heater services may be available for your platform. Be sure to check the available services Home Assistant has enabled by checking **Developer Tools** -> **Services**.
      diff --git a/source/_integrations/watson_iot.markdown b/source/_integrations/watson_iot.markdown index e20d6c57281..93b1fd68eae 100644 --- a/source/_integrations/watson_iot.markdown +++ b/source/_integrations/watson_iot.markdown @@ -5,6 +5,7 @@ ha_category: - History ha_release: 0.72 ha_domain: watson_iot +ha_iot_class: Cloud Push --- The `watson_iot` integration enables you to link the devices in Home Assistant diff --git a/source/_integrations/watson_tts.markdown b/source/_integrations/watson_tts.markdown index f0235ebd945..34f87e30b85 100644 --- a/source/_integrations/watson_tts.markdown +++ b/source/_integrations/watson_tts.markdown @@ -4,6 +4,7 @@ description: Instructions on how to setup IBM Watson TTS with Home Assistant. ha_category: - Text-to-speech ha_release: 0.94 +ha_iot_class: Cloud Push ha_codeowners: - '@rutkai' ha_domain: watson_tts diff --git a/source/_integrations/weather.darksky.markdown b/source/_integrations/weather.darksky.markdown index e24e45e2bca..51ce9dd7b82 100644 --- a/source/_integrations/weather.darksky.markdown +++ b/source/_integrations/weather.darksky.markdown @@ -16,7 +16,7 @@ The `darksky` platform uses the [Dark Sky](https://darksky.net/) web service as
      -On March 31, 2020 Dark Sky was [acquired by Apple](https://blog.darksky.net/dark-sky-has-a-new-home/) and is no longer allowing new API registrations. The Dark Sky API will continue to function for existing users through the end of 2021, but it is no longer possible to obtain an API key for new users. +On March 31, 2020 Dark Sky was [acquired by Apple](https://blog.darksky.net/dark-sky-has-a-new-home/) and is no longer allowing new API registrations. The Dark Sky API will continue to function for existing users through the end of 2021, but it is no longer possible to obtain an API key for new users. Home Assistant supports many alternative [weather integrations](/integrations/#weather).
      diff --git a/source/_integrations/wilight.markdown b/source/_integrations/wilight.markdown index 432672f6ad7..368cf25624d 100644 --- a/source/_integrations/wilight.markdown +++ b/source/_integrations/wilight.markdown @@ -5,6 +5,7 @@ ha_category: - Light ha_release: 0.115 ha_config_flow: true +ha_iot_class: Local Polling ha_codeowners: - '@leofig-rj' ha_domain: wilight diff --git a/source/_integrations/wled.markdown b/source/_integrations/wled.markdown index 7fdf92e969b..0f716fc6247 100644 --- a/source/_integrations/wled.markdown +++ b/source/_integrations/wled.markdown @@ -96,7 +96,7 @@ This service allows for controlling the WLED effect. | ---------------------- | -------- | --------------------------------------------------------------------------------------------------------------- | | `entity_id` | no | A WLED entity ID, or list entity IDs, to apply the effect to. Use `entity_id: all` to target all WLED entities. | | `effect` | no | Name or ID of the WLED light effect. | -| `intensity` | no | Intensity of the effect. | +| `intensity` | no | Intensity of the effect. Number between `0` and `255`. | | `palette` | no | Name or ID of the WLED light palette. | | `speed` | no | Speed of the effect. Number between `0` (slow) and `255` (fast). | | `reverse` | no | Reverse the effect. Either `true` to reverse or `false` otherwise. | diff --git a/source/_integrations/wolflink.markdown b/source/_integrations/wolflink.markdown index 480dcd87ffa..bfa33cdf21d 100644 --- a/source/_integrations/wolflink.markdown +++ b/source/_integrations/wolflink.markdown @@ -21,7 +21,8 @@ The integration fetches all data based on parameters, that are exposed by your h ### Tested devices -This integration is with Wolf Link Home Pro connected to a FGB-28 device. +- Wolf Link Home Pro connected to a FGB-28 device +- Wolf ISM7e / Link Pro connected to a COB-20 device ## Configuration diff --git a/source/_integrations/xiaomi.markdown b/source/_integrations/xiaomi.markdown index ef038ec5fa2..42503f3f218 100644 --- a/source/_integrations/xiaomi.markdown +++ b/source/_integrations/xiaomi.markdown @@ -35,7 +35,7 @@ Raspbian users: Don't forget to install `ffmpeg` support on your platform, other
      -The live stream writing by the camera is not a supported format when the hass reads through FTP for Yi 720p and Xiaofang Cameras, so this platform retrives the video which was saved 1 minute earlier. +The live stream writing by the camera is not a supported format when the hass reads through FTP for Yi 720p and Xiaofang Cameras, so this platform retrieves the video which was saved 1 minute earlier.
      diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown index 802d64c365d..922e9b6a2c3 100644 --- a/source/_integrations/xiaomi_miio.markdown +++ b/source/_integrations/xiaomi_miio.markdown @@ -63,7 +63,7 @@ After resetting the Wi-Fi settings of the Xiaomi robot vacuum, a new Access Toke

      These instructions are written for the Mi Home app - not for the new RoboRock app.

      -This token (32 hexadecimal characters) is required for the Xiaomi Mi Robot Vacuum, Mi Robot 2 (Roborock) Vacuum, Xiaomi Philips Lights and Xiaomi IR Remote. The Xiaomi Gateway uses another security method and requires a `key` (16 alphanumeric chars), which can be obtained easily via a hidden menu item at the Mi-Home app or using the `miio` command line tool. +This token (32 hexadecimal characters) is required for the Xiaomi Mi Robot Vacuum, Mi Robot 2 (Roborock) Vacuum, Xiaomi Philips Lights and Xiaomi IR Remote.
      ### Android (not rooted) @@ -1445,7 +1445,7 @@ Valid room numbers can be retrieved using miio command-line tool: miio protocol call get_room_mapping ``` -It will only give room numbers and not the room names. To mat the room numbers to your actual rooms, one can just test the clean_segment service with a number and see which room it cleans. The Xiaomi Home App will highlight the room after issuing the request, which makes the process rather convenient. +It will only give room numbers and not the room names. To map the room numbers to your actual rooms, one can just test the clean_segment service with a number and see which room it cleans. The Xiaomi Home App will highlight the room after issuing the request, which makes the process rather convenient. It seems to be the case that Numbers 1..15 are used to number the intitial segmentation done by the vacuum cleaner itself. Numbers 16 and upwards numbers rooms from the users manual editing. @@ -1649,7 +1649,7 @@ Please follow the instructions on [Retrieving the Access Token](/integrations/xi ### Xiaomi Smart WiFi Socket -Supported models: `chuangmi.plug.m1`, `chuangmi.plug.m3`, `chuangmi.plug.v2`, `chuangmi.plug.hmi205` +Supported models: `chuangmi.plug.m1`, `chuangmi.plug.m3`, `chuangmi.plug.v2`, `chuangmi.plug.hmi205`, `chuangmi.plug.hmi206` - Power (on, off) - Attributes diff --git a/source/_integrations/xmpp.markdown b/source/_integrations/xmpp.markdown index 26d93ac8c4b..f213113c352 100644 --- a/source/_integrations/xmpp.markdown +++ b/source/_integrations/xmpp.markdown @@ -8,6 +8,7 @@ ha_codeowners: - '@fabaff' - '@flowolf' ha_domain: xmpp +ha_iot_class: Cloud Push --- The `xmpp` notification platform allows you to deliver notifications from Home Assistant to a [Jabber (XMPP)](https://xmpp.org/) account. diff --git a/source/_integrations/yamaha.markdown b/source/_integrations/yamaha.markdown index 604a2f49cdc..bfe48aaa2da 100644 --- a/source/_integrations/yamaha.markdown +++ b/source/_integrations/yamaha.markdown @@ -4,6 +4,7 @@ description: Instructions on how to integrate Yamaha Network Receivers into Home ha_category: - Media Player ha_release: 0.16 +ha_iot_class: Local Polling ha_domain: yamaha --- @@ -14,6 +15,7 @@ Supported devices: - [HTR-4065](https://www.yamaha.com/cchtr4065/) - [RX-V473](https://ca.yamaha.com/en/products/audio_visual/av_receivers_amps/rx-v473/specs.html) - [RX-V573](https://ca.yamaha.com/en/products/audio_visual/av_receivers_amps/rx-v573/specs.html) +- [RX-V585](https://ca.yamaha.com/en/products/audio_visual/av_receivers_amps/rx-v585_u/specs.html) - [RX-V673](https://ca.yamaha.com/en/products/audio_visual/av_receivers_amps/rx-v673/specs.html) - [RX-V773](https://ca.yamaha.com/en/products/audio_visual/av_receivers_amps/rx-v773/specs.html) - And more diff --git a/source/_integrations/yamaha_musiccast.markdown b/source/_integrations/yamaha_musiccast.markdown index c54ff6ac18b..95afa542f75 100644 --- a/source/_integrations/yamaha_musiccast.markdown +++ b/source/_integrations/yamaha_musiccast.markdown @@ -6,6 +6,7 @@ ha_category: ha_release: 0.53 ha_codeowners: - '@jalmeroth' +ha_iot_class: Local Polling ha_domain: yamaha_musiccast --- diff --git a/source/_integrations/yandextts.markdown b/source/_integrations/yandextts.markdown index b92b614eb25..f198a5324e6 100644 --- a/source/_integrations/yandextts.markdown +++ b/source/_integrations/yandextts.markdown @@ -4,6 +4,7 @@ description: Instructions on how to setup Yandex SpeechKit TTS with Home Assista ha_category: - Text-to-speech ha_release: 0.36 +ha_iot_class: Cloud Push ha_domain: yandextts --- diff --git a/source/_integrations/zeroconf.markdown b/source/_integrations/zeroconf.markdown index 25765413154..86eb77ed3b9 100644 --- a/source/_integrations/zeroconf.markdown +++ b/source/_integrations/zeroconf.markdown @@ -8,6 +8,7 @@ ha_quality_scale: internal ha_codeowners: - '@Kane610' ha_domain: zeroconf +ha_iot_class: Local Push --- The `zeroconf` integration will scan the network for supported devices and services. Discovered integrations will show up in the discovered section on the integrations page in the configuration panel. It will also make Home Assistant discoverable for other services in the network. Zeroconf is also sometimes known as Bonjour, Rendezvous, and Avahi. diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index a30b2021d0c..c98beaf8bd8 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -40,7 +40,7 @@ There is also support for grouping of lights, switches, and fans (i.e. support f ## ZHA exception and deviation handling -Zigbee devices that deviate from or do not fully conform to the standard specifications set by the [Zigbee Alliance](https://zigbeealliance.org) may require the development of custom [ZHA Device Handlers](https://github.com/dmulcahey/zha-device-handlers) (ZHA custom quirks handler implementation) to for all their functions to work properly with the ZHA integration in Home Assistant. These ZHA Device Handlers for Home Assistant can thus be used to parse custom messages to and from Zigbee devices. +Zigbee devices that deviate from or do not fully conform to the standard specifications set by the [Zigbee Alliance](https://zigbeealliance.org) may require the development of custom [ZHA Device Handlers](https://github.com/dmulcahey/zha-device-handlers) (ZHA custom quirks handler implementation) for all their functions to work properly with the ZHA integration in Home Assistant. These ZHA Device Handlers for Home Assistant can thus be used to parse custom messages to and from Zigbee devices. The custom quirks implementations for zigpy implemented as ZHA Device Handlers for Home Assistant are a similar concept to that of [Hub-connected Device Handlers for the SmartThings Classics platform](https://docs.smartthings.com/en/latest/device-type-developers-guide/) as well as that of [Zigbee-Shepherd Converters as used by Zigbee2mqtt](https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html), meaning they are each virtual representations of a physical device that expose additional functionality that is not provided out-of-the-box by the existing integration between these platforms. @@ -64,7 +64,7 @@ ZHA integration uses a hardware independent Zigbee stack implementation with mod - Telegesis ETRX357USB (Note! This first have to be flashed with other EmberZNet firmware) - Telegesis ETRX357USB-LRS (Note! This first have to be flashed with other EmberZNet firmware) - Telegesis ETRX357USB-LRS+8M (Note! This first have to be flashed with other EmberZNet firmware) -- XBee Zigbee based radios (via the [zigpy-xbee](https://github.com/zigpy/zigpy-xbee) library for zigpy) +- Digi XBee Zigbee based radios (via the [zigpy-xbee](https://github.com/zigpy/zigpy-xbee) library for zigpy) - Digi XBee Series 3 (xbee3-24) modules - Digi XBee Series 2C (S2C) modules - Digi XBee Series 2 (S2) modules (Note! This first have to be flashed with Zigbee Coordinator API firmware) @@ -118,7 +118,7 @@ radio type. In the pop-up: - port speed (not applicable for all radios) - data flow control (not applicable for all radios) -Most devices need at very least the serial device path, like `/dev/ttyUSB0`, but it is recommended to use +Most devices need at the very least the serial device path, like `/dev/ttyUSB0`, but it is recommended to use device path from `/dev/serial/by-id` folder, e.g., `/dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_C0F003D3-if01-port0` @@ -205,6 +205,18 @@ You can choose if the IKEA or LEDVANCE provider should be set to enabled (`true` Note that the `otau_directory` setting is optional and can be used for any firmware files you have downloaded yourself. +### Defining Zigbee channel to use + +```yaml +zha: + zigpy_config: + network: + channel: 15 # What channel the radio should try to use. + channels: [15, 20, 25] # Channel mask +``` + +This is a good reference for channel selection [Zigbee and Wifi Coexistance](https://support.metageek.com/hc/en-us/articles/203845040-ZigBee-and-WiFi-Coexistence) + ## Adding devices To add a new device: @@ -216,6 +228,14 @@ To add a new device: ## Troubleshooting +To help resolve any kinks or compatibility problems by reporting bugs as issues with debug logs. Please follow the instructions in this troubleshooting section. + +### Knowing which devices are supported + +There is no official compatibility list of supported devices for the simple reason that practically all devices Zigbee Home Automation that are fully compliant with the standards and specifications as set by the [Zigbee Alliance](https://zigbeealliance.org) the should technically be compatible with this ZHA integration. The fact however remains that some hardware manufacturers do not always fully comply with each set specification which can cause a few devices to only partially work or not work at all with ZHA, but developers can create workarounds for such issues via a solution for 'ZHA exception and deviation handling' that this implementation features, please see that section for more information. + +Tip to new users is that while there is no official list of supported devices, some ZHA users take comfort that blakadder maintains an unofficial Zigbee Device Compatibility Repository which anyone can submit compatibility reports to, it can be found at [zigbee.blakadder.com](https://zigbee.blakadder.com) and currently contains independent compatibility lists and device pairing tips for several home automation gateway/bridge/hub software, including but not limited to open source Zigbee implementations such as; ZHA, Tasmota, Zigbee2MQTT, and ZiGate. + ### Reporting issues When reporting issues, please provide the following information in addition to information requested by issue template: @@ -259,7 +279,7 @@ Using a Philips Hue Dimmer Switch is probably the easiest way to factory-reset y 1. Turn on your Hue bulb you want to reset 2. Hold the Dimmer Switch near your bulb (< 10 cm) 3. Press and hold the (I)/(ON) and (O)/(OFF) buttons of the Dimmer Switch for about 10 seconds until your bulb starts to blink -4. Your bulb should stop blinking and eventually turning on again. At the same time, a green light on the top left of your remote indicates that your bulb has been successfully reset to factory settings. +4. Your bulb should stop blinking and eventually turn on again. At the same time, a green light on the top left of your remote indicates that your bulb has been successfully reset to factory settings. #### hue-thief diff --git a/source/_integrations/zone.markdown b/source/_integrations/zone.markdown index 17a983d882c..c1875a47608 100644 --- a/source/_integrations/zone.markdown +++ b/source/_integrations/zone.markdown @@ -3,6 +3,7 @@ title: Zone description: Instructions on how to set up zones within Home Assistant. ha_category: - Organization + - Presence Detection ha_release: 0.69 ha_quality_scale: internal ha_codeowners: diff --git a/source/_integrations/zwave.markdown b/source/_integrations/zwave.markdown index eb78e3f7c0e..ab7e07ed8d1 100644 --- a/source/_integrations/zwave.markdown +++ b/source/_integrations/zwave.markdown @@ -80,7 +80,7 @@ automation: temperature: 24 ``` -Generally, in Home Assistant, you can use the `homeassistant/turn_off` service to turn devices off. For the Remotec ZXT-120, you must instead make a service call like the following. +Generally, in Home Assistant, you can use the `homeassistant.turn_off` service to turn devices off. For the Remotec ZXT-120, you must instead make a service call like the following. ```yaml automation: @@ -99,13 +99,11 @@ automation: ### Test if it works -A simple way to test if your Z-Wave climate device is working is to use service developer tool icon **Services** from the **Developer Tools**. Choose the applicable Climate service from the list of **Available services:** and enter something like the sample below into the **Service Data** field and then press **CALL SERVICE**. +A simple way to test if your Z-Wave climate device is working is to use **Developer Tools** -> **Services**. Choose the applicable Climate service from the list of **Available services:** and enter something like the sample below into the **Service Data** field and then press **CALL SERVICE**. -```json -{ - "entity_id": "climate.remotec_zxt120_heating_1_id", - "hvac_mode": "Heat" -} +```yaml +entity_id: climate.remotec_zxt120_heating_1_id +hvac_mode: Heat ``` ## Cover diff --git a/source/_lovelace/alarm-panel.markdown b/source/_lovelace/alarm-panel.markdown index a31020d0ac0..edb26ff053d 100644 --- a/source/_lovelace/alarm-panel.markdown +++ b/source/_lovelace/alarm-panel.markdown @@ -4,13 +4,17 @@ sidebar_label: Alarm Panel description: "The Alarm Panel card allows you to Arm and Disarm your alarm control panel integrations." --- -The Alarm Panel card allows you to Arm and Disarm your alarm control panel integrations. +The Alarm Panel card allows you to Arm and Disarm your [alarm control panel](/integrations/#alarm) integrations.

      Screenshot of the alarm panel card Screenshot of the Alarm Panel card.

      +To add the Alarm Panel card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Alarm Panel** from the card picker. All options for this card can be configured via the user interface. + +Alternatively, the card can be configured using YAML: + ```yaml type: alarm-panel entity: alarm_control_panel.alarm diff --git a/source/_lovelace/button.markdown b/source/_lovelace/button.markdown index cfb15ad8e7e..683015300eb 100644 --- a/source/_lovelace/button.markdown +++ b/source/_lovelace/button.markdown @@ -11,6 +11,10 @@ The Button card allows you to add buttons to perform tasks. Screenshot of the Button card.

      +To add the Button card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Button** from the card picker. All options for this card can be configured via the user interface. + +Alternatively, the card can be configured using YAML: + ```yaml type: button entity: light.living_room diff --git a/source/_lovelace/calendar.markdown b/source/_lovelace/calendar.markdown index cd01ccb4366..2194b4e9c70 100644 --- a/source/_lovelace/calendar.markdown +++ b/source/_lovelace/calendar.markdown @@ -4,13 +4,15 @@ sidebar_label: Calendar description: "The calendar card displays your calendar entities in a month, day and list view" --- -The Calendar card displays your calendar entities in a month, day and list view. +The Calendar card displays your [calendar](/integrations/#calendar) entities in a month, day and list view.

      Screenshot of the calendar card - Screenshot of the calendar card. + Screenshot of the Calendar card.

      +To add the Calendar card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Calendar** from the card picker. All options for this card can be configured via the user interface. + ### Card Settings {% configuration_basic %} diff --git a/source/_lovelace/conditional.markdown b/source/_lovelace/conditional.markdown index a82ba6c9212..eceb1dc9efd 100644 --- a/source/_lovelace/conditional.markdown +++ b/source/_lovelace/conditional.markdown @@ -6,6 +6,8 @@ description: The Conditional card displays another card based on entity states. The Conditional card displays another card based on entity states. +To add the Conditional card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Conditional** from the card picker. All options for this card can be configured via the user interface. + {% configuration %} type: required: true diff --git a/source/_lovelace/entities.markdown b/source/_lovelace/entities.markdown index 63540c99193..91b8cc1acc0 100644 --- a/source/_lovelace/entities.markdown +++ b/source/_lovelace/entities.markdown @@ -6,6 +6,8 @@ description: "The Entities card is the most common type of card. It groups items The Entities card is the most common type of card. It groups items together into lists. +To add the Entities card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Entities** from the card picker. + {% configuration %} type: required: true @@ -374,7 +376,3 @@ entities: text: Are you sure you want to restart? service: script.libreelec_power_cycle ``` - -
      -Please be aware that the entity types divider and weblink aren't yet supported by the UI editor and a warning about `Expected a value of type...` is shown. You can ignore the warning and save your edits to verify. -
      diff --git a/source/_lovelace/entity.markdown b/source/_lovelace/entity.markdown index 737fd6e3265..82cae39e3b3 100644 --- a/source/_lovelace/entity.markdown +++ b/source/_lovelace/entity.markdown @@ -8,9 +8,11 @@ The Entity card gives you a quick overview of your entity's state.

      Screenshot of the entity card - Screenshot of the entity card. + Screenshot of the Entity card.

      +To add the Entity card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Entity** from the card picker. + {% configuration %} type: required: true @@ -50,6 +52,8 @@ footer: ## Example +Alternatively, the card can be configured using YAML: + ```yaml - type: entity entity: cover.kitchen_window diff --git a/source/_lovelace/gauge.markdown b/source/_lovelace/gauge.markdown index 4d0f362f1ac..1e99890eb22 100644 --- a/source/_lovelace/gauge.markdown +++ b/source/_lovelace/gauge.markdown @@ -8,9 +8,13 @@ The Gauge card is a basic card that allows visually seeing sensor data.

      Screenshot of the gauge card -Screenshot of the gauge card. +Screenshot of the Gauge card.

      +To add the Gauge card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Gauge** from the card picker. All options for this card can be configured via the user interface. + +Alternatively, the card can be configured using YAML: + ```yaml type: gauge entity: sensor.cpu_usage @@ -74,7 +78,7 @@ Title and Unit of Measurement Example: ```yaml type: gauge -name: CPU Usuage +name: CPU Usage unit: '%' entity: sensor.cpu_usage ``` diff --git a/source/_lovelace/glance.markdown b/source/_lovelace/glance.markdown index 45b808d4c9f..bc6d15a4c1e 100644 --- a/source/_lovelace/glance.markdown +++ b/source/_lovelace/glance.markdown @@ -8,9 +8,11 @@ The Glance card is useful to group multiple sensors in a compact overview. Keep

      Screenshot of the glance card -Screenshot of the glance card. +Screenshot of the Glance card.

      +To add the Glance card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Glance** from the card picker. + {% configuration %} type: required: true diff --git a/source/_lovelace/history-graph.markdown b/source/_lovelace/history-graph.markdown index 04fa9819ced..f5669bfd83c 100644 --- a/source/_lovelace/history-graph.markdown +++ b/source/_lovelace/history-graph.markdown @@ -8,14 +8,16 @@ The History Graph card allows you to display a graph for each of the entities li

      Screenshot of the history graph card for entities without a unit_of_measurement -Screenshot of the history graph card, when the sensor has no `unit_of_measurement` defined. +Screenshot of the History Graph card, when the sensor has no `unit_of_measurement` defined.

      Screenshot of the history graph card for entities with a unit_of_measurement -Screenshot of the history graph card, when the sensor has a `unit_of_measurement` defined. +Screenshot of the History Graph card, when the sensor has a `unit_of_measurement` defined.

      +To add the History Graph card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **History Graph** from the card picker. All options for this card can be configured via the user interface. + {% configuration %} type: required: true @@ -58,6 +60,8 @@ name: ## Example +Alternatively, the card can be configured using YAML: + ```yaml type: history-graph title: 'My Graph' diff --git a/source/_lovelace/horizontal-stack.markdown b/source/_lovelace/horizontal-stack.markdown index 4fc74ed3aa3..fdbfaf6607f 100644 --- a/source/_lovelace/horizontal-stack.markdown +++ b/source/_lovelace/horizontal-stack.markdown @@ -6,6 +6,8 @@ description: "The Horizontal Stack card allows you to stack together multiple ca The Horizontal Stack card allows you to stack together multiple cards, so they always sit next to each other in the space of one column. +To add the Horizontal Stack card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Horizontal Stack** from the card picker. All options for this card can be configured via the user interface. + {% configuration %} type: required: true @@ -37,5 +39,5 @@ cards:

      Two picture cards in a horizontal stack card - Two picture cards in a horizontal stack card. + Two Picture cards in a Horizontal Stack card.

      diff --git a/source/_lovelace/humidifier.markdown b/source/_lovelace/humidifier.markdown index ce853fbfc8f..3735d50d1ed 100644 --- a/source/_lovelace/humidifier.markdown +++ b/source/_lovelace/humidifier.markdown @@ -11,6 +11,8 @@ The Humidifier card lets you control and monitor humidifiers, dehumidifiers, and Screenshot of the humidifier card.

      +To add the Humidifier card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Humidifier** from the card picker. All options for this card can be configured via the user interface. + {% configuration %} type: required: true @@ -33,6 +35,8 @@ theme: ## Example +Alternatively, the card can be configured using YAML: + ```yaml - type: humidifier entity: humidifier.bedroom diff --git a/source/_lovelace/iframe.markdown b/source/_lovelace/iframe.markdown index 24db48ba9ee..71490ecd710 100644 --- a/source/_lovelace/iframe.markdown +++ b/source/_lovelace/iframe.markdown @@ -15,6 +15,8 @@ You can't embed sites using HTTP if you are using HTTPS for your Home Assistant. Windy weather radar as Webpage.

      +To add the Webpage card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Webpage** from the card picker. All options for this card can be configured via the user interface. + {% configuration %} type: required: true @@ -37,6 +39,8 @@ title: ### Examples +The card can also be configured using YAML, some examples below: + ```yaml type: iframe url: https://grafana.localhost/d/000000027/worldping-endpoint-summary?var-probe=All&panelId=2&fullscreen&orgId=3&theme=light diff --git a/source/_lovelace/light.markdown b/source/_lovelace/light.markdown index 36d2a53f626..97f7a73aca3 100644 --- a/source/_lovelace/light.markdown +++ b/source/_lovelace/light.markdown @@ -11,6 +11,10 @@ The Light card allows you to change the brightness of the light. Screenshot of the Light card.

      +To add the Light card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Light** from the card picker. All options for this card can be configured via the user interface. + +Alternatively, the card can be configured using YAML: + ```yaml type: light entity: light.bedroom @@ -39,6 +43,14 @@ theme: required: false description: Set to any theme within `themes.yaml`. type: string +hold_action: + required: false + description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action). + type: map +double_tap_action: + required: false + description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action). + type: map {% endconfiguration %} ## Examples diff --git a/source/_lovelace/map.markdown b/source/_lovelace/map.markdown index 611ad44655c..75f83599340 100644 --- a/source/_lovelace/map.markdown +++ b/source/_lovelace/map.markdown @@ -11,6 +11,8 @@ The Map card that allows you to display entities on a map Screenshot of the map card.

      +To add the Map card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Map** from the card picker. All options for this card can be configured via the user interface. + {% configuration %} type: required: true @@ -63,6 +65,8 @@ hours_to_show: ## Examples +The card can also be configured using YAML, some examples below: + ```yaml type: map aspect_ratio: 16:9 diff --git a/source/_lovelace/markdown.markdown b/source/_lovelace/markdown.markdown index 6b443900371..2de258affc3 100644 --- a/source/_lovelace/markdown.markdown +++ b/source/_lovelace/markdown.markdown @@ -10,9 +10,11 @@ The renderer uses [Marked.js](https://marked.js.org), which supports [several sp

      Screenshot of the markdown card -Screenshot of the markdown card. +Screenshot of the Markdown card.

      +To add the Markdown card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Markdown** from the card picker. + {% configuration %} type: required: true @@ -45,6 +47,8 @@ theme: ## Example +The card can also be configured using YAML, some examples below: + ```yaml type: markdown content: > diff --git a/source/_lovelace/media-control.markdown b/source/_lovelace/media-control.markdown index 61460487489..181662cc289 100644 --- a/source/_lovelace/media-control.markdown +++ b/source/_lovelace/media-control.markdown @@ -8,9 +8,11 @@ The Media Control card is used to display [Media Player](/integrations/#media-pl

      Screenshot of the media player control card -Screenshot of the media player control card. +Screenshot of the Media Control card.

      +To add the Media Control card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Media Control** from the card picker. + {% configuration %} type: required: true @@ -29,6 +31,8 @@ name: ## Example +Alternatively, the card can be configured using YAML: + ```yaml type: media-control entity: media_player.lounge_room diff --git a/source/_lovelace/plant-status.markdown b/source/_lovelace/plant-status.markdown index 221345752a1..edcbd4912f6 100644 --- a/source/_lovelace/plant-status.markdown +++ b/source/_lovelace/plant-status.markdown @@ -11,6 +11,8 @@ The Plant Status card is for all the lovely botanists out there. Screenshot of the plant status card.

      +To add the Plant Status card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Plant Status** from the card picker. All options for this card can be configured via the user interface. + {% configuration %} type: required: true @@ -33,6 +35,8 @@ theme: ## Example +Alternatively, the card can be configured using YAML: + ```yaml type: plant-status entity: plant.bonsai diff --git a/source/_lovelace/sensor.markdown b/source/_lovelace/sensor.markdown index d47eef1de3a..01949b77cc8 100644 --- a/source/_lovelace/sensor.markdown +++ b/source/_lovelace/sensor.markdown @@ -11,6 +11,8 @@ The Sensor card gives you a quick overview of your sensors state with an optiona Screenshot of the sensor card.

      +To add the Sensor card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Sensor** from the card picker. All options for this card can be configured via the user interface. + {% configuration %} type: required: true @@ -54,6 +56,8 @@ theme: ## Example +Alternatively, the card can be configured using YAML: + ```yaml type: sensor entity: sensor.illumination diff --git a/source/_lovelace/shopping-list.markdown b/source/_lovelace/shopping-list.markdown index 276128687cc..ba1893b3960 100644 --- a/source/_lovelace/shopping-list.markdown +++ b/source/_lovelace/shopping-list.markdown @@ -6,13 +6,18 @@ description: "The Shopping List card allows you to add, edit, check-off, and cle The Shopping List card allows you to add, edit, check-off, and clear items from your shopping list. -Setup of the [Shopping List Intent](/integrations/shopping_list/) is required +Setup of the [Shopping List integration](/integrations/shopping_list/) is required.

      Screenshot of the shopping list card Screenshot of the Shopping List card.

      + +To add the Shopping List card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Shopping List** from the card picker. All options for this card can be configured via the user interface. + +Alternatively, the card can be configured using YAML: + ```yaml type: shopping-list ``` diff --git a/source/_lovelace/thermostat.markdown b/source/_lovelace/thermostat.markdown index b56883fe984..ffba79e7b41 100644 --- a/source/_lovelace/thermostat.markdown +++ b/source/_lovelace/thermostat.markdown @@ -1,16 +1,18 @@ --- title: "Thermostat Card" sidebar_label: Thermostat -description: "The Thermostat card gives control of your climate entity. Allowing you to change the temperature and mode of the entity." +description: "The Thermostat card gives control of your climate entity, allowing you to change the temperature and mode of the entity." --- -The Thermostat card gives control of your climate entity. Allowing you to change the temperature and mode of the entity. +The Thermostat card gives control of your [climate](/integrations/#climate) entity, allowing you to change the temperature and mode of the entity.

      Screenshot of the thermostat card - Screenshot of the thermostat card. + Screenshot of the Thermostat card.

      +To add the Thermostat card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Thermostat** from the card picker. All options for this card can be configured via the user interface. + {% configuration %} type: required: true @@ -33,6 +35,8 @@ theme: ## Example +Alternatively, the card can be configured using YAML: + ```yaml type: thermostat entity: climate.nest diff --git a/source/_lovelace/vertical-stack.markdown b/source/_lovelace/vertical-stack.markdown index 6d12f2dc03c..23bb093243e 100644 --- a/source/_lovelace/vertical-stack.markdown +++ b/source/_lovelace/vertical-stack.markdown @@ -6,6 +6,8 @@ description: "The Vertical Stack card allows you to group multiple cards so they The Vertical Stack card allows you to group multiple cards so they always sit in the same column. +To add the Vertical Stack card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Vertical Stack** from the card picker. All options for this card can be configured via the user interface. + {% configuration %} type: required: true @@ -23,6 +25,8 @@ cards: ### Examples +Alternatively, the card can be configured using YAML: + Basic example: ```yaml @@ -39,7 +43,7 @@ cards:

      Picture- and entities-card in a stack - Picture- and entities-card in a stack. + Picture and entities-card in a stack.

      Combination of vertical and horizontal stack card: diff --git a/source/_lovelace/weather-forecast.markdown b/source/_lovelace/weather-forecast.markdown index f8f47cb37db..b363b5d32e0 100644 --- a/source/_lovelace/weather-forecast.markdown +++ b/source/_lovelace/weather-forecast.markdown @@ -8,9 +8,10 @@ The Weather Forecast card displays the weather. Very useful to include on interf

      Screenshot of the weather card - Screenshot of the weather card. + Screenshot of the Weather card.

      +To add the Weather card to your user interface, click the Lovelace menu (three dots at the top right of the screen) and then **Edit Dashboard**. Click the plus button in the bottom right corner and select **Weather** from the card picker. ### Card Settings @@ -83,7 +84,7 @@ entity: weather.openweathermap ##### Themeable Icons -The default weather icons are themable via a [Theme](https://www.home-assistant.io/integrations/frontend/#themes). Theme variables include: +The default weather icons are themable via a [theme](/integrations/frontend/#themes). Theme variables include: ```yaml --weather-icon-cloud-front-color @@ -106,7 +107,7 @@ Example theme configuration: ##### Personal Icons -Weather icons can be overwritten with your own personal images via a [Theme](https://www.home-assistant.io/integrations/frontend/#themes). Theme variables include: +Weather icons can be overwritten with your own personal images via a [theme](/integrations/frontend/#themes). Theme variables include: ```yaml --weather-icon-clear-night diff --git a/source/_posts/2020-10-07-release-116.markdown b/source/_posts/2020-10-07-release-116.markdown new file mode 100644 index 00000000000..65022e06a43 --- /dev/null +++ b/source/_posts/2020-10-07-release-116.markdown @@ -0,0 +1,1547 @@ +--- +layout: post +title: "0.116: Entities card row editor, restore snapshots and performance metrics" +description: "Snapshots can now be uploaded and restored during onboarding. Entities card rows now have a UI editor, automation editor weekday support, and Supervisor performance metrics" +date: 2020-10-07 00:00:00 +date_formatted: "October 7, 2020" +author: Franck Nijhof +author_twitter: frenck +comments: true +categories: Release-Notes +og_image: /images/blog/2020-10-0.116/social.png +--- + + + +Home Assistant Core 0.116! + +So, how have you been? Fully processed the massive 0.115 birthday release yet? + +Honestly, I haven't. There was soo much in 0.115, and to me, it feels like that +release was yesterday. 😅 + +So, today, a nice size, manageable release that brings some smaller things to +the table. Lots of fixes, UI tweaks and improvements; hopefully a smooth sail! + +The biggest changes can be found in the Supervisor. [@ludeeus] has been smashing +on his keyboard to add the option to upload and restore snapshots during +onboarding. A much-upvoted WTH. As a bonus, he also added performance +metrics to the Supervisor UI. Nice work! + +As always, enjoy the release! + +../Frenck + +- [Entities card editor](#entities-card-editor) +- [User and person management combined](#user-and-person-management-combined) +- [Restore snapshots](#restore-snapshots) +- [Performance metrics in the Supervisor UI](#performance-metrics-in-the-supervisor-ui) +- [H.265 stream support for Android](#h265-stream-support-for-android) +- [Automation editor has now weekday support](#automation-editor-has-now-weekday-support) +- [Python 3.7 deprecated](#python-37-deprecated) +- [Other noteworthy changes](#other-noteworthy-changes) +- [New Integrations](#new-integrations) +- [New Platforms](#new-platforms) +- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui) +- [Release 0.116.1 - October 8](#release-01161---october-8) +- [Release 0.116.2 - October 9](#release-01162---october-9) +- [Release 0.116.3 - October 15](#release-01163---october-15) +- [Release 0.116.4 - October 15](#release-01164---october-15) +- [If you need help...](#if-you-need-help) +- [Breaking Changes](#breaking-changes) +- [All changes](#all-changes) + +## Entities card editor + +You can now edit the entity rows of your entity card. That means you can +not only set an entity id, but also set the name, icon and secondary info. + +

      +Screenshot of the new editor for the entity card. +You can now edit the entity row; adjust the name, icon and secondary info. +

      + +Also, using special rows will no longer force you use the YAML editor, however, +you you can still use the UI editor and edit the special rows. UI editors for +the special rows will come in the future. + +## User and person management combined + +We combined the user and person UI, this means that the user configuration +panel will only be visible for users that have advanced mode enabled. + +The person detail dialog now has a toggle that allows you to give the person +access to Home Assistant. If you toggle it on, you can set a username and a +password for the person. If you toggle it off, the user will be removed. + +This makes it easier to manage the people in Home Assistant, +everything in one place. + +

      +Screenshot of the person "allow to login" option. +The person edit dialog now has a toggle to allow a person to log in. +

      + +## Restore snapshots + +You can now upload snapshots from the UI and restores them. You can do this in +the supervisor UI in the snapshots panel. But you can also do this during +onboarding! + +

      +Screen recording of restoring a snapshot during onboarding. +Screen recording of restoring a snapshot during onboarding. +

      + +This means you no longer have to set up Home Assistant, add and set up the Samba +add-on to then restore your snapshot. Instead, you can just select your snapshot +in the first step of the onboarding and it will be restored. + +This makes moving to another system a breeze! + +## Performance metrics in the Supervisor UI + +The Supervisor now shows performance metrics in its UI, so you'll have a better +idea of how much resources are used. Thanks [@ludeeus]! + +

      +Screenshot of the new Supervisor performance metrics. +Supervisor UI now shows performance metrics. +

      + +## H.265 stream support for Android + +[@uvjustin] added support for H.265 streaming in the Android app, it will use a +native video player that is shown on top of the Home Assistant UI. This player +will only work in the more info dialog, and can not be used In Lovelace cards. + +## Automation editor has now weekday support + +[@misiu] added a nice feature to the automation editor. Using a time +condition in the UI, now has the ability to select the weekdays the condition +should test against. + +

      +Screenshot of the new weekday conditions. +You can now select the days to match in time conditions. +

      + +## Python 3.7 deprecated + +Python 3.9 has been released on 5 October. This means that Python 3.7 support +is now deprecated and will be removed after two months (which will be +effective in 0.118). + +This is only a concern if you are running Home Assistant Core directly on +Python. You can check the Python version Home Assistant uses by going to the +information screen in **Configuration** -> **Info**. + +If you run Home Assistant OS, Supervised or Container, you don't have to worry +about this, as the Home Assistant project takes care of this for you. As a +matter of fact, if you use one of those methods, you are already running +Python 3.8. + +We are currently working on ensuring Python 3.9 is fully supported and tested. + +## Other noteworthy changes + +- [MQTT now supports tag scanning](/integrations/tag.mqtt), thanks to [@emontnemery]. +- The Hyperion integration had a large overhaul by [@dermotduffy], ensuring + this integration now actually works! +- [@Misiu] ensured the OpenWeatherMap integration supports all languages + it can provide. +- The utility meter now supports a bi-weekly cycle, thanks to [@hareeshmu]. +- [@timkoers] added uptime sensors for network clients to the UniFi integration. +- The Shelly integration now shows power and energy sensors for roller mode + devices, thanks to [@firstof9]. +- You can now filter history by using glob matching filters. For example, you + can now exclude `sensor.*_temperature` from being recorded. Thanks [@bdraco]! +- deCONZ has a new option; You can now disable the automatic addition of new + devices. Furthermore, [@Kane610] also added a service to clean up up + orphaned devices. Thanks! + +## New Integrations + +We welcome the following new integration this release: + +- [Raspberry Pi Power Supply Checker][rpi_power docs], added by [@shenxn] +- [Zodiac][zodiac docs], added by [@JulienTant] +- [Hayward OmniLogic][omnilogic docs], added by [@Oliver84] +- [GoalZero][goalzero docs], added by [@tkdrob] + +## New Platforms + +The following integration got support for a new platform: + +- [Synology DSM][synology_dsm docs] now supports cameras, added by [@shenxn] +- [HVV Departures][hvv_departures docs] added binary sensors to show elevator + statuses. Added by [@vigonotion] +- Support for covers was added to [Modbus][modbus docs], by [@vzahradnik] +- [Firmata][firmata docs] to support analog input and PWM/analog output + Added by [@DaAwesomeP] +- [NZBGet][nzbget docs] now has a switch to control downloads, + added by [@ctalkington] + +## Integrations now available to set up from the UI + +The following integrations are now available via the Home Assistant UI: + +- [AlarmDecoder][alarmdecoder docs], done by [@ajschmidt8] +- [Canary][canary docs], done by [@ctalkington] + +## Release 0.116.1 - October 8 + +- Update Pyhiveapi Library Version ([@KJonline] - [#40804]) ([hive docs]) +- Ensure recorder commit can retry after encountering invalid data ([@bdraco] - [#41426]) ([recorder docs]) +- Downgrade Paho MQTT to 1.5.0 ([@balloob] - [#41479]) ([mqtt docs]) +- Bump pyatmo version to 4.1.0 ([@cgtobi] - [#41487]) ([netatmo docs]) +- Fix async_unload_entry for devolo Home Control ([@Shutgun] - [#41488]) ([devolo_home_control docs]) +- Update frontend to 20201001.2 ([@bramkragten] - [#41491]) ([frontend docs]) +- Add missing on states to media player groups ([@bdraco] - [#41496]) + +[#40804]: https://github.com/home-assistant/core/pull/40804 +[#41426]: https://github.com/home-assistant/core/pull/41426 +[#41479]: https://github.com/home-assistant/core/pull/41479 +[#41487]: https://github.com/home-assistant/core/pull/41487 +[#41488]: https://github.com/home-assistant/core/pull/41488 +[#41491]: https://github.com/home-assistant/core/pull/41491 +[#41496]: https://github.com/home-assistant/core/pull/41496 +[@KJonline]: https://github.com/KJonline +[@Shutgun]: https://github.com/Shutgun +[@balloob]: https://github.com/balloob +[@bdraco]: https://github.com/bdraco +[@bramkragten]: https://github.com/bramkragten +[@cgtobi]: https://github.com/cgtobi +[devolo_home_control docs]: /integrations/devolo_home_control/ +[frontend docs]: /integrations/frontend/ +[hive docs]: /integrations/hive/ +[mqtt docs]: /integrations/mqtt/ +[netatmo docs]: /integrations/netatmo/ +[recorder docs]: /integrations/recorder/ + +## Release 0.116.2 - October 9 + +- Fix Netatmo non specified sensor types ([@cgtobi] - [#41517]) ([netatmo docs]) +- Update Arris TG2492LG dependency version ([@vanbalken] - [#41465]) ([arris_tg2492lg docs]) +- Fix omnilogic temperature sensor with metric setting ([@djtimca] - [#41509]) ([omnilogic docs]) +- Restore group support to plant entities ([@bdraco] - [#41519]) ([group docs]) ([plant docs]) +- Bump yeelight to 0.5.4 ([@shenxn] - [#41524]) ([yeelight docs]) +- Fix description reference in PoolSense config flow ([@bieniu] - [#41535]) ([poolsense docs]) +- Fix missing weather sensors ([@cgtobi] - [#41540]) ([netatmo docs]) + +[#41465]: https://github.com/home-assistant/core/pull/41465 +[#41509]: https://github.com/home-assistant/core/pull/41509 +[#41517]: https://github.com/home-assistant/core/pull/41517 +[#41519]: https://github.com/home-assistant/core/pull/41519 +[#41524]: https://github.com/home-assistant/core/pull/41524 +[#41535]: https://github.com/home-assistant/core/pull/41535 +[#41540]: https://github.com/home-assistant/core/pull/41540 +[@bdraco]: https://github.com/bdraco +[@bieniu]: https://github.com/bieniu +[@cgtobi]: https://github.com/cgtobi +[@djtimca]: https://github.com/djtimca +[@shenxn]: https://github.com/shenxn +[@vanbalken]: https://github.com/vanbalken +[arris_tg2492lg docs]: /integrations/arris_tg2492lg/ +[group docs]: /integrations/group/ +[netatmo docs]: /integrations/netatmo/ +[omnilogic docs]: /integrations/omnilogic/ +[plant docs]: /integrations/plant/ +[poolsense docs]: /integrations/poolsense/ +[yeelight docs]: /integrations/yeelight/ + +## Release 0.116.3 - October 15 + +- Add delete to hassio API ([@ludeeus] - [#41500]) ([hassio docs]) (new-integration) +- Fix disabled Synology DSM camera ([@Quentame] - [#41686]) ([synology_dsm docs]) +- Fix KEF LSX becoming unavailable ([@basnijholt] - [#41700]) ([kef docs]) +- Ensure all template errors are caught and the websocket api reports them ([@bdraco] - [#41719]) ([websocket_api docs]) +- Offload dockermachines into core ([@pvizeli] - [#41756]) +- Fix issues with metric conversion and single pump type for filter pumps in Omnilogic integration ([@djtimca] - [#41777]) ([omnilogic docs]) +- Fix SimpliSafe re-auth flow ([@bachya] - [#41805]) ([simplisafe docs]) +- Shelly: fix for RGB devices ([@chemelli74] - [#41841]) ([shelly docs]) +- Permit event trackers to accept an empty list of entities or domains ([@bdraco] - [#41857]) +- Reduce polling for Netatmo weather station sensors ([@cgtobi] - [#41858]) ([netatmo docs]) + +[#41500]: https://github.com/home-assistant/core/pull/41500 +[#41686]: https://github.com/home-assistant/core/pull/41686 +[#41700]: https://github.com/home-assistant/core/pull/41700 +[#41719]: https://github.com/home-assistant/core/pull/41719 +[#41756]: https://github.com/home-assistant/core/pull/41756 +[#41777]: https://github.com/home-assistant/core/pull/41777 +[#41805]: https://github.com/home-assistant/core/pull/41805 +[#41841]: https://github.com/home-assistant/core/pull/41841 +[#41857]: https://github.com/home-assistant/core/pull/41857 +[#41858]: https://github.com/home-assistant/core/pull/41858 +[@Quentame]: https://github.com/Quentame +[@bachya]: https://github.com/bachya +[@basnijholt]: https://github.com/basnijholt +[@bdraco]: https://github.com/bdraco +[@cgtobi]: https://github.com/cgtobi +[@chemelli74]: https://github.com/chemelli74 +[@djtimca]: https://github.com/djtimca +[@ludeeus]: https://github.com/ludeeus +[@pvizeli]: https://github.com/pvizeli +[hassio docs]: /integrations/hassio/ +[kef docs]: /integrations/kef/ +[netatmo docs]: /integrations/netatmo/ +[omnilogic docs]: /integrations/omnilogic/ +[shelly docs]: /integrations/shelly/ +[simplisafe docs]: /integrations/simplisafe/ +[synology_dsm docs]: /integrations/synology_dsm/ +[websocket_api docs]: /integrations/websocket_api/ + +## Release 0.116.4 - October 15 + +- Bump ONVIF and pin Zeep ([@hunterjm] - [#41907]) ([onvif docs]) +- Cap AVC profile level at 4.1 in stream master playlist ([@uvjustin] - [#41592]) ([stream docs]) + +[#41592]: https://github.com/home-assistant/core/pull/41592 +[#41879]: https://github.com/home-assistant/core/pull/41879 +[#41907]: https://github.com/home-assistant/core/pull/41907 +[@hunterjm]: https://github.com/hunterjm +[@pvizeli]: https://github.com/pvizeli +[@uvjustin]: https://github.com/uvjustin +[onvif docs]: /integrations/onvif/ +[stream docs]: /integrations/stream/ + +## If you need help... + +...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). + +Experiencing issues introduced by this release? Please report them in our [issue tracker](https://github.com/home-assistant/core/issues). Make sure to fill in all fields of the issue template. + + + +## 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. + +
      + Custom Lovelace Cards +

      + +This release contains breaking changes for custom card developers, check the +[developers blog](https://developers.home-assistant.io/blog/2020/10/02/lazyMoreInfo) +for more information. + +If you have a custom card that stopped working this release, please report +this with the custom card author. + +

      +
      + +
      + AlarmDecoder +

      + +YAML support for AlarmDecoder has been removed in favor of UI configuration. +Additionally, the `panel_display` option has been removed and the alarm display +sensor will always be created with AlarmDecoder now. Please see the updated +[AlarmDecoder documentation][alarmdecoder docs] for instructions on how to +set up AlarmDecoder via the UI. + +([@ajschmidt8] - [#37998]) ([alarmdecoder docs]) + +

      +
      + +
      + Automation +

      + +State conditions with attribute specified: When testing against a non-string +attribute value, you now need to specify the value in your configuration in the +same type as it is in the attribute (instead of as a string). + +([@balloob] - [#41261]) + +

      +
      + +
      + Canary +

      + +Canary is now available for configuration via the UI. This also means its no +longer configured in YAML. Existing configurations should be automatically +transitioned to configuration via UI. You can safely remove you Canary YAML +configuration after ugprading. YAML support will be fully removed in +Home Assistant 0.118.0. + +([@ctalkington] - [#40055]) ([canary docs]) + +

      +
      + +
      + HomeKit Controller, Plant, SmartThings, Xiaomi +

      + +Some integrations (`homekit_controller`, `plant`, `smartthings` +and `xiaomi_miio`) previously used `lux` as their unit of measurement for +entities that covered illuminance. Now, these entities use `lx` as their unit +of measurement to be consistent with other integrations. + +This could be a breaking change for using such entities in, +for example, `influxdb`. + +([@springstan] - [#40171]) + +

      +
      + +
      + Hyperion +

      + +Fixes the Hyperion Integration to work with the current Hyperion-NG release. +Refactors to rely on the +[hyperion-py](https://github.com/dermotduffy/hyperion-py) client. + +The `default_color`, `hdmi_priority` and `effect_list` parameters no longer have +any effect. Instead, users should use [light profiles](/integrations/light/) +as default color. + +The `effect_list` is now automatically populated. + +The `hdmi_priority` parameter no longer make sense with Hyperion-NG and will +be removed in a future release. + +([@dermotduffy] - [#39738]) ([hyperion docs]) + +

      +
      + +
      + KNX +

      + +We changed the way how we handle binary sensors in the underlying library. It +is no longer possible to support automations based on the `binary_sensor` +schema. Instead, you can use the new `counter` state attribute for any given +KNX binary sensor. + +Before this change: + +```yaml +- name: cover_abstell + state_address: "2/0/33" + automation: + - counter: 1 + hook: 'on' + action: + - entity_id: cover.sonne_abstellkammer + service: cover.open_cover + - counter: 1 + hook: 'off' + action: + - entity_id: cover.sonne_abstellkammer + service: cover.close_cover +``` + +After this change: + +```yaml +# binary_sensor.yaml +- name: cover_abstell + state_address: "2/0/33" +``` + +```yaml +# automation.yaml +automation: + - alias: 'Binary sensor test counter=1 on' + trigger: + platform: numeric_state + entity_id: binary_sensor.cover_abstell + attribute: counter + above: 0 + below: 2 + condition: + - condition: state + entity_id: binary_sensor.cover_abstell + state: 'on' + action: + - service: cover.open_cover + entity_id: cover.sonne_abstellkammer + + - alias: 'Binary sensor test counter=1 off' + trigger: + platform: numeric_state + entity_id: binary_sensor.cover_abstell + attribute: counter + above: 0 + below: 2 + condition: + - condition: state + entity_id: binary_sensor.cover_abstell + state: 'off' + action: + - service: cover.close_cover + entity_id: cover.sonne_abstellkammer +``` + +If you intend to use the counter feature (counter > 1) make sure you also +enable `ignore_internal_state` (default: `true`) for your `binary_sensor` and +set the new `context_timeout` attribute to the time in between you want it to +react to your sensor clicks (defaults to `1` - which should be fine). +Otherwise, the counter will not work correctly. + +([@marvin-w] - [#40304]) ([knx docs]) + +

      +
      + +
      + Logbook +

      + +Message and domain are now removed from the logbook `state_changed` events. + +These are now handled by the frontend as we move closer to making the logbook +localized. + +([@bdraco] - [#40070]) ([logbook docs]) + +

      +
      + +
      + Material Design Icons +

      + +The Material Design Icons are updated to v5.6.55, the `mdi:scooter` icon is +replaced by a new icon, the old icon is available as `mdi:human-scooter` + +

      +
      + +
      + Pilight +

      + +Lights using the Pilight integration will now turn on to the last used +brightness instead of its maximum brightness. + +If you want to retain you lights turning on to its maximum brightness you can +set the default intensity in the `light_profiles.csv` file. + +The steps to set this up: + +1. In the your main `config` folder (where you'll find `configuration.yaml`) + create a new file called `light_profiles.csv`. +2. For each of lights add an line with its entity id and the brightness + you want, as a value from `0` to `255`. + +Example: + +```txt +light..default,0,0,255 +``` + +([@daniel-jong] - [#39549]) ([pilight docs]) + +

      +
      + +
      + Synology +

      + +The Synology integration is now deprecated. You should now use the Synology DSM +instead. Support for cameras has been added to the Synology DSM integration +making it a full replacement. + +([@shenxn] - [#39958]) ([synology docs]) + +

      +
      + +
      + System Monitor +

      + +Not really a breaking change, since the overall logic did not change. Arguments +that were previously mandatory for sensors of this integration are still +mandatory and optional arguments remain optional. + +However, we now enforce those mandatory arguments to be present, +since otherwise this integration creates entities that cannot do anything, +e.g., the sensor for IPv4 addresses cannot do anything if no network interface +is specified from which to take the IP. + +If the integration fails to load, check the log to see which arguments are +missing in your configuration. The documentation also has been updated to +clearly show which arguments are mandatory. + +([@spacegaier] - [#39687]) ([systemmonitor docs]) + +

      +
      + +
      + TekSavvy +

      + +The TekSavvy integration has been removed. The API that was used by this +integration is no longer available. + +([@mikeodr] - [#40762]) + +

      +
      + +
      + Universal Devices ISY994 / LCN +

      + +The Kelvin unit no longer includes the degree sign in accordance with +scientific standards. If you use the `isy994` and `lcn` integrations you may +need to update automations or data collectors that depend on the unit of +measurement. + +([@RichieFrame] - [#40574]) ([isy994 docs]) + +

      +
      + +
      + VeSync +

      + +The auto fan mode for the fan platform has been removed. The auto mode isn't +supported by the entity model in Home Assistant and was initially added +overlooking our entity model. + +If you have automations or scripts targeting the VeSync fan entity should +review these and update as needed. + +([@TheGardenMonkey] - [#40559]) ([vesync docs]) + +

      +
      + +
      + ZHA +

      + +The `ieee_address` parameter was renamed to `ieee` for `zha.permit` +and `zha.remove` services. + +This makes all services to use consistently named parameters. + +([@Adminiuga] - [#40652]) ([zha docs]) + +

      +
      + +## All changes + +
      + Click to see all changes! + +- Add missing EDL21 OBIS codes ([@DAMEK86] - [#39714]) ([edl21 docs]) +- Bump version to 0.116.0dev0 ([@frenck] - [#39768]) +- Bump Synology DSM to 0.9.0 ([@Quentame] - [#39819]) ([synology_dsm docs]) +- Add systemmonitor check for mandatory "arg" of sensors ([@spacegaier] - [#39687]) ([systemmonitor docs]) (breaking-change) +- Allow setting of hvac_mode when setting temperature in ozw ([@firstof9] - [#39853]) ([ozw docs]) +- Prompt user to reauthenticate AirVisual when API key expires ([@bachya] - [#38341]) ([airvisual docs]) +- Upgrade sentry-sdk to 0.17.4 ([@frenck] - [#39868]) ([sentry docs]) +- Bump pyTibber to 0.15.2 ([@soldag] - [#39870]) ([tibber docs]) +- Upgrade isort to 5.5.2 ([@frenck] - [#39879]) +- Use entity_class 'safety' in synology_dsm storage sensors ([@Mariusthvdb] - [#39757]) ([synology_dsm docs]) +- Optimize requirements check with stdlib ([@balloob] - [#39871]) +- Remove stale debug from WLED tests ([@frenck] - [#39882]) ([wled docs]) +- Add Carbon Monoxide binary sensor to Homekit Controller ([@RogerSelwyn] - [#39889]) ([homekit_controller docs]) +- Increase template test coverage. ([@bdraco] - [#39908]) +- Add zeroconf discovery to homekit ([@bdraco] - [#39907]) ([homekit docs]) +- Upgrade numpy to 1.19.2 ([@frenck] - [#39912]) ([iqvia docs]) ([opencv docs]) ([tensorflow docs]) ([trend docs]) +- Add camera support to synology_dsm ([@shenxn] - [#39838]) ([synology_dsm docs]) (new-platform) +- Add async_track_state_removed_domain to allow tracking when a state is removed from a domain ([@bdraco] - [#39859]) +- Device automation triggers for stateless HomeKit accessories ([@Jc2k] - [#39090]) ([homekit_controller docs]) +- Activate hassfest requirements CI check ([@MartinHjelmare] - [#39940]) +- Use STATE_UNKNOWN constant in dlink and ecobee ([@springstan] - [#39948]) ([dlink docs]) ([ecobee docs]) +- Add template filter timedelta_seconds to create a timedelta from seconds ([@jschlyter] - [#39608]) +- Remove unchecked return value in synology_dsm ([@shenxn] - [#39929]) ([synology_dsm docs]) +- Use sound, vibration and safety device class constants in various integrations ([@springstan] - [#39952]) ([concord232 docs]) ([ffmpeg_noise docs]) ([meteoalarm docs]) ([mysensors docs]) ([nest docs]) ([smartthings docs]) ([wink docs]) +- Improve tests for Broadlink devices ([@felipediel] - [#39898]) ([broadlink docs]) +- Use DEVICE_CLASS_WINDOW constant in various integrations ([@springstan] - [#39949]) ([brunt docs]) ([deconz docs]) ([fibaro docs]) ([fritzbox docs]) ([maxcube docs]) ([notion docs]) ([somfy_mylink docs]) +- Upgrade codecov to 2.1.9 ([@frenck] - [#39960]) +- Upgrade pytest-cov to 2.10.1 ([@frenck] - [#39964]) +- Upgrade pytest-sugar to 0.9.4 ([@frenck] - [#39966]) +- Upgrade mypy to 0.782 ([@frenck] - [#39967]) +- Use DEVICE_CLASS_DOOR and DEVICE_CLASS_SMOKE in various integrations ([@springstan] - [#39950]) ([concord232 docs]) ([fibaro docs]) ([notion docs]) ([satel_integra docs]) ([spc docs]) ([tahoma docs]) ([wink docs]) +- Upgrade youtube_dl to version 2020.09.06 ([@BKPepe] - [#39969]) ([media_extractor docs]) +- Use opening and occupancy device class in various integrations ([@springstan] - [#39965]) +- Upgrade pytest-timeout to 1.4.2 ([@frenck] - [#39983]) +- Upgrade responses to 0.12.0 ([@frenck] - [#39986]) +- Use connectivity device class constant in various integrations ([@springstan] - [#39972]) +- Use problem, presence and plug device class constants in various integrations ([@springstan] - [#39973]) ([bmw_connected_drive docs]) ([opentherm_gw docs]) ([smappee docs]) ([smartthings docs]) ([smarty docs]) +- Shelly: Power and Energy sensors in roller mode ([@chemelli74] - [#39709]) ([shelly docs]) +- Use DEVICE_CLASS_MOTION in various integrations ([@springstan] - [#39962]) +- Add timeout config option to Synology DSM ([@Quentame] - [#40000]) ([synology_dsm docs]) +- Fix xiaomi_aqara duplicated battery sensors ([@shenxn] - [#39961]) ([xiaomi_aqara docs]) +- Cleanup and reduce duplicate code from recent template changes ([@bdraco] - [#40012]) +- Use moisture and moving device class in various integrations ([@springstan] - [#39963]) +- Revert 'Use STATE_UNKNOWN constant in dlink and ecobee' ([@springstan] - [#40022]) ([dlink docs]) ([ecobee docs]) +- Improve canary tests ([@ctalkington] - [#39956]) ([canary docs]) +- Add Config Flow to AlarmDecoder ([@ajschmidt8] - [#37998]) ([alarmdecoder docs]) (breaking-change) +- Update phrasing and pin validation for homekit_controller ([@bdraco] - [#40006]) ([homekit_controller docs]) +- Add canary alarm_control_panel tests ([@ctalkington] - [#40029]) ([canary docs]) +- Refactor zeroconf setup to be async ([@bdraco] - [#39955]) ([zeroconf docs]) +- Mark Azure DevOps device as a service ([@timmo001] - [#40044]) ([azure_devops docs]) +- Add unique_id to canary alarm_control_panel ([@ctalkington] - [#40041]) ([canary docs]) +- Add device class to canary sensors ([@ctalkington] - [#40050]) ([canary docs]) +- Fix intermittently failing dyson test ([@bdraco] - [#40051]) ([dyson docs]) +- Upgrade coverage to 5.3.0 ([@frenck] - [#40056]) +- Fix vizio async mock fixtures on Python 3.8.0 and .1 ([@scop] - [#39926]) ([vizio docs]) +- Don't try to create /test dir in camera tests ([@scop] - [#39914]) ([camera docs]) +- Make recorder block_till_done reliable ([@bdraco] - [#40043]) ([recorder docs]) +- Make system_log test reliable ([@bdraco] - [#40049]) ([system_log docs]) +- Add more SSDP discovery data and constants ([@scop] - [#39984]) ([ssdp docs]) +- Add temperature and uptime to Synology DSM ([@thomasgermain] - [#39419]) ([synology_dsm docs]) +- Improve reproduce_state for media players ([@rajlaud] - [#38266]) ([media_player docs]) +- Deprecate the synology integration ([@shenxn] - [#39958]) ([synology docs]) (breaking-change) +- Add rpi_power integration ([@shenxn] - [#35527]) ([rpi_power docs]) (new-integration) +- Extract the icon and state for logbook state changed events ([@bdraco] - [#40039]) ([logbook docs]) +- Add unique_id to canary camera ([@ctalkington] - [#40054]) ([canary docs]) +- Reduce listener cancelation code in template tracker ([@bdraco] - [#40040]) +- Fix homekit error when the bridge has been ignored. ([@bdraco] - [#40082]) ([homekit docs]) +- Add support for multiple vera controller hubs ([@vangorra] - [#33613]) ([vera docs]) +- Upgrade pytest to 6.0.2 ([@frenck] - [#39959]) +- Upgrade sentry-sdk to 0.17.5 ([@frenck] - [#40092]) ([sentry docs]) +- Fix hvv_departures config flow patches ([@MartinHjelmare] - [#40095]) ([hvv_departures docs]) +- Upgrade pytest-xdist to 2.1.0 ([@frenck] - [#40057]) +- Add bimonthly period feature for utility_meter component ([@hareeshmu] - [#39931]) ([utility_meter docs]) +- Upgrade youtube_dl to version 2020.09.14 ([@BKPepe] - [#40104]) ([media_extractor docs]) +- Use http status constants more, add HTTP_ACCEPTED and HTTP_BAD_GATEWAY ([@springstan] - [#39993]) +- Add and use volume cubic constants ([@springstan] - [#40106]) ([airvisual docs]) ([comfoconnect docs]) ([isy994 docs]) ([mysensors docs]) ([zha docs]) +- Expose angle and xy attributes in deCONZ event if present ([@klada] - [#39822]) ([deconz docs]) +- Extract Netatmo test data ([@cgtobi] - [#40094]) ([netatmo docs]) +- Clean dyson climate tests ([@MartinHjelmare] - [#40110]) ([dyson docs]) +- Use AREA_SQUARE_METERS constant in all integrations ([@springstan] - [#40107]) ([ambient_station docs]) ([bloomsky docs]) ([isy994 docs]) ([smartthings docs]) ([zamg docs]) +- Add and use currency constants ([@springstan] - [#40113]) ([dsmr_reader docs]) ([growatt_server docs]) ([isy994 docs]) ([pvpc_hourly_pricing docs]) ([tankerkoenig docs]) +- AlarmDecoder config flow fixes ([@ajschmidt8] - [#40037]) ([alarmdecoder docs]) +- Upgrade sentry-sdk to 0.17.6 ([@frenck] - [#40133]) ([sentry docs]) +- Remove unsupported states from security systems in HomeKit ([@nzapponi] - [#40060]) ([homekit docs]) +- Prompt to reauth when the august password is changed or token expires ([@bdraco] - [#40103]) ([august docs]) +- Clean up vera typings ([@vangorra] - [#40143]) ([vera docs]) +- Fix static/class async mocks on Python 3.8.0 and .1 ([@scop] - [#40147]) ([forked_daapd docs]) ([shelly docs]) ([simplisafe docs]) +- Add config support to zoneminder integration ([@vangorra] - [#37060]) ([zoneminder docs]) (breaking-change) +- Fix typo in strings for wolflink ([@SNoof85] - [#40164]) ([wolflink docs]) +- Do not default Pilight lights to max brightness ([@daniel-jong] - [#39549]) ([pilight docs]) (breaking-change) +- Use async_on_remove for vizio listeners ([@raman325] - [#40185]) ([vizio docs]) +- Add cgtobi to sonos code owners ([@cgtobi] - [#40204]) ([sonos docs]) +- Add cgtobi to kodi code owners ([@cgtobi] - [#40202]) ([kodi docs]) +- Fix shelly sensor names ([@Misiu] - [#39854]) ([shelly docs]) +- Catch TypeError in strptime() template helper ([@spacegaier] - [#40226]) +- Use default values in advanced options in devolo home control ([@2Fake] - [#40216]) ([devolo_home_control docs]) +- Add UniFi Uptime sensor ([@timkoers] - [#40058]) ([unifi docs]) +- Update velbus to 2.0.45 ([@Cereal2nd] - [#40256]) ([velbus docs]) +- Add Influxdb precision option ([@twdkeule] - [#38454]) ([influxdb docs]) +- Make tplink SmartStrip communication more robust ([@gjbadros] - [#40281]) ([tplink docs]) +- Add config flow to canary ([@ctalkington] - [#40055]) ([canary docs]) (breaking-change) +- Use pressure constants in code base ([@springstan] - [#40262]) +- Add missing integration quality scale to image integration ([@frenck] - [#40289]) ([image docs]) +- Add missing integration quality scale to tags integration ([@frenck] - [#40291]) ([tag docs]) +- Add port to plugwise ([@CoMPaTech] - [#40017]) ([plugwise docs]) +- Add device info to canary camera and sensors ([@ctalkington] - [#40053]) ([canary docs]) +- Add kodi browse media for channels ([@imduffy15] - [#40277]) ([kodi docs]) +- Use percentage constant in more integrations ([@springstan] - [#40165]) ([growatt_server docs]) ([numato docs]) ([nut docs]) +- Add and use currency cent constant ([@springstan] - [#40261]) ([griddy docs]) ([isy994 docs]) ([nsw_fuel_station docs]) +- Add binary_sensor for cloud connectivity to HomematicIP Cloud ([@SukramJ] - [#39675]) ([homematicip_cloud docs]) +- Update roku media browser classes ([@ctalkington] - [#40285]) ([roku docs]) +- Complete helpers.service type hints ([@scop] - [#40193]) +- Rebuilt Splunk using custom library ([@Bre77] - [#40123]) ([splunk docs]) +- Use content type text plain constant ([@springstan] - [#40313]) ([prometheus docs]) ([rest docs]) ([rest_command docs]) +- Update xknx to 0.14.2 ([@marvin-w] - [#40304]) ([knx docs]) (breaking-change) +- Apply code review for canary config flow ([@ctalkington] - [#40355]) ([canary docs]) +- Add reauth source constant for config entries ([@ctalkington] - [#40352]) +- Add supervisor install add-on helper ([@MartinHjelmare] - [#40138]) +- Upgrade youtube_dl to version 2020.09.20 ([@BKPepe] - [#40395]) ([media_extractor docs]) +- Remove myself as Luci code owner ([@fbradyirl] - [#40398]) ([luci docs]) +- Fix supervisor get addon info ([@MartinHjelmare] - [#40412]) +- Add zodiac integration ([@JulienTant] - [#38935]) ([zodiac docs]) (new-integration) +- Update voluptuous to 0.12.0 ([@spacegaier] - [#40401]) +- Update Solax Library to 0.2.4 ([@squishykid] - [#40330]) ([solax docs]) +- Use centralized KnxEntity for all KNX platforms ([@marvin-w] - [#40381]) ([knx docs]) +- bump pynws to 1.3.0 ([@MatthewFlamm] - [#40386]) ([nws docs]) +- Add supervisor add-on uninstall helper ([@MartinHjelmare] - [#40413]) +- Use more state attribute name constants ([@scop] - [#40428]) +- Improve timeout error handling for Splunk ([@Bre77] - [#40384]) ([splunk docs]) +- Add debug logging to Bond fireplace entity ([@prystupa] - [#40318]) ([bond docs]) +- Add PLAY and PAUSE to webos button service description ([@basnijholt] - [#40353]) ([webostv docs]) +- Firmata analog input, PWM/analog output, deprecate arduino ([@DaAwesomeP] - [#40369]) ([arduino docs]) ([firmata docs]) (new-platform) +- Bump pywemo to 0.5.0 ([@sqldiablo] - [#40439]) ([wemo docs]) +- Update xknx to 0.14.3 ([@marvin-w] - [#40430]) ([knx docs]) +- Serialize websocket event message once ([@bdraco] - [#40453]) ([websocket_api docs]) +- Add support for selecting multiple entity ids from logbook ([@bdraco] - [#40075]) ([logbook docs]) +- Defer template tracking setup until template entity start ([@bdraco] - [#40388]) ([template docs]) +- Add binary_sensor for elevator states to hvv_departures ([@vigonotion] - [#36822]) ([hvv_departures docs]) (new-platform) +- deCONZ - move event handling ([@Kane610] - [#40424]) ([deconz docs]) +- Add and use length millimeters constant ([@springstan] - [#40116]) +- Update xknx to version 0.14.4 ([@marvin-w] - [#40472]) ([knx docs]) +- Improve DOODS folder handling and add process time attribute ([@lamiskin] - [#40344]) ([doods docs]) +- Support learning different command types with remote ([@felipediel] - [#39670]) ([remote docs]) +- Refactor Plex tests using fixtures ([@jjlawren] - [#40260]) ([plex docs]) +- Use content type multipart constant ([@springstan] - [#40314]) ([camera docs]) ([ffmpeg docs]) +- Revert "Support learning different command types with remote" ([@frenck] - [#40486]) ([remote docs]) +- Upgrade sentry-sdk to 0.17.7 ([@frenck] - [#40492]) ([sentry docs]) +- Upgrade isort to 5.5.3 ([@frenck] - [#40493]) +- Add supervisor helper to start add-on ([@MartinHjelmare] - [#40495]) +- Add supervisor add-on stop helper ([@MartinHjelmare] - [#40501]) +- Support all available languages in voicerss integration ([@nagyrobi] - [#40502]) ([voicerss docs]) +- Add all supported languages to OpenWeatherMap ([@Misiu] - [#40448]) ([openweathermap docs]) +- Adjust safe_theme for better readability ([@spacegaier] - [#40223]) ([frontend docs]) +- Use content type json constant ([@springstan] - [#40312]) +- Add and use light lux constant in entire code base ([@springstan] - [#40171]) (breaking-change) +- Correct label in mqtt config flow ([@springstan] - [#40507]) ([mqtt docs]) +- Bump plexapi to 4.1.1 ([@jjlawren] - [#40512]) ([plex docs]) +- Update sonarr to 0.3.0 ([@ctalkington] - [#40515]) ([sonarr docs]) +- Fix Bond error logging format ([@prystupa] - [#40519]) ([bond docs]) +- Upgrade sentry-sdk to 0.17.8 ([@frenck] - [#40531]) ([sentry docs]) +- Add more Huawei LTE sensor metadata ([@scop] - [#39988]) ([huawei_lte docs]) +- Update constant name for onewire ([@epenet] - [#40530]) ([onewire docs]) +- Ensure consitstency of file docstring for 1-wire ([@epenet] - [#40528]) ([onewire docs]) +- Ensure the title is consistent ([@epenet] - [#40528]) ([onewire docs]) +- Improve devolo Home Control code quality ([@Shutgun] - [#40480]) ([devolo_home_control docs]) +- Add Huawei LTE SMS storage full and unread sensors ([@scop] - [#40021]) ([huawei_lte docs]) +- Fix/Refactor Hyperion Integration ([@dermotduffy] - [#39738]) ([hyperion docs]) (breaking-change) +- Bump pyairvisual to 5.0.2 ([@bachya] - [#40554]) ([airvisual docs]) +- Bump simplisafe-python to 9.3.3 ([@bachya] - [#40560]) ([simplisafe docs]) +- Improve handling of sources without a name in Denon ([@asimonen] - [#40514]) ([denon docs]) +- Add @darkfox as Rejseplanen code owner ([@DarkFox] - [#40329]) +- Add modifications for snapshot uploads ([@ludeeus] - [#40503]) +- Upgrade Tibber library to 0.15.3 ([@Danielhiversen] - [#40570]) ([tibber docs]) +- Use HA constants for Rfxtrx units ([@elupus] - [#40562]) ([rfxtrx docs]) +- Upgrade tqdm to 4.49.0 ([@frenck] - [#40573]) +- Remove auto from the fan speed modes for VeSync ([@TheGardenMonkey] - [#40559]) ([vesync docs]) (breaking-change) +- Add Omnilogic integration ([@Oliver84] - [#40474]) ([omnilogic docs]) (new-integration) +- Rewrite light component tests to async pytest tests ([@frenck] - [#40589]) ([light docs]) +- Improve tracking of existing entities in deconz ([@Kane610] - [#40265]) ([deconz docs]) +- Update schema for zha.set_zigbee_cluster_attribute service ([@Adminiuga] - [#40600]) ([zha docs]) +- Add device info to gogogate2 ([@bdraco] - [#40538]) ([gogogate2 docs]) +- Upgrade spotipy to 2.16.0 ([@frenck] - [#40606]) ([spotify docs]) +- Throttle ebusd sensors instead of the whole component ([@danielkucera] - [#40610]) ([ebusd docs]) +- Bump pychromecast to 7.4.1 ([@emontnemery] - [#40587]) ([cast docs]) +- Add installation type to discovery endpoint ([@ludeeus] - [#40585]) ([api docs]) +- Allow non-authenticated calls to snapshots during onboarding ([@ludeeus] - [#40582]) +- Log the remote ip address for incoming websocket connections when debug is on ([@bdraco] - [#40581]) ([websocket_api docs]) +- Add bare hostname as valid known hostname in get_url helper ([@frenck] - [#40510]) +- Use direct service calls in light platform tests ([@frenck] - [#40604]) ([light docs]) +- Use common strings for somfy config flow ([@RobBie1221] - [#40594]) ([somfy docs]) +- Use common strings for monoprice config flow ([@RobBie1221] - [#40592]) ([monoprice docs]) +- Use common strings for Freebox config flow ([@SNoof85] - [#40590]) ([freebox docs]) +- Bump python-broadlink to 0.15.0 ([@felipediel] - [#39228]) ([broadlink docs]) +- Add Modbus cover ([@vzahradnik] - [#33642]) ([modbus docs]) (new-platform) +- Improve performance of counting and iterating states in templates ([@bdraco] - [#40250]) +- Use direct service calls in tests instead of automation common ([@frenck] - [#40623]) +- Reduce the number of template re-renders when we are only counting states ([@bdraco] - [#40272]) +- Ensure all jinja2 errors are trapped and displayed in the developer tools ([@bdraco] - [#40624]) ([websocket_api docs]) +- Add support for homekit windows ([@Julius2342] - [#40635]) ([homekit docs]) +- Handle Shelly channel names (if available) ([@chemelli74] - [#40119]) ([shelly docs]) +- deCONZ fix comments from #40265 ([@Kane610] - [#40640]) ([deconz docs]) +- Fix solaredge service data KeyError ([@Cereal2nd] - [#40653]) ([solaredge docs]) +- Resolve Frontend Services.yaml Minor Oversight ([@Brahmah] - [#40659]) ([frontend docs]) +- Rewrite core event tests to pytest tests ([@frenck] - [#40664]) +- Bump python-velbus to 2.0.46 ([@Cereal2nd] - [#40663]) ([velbus docs]) +- Add authentication support to Nightscout ([@marciogranzotto] - [#40602]) ([nightscout docs]) +- Use common strings for oauth config flows ([@MBlokhuijzen] - [#40608]) ([almond docs]) ([home_connect docs]) ([smappee docs]) ([somfy docs]) ([spotify docs]) ([withings docs]) +- Remove pre-0.102 Huawei LTE setup noop warnings ([@scop] - [#40654]) ([huawei_lte docs]) +- Add Integration for Goal Zero Yeti Power Stations ([@tkdrob] - [#39231]) ([goalzero docs]) (new-integration) +- Bump dwdwfsapi to v1.0.3 ([@stephan192] - [#40644]) ([dwd_weather_warnings docs]) +- Update wolf_smartset to 0.1.6 ([@adamkrol93] - [#40668]) ([wolflink docs]) +- Increase the timeout during config entry setup in Shelly integration ([@bieniu] - [#40684]) ([shelly docs]) +- Upgrade zigpy-znp from 0.1.1 to 0.2.0 ([@puddly] - [#40674]) ([zha docs]) +- Fix issue with HobbyBoard moisture meter ([@epenet] - [#40680]) ([onewire docs]) +- Move onewire constants to separate file ([@epenet] - [#40550]) ([onewire docs]) +- Add onewire humidity sensors connected via DS2438 ([@epenet] - [#39780]) ([onewire docs]) +- Add tests for modbus binary sensor ([@janiversen] - [#40367]) ([modbus docs]) +- Bump up zha dependency ([@Adminiuga] - [#40689]) ([zha docs]) +- Re-enable hdmi_cec component ([@newAM] - [#40671]) ([hdmi_cec docs]) +- Allow non-authenticated calls to supervisor logs during onboarding ([@ludeeus] - [#40617]) +- Improve config flow descriptions in Shelly integration ([@bieniu] - [#40396]) ([shelly docs]) +- Bump snapcast dependency to 2.1.1 ([@mafrosis] - [#40561]) ([snapcast docs]) +- Abort execution of template renders that overwhelm the system ([@bdraco] - [#40647]) ([websocket_api docs]) +- Add entity glob matching support to history ([@bdraco] - [#40387]) ([history docs]) +- Remove degree from Kelvin unit ([@RichieFrame] - [#40574]) ([isy994 docs]) ([lcn docs]) (breaking-change) +- Fix Android TV 'async_get_media_image' ([@JeffLIrion] - [#40672]) ([androidtv docs]) +- Add rpi_power during onboarding on RPi ([@MartinHjelmare] - [#40076]) ([onboarding docs]) ([rpi_power docs]) +- Add support to reauthorize expired Plex tokens ([@jjlawren] - [#40469]) ([plex docs]) +- Improve performance of accessing template state ([@bdraco] - [#40323]) +- Improve devolo Home Control code quality ([@Shutgun] - [#40708]) ([devolo_home_control docs]) +- Bump pypck to v0.7.2 ([@alengwenus] - [#40716]) ([lcn docs]) +- Use NamedTuple for Huawei LTE sensor metadata ([@scop] - [#40655]) ([huawei_lte docs]) +- Fix support for Aqara WXKG06LM ([@fabricepipart] - [#40694]) ([deconz docs]) ([xiaomi_aqara docs]) +- Fix name of the Vallox integration in the manifest ([@frenck] - [#40727]) ([vallox docs]) +- Add MQTT tag scanner ([@emontnemery] - [#40709]) ([mqtt docs]) +- Update islamic_prayer_times with common strings ([@Brahmah] - [#40712]) ([islamic_prayer_times docs]) +- Bump up ZHA dependency ([@Adminiuga] - [#40734]) ([zha docs]) +- Refactor permit services to allow joining using install codes ([@Adminiuga] - [#40652]) ([zha docs]) (breaking-change) +- Add switch to control downloads for nzbget ([@ctalkington] - [#40673]) ([nzbget docs]) (new-platform) +- Add ability to reauth sonarr ([@ctalkington] - [#40306]) ([sonarr docs]) +- Add deconz option to disable automatic addition of new devices ([@Kane610] - [#40545]) ([deconz docs]) +- Update pyatag to 0.3.4.4 ([@MatsNl] - [#40720]) ([atag docs]) +- Add template cover opening and closing states ([@TheNr1Guest] - [#40677]) ([template docs]) +- Upgrade paho-mqtt to 1.5.1 ([@frenck] - [#40703]) ([mqtt docs]) ([shiftr docs]) +- Add Neighbors & Endpoint Names to zha/devices reply ([@Samantha-uk] - [#40748]) ([zha docs]) +- Bump ZHA quirks lib to 0.0.45 ([@dmulcahey] - [#40769]) ([zha docs]) +- Normalise headers in onewire integration ([@epenet] - [#40774]) ([onewire docs]) +- Update xknx to 0.15.0 ([@marvin-w] - [#40649]) ([knx docs]) +- Use direct service calls in flux tests instead of switch common ([@frenck] - [#40704]) ([flux docs]) +- Update devolo-home-control-api to 0.15.0 ([@Shutgun] - [#40764]) ([devolo_home_control docs]) +- Code cleanups for async_track_template_result ([@bdraco] - [#40737]) +- Add unique_id to the light switch ([@tetienne] - [#40603]) ([switch docs]) +- Fix logbook with empty filter and remove unused code ([@bdraco] - [#40565]) ([logbook docs]) ([recorder docs]) +- Setup recorder model relationships to avoid calling flush ([@bdraco] - [#40467]) ([recorder docs]) +- Remove TekSavvy Component, no longer available ([@mikeodr] - [#40762]) (breaking-change) +- Improve command_line switch tests ([@frenck] - [#40749]) ([command_line docs]) +- Use common strings for velbus config flow ([@Cereal2nd] - [#40660]) ([velbus docs]) +- Upgrade sentry-sdk to 0.18.0 ([@frenck] - [#40784]) ([sentry docs]) +- Refactor group to extend domains that can be grouped ([@bdraco] - [#40607]) ([group docs]) +- Disable hourly sensor by default in NWS ([@MatthewFlamm] - [#40566]) ([nws docs]) +- Fix and clean tox.ini ([@MartinHjelmare] - [#40789]) +- Fix DWD namings ([@creichel] - [#40791]) ([dwd_weather_warnings docs]) +- Tibber, combine two fetches into one fetch ([@Danielhiversen] - [#40787]) ([tibber docs]) +- Create MQTTMatcher once per subscription instead of each message ([@bdraco] - [#40345]) ([mqtt docs]) +- Use the Home Assistant Cast app to play media on Chromecast ([@bramkragten] - [#40782]) ([cast docs]) +- Improve deCONZ state updates ([@Kane610] - [#40601]) ([deconz docs]) +- Switch group to use None for the state unknown case ([@bdraco] - [#40792]) ([group docs]) +- Log timestamp overflow in stream ([@uvjustin] - [#39844]) ([stream docs]) +- Return target duration of 1 when no segments ([@uvjustin] - [#40518]) ([stream docs]) +- Add Surveillance Station home mode switch for Synology DSM ([@Quentame] - [#40490]) ([synology_dsm docs]) (new-platform) +- Remove message and domain from logbook state_changed events ([@bdraco] - [#40070]) ([logbook docs]) (breaking-change) +- Update frontend to 20200930.0 ([@bramkragten] - [#40794]) ([frontend docs]) +- Include config flow modules in coverage ([@Danielhiversen] - [#40798]) +- Add deCONZ service to clean up orphaned device and entity entries ([@Kane610] - [#40629]) ([deconz docs]) +- Discover additional ozw thermostats lacking mode support ([@firstof9] - [#40799]) ([ozw docs]) +- Seperate state change tracking from async_track_template_result into async_track_state_change_filtered ([@bdraco] - [#40803]) (beta fix) +- Implement template rate_limit directive ([@bdraco] - [#40667]) (breaking-change) (beta fix) +- Accept new Plex websocket callback payloads ([@jjlawren] - [#40773]) ([plex docs]) (beta fix) +- Fix Netatmo climate error when no boiler status is set ([@cgtobi] - [#40815]) ([netatmo docs]) (beta fix) +- Bump simplisafe-python to 9.4.1 ([@bachya] - [#40819]) ([simplisafe docs]) (beta fix) +- Bump up zha dependencies ([@Adminiuga] - [#40914]) ([zha docs]) (beta fix) +- Revert using own cast app for media ([@bramkragten] - [#40937]) ([cast docs]) (beta fix) +- Update frontend to 20201001.0 ([@bramkragten] - [#40974]) ([frontend docs]) (beta fix) +- Prevent sqlalchemy from refetching the old_state_id as it will never change ([@bdraco] - [#40982]) ([recorder docs]) (beta fix) +- Plex websocket callback async cleanup ([@jjlawren] - [#40992]) ([plex docs]) (beta fix) +- Prevent template loop detection from triggering when all templates are self referencing ([@bdraco] - [#41013]) ([template docs]) (beta fix) +- Better parsing of the ZHA device profile id ([@Adminiuga] - [#41024]) ([zha docs]) (beta fix) +- Change Swap free mandatory arg ([@Mariusthvdb] - [#41025]) ([systemmonitor docs]) (beta fix) +- Ensure lights added after group is created have the correct state ([@bdraco] - [#41034]) ([group docs]) (beta fix) +- Bump aioshelly to 0.3.4 ([@balloob] - [#41065]) ([shelly docs]) (beta fix) +- Add full command details to exception Debug log ([@Samantha-uk] - [#41070]) ([zha docs]) (beta fix) +- Fix SmartHab import flow ([@outadoc] - [#41093]) ([smarthab docs]) (beta fix) +- Fix referenced entity extraction when service call entity contains a template ([@frenck] - [#41107]) (beta fix) +- Bump up ZHA dependency ([@Adminiuga] - [#41109]) ([zha docs]) (beta fix) +- Treat optional input as optional in ZoneMinder config flow ([@rohankapoorcom] - [#41156]) ([zoneminder docs]) (beta fix) +- Handle Shelly channel names (if available) for emeters devices ([@chemelli74] - [#40820]) ([shelly docs]) (beta fix) +- Simplify template tracking and make it easier to follow ([@bdraco] - [#41030]) (beta fix) +- Fix TTS handling of non-ID3 metadata tags ([@blueshiftlabs] - [#41191]) ([tts docs]) (beta fix) +- Remove deprecation invalidation version from cast integration ([@frenck] - [#41197]) ([cast docs]) (beta fix) +- Remove manual rate_limit control directive from templates ([@bdraco] - [#41225]) (beta fix) +- Bump apprise version to avoid sync in async issues ([@raman325] - [#41253]) ([apprise docs]) (beta fix) +- Allow any value when triggering on state attribute ([@balloob] - [#41261]) ([homeassistant docs]) (breaking-change) (beta fix) +- Add extended validation for script repeat/choose ([@balloob] - [#41265]) (beta fix) +- Updated frontend to 20201001.1 ([@bramkragten] - [#41273]) ([frontend docs]) (beta fix) +- Update pysmartthings ([@andrewsayre] - [#41294]) ([smartthings docs]) (beta fix) +- Exclude media_dirs from YAML config check ([@bramkragten] - [#41299]) (beta fix) +- Prevent collecting states already referenced by domain or all ([@bdraco] - [#41308]) (beta fix) +- Don't set upnp config_entry.unique_id from setup entry ([@StevenLooman] - [#40988]) ([upnp docs]) (beta fix) +- Fix TTS ID3 Tag capability check ([@frenck] - [#41343]) ([tts docs]) (beta fix) +- Resolve memory leak in recorder ([@bdraco] - [#41349]) ([recorder docs]) (beta fix) +- Set longer timeout during synology_dsm config flow ([@Quentame] - [#41364]) ([synology_dsm docs]) (beta fix) +- Add additionalAttributes to Alexa discovery payload ([@balloob] - [#41370]) ([alexa docs]) (beta fix) +- Bump up zha dependency to 0.26.0 ([@Adminiuga] - [#41371]) ([zha docs]) (beta fix) +- Fix elkm1 changed by ([@gwww] - [#41378]) ([elkm1 docs]) (beta fix) +- Reduce Somfy polling ([@balloob] - [#41389]) ([somfy docs]) (beta fix) +- Revert zoneminder config flow ([@MartinHjelmare] - [#41395]) ([zoneminder docs]) (beta fix) +- Warn when using Python 3.7 ([@balloob] - [#41400]) (beta fix) + +
      + +[#33613]: https://github.com/home-assistant/core/pull/33613 +[#33642]: https://github.com/home-assistant/core/pull/33642 +[#35527]: https://github.com/home-assistant/core/pull/35527 +[#36822]: https://github.com/home-assistant/core/pull/36822 +[#37060]: https://github.com/home-assistant/core/pull/37060 +[#37998]: https://github.com/home-assistant/core/pull/37998 +[#38266]: https://github.com/home-assistant/core/pull/38266 +[#38341]: https://github.com/home-assistant/core/pull/38341 +[#38454]: https://github.com/home-assistant/core/pull/38454 +[#38935]: https://github.com/home-assistant/core/pull/38935 +[#39090]: https://github.com/home-assistant/core/pull/39090 +[#39228]: https://github.com/home-assistant/core/pull/39228 +[#39231]: https://github.com/home-assistant/core/pull/39231 +[#39419]: https://github.com/home-assistant/core/pull/39419 +[#39549]: https://github.com/home-assistant/core/pull/39549 +[#39608]: https://github.com/home-assistant/core/pull/39608 +[#39670]: https://github.com/home-assistant/core/pull/39670 +[#39675]: https://github.com/home-assistant/core/pull/39675 +[#39687]: https://github.com/home-assistant/core/pull/39687 +[#39709]: https://github.com/home-assistant/core/pull/39709 +[#39714]: https://github.com/home-assistant/core/pull/39714 +[#39738]: https://github.com/home-assistant/core/pull/39738 +[#39757]: https://github.com/home-assistant/core/pull/39757 +[#39768]: https://github.com/home-assistant/core/pull/39768 +[#39780]: https://github.com/home-assistant/core/pull/39780 +[#39819]: https://github.com/home-assistant/core/pull/39819 +[#39822]: https://github.com/home-assistant/core/pull/39822 +[#39838]: https://github.com/home-assistant/core/pull/39838 +[#39844]: https://github.com/home-assistant/core/pull/39844 +[#39853]: https://github.com/home-assistant/core/pull/39853 +[#39854]: https://github.com/home-assistant/core/pull/39854 +[#39859]: https://github.com/home-assistant/core/pull/39859 +[#39868]: https://github.com/home-assistant/core/pull/39868 +[#39870]: https://github.com/home-assistant/core/pull/39870 +[#39871]: https://github.com/home-assistant/core/pull/39871 +[#39879]: https://github.com/home-assistant/core/pull/39879 +[#39882]: https://github.com/home-assistant/core/pull/39882 +[#39889]: https://github.com/home-assistant/core/pull/39889 +[#39898]: https://github.com/home-assistant/core/pull/39898 +[#39907]: https://github.com/home-assistant/core/pull/39907 +[#39908]: https://github.com/home-assistant/core/pull/39908 +[#39912]: https://github.com/home-assistant/core/pull/39912 +[#39914]: https://github.com/home-assistant/core/pull/39914 +[#39926]: https://github.com/home-assistant/core/pull/39926 +[#39929]: https://github.com/home-assistant/core/pull/39929 +[#39931]: https://github.com/home-assistant/core/pull/39931 +[#39940]: https://github.com/home-assistant/core/pull/39940 +[#39948]: https://github.com/home-assistant/core/pull/39948 +[#39949]: https://github.com/home-assistant/core/pull/39949 +[#39950]: https://github.com/home-assistant/core/pull/39950 +[#39952]: https://github.com/home-assistant/core/pull/39952 +[#39955]: https://github.com/home-assistant/core/pull/39955 +[#39956]: https://github.com/home-assistant/core/pull/39956 +[#39958]: https://github.com/home-assistant/core/pull/39958 +[#39959]: https://github.com/home-assistant/core/pull/39959 +[#39960]: https://github.com/home-assistant/core/pull/39960 +[#39961]: https://github.com/home-assistant/core/pull/39961 +[#39962]: https://github.com/home-assistant/core/pull/39962 +[#39963]: https://github.com/home-assistant/core/pull/39963 +[#39964]: https://github.com/home-assistant/core/pull/39964 +[#39965]: https://github.com/home-assistant/core/pull/39965 +[#39966]: https://github.com/home-assistant/core/pull/39966 +[#39967]: https://github.com/home-assistant/core/pull/39967 +[#39969]: https://github.com/home-assistant/core/pull/39969 +[#39972]: https://github.com/home-assistant/core/pull/39972 +[#39973]: https://github.com/home-assistant/core/pull/39973 +[#39983]: https://github.com/home-assistant/core/pull/39983 +[#39984]: https://github.com/home-assistant/core/pull/39984 +[#39986]: https://github.com/home-assistant/core/pull/39986 +[#39988]: https://github.com/home-assistant/core/pull/39988 +[#39993]: https://github.com/home-assistant/core/pull/39993 +[#40000]: https://github.com/home-assistant/core/pull/40000 +[#40006]: https://github.com/home-assistant/core/pull/40006 +[#40012]: https://github.com/home-assistant/core/pull/40012 +[#40017]: https://github.com/home-assistant/core/pull/40017 +[#40021]: https://github.com/home-assistant/core/pull/40021 +[#40022]: https://github.com/home-assistant/core/pull/40022 +[#40029]: https://github.com/home-assistant/core/pull/40029 +[#40037]: https://github.com/home-assistant/core/pull/40037 +[#40039]: https://github.com/home-assistant/core/pull/40039 +[#40040]: https://github.com/home-assistant/core/pull/40040 +[#40041]: https://github.com/home-assistant/core/pull/40041 +[#40043]: https://github.com/home-assistant/core/pull/40043 +[#40044]: https://github.com/home-assistant/core/pull/40044 +[#40049]: https://github.com/home-assistant/core/pull/40049 +[#40050]: https://github.com/home-assistant/core/pull/40050 +[#40051]: https://github.com/home-assistant/core/pull/40051 +[#40053]: https://github.com/home-assistant/core/pull/40053 +[#40054]: https://github.com/home-assistant/core/pull/40054 +[#40055]: https://github.com/home-assistant/core/pull/40055 +[#40056]: https://github.com/home-assistant/core/pull/40056 +[#40057]: https://github.com/home-assistant/core/pull/40057 +[#40058]: https://github.com/home-assistant/core/pull/40058 +[#40060]: https://github.com/home-assistant/core/pull/40060 +[#40070]: https://github.com/home-assistant/core/pull/40070 +[#40075]: https://github.com/home-assistant/core/pull/40075 +[#40076]: https://github.com/home-assistant/core/pull/40076 +[#40082]: https://github.com/home-assistant/core/pull/40082 +[#40092]: https://github.com/home-assistant/core/pull/40092 +[#40094]: https://github.com/home-assistant/core/pull/40094 +[#40095]: https://github.com/home-assistant/core/pull/40095 +[#40103]: https://github.com/home-assistant/core/pull/40103 +[#40104]: https://github.com/home-assistant/core/pull/40104 +[#40106]: https://github.com/home-assistant/core/pull/40106 +[#40107]: https://github.com/home-assistant/core/pull/40107 +[#40110]: https://github.com/home-assistant/core/pull/40110 +[#40113]: https://github.com/home-assistant/core/pull/40113 +[#40116]: https://github.com/home-assistant/core/pull/40116 +[#40119]: https://github.com/home-assistant/core/pull/40119 +[#40123]: https://github.com/home-assistant/core/pull/40123 +[#40133]: https://github.com/home-assistant/core/pull/40133 +[#40138]: https://github.com/home-assistant/core/pull/40138 +[#40143]: https://github.com/home-assistant/core/pull/40143 +[#40147]: https://github.com/home-assistant/core/pull/40147 +[#40164]: https://github.com/home-assistant/core/pull/40164 +[#40165]: https://github.com/home-assistant/core/pull/40165 +[#40171]: https://github.com/home-assistant/core/pull/40171 +[#40185]: https://github.com/home-assistant/core/pull/40185 +[#40193]: https://github.com/home-assistant/core/pull/40193 +[#40202]: https://github.com/home-assistant/core/pull/40202 +[#40204]: https://github.com/home-assistant/core/pull/40204 +[#40216]: https://github.com/home-assistant/core/pull/40216 +[#40223]: https://github.com/home-assistant/core/pull/40223 +[#40226]: https://github.com/home-assistant/core/pull/40226 +[#40250]: https://github.com/home-assistant/core/pull/40250 +[#40256]: https://github.com/home-assistant/core/pull/40256 +[#40260]: https://github.com/home-assistant/core/pull/40260 +[#40261]: https://github.com/home-assistant/core/pull/40261 +[#40262]: https://github.com/home-assistant/core/pull/40262 +[#40265]: https://github.com/home-assistant/core/pull/40265 +[#40272]: https://github.com/home-assistant/core/pull/40272 +[#40277]: https://github.com/home-assistant/core/pull/40277 +[#40281]: https://github.com/home-assistant/core/pull/40281 +[#40285]: https://github.com/home-assistant/core/pull/40285 +[#40289]: https://github.com/home-assistant/core/pull/40289 +[#40291]: https://github.com/home-assistant/core/pull/40291 +[#40304]: https://github.com/home-assistant/core/pull/40304 +[#40306]: https://github.com/home-assistant/core/pull/40306 +[#40312]: https://github.com/home-assistant/core/pull/40312 +[#40313]: https://github.com/home-assistant/core/pull/40313 +[#40314]: https://github.com/home-assistant/core/pull/40314 +[#40318]: https://github.com/home-assistant/core/pull/40318 +[#40323]: https://github.com/home-assistant/core/pull/40323 +[#40329]: https://github.com/home-assistant/core/pull/40329 +[#40330]: https://github.com/home-assistant/core/pull/40330 +[#40344]: https://github.com/home-assistant/core/pull/40344 +[#40345]: https://github.com/home-assistant/core/pull/40345 +[#40352]: https://github.com/home-assistant/core/pull/40352 +[#40353]: https://github.com/home-assistant/core/pull/40353 +[#40355]: https://github.com/home-assistant/core/pull/40355 +[#40367]: https://github.com/home-assistant/core/pull/40367 +[#40369]: https://github.com/home-assistant/core/pull/40369 +[#40381]: https://github.com/home-assistant/core/pull/40381 +[#40384]: https://github.com/home-assistant/core/pull/40384 +[#40386]: https://github.com/home-assistant/core/pull/40386 +[#40387]: https://github.com/home-assistant/core/pull/40387 +[#40388]: https://github.com/home-assistant/core/pull/40388 +[#40395]: https://github.com/home-assistant/core/pull/40395 +[#40396]: https://github.com/home-assistant/core/pull/40396 +[#40398]: https://github.com/home-assistant/core/pull/40398 +[#40401]: https://github.com/home-assistant/core/pull/40401 +[#40412]: https://github.com/home-assistant/core/pull/40412 +[#40413]: https://github.com/home-assistant/core/pull/40413 +[#40424]: https://github.com/home-assistant/core/pull/40424 +[#40428]: https://github.com/home-assistant/core/pull/40428 +[#40430]: https://github.com/home-assistant/core/pull/40430 +[#40439]: https://github.com/home-assistant/core/pull/40439 +[#40448]: https://github.com/home-assistant/core/pull/40448 +[#40453]: https://github.com/home-assistant/core/pull/40453 +[#40467]: https://github.com/home-assistant/core/pull/40467 +[#40469]: https://github.com/home-assistant/core/pull/40469 +[#40472]: https://github.com/home-assistant/core/pull/40472 +[#40474]: https://github.com/home-assistant/core/pull/40474 +[#40480]: https://github.com/home-assistant/core/pull/40480 +[#40486]: https://github.com/home-assistant/core/pull/40486 +[#40490]: https://github.com/home-assistant/core/pull/40490 +[#40492]: https://github.com/home-assistant/core/pull/40492 +[#40493]: https://github.com/home-assistant/core/pull/40493 +[#40495]: https://github.com/home-assistant/core/pull/40495 +[#40501]: https://github.com/home-assistant/core/pull/40501 +[#40502]: https://github.com/home-assistant/core/pull/40502 +[#40503]: https://github.com/home-assistant/core/pull/40503 +[#40507]: https://github.com/home-assistant/core/pull/40507 +[#40510]: https://github.com/home-assistant/core/pull/40510 +[#40512]: https://github.com/home-assistant/core/pull/40512 +[#40514]: https://github.com/home-assistant/core/pull/40514 +[#40515]: https://github.com/home-assistant/core/pull/40515 +[#40518]: https://github.com/home-assistant/core/pull/40518 +[#40519]: https://github.com/home-assistant/core/pull/40519 +[#40528]: https://github.com/home-assistant/core/pull/40528 +[#40530]: https://github.com/home-assistant/core/pull/40530 +[#40531]: https://github.com/home-assistant/core/pull/40531 +[#40538]: https://github.com/home-assistant/core/pull/40538 +[#40545]: https://github.com/home-assistant/core/pull/40545 +[#40550]: https://github.com/home-assistant/core/pull/40550 +[#40554]: https://github.com/home-assistant/core/pull/40554 +[#40559]: https://github.com/home-assistant/core/pull/40559 +[#40560]: https://github.com/home-assistant/core/pull/40560 +[#40561]: https://github.com/home-assistant/core/pull/40561 +[#40562]: https://github.com/home-assistant/core/pull/40562 +[#40565]: https://github.com/home-assistant/core/pull/40565 +[#40566]: https://github.com/home-assistant/core/pull/40566 +[#40570]: https://github.com/home-assistant/core/pull/40570 +[#40573]: https://github.com/home-assistant/core/pull/40573 +[#40574]: https://github.com/home-assistant/core/pull/40574 +[#40581]: https://github.com/home-assistant/core/pull/40581 +[#40582]: https://github.com/home-assistant/core/pull/40582 +[#40585]: https://github.com/home-assistant/core/pull/40585 +[#40587]: https://github.com/home-assistant/core/pull/40587 +[#40589]: https://github.com/home-assistant/core/pull/40589 +[#40590]: https://github.com/home-assistant/core/pull/40590 +[#40592]: https://github.com/home-assistant/core/pull/40592 +[#40594]: https://github.com/home-assistant/core/pull/40594 +[#40600]: https://github.com/home-assistant/core/pull/40600 +[#40601]: https://github.com/home-assistant/core/pull/40601 +[#40602]: https://github.com/home-assistant/core/pull/40602 +[#40603]: https://github.com/home-assistant/core/pull/40603 +[#40604]: https://github.com/home-assistant/core/pull/40604 +[#40606]: https://github.com/home-assistant/core/pull/40606 +[#40607]: https://github.com/home-assistant/core/pull/40607 +[#40608]: https://github.com/home-assistant/core/pull/40608 +[#40610]: https://github.com/home-assistant/core/pull/40610 +[#40617]: https://github.com/home-assistant/core/pull/40617 +[#40623]: https://github.com/home-assistant/core/pull/40623 +[#40624]: https://github.com/home-assistant/core/pull/40624 +[#40629]: https://github.com/home-assistant/core/pull/40629 +[#40635]: https://github.com/home-assistant/core/pull/40635 +[#40640]: https://github.com/home-assistant/core/pull/40640 +[#40644]: https://github.com/home-assistant/core/pull/40644 +[#40647]: https://github.com/home-assistant/core/pull/40647 +[#40649]: https://github.com/home-assistant/core/pull/40649 +[#40652]: https://github.com/home-assistant/core/pull/40652 +[#40653]: https://github.com/home-assistant/core/pull/40653 +[#40654]: https://github.com/home-assistant/core/pull/40654 +[#40655]: https://github.com/home-assistant/core/pull/40655 +[#40659]: https://github.com/home-assistant/core/pull/40659 +[#40660]: https://github.com/home-assistant/core/pull/40660 +[#40663]: https://github.com/home-assistant/core/pull/40663 +[#40664]: https://github.com/home-assistant/core/pull/40664 +[#40667]: https://github.com/home-assistant/core/pull/40667 +[#40668]: https://github.com/home-assistant/core/pull/40668 +[#40671]: https://github.com/home-assistant/core/pull/40671 +[#40672]: https://github.com/home-assistant/core/pull/40672 +[#40673]: https://github.com/home-assistant/core/pull/40673 +[#40674]: https://github.com/home-assistant/core/pull/40674 +[#40677]: https://github.com/home-assistant/core/pull/40677 +[#40680]: https://github.com/home-assistant/core/pull/40680 +[#40684]: https://github.com/home-assistant/core/pull/40684 +[#40689]: https://github.com/home-assistant/core/pull/40689 +[#40694]: https://github.com/home-assistant/core/pull/40694 +[#40703]: https://github.com/home-assistant/core/pull/40703 +[#40704]: https://github.com/home-assistant/core/pull/40704 +[#40708]: https://github.com/home-assistant/core/pull/40708 +[#40709]: https://github.com/home-assistant/core/pull/40709 +[#40712]: https://github.com/home-assistant/core/pull/40712 +[#40716]: https://github.com/home-assistant/core/pull/40716 +[#40720]: https://github.com/home-assistant/core/pull/40720 +[#40727]: https://github.com/home-assistant/core/pull/40727 +[#40734]: https://github.com/home-assistant/core/pull/40734 +[#40737]: https://github.com/home-assistant/core/pull/40737 +[#40748]: https://github.com/home-assistant/core/pull/40748 +[#40749]: https://github.com/home-assistant/core/pull/40749 +[#40762]: https://github.com/home-assistant/core/pull/40762 +[#40764]: https://github.com/home-assistant/core/pull/40764 +[#40769]: https://github.com/home-assistant/core/pull/40769 +[#40773]: https://github.com/home-assistant/core/pull/40773 +[#40774]: https://github.com/home-assistant/core/pull/40774 +[#40782]: https://github.com/home-assistant/core/pull/40782 +[#40784]: https://github.com/home-assistant/core/pull/40784 +[#40787]: https://github.com/home-assistant/core/pull/40787 +[#40789]: https://github.com/home-assistant/core/pull/40789 +[#40791]: https://github.com/home-assistant/core/pull/40791 +[#40792]: https://github.com/home-assistant/core/pull/40792 +[#40794]: https://github.com/home-assistant/core/pull/40794 +[#40798]: https://github.com/home-assistant/core/pull/40798 +[#40799]: https://github.com/home-assistant/core/pull/40799 +[#40803]: https://github.com/home-assistant/core/pull/40803 +[#40815]: https://github.com/home-assistant/core/pull/40815 +[#40819]: https://github.com/home-assistant/core/pull/40819 +[#40820]: https://github.com/home-assistant/core/pull/40820 +[#40914]: https://github.com/home-assistant/core/pull/40914 +[#40937]: https://github.com/home-assistant/core/pull/40937 +[#40974]: https://github.com/home-assistant/core/pull/40974 +[#40982]: https://github.com/home-assistant/core/pull/40982 +[#40988]: https://github.com/home-assistant/core/pull/40988 +[#40992]: https://github.com/home-assistant/core/pull/40992 +[#41013]: https://github.com/home-assistant/core/pull/41013 +[#41024]: https://github.com/home-assistant/core/pull/41024 +[#41025]: https://github.com/home-assistant/core/pull/41025 +[#41030]: https://github.com/home-assistant/core/pull/41030 +[#41034]: https://github.com/home-assistant/core/pull/41034 +[#41065]: https://github.com/home-assistant/core/pull/41065 +[#41070]: https://github.com/home-assistant/core/pull/41070 +[#41093]: https://github.com/home-assistant/core/pull/41093 +[#41107]: https://github.com/home-assistant/core/pull/41107 +[#41109]: https://github.com/home-assistant/core/pull/41109 +[#41156]: https://github.com/home-assistant/core/pull/41156 +[#41191]: https://github.com/home-assistant/core/pull/41191 +[#41197]: https://github.com/home-assistant/core/pull/41197 +[#41225]: https://github.com/home-assistant/core/pull/41225 +[#41253]: https://github.com/home-assistant/core/pull/41253 +[#41261]: https://github.com/home-assistant/core/pull/41261 +[#41265]: https://github.com/home-assistant/core/pull/41265 +[#41273]: https://github.com/home-assistant/core/pull/41273 +[#41294]: https://github.com/home-assistant/core/pull/41294 +[#41299]: https://github.com/home-assistant/core/pull/41299 +[#41308]: https://github.com/home-assistant/core/pull/41308 +[#41343]: https://github.com/home-assistant/core/pull/41343 +[#41349]: https://github.com/home-assistant/core/pull/41349 +[#41364]: https://github.com/home-assistant/core/pull/41364 +[#41370]: https://github.com/home-assistant/core/pull/41370 +[#41371]: https://github.com/home-assistant/core/pull/41371 +[#41378]: https://github.com/home-assistant/core/pull/41378 +[#41389]: https://github.com/home-assistant/core/pull/41389 +[#41395]: https://github.com/home-assistant/core/pull/41395 +[#41400]: https://github.com/home-assistant/core/pull/41400 +[@2Fake]: https://github.com/2Fake +[@Adminiuga]: https://github.com/Adminiuga +[@BKPepe]: https://github.com/BKPepe +[@Brahmah]: https://github.com/Brahmah +[@Bre77]: https://github.com/Bre77 +[@Cereal2nd]: https://github.com/Cereal2nd +[@CoMPaTech]: https://github.com/CoMPaTech +[@DAMEK86]: https://github.com/DAMEK86 +[@DaAwesomeP]: https://github.com/DaAwesomeP +[@Danielhiversen]: https://github.com/Danielhiversen +[@DarkFox]: https://github.com/DarkFox +[@Jc2k]: https://github.com/Jc2k +[@JeffLIrion]: https://github.com/JeffLIrion +[@JulienTant]: https://github.com/JulienTant +[@Julius2342]: https://github.com/Julius2342 +[@Kane610]: https://github.com/Kane610 +[@MBlokhuijzen]: https://github.com/MBlokhuijzen +[@Mariusthvdb]: https://github.com/Mariusthvdb +[@MartinHjelmare]: https://github.com/MartinHjelmare +[@MatsNl]: https://github.com/MatsNl +[@MatthewFlamm]: https://github.com/MatthewFlamm +[@Misiu]: https://github.com/Misiu +[@Oliver84]: https://github.com/Oliver84 +[@Quentame]: https://github.com/Quentame +[@RichieFrame]: https://github.com/RichieFrame +[@RobBie1221]: https://github.com/RobBie1221 +[@RogerSelwyn]: https://github.com/RogerSelwyn +[@SNoof85]: https://github.com/SNoof85 +[@Samantha-uk]: https://github.com/Samantha-uk +[@Shutgun]: https://github.com/Shutgun +[@StevenLooman]: https://github.com/StevenLooman +[@SukramJ]: https://github.com/SukramJ +[@TheGardenMonkey]: https://github.com/TheGardenMonkey +[@TheNr1Guest]: https://github.com/TheNr1Guest +[@adamkrol93]: https://github.com/adamkrol93 +[@ajschmidt8]: https://github.com/ajschmidt8 +[@alengwenus]: https://github.com/alengwenus +[@andrewsayre]: https://github.com/andrewsayre +[@asimonen]: https://github.com/asimonen +[@bachya]: https://github.com/bachya +[@balloob]: https://github.com/balloob +[@basnijholt]: https://github.com/basnijholt +[@bdraco]: https://github.com/bdraco +[@bieniu]: https://github.com/bieniu +[@blueshiftlabs]: https://github.com/blueshiftlabs +[@bramkragten]: https://github.com/bramkragten +[@cgtobi]: https://github.com/cgtobi +[@chemelli74]: https://github.com/chemelli74 +[@creichel]: https://github.com/creichel +[@ctalkington]: https://github.com/ctalkington +[@daniel-jong]: https://github.com/daniel-jong +[@danielkucera]: https://github.com/danielkucera +[@dermotduffy]: https://github.com/dermotduffy +[@dmulcahey]: https://github.com/dmulcahey +[@elupus]: https://github.com/elupus +[@emontnemery]: https://github.com/emontnemery +[@epenet]: https://github.com/epenet +[@fabricepipart]: https://github.com/fabricepipart +[@fbradyirl]: https://github.com/fbradyirl +[@felipediel]: https://github.com/felipediel +[@firstof9]: https://github.com/firstof9 +[@frenck]: https://github.com/frenck +[@gjbadros]: https://github.com/gjbadros +[@gwww]: https://github.com/gwww +[@hareeshmu]: https://github.com/hareeshmu +[@imduffy15]: https://github.com/imduffy15 +[@janiversen]: https://github.com/janiversen +[@jjlawren]: https://github.com/jjlawren +[@jschlyter]: https://github.com/jschlyter +[@klada]: https://github.com/klada +[@lamiskin]: https://github.com/lamiskin +[@ludeeus]: https://github.com/ludeeus +[@mafrosis]: https://github.com/mafrosis +[@marciogranzotto]: https://github.com/marciogranzotto +[@marvin-w]: https://github.com/marvin-w +[@mikeodr]: https://github.com/mikeodr +[@nagyrobi]: https://github.com/nagyrobi +[@newAM]: https://github.com/newAM +[@nzapponi]: https://github.com/nzapponi +[@outadoc]: https://github.com/outadoc +[@prystupa]: https://github.com/prystupa +[@puddly]: https://github.com/puddly +[@rajlaud]: https://github.com/rajlaud +[@raman325]: https://github.com/raman325 +[@rohankapoorcom]: https://github.com/rohankapoorcom +[@scop]: https://github.com/scop +[@shenxn]: https://github.com/shenxn +[@soldag]: https://github.com/soldag +[@spacegaier]: https://github.com/spacegaier +[@springstan]: https://github.com/springstan +[@sqldiablo]: https://github.com/sqldiablo +[@squishykid]: https://github.com/squishykid +[@stephan192]: https://github.com/stephan192 +[@tetienne]: https://github.com/tetienne +[@thomasgermain]: https://github.com/thomasgermain +[@timkoers]: https://github.com/timkoers +[@timmo001]: https://github.com/timmo001 +[@tkdrob]: https://github.com/tkdrob +[@twdkeule]: https://github.com/twdkeule +[@uvjustin]: https://github.com/uvjustin +[@vangorra]: https://github.com/vangorra +[@vigonotion]: https://github.com/vigonotion +[@vzahradnik]: https://github.com/vzahradnik +[airvisual docs]: /integrations/airvisual/ +[alarmdecoder docs]: /integrations/alarmdecoder/ +[alexa docs]: /integrations/alexa/ +[almond docs]: /integrations/almond/ +[ambient_station docs]: /integrations/ambient_station/ +[androidtv docs]: /integrations/androidtv/ +[api docs]: /integrations/api/ +[apprise docs]: /integrations/apprise/ +[arduino docs]: /integrations/arduino/ +[atag docs]: /integrations/atag/ +[august docs]: /integrations/august/ +[azure_devops docs]: /integrations/azure_devops/ +[bloomsky docs]: /integrations/bloomsky/ +[bmw_connected_drive docs]: /integrations/bmw_connected_drive/ +[bond docs]: /integrations/bond/ +[broadlink docs]: /integrations/broadlink/ +[brunt docs]: /integrations/brunt/ +[camera docs]: /integrations/camera/ +[canary docs]: /integrations/canary/ +[cast docs]: /integrations/cast/ +[comfoconnect docs]: /integrations/comfoconnect/ +[command_line docs]: /integrations/command_line/ +[concord232 docs]: /integrations/concord232/ +[deconz docs]: /integrations/deconz/ +[denon docs]: /integrations/denon/ +[devolo_home_control docs]: /integrations/devolo_home_control/ +[dlink docs]: /integrations/dlink/ +[doods docs]: /integrations/doods/ +[dsmr_reader docs]: /integrations/dsmr_reader/ +[dwd_weather_warnings docs]: /integrations/dwd_weather_warnings/ +[dyson docs]: /integrations/dyson/ +[ebusd docs]: /integrations/ebusd/ +[ecobee docs]: /integrations/ecobee/ +[edl21 docs]: /integrations/edl21/ +[elkm1 docs]: /integrations/elkm1/ +[ffmpeg docs]: /integrations/ffmpeg/ +[ffmpeg_noise docs]: /integrations/ffmpeg_noise/ +[fibaro docs]: /integrations/fibaro/ +[firmata docs]: /integrations/firmata/ +[flux docs]: /integrations/flux/ +[forked_daapd docs]: /integrations/forked_daapd/ +[freebox docs]: /integrations/freebox/ +[fritzbox docs]: /integrations/fritzbox/ +[frontend docs]: /integrations/frontend/ +[goalzero docs]: /integrations/goalzero/ +[gogogate2 docs]: /integrations/gogogate2/ +[griddy docs]: /integrations/griddy/ +[group docs]: /integrations/group/ +[growatt_server docs]: /integrations/growatt_server/ +[hdmi_cec docs]: /integrations/hdmi_cec/ +[history docs]: /integrations/history/ +[home_connect docs]: /integrations/home_connect/ +[homeassistant docs]: /integrations/homeassistant/ +[homekit docs]: /integrations/homekit/ +[homekit_controller docs]: /integrations/homekit_controller/ +[homematicip_cloud docs]: /integrations/homematicip_cloud/ +[huawei_lte docs]: /integrations/huawei_lte/ +[hvv_departures docs]: /integrations/hvv_departures/ +[hyperion docs]: /integrations/hyperion/ +[image docs]: /integrations/image/ +[influxdb docs]: /integrations/influxdb/ +[iqvia docs]: /integrations/iqvia/ +[islamic_prayer_times docs]: /integrations/islamic_prayer_times/ +[isy994 docs]: /integrations/isy994/ +[knx docs]: /integrations/knx/ +[kodi docs]: /integrations/kodi/ +[lcn docs]: /integrations/lcn/ +[light docs]: /integrations/light/ +[logbook docs]: /integrations/logbook/ +[luci docs]: /integrations/luci/ +[maxcube docs]: /integrations/maxcube/ +[media_extractor docs]: /integrations/media_extractor/ +[media_player docs]: /integrations/media_player/ +[meteoalarm docs]: /integrations/meteoalarm/ +[modbus docs]: /integrations/modbus/ +[monoprice docs]: /integrations/monoprice/ +[mqtt docs]: /integrations/mqtt/ +[mysensors docs]: /integrations/mysensors/ +[nest docs]: /integrations/nest/ +[netatmo docs]: /integrations/netatmo/ +[nightscout docs]: /integrations/nightscout/ +[notion docs]: /integrations/notion/ +[nsw_fuel_station docs]: /integrations/nsw_fuel_station/ +[numato docs]: /integrations/numato/ +[nut docs]: /integrations/nut/ +[nws docs]: /integrations/nws/ +[nzbget docs]: /integrations/nzbget/ +[omnilogic docs]: /integrations/omnilogic/ +[onboarding docs]: /integrations/onboarding/ +[onewire docs]: /integrations/onewire/ +[opencv docs]: /integrations/opencv/ +[opentherm_gw docs]: /integrations/opentherm_gw/ +[openweathermap docs]: /integrations/openweathermap/ +[ozw docs]: /integrations/ozw/ +[pilight docs]: /integrations/pilight/ +[plex docs]: /integrations/plex/ +[plugwise docs]: /integrations/plugwise/ +[prometheus docs]: /integrations/prometheus/ +[pvpc_hourly_pricing docs]: /integrations/pvpc_hourly_pricing/ +[recorder docs]: /integrations/recorder/ +[remote docs]: /integrations/remote/ +[rest docs]: /integrations/rest/ +[rest_command docs]: /integrations/rest_command/ +[rfxtrx docs]: /integrations/rfxtrx/ +[roku docs]: /integrations/roku/ +[rpi_power docs]: /integrations/rpi_power/ +[satel_integra docs]: /integrations/satel_integra/ +[sentry docs]: /integrations/sentry/ +[shelly docs]: /integrations/shelly/ +[shiftr docs]: /integrations/shiftr/ +[simplisafe docs]: /integrations/simplisafe/ +[smappee docs]: /integrations/smappee/ +[smarthab docs]: /integrations/smarthab/ +[smartthings docs]: /integrations/smartthings/ +[smarty docs]: /integrations/smarty/ +[snapcast docs]: /integrations/snapcast/ +[solaredge docs]: /integrations/solaredge/ +[solax docs]: /integrations/solax/ +[somfy docs]: /integrations/somfy/ +[somfy_mylink docs]: /integrations/somfy_mylink/ +[sonarr docs]: /integrations/sonarr/ +[sonos docs]: /integrations/sonos/ +[spc docs]: /integrations/spc/ +[splunk docs]: /integrations/splunk/ +[spotify docs]: /integrations/spotify/ +[ssdp docs]: /integrations/ssdp/ +[stream docs]: /integrations/stream/ +[switch docs]: /integrations/switch/ +[synology docs]: /integrations/synology/ +[synology_dsm docs]: /integrations/synology_dsm/ +[system_log docs]: /integrations/system_log/ +[systemmonitor docs]: /integrations/systemmonitor/ +[tag docs]: /integrations/tag/ +[tahoma docs]: /integrations/tahoma/ +[tankerkoenig docs]: /integrations/tankerkoenig/ +[template docs]: /integrations/template/ +[tensorflow docs]: /integrations/tensorflow/ +[tibber docs]: /integrations/tibber/ +[tplink docs]: /integrations/tplink/ +[trend docs]: /integrations/trend/ +[tts docs]: /integrations/tts/ +[unifi docs]: /integrations/unifi/ +[upnp docs]: /integrations/upnp/ +[utility_meter docs]: /integrations/utility_meter/ +[vallox docs]: /integrations/vallox/ +[velbus docs]: /integrations/velbus/ +[vera docs]: /integrations/vera/ +[vesync docs]: /integrations/vesync/ +[vizio docs]: /integrations/vizio/ +[voicerss docs]: /integrations/voicerss/ +[webostv docs]: /integrations/webostv/ +[websocket_api docs]: /integrations/websocket_api/ +[wemo docs]: /integrations/wemo/ +[wink docs]: /integrations/wink/ +[withings docs]: /integrations/withings/ +[wled docs]: /integrations/wled/ +[wolflink docs]: /integrations/wolflink/ +[xiaomi_aqara docs]: /integrations/xiaomi_aqara/ +[zamg docs]: /integrations/zamg/ +[zeroconf docs]: /integrations/zeroconf/ +[zha docs]: /integrations/zha/ +[zodiac docs]: /integrations/zodiac/ +[zoneminder docs]: /integrations/zoneminder/ diff --git a/source/conference/index.markdown b/source/conference/index.markdown new file mode 100644 index 00000000000..815f8b50752 --- /dev/null +++ b/source/conference/index.markdown @@ -0,0 +1,27 @@ +--- +title: Home Assistant Conference 2020 +show_title: false +# is_homepage: true +hide_github_edit: true +description: December 13, 2020 we will host the first online Home Assistant Conference. +og_image: /images/conference/social.png +--- + +Home Assistant Conference header +

      + +The Home Assistant Conference is an online event where the Home Assistant community will share their ideas, creations and major milestones. The event will take place on December 13, 2020 and will be free to participate. + +We're still working out the details, so check back on this page for updates. + +## Open call for speakers + +We're currently looking for people that want to speak at the conference. Talks will need to be either 15 or 30 minutes. You will stream them from your house during the event. + +Talks can be about things you created, like a great automation, an amazing Lovelace dashboard, or a cool new feature. It can also be about your experience with Home Assistant, like how it has improved peoples lives, how you use it for education or some other unique use case. + +If you're interested in speaking, [fill in the form](https://forms.gle/2bxEzk4kWx4fPVMPA). The deadline for submitting a talk is October 31, 2020. + +## Speakers & Schedule + +This will come soon. diff --git a/source/developers/cla_sign.html b/source/developers/cla_sign.html index 47d5e24c32d..f50ed558ea0 100644 --- a/source/developers/cla_sign.html +++ b/source/developers/cla_sign.html @@ -80,7 +80,10 @@ description: "The Home Assistant contributor license agreement (CLA) signature p

      Thank you for signing the Home Assistant Contributor license agreement. We are now redirecting you back to your pull request.

      - + + - - - + + + {% raw %}