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

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2020-08-04 00:45:20 +02:00
commit 12b83ab633
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
47 changed files with 2477 additions and 2106 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
_config.yml
View File

@ -101,8 +101,8 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 113
current_patch_version: 1
date_released: 2020-07-24
current_patch_version: 3
date_released: 2020-08-01
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

434
package-lock.json generated
View File

@ -104,40 +104,56 @@
"dev": true
},
"@textlint/ast-tester": {
"version": "2.1.6",
"resolved": "https://registry.npmjs.org/@textlint/ast-tester/-/ast-tester-2.1.6.tgz",
"integrity": "sha512-i+UrSKZXs561g8LXsCBkgpNYkgBS3T3Pif2/+DraZmSKpQ2r2D1yCOdH82IGPWWpQ/GMSg6Z0qpLJpjnYz+bpg==",
"version": "2.2.4",
"resolved": "https://registry.npmjs.org/@textlint/ast-tester/-/ast-tester-2.2.4.tgz",
"integrity": "sha512-676xpY3/+Xa+tPaiUPaD4sl//+p3xsnSPYLrQjSmHWXX78F3MwAWd/Lek+SCn4wwvf1tCIx0SPtjfOCa6ru8qw==",
"dev": true,
"requires": {
"@textlint/ast-node-types": "^4.2.5"
"@textlint/ast-node-types": "^4.3.4"
},
"dependencies": {
"@textlint/ast-node-types": {
"version": "4.3.4",
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-4.3.4.tgz",
"integrity": "sha512-Grq+vJuNH7HCa278eFeiqJvowrD+onMCoG2ctLyoN+fXYIQGIr1/8fo8AcIg+VM16Kga+N6Y1UWNOWPd8j1nFg==",
"dev": true
}
}
},
"@textlint/ast-traverse": {
"version": "2.1.7",
"resolved": "https://registry.npmjs.org/@textlint/ast-traverse/-/ast-traverse-2.1.7.tgz",
"integrity": "sha512-73Nw0R4TaskPmF36Hop1DZ8AbH339WrGiLQjzbOLaXHaBHQ4hdNw28UMlw4glfPZb7/zvxPcJRtg9AB8F3ZW0g==",
"version": "2.2.5",
"resolved": "https://registry.npmjs.org/@textlint/ast-traverse/-/ast-traverse-2.2.5.tgz",
"integrity": "sha512-YduGVn7iaUYOfo7TwHO4b0K/qQpj61Ol/M884ck3vetNd0zBxpHO3GpQKW87SZGGtlsBa9v5Suz/yypnlPo3Og==",
"dev": true,
"requires": {
"@textlint/ast-node-types": "^4.2.5"
"@textlint/ast-node-types": "^4.3.4"
},
"dependencies": {
"@textlint/ast-node-types": {
"version": "4.3.4",
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-4.3.4.tgz",
"integrity": "sha512-Grq+vJuNH7HCa278eFeiqJvowrD+onMCoG2ctLyoN+fXYIQGIr1/8fo8AcIg+VM16Kga+N6Y1UWNOWPd8j1nFg==",
"dev": true
}
}
},
"@textlint/feature-flag": {
"version": "3.1.6",
"resolved": "https://registry.npmjs.org/@textlint/feature-flag/-/feature-flag-3.1.6.tgz",
"integrity": "sha512-R2s027/WG3zhCMHZG79OhRFmkSL2ghwvFYg/W+2VUva5aYC8i9yeuwRyWt7m83tP1qlI+bq7j3S04fyn6yNheg==",
"version": "3.2.4",
"resolved": "https://registry.npmjs.org/@textlint/feature-flag/-/feature-flag-3.2.4.tgz",
"integrity": "sha512-ABhbZ5rfkwa/kTBFxVmeMzE1flcnUjLJ5LTZvOaxH/pElfLLN1J4FEmAZTRCvXGAB498II6nkM2CqcikbKzh6A==",
"dev": true,
"requires": {
"map-like": "^2.0.0"
}
},
"@textlint/fixer-formatter": {
"version": "3.1.13",
"resolved": "https://registry.npmjs.org/@textlint/fixer-formatter/-/fixer-formatter-3.1.13.tgz",
"integrity": "sha512-FXqAJZ+5fLsOZjvFmn1JhCer8gQI4ZQk3R45bXizRJm6DASByPAGGh/MAQxxHSGeR5wR8miO/koxA2BrS8OhAw==",
"version": "3.2.5",
"resolved": "https://registry.npmjs.org/@textlint/fixer-formatter/-/fixer-formatter-3.2.5.tgz",
"integrity": "sha512-fh6XiLbX9WF8+79g20qb1I85k/Yc9+h7LRccmaLzTBjVQDNYxX5BtfvGsY0Vf5tBZKT2xFZH4eSLH/EWoL3weg==",
"dev": true,
"requires": {
"@textlint/module-interop": "^1.0.2",
"@textlint/types": "^1.3.1",
"@textlint/module-interop": "^1.1.4",
"@textlint/types": "^1.4.5",
"chalk": "^1.1.3",
"debug": "^4.1.1",
"diff": "^4.0.1",
@ -148,6 +164,21 @@
"try-resolve": "^1.0.1"
},
"dependencies": {
"@textlint/ast-node-types": {
"version": "4.3.4",
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-4.3.4.tgz",
"integrity": "sha512-Grq+vJuNH7HCa278eFeiqJvowrD+onMCoG2ctLyoN+fXYIQGIr1/8fo8AcIg+VM16Kga+N6Y1UWNOWPd8j1nFg==",
"dev": true
},
"@textlint/types": {
"version": "1.4.5",
"resolved": "https://registry.npmjs.org/@textlint/types/-/types-1.4.5.tgz",
"integrity": "sha512-7pA1rdiw1jsDNGwxupMC6fPlRNAHY6fKZ3s+jAY53o6RroOSR+5qO0sAjJ26lsSOhveH8imZzyyD08dk58IVJQ==",
"dev": true,
"requires": {
"@textlint/ast-node-types": "^4.3.4"
}
},
"ansi-regex": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.1.1.tgz",
@ -215,23 +246,6 @@
}
}
},
"strip-ansi": {
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.0.tgz",
"integrity": "sha512-AuvKTrTfQNYNIctbR1K/YGTR1756GycPsg7b9bdV9Duqur4gv6aKqHXah67Z8ImS7WEz5QVcOtlfW2rZEugt6w==",
"dev": true,
"requires": {
"ansi-regex": "^5.0.0"
},
"dependencies": {
"ansi-regex": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz",
"integrity": "sha512-bY6fj56OUQ0hU1KjFNDQuJFezqKdrAyFdIevADiqrWHwSlbmBNMHp5ak2f40Pm8JTFyM2mqxkG6ngkHO11f/lg==",
"dev": true
}
}
},
"supports-color": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
@ -241,33 +255,50 @@
}
},
"@textlint/kernel": {
"version": "3.2.1",
"resolved": "https://registry.npmjs.org/@textlint/kernel/-/kernel-3.2.1.tgz",
"integrity": "sha512-gMCgP/tAjCX8dGqgu7nhUwaDC/TzDKeRZb9qa50nqbnILRasKplj3lOWn2osZdkScVZPLQp+al1pDh9pU4D+Dw==",
"version": "3.3.6",
"resolved": "https://registry.npmjs.org/@textlint/kernel/-/kernel-3.3.6.tgz",
"integrity": "sha512-M2ciQDAo5W6rpRADzGnMXyxhvJ+lnqYG9iHrqmfDQ2MA0VcolWuA37H67/UstqTs3NYaGC7RZkq9FAV//pl30w==",
"dev": true,
"requires": {
"@textlint/ast-node-types": "^4.2.5",
"@textlint/ast-tester": "^2.1.6",
"@textlint/ast-traverse": "^2.1.7",
"@textlint/feature-flag": "^3.1.6",
"@textlint/types": "^1.3.1",
"@textlint/utils": "^1.0.3",
"@textlint/ast-node-types": "^4.3.4",
"@textlint/ast-tester": "^2.2.4",
"@textlint/ast-traverse": "^2.2.5",
"@textlint/feature-flag": "^3.2.4",
"@textlint/types": "^1.4.5",
"@textlint/utils": "^1.1.4",
"debug": "^4.1.1",
"deep-equal": "^1.1.0",
"deep-equal": "^1.1.1",
"map-like": "^2.0.0",
"structured-source": "^3.0.2"
},
"dependencies": {
"@textlint/ast-node-types": {
"version": "4.3.4",
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-4.3.4.tgz",
"integrity": "sha512-Grq+vJuNH7HCa278eFeiqJvowrD+onMCoG2ctLyoN+fXYIQGIr1/8fo8AcIg+VM16Kga+N6Y1UWNOWPd8j1nFg==",
"dev": true
},
"@textlint/types": {
"version": "1.4.5",
"resolved": "https://registry.npmjs.org/@textlint/types/-/types-1.4.5.tgz",
"integrity": "sha512-7pA1rdiw1jsDNGwxupMC6fPlRNAHY6fKZ3s+jAY53o6RroOSR+5qO0sAjJ26lsSOhveH8imZzyyD08dk58IVJQ==",
"dev": true,
"requires": {
"@textlint/ast-node-types": "^4.3.4"
}
}
}
},
"@textlint/linter-formatter": {
"version": "3.1.12",
"resolved": "https://registry.npmjs.org/@textlint/linter-formatter/-/linter-formatter-3.1.12.tgz",
"integrity": "sha512-OEP4pklu01MEgBJrftD9vwe3HFx+jhiEe1JFIgf7GZ4a0fSer5vQWXBo5wHW6WtZtSa+iLBsLC3mI5VMeshzdA==",
"version": "3.2.5",
"resolved": "https://registry.npmjs.org/@textlint/linter-formatter/-/linter-formatter-3.2.5.tgz",
"integrity": "sha512-oy5RcBWrC2d7r0Mjw/FBH8cvQuOaCB5PeOPG0Pp44Yr5JbIGLXfh84umHQOTCmxfRxw3ccnUfA9wjbxuL8rWOQ==",
"dev": true,
"requires": {
"@azu/format-text": "^1.0.1",
"@azu/style-format": "^1.0.0",
"@textlint/module-interop": "^1.0.2",
"@textlint/types": "^1.3.1",
"@textlint/module-interop": "^1.1.4",
"@textlint/types": "^1.4.5",
"chalk": "^1.0.0",
"concat-stream": "^1.5.1",
"debug": "^4.1.1",
@ -276,7 +307,6 @@
"optionator": "^0.8.1",
"pluralize": "^2.0.0",
"string-width": "^1.0.1",
"string.prototype.padstart": "^3.0.0",
"strip-ansi": "^6.0.0",
"table": "^3.7.8",
"text-table": "^0.2.0",
@ -284,6 +314,21 @@
"xml-escape": "^1.0.0"
},
"dependencies": {
"@textlint/ast-node-types": {
"version": "4.3.4",
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-4.3.4.tgz",
"integrity": "sha512-Grq+vJuNH7HCa278eFeiqJvowrD+onMCoG2ctLyoN+fXYIQGIr1/8fo8AcIg+VM16Kga+N6Y1UWNOWPd8j1nFg==",
"dev": true
},
"@textlint/types": {
"version": "1.4.5",
"resolved": "https://registry.npmjs.org/@textlint/types/-/types-1.4.5.tgz",
"integrity": "sha512-7pA1rdiw1jsDNGwxupMC6fPlRNAHY6fKZ3s+jAY53o6RroOSR+5qO0sAjJ26lsSOhveH8imZzyyD08dk58IVJQ==",
"dev": true,
"requires": {
"@textlint/ast-node-types": "^4.3.4"
}
},
"ansi-regex": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-2.1.1.tgz",
@ -387,23 +432,6 @@
"safe-buffer": "~5.1.0"
}
},
"strip-ansi": {
"version": "6.0.0",
"resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.0.tgz",
"integrity": "sha512-AuvKTrTfQNYNIctbR1K/YGTR1756GycPsg7b9bdV9Duqur4gv6aKqHXah67Z8ImS7WEz5QVcOtlfW2rZEugt6w==",
"dev": true,
"requires": {
"ansi-regex": "^5.0.0"
},
"dependencies": {
"ansi-regex": {
"version": "5.0.0",
"resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz",
"integrity": "sha512-bY6fj56OUQ0hU1KjFNDQuJFezqKdrAyFdIevADiqrWHwSlbmBNMHp5ak2f40Pm8JTFyM2mqxkG6ngkHO11f/lg==",
"dev": true
}
}
},
"supports-color": {
"version": "2.0.0",
"resolved": "https://registry.npmjs.org/supports-color/-/supports-color-2.0.0.tgz",
@ -413,12 +441,12 @@
}
},
"@textlint/markdown-to-ast": {
"version": "6.1.7",
"resolved": "https://registry.npmjs.org/@textlint/markdown-to-ast/-/markdown-to-ast-6.1.7.tgz",
"integrity": "sha512-B0QtokeQR4a9+4q0NQr8T9l7A1fFihTN5Ze57tVgqW+3ymzXEouh8DvPHeNQ4T6jEkAThvdjk95mxAMpGRJ79w==",
"version": "6.2.5",
"resolved": "https://registry.npmjs.org/@textlint/markdown-to-ast/-/markdown-to-ast-6.2.5.tgz",
"integrity": "sha512-9vlQbylGjnnRGev3yt9ntNy6I9FQH3p+MkbijybKnwobK/msoAX9sThDHOMbGM24PsUHxcDjktDlj2vHN/pwDA==",
"dev": true,
"requires": {
"@textlint/ast-node-types": "^4.2.5",
"@textlint/ast-node-types": "^4.3.4",
"debug": "^4.1.1",
"remark-frontmatter": "^1.2.0",
"remark-parse": "^5.0.0",
@ -427,6 +455,12 @@
"unified": "^6.1.6"
},
"dependencies": {
"@textlint/ast-node-types": {
"version": "4.3.4",
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-4.3.4.tgz",
"integrity": "sha512-Grq+vJuNH7HCa278eFeiqJvowrD+onMCoG2ctLyoN+fXYIQGIr1/8fo8AcIg+VM16Kga+N6Y1UWNOWPd8j1nFg==",
"dev": true
},
"is-buffer": {
"version": "1.1.6",
"resolved": "https://registry.npmjs.org/is-buffer/-/is-buffer-1.1.6.tgz",
@ -516,36 +550,44 @@
}
},
"@textlint/module-interop": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/@textlint/module-interop/-/module-interop-1.0.2.tgz",
"integrity": "sha512-qQ6dqlg4SYywCywimIbkveQZu1MG6ugf6fcJuWDi3D51FbdkSRsMrPusJ1YoW6Y3XBp0ww9fJjXWtlUStGeQsw==",
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/@textlint/module-interop/-/module-interop-1.1.4.tgz",
"integrity": "sha512-9M3kYG5nBoD2lhp05sqi6fieNU6rBcf+A8Trp+4d8o5uJ4RRsWeRtAQMWM7Tv15onqIITRq7fm3la7xovVB9KA==",
"dev": true
},
"@textlint/text-to-ast": {
"version": "3.1.7",
"resolved": "https://registry.npmjs.org/@textlint/text-to-ast/-/text-to-ast-3.1.7.tgz",
"integrity": "sha512-CBAEQmiEa2G/wonlLr1HgUtXfTSas6OGGvYGRIRMJweNh5Ilhbz2nM2/9XQMfLQbdn5pGYrAAAQRB2+/9fZ31A==",
"version": "3.2.4",
"resolved": "https://registry.npmjs.org/@textlint/text-to-ast/-/text-to-ast-3.2.4.tgz",
"integrity": "sha512-uIiNg52OdQ3Fn8aOYaV7BLW2QakNsmf4doypIwrW4q+gHYQ3jxdPHHkq6RxuYoO112vO40M3zmAoEZmM1qmPhw==",
"dev": true,
"requires": {
"@textlint/ast-node-types": "^4.2.5"
"@textlint/ast-node-types": "^4.3.4"
},
"dependencies": {
"@textlint/ast-node-types": {
"version": "4.3.4",
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-4.3.4.tgz",
"integrity": "sha512-Grq+vJuNH7HCa278eFeiqJvowrD+onMCoG2ctLyoN+fXYIQGIr1/8fo8AcIg+VM16Kga+N6Y1UWNOWPd8j1nFg==",
"dev": true
}
}
},
"@textlint/textlint-plugin-markdown": {
"version": "5.1.12",
"resolved": "https://registry.npmjs.org/@textlint/textlint-plugin-markdown/-/textlint-plugin-markdown-5.1.12.tgz",
"integrity": "sha512-CJWWTaomR22hQD3ogrZujMH1pNN7DqZadmx9CJXxgKwpI/cuD5d2kClwXO3MeLFckJr5HRso7SFN5ebqKu1ycw==",
"version": "5.2.6",
"resolved": "https://registry.npmjs.org/@textlint/textlint-plugin-markdown/-/textlint-plugin-markdown-5.2.6.tgz",
"integrity": "sha512-S65wy2npaBLT7pwPPlrN9Pw40hOJsxiW+T6peMJOFEMLRem5qlCIlT+02Wlf0Rrtr6/gKDckpphTUiZT1+xRnQ==",
"dev": true,
"requires": {
"@textlint/markdown-to-ast": "^6.1.7"
"@textlint/markdown-to-ast": "^6.2.5"
}
},
"@textlint/textlint-plugin-text": {
"version": "4.1.13",
"resolved": "https://registry.npmjs.org/@textlint/textlint-plugin-text/-/textlint-plugin-text-4.1.13.tgz",
"integrity": "sha512-KQfSYNDt8HSX8ZL/r86N8OrAuQ9LEuevAtGomtfkw0h7Ed/pUfmuYXjht8wYRdysYBa4JyjrXcmqzRAUdkWrag==",
"version": "4.2.6",
"resolved": "https://registry.npmjs.org/@textlint/textlint-plugin-text/-/textlint-plugin-text-4.2.6.tgz",
"integrity": "sha512-KCgb5GVjoEDIi37UpQN6kFciiouyATNYrj/JufCeLNJEcVcxSm12EoFRKjpXpXmTOVqZUyGnIDU797z1usAZDw==",
"dev": true,
"requires": {
"@textlint/text-to-ast": "^3.1.7"
"@textlint/text-to-ast": "^3.2.4"
}
},
"@textlint/types": {
@ -558,9 +600,9 @@
}
},
"@textlint/utils": {
"version": "1.0.3",
"resolved": "https://registry.npmjs.org/@textlint/utils/-/utils-1.0.3.tgz",
"integrity": "sha512-6oGaBKXYpg5Ooph5p32OFdp1dXDUC1z5mpHg2gmQbx6QZjmP4QX+ygBQdNoCq15d1w88+We6koJl0n0WXjItYw==",
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/@textlint/utils/-/utils-1.1.4.tgz",
"integrity": "sha512-KmU+kGi7vG5toUhNdLHHPxyVN1mNGcjMVe1tNDEXT1wU/3oqA96bunElrROWHYw5iNt1QVRaIAtNeMVyzyAdVA==",
"dev": true
},
"@types/color-name": {
@ -874,22 +916,22 @@
}
},
"es-abstract": {
"version": "1.17.4",
"resolved": "https://registry.npmjs.org/es-abstract/-/es-abstract-1.17.4.tgz",
"integrity": "sha512-Ae3um/gb8F0mui/jPL+QiqmglkUsaQf7FwBEHYIFkztkneosu9imhqHpBzQ3h1vit8t5iQ74t6PEVvphBZiuiQ==",
"version": "1.17.6",
"resolved": "https://registry.npmjs.org/es-abstract/-/es-abstract-1.17.6.tgz",
"integrity": "sha512-Fr89bON3WFyUi5EvAeI48QTWX0AyekGgLA8H+c+7fbfCkJwRWRMLd8CQedNEyJuoYYhmtEqY92pgte1FAhBlhw==",
"dev": true,
"requires": {
"es-to-primitive": "^1.2.1",
"function-bind": "^1.1.1",
"has": "^1.0.3",
"has-symbols": "^1.0.1",
"is-callable": "^1.1.5",
"is-regex": "^1.0.5",
"is-callable": "^1.2.0",
"is-regex": "^1.1.0",
"object-inspect": "^1.7.0",
"object-keys": "^1.1.1",
"object.assign": "^4.1.0",
"string.prototype.trimleft": "^2.1.1",
"string.prototype.trimright": "^2.1.1"
"string.prototype.trimend": "^1.0.1",
"string.prototype.trimstart": "^1.0.1"
}
},
"es-to-primitive": {
@ -990,9 +1032,9 @@
}
},
"flatted": {
"version": "2.0.1",
"resolved": "https://registry.npmjs.org/flatted/-/flatted-2.0.1.tgz",
"integrity": "sha512-a1hQMktqW9Nmqr5aktAux3JMNqaucxGcjtjWnZLHX7yyPCmlSV3M54nGYbqT8K+0GhF3NBgmJCc3ma+WOgX8Jg==",
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/flatted/-/flatted-2.0.2.tgz",
"integrity": "sha512-r5wGx7YeOwNWNlCA0wQ86zKyDLMQr+/RB8xy74M4hTphfmjlijTSSXGuH8rnvKZnfT9i+75zmd8jcKdMR4O6jA==",
"dev": true
},
"format": {
@ -1050,9 +1092,9 @@
}
},
"graceful-fs": {
"version": "4.2.3",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.3.tgz",
"integrity": "sha512-a30VEBm4PEdx1dRB7MFK7BejejvCvBronbLjht+sHuGYj8PHs7M/5Z+rt5lw551vZ7yfTCj4Vuyy3mSJytDWRQ==",
"version": "4.2.4",
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.4.tgz",
"integrity": "sha512-WjKPNJF79dtJAVniUlGGWHYGz2jWxT6VhN/4m1NdkbZ2nOsEF+cI1Edgql5zCRhs/VsQYRvrXctxktVXZUkixw==",
"dev": true
},
"has": {
@ -1094,9 +1136,9 @@
"dev": true
},
"hosted-git-info": {
"version": "2.8.5",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.5.tgz",
"integrity": "sha512-kssjab8CvdXfcXMXVcvsXum4Hwdq9XGtRD3TteMEvEbq0LXyiNQr6AprqKqfeaDXze7SxWvRxdpwE6ku7ikLkg==",
"version": "2.8.8",
"resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.8.tgz",
"integrity": "sha512-f/wzC2QaWBs7t9IYqB4T3sR1xviIViXJRJTWBlx2Gf3g0Xi5vI7Yy4koXQ1c9OYDGHN9sBy1DQ2AB8fqZBWhUg==",
"dev": true
},
"ignore": {
@ -1177,9 +1219,9 @@
"dev": true
},
"is-callable": {
"version": "1.1.5",
"resolved": "https://registry.npmjs.org/is-callable/-/is-callable-1.1.5.tgz",
"integrity": "sha512-ESKv5sMCJB2jnHTWZ3O5itG+O128Hsus4K4Qh1h2/cgn2vbgnLSVqfV46AeJA9D5EeeLa9w81KUXMtn34zhX+Q==",
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/is-callable/-/is-callable-1.2.0.tgz",
"integrity": "sha512-pyVD9AaGLxtg6srb2Ng6ynWJqkHU9bEM087AKck0w8QwDarTfNcpIYoU8x8Hv2Icm8u6kFJM18Dag8lyqGkviw==",
"dev": true
},
"is-date-object": {
@ -1246,12 +1288,12 @@
"dev": true
},
"is-regex": {
"version": "1.0.5",
"resolved": "https://registry.npmjs.org/is-regex/-/is-regex-1.0.5.tgz",
"integrity": "sha512-vlKW17SNq44owv5AQR3Cq0bQPEb8+kF3UKZ2fiZNOWtztYE5i0CzCZxFDwO58qAOWtxdBRVO/V5Qin1wjCqFYQ==",
"version": "1.1.0",
"resolved": "https://registry.npmjs.org/is-regex/-/is-regex-1.1.0.tgz",
"integrity": "sha512-iI97M8KTWID2la5uYXlkbSDQIg4F6o1sYboZKKTDpnDQMLtUL86zxhgDet3Q2SriaYsyGqZ6Mn2SjbRKeLHdqw==",
"dev": true,
"requires": {
"has": "^1.0.3"
"has-symbols": "^1.0.1"
}
},
"is-symbol": {
@ -1416,17 +1458,6 @@
"pify": "^2.0.0",
"pinkie-promise": "^2.0.0",
"strip-bom": "^2.0.0"
},
"dependencies": {
"parse-json": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"integrity": "sha1-9ID0BDTvgHQfhGkJn43qGPVaTck=",
"dev": true,
"requires": {
"error-ex": "^1.2.0"
}
}
}
},
"load-plugin": {
@ -1663,16 +1694,20 @@
"dev": true
},
"object-inspect": {
"version": "1.7.0",
"resolved": "https://registry.npmjs.org/object-inspect/-/object-inspect-1.7.0.tgz",
"integrity": "sha512-a7pEHdh1xKIAgTySUGgLMx/xwDZskN1Ud6egYYN3EdRW4ZMPNEDUTF+hwy2LUC+Bl+SyLXANnwz/jyh/qutKUw==",
"version": "1.8.0",
"resolved": "https://registry.npmjs.org/object-inspect/-/object-inspect-1.8.0.tgz",
"integrity": "sha512-jLdtEOB112fORuypAyl/50VRVIBIdVQOSUUGQHzJ4xBSbit81zRarz7GThkEFZy1RceYrWYcPcBFPQwHyAc1gA==",
"dev": true
},
"object-is": {
"version": "1.0.2",
"resolved": "https://registry.npmjs.org/object-is/-/object-is-1.0.2.tgz",
"integrity": "sha512-Epah+btZd5wrrfjkJZq1AOB9O6OxUQto45hzFd7lXGrpHPGE0W1k+426yrZV+k6NJOzLNNW/nVsmZdIWsAqoOQ==",
"dev": true
"version": "1.1.2",
"resolved": "https://registry.npmjs.org/object-is/-/object-is-1.1.2.tgz",
"integrity": "sha512-5lHCz+0uufF6wZ7CRFWJN3hp8Jqblpgve06U5CMQ3f//6iDjPr2PEo9MWCjEssDsa+UZEL4PkFpr+BMop6aKzQ==",
"dev": true,
"requires": {
"define-properties": "^1.1.3",
"es-abstract": "^1.17.5"
}
},
"object-keys": {
"version": "1.1.1",
@ -1754,13 +1789,12 @@
}
},
"parse-json": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-4.0.0.tgz",
"integrity": "sha1-vjX1Qlvh9/bHRxhPmKeIy5lHfuA=",
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-2.2.0.tgz",
"integrity": "sha1-9ID0BDTvgHQfhGkJn43qGPVaTck=",
"dev": true,
"requires": {
"error-ex": "^1.3.1",
"json-parse-better-errors": "^1.0.1"
"error-ex": "^1.2.0"
}
},
"path-exists": {
@ -1853,17 +1887,6 @@
"js-yaml": "^3.12.0",
"json5": "^2.1.1",
"require-from-string": "^2.0.2"
},
"dependencies": {
"json5": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/json5/-/json5-2.1.1.tgz",
"integrity": "sha512-l+3HXD0GEI3huGq1njuqtzYK8OYJyXMkOLtQ53pjWh89tvWS2h6l+1zMkYWqlb57+SiQodKZyvMEFb2X+KrFhQ==",
"dev": true,
"requires": {
"minimist": "^1.2.0"
}
}
}
},
"read-pkg": {
@ -1899,6 +1922,16 @@
"strip-bom": "^3.0.0"
}
},
"parse-json": {
"version": "4.0.0",
"resolved": "https://registry.npmjs.org/parse-json/-/parse-json-4.0.0.tgz",
"integrity": "sha1-vjX1Qlvh9/bHRxhPmKeIy5lHfuA=",
"dev": true,
"requires": {
"error-ex": "^1.3.1",
"json-parse-better-errors": "^1.0.1"
}
},
"path-type": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/path-type/-/path-type-3.0.0.tgz",
@ -2233,9 +2266,9 @@
"dev": true
},
"resolve": {
"version": "1.15.1",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.15.1.tgz",
"integrity": "sha512-84oo6ZTtoTUpjgNEr5SJyzQhzL72gaRodsSfyxC/AXRvwu0Yse9H8eF9IpGo7b8YetZhlI6v7ZQ6bKBFV/6S7w==",
"version": "1.17.0",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.17.0.tgz",
"integrity": "sha512-ic+7JYiV8Vi2yzQGFWOkiZD5Z9z7O2Zhm9XMaTxdJExKasieFCr+yXZ/WmXsckHiKl12ar0y6XiXDx3m4RHn1w==",
"dev": true,
"requires": {
"path-parse": "^1.0.6"
@ -2281,9 +2314,9 @@
"dev": true
},
"spdx-correct": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-3.1.0.tgz",
"integrity": "sha512-lr2EZCctC2BNR7j7WzJ2FpDznxky1sjfxvvYEyzxNyb6lZXHODmEoJeFu4JupYlkfha1KZpJyoqiJ7pgA1qq8Q==",
"version": "3.1.1",
"resolved": "https://registry.npmjs.org/spdx-correct/-/spdx-correct-3.1.1.tgz",
"integrity": "sha512-cOYcUWwhCuHCXi49RhFRCyJEK3iPj1Ziz9DpViV3tbZOwXD49QzIN3MpOLJNxh2qwq2lJJZaKMVw9qNi4jTC0w==",
"dev": true,
"requires": {
"spdx-expression-parse": "^3.0.0",
@ -2291,15 +2324,15 @@
}
},
"spdx-exceptions": {
"version": "2.2.0",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-2.2.0.tgz",
"integrity": "sha512-2XQACfElKi9SlVb1CYadKDXvoajPgBVPn/gOQLrTvHdElaVhr7ZEbqJaRnJLVNeaI4cMEAgVCeBMKF6MWRDCRA==",
"version": "2.3.0",
"resolved": "https://registry.npmjs.org/spdx-exceptions/-/spdx-exceptions-2.3.0.tgz",
"integrity": "sha512-/tTrYOC7PPI1nUAgx34hUpqXuyJG+DTHJTnIULG4rDygi4xu/tfgmq1e1cIRwRzwZgo4NLySi+ricLkZkw4i5A==",
"dev": true
},
"spdx-expression-parse": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-3.0.0.tgz",
"integrity": "sha512-Yg6D3XpRD4kkOmTpdgbUiEJFKghJH03fiC1OPll5h/0sO6neh2jqRDVHOQ4o/LMea0tgCkbMgea5ip/e+MkWyg==",
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/spdx-expression-parse/-/spdx-expression-parse-3.0.1.tgz",
"integrity": "sha512-cbqHunsQWnJNE6KhVSMsMeH5H/L9EpymbzqTQ3uLwNCLZ1Q481oWaofqH7nO6V07xlXwY6PhQdQ2IedWx/ZK4Q==",
"dev": true,
"requires": {
"spdx-exceptions": "^2.1.0",
@ -2335,34 +2368,24 @@
"strip-ansi": "^6.0.0"
}
},
"string.prototype.padstart": {
"version": "3.1.0",
"resolved": "https://registry.npmjs.org/string.prototype.padstart/-/string.prototype.padstart-3.1.0.tgz",
"integrity": "sha512-envqZvUp2JItI+OeQ5UAh1ihbAV5G/2bixTojvlIa090GGqF+NQRxbWb2nv9fTGrZABv6+pE6jXoAZhhS2k4Hw==",
"string.prototype.trimend": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/string.prototype.trimend/-/string.prototype.trimend-1.0.1.tgz",
"integrity": "sha512-LRPxFUaTtpqYsTeNKaFOw3R4bxIzWOnbQ837QfBylo8jIxtcbK/A/sMV7Q+OAV/vWo+7s25pOE10KYSjaSO06g==",
"dev": true,
"requires": {
"define-properties": "^1.1.3",
"es-abstract": "^1.17.0-next.1"
"es-abstract": "^1.17.5"
}
},
"string.prototype.trimleft": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/string.prototype.trimleft/-/string.prototype.trimleft-2.1.1.tgz",
"integrity": "sha512-iu2AGd3PuP5Rp7x2kEZCrB2Nf41ehzh+goo8TV7z8/XDBbsvc6HQIlUl9RjkZ4oyrW1XM5UwlGl1oVEaDjg6Ag==",
"string.prototype.trimstart": {
"version": "1.0.1",
"resolved": "https://registry.npmjs.org/string.prototype.trimstart/-/string.prototype.trimstart-1.0.1.tgz",
"integrity": "sha512-XxZn+QpvrBI1FOcg6dIpxUPgWCPuNXvMD72aaRaUQv1eD4e/Qy8i/hFTe0BUmD60p/QA6bh1avmuPTfNjqVWRw==",
"dev": true,
"requires": {
"define-properties": "^1.1.3",
"function-bind": "^1.1.1"
}
},
"string.prototype.trimright": {
"version": "2.1.1",
"resolved": "https://registry.npmjs.org/string.prototype.trimright/-/string.prototype.trimright-2.1.1.tgz",
"integrity": "sha512-qFvWL3/+QIgZXVmJBfpHmxLB7xsUXz6HsUmP8+5dRaC3Q7oKUv9Vo6aMCRZC1smrtyECFsIT30PqBJ1gTjAs+g==",
"dev": true,
"requires": {
"define-properties": "^1.1.3",
"function-bind": "^1.1.1"
"es-abstract": "^1.17.5"
}
},
"string_decoder": {
@ -2527,22 +2550,22 @@
"dev": true
},
"textlint": {
"version": "11.6.3",
"resolved": "https://registry.npmjs.org/textlint/-/textlint-11.6.3.tgz",
"integrity": "sha512-tTLLgB49zkJgq6GYDJOT6F31kHLulFjzovCHpN6ycv8d/aPcYl9vv7f/luR33YBQZdnGLtn+j8+G4GJAZ6Uz6w==",
"version": "11.7.6",
"resolved": "https://registry.npmjs.org/textlint/-/textlint-11.7.6.tgz",
"integrity": "sha512-o9nhbylWjOErba1gq2bMoJzughp9JK2VbENR+NCiMsNNEiaJ1P8jbnrL3ES86D6e0QMxziR79w5l7VmmdmLjCw==",
"dev": true,
"requires": {
"@textlint/ast-node-types": "^4.2.5",
"@textlint/ast-traverse": "^2.1.7",
"@textlint/feature-flag": "^3.1.6",
"@textlint/fixer-formatter": "^3.1.13",
"@textlint/kernel": "^3.2.1",
"@textlint/linter-formatter": "^3.1.12",
"@textlint/module-interop": "^1.0.2",
"@textlint/textlint-plugin-markdown": "^5.1.12",
"@textlint/textlint-plugin-text": "^4.1.13",
"@textlint/types": "^1.3.1",
"@textlint/utils": "^1.0.3",
"@textlint/ast-node-types": "^4.3.4",
"@textlint/ast-traverse": "^2.2.5",
"@textlint/feature-flag": "^3.2.4",
"@textlint/fixer-formatter": "^3.2.5",
"@textlint/kernel": "^3.3.6",
"@textlint/linter-formatter": "^3.2.5",
"@textlint/module-interop": "^1.1.4",
"@textlint/textlint-plugin-markdown": "^5.2.6",
"@textlint/textlint-plugin-text": "^4.2.6",
"@textlint/types": "^1.4.5",
"@textlint/utils": "^1.1.4",
"debug": "^4.1.1",
"deep-equal": "^1.1.0",
"file-entry-cache": "^5.0.1",
@ -2561,6 +2584,23 @@
"structured-source": "^3.0.2",
"try-resolve": "^1.0.1",
"unique-concat": "^0.2.2"
},
"dependencies": {
"@textlint/ast-node-types": {
"version": "4.3.4",
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-4.3.4.tgz",
"integrity": "sha512-Grq+vJuNH7HCa278eFeiqJvowrD+onMCoG2ctLyoN+fXYIQGIr1/8fo8AcIg+VM16Kga+N6Y1UWNOWPd8j1nFg==",
"dev": true
},
"@textlint/types": {
"version": "1.4.5",
"resolved": "https://registry.npmjs.org/@textlint/types/-/types-1.4.5.tgz",
"integrity": "sha512-7pA1rdiw1jsDNGwxupMC6fPlRNAHY6fKZ3s+jAY53o6RroOSR+5qO0sAjJ26lsSOhveH8imZzyyD08dk58IVJQ==",
"dev": true,
"requires": {
"@textlint/ast-node-types": "^4.3.4"
}
}
}
},
"textlint-rule-common-misspellings": {
@ -2844,9 +2884,9 @@
"dev": true
},
"unist-util-remove-position": {
"version": "1.1.3",
"resolved": "https://registry.npmjs.org/unist-util-remove-position/-/unist-util-remove-position-1.1.3.tgz",
"integrity": "sha512-CtszTlOjP2sBGYc2zcKA/CvNdTdEs3ozbiJ63IPBxh8iZg42SCCb8m04f8z2+V1aSk5a7BxbZKEdoDjadmBkWA==",
"version": "1.1.4",
"resolved": "https://registry.npmjs.org/unist-util-remove-position/-/unist-util-remove-position-1.1.4.tgz",
"integrity": "sha512-tLqd653ArxJIPnKII6LMZwH+mb5q+n/GtXQZo6S6csPRs5zB0u79Yw8ouR3wTw8wxvdJFhpP6Y7jorWdCgLO0A==",
"dev": true,
"requires": {
"unist-util-visit": "^1.1.0"
@ -2909,9 +2949,9 @@
}
},
"vfile-location": {
"version": "2.0.5",
"resolved": "https://registry.npmjs.org/vfile-location/-/vfile-location-2.0.5.tgz",
"integrity": "sha512-Pa1ey0OzYBkLPxPZI3d9E+S4BmvfVwNAAXrrqGbwTVXWaX2p9kM1zZ+n35UtVM06shmWKH4RPRN8KI80qE3wNQ==",
"version": "2.0.6",
"resolved": "https://registry.npmjs.org/vfile-location/-/vfile-location-2.0.6.tgz",
"integrity": "sha512-sSFdyCP3G6Ka0CEmN83A2YCMKIieHx0EDaj5IDP4g1pa5ZJ4FJDvpO0WODLxo4LUX4oe52gmSCK7Jw4SBghqxA==",
"dev": true
},
"vfile-message": {

2
package.json
View File

@ -10,7 +10,7 @@
"remark-lint-fenced-code-flag": "^2.0.1",
"remark-lint-no-shell-dollars": "^2.0.2",
"remark-stringify": "^8.1.1",
"textlint": "^11.6.3",
"textlint": "^11.7.6",
"textlint-rule-common-misspellings": "^1.0.1",
"textlint-rule-terminology": "^2.1.4"
},

30
source/.well-known/apple-app-site-association
View File

@ -5,19 +5,43 @@
{
"appID": "UTQFCBPQRF.io.robbie.HomeAssistant.dev",
"paths": [
"/ios/*"
"/ios/*",
"/nfc/*"
]
},
{
"appID": "UTQFCBPQRF.io.robbie.HomeAssistant.beta",
"paths": [
"/ios/*"
"/ios/*",
"/nfc/*"
]
},
{
"appID": "UTQFCBPQRF.io.robbie.HomeAssistant",
"paths": [
"/ios/*"
"/ios/*",
"/nfc/*"
]
},
{
"appID": "QMQYCKL255.io.robbie.HomeAssistant.dev",
"paths": [
"/ios/*",
"/nfc/*"
]
},
{
"appID": "QMQYCKL255.io.robbie.HomeAssistant.beta",
"paths": [
"/ios/*",
"/nfc/*"
]
},
{
"appID": "QMQYCKL255.io.robbie.HomeAssistant",
"paths": [
"/ios/*",
"/nfc/*"
]
}
]

162
source/_cookbook/dim_and_brighten_lights.markdown
View File

@ -6,7 +6,9 @@ ha_category: Automation Examples
This requires both a dimmable light, and a Z-Wave remote control that sends one scene when a button is held, and another when released. This ensures that the scripts (which follow) are stopped, avoiding the risks of a script that never ends.
In the following automation, replace `zwave.YOUR_REMOTE` with the actual entity ID of your controller. For the controller this was written for scene ID 13 was sent when the up button was held, and 15 when released. Similarly, scene 14 when the down button was held, and 16 when released. You'll need to use the scene IDs that are sent by your remote if different.
In the following automations, replace `zwave.YOUR_REMOTE` with the actual entity ID of your controller, and `light.YOUR_LIGHT` with the actual entity ID of your light.
For the controller this was written for scene ID 13 was sent when the up button was held, and 15 when released. Similarly, scene 14 when the down button was held, and 16 when released. You'll need to use the scene IDs that are sent by your remote if different.
```yaml
automation:
@ -21,24 +23,11 @@ automation:
entity_id: zwave.YOUR_REMOTE
action:
- service: script.turn_on
entity_id: script.ramp_light
data:
entity_id: script.light_bright
- alias: 'Stop the bright just there'
initial_state: 'on'
trigger:
- platform: event
event_type: zwave.scene_activated
event_data:
scene_id: 15
entity_id: zwave.YOUR_REMOTE
action:
- service: script.turn_off
data:
entity_id: script.light_bright
- service: script.turn_off
data:
entity_id: script.light_bright_pause
variables:
direction: up
light: light.YOUR_LIGHT
- alias: 'Make the lights go dim'
initial_state: 'on'
@ -50,12 +39,20 @@ automation:
entity_id: zwave.YOUR_REMOTE
action:
- service: script.turn_on
entity_id: script.ramp_light
data:
entity_id: script.light_dim
variables:
direction: down
light: light.YOUR_LIGHT
- alias: 'Stop the dim just there'
- alias: 'Stop the light just there'
initial_state: 'on'
trigger:
- platform: event
event_type: zwave.scene_activated
event_data:
scene_id: 15
entity_id: zwave.YOUR_REMOTE
- platform: event
event_type: zwave.scene_activated
event_data:
@ -63,16 +60,15 @@ automation:
entity_id: zwave.YOUR_REMOTE
action:
- service: script.turn_off
data:
entity_id: script.light_dim
- service: script.turn_off
data:
entity_id: script.light_dim_pause
entity_id: script.ramp_light
```
There are 2 variables that control the speed of the change for the scripts below. The first is the `step`, small steps create a smooth transition. The second is the delay, larger delays will create a slower transition.
There are two variables that control the speed of the change for the script below. The first is the step -- small steps create a smooth transition. The second is the delay -- larger delays will create a slower transition.
Please note that some lights do not update their new brightness attribute very quickly, so make sure to use a large enough delay for your particular light.
To allow flexibility, an [Input Number](/integrations/input_number/) is used for the step (at the time of writing this, it's not possible to template the delay when the delay uses milliseconds). Two additional [Input Numbers](/integrations/input_number/) are used to set the minimum and maximum brightness, so that it's easy to tune that (or manage it through an automation).
There are two other variables that control the minimum and maximum brightness levels at which to stop the script.
To allow flexibility all four variables are controlled by [Input Number](/integrations/input_number/) entities so that it's easy to tune (or manage through an automation).
```yaml
input_number:
@ -89,79 +85,63 @@ input_number:
min: 1
max: 255
step: 1
light_maximum:
name: 'No brighter than this'
initial: 255
min: 50
max: 255
step: 1
light_delay_ms:
name: 'Step the lights this often (ms)'
initial: 500
min: 100
max: 5000
step: 100
```
Now the scripts. There are 2 pairs of scripts. The first steps the light brighter to the maximum and the second provides the delay. These call each other until both are stopped. The second pair does the same for dimming.
Now the script.
{% raw %}
```yaml
# Replace YOURLIGHT with the actual light entity
script:
light_bright:
sequence:
- service: light.turn_on
data_template:
entity_id: light.YOUR_LIGHT
brightness: >-
{% raw %}{% set current = state_attr('light.YOUR_LIGHT', 'brightness')|default(0)|int %}
{% set step = states('input_number.light_step')|int %}
{% set next = current + step %}
{% if next > states('input_number.light_maximum')|int %}
{% set next = states('input_number.light_maximum')|int %}
{% endif %}
{{ next }}{% endraw %}
- service_template: >
{% raw %}{% if state_attr('light.YOUR_LIGHT', 'brightness')|default(0)|int < states('input_number.light_maximum')|int %}
script.turn_on
{% else %}
script.turn_off
{% endif %}{% endraw %}
data:
entity_id: script.light_bright_pause
light_bright_pause:
sequence:
- delay:
milliseconds: 1
- service: script.turn_on
data:
entity_id: script.light_bright
light_dim:
sequence:
- service: light.turn_on
data_template:
entity_id: light.YOUR_LIGHT
brightness: >-
{% raw %}{% set current = state_attr('light.YOUR_LIGHT', 'brightness')|default(0)|int %}
{% set step = states('input_number.light_step')|int %}
{% set next = current - step %}
{% if next < states('input_number.light_minimum')|int %}
{% set next = states('input_number.light_minimum')|int %}
{% endif %}
{{ next }}{% endraw %}
- service_template: >
{% raw %}{% if state_attr('light.YOUR_LIGHT', 'brightness')|default(0)|int > states('input_number.light_minimum')|int %}
script.turn_on
{% else %}
script.turn_off
{% endif %}{% endraw %}
data:
entity_id: script.light_dim_pause
light_dim_pause:
sequence:
- delay:
milliseconds: 1
- service: script.turn_on
data:
entity_id: script.light_dim
ramp_light:
alias: Ramp Light Brightness
description: Ramp light brightness up or down
fields:
direction:
description: "Direction to change brightness: up or down"
example: up
light:
description: Light entity_id
example: light.family_room_lamp
mode: restart
sequence:
- repeat:
while:
- condition: template
value_template: >
{% set br = state_attr(light, 'brightness')|int(0) %}
{% set mn = states('input_number.light_minimum')|int %}
{% set mx = states('input_number.light_maximum')|int %}
{{ direction == 'up' and br < mx or
direction == 'down' and br > mn }}
sequence:
- service: light.turn_on
data_template:
entity_id: "{{ light }}"
brightness: >
{% set br = state_attr(light, 'brightness')|int(0) %}
{% set mn = states('input_number.light_minimum')|int %}
{% set mx = states('input_number.light_maximum')|int %}
{% set st = states('input_number.light_step')|int %}
{% if direction == 'up' %}
{{ [br + st, mx]|min }}
{% else %}
{{ [br - st, mn]|max }}
{% endif %}
- delay:
milliseconds: "{{ states('input_number.light_delay_ms')|int }}"
```
{% endraw %}

10
source/_cookbook/foscam_away_mode_PTZ.markdown
View File

@ -19,9 +19,9 @@ switch:
switches:
#Switch for Foscam Motion Detection
foscam_motion:
command_on: 'curl -k "https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=setMotionDetectConfig&isEnable=1&usr=admin&pwd=password"'
command_off: 'curl -k "https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=setMotionDetectConfig&isEnable=0&usr=admin&pwd=password"'
command_state: 'curl -k --silent "https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=getMotionDetectConfig&usr=admin&pwd=password" | grep -oP "(?<=isEnable>).*?(?=</isEnable>)"'
command_on: 'curl -k --tls-max 1.2 "https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=setMotionDetectConfig&isEnable=1&usr=admin&pwd=password"'
command_off: 'curl -k --tls-max 1.2 "https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=setMotionDetectConfig&isEnable=0&usr=admin&pwd=password"'
command_state: 'curl -k --silent --tls-max 1.2 "https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=getMotionDetectConfig&usr=admin&pwd=password" | grep "isEnable" | cut -b 15'
value_template: '{% raw %}{{ value == "1" }}{% endraw %}'
```
@ -30,9 +30,9 @@ The service `shell_command.foscam_turn_off` sets the camera to point down and aw
```yaml
shell_command:
#Created a preset point in Foscam Web Interface named Off which essentially points the camera down and away
foscam_turn_off: 'curl -k "https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=ptzGotoPresetPoint&name=Off&usr=admin&pwd=password"'
foscam_turn_off: 'curl -k --tls-max 1.2 "https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=ptzGotoPresetPoint&name=Off&usr=admin&pwd=password"'
#Created a preset point in Foscam Web Interface named Main which points in the direction I would like to record
foscam_turn_on: 'curl -k "https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=ptzGotoPresetPoint&name=Main&usr=admin&pwd=password"'
foscam_turn_on: 'curl -k --tls-max 1.2 "https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=ptzGotoPresetPoint&name=Main&usr=admin&pwd=password"'
```
The `script.foscam_off` and `script.foscam_on` can be used to set the motion detection appropriately, and then move the camera. These scripts can be called as part of an automation with `device_tracker` triggers to set `home` and `not_home` modes for your Foscam and disable motion detection recording while `home`.

4
source/_docs/mqtt/birth_will.markdown
View File

@ -23,12 +23,12 @@ mqtt:
{% configuration %}
birth_message:
description: Birth Message.
description: Birth Message. Set to the empty dict, `{}`, to disable publishing a birth message.
required: false
type: list
keys:
topic:
description: The MQTT topic to publish the message. Set to the empty dict, `{}`, to disable publishing a birth message.
description: The MQTT topic to publish the message.
required: false
default: homeassistant/status
type: string

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

@ -8,7 +8,7 @@ The MQTT integration needs you to run an MQTT broker for Home Assistant to conne
### Run your own
This is the most private option, is running your own MQTT broker.
The most private option is running your own MQTT broker.
The recommended setup method is to use the [Mosquitto MQTT broker add-on](https://github.com/home-assistant/hassio-addons/blob/master/mosquitto/DOCS.md).

1
source/_docs/mqtt/discovery.markdown
View File

@ -271,6 +271,7 @@ The following software has built-in support for MQTT discovery:
- [Zigbee2mqtt](https://github.com/koenkk/zigbee2mqtt)
- [Zwave2Mqtt](https://github.com/OpenZWave/Zwave2Mqtt) (starting with 2.0.1)
- [IOTLink](https://iotlink.gitlab.io) (starting with 2.0.0)
- [WyzeSense2MQTT](https://github.com/raetha/wyzesense2mqtt)
## Examples

13
source/_includes/asides/hassio_navigation.html
View File

@ -1,17 +1,18 @@
<section class="aside-module grid__item one-whole lap-one-half">
<div class='section'>
<div class="section">
<h1 class="title delta">Topics</h1>
<ul class='divided sidebar-menu'>
<ul class="divided sidebar-menu">
<li>
{% active_link /hassio/ Home Assistant %}
<ul>
<li>{% active_link /hassio/installation/ Installation %}</li>
<li>{% active_link /addons/ Available add-ons %}</li>
<li>{% active_link /hassio/installing_third_party_addons/ Installing third-party add-ons %}</li>
<li>{% active_link /hassio/hassos_faq/ Home Assistant OS FAQ %}</li>
</ul>
</li>
</ul>
<ul class='divided sidebar-menu'>
<ul class="divided sidebar-menu">
<li>
Advanced
<ul>
@ -21,8 +22,10 @@
</ul>
</li>
</ul>
<ul class='divided sidebar-menu'>
<li><a href='/developers/hassio/addon_development/'>Looking to create an add-on?</a></li>
<ul class="divided sidebar-menu">
<li>
<a href="/developers/hassio/addon_development/">Looking to create an add-on?</a>
</li>
</ul>
</div>
</section>

2
source/_integrations/ads.markdown
View File

@ -140,7 +140,7 @@ sensor:
- platform: ads
adsvar: GVL.temperature
unit_of_measurement: '°C'
adstype: integer
adstype: int
```
{% configuration %}

2
source/_integrations/aftership.markdown
View File

@ -8,7 +8,7 @@ ha_iot_class: Cloud Polling
ha_domain: aftership
---
The `aftership` platform allows one to track deliveries by [AfterShip](https://www.aftership.com), a service that supports 490+ couriers worldwide. It is free to use up to 100 tracked packages per month, after that there is a fee.
The `aftership` platform allows one to track deliveries by [AfterShip](https://www.aftership.com), a service that supports 490+ couriers worldwide. There is a 'Forever Free' tier which allows tracking of up to 50 packages per month. There are various paid-for tiers after that.
The sensor value shows the number of packages that are not in `Delivered` state. As attributes are the number of packages per status.

50
source/_integrations/air_quality.xiaomi_miio.markdown
View File

@ -1,50 +0,0 @@
---
title: "Xiaomi Air Quality Monitor"
description: "Instructions how to integrate your Xiaomi Mi Air Quality Monitor within Home Assistant."
ha_category:
- Health
ha_iot_class: Local Polling
ha_release: 0.102
ha_domain: xiaomi_miio
---
The `xiaomi_miio` sensor platform is observing your Xiaomi Mi Air Quality Monitor and reporting the air quality values.
Currently, the supported features are:
- Particulate matter 2.5
- Attributes
- carbon_dioxide_equivalent
- total_volatile_organic_compounds
- temperature
- humidity
Please follow the instructions on [Retrieving the Access Token](/integrations/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token.
## Configuration
To add a Xiaomi Mi Air Quality Monitor to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
air_quality:
- platform: xiaomi_miio
host: IP_ADDRESS
token: YOUR_TOKEN
```
{% configuration %}
host:
description: The IP address of your miio device.
required: true
type: string
token:
description: The API token of your miio device.
required: true
type: string
name:
description: The name of your miio device.
required: false
type: string
default: Xiaomi Miio Air Quality Monitor
{% endconfiguration %}

38
source/_integrations/alarm_control_panel.xiaomi_miio.markdown
View File

@ -1,38 +0,0 @@
---
title: "Xiaomi Gateway Alarm"
description: "Instructions on how to integrate your Xiaomi Gateway Alarm within Home Assistant."
ha_category:
- Alarm
ha_iot_class: Local Polling
ha_release: '0.110'
ha_domain: xiaomi_miio
---
The `xiaomi_miio` alarm_control_panel platform allows you to control the state of your Xiaomi Gateway Alarm.
Please follow the instructions on [Retrieving the Access Token](/integrations/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token to use during configuration.
## Features
- Turn on/off Alarm
- See the status of Alarm (armed_away, disarmed, arming)
## Configuration
To set up the Xiaomi gateway, click Configuration in the sidebar, then click Integrations and then click the + icon in the lower right and find xiaomi_miio. Select the option "Connect to a Xiaomi Gateway" and click submit. You will then be presented with a form in which you will need to fill in the "IP address" and 32 characters "token". Optionally, you can specify a different name for the gateway. After you click submit, you will have the opportunity to select the area that your devices are located.
{% configuration %}
host:
description: The IP address of your Xiaomi gateway.
required: true
type: string
token:
description: The API token of your Xiaomi gateway.
required: true
type: string
name:
description: The name of your Xiaomi gateway.
required: false
type: string
default: Xiaomi Gateway
{% endconfiguration %}

8
source/_integrations/amcrest.markdown
View File

@ -106,13 +106,13 @@ binary_sensors:
default: None
keys:
audio_detected:
description: "Return `on` when audio is detected, `off` when not. Uses streaming method (see [below](#streaming-vs-polled-binary-sensors))."
description: "Return `on` when audio is detected, `off` when not. In order to use this feature you must enable it in your cameras interface under Settings > Events > Audio Detection. Uses streaming method (see [below](#streaming-vs-polled-binary-sensors))."
audio_detected_polled:
description: "Return `on` when audio is detected, `off` when not. Uses polled method (see [below](#streaming-vs-polled-binary-sensors))."
description: "Return `on` when audio is detected, `off` when not. In order to use this feature you must enable it in your cameras interface under Settings > Events > Audio Detection. Uses polled method (see [below](#streaming-vs-polled-binary-sensors))."
motion_detected:
description: "Return `on` when a motion is detected, `off` when not. Uses streaming method (see [below](#streaming-vs-polled-binary-sensors))."
description: "Return `on` when a motion is detected, `off` when not. Motion detection is enabled by default for most cameras, if this functionality is not working check that it is enabled in Settings > Events > Video Detection. Uses streaming method (see [below](#streaming-vs-polled-binary-sensors))."
motion_detected_polled:
description: "Return `on` when a motion is detected, `off` when not. Uses polled method (see [below](#streaming-vs-polled-binary-sensors))."
description: "Return `on` when a motion is detected, `off` when not. Motion detection is enabled by default for most cameras, if this functionality is not working check that it is enabled in Settings > Events > Video Detection. Uses polled method (see [below](#streaming-vs-polled-binary-sensors))."
online:
description: "Return `on` when camera is available (i.e., responding to commands), `off` when not."
sensors:

6
source/_integrations/camera.markdown
View File

@ -73,7 +73,7 @@ Both `duration` and `lookback` options are suggestions, but should be consistent
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | no | Name(s) of entities to create a snapshot from, e.g., `camera.living_room_camera`. |
| `filename` | no | Template of a file name. Variable is `entity_id`, e.g., {% raw %}`/tmp/{{ entity_id }}.mp4`{% endraw %}. |
| `filename` | no | Template of a file name. Variable is `entity_id`, e.g., {% raw %}`/tmp/{{ entity_id.name }}.mp4`{% endraw %}. |
| `duration` | yes | Target recording length (in seconds). Default: 30 |
| `lookback` | yes | Target lookback period (in seconds) to include in addition to duration. Only available if there is currently an active HLS stream. Default: 0 |
@ -87,7 +87,7 @@ action:
service: camera.record
data_template:
entity_id: camera.yourcamera
filename: '/tmp/{{ entity_id }}_{{ now().strftime("%Y%m%d-%H%M%S") }}.mp4'
filename: '/tmp/{{ entity_id.name }}_{{ now().strftime("%Y%m%d-%H%M%S") }}.mp4'
```
{% endraw %}
@ -98,7 +98,7 @@ Take a snapshot from a camera.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | no | Name(s) of entities to create a snapshot from, e.g., `camera.living_room_camera`. |
| `filename` | no | Template of a file name. Variable is `entity_id`, e.g., {% raw %}`/tmp/snapshot_{{ entity_id }}`{% endraw %}. |
| `filename` | no | Template of a file name. Variable is `entity_id`, e.g., {% raw %}`/tmp/snapshot_{{ entity_id.name }}`{% endraw %}. |
The path part of `filename` must be an entry in the `allowlist_external_dirs` in your [`homeassistant:`](/docs/configuration/basic/) section of your `configuration.yaml` file.

4
source/_integrations/coronavirus.markdown
View File

@ -31,8 +31,8 @@ This integration can be configured via the Home Assistant frontend.
- Go to **Configuration** -> **Integrations**.
- Click on the `+` in the bottom right corner to add a new integration.
- Search and select the **Coronavirus** integration form the list.
- Follow the instruction on screen to add the sensors. Either choose for adding
- Search and select the **Coronavirus** integration from the list.
- Follow the instruction on screen to add the sensors. Either choose to add
world-wide sensors, or a specific set of sensors for your country.
If you want to track both world-wide and one or more countries at the same time,

2
source/_integrations/dexcom.markdown
View File

@ -29,7 +29,7 @@ There are two Dexcom Share servers, `US` for United States customers, and `OUS`
#### Unit of measurement
The integrations allows both `md/dL` and `mmol/l` units of measurement for blood glucose values. To change your preferred unit of measurement, got to **Configuration** >> **Integrations** in the UI, and click `OPTIONS`.
The integrations allows both `mg/dL` and `mmol/l` units of measurement for blood glucose values. To change your preferred unit of measurement, got to **Configuration** >> **Integrations** in the UI, and click `OPTIONS`.
### Sensor

1
source/_integrations/dsmr.markdown
View File

@ -35,7 +35,6 @@ USB serial converters:
- Cheap (Banggood/ebay) Generic PL2303
- <https://sites.google.com/site/nta8130p1smartmeter/webshop>
- <https://www.sossolutions.nl/slimme-meter-kabel>
- <https://tweakers.net/gallery/269738/aanbod/>
- <https://nl.aliexpress.com/item/32945187155.html>
Serial to network proxies:

542
source/_integrations/fan.xiaomi_miio.markdown
View File

@ -1,542 +0,0 @@
---
title: "Xiaomi Air Purifier"
description: "Instructions on how to integrate your Xiaomi Air Purifier and Xiaomi Air Humidifier within Home Assistant."
ha_category:
- Fan
ha_iot_class: Local Polling
ha_release: 0.57
ha_domain: xiaomi_miio
---
The `xiaomi_miio` fan platform allows you to control the Xiaomi Air Purifier, Air Humidifier and Air Fresh.
Supported devices:
| Name | Model | Model no. |
| ---------------------- | ---------------------- | --------- |
| Air Purifier | zhimi.airpurifier.v1 | |
| Air Purifier 2 | zhimi.airpurifier.v2 | FJY4006CN |
| Air Purifier V3 | zhimi.airpurifier.v3 | |
| Air Purifier V5 | zhimi.airpurifier.v5 | |
| Air Purifier Pro | zhimi.airpurifier.v6 | |
| Air Purifier Pro V7 | zhimi.airpurifier.v7 | |
| Air Purifier 2 (mini) | zhimi.airpurifier.m1 | |
| Air Purifier (mini) | zhimi.airpurifier.m2 | |
| Air Purifier MA1 | zhimi.airpurifier.ma1 | |
| Air Purifier 2S | zhimi.airpurifier.ma2 | |
| Air Purifier 2S | zhimi.airpurifier.mc1 | |
| Air Purifier Super | zhimi.airpurifier.sa1 | |
| Air Purifier Super 2 | zhimi.airpurifier.sa2 | |
| Air Purifier 3 (2019) | zhimi.airpurifier.ma4 | |
| Air Purifier 3H (2019) | zhimi.airpurifier.mb3 | |
| Air Humidifier | zhimi.humidifier.v1 | |
| Air Humidifier CA1 | zhimi.humidifier.ca1 | |
| Air Humidifier CB1 | zhimi.humidifier.cb1 | |
| Air Fresh VA2 | zhimi.airfresh.va2 | |
## Features
### Air Purifier 2 et al.
- Power (on, off)
- Operation modes (auto, silent, favorite, idle)
- Buzzer (on, off)
- Child lock (on, off)
- LED (on, off), LED brightness (bright, dim, off)
- Favorite Level (0...16)
- Attributes
- `model`
- `temperature`
- `humidity`
- `aqi`
- `mode`
- `filter_hours_used`
- `filter_life_remaining`
- `favorite_level`
- `child_lock`
- `led`
- `motor_speed`
- `average_aqi`
- `purify_volume`
- `learn_mode`
- `sleep_time`
- `sleep_mode_learn_count`
- `extra_features`
- `turbo_mode_supported`
- `auto_detect`
- `use_time`
- `button_pressed`
- `buzzer`
- `led_brightness`
- `sleep_mode`
### Air Purifier Pro (zhimi.airpurifier.v6)
- Power (on, off)
- Operation modes (auto, silent, favorite)
- Child lock (on, off)
- LED (on, off)
- Favorite Level (0...16)
- Attributes
- `model`
- `temperature`
- `humidity`
- `aqi`
- `mode`
- `filter_hours_used`
- `filter_life_remaining`
- `favorite_level`
- `child_lock`
- `led`
- `motor_speed`
- `average_aqi`
- `purify_volume`
- `learn_mode`
- `sleep_time`
- `sleep_mode_learn_count`
- `extra_features`
- `turbo_mode_supported`
- `auto_detect`
- `use_time`
- `button_pressed`
- `filter_rfid_product_id`
- `filter_rfid_tag`
- `filter_type`
- `illuminance`
- `motor2_speed`
- `volume`
### Air Purifier Pro V7 (zhimi.airpurifier.v7)
- Power (on, off)
- Operation modes (auto, silent, favorite)
- Child lock (on, off)
- LED (on, off)
- Favorite Level (0...16)
- Attributes
- `model`
- `temperature`
- `humidity`
- `aqi`
- `mode`
- `filter_hours_used`
- `filter_life_remaining`
- `favorite_level`
- `child_lock`
- `led`
- `motor_speed`
- `average_aqi`
- `learn_mode`
- `extra_features`
- `turbo_mode_supported`
- `button_pressed`
- `filter_rfid_product_id`
- `filter_rfid_tag`
- `filter_type`
- `illuminance`
- `motor2_speed`
- `volume`
### Air Purifier 2S (zhimi.airpurifier.mc1)
- Power (on, off)
- Operation modes (auto, silent, favorite)
- Buzzer (on, off)
- Child lock (on, off)
- LED (on, off)
- Favorite Level (0...16)
- Attributes
- `model`
- `temperature`
- `humidity`
- `aqi`
- `mode`
- `filter_hours_used`
- `filter_life_remaining`
- `favorite_level`
- `child_lock`
- `led`
- `motor_speed`
- `average_aqi`
- `learn_mode`
- `extra_features`
- `turbo_mode_supported`
- `button_pressed`
- `filter_rfid_product_id`
- `filter_rfid_tag`
- `filter_type`
- `illuminance`
- `buzzer`
### Air Purifier 3/3H (2019) (zhimi.airpurifier.ma4/zhimi.airpurifier.mb3)
This model uses newer MiOT communication protocol.
- Power (on, off)
- Operation modes (auto, silent, favorite, fan)
- Buzzer (on, off)
- Child lock (on, off)
- LED (on, off)
- Favorite Level (0...16)
- Fan Level (1...3)
- Attributes
- `model`
- `temperature`
- `humidity`
- `aqi`
- `mode`
- `filter_hours_used`
- `filter_life_remaining`
- `favorite_level`
- `child_lock`
- `led`
- `motor_speed`
- `average_aqi`
- `purify_volume`
- `use_time`
- `buzzer`
- `led_brightness`
- `filter_rfid_product_id`
- `filter_rfid_tag`
- `filter_type`
- `fan_level`
### Air Purifier V3 (zhimi.airpurifier.v3)
- Power (on, off)
- Operation modes (auto, silent, favorite, idle, medium, high, strong)
- Child lock (on, off)
- LED (on, off)
- Attributes
- `model`
- `aqi`
- `mode`
- `led`
- `buzzer`
- `child_lock`
- `illuminance`
- `filter_hours_used`
- `filter_life_remaining`
- `motor_speed`
- `average_aqi`
- `volume`
- `motor2_speed`
- `filter_rfid_product_id`
- `filter_rfid_tag`
- `filter_type`
- `purify_volume`
- `learn_mode`
- `sleep_time`
- `sleep_mode_learn_count`
- `extra_features`
- `auto_detect`
- `use_time`
- `button_pressed`
### Air Humidifier (zhimi.humidifier.v1)
- On, Off
- Operation modes (silent, medium, high, strong)
- Buzzer (on, off)
- Child lock (on, off)
- LED (on, off), LED brightness (bright, dim, off)
- Target humidity (30, 40, 50, 60, 70, 80)
- Attributes
- `model`
- `temperature`
- `humidity`
- `mode`
- `buzzer`
- `child_lock`
- `trans_level`
- `target_humidity`
- `led_brightness`
- `button_pressed`
- `use_time`
- `hardware_version`
### Air Humidifier CA (zhimi.humidifier.ca1)
- On, Off
- Operation modes (silent, medium, high, auto)
- Buzzer (on, off)
- Child lock (on, off)
- LED (on, off), LED brightness (bright, dim, off)
- Target humidity (30, 40, 50, 60, 70, 80)
- Dry mode (on, off)
- Attributes
- `model`
- `temperature`
- `humidity`
- `mode`
- `buzzer`
- `child_lock`
- `trans_level`
- `target_humidity`
- `led_brightness`
- `button_pressed`
- `use_time`
- `hardware_version`
- `motor_speed`
- `depth`
- `dry`
### Air Humidifier CB (zhimi.humidifier.cb1)
- On, Off
- Operation modes (silent, medium, high, auto)
- Buzzer (on, off)
- Child lock (on, off)
- LED (on, off), LED brightness (bright, dim, off)
- Target humidity (30, 40, 50, 60, 70, 80)
- Dry mode (on, off)
- Attributes
- `speed`
- `speed_list`
- `model`
- `temperature`
- `humidity`
- `mode`
- `buzzer`
- `child_lock`
- `target_humidity`
- `led_brightness`
- `use_time`
- `hardware_version`
- `motor_speed`
- `depth`
- `dry`
- `supported_features`
### Air Fresh VA2
* Power (on, off)
* Operation modes (auto, silent, interval, low, middle, strong)
* Buzzer (on, off)
* Child lock (on, off)
* LED (on, off), LED brightness (bright, dim, off)
* Attributes
- `model`
- `aqi`
- `average_aqi`
- `temperature`
- `humidity`
- `co2`
- `mode`
- `led`
- `led_brightness`
- `buzzer`
- `child_lock`
- `filter_life_remaining`
- `filter_hours_used`
- `use_time`
- `motor_speed`
- `extra_features`
Please follow the instructions on [Retrieving the Access Token](/integrations/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token to use in the `configuration.yaml` file.
To add a Xiaomi Air Purifier to your installation, add the following to your `configuration.yaml` file:
```yaml
fan:
# Example configuration.yaml entry
- platform: xiaomi_miio
host: 192.168.130.66
token: YOUR_TOKEN
```
{% configuration %}
host:
description: The IP address of your miio fan.
required: true
type: string
token:
description: The API token of your miio fan.
required: true
type: string
name:
description: The name of your miio fan.
required: false
type: string
default: Xiaomi Air Purifier
model:
description: The model of your miio fan. See the table above for valid values (f.e. `zhimi.airpurifier.v2`). This setting can be used to bypass the device model detection and is recommended if your device isn't always available.
required: false
type: string
{% endconfiguration %}
## Platform Services
### Service `fan.set_speed`
Set the fan speed/operation mode.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
| `speed` | no | Fan speed. Valid values are 'Auto', 'Silent', 'Favorite' and 'Idle' |
### Service `xiaomi_miio.fan_set_buzzer_on` (Air Purifier Pro excluded)
Turn the buzzer on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `xiaomi_miio.fan_set_buzzer_off` (Air Purifier Pro excluded)
Turn the buzzer off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `xiaomi_miio.fan_set_led_on` (Air Purifiers only)
Turn the LED on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `xiaomi_miio.fan_set_led_off` (Air Purifiers only)
Turn the LED off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `xiaomi_miio.fan_set_child_lock_on`
Turn the child lock on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `xiaomi_miio.fan_set_child_lock_off`
Turn the child lock off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `xiaomi_miio.fan_set_led_brightness` (Air Purifier 2S and Air Purifier Pro excluded)
Set the LED brightness. Supported values are 0 (Bright), 1 (Dim), 2 (Off).
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
| `brightness` | no | Brightness, between 0 and 2. |
### Service `xiaomi_miio.fan_set_favorite_level` (Air Purifiers only)
Set the favorite level of the operation mode "favorite".
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
| `level` | no | Level, between 0 and 16. |
### Service `xiaomi_miio.fan_set_fan_level` (Air Purifiers only)
Set the fan level for "fan" operation mode.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi MiOT fan entity. |
| `level` | no | Level, between 1 and 3. |
### Service `xiaomi_miio.fan_set_auto_detect_on` (Air Purifier 2S and Air Purifier Pro only)
Turn the auto detect on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `xiaomi_miio.fan_set_auto_detect_off` (Air Purifier 2S and Air Purifier Pro only)
Turn the auto detect off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `xiaomi_miio.fan_set_learn_mode_on` (Air Purifier 2 only)
Turn the learn mode on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `xiaomi_miio.fan_set_learn_mode_off` (Air Purifier 2 only)
Turn the learn mode off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `xiaomi_miio.fan_set_volume` (Air Purifier Pro only)
Set the sound volume.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
| `volume` | no | Volume, between 0 and 100. |
### Service `xiaomi_miio.fan_reset_filter` (Air Purifier 2 only)
Reset the filter lifetime and usage.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `xiaomi_miio.fan_set_extra_features` (Air Purifier only)
Set the extra features.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
| `features` | no | Integer, known values are 0 and 1. |
### Service `xiaomi_miio.fan_set_target_humidity` (Air Humidifier only)
Set the target humidity.
| Service data attribute | Optional | Description |
|---------------------------|----------|-----------------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
| `humidity` | no | Target humidity. Allowed values are 30, 40, 50, 60, 70 and 80 |
### Service `fan.xiaomi_miio_set_dry_on` (Air Humidifier CA and CB)
Turn the dry mode on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
### Service `fan.xiaomi_miio_set_dry_off` (Air Humidifier CA and CB)
Turn the dry mode off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
## Troubleshooting `Unable to find device` error messages
Check if the device is in the same subnet as the Home Assistant instance. Otherwise, you should configure your router/firewall to put this device in the same VLAN as the Home Assistant instance.
If it's not possible to use VLANs for some reason, your last resort may be using NAT translation, between the IPs.

1
source/_integrations/freebox.markdown
View File

@ -79,6 +79,7 @@ To make the Wi-Fi switch and the reboot service working you will have to add "Mo
Only the routers with Freebox OS are supported:
* Freebox V8 also known as Freebox Pop
* Freebox V7 also known as Freebox Delta
* Freebox V6 also known as Freebox Revolution
* Freebox mini 4k

49
source/_integrations/google_assistant.markdown
View File

@ -31,20 +31,25 @@ 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.
1. Create a new project in the [Actions on Google console](https://console.actions.google.com/).
1. Add/Import a project and give it a name.
2. Click on the `Smart Home` card, select the `Smart home` recommendation.
3. Click `Build your Action`, select `Add Action(s)`. Add your Home Assistant URL: `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant` in the `Fulfillment URL` box, replace the `[YOUR HOME ASSISTANT URL:PORT]` with the domain / IP address and the port under which your Home Assistant is reachable.
4. Click `Save`. Then click on `Overview`, which will lead you back to the app details screen.
2. `Account linking` is required for your app to interact with Home Assistant. Set this up under the `Quick Setup` section.
1. Leave it at the default `No, I only want to allow account creation on my website` and select `Next`.
2. For the `Linking type` select `OAuth` and `Authorization Code`. Click `Next`
3. Client ID: `https://oauth-redirect.googleusercontent.com/r/YOUR_PROJECT_ID`.
4. Client Secret: Anything you like, Home Assistant doesn't need this field.
5. Authorization URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL:PORT]/auth/authorize`.
6. Token URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL:PORT]/auth/token`. Click `Next`
7. Configure your client: Type `email` and click `Add scope`, then type `name` and click `Add scope` again.
8. Do **NOT** check `Google to transmit clientID and secret via HTTP basic auth header`. Click `Next`
9. Testing instructions: Enter anything. It doesn't matter since you won't submit this app. Click `Save`
1. Click `New Project` and give your project a name.
2. Click on the `Smart Home` card, then click the `Start Building` button.
3. Click `Build your Action`, then click `Add Action(s)`.
4. Add your Home Assistant URL: `https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant` in the `Fulfillment URL` box, replace the `[YOUR HOME ASSISTANT URL:PORT]` with the domain / IP address and the port under which your Home Assistant is reachable.
5. Click `Save`.
6. Click on the `Overview` tab, which will lead you back to the app details screen.
2. `Account linking` is required for your app to interact with Home Assistant.
1. Set this up by clicking on `Setup account linking` under the `Quick Setup` section of the `Overview` page.
2. If asked, leave options as they default `No, I only want to allow account creation on my website` and select `Next`.
3. Then if asked, for the `Linking type` select `OAuth` and `Authorization Code`. Click `Next`
4. Enter the following:
1. Client ID: `https://oauth-redirect.googleusercontent.com/r/YOUR_PROJECT_ID`. (Find your YOUR_PROJECT_ID by clicking on the three little dots (more) icon in the upper right corner of the console, selecting `Project settings`, your Project ID will be listed on the `GENERAL` tab of the `Settings` page.)
2. Client Secret: Anything you like, Home Assistant doesn't need this field.
3. Authorization URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL:PORT]/auth/authorize`.
4. Token URL (replace with your actual URL): `https://[YOUR HOME ASSISTANT URL:PORT]/auth/token`.
Click `Next`, then `Next` again.
5. In the `Configure your client` `Scopes` textbox, type `email` and click `Add scope`, then type `name` and click `Add scope` again.
6. Do **NOT** check `Google to transmit clientID and secret via HTTP basic auth header`.
7. Click `Next`, then click `Save`
<img src='/images/integrations/google_assistant/accountlinking.png' alt='Screenshot: Account linking'>
@ -60,11 +65,15 @@ If you've added Home Assistant to your phone's home screen, you have to first re
</div>
1. If you want to allow other household users to control the devices:
1. Go to the settings for the project you created in the [Actions on Google console](https://console.actions.google.com/).
2. Click `Test -> Simulator`, then click `Share` icon in the right top corner. Follow the on-screen instruction:
1. Add team members: Got to `Settings -> Permission`, click `Add`, type the new user's e-mail address and choose `Project -> Viewer` role.
2. Copy and share the link with the new user.
3. When the new user opens the link with their own Google account, it will enable your draft test app under their account.
1. Open the project you created in the [Actions on Google console](https://console.actions.google.com/).
2. Click `Test` on the top of the page, then click `Simulator` located to the page left, then click the three little dots (more) icon in the upper right corner of the console.
3. Click Manage user access. This redirects you to the Google Cloud Platform IAM permissions page.
4. Click ADD at the top of the page.
1. Enter the email address of the user you want to add.
2. Click Select a role and choose Project < Viewer.
3. Click SAVE
2. Copy and share the link with the new user.
3. When the new user opens the link with their own Google account, it will enable your draft test app under their account.
3. Have the new user go to their `Google Assistant` app to add `[test] your app name` to their account.
2. If you want to support actively reporting of state to Google's server (configuration option `report_state`) and support `google_assistant.request_sync`, you need to generate a service account.
1. In the GCP Console, go to the [Create Service account key](https://console.cloud.google.com/apis/credentials/serviceaccountkey) page.
@ -119,7 +128,7 @@ api_key:
type: string
service_account:
description: Service account information. You can use an include statement with your downloaded JSON file, enter data here directly or use secrets file to populate.
required: false
required: true
type: map
keys:
private_key:

2
source/_integrations/homekit.markdown
View File

@ -11,7 +11,7 @@ ha_codeowners:
- '@bdraco'
---
The HomeKit Bridge integration allows you to forward entities from Home Assistant to Apple HomeKit, so they can be controlled from Apple's Home app and Siri. Please make sure that you have read the [considerations](#considerations) listed below to save you some trouble later. However if you do encounter issues, check out the [troubleshooting](#troubleshooting) section.
The HomeKit Bridge integration allows you to make your Home Assistant entities available in Apple HomeKit, so they can be controlled from Apple's Home app and Siri. Please make sure that you have read the [considerations](#considerations) listed below to save you some trouble later. However if you do encounter issues, check out the [troubleshooting](#troubleshooting) section.
<div class="note">

2
source/_integrations/honeywell.markdown
View File

@ -14,7 +14,7 @@ The `honeywell` climate platform integrates Home Assistant with _US-based_ [Hone
It uses the [somecomfort](https://github.com/kk7ds/somecomfort) client library. It does not support the home security functionality of TCC.
If your system is compatible with this integration, then you will be able access your it via [https://mytotalconnectcomfort.com/portal/](https://mytotalconnectcomfort.com/portal/) (note the `/portal/`).
If your system is compatible with this integration, then you will be able access it via [https://mytotalconnectcomfort.com/portal/](https://mytotalconnectcomfort.com/portal/) (note the `/portal/`).
## Configuration

6
source/_integrations/iammeter.markdown
View File

@ -13,6 +13,12 @@ ha_codeowners:
`iammeter` provides real-time readings of single-phase (WEM3080, WEM3162) and three-phase (WEM3080T) meters from [IAMMETER](https://www.iammeter.com) over Wi-Fi.
Example Lovelace Dashboard:
<p class='img'>
<img src='/images/integrations/iammeter/demo.jpg' />
</p>
## Configuration
To use this sensor in your installation, add the following to your `configuration.yaml` file:

2
source/_integrations/input_number.markdown
View File

@ -242,7 +242,7 @@ automation:
entity_id: switch.something
to: 'on'
action:
- delay: '00:{{ states('input_number.minutes') | int }}:{{ states('input_number.seconds') | int }}'
- delay: "00:{{ states('input_number.minutes') | int }}:{{ states('input_number.seconds') | int }}"
- service: switch.turn_off
entity_id: switch.something
```

199
source/_integrations/light.xiaomi_miio.markdown
View File

@ -1,199 +0,0 @@
---
title: "Xiaomi Philips Light"
description: "Instructions on how to integrate your Xiaomi Philips Lights within Home Assistant."
ha_category:
- Light
ha_iot_class: Local Polling
ha_release: 0.53
ha_domain: xiaomi_miio
---
The `xiaomi_miio` platform allows you to control the state of your Xiaomi Philips LED Ball Lamp, Xiaomi Philips Zhirui LED Bulb E14 Candle Lamp, Xiaomi Philips Zhirui Downlight, Xiaomi Philips LED Ceiling Lamp, Xiaomi Philips Eyecare Lamp 2, Xiaomi Philips Moonlight Bedside Lamp and Philips Zhirui Desk Lamp.
## Features
### Philips LED Ball Lamp, Philips Zhirui LED Candle Lamp and Philips Zhirui Downlight
Supported models: `philips.light.bulb`, `philips.light.candle`, `philips.light.candle2`, `philips.light.downlight`
* Power (on, off)
* Brightness
* Color temperature (175...333 mireds)
* Scene (1, 2, 3, 4)
* Delayed turn off (Resolution in seconds)
* Attributes
- model
- scene
- delayed_turn_off
### Philips LED Ceiling Lamp
Supported models: `philips.light.ceiling`, `philips.light.zyceiling`
* Power (on, off)
* Brightness
* Color temperature (175...370 mireds)
* Scene (1, 2, 3, 4)
* Night light mode (on, off)
* Delayed turn off (Resolution in seconds)
* Attributes
- model
- scene
- delayed_turn_off
- night_light_mode
- automatic_color_temperature
### Philips Eyecare Smart Lamp 2
Supported models: `philips.light.sread1`
* Eyecare light (on, off)
* Ambient light (on, off)
* Brightness (of each light)
* Scene (1, 2, 3, 4)
* Night light mode (on, off)
* Delayed turn off (Resolution in seconds)
* Eye fatigue reminder / notification (on, off)
* Eyecare mode (on, off)
* Attributes
- model
- scene
- delayed_turn_off
- night_light_mode
- reminder
- eyecare_mode
### Philips Zhirui Desk Lamp
Supported models: `philips.light.mono1`
* Power (on, off)
* Brightness
* Scene (1, 2, 3, 4)
* Delayed turn off (Resolution in seconds)
* Attributes
- model
- scene
- delayed_turn_off
### Philips Moonlight Bedside Lamp
Supported models: `philips.light.moonlight`
* Power (on, off)
* Brightness
* Color
* Color temperature (153...588 mireds)
* Scene (1, 2, 3, 4, 5, 6)
* Attributes
- model
- scene
- sleep_assistant
- sleep_off_time
- total_assistant_sleep_time
- brand_sleep
- brand
Please follow the instructions on [Retrieving the Access Token](/integrations/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token to use in the `configuration.yaml` file.
To add a Xiaomi Philips Light to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entries
light:
- platform: xiaomi_miio
name: Xiaomi Philips Smart LED Ball
host: 192.168.130.67
token: YOUR_TOKEN
model: philips.light.bulb
```
{% configuration %}
host:
description: The IP address of your miio light.
required: true
type: string
token:
description: The API token of your miio light.
required: true
type: string
name:
description: The name of your miio light.
required: false
type: string
default: Xiaomi Philips Light
model:
description: The model of your light. Valid values are `philips.light.sread1`, `philips.light.ceiling`, `philips.light.zyceiling`, `philips.light.moonlight`, `philips.light.bulb`, `philips.light.candle`, `philips.light.candle2`, `philips.light.mono1` and `philips.light.downlight`. This setting can be used to bypass the device model detection and is recommended if your device isn't always available.
required: false
type: string
{% endconfiguration %}
## Platform Services
### Service `xiaomi_miio.light_set_scene`
Set one of the 4 available fixed scenes.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
| `scene` | no | Scene, between 1 and 4. |
### Service `xiaomi_miio.light_set_delayed_turn_off`
Delayed turn off.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
| `time_period` | no | Time period for the delayed turn off. |
### Service `xiaomi_miio.light_reminder_on` (Eyecare Smart Lamp 2 only)
Enable the eye fatigue reminder/notification.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
### Service `xiaomi_miio.light_reminder_off` (Eyecare Smart Lamp 2 only)
Disable the eye fatigue reminder/notification.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
### Service `xiaomi_miio.light_night_light_mode_on` (Eyecare Smart Lamp 2 only)
Turn the smart night light mode on.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
### Service `xiaomi_miio.light_night_light_mode_off` (Eyecare Smart Lamp 2 only)
Turn the smart night light mode off.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
### Service `xiaomi_miio.light_eyecare_mode_on` (Eyecare Smart Lamp 2 only)
Turn the eyecare mode on.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |
### Service `xiaomi_miio.light_eyecare_mode_off` (Eyecare Smart Lamp 2 only)
Turn the eyecare mode off.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO light entity. |

6
source/_integrations/owntracks.markdown
View File

@ -8,7 +8,7 @@ ha_config_flow: true
ha_domain: owntracks
---
[OwnTracks](https://owntracks.org/) is a free and open source application for iOS and Android that allow you to track your location and send it directly to Home Assistant. It can be set up via the integrations panel in the configuration screen.
[OwnTracks](https://owntracks.org/) (and its Android fork [NextTracks](https://codeberg.org/nexttracks/android)) is a free and open source application for iOS and Android that allow you to track your location and send it directly to Home Assistant. It can be set up via the integrations panel in the configuration screen.
By default the integration will listen for incoming messages from OwnTracks via HTTP. It will also listen for MQTT messages if Home Assistant is configured to use MQTT. When a location is submitted via HTTP, Home Assistant will return all [Persons](/integrations/person/)' last known locations and they will be displayed within the OwnTracks app.
@ -22,9 +22,9 @@ To configure OwnTracks, you must set it up via the integrations panel in the con
### Configuring the app - Android
[Install the OwnTracks application for Android.](https://play.google.com/store/apps/details?id=org.owntracks.android)
Install [OwnTracks](https://play.google.com/store/apps/details?id=org.owntracks.android) or [NextTracks](https://codeberg.org/nexttracks/android/releases) (Soon available from [F-Droid](https://gitlab.com/fdroid/fdroiddata/-/merge_requests/6831)) application for Android.
In the OwnTracks app, open sidebar and click on preferences, then on connection. Change the following settings:
In the app, open the sidebar and click on preferences, then on the connection. Change the following settings:
- Mode: Private HTTP
- Host: `<URL given to you when setting up the integration>`

1
source/_integrations/panasonic_viera.markdown
View File

@ -102,6 +102,7 @@ script:
- TC-P65VT30
- TX-32AS520E
- TX-32DSX609
- TX-40CXE720
- TX-40DX600
- TX-40DX700B
- TX-49DX650B

190
source/_integrations/remote.xiaomi_miio.markdown
View File

@ -1,190 +0,0 @@
---
title: "Xiaomi IR Remote"
description: "Instructions for how to integrate the Xiaomi IR Remote within Home Assistant."
ha_category:
- Remote
ha_release: 0.63
ha_iot_class: Local Polling
ha_domain: xiaomi_miio
---
The `xiaomi miio` remote platform allows you to send IR commands from your Xiaomi IR Remote (ChuangmiIr).
## Setup
Please follow the instructions on [Retrieving the Access Token](/integrations/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token to use in the `configuration.yaml` file.
## Configuring the Platform
To add a Xiaomi IR Remote to your installation, add the following to your `configuration.yaml` file:
```yaml
remote:
- platform: xiaomi_miio
host: 192.168.42.42
token: YOUR_TOKEN
```
{% configuration %}
host:
description: The IP of your remote.
required: true
type: string
token:
description: The API token of your remote.
required: true
type: string
name:
description: The name of your remote.
required: false
type: string
slot:
description: The slot used to save learned command.
required: false
type: integer
default: 1
timeout:
description: Timeout for learning a new command.
required: false
type: integer
default: 30
commands:
description: A list of commands
required: false
type: map
keys:
command:
description: A list of commands as [raw (learned command)](/integrations/remote.xiaomi_miio/#raw) or [pronto hex code](/integrations/remote.xiaomi_miio/#pronto-hex-code).
required: true
type: list
{% endconfiguration %}
## Full Configuration
```yaml
remote:
- platform: xiaomi_miio
name: "bathroom remote"
host: 192.168.42.42
token: YOUR_TOKEN
slot: 1
timeout: 30
commands:
activate_towel_heater:
command:
- raw:base64:[optional_frequency]
read_bad_poem:
command:
- raw:base64:[optional_frequency]
- pronto:pronto_hex:[optional_repeat]
```
## Add command as entity button in Lovelace UI
```yaml
type: entity-button
tap_action:
action: call-service
service: remote.send_command
service_data:
command: activate_towel_heater
entity_id: remote.xiaomi_miio_ir
hold_action:
action: more-info
show_icon: true
show_name: true
entity: remote.xiaomi_miio_ir
icon: 'mdi:radiator'
name: Activate Towel Heater
```
## Use named commands to create UI buttons
```yaml
script:
towel_heater:
sequence:
- service: remote.send_command
entity_id: 'remote.bathroom_remote'
data:
command:
- 'activate_towel_heater'
please_cover_your_ears:
sequence:
- service: remote.send_command
entity_id: 'remote.bathroom_remote'
data:
command:
- 'read_bad_poem'
```
## Command Types
The Xiaomi IR Remote Platform currently supports two different formats for IR codes.
### Raw
A raw command is a command learned from [`xiaomi_miio.remote_learn_command`](/integrations/remote.xiaomi_miio/#xiaomi_miioremote_learn_command).
A raw command is defined as in the following example:
```bash
raw:Z6UFANEAAAAjAQAAAwkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQIAE=
```
with an optional last parameter of frequency:
```bash
raw:Z6UFANEAAAAjAQAAAwkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQIAE=:38400
```
### Pronto Hex Code
A pronto hex code is a hex code often supplied by the device manufacturer.
A pronto hex code is defined as in the following example:
```bash
pronto:0000 006C 0022 0002 015B 00AD 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0016 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0623 015B 0057 0016 0E6E
```
with an optional last parameter of repeats (required by some devices):
```bash
pronto:0000 006C 0022 0002 015B 00AD 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0016 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0623 015B 0057 0016 0E6E:2
```
Note there are at least 4 versions of the Xiaomi IR Remote (ChuangmiIr) which can be recognized by their default hostname:
* `chuangmi.ir.v2`
* `chuangmi.remote.h102a03`
* `chuangmi.remote.v2`
* `chuangmi.remote.h102c01`
For now, pronto hex codes only work on the first version (`chuangmi.ir.v2`).
## Platform Services
The Xiaomi IR Remote Platform registers four services.
### `remote.send_command`
Allows sending either named commands using an identifier or sending commands as one of the two types defined in [Command Types](/integrations/remote.xiaomi_miio/#command-types).
### `xiaomi_miio.remote_learn_command`
Used to learn new commands.
Use the entity_id of the Xiaomi IR Remote to start a learning process.
`slot` and `timeout` can be specified, but multiple commands learned to the same slot can still be sent using [`remote.send_command`](/integrations/remote.xiaomi_miio/#remotesend_command) even if they are overwritten.
After learning the command the base64 string can be found as a notification in Overview, the string can be copied by left clicking on the string and choose the copy option.
### `xiaomi_miio.remote_set_led_on`
Used to turn remote's blue LED on.
### `xiaomi_miio.remote_set_led_off`
Used to turn remote's blue LED off.

92
source/_integrations/rfxtrx.markdown
View File

@ -235,34 +235,30 @@ The [RFXtrx433e](http://www.rfxcom.com/RFXtrx433E-USB-43392MHz-Transceiver/en) i
The `rfxtrx` platform support lights that communicate in the frequency range of 433.92 MHz.
Make sure you trigger a dimming command to get switches detected as lights otherwise, they will show up as switches.
#### Convert switch event to dimming event
To convert a standard switch to a light, use the [Light Switch](/integrations/light.switch/) component.
To convert a switch to a dimmable light, make sure the event contain a dimming command. You can usually convert a command by changing one byte.
*ARC:*<br>
0b11000248bc0cfe09 **01** 0f70<br>
0b11000248bc0cfe09 **02** 0f70
*LightwaveRF:*<br>
0a14000101f20302 **01** 0080<br>
0a14000101f20302 **10** 0080
*Waveman:*<br>
710030e4102 **01** 50<br>
710030e4102 **02** 50
### Switches
The `rfxtrx` platform support switches that communicate in the frequency range of 433.92 MHz.
#### Generate codes
If you need to generate codes for devices, you can use a template (useful for example for COCO switches).
- Go to home-assistant-IP:8123/dev-template
- Use this code to generate a code:
{% raw %}
```yaml
# for switches
0b11000{{ range(100,700) | random | int }}bc0cfe0{{ range(0,10) | random | int }}010f70
# for dimmers change 010f70 to 020f70 e.g.
0b11000{{ range(100,700) | random | int }}bc0cfe0{{ range(0,10) | random | int }}020f70
```
{% endraw %}
- Use this code to add a new device in your `configuration.yaml`.
- Launch your Home Assistant and go to the website.
- Enable learning mode on your switch (i.e., push learn button or plug it in a wall socket)
- Toggle your new device in the Home Assistant interface
### Sensors
The `rfxtrx` platform support sensors that communicate in the frequency range of 433.92 MHz.
@ -473,7 +469,7 @@ automation:
## Services
- `rftrx.send`: Send a custom event using the RFXtrx device.
- `rfxtrx.send`: Send a custom event using the RFXtrx device.
#### Service: Send
@ -482,7 +478,51 @@ Simulate a button being pressed:
```yaml
...
action:
service: rftrx.send
service: rfxtrx.send
data:
event: 0b1111e003af16aa10000060
```
## Generate codes
If you need to generate codes for switches and lights, you can use a template (useful for example COCO switches).
- Go to home-assistant-IP:8123/dev-template
- Use the follwing codes to generate an event:
*Switch: ARC*
{% raw %}
```yaml
0b11000{{ range(100,700) | random | int }}bc0cfe0{{ range(0,10) | random | int }}010f70
```
{% endraw %}
*Light: ARC*
{% raw %}
```yaml
0b11000{{ range(100,700) | random | int }}bc0cfe0{{ range(0,10) | random | int }}020f70
```
{% endraw %}
*Light: Lightwave RF*
{% raw %}
```yaml
0a14000{{ range(100,700) | random | int }}bc0cf{{ range(0,10) | random | int }}100f70
```
{% endraw %}
- Use this code to add a new switch in your `configuration.yaml`.
- Launch your Home Assistant and go to the website.
- Enable learning mode on your switch (i.e., push learn button or plug it in a wall socket)
- Toggle your new switch in the Home Assistant interface

1
source/_integrations/samsungtv.markdown
View File

@ -130,6 +130,7 @@ For example: for model `UN55NU7100`, the `UN55` would mean it's an LED, North Am
- RU7100
- RU7170
- RU7172
- RU7300 (on works with WOL)
- RU7475
- Q90RATXZT
- QA55Q7FAM

50
source/_integrations/sensor.xiaomi_miio.markdown
View File

@ -1,50 +0,0 @@
---
title: "Xiaomi Air Quality Index Monitor"
description: "Instructions how to integrate your Xiaomi Mi Air Quality Index Monitor within Home Assistant."
ha_category:
- Health
ha_iot_class: Local Polling
ha_release: 0.66
ha_domain: xiaomi_miio
---
The `xiaomi_miio` sensor platform is observing your Xiaomi Mi Air Quality Monitor (PM2.5) and reporting the air quality index.
Currently, the supported features are:
- Air Quality Index (AQI)
- Attributes
- power
- charging
- battery
- time_stat
Please follow the instructions on [Retrieving the Access Token](/integrations/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token.
## Configuration
To add a Xiaomi Mi Air Quality Monitor to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
sensor:
- platform: xiaomi_miio
host: IP_ADDRESS
token: YOUR_TOKEN
```
{% configuration %}
host:
description: The IP address of your miio device.
required: true
type: string
token:
description: The API token of your miio device.
required: true
type: string
name:
description: The name of your miio device.
required: false
type: string
default: Xiaomi Miio Sensor
{% endconfiguration %}

6
source/_integrations/smartthings.markdown
View File

@ -40,11 +40,11 @@ The PAT is used to create a Home Assistant SmartApp in your SmartThings account
1. Log into the [personal access tokens page](https://account.smartthings.com/tokens) and click '[Generate new token](https://account.smartthings.com/tokens/new)'
1. Enter a token name (can be whatever you want), for example, 'Home Assistant' and select the following authorized scopes:
- Devices (all)
- Installed Apps (all)
- Locations (all)
- Installed Applications (all)
- Apps (all)
- Schedules (all)
- Locations (all)
- Scenes (all)
- Schedules (all)
1. Click 'Generate token'. When the token is displayed copy and save it somewhere safe (such as your keystore) as you will not be able to retrieve it again.
### Webhook

123
source/_integrations/switch.xiaomi_miio.markdown
View File

@ -1,123 +0,0 @@
---
title: "Xiaomi Smart WiFi Socket and Smart Power Strip"
description: "Instructions on how to integrate your Xiaomi Smart WiFi Socket aka Plug or Xiaomi Smart Power Strip within Home Assistant."
ha_category:
- Switch
ha_iot_class: Local Polling
ha_release: 0.56
ha_domain: xiaomi_miio
---
The `xiaomi_miio` switch platform allows you to control the state of your Xiaomi Smart WiFi Socket aka Plug, Xiaomi Smart Power Strip and Xiaomi Chuangmi Plug V1.
Please follow the instructions on [Retrieving the Access Token](/integrations/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token to use in the `configuration.yaml` file.
## Features
### Xiaomi Smart WiFi Socket
Supported models: `chuangmi.plug.m1`, `chuangmi.plug.m3`, `chuangmi.plug.v2`, `chuangmi.plug.hmi205`
- Power (on, off)
- Attributes
- Temperature
### Xiaomi Chuangmi Plug V1
Supported models: `chuangmi.plug.v1`, `chuangmi.plug.v3`
- Power (on, off)
- USB (on, off)
- Attributes
- Temperature
### Xiaomi Smart Power Strip
Supported models: `qmi.powerstrip.v1`, `zimi.powerstrip.v2`
- Power (on, off)
- Wifi LED (on, off)
- Power Price (0...999)
- Power Mode (green, normal) (Power Strip V1 only)
- Attributes
- Temperature
- Current
- Load power
- Wifi LED
- Mode (Power Strip V1 only)
### Xiaomi Air Conditioning Companion V3
Supported models: `lumi.acpartner.v3` (the socket of the `acpartner.v1` and `v2` isn't switchable!)
* Power (on, off)
* Attributes
- Load power
## Configuration
To add a plug to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entries
switch:
- platform: xiaomi_miio
host: MIIO_IP_ADDRESS
token: YOUR_TOKEN
```
{% configuration %}
host:
description: The IP address of your miio device.
required: true
type: string
token:
description: The API token of your miio device.
required: true
type: string
name:
description: The name of your miio device.
required: false
type: string
default: Xiaomi Miio Switch
model:
description: The model of your miio device. Valid values are `chuangmi.plug.v1`, `qmi.powerstrip.v1`, `zimi.powerstrip.v2`, `chuangmi.plug.m1`, `chuangmi.plug.m3`, `chuangmi.plug.v2`, `chuangmi.plug.v3` and `chuangmi.plug.hmi205`. This setting can be used to bypass the device model detection and is recommended if your device isn't always available.
required: false
type: string
{% endconfiguration %}
## Platform Services
### Service `xiaomi_miio.switch_set_wifi_led_on` (Power Strip only)
Turn the wifi LED on.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO switch entity. |
### Service `xiaomi_miio.switch_set_wifi_led_off` (Power Strip only)
Turn the wifi LED off.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO switch entity. |
### Service `xiaomi_miio.switch_set_power_price` (Power Strip)
Set the power price.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO switch entity. |
| `price` | no | Power price, between 0 and 999. |
### Service `xiaomi_miio.switch_set_power_mode` (Power Strip V1 only)
Set the power mode.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------------------|
| `entity_id` | no | Only act on a specific Xiaomi miIO switch entity. |
| `mode` | no | Power mode, valid values are 'normal' and 'green' |

480
source/_integrations/vacuum.xiaomi_miio.markdown
View File

@ -1,480 +0,0 @@
---
title: "Xiaomi Mi Robot Vacuum"
description: "Instructions on how to integrate your Xiaomi Mi Robot Vacuum within Home Assistant."
ha_category:
- Vacuum
ha_release: 0.51
ha_iot_class: Local Polling
ha_domain: xiaomi_miio
---
The `xiaomi_miio` vacuum platform allows you to control the state of your [Xiaomi Mi Robot Vacuum](https://www.mi.com/roomrobot/).
Currently supported services are:
- `start`
- `pause`
- `stop`
- `return_to_base`
- `locate`
- `clean_spot`
- `set_fan_speed`
Fan speeds: `Silent`, `Standard`, `Medium`, `Turbo` and `Gentle` (exclusively for mopping).
- `remote_control_*` (of your robot)
- `xiaomi_clean_zone`
## Configuration
Please follow [Retrieving the Access Token](/integrations/vacuum.xiaomi_miio/#retrieving-the-access-token) to retrieve the API token used in
`configuration.yaml`.
To add a vacuum to your installation, add the following to `configuration.yaml`:
```yaml
vacuum:
- platform: xiaomi_miio
host: 192.168.1.2
token: YOUR_TOKEN
```
{% configuration %}
host:
description: The IP address of your robot.
required: true
type: string
token:
description: The API token of your robot.
required: true
type: string
name:
description: The name of your robot.
required: false
type: string
default: Xiaomi Vacuum cleaner
{% endconfiguration %}
## Platform Services
In addition to all of the services provided by the `vacuum` integration (`start`, `pause`, `stop`, `return_to_base`, `locate`, `set_fan_speed` and `send_command`), the `xiaomi_miio` platform introduces specific services to access the remote control mode of the robot. These are:
- `xiaomi_miio.vacuum_remote_control_start`
- `xiaomi_miio.vacuum_remote_control_stop`
- `xiaomi_miio.vacuum_remote_control_move`
- `xiaomi_miio.vacuum_remote_control_move_step`
- `xiaomi_miio.vacuum_clean_zone`
### Service `xiaomi_miio.vacuum_remote_control_start`
Start the remote control mode of the robot. You can then move it with `remote_control_move`; when done, call `remote_control_stop`.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------|
| `entity_id` | no | Only act on a specific robot |
### Service `xiaomi_miio.vacuum_remote_control_stop`
Exit the remote control mode of the robot.
| Service data attribute | Optional | Description |
|---------------------------|----------|---------------------------------------------------|
| `entity_id` | no | Only act on a specific robot |
### Service `xiaomi_miio.vacuum_remote_control_move`
Remote control the robot. Please ensure you first set it in remote control mode with `remote_control_start`.
| Service data attribute | Optional | Description |
|---------------------------|----------|-----------------------------------------------------------|
| `entity_id` | no | Only act on a specific robot |
| `velocity` | no | Speed: between -0.29 and 0.29 |
| `rotation` | no | Rotation: between -179 degrees and 179 degrees |
| `duration` | no | The number of milliseconds that the robot should move for |
### Service `xiaomi_miio.vacuum_remote_control_move_step`
Enter remote control mode, make one move, stop, and exit remote control mode.
| Service data attribute | Optional | Description |
|---------------------------|----------|-----------------------------------------------------------|
| `entity_id` | no | Only act on a specific robot |
| `velocity` | no | Speed: between -0.29 and 0.29 |
| `rotation` | no | Rotation: between -179 degrees and 179 degrees |
| `duration` | no | The number of milliseconds that the robot should move for |
### Service `xiaomi_miio.vacuum_clean_zone`
Start the cleaning operation in the areas selected for the number of repeats indicated.
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | no | Only act on a specific robot |
| `zone` | no | List of zones. Each zone is an array of 4 integer value. Example: [[23510,25311,25110,26361]] |
| `repeats` | no | Number of cleaning repeats for each zone between 1 and 3. |
Example of `xiaomi_miio.vacuum_clean_zone` use:
Inline array:
{% raw %}
```yaml
automation:
- alias: Test vacuum zone3
trigger:
- event: start
platform: homeassistant
condition: []
action:
- service: xiaomi_miio.vacuum_clean_zone
data_template:
entity_id: vacuum.xiaomi_vacuum
repeats: '{{states('input_number.vacuum_passes')|int}}'
zone: [[30914,26007,35514,28807], [20232,22496,26032,26496]]
```
{% endraw %}
Array with inline zone:
{% raw %}
```yaml
automation:
- alias: Test vacuum zone3
trigger:
- event: start
platform: homeassistant
condition: []
action:
- service: xiaomi_miio.vacuum_clean_zone
data_template:
entity_id: vacuum.xiaomi_vacuum
repeats: '{{states('input_number.vacuum_passes')|int}}'
zone:
- [30914,26007,35514,28807]
- [20232,22496,26032,26496]
```
{% endraw %}
Array mode:
```yaml
automation:
- alias: Test vacuum zone3
trigger:
- event: start
platform: homeassistant
condition: []
action:
- service: xiaomi_miio.vacuum_clean_zone
data:
entity_id: vacuum.xiaomi_vacuum
repeats: 1
zone:
- - 30914
- 26007
- 35514
- 28807
- - 20232
- 22496
- 26032
- 26496
```
### Service `xiaomi_miio.vacuum_goto`
Go the specified coordinates
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | no | Only act on a specific robot |
| `x_coord` | no | X-coordinate, integer value. The dock is located at x-coordinate 25500. |
| `y_coord` | no | Y-coordinate, integer value. The dock is located at y-coordinate 25500. |
### Service `xiaomi_miio.vacuum_clean_segment`
Clean the specified segment/room. A room is identified by a number. Instructions on how to find the valid room numbers and determine what rooms they map to, read the section [Retrieving room numbers](#retrieving-room-numbers).
| Service data attribute | Optional | Description |
|---------------------------|----------|-------------------------------------------------------|
| `entity_id` | no | Only act on a specific robot |
| `segments` | no | List of segment numbers or one single segment number. |
Example of `xiaomi_miio.vacuum_clean_segment` use:
Multiple segments:
```yaml
automation:
- alias: Vaccum kitchen and living room
trigger:
- event: start
platform: homeassistant
condition: []
action:
- service: xiaomi_miio.vacuum_clean_segment
data:
entity_id: vacuum.xiaomi_vacuum
segments: [1,2]
```
Single segment:
```yaml
automation:
- alias: Vacuum kitchen
trigger:
- event: start
platform: homeassistant
condition: []
action:
- service: xiaomi_miio.vacuum_clean_segment
data:
entity_id: vacuum.xiaomi_vacuum
segments: 1
```
## Attributes
In addition to [all of the attributes provided by the `vacuum` component](/integrations/vacuum/#attributes),
(`battery_icon`, `cleaned_area`, `fan_speed`, `fan_speed_list`, and `params`), the `xiaomi` platform introduces specific attributes. These are:
- `cleaning_time`
- `do_not_disturb`
- `main_brush_left`
- `side_brush_left`
- `filter_left`
- `sensor_dirty_left`
- `cleaning_count`
- `total_cleaned_area`
- `total_cleaning_time`
- `clean_start`
- `clean_end`
The following table shows the units of measurement for each attribute:
| Attribute | Unit of measurement | Description |
|---------------------------|---------------------|----------------------------------------------------------------|
| `do_not_disturb` | | DND mode on / off |
| `cleaning_time` | minutes | Last / actual cleaning time in minutes |
| `cleaned_area` | square meter | Last / actual cleaned area in square meters |
| `main_brush_left` | hours | Hours left until a change of the main brush is needed |
| `side_brush_left` | hours | Hours left until a change of the side brush is needed |
| `filter_left` | hours | Hours left until a change of the filter is needed |
| `sensor_dirty_left` | hours | Hours left until the wall and cliff sensors should be cleaned |
| `cleaning_count` | | Number of total cleaning cycles |
| `total_cleaned_area` | square meter | Total cleaned area in square meters |
| `total_cleaning_time` | minutes | Total cleaning time in minutes |
| `clean_start` | datetime | The last date/time the vacuum started cleaning (offset naive) |
| `clean_end` | datetime | The last date/time the vacuum finished cleaning (offset naive) |
## Retrieving the Access Token
### Xiaomi Home app (Xiaomi Aqara Gateway, Android & iOS)
1. Install the Xiaomi Home app.
2. Sign In/make an account.
3. Make sure you set your region to: Mainland China (Seems to be the longest line with Chines characters) under settings -> Region (language can later be set on English).
4. Select your Gateway in Xiaomi Home app.
5. Then the 3 dots at the top right of the screen.
6. Then click on about.
7. Tap the version number (Plug-in version 2.77.1 as of January 2020, iOS has a white space instead of version number) at the bottom of the screen repeatedly.
8. You should now see 2 extra options listed in English (iOS still in Chinese), this means you enabled developer mode. [if not, try all steps again!].
9. Android: under "Hub info" there is quite some text in JSON format, this includes the "token" that you need.
iOS: Most options are still in Chinese, you need the fourth item from the top.
Note: If you have multiple devices needing a token, e.g., Xiaomi Mi Robot Vacuum and a Xiaomi IR Remote, the above method may not work. The Xiaomi Home app will display a token, though it isn't the correct one. The alternative method using "Mi Home v5.4.49" will provide the correct token.
### Alternative methods
<div class='note'>
If using an Android device to retrieve the Access Token only `v5.4.49` of Mi Home is confirmed working (December 2019). Use `v5.4.49` of Mi Home locate a text file under the `Smarthome/logs` folder where the 32 character token is stored. There will likely be several text files in this directory, search all of them for the word 'token' and you should find it there. Be advised that the latest version of Mi Home does not store the token in clear text.
<br/> <br/>
The iPhone app still stores the token in the SQLite db as of `v4.23.4` (Nov 17, 2019).
<br/> <br/>
After resetting the Wi-Fi settings of the Xiaomi robot vacuum, a new Access Token will be generated and therefore these instructions need to be followed again.
<br/> <br/>
These instructions are written for the Mi Home app - not for the new RoboRock app.
<br/> <br/>
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.
</div>
### Android (not rooted)
> If using an Android device to retrieve the Access Token only `v5.4.49` of Mi Home is confirmed working (December 2019).
1. To begin, set up your Robovac with the latest version of Mi Home on your primary Android device as you normally would.
2. If your Robovac is already set up, you must reset its WiFi settings for it to get a new token.
3. Using `v5.4.49` of Mi Home locate a text file under the `Smarthome/logs` folder where the 32 character token is stored.
4. There will likely be several text files in this directory, search all of them for the word 'token' and you should find it there. Be advised that the latest version of Mi Home does not store the token in clear text.
### Linux and Rooted Android
1. To begin, set up your Robovac with the latest version of Mi Home on your primary Android device as you normally would.
2. Ensure successful operation using the latest Mi Home app and give the Vacuum a static IP in your router or however you do that on your LAN.
3. Install version `v5.4.54` of Mi Home on your rooted Android device and login (you can't have two version of Mi Home installed at the same time).
4. Ensure you are using the same server every time
5. Ensure successful operation using 5.4.54 (locate is a nice simple test)
6. Using adb we will now extract the token from the rooted phone
7. Use adb shell to connect to your device and become root (if using Magisck root do `adb shell -> su -> whoami` to ensure root access.
8. Then run grep -R '"token"' /data/data/com.xiaomi.smarthome and grab the token
### iOS
1. Configure the robot with the Mi Home app. Make sure to select the correct region, as Xiaomi uses different product names for different geographical areas. Note that the new RoboRock app is currently not supported for this method.
2. Using iTunes, create an unencrypted backup of your iPhone. Since macOS 10.15 there is no iTunes app. Use Finder instead - after connecting your iOS device you should see it in left menu of Finder window.
3. Install [iBackup Viewer](https://www.imactools.com/iphonebackupviewer/), open it, and open your backup.
4. Open the "Raw Data" module.
5. Navigate to `com.xiaomi.mihome`.
6. Search for a file that looks like this: `123456789_mihome.sqlite` (Note: `_mihome.sqlite` is *not* the correct file. Most likely, you will find this file in the `Documents` folder.)
7. Save this file to your filesystem.
8. Install [DB Browser for SQLite](https://sqlitebrowser.org/).
9. Open DB Browser and load the `.sqlite` file you saved from your backup.
10. Click on the `Execute SQL` tab.
11. Input and run this query (use appropriate SELECT query for your device i.e. Vacuum, Powerstrip or Plug):
```sql
-- Execute to retrieve token for Vacuum
SELECT ZTOKEN FROM ZDEVICE WHERE ZMODEL LIKE "%vacuum%"
-- Execute to retrieve token for Smart Powerstrip
SELECT ZTOKEN FROM ZDEVICE WHERE ZMODEL LIKE "%powerstrip%"
-- Execute to retrieve token for Smart Plug
SELECT ZTOKEN FROM ZDEVICE WHERE ZMODEL LIKE "%plug%"
```
12. Copy the returned 96-digit hexadecimal string to your clipboard.
13. Open `Terminal` and execute this command:
```bash
echo '0: <YOUR HEXADECIMAL STRING>' | xxd -r -p | openssl enc -d -aes-128-ecb -nopad -nosalt -K 00000000000000000000000000000000
```
14. Use the resulting 32-digit string as your token. (On your mac in front of the terminal session)
### Bluestacks
1. Configure the robot with the Mi-Home app. Make sure to select the correct region, as Xiaomi uses different product names for different geographical areas. Note that the new RoboRock app is currently not supported for this method.
2. Install [BlueStacks](https://www.bluestacks.com).
3. Set up [Mi Home version 5.4.49](https://www.apkmirror.com/apk/xiaomi-inc/mihome/mihome-5-4-49-release/) in BlueStacks and login to synchronize devices.
4. Open Filemanager in the `More Apps` menu.
5. Use `Explore` on the left and navigate to `sdcard/SmartHome/logs/plug_DeviceManager`.
6. Click on `Export to Windows` in the lower left corner and select any or all files to export to you local disk.
7. Search for `"token":"<yourTokenHere>"`.
### Miio command line tool
Use of Miio should be done before the Vacuum is connected to Mi Home. If you already connected to the app you will need to delete it and then join the ad-hoc Wi-Fi network the Vacuum creates. If the vacuum is already paired it's likely this method will only return `???` as your token.
You can install the command line tool using the following command:
```bash
npm install -g miio
```
Discovering devices on the current network:
```bash
miio discover
```
This will list devices that are connected to the same network as your computer. Let it run for a while so it has a chance to reach all devices, as it might take a minute or two for all devices to answer.
The commands outputs each device on this format:
```text
Device ID: 48765421
Model info: zhimi.airpurifier.m1
Address: 192.168.100.9
Token: token-as-hex-here via auto-token
Support: At least basic
```
The information output is:
- `Device ID` - The unique identifier of the device, does not change if the device is reset.
- `Model ID`- The model id if it could be determined, this indicates what type of device it is.
- `Address` - The IP that the device has on the network.
- `Token` - The token of the device or `???` if it could not be automatically determined.
## Example on how to clean a specific room
Example script using [`vacuum.send_command`](/integrations/vacuum/) to clean a specific room:
```yaml
vacuum_kitchen:
alias: "Clean the kitchen"
sequence:
- service: vacuum.send_command
data:
entity_id: vacuum.xiaomi_vacuum_cleaner
command: app_segment_clean
params: [18]
```
Where params specify room numbers, for multiple rooms, params can be specified like `[17,18]`. Instructions on how to find the valid room numbers and determine what rooms they map to, read the section [Retrieving room numbers](#retrieving-room-numbers).
## Example on how to reset maintenance hours (brushes, filter, sensors)
The vacuum entity stores attribute values for when brushes, filters and sensors need to be
cleaned or replaced (`main_brush_left`, `side_brush_left`, `filter_left` and
`sensor_dirty_left`). The values are measured in hours. Once the parts are cleaned
or replaced you can then reset those values on the vacuum. Here is an example script using
[`vacuum.send_command`](/integrations/vacuum/) to reset the hours for the main brush:
```yaml
reset_main_brush_left:
alias: "Reset hours for main brush replacement"
sequence:
- service: vacuum.send_Command
data:
entity_id: vacuum.xiaomi_vacuum_cleaner
command: reset_consumable
params: ['main_brush_work_time']
```
Allowed `params` for the `reset_consumable` command:
* `['main_brush_work_time']`
* `['side_brush_work_time']`
* `['filter_work_time']`
* `['sensor_dirty_time']`
## Retrieving Zoned Cleaning Coordinates
### Using FloleVac (Android)
1. Download [FloleVac](https://play.google.com/store/apps/details?id=de.flole.xiaomi)
2. Login with your Xiaomi credentials
3. Open Map (make sure you're on the same network as your vacuum cleaner)
4. Select "Zone cleanup" and draw a box around the zone you'd like to clean
5. Long press "Cleanup" and the zone coordinates will be copied to your clipboard
### Using RoboRock Control Center (requires Valetudo firmware)
[RRCC](https://github.com/LazyT/rrcc) supports both rooted and non-rooted Vacuums and acts as a mostly fully featured replacement for Mi Home that works locally without the cloud. If you have installed the rooted firmware [Valetudo](https://github.com/Hypfer/Valetudo) you are able to SSH into your Vacuum and enable MQTT plus use map functions with no cloud requirement.
Using the map editor you are able to acquire the co-ordinates required for zoned clean up. Here is an example script for zoned clean up:
```yaml
vacuum_kitchen:
alias: "vacuum kitchen"
sequence:
- service: vacuum.send_command
data:
entity_id: 'vacuum.xiaomi_vacuum_cleaner'
command: app_zoned_clean
params: [[23084,26282,27628,29727,1]]
```
## Retrieving Room numbers
Valid room numbers can be retrieved using miio command-line tool:
```bash
miio protocol call <ip of the vacuum> 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 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.

2
source/_integrations/workday.markdown
View File

@ -40,7 +40,7 @@ country:
required: true
type: string
province:
description: Province code according to [holidays](https://pypi.org/project/holidays/) notation.
description: Province/State code according to [holidays](https://pypi.org/project/holidays/) notation.
required: false
type: string
workdays:

1725
source/_integrations/xiaomi_miio.markdown
View File

File diff suppressed because it is too large Load Diff

4
source/_integrations/zha.markdown
View File

@ -55,6 +55,7 @@ ZHA integration uses a hardware independent Zigbee stack implementation with mod
- [RaspBee II (a.k.a. RaspBee 2) Raspberry Pi Shield from dresden elektronik](https://www.dresden-elektronik.com/product/raspbee-II.html)
- [RaspBee Raspberry Pi Shield from dresden elektronik](https://phoscon.de/raspbee)
- EmberZNet based radios using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy)
- [ITEAD Sonoff ZBBridge](https://www.itead.cc/smart-home/sonoff-zbbridge.html) (Note! This first have to be flashed with [Tasmota firmware and EmberZNet 6.5.x.x](https://www.digiblur.com/2020/07/how-to-use-sonoff-zigbee-bridge-with.html))
- [Nortek GoControl QuickStick Combo Model HUSBZB-1 (Z-Wave & Zigbee USB Adapter)](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/)
- [Elelabs Zigbee USB Adapter](https://elelabs.com/products/elelabs_usb_adapter.html)
- [Elelabs Zigbee Raspberry Pi Shield](https://elelabs.com/products/elelabs_zigbee_shield.html)
@ -120,11 +121,12 @@ eg `/dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_C0F003D3-if01-
Press `Submit` The success dialog will appear or an error will be displayed in the popup. An error is likely if Home Assistant can't access the USB device or your device is not up to date. Refer to [Troubleshooting](#troubleshooting) below for more information.
If you are use ZiGate, you have to use some special usb_path configuration:
If you are use ZiGate or Sonoff ZBBridge you have to use some special usb_path configuration:
- ZiGate USB TTL or DIN: `/dev/ttyUSB0` or `auto` to auto discover the zigate
- PiZigate : `pizigate:/dev/serial0`
- Wifi Zigate : `socket://[IP]:[PORT]` for example `socket://192.168.1.10:9999`
- Sonoff ZBBridge : `socket://[IP]:[PORT]` for example `socket://192.168.1.11:8888`
{% configuration %}
database_path:

2
source/_lovelace/picture-elements.markdown
View File

@ -19,7 +19,7 @@ type:
description: picture-elements
type: string
image:
required: false
required: true
description: The URL of an image.<br/>To use a locally hosted image, see [Hosting](/integrations/http#hosting-files).
type: string
camera_image:

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

@ -63,7 +63,7 @@ show_forecast:
secondary_info_attribute:
required: false
description: Which attribute to display under the temperature.
type: boolean
type: string
default: Defaults to `extrema` if available, if not available then `precipitation` and if precipitation isn't available then `humidity`.
theme:
required: false

220
source/_posts/2020-07-01-release-113.markdown
View File

@ -234,20 +234,20 @@ automation:
- binary_sensor.button3
action:
- choose:
- conditions:
- condition: state
entity_id: binary_sensor.button1
state: "on"
sequence:
- service: light.turn_on
entity_id: light.bulb
- conditions:
- condition: state
entity_id: binary_sensor.button2
state: "on"
sequence:
- service: light.turn_off
entity_id: light.bulb
- conditions:
- condition: state
entity_id: binary_sensor.button1
state: "on"
sequence:
- service: light.turn_on
entity_id: light.bulb
- conditions:
- condition: state
entity_id: binary_sensor.button2
state: "on"
sequence:
- service: light.turn_off
entity_id: light.bulb
default:
- service: notify.frenck
data:
@ -283,10 +283,10 @@ script:
repeat:
count: 10
sequence:
- service: light.toggle
entity_id: light.bulb
- delay:
milliseconds: 500
- service: light.toggle
entity_id: light.bulb
- delay:
milliseconds: 500
```
### Automations & Scripts: Bonus! Cool down
@ -674,12 +674,12 @@ instead of being delayed until the activity is finished setting up.
<summary><b>Xiaomi Miio</b></summary>
<p>
Fan and remote components now have unique LED strings.
If you had previously set your automation calls from
"**fan**_set_led_on/off" to "**remote**_set_led_on/off",
you will now need to set those back to "fan".
Fan and remote components now have unique LED strings.
If you had previously set your automation calls from
"**fan**\_set_led_on/off" to "**remote**\_set_led_on/off",
you will now need to set those back to "fan".
([@alexhardwicke] - [#37605]) ([xiaomi_miio docs])
([@alexhardwicke] - [#37605]) ([xiaomi_miio docs])
</p>
</details>
@ -691,6 +691,7 @@ instead of being delayed until the activity is finished setting up.
Syncthru configuration is now done through the integrations UI page.
([@scop] - [#36690]) ([discovery docs]) ([syncthru docs])
</p>
</details>
@ -718,7 +719,7 @@ the Slack integration documentation.
- The events signalled from entity id's are removed in favor of events from an integration level.
- The events format has changed.
([@elupus] - [#37742] [#37565]) ([rfxtrx docs])
([@elupus] - [#37742][#37565]) ([rfxtrx docs])
</p>
</details>
@ -747,8 +748,8 @@ component instead of JavaScript. That's why we have always supported importing
extra HTML in the frontend and custom panels.
This has been deprecated and superseded by ES modules since some time and has
no support anymore in browsers. We have a polyfill in place to still support
this, but we are going to remove this.
no support anymore in browsers. We have a polyfill in place to still support
this, but we are going to remove this.
In version 0.115 we will remove the ability to import HTML, you can use ES
modules as a replacement.
@ -802,16 +803,16 @@ In general, all variables that start with `paper` will be removed at some point.
[#38149]: https://github.com/home-assistant/core/pull/38149
[#38159]: https://github.com/home-assistant/core/pull/38159
[#38163]: https://github.com/home-assistant/core/pull/38163
[@DubhAd]: https://github.com/DubhAd
[@JeffLIrion]: https://github.com/JeffLIrion
[@RobBie1221]: https://github.com/RobBie1221
[@dubhad]: https://github.com/DubhAd
[@jefflirion]: https://github.com/JeffLIrion
[@robbie1221]: https://github.com/RobBie1221
[@andrewsayre]: https://github.com/andrewsayre
[@bachya]: https://github.com/bachya
[@balloob]: https://github.com/balloob
[@bdraco]: https://github.com/bdraco
[@frenck]: https://github.com/frenck
[@ludeeus]: https://github.com/ludeeus
[@mKeRix]: https://github.com/mKeRix
[@mkerix]: https://github.com/mKeRix
[@pnbruckner]: https://github.com/pnbruckner
[@pschmitt]: https://github.com/pschmitt
[androidtv docs]: /integrations/androidtv/
@ -824,6 +825,123 @@ In general, all variables that start with `paper` will be removed at some point.
[toon docs]: /integrations/toon/
[xbox_live docs]: /integrations/xbox_live/
## Release 0.113.2 - July 28
- Bump netdisco to 2.8.1 ([@bdraco] - [#38173]) ([discovery docs])
- Stop automation runs when turned off or reloaded ([@pnbruckner] - [#38174]) ([automation docs])
- Bump tesla-powerwall to 0.2.12 to handle powerwall firmware 1.48+ ([@bdraco] - [#38180]) ([powerwall docs])
- Ignore harmony hubs ips that are already configured during ssdp discovery ([@bdraco] - [#38181]) ([harmony docs])
- Fix detection of zones 2 and 3 in Onkyo/Pioneer amplifiers ([@vdkeybus] - [#38234]) ([onkyo docs])
- Fix repeat action when variables present ([@pnbruckner] - [#38237]) ([script docs])
- Fix parallel script containing repeat or choose action with max_runs > 10 ([@pnbruckner] - [#38243]) ([automation docs]) ([script docs])
- Fix Skybell useragent ([@MisterWil] - [#38245]) ([skybell docs])
- Improve setup retry logic to handle inconsistent powerview hub availability ([@bdraco] - [#38249]) ([hunterdouglas_powerview docs])
- Don't set up callbacks until entity is created. ([@pavoni] - [#38251]) ([vera docs])
- Prevent onvif from blocking startup ([@bdraco] - [#38256]) ([onvif docs])
- Fix #38289 issue with xboxapi lib ([@marciogranzotto] - [#38293]) ([xbox_live docs])
- Bump python-miio to 0.5.3 ([@rytilahti] - [#38300]) ([xiaomi_miio docs])
- Prevent speedtest from blocking startup or causing other intergations to fail setup ([@bdraco] - [#38305]) ([speedtestdotnet docs])
- Fix issue with certain Samsung TVs repeatedly showing auth dialog ([@kylehendricks] - [#38308]) ([samsungtv docs])
- Add debug logging for when a chain of tasks blocks startup ([@bdraco] - [#38311])
- Remove AdGuard version check ([@frenck] - [#38326]) ([adguard docs])
[#38173]: https://github.com/home-assistant/core/pull/38173
[#38174]: https://github.com/home-assistant/core/pull/38174
[#38180]: https://github.com/home-assistant/core/pull/38180
[#38181]: https://github.com/home-assistant/core/pull/38181
[#38234]: https://github.com/home-assistant/core/pull/38234
[#38237]: https://github.com/home-assistant/core/pull/38237
[#38243]: https://github.com/home-assistant/core/pull/38243
[#38245]: https://github.com/home-assistant/core/pull/38245
[#38249]: https://github.com/home-assistant/core/pull/38249
[#38251]: https://github.com/home-assistant/core/pull/38251
[#38256]: https://github.com/home-assistant/core/pull/38256
[#38293]: https://github.com/home-assistant/core/pull/38293
[#38300]: https://github.com/home-assistant/core/pull/38300
[#38305]: https://github.com/home-assistant/core/pull/38305
[#38308]: https://github.com/home-assistant/core/pull/38308
[#38311]: https://github.com/home-assistant/core/pull/38311
[#38326]: https://github.com/home-assistant/core/pull/38326
[@misterwil]: https://github.com/MisterWil
[@bdraco]: https://github.com/bdraco
[@frenck]: https://github.com/frenck
[@kylehendricks]: https://github.com/kylehendricks
[@marciogranzotto]: https://github.com/marciogranzotto
[@pavoni]: https://github.com/pavoni
[@pnbruckner]: https://github.com/pnbruckner
[@rytilahti]: https://github.com/rytilahti
[@vdkeybus]: https://github.com/vdkeybus
[adguard docs]: /integrations/adguard/
[automation docs]: /integrations/automation/
[discovery docs]: /integrations/discovery/
[harmony docs]: /integrations/harmony/
[hunterdouglas_powerview docs]: /integrations/hunterdouglas_powerview/
[onkyo docs]: /integrations/onkyo/
[onvif docs]: /integrations/onvif/
[powerwall docs]: /integrations/powerwall/
[rfxtrx docs]: /integrations/rfxtrx/
[samsungtv docs]: /integrations/samsungtv/
[script docs]: /integrations/script/
[skybell docs]: /integrations/skybell/
[speedtestdotnet docs]: /integrations/speedtestdotnet/
[vera docs]: /integrations/vera/
[xbox_live docs]: /integrations/xbox_live/
[xiaomi_miio docs]: /integrations/xiaomi_miio/
## Release 0.113.3 - August 1
- Add Abode camera on and off support ([@shred86] - [#35164]) ([abode docs])
- Fix songpal already configured check in config flow ([@shenxn] - [#37813]) ([songpal docs])
- Prevent kodi from blocking startup ([@bdraco] - [#38257]) ([kodi docs])
- Ignore remote Plex clients during plex.tv lookup ([@jjlawren] - [#38327]) ([plex docs])
- Bump androidtv to 0.0.47 and adb-shell to 0.2.1 ([@JeffLIrion] - [#38344]) ([androidtv docs])
- Bump pychromecast to 7.2.0 ([@emontnemery] - [#38351]) ([cast docs])
- Update aioharmony to 0.2.6 ([@ehendrix23] - [#38360]) ([harmony docs])
- Avoid error with ignored harmony config entries ([@bdraco] - [#38367]) ([harmony docs])
- Prevent nut config flow error when checking ignored entries ([@bdraco] - [#38372]) ([nut docs])
- Ensure Toon webhook ID isn't registered on re-registration ([@frenck] - [#38376]) ([toon docs])
- Fix rmvtransport breaking when destinations don't match ([@cgtobi] - [#38401]) ([rmvtransport docs])
- Fix ads integration after 0.113 ([@stlehmann] - [#38402]) ([ads docs])
- Pin yarl dependency to 1.4.2 as core dependency ([@frenck] - [#38428])
- Fix double encoding issue in google_translate TTS ([@frenck] - [#38429]) ([google_translate docs])
[#35164]: https://github.com/home-assistant/core/pull/35164
[#37813]: https://github.com/home-assistant/core/pull/37813
[#38257]: https://github.com/home-assistant/core/pull/38257
[#38327]: https://github.com/home-assistant/core/pull/38327
[#38344]: https://github.com/home-assistant/core/pull/38344
[#38351]: https://github.com/home-assistant/core/pull/38351
[#38360]: https://github.com/home-assistant/core/pull/38360
[#38367]: https://github.com/home-assistant/core/pull/38367
[#38372]: https://github.com/home-assistant/core/pull/38372
[#38376]: https://github.com/home-assistant/core/pull/38376
[#38401]: https://github.com/home-assistant/core/pull/38401
[#38402]: https://github.com/home-assistant/core/pull/38402
[#38428]: https://github.com/home-assistant/core/pull/38428
[#38429]: https://github.com/home-assistant/core/pull/38429
[@jefflirion]: https://github.com/JeffLIrion
[@bdraco]: https://github.com/bdraco
[@cgtobi]: https://github.com/cgtobi
[@ehendrix23]: https://github.com/ehendrix23
[@emontnemery]: https://github.com/emontnemery
[@frenck]: https://github.com/frenck
[@jjlawren]: https://github.com/jjlawren
[@shenxn]: https://github.com/shenxn
[@shred86]: https://github.com/shred86
[@stlehmann]: https://github.com/stlehmann
[abode docs]: /integrations/abode/
[ads docs]: /integrations/ads/
[androidtv docs]: /integrations/androidtv/
[cast docs]: /integrations/cast/
[google_translate docs]: /integrations/google_translate/
[harmony docs]: /integrations/harmony/
[kodi docs]: /integrations/kodi/
[nut docs]: /integrations/nut/
[plex docs]: /integrations/plex/
[rmvtransport docs]: /integrations/rmvtransport/
[songpal docs]: /integrations/songpal/
[toon docs]: /integrations/toon/
## All changes
<details>
@ -1463,26 +1581,26 @@ In general, all variables that start with `paper` will be removed at some point.
[#38043]: https://github.com/home-assistant/core/pull/38043
[#38049]: https://github.com/home-assistant/core/pull/38049
[#38057]: https://github.com/home-assistant/core/pull/38057
[@2Fake]: https://github.com/2Fake
[@Adminiuga]: https://github.com/Adminiuga
[@CoMPaTech]: https://github.com/CoMPaTech
[@DarkFox]: https://github.com/DarkFox
[@GMTA]: https://github.com/GMTA
[@Harryjholmes]: https://github.com/Harryjholmes
[@InduPrakash]: https://github.com/InduPrakash
[@Jc2k]: https://github.com/Jc2k
[@JeffLIrion]: https://github.com/JeffLIrion
[@Kdemontf]: https://github.com/Kdemontf
[@MartinHjelmare]: https://github.com/MartinHjelmare
[@MatthewFlamm]: https://github.com/MatthewFlamm
[@Michsior14]: https://github.com/Michsior14
[@PaulAnnekov]: https://github.com/PaulAnnekov
[@Quentame]: https://github.com/Quentame
[@RogerSelwyn]: https://github.com/RogerSelwyn
[@SeraphimSerapis]: https://github.com/SeraphimSerapis
[@Shulyaka]: https://github.com/Shulyaka
[@SukramJ]: https://github.com/SukramJ
[@TheLastGimbus]: https://github.com/TheLastGimbus
[@2fake]: https://github.com/2Fake
[@adminiuga]: https://github.com/Adminiuga
[@compatech]: https://github.com/CoMPaTech
[@darkfox]: https://github.com/DarkFox
[@gmta]: https://github.com/GMTA
[@harryjholmes]: https://github.com/Harryjholmes
[@induprakash]: https://github.com/InduPrakash
[@jc2k]: https://github.com/Jc2k
[@jefflirion]: https://github.com/JeffLIrion
[@kdemontf]: https://github.com/Kdemontf
[@martinhjelmare]: https://github.com/MartinHjelmare
[@matthewflamm]: https://github.com/MatthewFlamm
[@michsior14]: https://github.com/Michsior14
[@paulannekov]: https://github.com/PaulAnnekov
[@quentame]: https://github.com/Quentame
[@rogerselwyn]: https://github.com/RogerSelwyn
[@seraphimserapis]: https://github.com/SeraphimSerapis
[@shulyaka]: https://github.com/Shulyaka
[@sukramj]: https://github.com/SukramJ
[@thelastgimbus]: https://github.com/TheLastGimbus
[@aaliddell]: https://github.com/aaliddell
[@abmantis]: https://github.com/abmantis
[@ajschmidt8]: https://github.com/ajschmidt8
@ -1549,7 +1667,7 @@ In general, all variables that start with `paper` will be removed at some point.
[@shenxn]: https://github.com/shenxn
[@shermdog]: https://github.com/shermdog
[@smugleafdev]: https://github.com/smugleafdev
[@starkillerOG]: https://github.com/starkillerOG
[@starkillerog]: https://github.com/starkillerOG
[@teharris1]: https://github.com/teharris1
[@timmo001]: https://github.com/timmo001
[@timvancann]: https://github.com/timvancann

35
source/_posts/2020-07-28-ios-app-migration.markdown Normal file
View File

@ -0,0 +1,35 @@
---
title: "Migrating the iOS Companion App to Nabu Casa"
description: "Overview of why we are changing the app's author and what you need to do"
date: 2020-07-28 00:00:00
date_formatted: "July 28, 2020"
comments: false
author: Robbie Trencheny
author_twitter: robbie
categories: Announcements
og_image: /images/blog/2020-07-28-ios-app-migration/social-update.png
---
Hi there, your friend and pal, Robbie the iOS developer here with an important update about a change to the Home Assistant Companion App for iOS and a few steps you, the user, will need to take.
## What's changing?
Recently, I transferred the Home Assistant app from my personal Apple Developer account to a new Apple Developer account owned by Nabu Casa, Inc. Why? Because Apple has silly limits on individual accounts that have made collaboration with others near impossible for the entire lifespan of the app (please don’t tell Tim or Craig I called their limits silly). This meant that during times when my work or personal life have been very busy, app updates have been far less frequent than I wanted. These limits also make it such that, if I were to be hit by a bus tomorrow, the app couldn't be easily updated on the App Store by others. The business account does not have these limits. Anyone on the account can update the app anytime without relying on me, Robbie, to push buttons. This will make collaboration easier and ensure the app will be available forever and ever, long after I’m gone.
## Why Nabu Casa?
Why did we transfer it to Nabu Casa, Inc.? Why not Home Assistant, Inc.? The short answer is there is no Home Assistant, Inc. Apple requires that business accounts are owned by… businesses. Real businesses. Which Home Assistant is not. Nabu Casa was the best option. To be very clear, Nabu Casa does not own the app now. The copyright and license has not changed. It’s still entirely open source. I am not stopping my work on the app, neither are others. Nabu Casa is simply the account under which the app is published. The same rock solid privacy guarantees apply just as before. The only change visible to you will be the name shown as the author in the App Store (Nabu Casa, Inc instead of Robert Trencheny).
## Does this mean there will be a charge for the app?
No.
## What do you need to do?
Right now, we are waiting for Apple to approve the entitlement to send [Critical Notifications](https://companion.home-assistant.io/docs/notifications/critical-notifications) for the new account. When that is done we will release an update (version 2020.5) from the new business account. Due to Apple limits, after updating you are going to need to re-authenticate one time to continue using the app. After that (assuming everything works) you are all done and the app will keep functioning as normal. No integration changes, no push notification changes, your actions are still there, etc etc. Remember that depending on your device settings, this update may well happen automatically, that's why we're telling you all about this in advance.
## When is this happening?
We're not quite sure about this sadly, currently we don't expect it to be before August 10th. As I mentioned, we are waiting for the new business account to be granted the critical notification entitlement. The time frame for this is entirely governed by Apple and beyond our control. We will be sure to keep you updated via [Twitter](https://twitter.com/home_assistant) and [Facebook](https://www.facebook.com/homeassistantio) so make sure you follow us! The current version of the app will also send a push notification closer to the time. We are currently working with our awesome team of translators to get this translated along with the in-app instructions that will be included in the 2020.5 update.
Thanks as always for being a Home Assistant Companion user. Please leave a review if you appreciate the app, it’s the fuel that keeps the fire burning.

8
source/_redirects
View File

@ -1080,6 +1080,14 @@
/components/weather.smhi /integrations/smhi
/components/weather.zamg /integrations/zamg#weather
/components/xiaomi /integrations/xiaomi_aqara
/integrations/air_quality.xiaomi_miio /integrations/xiaomi_miio
/integrations/alarm_control_panel.xiaomi_miio /integrations/xiaomi_miio
/integrations/fan.xiaomi_miio /integrations/xiaomi_miio
/integrations/light.xiaomi_miio /integrations/xiaomi_miio
/integrations/remote.xiaomi_miio /integrations/xiaomi_miio
/integrations/sensor.xiaomi_miio /integrations/xiaomi_miio
/integrations/switch.xiaomi_miio /integrations/xiaomi_miio
/integrations/vacuum.xiaomi_miio /integrations/xiaomi_miio
# Renaming components to integrations
/components /integrations

58
source/hassio/hassos_faq.markdown Normal file
View File

@ -0,0 +1,58 @@
---
title: "Home Assistant OS FAQ"
description: "Frequently Asked Questions for Home Assistant OS"
---
## Is USB Boot for the Pi4 supported? Is the Pi4 with 8GB RAM supported?
The bootloader for Home Assistant OS (uboot) does not yet support Pi4 booting from USB. Support is likely a month or two away as of July 2020.
The Pi4, with 8GB RAM, is similarly waiting for support from upstream.
## How do I run a specific version of Home Assistant?
For this you would need to install the [Terminal & SSH add-on][ssh] or use the console
that is available on your device by connecting a keyboard and screen.
To install the Terminal & SSH add-on, choose **Supervisor**, which is located in the sidebar and then the add-on store. If you don't see it, enable "Advanced Mode" from your profile page.
Use the web-based terminal or SSH to your Home Assistant system, or connect to the console, and run:
```bash
ha core update --version=0.XX.X
```
Replace 0.XX.X with the version you want. e.g., `0.111.2`
You can also use a similar command for the operating system:
```bash
ha os update --version 4.11
```
## Do I need to leave the USB stick connected for Wi-Fi?
No. The USB "CONFIG" stick is only used to import a network profile to `/etc/NetworkManager/system-connections/` and can be removed.
## 404 Client Error: Not Found ("no such image: homeassistant/...)
This error indicates the image, whether for updating to Home Assistant or installing or updating an add-on, was not able to be pulled to your system. This is usually a situation where there is not enough space for the image to be downloaded. The first thing to check for is the available space on your system.
Please note, if you are running the operating system as a virtual machine; the default VM image is only about 6GB. Many VM users run into this as they have not allocated enough storage. 32 GB is the minimum recommended size.
You'll need to explore your own system to determine where space has gone.
Using `df -h` in the SSH add-on console to you can quickly check to see if you have space available.
If there is plenty of space available then you might check to see if you are having network issues that are preventing images being downloaded.
## Why does the start button for an add-on flash red when I click it?
If you are looking for more information about add-ons, which won't start or install, navigate to Supervisor > System in the UI and check the logs.
The logs on this page are the same you would see using `ha logs` in the custom CLI.
## I'm trying to find my files on the host or SD card. Where are they?
On a Home Assistant OS install, your files are on the data partition within `/mnt/data/supervisor/`.
On the SD itself, this is an EXT4 partition labeled `hassos-data`
On a Supervised install, they are in `/usr/share/hassio/`.

BIN
source/images/blog/2020-07-28-ios-app-migration/social-update.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 57 KiB

BIN
source/images/integrations/iammeter/demo.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 190 KiB