mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 17:27:19 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
4bb58717b2
6
Gemfile
6
Gemfile
@ -10,9 +10,9 @@ group :development do
|
|||||||
gem 'stringex', '2.8.6'
|
gem 'stringex', '2.8.6'
|
||||||
# > 2.1.0 causes slowdowns https://github.com/sass/sassc-ruby/issues/189
|
# > 2.1.0 causes slowdowns https://github.com/sass/sassc-ruby/issues/189
|
||||||
gem 'sassc', '2.1.0'
|
gem 'sassc', '2.1.0'
|
||||||
gem 'sass-embedded', '1.87.0'
|
gem 'sass-embedded', '1.89.0'
|
||||||
gem 'rubocop', '1.75.5'
|
gem 'rubocop', '1.75.7'
|
||||||
gem 'ruby-lsp', '0.23.17'
|
gem 'ruby-lsp', '0.23.21'
|
||||||
gem 'rackup', '2.2.1'
|
gem 'rackup', '2.2.1'
|
||||||
end
|
end
|
||||||
|
|
||||||
|
|||||||
32
Gemfile.lock
32
Gemfile.lock
@ -30,10 +30,10 @@ GEM
|
|||||||
ffi (1.17.2-arm64-darwin)
|
ffi (1.17.2-arm64-darwin)
|
||||||
ffi (1.17.2-x86_64-linux-gnu)
|
ffi (1.17.2-x86_64-linux-gnu)
|
||||||
forwardable-extended (2.6.0)
|
forwardable-extended (2.6.0)
|
||||||
google-protobuf (4.30.2-arm64-darwin)
|
google-protobuf (4.31.0-arm64-darwin)
|
||||||
bigdecimal
|
bigdecimal
|
||||||
rake (>= 13)
|
rake (>= 13)
|
||||||
google-protobuf (4.30.2-x86_64-linux)
|
google-protobuf (4.31.0-x86_64-linux-gnu)
|
||||||
bigdecimal
|
bigdecimal
|
||||||
rake (>= 13)
|
rake (>= 13)
|
||||||
http_parser.rb (0.8.0)
|
http_parser.rb (0.8.0)
|
||||||
@ -70,12 +70,12 @@ GEM
|
|||||||
nokogiri (~> 1.12)
|
nokogiri (~> 1.12)
|
||||||
jekyll-watch (2.2.1)
|
jekyll-watch (2.2.1)
|
||||||
listen (~> 3.0)
|
listen (~> 3.0)
|
||||||
json (2.11.3)
|
json (2.12.0)
|
||||||
kramdown (2.5.1)
|
kramdown (2.5.1)
|
||||||
rexml (>= 3.3.9)
|
rexml (>= 3.3.9)
|
||||||
kramdown-parser-gfm (1.1.0)
|
kramdown-parser-gfm (1.1.0)
|
||||||
kramdown (~> 2.0)
|
kramdown (~> 2.0)
|
||||||
language_server-protocol (3.17.0.4)
|
language_server-protocol (3.17.0.5)
|
||||||
lint_roller (1.1.0)
|
lint_roller (1.1.0)
|
||||||
liquid (4.0.4)
|
liquid (4.0.4)
|
||||||
listen (3.9.0)
|
listen (3.9.0)
|
||||||
@ -99,7 +99,7 @@ GEM
|
|||||||
prism (1.4.0)
|
prism (1.4.0)
|
||||||
public_suffix (6.0.2)
|
public_suffix (6.0.2)
|
||||||
racc (1.8.1)
|
racc (1.8.1)
|
||||||
rack (3.1.14)
|
rack (3.1.15)
|
||||||
rack-protection (4.1.1)
|
rack-protection (4.1.1)
|
||||||
base64 (>= 0.1.0)
|
base64 (>= 0.1.0)
|
||||||
logger (>= 1.6.0)
|
logger (>= 1.6.0)
|
||||||
@ -114,12 +114,12 @@ GEM
|
|||||||
rb-fsevent (0.11.2)
|
rb-fsevent (0.11.2)
|
||||||
rb-inotify (0.11.1)
|
rb-inotify (0.11.1)
|
||||||
ffi (~> 1.0)
|
ffi (~> 1.0)
|
||||||
rbs (3.9.2)
|
rbs (3.9.4)
|
||||||
logger
|
logger
|
||||||
regexp_parser (2.10.0)
|
regexp_parser (2.10.0)
|
||||||
rexml (3.4.1)
|
rexml (3.4.1)
|
||||||
rouge (4.5.2)
|
rouge (4.5.2)
|
||||||
rubocop (1.75.5)
|
rubocop (1.75.7)
|
||||||
json (~> 2.3)
|
json (~> 2.3)
|
||||||
language_server-protocol (~> 3.17.0.2)
|
language_server-protocol (~> 3.17.0.2)
|
||||||
lint_roller (~> 1.1.0)
|
lint_roller (~> 1.1.0)
|
||||||
@ -133,7 +133,7 @@ GEM
|
|||||||
rubocop-ast (1.44.1)
|
rubocop-ast (1.44.1)
|
||||||
parser (>= 3.3.7.2)
|
parser (>= 3.3.7.2)
|
||||||
prism (~> 1.4)
|
prism (~> 1.4)
|
||||||
ruby-lsp (0.23.17)
|
ruby-lsp (0.23.21)
|
||||||
language_server-protocol (~> 3.17.0)
|
language_server-protocol (~> 3.17.0)
|
||||||
prism (>= 1.2, < 2.0)
|
prism (>= 1.2, < 2.0)
|
||||||
rbs (>= 3, < 4)
|
rbs (>= 3, < 4)
|
||||||
@ -142,10 +142,10 @@ GEM
|
|||||||
ruby2_keywords (0.0.5)
|
ruby2_keywords (0.0.5)
|
||||||
safe_yaml (1.0.5)
|
safe_yaml (1.0.5)
|
||||||
sass (3.4.25)
|
sass (3.4.25)
|
||||||
sass-embedded (1.87.0-arm64-darwin)
|
sass-embedded (1.89.0-arm64-darwin)
|
||||||
google-protobuf (~> 4.30)
|
google-protobuf (~> 4.31)
|
||||||
sass-embedded (1.87.0-x86_64-linux-gnu)
|
sass-embedded (1.89.0-x86_64-linux-gnu)
|
||||||
google-protobuf (~> 4.30)
|
google-protobuf (~> 4.31)
|
||||||
sass-globbing (1.1.5)
|
sass-globbing (1.1.5)
|
||||||
sass (>= 3.1)
|
sass (>= 3.1)
|
||||||
sassc (2.1.0)
|
sassc (2.1.0)
|
||||||
@ -159,7 +159,7 @@ GEM
|
|||||||
rack-protection (= 4.1.1)
|
rack-protection (= 4.1.1)
|
||||||
rack-session (>= 2.0.0, < 3)
|
rack-session (>= 2.0.0, < 3)
|
||||||
tilt (~> 2.0)
|
tilt (~> 2.0)
|
||||||
sorbet-runtime (0.5.12079)
|
sorbet-runtime (0.5.12124)
|
||||||
stringex (2.8.6)
|
stringex (2.8.6)
|
||||||
terminal-table (3.0.2)
|
terminal-table (3.0.2)
|
||||||
unicode-display_width (>= 1.1.1, < 3)
|
unicode-display_width (>= 1.1.1, < 3)
|
||||||
@ -185,9 +185,9 @@ DEPENDENCIES
|
|||||||
nokogiri (= 1.18.8)
|
nokogiri (= 1.18.8)
|
||||||
rackup (= 2.2.1)
|
rackup (= 2.2.1)
|
||||||
rake (= 13.2.1)
|
rake (= 13.2.1)
|
||||||
rubocop (= 1.75.5)
|
rubocop (= 1.75.7)
|
||||||
ruby-lsp (= 0.23.17)
|
ruby-lsp (= 0.23.21)
|
||||||
sass-embedded (= 1.87.0)
|
sass-embedded (= 1.89.0)
|
||||||
sass-globbing (= 1.1.5)
|
sass-globbing (= 1.1.5)
|
||||||
sassc (= 2.1.0)
|
sassc (= 2.1.0)
|
||||||
sinatra (= 4.1.1)
|
sinatra (= 4.1.1)
|
||||||
|
|||||||
@ -108,8 +108,8 @@ social:
|
|||||||
# Home Assistant release details
|
# Home Assistant release details
|
||||||
current_major_version: 2025
|
current_major_version: 2025
|
||||||
current_minor_version: 5
|
current_minor_version: 5
|
||||||
current_patch_version: 0
|
current_patch_version: 3
|
||||||
date_released: 2025-05-07
|
date_released: 2025-05-23
|
||||||
|
|
||||||
# Either # or the anchor link to latest release notes in the blog post.
|
# Either # or the anchor link to latest release notes in the blog post.
|
||||||
# Must be prefixed with a # and have double quotes around it.
|
# Must be prefixed with a # and have double quotes around it.
|
||||||
|
|||||||
234
package-lock.json
generated
234
package-lock.json
generated
@ -20,7 +20,7 @@
|
|||||||
"remark-lint-prohibited-strings": "^4.0.0",
|
"remark-lint-prohibited-strings": "^4.0.0",
|
||||||
"remark-lint-unordered-list-marker-style": "^4.0.1",
|
"remark-lint-unordered-list-marker-style": "^4.0.1",
|
||||||
"remark-stringify": "^11.0.0",
|
"remark-stringify": "^11.0.0",
|
||||||
"textlint": "^14.7.1",
|
"textlint": "^14.7.2",
|
||||||
"textlint-filter-rule-comments": "^1.2.2",
|
"textlint-filter-rule-comments": "^1.2.2",
|
||||||
"textlint-rule-common-misspellings": "^1.0.1",
|
"textlint-rule-common-misspellings": "^1.0.1",
|
||||||
"textlint-rule-terminology": "^5.0.13"
|
"textlint-rule-terminology": "^5.0.13"
|
||||||
@ -427,73 +427,73 @@
|
|||||||
"dev": true
|
"dev": true
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/ast-tester": {
|
"node_modules/@textlint/ast-tester": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/ast-tester/-/ast-tester-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/ast-tester/-/ast-tester-14.7.2.tgz",
|
||||||
"integrity": "sha512-WMXqBRsEaNJowPCASXOqKhu5zu+DL8I6u4R+j3gTHZiBZFXMCLVmBT6pY9ed1i2Owqzj7akYTqjaHJKagGLwxg==",
|
"integrity": "sha512-nlS1xJkIgyBinOx9zlMTU7e+06G8k6Xg8QBBeB+8oiY2UD4XKNHv0A3kOtW30DKtHcw1onZku00gI2ep1er77w==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@textlint/ast-node-types": "^14.7.1",
|
"@textlint/ast-node-types": "^14.7.2",
|
||||||
"debug": "^4.4.0"
|
"debug": "^4.4.0"
|
||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/ast-tester/node_modules/@textlint/ast-node-types": {
|
"node_modules/@textlint/ast-tester/node_modules/@textlint/ast-node-types": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.2.tgz",
|
||||||
"integrity": "sha512-7C/xYNZtaG+erIMjNZbRz7av9/S5eC+GAMh0rJ6A9Hik6nS4WyWKblutw2p+O2YWWT2tmOjzu/81fWzzDzmtRg==",
|
"integrity": "sha512-3rZc9vD8y/DlcFe3Y/cyKRRVgBH4ElEUzVFYdRVDwoMSwV/cIyZgYzVG6ZuOItQt+cHSREuijuucZ4VqZynbtg==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT"
|
"license": "MIT"
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/ast-traverse": {
|
"node_modules/@textlint/ast-traverse": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/ast-traverse/-/ast-traverse-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/ast-traverse/-/ast-traverse-14.7.2.tgz",
|
||||||
"integrity": "sha512-E9uflmEmr9bUbnX5W+KXoH4c2o5Bu6aimeqadIAixkVjVcYFKL7XJ44HJJx/Ern6hcSSYlbIPHjScjAMTT/kqQ==",
|
"integrity": "sha512-H2pH4NhxBO4nHf9bpEn1v5MZ3E1fKFyrGP3uminXWSqnz+ZEX3fVGYde8EyTdLXpwntUjBg67HBVM4EyTKuhTg==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@textlint/ast-node-types": "^14.7.1"
|
"@textlint/ast-node-types": "^14.7.2"
|
||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/ast-traverse/node_modules/@textlint/ast-node-types": {
|
"node_modules/@textlint/ast-traverse/node_modules/@textlint/ast-node-types": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.2.tgz",
|
||||||
"integrity": "sha512-7C/xYNZtaG+erIMjNZbRz7av9/S5eC+GAMh0rJ6A9Hik6nS4WyWKblutw2p+O2YWWT2tmOjzu/81fWzzDzmtRg==",
|
"integrity": "sha512-3rZc9vD8y/DlcFe3Y/cyKRRVgBH4ElEUzVFYdRVDwoMSwV/cIyZgYzVG6ZuOItQt+cHSREuijuucZ4VqZynbtg==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT"
|
"license": "MIT"
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/config-loader": {
|
"node_modules/@textlint/config-loader": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/config-loader/-/config-loader-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/config-loader/-/config-loader-14.7.2.tgz",
|
||||||
"integrity": "sha512-VBsKuqdrurhS8RUVwmMDShqRYm7oBKPHQxJXDKCY1zT1nXUR0y3/9KcZpKXtG1LEfluIteBmZicR/mwobZW56A==",
|
"integrity": "sha512-06Fqpe36ur7I+SZTtqZbJbsIbbu8uilJuiQG5t+7NIRPNo/d0TrioaMN2Ru/Yr+hq4eSJu+roZ20FNWHMEJb1Q==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@textlint/kernel": "^14.7.1",
|
"@textlint/kernel": "^14.7.2",
|
||||||
"@textlint/module-interop": "^14.7.1",
|
"@textlint/module-interop": "^14.7.2",
|
||||||
"@textlint/resolver": "^14.7.1",
|
"@textlint/resolver": "^14.7.2",
|
||||||
"@textlint/types": "^14.7.1",
|
"@textlint/types": "^14.7.2",
|
||||||
"@textlint/utils": "^14.7.1",
|
"@textlint/utils": "^14.7.2",
|
||||||
"debug": "^4.4.0",
|
"debug": "^4.4.0",
|
||||||
"rc-config-loader": "^4.1.3"
|
"rc-config-loader": "^4.1.3"
|
||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/feature-flag": {
|
"node_modules/@textlint/feature-flag": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/feature-flag/-/feature-flag-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/feature-flag/-/feature-flag-14.7.2.tgz",
|
||||||
"integrity": "sha512-yuwNOVPiwDRg+rL0uXzqo9q6g+Ac2T+TETU7RuMxPBlSQWak98I4c8NbjL+aWzL7xj5bZJw5q9MIlOk1jRxl2g==",
|
"integrity": "sha512-zfNbBZVrwgDJ4xTWe2FyL/vLvbfw1kTdPRStkFp1tu7I0ypsfwaMh41XZX8rbRqQ5x4p06rLexuOLig9HySyZg==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT"
|
"license": "MIT"
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/fixer-formatter": {
|
"node_modules/@textlint/fixer-formatter": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/fixer-formatter/-/fixer-formatter-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/fixer-formatter/-/fixer-formatter-14.7.2.tgz",
|
||||||
"integrity": "sha512-AnTLCHnMUNnwRZ3CmeaY15SLzjN3yWH/0OF4R0c+l2v6JF6cdlU907rdcjc9QQnszbaAqn1+fqT+oQ9N9nd5jA==",
|
"integrity": "sha512-KISSckKJD1JAHLy57D+EWRscp/GV7XM/nzPxRARpooIJyGlFNvg/VDkGDzU2ZitH63IduI5qdBxKzvbgk4OgdQ==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@textlint/module-interop": "^14.7.1",
|
"@textlint/module-interop": "^14.7.2",
|
||||||
"@textlint/resolver": "^14.7.1",
|
"@textlint/resolver": "^14.7.2",
|
||||||
"@textlint/types": "^14.7.1",
|
"@textlint/types": "^14.7.2",
|
||||||
"chalk": "^4.1.2",
|
"chalk": "^4.1.2",
|
||||||
"debug": "^4.4.0",
|
"debug": "^4.4.0",
|
||||||
"diff": "^5.2.0",
|
"diff": "^5.2.0",
|
||||||
@ -503,43 +503,43 @@
|
|||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/kernel": {
|
"node_modules/@textlint/kernel": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/kernel/-/kernel-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/kernel/-/kernel-14.7.2.tgz",
|
||||||
"integrity": "sha512-aRzw6jdU3UPKxZpeZtM98OBjx0gGUK1QP3RrNBaLSqKOeSn8q2NkfApVIldBV9oQ+z1Drwmati8Pf3xSExTYew==",
|
"integrity": "sha512-sb2npadp7rsnrVvwv4Ia13/HcwZtVZnY04cJYnDOS6R4TthnYRyP55WF7ftB8GX1bw7FIY/NPvJN/UuWTKQ8XA==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@textlint/ast-node-types": "^14.7.1",
|
"@textlint/ast-node-types": "^14.7.2",
|
||||||
"@textlint/ast-tester": "^14.7.1",
|
"@textlint/ast-tester": "^14.7.2",
|
||||||
"@textlint/ast-traverse": "^14.7.1",
|
"@textlint/ast-traverse": "^14.7.2",
|
||||||
"@textlint/feature-flag": "^14.7.1",
|
"@textlint/feature-flag": "^14.7.2",
|
||||||
"@textlint/source-code-fixer": "^14.7.1",
|
"@textlint/source-code-fixer": "^14.7.2",
|
||||||
"@textlint/types": "^14.7.1",
|
"@textlint/types": "^14.7.2",
|
||||||
"@textlint/utils": "^14.7.1",
|
"@textlint/utils": "^14.7.2",
|
||||||
"debug": "^4.4.0",
|
"debug": "^4.4.0",
|
||||||
"fast-equals": "^4.0.3",
|
"fast-equals": "^4.0.3",
|
||||||
"structured-source": "^4.0.0"
|
"structured-source": "^4.0.0"
|
||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/kernel/node_modules/@textlint/ast-node-types": {
|
"node_modules/@textlint/kernel/node_modules/@textlint/ast-node-types": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.2.tgz",
|
||||||
"integrity": "sha512-7C/xYNZtaG+erIMjNZbRz7av9/S5eC+GAMh0rJ6A9Hik6nS4WyWKblutw2p+O2YWWT2tmOjzu/81fWzzDzmtRg==",
|
"integrity": "sha512-3rZc9vD8y/DlcFe3Y/cyKRRVgBH4ElEUzVFYdRVDwoMSwV/cIyZgYzVG6ZuOItQt+cHSREuijuucZ4VqZynbtg==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT"
|
"license": "MIT"
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/linter-formatter": {
|
"node_modules/@textlint/linter-formatter": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/linter-formatter/-/linter-formatter-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/linter-formatter/-/linter-formatter-14.7.2.tgz",
|
||||||
"integrity": "sha512-saAE+e4RZFInRmCF9pu7ukZAHxWaYw9WIA1PptYHItCnlyGS7WB7cYHilkj4coWGr3xGaQ2qAjqX/QIbVE7QGA==",
|
"integrity": "sha512-QZOqft5uK+o/UN8UcEF3cHgfbG1r3+OWqlJojyjGNkEBbBNPSyDfYlVxDjHqnOAwm7jBaeqVGlwvw/7PUFmsmw==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@azu/format-text": "^1.0.2",
|
"@azu/format-text": "^1.0.2",
|
||||||
"@azu/style-format": "^1.0.1",
|
"@azu/style-format": "^1.0.1",
|
||||||
"@textlint/module-interop": "^14.7.1",
|
"@textlint/module-interop": "^14.7.2",
|
||||||
"@textlint/resolver": "^14.7.1",
|
"@textlint/resolver": "^14.7.2",
|
||||||
"@textlint/types": "^14.7.1",
|
"@textlint/types": "^14.7.2",
|
||||||
"chalk": "^4.1.2",
|
"chalk": "^4.1.2",
|
||||||
"debug": "^4.4.0",
|
"debug": "^4.4.0",
|
||||||
"js-yaml": "^3.14.1",
|
"js-yaml": "^3.14.1",
|
||||||
@ -552,13 +552,13 @@
|
|||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/markdown-to-ast": {
|
"node_modules/@textlint/markdown-to-ast": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/markdown-to-ast/-/markdown-to-ast-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/markdown-to-ast/-/markdown-to-ast-14.7.2.tgz",
|
||||||
"integrity": "sha512-aKIJi1FZj8PYr/n9EYFsifofT2XNPDX9E/24PiFMNBjiOfovCayOpfn6iuqNEo3CEPx7w4d20rQOUnxD+GYzhg==",
|
"integrity": "sha512-gfOQaBFoFVTj/9rzhEjnJonWZwWjM1RLmaO4J7GHIOFBAo/qr/EJRO3QijQWaAJFoH8xd/3cpUCEzpRwhwkeoA==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@textlint/ast-node-types": "^14.7.1",
|
"@textlint/ast-node-types": "^14.7.2",
|
||||||
"debug": "^4.4.0",
|
"debug": "^4.4.0",
|
||||||
"mdast-util-gfm-autolink-literal": "^0.1.3",
|
"mdast-util-gfm-autolink-literal": "^0.1.3",
|
||||||
"neotraverse": "^0.6.15",
|
"neotraverse": "^0.6.15",
|
||||||
@ -570,9 +570,9 @@
|
|||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/markdown-to-ast/node_modules/@textlint/ast-node-types": {
|
"node_modules/@textlint/markdown-to-ast/node_modules/@textlint/ast-node-types": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.2.tgz",
|
||||||
"integrity": "sha512-7C/xYNZtaG+erIMjNZbRz7av9/S5eC+GAMh0rJ6A9Hik6nS4WyWKblutw2p+O2YWWT2tmOjzu/81fWzzDzmtRg==",
|
"integrity": "sha512-3rZc9vD8y/DlcFe3Y/cyKRRVgBH4ElEUzVFYdRVDwoMSwV/cIyZgYzVG6ZuOItQt+cHSREuijuucZ4VqZynbtg==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT"
|
"license": "MIT"
|
||||||
},
|
},
|
||||||
@ -819,88 +819,88 @@
|
|||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/module-interop": {
|
"node_modules/@textlint/module-interop": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/module-interop/-/module-interop-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/module-interop/-/module-interop-14.7.2.tgz",
|
||||||
"integrity": "sha512-9mfLErTFx8N+tZNTL+46YCY/jnCDOJKpceng5WVwDeZeMJbewhjY3PVcxMoPnvPT10QnE/hDk3b6riUYckgHgw==",
|
"integrity": "sha512-rDQhFERa2+xMqhyrPFvAL9d5Tb4RpQGKQExwrezvtCTREh6Zsp/nKxtK0r6o0P9xn1+zq2sZHW9NZjpe7av3xw==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT"
|
"license": "MIT"
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/resolver": {
|
"node_modules/@textlint/resolver": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/resolver/-/resolver-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/resolver/-/resolver-14.7.2.tgz",
|
||||||
"integrity": "sha512-lQ5ATfpsOgiYnwe2aoS0t9uJ4SrvyiCJpfJdqUQZCVL161O/yMKZBc6nwsyBlruEcFoNxK06F3s3IIV4EsI12A==",
|
"integrity": "sha512-FCZa9XJx5KihK/4gxXLhS/KfOnBD6vD5UxAMtgrvbifn+JFrW9Kh17uZLCcuJDDJJCnZOHq8jdT7AU+rpmJZ+w==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT"
|
"license": "MIT"
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/source-code-fixer": {
|
"node_modules/@textlint/source-code-fixer": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/source-code-fixer/-/source-code-fixer-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/source-code-fixer/-/source-code-fixer-14.7.2.tgz",
|
||||||
"integrity": "sha512-2teYM26+mwFhKaPKYiKjTH3gInjBFJRMPrd2t+WO8NkZnVCrCq0IdWNJYAP34zBd1JLgXAK0EL93Mo+RPwCtcQ==",
|
"integrity": "sha512-1aWxLIzUIYq9pnrHx7NT7huNbdMONBGORrxYNFC6yIAlSjPo4j44yZabaOMTxjGTPMOvFTUVl2gXTUYqygBGOA==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@textlint/types": "^14.7.1",
|
"@textlint/types": "^14.7.2",
|
||||||
"debug": "^4.4.0"
|
"debug": "^4.4.0"
|
||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/text-to-ast": {
|
"node_modules/@textlint/text-to-ast": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/text-to-ast/-/text-to-ast-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/text-to-ast/-/text-to-ast-14.7.2.tgz",
|
||||||
"integrity": "sha512-sSyWYdsX407xMiTKqnB5xWW4ft9SyxwFW2sY3Cpl0emoH5x1CLiYnxpW8uLIN/eFWiSzQlKU9UpyHFfozSC3Ag==",
|
"integrity": "sha512-8+4WvYnaDR0F7gDszhs9iCQp5kbbEQ9itbvQHcFDhHi4XCDksWdrQz6XJ+Kw/zbLUEz9QtvoXZ1VjZRiwgtTIg==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@textlint/ast-node-types": "^14.7.1"
|
"@textlint/ast-node-types": "^14.7.2"
|
||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/text-to-ast/node_modules/@textlint/ast-node-types": {
|
"node_modules/@textlint/text-to-ast/node_modules/@textlint/ast-node-types": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.2.tgz",
|
||||||
"integrity": "sha512-7C/xYNZtaG+erIMjNZbRz7av9/S5eC+GAMh0rJ6A9Hik6nS4WyWKblutw2p+O2YWWT2tmOjzu/81fWzzDzmtRg==",
|
"integrity": "sha512-3rZc9vD8y/DlcFe3Y/cyKRRVgBH4ElEUzVFYdRVDwoMSwV/cIyZgYzVG6ZuOItQt+cHSREuijuucZ4VqZynbtg==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT"
|
"license": "MIT"
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/textlint-plugin-markdown": {
|
"node_modules/@textlint/textlint-plugin-markdown": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/textlint-plugin-markdown/-/textlint-plugin-markdown-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/textlint-plugin-markdown/-/textlint-plugin-markdown-14.7.2.tgz",
|
||||||
"integrity": "sha512-FnxwOOvvkIZ7HPV4gV0ZU6mA+G6LhA5QdspUqXAqTPQ0SY7X95PfQYbzk8Yz4RNyXFMhIcviKLO4+eSyBBTSuw==",
|
"integrity": "sha512-s6CR68bK9Y/+c0jvM+9oDT5LgvgRbP2A8IzPwuGVhqwFQBJmrSdG4KvBN4ycsq+h3EACTCeyv9bN9no0td9vgw==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@textlint/markdown-to-ast": "^14.7.1"
|
"@textlint/markdown-to-ast": "^14.7.2"
|
||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/textlint-plugin-text": {
|
"node_modules/@textlint/textlint-plugin-text": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/textlint-plugin-text/-/textlint-plugin-text-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/textlint-plugin-text/-/textlint-plugin-text-14.7.2.tgz",
|
||||||
"integrity": "sha512-Cq1pmUWU95W2cYpXr9GDkKm5RN5XAPwVThFeMtj6RE4bCS+qqH/2O08yhUobKo0ryKb7j1zzBi/QdQ2U34YwvQ==",
|
"integrity": "sha512-ZtO/i4cZ+y9j7KqsP8P3cbj/XpUDMyedkV+fQP8DkJb238vJ/EUrW8wBwvIq0BmGe7DKIgIl3WeFp8AKxNw7aw==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@textlint/text-to-ast": "^14.7.1"
|
"@textlint/text-to-ast": "^14.7.2"
|
||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/types": {
|
"node_modules/@textlint/types": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/types/-/types-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/types/-/types-14.7.2.tgz",
|
||||||
"integrity": "sha512-j10OEEHRAaqGMC6dK3+H1Eg3bksASGTmGDozsSepYs7qInY+lYBCe5m3JTrKkDnAX4nNy8ninnKzrYKcVkWahw==",
|
"integrity": "sha512-VpsmtJf9+7cnIxmKtAVVGVzI6f2k09kBZnzjdTAO8JZ+HTmV46jeoVrotpSfQbWDpuQk2UFPfrsZL/LNf/99ew==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@textlint/ast-node-types": "^14.7.1"
|
"@textlint/ast-node-types": "^14.7.2"
|
||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/types/node_modules/@textlint/ast-node-types": {
|
"node_modules/@textlint/types/node_modules/@textlint/ast-node-types": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.2.tgz",
|
||||||
"integrity": "sha512-7C/xYNZtaG+erIMjNZbRz7av9/S5eC+GAMh0rJ6A9Hik6nS4WyWKblutw2p+O2YWWT2tmOjzu/81fWzzDzmtRg==",
|
"integrity": "sha512-3rZc9vD8y/DlcFe3Y/cyKRRVgBH4ElEUzVFYdRVDwoMSwV/cIyZgYzVG6ZuOItQt+cHSREuijuucZ4VqZynbtg==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT"
|
"license": "MIT"
|
||||||
},
|
},
|
||||||
"node_modules/@textlint/utils": {
|
"node_modules/@textlint/utils": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/utils/-/utils-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/utils/-/utils-14.7.2.tgz",
|
||||||
"integrity": "sha512-nvIOltt0U5HQzu28qfYgbXUvZxEZBPRnQZHqlwMsqKp55bZ5L3iSNYwHvCej7fm9GOXH7Yz3UzLSko9eF5m3PA==",
|
"integrity": "sha512-NMLtiALWVYtl/zqRB0GIw3CJLNSV5bq8u35v1qaJOLrWhBVxOkbWISItHhQGndCalHTt8uYkntHXYKpk0oSPtQ==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT"
|
"license": "MIT"
|
||||||
},
|
},
|
||||||
@ -1648,15 +1648,6 @@
|
|||||||
"integrity": "sha512-yIovAzMX49sF8Yl58fSCWJ5svSLuaibPxXQJFLmBObTuCr0Mf1KiPopGM9NiFjiYBCbfaa2Fh6breQ6ANVTI0A==",
|
"integrity": "sha512-yIovAzMX49sF8Yl58fSCWJ5svSLuaibPxXQJFLmBObTuCr0Mf1KiPopGM9NiFjiYBCbfaa2Fh6breQ6ANVTI0A==",
|
||||||
"dev": true
|
"dev": true
|
||||||
},
|
},
|
||||||
"node_modules/get-stdin": {
|
|
||||||
"version": "5.0.1",
|
|
||||||
"resolved": "https://registry.npmjs.org/get-stdin/-/get-stdin-5.0.1.tgz",
|
|
||||||
"integrity": "sha512-jZV7n6jGE3Gt7fgSTJoz91Ak5MuTLwMwkoYdjxuJ/AmjIsE1UC03y/IWkZCQGEvVNS9qoRNwy5BCqxImv0FVeA==",
|
|
||||||
"dev": true,
|
|
||||||
"engines": {
|
|
||||||
"node": ">=0.12.0"
|
|
||||||
}
|
|
||||||
},
|
|
||||||
"node_modules/glob-parent": {
|
"node_modules/glob-parent": {
|
||||||
"version": "5.1.2",
|
"version": "5.1.2",
|
||||||
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz",
|
"resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz",
|
||||||
@ -6107,28 +6098,27 @@
|
|||||||
"dev": true
|
"dev": true
|
||||||
},
|
},
|
||||||
"node_modules/textlint": {
|
"node_modules/textlint": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/textlint/-/textlint-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/textlint/-/textlint-14.7.2.tgz",
|
||||||
"integrity": "sha512-jhWEeF3SWYPuItcTRLA1KAyxHAX2diWpqtglcagPzPidFi2OMKCNW55FlaIQvOkWdohp5LzFk0mv4XiChqGr0Q==",
|
"integrity": "sha512-SRff/IHVonktwTMm0momjMZeh0WTPWbQR0S0NXHoU7MUwLM9e4VJeQvkq7V0d37GiM1WfXJSkbaTVidOhOE+0Q==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@textlint/ast-node-types": "^14.7.1",
|
"@textlint/ast-node-types": "^14.7.2",
|
||||||
"@textlint/ast-traverse": "^14.7.1",
|
"@textlint/ast-traverse": "^14.7.2",
|
||||||
"@textlint/config-loader": "^14.7.1",
|
"@textlint/config-loader": "^14.7.2",
|
||||||
"@textlint/feature-flag": "^14.7.1",
|
"@textlint/feature-flag": "^14.7.2",
|
||||||
"@textlint/fixer-formatter": "^14.7.1",
|
"@textlint/fixer-formatter": "^14.7.2",
|
||||||
"@textlint/kernel": "^14.7.1",
|
"@textlint/kernel": "^14.7.2",
|
||||||
"@textlint/linter-formatter": "^14.7.1",
|
"@textlint/linter-formatter": "^14.7.2",
|
||||||
"@textlint/module-interop": "^14.7.1",
|
"@textlint/module-interop": "^14.7.2",
|
||||||
"@textlint/resolver": "^14.7.1",
|
"@textlint/resolver": "^14.7.2",
|
||||||
"@textlint/textlint-plugin-markdown": "^14.7.1",
|
"@textlint/textlint-plugin-markdown": "^14.7.2",
|
||||||
"@textlint/textlint-plugin-text": "^14.7.1",
|
"@textlint/textlint-plugin-text": "^14.7.2",
|
||||||
"@textlint/types": "^14.7.1",
|
"@textlint/types": "^14.7.2",
|
||||||
"@textlint/utils": "^14.7.1",
|
"@textlint/utils": "^14.7.2",
|
||||||
"debug": "^4.4.0",
|
"debug": "^4.4.0",
|
||||||
"file-entry-cache": "^10.0.5",
|
"file-entry-cache": "^10.0.5",
|
||||||
"get-stdin": "^5.0.1",
|
|
||||||
"glob": "^10.4.5",
|
"glob": "^10.4.5",
|
||||||
"md5": "^2.3.0",
|
"md5": "^2.3.0",
|
||||||
"mkdirp": "^0.5.6",
|
"mkdirp": "^0.5.6",
|
||||||
@ -6250,9 +6240,9 @@
|
|||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/textlint/node_modules/@textlint/ast-node-types": {
|
"node_modules/textlint/node_modules/@textlint/ast-node-types": {
|
||||||
"version": "14.7.1",
|
"version": "14.7.2",
|
||||||
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.1.tgz",
|
"resolved": "https://registry.npmjs.org/@textlint/ast-node-types/-/ast-node-types-14.7.2.tgz",
|
||||||
"integrity": "sha512-7C/xYNZtaG+erIMjNZbRz7av9/S5eC+GAMh0rJ6A9Hik6nS4WyWKblutw2p+O2YWWT2tmOjzu/81fWzzDzmtRg==",
|
"integrity": "sha512-3rZc9vD8y/DlcFe3Y/cyKRRVgBH4ElEUzVFYdRVDwoMSwV/cIyZgYzVG6ZuOItQt+cHSREuijuucZ4VqZynbtg==",
|
||||||
"dev": true,
|
"dev": true,
|
||||||
"license": "MIT"
|
"license": "MIT"
|
||||||
},
|
},
|
||||||
|
|||||||
@ -15,7 +15,7 @@
|
|||||||
"remark-lint-prohibited-strings": "^4.0.0",
|
"remark-lint-prohibited-strings": "^4.0.0",
|
||||||
"remark-lint-unordered-list-marker-style": "^4.0.1",
|
"remark-lint-unordered-list-marker-style": "^4.0.1",
|
||||||
"remark-stringify": "^11.0.0",
|
"remark-stringify": "^11.0.0",
|
||||||
"textlint": "^14.7.1",
|
"textlint": "^14.7.2",
|
||||||
"textlint-filter-rule-comments": "^1.2.2",
|
"textlint-filter-rule-comments": "^1.2.2",
|
||||||
"textlint-rule-common-misspellings": "^1.0.1",
|
"textlint-rule-common-misspellings": "^1.0.1",
|
||||||
"textlint-rule-terminology": "^5.0.13"
|
"textlint-rule-terminology": "^5.0.13"
|
||||||
|
|||||||
@ -43,9 +43,9 @@ module Jekyll
|
|||||||
<<~MARKUP
|
<<~MARKUP
|
||||||
<div class="alert alert-#{@type}">
|
<div class="alert alert-#{@type}">
|
||||||
<p class="alert-title"><iconify-icon inline icon='#{icon}'></iconify-icon> #{title}</p>
|
<p class="alert-title"><iconify-icon inline icon='#{icon}'></iconify-icon> #{title}</p>
|
||||||
<p class="alert-content">
|
<div class="alert-content">
|
||||||
#{contents}
|
#{contents}
|
||||||
</p>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
MARKUP
|
MARKUP
|
||||||
end
|
end
|
||||||
|
|||||||
@ -39,6 +39,8 @@
|
|||||||
excerpt: >
|
excerpt: >
|
||||||
Add-ons are additional standalone third-party software packages that can be
|
Add-ons are additional standalone third-party software packages that can be
|
||||||
installed on Home Assistant OS.
|
installed on Home Assistant OS.
|
||||||
|
aliases:
|
||||||
|
- add-ons
|
||||||
link: /getting-started/concepts-terminology/#add-ons
|
link: /getting-started/concepts-terminology/#add-ons
|
||||||
- term: Area
|
- term: Area
|
||||||
definition: >-
|
definition: >-
|
||||||
@ -77,7 +79,7 @@
|
|||||||
Home Assistant has built-in functionality to create files containing a copy
|
Home Assistant has built-in functionality to create files containing a copy
|
||||||
of your configuration. This can be used to restore your Home Assistant as
|
of your configuration. This can be used to restore your Home Assistant as
|
||||||
well as migrate to a new system. The backup feature is available for all
|
well as migrate to a new system. The backup feature is available for all
|
||||||
[installation types](/installation/#advanced-installation-methods).
|
[installation types](/installation/#about-installation-methods).
|
||||||
link: /common-tasks/general/#backups
|
link: /common-tasks/general/#backups
|
||||||
aliases:
|
aliases:
|
||||||
- backups
|
- backups
|
||||||
@ -305,37 +307,28 @@
|
|||||||
Home Assistant Container is a standalone container-based installation of
|
Home Assistant Container is a standalone container-based installation of
|
||||||
Home Assistant Core. Any [OCI](https://opencontainers.org/) compatible
|
Home Assistant Core. Any [OCI](https://opencontainers.org/) compatible
|
||||||
runtime can be used, but the documentation focus is on Docker.
|
runtime can be used, but the documentation focus is on Docker.
|
||||||
link: /installation/#advanced-installation-methods
|
link: /installation/#about-installation-methods
|
||||||
- term: Home Assistant Core
|
- term: Home Assistant Core
|
||||||
definition: >-
|
definition: >-
|
||||||
Home Assistant Core is the Python program at the heart of Home Assistant. It
|
Home Assistant Core is the Python program at the heart of Home Assistant. It
|
||||||
is part of all of the four installation types and can be run on various
|
is part of all installation types. It can be installed standalone (without Home Assistant
|
||||||
operating systems. It can be installed standalone (without Home Assistant
|
Supervisor) as a container using Docker (this is typically referred to as the Home Assistant
|
||||||
Supervisor), using a Virtual Environment (typically referred to as Home
|
Container installation method). For development, Core can also be run using a Virtual
|
||||||
Assistant Core installation method) or as a container using Docker
|
Environment (previously referred as the Home Assistant Core installation method.
|
||||||
(typically referred to as Home Assistant Container installation method).
|
For production setup, the [Home Assistant Core installation method is deprecated](https://www.home-assistant.io/blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/).
|
||||||
link: /installation/#advanced-installation-methods
|
|
||||||
excerpt: >
|
|
||||||
Home Assistant Core is the heart of Home Assistant itself. It is a Python
|
|
||||||
program that powers every installation type, but can be installed
|
|
||||||
standalone.
|
|
||||||
- term: Home Assistant Supervised
|
- term: Home Assistant Supervised
|
||||||
definition: >-
|
definition: >-
|
||||||
Home Assistant Supervised is a full UI managed home automation ecosystem
|
The Home Assistant Supervised installation method is a full UI managed home automation ecosystem
|
||||||
that runs the Home Assistant Core program, the Home Assistant Supervisor and
|
that runs the Home Assistant Core program, the Home Assistant Supervisor and
|
||||||
add-ons. It comes pre-installed on Home Assistant OS, but can be installed
|
add-ons. It comes pre-installed on Home Assistant OS, but can be installed
|
||||||
standalone on Debian Linux systems. It leverages Docker, which is managed by
|
standalone on Debian Linux systems. It leverages Docker, which is managed by
|
||||||
the Home Assistant Supervisor.
|
the Home Assistant Supervisor. The
|
||||||
excerpt: >
|
[Home Assistant Supervised installation method is deprecated](https://www.home-assistant.io/blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/).
|
||||||
Home Assistant Supervised is the full Home Assistant ecosystem, without the
|
|
||||||
Home Assistant Operating System.
|
|
||||||
link: /installation/#advanced-installation-methods
|
|
||||||
- term: Home Assistant Supervisor
|
- term: Home Assistant Supervisor
|
||||||
definition: >-
|
definition: >-
|
||||||
The Home Assistant Supervisor is a program that manages a Home Assistant
|
The Home Assistant Supervisor is a program that manages a Home Assistant
|
||||||
installation, taking care of installing and updating Home Assistant,
|
installation, taking care of installing and updating Home Assistant,
|
||||||
add-ons, itself, and, if used, updating the Home Assistant Operating System.
|
add-ons, itself, and, if used, updating the Home Assistant Operating System.
|
||||||
link: /installation/#advanced-installation-methods
|
|
||||||
- term: Home Assistant Operating System
|
- term: Home Assistant Operating System
|
||||||
definition: >-
|
definition: >-
|
||||||
Home Assistant OS, the Home Assistant Operating System, is an embedded,
|
Home Assistant OS, the Home Assistant Operating System, is an embedded,
|
||||||
@ -345,11 +338,6 @@
|
|||||||
add-ons. Home Assistant Supervisor keeps it up to date, removing the need
|
add-ons. Home Assistant Supervisor keeps it up to date, removing the need
|
||||||
for you to manage an operating system. Home Assistant Operating System is
|
for you to manage an operating system. Home Assistant Operating System is
|
||||||
the recommended installation method for most users.
|
the recommended installation method for most users.
|
||||||
excerpt: >
|
|
||||||
Home Assistant OS, the Home Assistant Operating System, is an embedded,
|
|
||||||
minimalistic, operating system designed to run the Home Assistant ecosystem.
|
|
||||||
It is the recommended installation method for most users.
|
|
||||||
link: /installation/#advanced-installation-methods
|
|
||||||
- term: Host
|
- term: Host
|
||||||
definition: >-
|
definition: >-
|
||||||
A device that can communicate with other devices on a network. During setup
|
A device that can communicate with other devices on a network. During setup
|
||||||
|
|||||||
@ -11,11 +11,11 @@ Many automations can be tested directly in the automation editor UI.
|
|||||||
|
|
||||||
### Running the entire automation
|
### Running the entire automation
|
||||||
|
|
||||||
In the three dots menu in the automation list or automation editor UI, select the **Run** button. This will execute all of the {% term actions %}, while skipping all {% term triggers %} and {% term conditions %}. This lets you test the full sequence of actions, as if the automation was triggered and all conditions were true. Note that any [trigger ID](/docs/automation/trigger/#trigger-id) used in your triggers will not be active when you test this way. The Trigger ID or any data passed by in the `trigger` data in conditions or actions can't be tested directly this way.
|
In the three dots menu in the automation list or automation editor UI, select the **Run actions** button. This will execute all of the {% term actions %}, while skipping all {% term triggers %} and {% term conditions %}. This lets you test the full sequence of actions, as if the automation was triggered and all conditions were true. Note that any [trigger ID](/docs/automation/trigger/#trigger-id) used in your triggers will not be active when you test this way. The Trigger ID or any data passed by in the `trigger` data in conditions or actions can't be tested directly this way.
|
||||||
|
|
||||||
You can also trigger an automation manually. This can test the conditions as if the automation was triggered by an event. Navigate to {% my developer_services title="**Developer tools** > **Actions**" %}. In the **Action** drop-down, select **Automation: Trigger**, then **Choose entity** to select the automation you are testing. Toggle whether to skip the conditions, then **Perform action**. If needed, additional `trigger` or other data can be added in the YAML view for testing. The [trigger](/docs/automation/trigger/) page has more information about data within the trigger.
|
You can also trigger an automation manually. This can test the conditions as if the automation was triggered by an event. Navigate to {% my developer_services title="**Developer tools** > **Actions**" %}. In the **Action** drop-down, select **Automation: Trigger**, then **Choose entity** to select the automation you are testing. Toggle whether to skip the conditions, then **Perform action**. If needed, additional `trigger` or other data can be added in the YAML view for testing. The [trigger](/docs/automation/trigger/) page has more information about data within the trigger.
|
||||||
|
|
||||||
Testing with complex triggers, conditions, and variables can be difficult. Note that using the **Run** button will skip all triggers and conditions, while **Developer Tools** can be used with or without checking conditions.
|
Testing with complex triggers, conditions, and variables can be difficult. Note that using the **Run actions** button will skip all triggers and conditions, while **Developer Tools** can be used with or without checking conditions.
|
||||||
|
|
||||||
### Running individual actions or conditions
|
### Running individual actions or conditions
|
||||||
|
|
||||||
|
|||||||
@ -8,14 +8,10 @@ related:
|
|||||||
title: Storing credentials in `secrets.yaml` file
|
title: Storing credentials in `secrets.yaml` file
|
||||||
- docs: /common-tasks/general/#backups
|
- docs: /common-tasks/general/#backups
|
||||||
title: Creating and restoring backups
|
title: Creating and restoring backups
|
||||||
- docs: /integrations/backup/docs/tools/dev-tools/#reloading-the-yaml-configuration
|
|
||||||
title: Creating backups for Home Assistant Container and Core
|
|
||||||
- docs: /docs/tools/dev-tools/#reloading-the-yaml-configuration
|
- docs: /docs/tools/dev-tools/#reloading-the-yaml-configuration
|
||||||
title: Reloading the YAML configuration from developer tools
|
title: Reloading the YAML configuration from developer tools
|
||||||
- docs: /common-tasks/os/#configuring-access-to-files
|
- docs: /common-tasks/os/#configuring-access-to-files
|
||||||
title: Configuring file access on the Operating System
|
title: Configuring file access on the Operating System
|
||||||
- docs: /common-tasks/supervised/#configuring-access-to-files
|
|
||||||
title: Configuring file access on Supervised
|
|
||||||
- docs: docs/configuration/troubleshooting/
|
- docs: docs/configuration/troubleshooting/
|
||||||
title: Troubleshooting the configuration
|
title: Troubleshooting the configuration
|
||||||
---
|
---
|
||||||
@ -31,7 +27,7 @@ Example of a configuration.yaml file, accessed using the File editor add-on on a
|
|||||||
|
|
||||||
## Editing `configuration.yaml`
|
## Editing `configuration.yaml`
|
||||||
|
|
||||||
How you edit your `configuration.yaml` file depends on your editor preferences and the [installation method](/installation/#advanced-installation-methods) you used to set up Home Assistant. Follow these steps:
|
How you edit your `configuration.yaml` file depends on your editor preferences and the [installation method](/installation/#about-installation-methods) you used to set up Home Assistant. Follow these steps:
|
||||||
|
|
||||||
1. [Set up file access](#to-set-up-access-to-the-files-and-prepare-an-editor).
|
1. [Set up file access](#to-set-up-access-to-the-files-and-prepare-an-editor).
|
||||||
2. [Locate the config directory](#to-find-the-configuration-directory).
|
2. [Locate the config directory](#to-find-the-configuration-directory).
|
||||||
@ -41,18 +37,13 @@ How you edit your `configuration.yaml` file depends on your editor preferences a
|
|||||||
### To set up access to the files and prepare an editor
|
### To set up access to the files and prepare an editor
|
||||||
|
|
||||||
Before you can edit a file, you need to know how to access files in Home Assistant and setup an editor.
|
Before you can edit a file, you need to know how to access files in Home Assistant and setup an editor.
|
||||||
File access depends on your [installation method](/installation/#advanced-installation-methods). If you use {% term "Home Assistant Operating System" %} or {% term "Home Assistant Supervised" %}, you can use editor add-ons, for example, but not if you use {% term "Home Assistant Core" %} or {% term "Home Assistant Container" %}.
|
File access depends on your [installation method](/installation/#about-installation-methods). If you use {% term "Home Assistant Operating System" %}, you can use editor add-ons, for example. If you use {% term "Home Assistant Container" %}, add-ons are not available.
|
||||||
|
|
||||||
To set up file access, follow the steps for your [installation method](/installation/#advanced-installation-methods):
|
To set up file access on the Home Assistant Operating System, follow these steps:
|
||||||
|
|
||||||
- [Configure file access on the Operating System](/common-tasks/os/#configuring-access-to-files):
|
- If you are unsure which option to choose, install the [file editor add-on](/common-tasks/os/#installing-and-using-the-file-editor-add-on).
|
||||||
- If you are unsure which option to choose, install the [file editor add-on](/common-tasks/os/#installing-and-using-the-file-editor-add-on).
|
|
||||||
- Alternatively, use the [Studio Code Server add-on](/common-tasks/os/#installing-and-using-the-visual-studio-code-vsc-add-on). This editor offers live syntax checking and auto-fill of various Home Assistant entities. But it looks more complex than the file editor.
|
- Alternatively, use the [Studio Code Server add-on](/common-tasks/os/#installing-and-using-the-visual-studio-code-vsc-add-on). This editor offers live syntax checking and auto-fill of various Home Assistant entities. But it looks more complex than the file editor.
|
||||||
- If you prefer to use a file editor on your computer, use the [Samba add-on](/common-tasks/os/#installing-and-using-the-samba-add-on).
|
- If you prefer to use a file editor on your computer, use the [Samba add-on](/common-tasks/os/#installing-and-using-the-samba-add-on).
|
||||||
- [Configure file access on Supervised](/common-tasks/supervised/#configuring-access-to-files):
|
|
||||||
- Using the [File editor add-on](/common-tasks/supervised/#installing-and-using-the-file-editor-add-on).
|
|
||||||
- Using the [Studio Code Server add-on](/common-tasks/supervised/#installing-and-using-the-visual-studio-code-vsc-add-on).
|
|
||||||
- Using the [Samba add-on](/common-tasks/supervised/#installing-and-using-the-samba-add-on).
|
|
||||||
|
|
||||||
### To find the configuration directory
|
### To find the configuration directory
|
||||||
|
|
||||||
@ -67,7 +58,6 @@ To set up file access, follow the steps for your [installation method](/installa
|
|||||||
- Unless you changed the file structure, the default is as follows: -
|
- Unless you changed the file structure, the default is as follows: -
|
||||||
- {% term "Home Assistant Operating System" %}: the `configuration.yaml` is in the `/config` folder of the installation.
|
- {% term "Home Assistant Operating System" %}: the `configuration.yaml` is in the `/config` folder of the installation.
|
||||||
- {% term "Home Assistant Container" %}: the `configuration.yaml` is in the config folder that you mounted in your container.
|
- {% term "Home Assistant Container" %}: the `configuration.yaml` is in the config folder that you mounted in your container.
|
||||||
- {% term "Home Assistant Core" %}: the `configuration.yaml` is in the config folder passed to the `hass` command (default is `~/.homeassistant`).
|
|
||||||
3. Once you located the config folder, you can edit your `configuration.yaml` file.
|
3. Once you located the config folder, you can edit your `configuration.yaml` file.
|
||||||
|
|
||||||
{% note %}
|
{% note %}
|
||||||
@ -80,12 +70,10 @@ If you have watched any videos about setting up Home Assistant using `configurat
|
|||||||
|
|
||||||
After changing configuration or automation files, you can check if the configuration is valid. A configuration check is also applied automatically when you reload the configuration or when you restart Home Assistant.
|
After changing configuration or automation files, you can check if the configuration is valid. A configuration check is also applied automatically when you reload the configuration or when you restart Home Assistant.
|
||||||
|
|
||||||
The method for running a configuration check depends on your [installation type](/installation/#advanced-installation-methods). Check the common tasks for your installation type:
|
The method for running a configuration check depends on your [installation type](/installation/#about-installation-methods). Check the common tasks for your installation type:
|
||||||
|
|
||||||
- [Configuration check on Operating System](/common-tasks/os/#configuration-check)
|
- [Configuration check on Operating System](/common-tasks/os/#configuration-check)
|
||||||
- [Configuration check on Supervised](/common-tasks/supervised/#configuration-check)
|
|
||||||
- [Configuration check on Container](/common-tasks/container/#configuration-check)
|
- [Configuration check on Container](/common-tasks/container/#configuration-check)
|
||||||
- [Configuration check on Core](/common-tasks/core/#configuration-check)
|
|
||||||
|
|
||||||
## Reloading the configuration to apply changes
|
## Reloading the configuration to apply changes
|
||||||
|
|
||||||
|
|||||||
@ -24,7 +24,7 @@ Here's the summary of what you *must* do to secure your Home Assistant system:
|
|||||||
|
|
||||||
## Remote access
|
## Remote access
|
||||||
|
|
||||||
If you want secure remote access, the easiest option is to use [Home Assistant Cloud](/cloud/) by which you also [support](https://www.nabucasa.com/about/) the founders of Home Assistant.
|
If you want secure remote access, the easiest option is to use [Home Assistant Cloud](/cloud/) by which you also support the [Open Home Foundation](https://www.openhomefoundation.org), which develops Home Assistant, ESPHome and much more.
|
||||||
|
|
||||||
Another option is to use TLS/SSL via the add-on [Duck DNS](/integrations/duckdns/) integrating Let's Encrypt.
|
Another option is to use TLS/SSL via the add-on [Duck DNS](/integrations/duckdns/) integrating Let's Encrypt.
|
||||||
|
|
||||||
|
|||||||
@ -4,9 +4,9 @@ description: "Options for regaining access"
|
|||||||
related:
|
related:
|
||||||
- docs: /common-tasks/os/#listing-all-users-from-the-command-line
|
- docs: /common-tasks/os/#listing-all-users-from-the-command-line
|
||||||
title: Listing all usernames via command line
|
title: Listing all usernames via command line
|
||||||
- url: https://yellow.home-assistant.io/guides/factory-reset/
|
- url: https://support.nabucasa.com/hc/en-us/articles/25463622043165
|
||||||
title: Reset the Yellow
|
title: Reset the Yellow
|
||||||
- url: https://green.home-assistant.io/guides/reset/
|
- url: https://support.nabucasa.com/hc/en-us/articles/25161225495837
|
||||||
title: Reset the Green
|
title: Reset the Green
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -25,10 +25,10 @@ You are the **owner** of the Home Assistant server and you cannot login because
|
|||||||
- you are using the {% term "Home Assistant Operating System" %}
|
- you are using the {% term "Home Assistant Operating System" %}
|
||||||
- you have access to the Home Assistant server.
|
- you have access to the Home Assistant server.
|
||||||
2. Open a terminal connection to Home Assistant:
|
2. Open a terminal connection to Home Assistant:
|
||||||
- If you are using a Home Assistant Green, follow these steps [to access the console](https://green.home-assistant.io/guides/use-terminal/).
|
- If you are using a Home Assistant Green, follow these steps [to access the console](https://support.nabucasa.com/hc/en-us/articles/25153288092829).
|
||||||
- If you are using a Home Assistant Yellow, follow these steps:
|
- If you are using a Home Assistant Yellow, follow these steps:
|
||||||
- [to access the console from Windows](https://yellow.home-assistant.io/guides/use-serial-console-windows/)
|
- [to access the console from Windows](https://support.nabucasa.com/hc/en-us/articles/25454894609693)
|
||||||
- [to access the console from Linux or macOS](https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/).
|
- [to access the console from Linux or macOS](https://support.nabucasa.com/hc/en-us/articles/25454972435357).
|
||||||
- If you are using another system, connect keyboard and monitor. The procedure might be similar the one used for Green.
|
- If you are using another system, connect keyboard and monitor. The procedure might be similar the one used for Green.
|
||||||
- If you are using a Home Assistant OVA (virtualization image):
|
- If you are using a Home Assistant OVA (virtualization image):
|
||||||
- Access the system console by opening the terminal through your virtualization platform's interface (for example, Proxmox, VMware, VirtualBox).
|
- Access the system console by opening the terminal through your virtualization platform's interface (for example, Proxmox, VMware, VirtualBox).
|
||||||
@ -72,9 +72,9 @@ Use this procedure only if the following conditions are met:
|
|||||||
|
|
||||||
1. If you are using a Home Assistant Yellow or Green, refer to their documentation.
|
1. If you are using a Home Assistant Yellow or Green, refer to their documentation.
|
||||||
- If you are using a Home Assistant Yellow, refer to the following procedure:
|
- If you are using a Home Assistant Yellow, refer to the following procedure:
|
||||||
- [Resetting the owner password on Home Assistant Yellow](https://yellow.home-assistant.io/faq/#i-forgot-the-owner-password-for-home-assistant-how-can-i-reset-it)
|
- [Resetting the owner password on Home Assistant Yellow](https://support.nabucasa.com/hc/en-us/articles/25455301907997)
|
||||||
- If you are using a Home Assistant Green, refer to the following procedure:
|
- If you are using a Home Assistant Green, refer to the following procedure:
|
||||||
- [Resetting the owner password on Home Assistant Green](https://green.home-assistant.io/faq/#i-forgot-the-owner-password-for-the-home-assistant-green-how-can-i-reset-it)
|
- [Resetting the owner password on Home Assistant Green](https://support.nabucasa.com/hc/en-us/articles/25142896227357)
|
||||||
2. If you are not using a Yellow or Green: Connect to the console of the Home Assistant server:
|
2. If you are not using a Yellow or Green: Connect to the console of the Home Assistant server:
|
||||||
- If you are using a virtual machine, connect to your virtual machine console.
|
- If you are using a virtual machine, connect to your virtual machine console.
|
||||||
- If you are using another board, connect a keyboard and monitor to your device and access the terminal. The procedure is likely very similar to the one described for the Home Assistant Green.
|
- If you are using another board, connect a keyboard and monitor to your device and access the terminal. The procedure is likely very similar to the one described for the Home Assistant Green.
|
||||||
@ -115,8 +115,8 @@ If you lose the password associated with the owner account and the steps above d
|
|||||||
- If you have an external backup with an administrator account of which you still know the login credentials, you can restore that backup.
|
- If you have an external backup with an administrator account of which you still know the login credentials, you can restore that backup.
|
||||||
- If you do not have a backup, resetting the device will erase all data.
|
- If you do not have a backup, resetting the device will erase all data.
|
||||||
|
|
||||||
- If you have a Home Assistant Green, [reset the Green](https://green.home-assistant.io/guides/reset/).
|
- If you have a Home Assistant Green, [reset the Green](https://support.nabucasa.com/hc/en-us/articles/25161225495837).
|
||||||
- If you have a Home Assistant Yellow, [reset the Yellow](https://yellow.home-assistant.io/guides/factory-reset/).
|
- If you have a Home Assistant Yellow, [reset the Yellow](https://support.nabucasa.com/hc/en-us/articles/25463622043165).
|
||||||
|
|
||||||
## Recovering data for Home Assistant (including Supervised)
|
## Recovering data for Home Assistant (including Supervised)
|
||||||
|
|
||||||
|
|||||||
@ -171,7 +171,7 @@ This procedure has been tested with the following modules:
|
|||||||
|
|
||||||
1. Make sure the module is properly seated on the Home Assistant Yellow.
|
1. Make sure the module is properly seated on the Home Assistant Yellow.
|
||||||
.
|
.
|
||||||
2. Carefully [close the case](https://yellow.home-assistant.io/guides/add-ssd-existing-installation/#reassembling-top-part) and power up Home Assistant Yellow.
|
2. Carefully [close the case](https://support.nabucasa.com/hc/en-us/articles/25606333033501) (see Reassembling your Home Assistant Yellow section) and power up Home Assistant Yellow.
|
||||||
3. Follow the procedure on [setting up a Z-Wave JS server](/integrations/zwave_js/#setting-up-a-z-wave-js-server).
|
3. Follow the procedure on [setting up a Z-Wave JS server](/integrations/zwave_js/#setting-up-a-z-wave-js-server).
|
||||||
1. In step 2, follow the manual setup steps to install the Z-Wave integration.
|
1. In step 2, follow the manual setup steps to install the Z-Wave integration.
|
||||||
2. in Step 4, you will be prompted to choose a **Device path**. Choose **ttyAMA0**.
|
2. in Step 4, you will be prompted to choose a **Device path**. Choose **ttyAMA0**.
|
||||||
|
|||||||
@ -10,7 +10,7 @@ If you try to access the configuration dialog for an entity in your Home Assista
|
|||||||
|
|
||||||
This means that this entity does not have a unique identification, e.g., a serial number or another identifier that is guaranteed to be static and never changes. As a result, the normal editing process that allows you to change various settings through the user interface (such as the entity ID, icon, friendly name, etc.) is not possible here.
|
This means that this entity does not have a unique identification, e.g., a serial number or another identifier that is guaranteed to be static and never changes. As a result, the normal editing process that allows you to change various settings through the user interface (such as the entity ID, icon, friendly name, etc.) is not possible here.
|
||||||
|
|
||||||
Typically, you'll see this when you create entities manually using YAML, but it can also appear if the integration that provides this entity, cannot determine a unique ID. This however is not an error, but just a limitation of the integration you use. A few selected integrations (such as [`template`](/integrations/template/) and [`mqtt`](/integrations/mqtt/)) allow the user to define a unique ID.
|
Typically, you'll see this when you create entities manually using YAML, but it can also appear if the integration that provides this entity cannot determine a unique ID. This is not an error, but rather a limitation of the integration you use. A few selected integrations (such as [`template`](/integrations/template/) and [`mqtt`](/integrations/mqtt/)) allow you to define a unique ID.
|
||||||
|
|
||||||
### Used where?
|
### Used where?
|
||||||
|
|
||||||
@ -36,4 +36,12 @@ Typically, you'll see this when you create entities manually using YAML, but it
|
|||||||
|
|
||||||
In case your entity has no unique ID and therefore cannot be changed through the UI, there are some [manual customization options](/docs/configuration/customizing-devices) directly through YAML files.
|
In case your entity has no unique ID and therefore cannot be changed through the UI, there are some [manual customization options](/docs/configuration/customizing-devices) directly through YAML files.
|
||||||
|
|
||||||
|
### Can I add a unique ID myself?
|
||||||
|
|
||||||
|
No, as an end-user, you cannot add a unique ID to an entity that doesn't have one. Unique IDs are a feature that must be provided by the integration itself. This is because the unique ID needs to be persistent across restarts and should consistently identify the same physical device or service.
|
||||||
|
|
||||||
|
If an integration currently doesn't provide unique IDs for its entities, this means the integration could potentially be modernized to include this capability. However, providing unique IDs is not currently a mandatory requirement for all integrations.
|
||||||
|
|
||||||
|
The Home Assistant project always welcomes code contributions to enhance integrations with this capability. If you're interested in improving an integration to provide unique IDs, you can contribute code to the Home Assistant project. For more information on contributing, please visit the [developer documentation](https://developers.home-assistant.io/docs/development_index).
|
||||||
|
|
||||||
In case you want to read more about unique IDs, head over to this [developer documentation page](https://developers.home-assistant.io/docs/entity_registry_index/).
|
In case you want to read more about unique IDs, head over to this [developer documentation page](https://developers.home-assistant.io/docs/entity_registry_index/).
|
||||||
|
|||||||
@ -276,9 +276,9 @@
|
|||||||
<li>
|
<li>
|
||||||
{% icon "bitcoin-icons:node-hardware-filled" %} Official hardware
|
{% icon "bitcoin-icons:node-hardware-filled" %} Official hardware
|
||||||
<ul>
|
<ul>
|
||||||
<li><a href="https://green.home-assistant.io/">Home Assistant Green {% icon "tabler:external-link" %}</a></li>
|
<li><a href="https://support.nabucasa.com/hc/en-us/categories/24638797677853-Home-Assistant-Green">Home Assistant Green {% icon "tabler:external-link" %}</a></li>
|
||||||
<li><a href="https://yellow.home-assistant.io/">Home Assistant Yellow {% icon "tabler:external-link" %}</a></li>
|
<li><a href="https://support.nabucasa.com/hc/en-us/categories/24734620813469">Home Assistant Connect ZBT-1 {% icon "tabler:external-link" %}</a></li>
|
||||||
<li><a href="https://connectzbt1.home-assistant.io/">Home Assistant Connect ZBT-1 {% icon "tabler:external-link" %}</a></li>
|
<li><a href="https://support.nabucasa.com/hc/en-us/categories/24734575925149-Home-Assistant-Yellow">Home Assistant Yellow {% icon "tabler:external-link" %}</a></li>
|
||||||
<li><a href="https://voice-pe.home-assistant.io/">Home Assistant Voice Preview Edition {% icon "tabler:external-link" %}</a></li>
|
<li><a href="https://support.nabucasa.com/hc/en-us/categories/24451727188125-Home-Assistant-Voice-Preview-Edition">Home Assistant Voice Preview Edition {% icon "tabler:external-link" %}</a></li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
|
|||||||
@ -9,8 +9,8 @@
|
|||||||
<li>{% active_link /installation/ Installation %}
|
<li>{% active_link /installation/ Installation %}
|
||||||
{% if root == 'installation' %}
|
{% if root == 'installation' %}
|
||||||
<ul>
|
<ul>
|
||||||
<li><a href="https://green.home-assistant.io/">Home Assistant Green {% icon "tabler:external-link" %}</a></li>
|
<li><a href="https://support.nabucasa.com/hc/en-us/categories/24638797677853-Home-Assistant-Green">Home Assistant Green {% icon "tabler:external-link" %}</a></li>
|
||||||
<li><a href="https://yellow.home-assistant.io/">Home Assistant Yellow {% icon "tabler:external-link" %}</a></li>
|
<li><a href="https://support.nabucasa.com/hc/en-us/categories/24734575925149-Home-Assistant-Yellow">Home Assistant Yellow {% icon "tabler:external-link" %}</a></li>
|
||||||
<li>{% active_link /installation/raspberrypi Raspberry Pi %}</li>
|
<li>{% active_link /installation/raspberrypi Raspberry Pi %}</li>
|
||||||
<li>{% active_link /installation/odroid ODROID %}</li>
|
<li>{% active_link /installation/odroid ODROID %}</li>
|
||||||
<li>{% active_link /installation/generic-x86-64 Generic x86-64 %}</li>
|
<li>{% active_link /installation/generic-x86-64 Generic x86-64 %}</li>
|
||||||
|
|||||||
@ -113,8 +113,8 @@ Note, some systems have a reset button you can use to clear the data disk, inste
|
|||||||
|
|
||||||
- If you have a Home Assistant Yellow with a Raspberry Pi Compute Module 5, use the command line steps described above.
|
- If you have a Home Assistant Yellow with a Raspberry Pi Compute Module 5, use the command line steps described above.
|
||||||
|
|
||||||
- If you have a Home Assistant Yellow with a Raspberry Pi Compute Module 4, there is a red hardware button to wipe the data disk. Follow the procedure on [resetting the Home Assistant Yellow](https://yellow.home-assistant.io/guides/factory-reset/).
|
- If you have a Home Assistant Yellow with a Raspberry Pi Compute Module 4, there is a red hardware button to wipe the data disk. Follow the procedure on [resetting the Home Assistant Yellow](https://support.nabucasa.com/hc/en-us/articles/25463622043165).
|
||||||
- If you have a Home Assistant Green, there is a black hardware button to wipe the data disk. Follow the procedure on [resetting the Home Assistant Green](https://green.home-assistant.io/guides/reset/).
|
- If you have a Home Assistant Green, there is a black hardware button to wipe the data disk. Follow the procedure on [resetting the Home Assistant Green](https://support.nabucasa.com/hc/en-us/articles/25161225495837).
|
||||||
|
|
||||||
#### Listing all users from the command line
|
#### Listing all users from the command line
|
||||||
|
|
||||||
|
|||||||
@ -4,7 +4,7 @@
|
|||||||
These below instructions are for an installation of {% term "Home Assistant Container" %} running in your own container environment, which you manage yourself. Any [OCI](https://opencontainers.org/) compatible runtime can be used, however this guide will focus on installing it with Docker.
|
These below instructions are for an installation of {% term "Home Assistant Container" %} running in your own container environment, which you manage yourself. Any [OCI](https://opencontainers.org/) compatible runtime can be used, however this guide will focus on installing it with Docker.
|
||||||
|
|
||||||
{% note %}
|
{% note %}
|
||||||
This installation method **does not have access to add-ons**. If you want to use add-ons, you need to use another installation method. The recommended method is {% term "Home Assistant Operating System" %}. Checkout the [overview table of installation types](https://www.home-assistant.io/installation/#advanced-installation-methods) to see the differences.
|
This installation method **does not have access to add-ons**. If you want to use add-ons, you need to use another installation method. The recommended method is {% term "Home Assistant Operating System" %}. Checkout the [overview table of installation types](https://www.home-assistant.io/installation/#about-installation-methods) to see the differences.
|
||||||
{% endnote %}
|
{% endnote %}
|
||||||
|
|
||||||
{% important %}
|
{% important %}
|
||||||
|
|||||||
@ -277,8 +277,10 @@ If you are running an older Windows version or have a stricter network configura
|
|||||||
|
|
||||||
### Download the appropriate image
|
### Download the appropriate image
|
||||||
|
|
||||||
- [VirtualBox][vdi] (.vdi)
|
- [VirtualBox (Intel chip)][vdi] (.vdi)
|
||||||
{% if page.installation_type == 'linux' %}
|
{% if page.installation_type == 'macos' %}
|
||||||
|
- [VirtualBox (Apple Silicon chip)][vmdk_arch64] (.vmdk)
|
||||||
|
{% elsif page.installation_type == 'linux' %}
|
||||||
- [KVM][qcow2] (.qcow2)
|
- [KVM][qcow2] (.qcow2)
|
||||||
{% elsif page.installation_type == 'alternative' %}
|
{% elsif page.installation_type == 'alternative' %}
|
||||||
- [KVM/Proxmox][qcow2] (.qcow2)
|
- [KVM/Proxmox][qcow2] (.qcow2)
|
||||||
@ -317,14 +319,11 @@ Minimum recommended assignments:
|
|||||||
- title: VirtualBox
|
- title: VirtualBox
|
||||||
content: |
|
content: |
|
||||||
1. Create a new virtual machine.
|
1. Create a new virtual machine.
|
||||||
2. Select type **Linux** and version **Linux 2.6 / 3.x / 4.x (64-bit)**.
|
2. Select type **Linux**, subtype **Oracle Linux** and version **Oracle Linux (ARM 64-bit)**.
|
||||||
3. Under **Hardware**, select the amount of memory and number of CPUs. Then, select **Enable EFI**.
|
3. Under **Hardware**, select the amount of memory and number of CPUs. Then, select **Enable EFI**.
|
||||||
- Make sure **EFI** is enabled. If EFI is not enabled, HAOS won't boot.
|
- Make sure **EFI** is enabled. If EFI is not enabled, HAOS won't boot.
|
||||||
4. Under **Hard Disk**, select **Use an existing virtual hard disk file**, select the unzipped VDI file from above.
|
4. Under **Hard Disk**, select **Use an existing virtual hard disk file**, select the unzipped VDI file from above.
|
||||||
5. Then go to **Network** > **Adapter 1**. Choose **Bridged Adapter** and choose your network adapter.
|
5. Then go to **Network** > **Adapter 1**. Choose **Bridged Adapter** and choose your network adapter (i.e. `en0:Wi-Fi`).
|
||||||
{% icon "mdi:alert-outline" %} Please keep in mind that the bridged
|
|
||||||
adapter only functions over a hardwired Ethernet connection.
|
|
||||||
Using Wi-Fi on your VirtualBox host is unsupported.
|
|
||||||
6. Then go to <b>Audio</b> and choose <b>Intel HD Audio</b> as audio controller.
|
6. Then go to <b>Audio</b> and choose <b>Intel HD Audio</b> as audio controller.
|
||||||
|
|
||||||
{% icon "mdi:alert-outline" %} By default, VirtualBox does not
|
{% icon "mdi:alert-outline" %} By default, VirtualBox does not
|
||||||
@ -484,6 +483,7 @@ With the Home Assistant Operating System installed and accessible, you can conti
|
|||||||
|
|
||||||
[generic-x86-64]: {{release_url}}/{{site.data.version_data.hassos['generic-x86-64']}}/haos_generic-x86-64-{{site.data.version_data.hassos['generic-x86-64']}}.img.xz
|
[generic-x86-64]: {{release_url}}/{{site.data.version_data.hassos['generic-x86-64']}}/haos_generic-x86-64-{{site.data.version_data.hassos['generic-x86-64']}}.img.xz
|
||||||
[vmdk]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/haos_ova-{{site.data.version_data.hassos['ova']}}.vmdk.zip
|
[vmdk]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/haos_ova-{{site.data.version_data.hassos['ova']}}.vmdk.zip
|
||||||
|
[vmdk_arch64]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/haos_generic-aarch64-{{site.data.version_data.hassos['ova']}}.vmdk.zip
|
||||||
[vhdx]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/haos_ova-{{site.data.version_data.hassos['ova']}}.vhdx.zip
|
[vhdx]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/haos_ova-{{site.data.version_data.hassos['ova']}}.vhdx.zip
|
||||||
[vdi]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/haos_ova-{{site.data.version_data.hassos['ova']}}.vdi.zip
|
[vdi]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/haos_ova-{{site.data.version_data.hassos['ova']}}.vdi.zip
|
||||||
[qcow2]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/haos_ova-{{site.data.version_data.hassos['ova']}}.qcow2.xz
|
[qcow2]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/haos_ova-{{site.data.version_data.hassos['ova']}}.qcow2.xz
|
||||||
|
|||||||
@ -1,19 +0,0 @@
|
|||||||
## Install Home Assistant Supervised
|
|
||||||
|
|
||||||
{% caution %}
|
|
||||||
|
|
||||||
This way of running Home Assistant will require the most of you. It also has strict requirements you need to follow.
|
|
||||||
|
|
||||||
Unless you really need this installation type, you should install Home Assistant OS (this can also be a [virtual machine](#install-home-assistant-operating-system)), or [Home Assistant Container](#install-home-assistant-container).
|
|
||||||
|
|
||||||
{% endcaution %}
|
|
||||||
|
|
||||||
1. First make sure you understand the <a href="https://github.com/home-assistant/architecture/blob/master/adr/0014-home-assistant-supervised.md" target="_blank">requirements</a>.
|
|
||||||
2. This installation method has very strict requirements, for example, it only
|
|
||||||
supports Debian (Ubuntu, Armbian, and Raspberry Pi OS are **not**
|
|
||||||
supported). So, make sure you understand the requirements from step 1 above.
|
|
||||||
3. Then head over to <a href="https://github.com/home-assistant/supervised-installer" target="_blank">home-assistant/supervised-installer</a> to set it up.
|
|
||||||
|
|
||||||
Once the {% term "Home Assistant Supervised" %} installation is running and Home Assistant is accessible you can continue with onboarding.
|
|
||||||
|
|
||||||
{% include getting-started/next_step.html step="Onboarding" link="/getting-started/onboarding/" %}
|
|
||||||
@ -10,7 +10,7 @@
|
|||||||
</iframe>
|
</iframe>
|
||||||
|
|
||||||
<a id="HAdemoScreenshot" href='https://demo.home-assistant.io/' target='_blank'>
|
<a id="HAdemoScreenshot" href='https://demo.home-assistant.io/' target='_blank'>
|
||||||
<img src="/images/frontpage/hero_screenshot.png" alt="Home Assistant screenshot">
|
<img src="/images/frontpage/hero_screenshot.png" alt="Home Assistant screenshot" fetchpriority="high">
|
||||||
</a>
|
</a>
|
||||||
|
|
||||||
<!-- <script>
|
<!-- <script>
|
||||||
|
|||||||
@ -151,17 +151,8 @@ apple_tv_sleep:
|
|||||||
target:
|
target:
|
||||||
entity_id: remote.lounge_appletv
|
entity_id: remote.lounge_appletv
|
||||||
data:
|
data:
|
||||||
hold_secs: 1
|
|
||||||
delay_secs: 1
|
|
||||||
command:
|
command:
|
||||||
- home
|
- suspend
|
||||||
- action: remote.send_command
|
|
||||||
target:
|
|
||||||
entity_id: remote.lounge_appletv
|
|
||||||
data:
|
|
||||||
delay_secs: 1
|
|
||||||
command:
|
|
||||||
- select
|
|
||||||
- action: media_player.turn_off
|
- action: media_player.turn_off
|
||||||
target:
|
target:
|
||||||
entity_id: media_player.lounge_appletv
|
entity_id: media_player.lounge_appletv
|
||||||
|
|||||||
@ -13,7 +13,82 @@ ha_integration_type: service
|
|||||||
ha_quality_scale: bronze
|
ha_quality_scale: bronze
|
||||||
---
|
---
|
||||||
|
|
||||||
The **AWS S3** {% term integrations %} allows you to use [AWS S3](https://aws.amazon.com/s3/) bucket with Home Assistant Backups.
|
The **AWS S3** {% term integration %} allows you to use [AWS S3](https://aws.amazon.com/s3/) bucket with Home Assistant Backups.
|
||||||
|
|
||||||
|
## Prerequisites
|
||||||
|
|
||||||
|
{% important %}
|
||||||
|
This integration is specifically designed to work **only with Amazon AWS S3** and not with third-party storage providers that claim S3 API compatibility. Third-party providers like Wasabi, DigitalOcean Spaces, Backblaze B2, Infomaniak, and others are not supported.
|
||||||
|
{% endimportant %}
|
||||||
|
|
||||||
|
This integration requires an existing S3 bucket and an IAM user that has access to that bucket. For security reasons, it is strongly recommended to scope the IAM policy as narrowly as possible to only the required operations and resources.
|
||||||
|
|
||||||
|
{% details "Create a new S3 bucket" %}
|
||||||
|
|
||||||
|
1. Log in to the [AWS Management Console](https://console.aws.amazon.com/).
|
||||||
|
1. Navigate to **S3** from the Services menu.
|
||||||
|
1. Click **Create bucket**.
|
||||||
|
1. Choose a unique **bucket name** (e.g., `home-assistant-backups-123456`).
|
||||||
|
1. Select your preferred AWS **region** (e.g., `eu-central-1`).
|
||||||
|
1. Adjust the settings:
|
||||||
|
- ✅ **Block all public access** (enabled by default, recommended)
|
||||||
|
- ⚠️ **Enable Bucket Versioning** (optional). This lets you recover backups after Home Assistant deletes them, but it **can increase storage costs**. Disable this to allow permanent deletion based on retention settings.
|
||||||
|
1. Click **Create bucket**.
|
||||||
|
|
||||||
|
Make a note of the bucket name — you’ll need it later.
|
||||||
|
|
||||||
|
{% enddetails %}
|
||||||
|
|
||||||
|
{% details "Create an IAM user" %}
|
||||||
|
|
||||||
|
To create a new IAM user that can access the S3 bucket:
|
||||||
|
|
||||||
|
1. Go to **IAM > Users** in the AWS Management Console.
|
||||||
|
1. Click **Add users**.
|
||||||
|
1. Use a name like `home-assistant-backup`.
|
||||||
|
1. Check **Access key - Programmatic access** only.
|
||||||
|
1. Click **Next: Permissions**.
|
||||||
|
|
||||||
|
Now, let's create and attach a custom IAM policy to give the user the necessary permissions to the bucket:
|
||||||
|
|
||||||
|
1. Click **Create policy**, go to the **JSON** tab, and paste the following (replace `YOUR_BUCKET_NAME`):
|
||||||
|
|
||||||
|
```json
|
||||||
|
{
|
||||||
|
"Version": "2012-10-17",
|
||||||
|
"Statement": [
|
||||||
|
{
|
||||||
|
"Sid": "AllowS3BackupOperations",
|
||||||
|
"Effect": "Allow",
|
||||||
|
"Action": [
|
||||||
|
"s3:ListBucket",
|
||||||
|
"s3:GetObject",
|
||||||
|
"s3:PutObject",
|
||||||
|
"s3:DeleteObject",
|
||||||
|
"s3:AbortMultipartUpload"
|
||||||
|
],
|
||||||
|
"Resource": [
|
||||||
|
"arn:aws:s3:::YOUR_BUCKET_NAME",
|
||||||
|
"arn:aws:s3:::YOUR_BUCKET_NAME/*"
|
||||||
|
]
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
1. Name the policy (e.g., `HomeAssistantS3Policy`) and create it.
|
||||||
|
1. Return to the user creation wizard and attach the new policy.
|
||||||
|
1. Complete the user setup.
|
||||||
|
1. Save the **Access Key ID** and **Secret Access Key** — you'll need these when setting up the AWS S3 integration in Home Assistant.
|
||||||
|
|
||||||
|
{% enddetails %}
|
||||||
|
|
||||||
|
{% note %}
|
||||||
|
|
||||||
|
- Avoid using credentials for your AWS root account or IAM users that have more permissions than is necessary.
|
||||||
|
- By limiting credentials to a specific bucket, you reduce risk and help keep your AWS account secure.
|
||||||
|
|
||||||
|
{% endnote %}
|
||||||
|
|
||||||
{% include integrations/config_flow.md %}
|
{% include integrations/config_flow.md %}
|
||||||
|
|
||||||
@ -28,6 +103,25 @@ Endpoint URL:
|
|||||||
description: "Endpoint URL provided to [Boto3 Session](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/core/session.html). Region-specific [AWS S3 endpoints](https://docs.aws.amazon.com/general/latest/gr/s3.html) are available in their documentation. Defaults to `https://s3.eu-central-1.amazonaws.com/`."
|
description: "Endpoint URL provided to [Boto3 Session](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/core/session.html). Region-specific [AWS S3 endpoints](https://docs.aws.amazon.com/general/latest/gr/s3.html) are available in their documentation. Defaults to `https://s3.eu-central-1.amazonaws.com/`."
|
||||||
{% endconfiguration_basic %}
|
{% endconfiguration_basic %}
|
||||||
|
|
||||||
|
## Setting up the AWS S3 integration in Home Assistant
|
||||||
|
|
||||||
|
1. In Home Assistant, go to **Settings > Devices & Services**.
|
||||||
|
1. Click **Add Integration** and search for **AWS S3**.
|
||||||
|
1. Enter the following details:
|
||||||
|
- Access Key ID and Secret Access Key from the IAM user
|
||||||
|
- Your bucket name
|
||||||
|
- The region endpoint (e.g., `https://s3.eu-central-1.amazonaws.com/`)
|
||||||
|
|
||||||
|
The integration will test the connection and confirm access to your S3 bucket.
|
||||||
|
|
||||||
|
## Known limitations
|
||||||
|
|
||||||
|
The AWS S3 integration has the following limitations:
|
||||||
|
|
||||||
|
### No support for third-party S3 API compatible providers
|
||||||
|
|
||||||
|
This integration is designed to work only with the official Amazon AWS S3 service. Despite claims of S3 API compatibility, third-party storage providers like Wasabi, DigitalOcean Spaces, Backblaze B2, Infomaniak, OVH Cloud, and others have often proven to be incompatible. Even when they appear to work initially, they cannot guarantee ongoing compatibility with this AWS S3 integration in the future.
|
||||||
|
|
||||||
## Removing the integration
|
## Removing the integration
|
||||||
|
|
||||||
This integration follows standard integration removal. No extra steps are required.
|
This integration follows standard integration removal. No extra steps are required.
|
||||||
|
|||||||
@ -27,7 +27,7 @@ related:
|
|||||||
title: backup emergency kit
|
title: backup emergency kit
|
||||||
---
|
---
|
||||||
|
|
||||||
The **Backup** {% term integration %} is used by all [installation types](/installation/#advanced-installation-methods) to create and restore backups.
|
The **Backup** {% term integration %} is used by all [installation types](/installation/#about-installation-methods) to create and restore backups.
|
||||||
|
|
||||||
To learn how to create and restore a backup, refer to the backup section under [common tasks](/common-tasks/general/#backups).
|
To learn how to create and restore a backup, refer to the backup section under [common tasks](/common-tasks/general/#backups).
|
||||||
|
|
||||||
@ -61,7 +61,7 @@ action: backup.create_automatic
|
|||||||
The {% my developer_call_service service="backup.create" %} action can be used
|
The {% my developer_call_service service="backup.create" %} action can be used
|
||||||
to create a backup of your Home Assistant instance.
|
to create a backup of your Home Assistant instance.
|
||||||
|
|
||||||
- This action is only available in [core and container installations](/installation/#advanced-installation-methods).
|
- This action is only available in [core and container installations](/installation/#about-installation-methods).
|
||||||
- The action has no additional options or parameters.
|
- The action has no additional options or parameters.
|
||||||
- The backup will only be saved on the local storage.
|
- The backup will only be saved on the local storage.
|
||||||
- The backup created with `backup.create` always includes the database.
|
- The backup created with `backup.create` always includes the database.
|
||||||
|
|||||||
@ -33,7 +33,7 @@ To use your MQTT cover in your installation, add the following to your {% term "
|
|||||||
# Example configuration.yaml entry
|
# Example configuration.yaml entry
|
||||||
mqtt:
|
mqtt:
|
||||||
- cover:
|
- cover:
|
||||||
command_topic: "home-assistant/cover/set"
|
command_topic: "living-room-cover/set"
|
||||||
```
|
```
|
||||||
|
|
||||||
{% configuration %}
|
{% configuration %}
|
||||||
@ -350,10 +350,10 @@ The example below shows a full configuration for a cover without tilt with state
|
|||||||
mqtt:
|
mqtt:
|
||||||
- cover:
|
- cover:
|
||||||
name: "MQTT Cover"
|
name: "MQTT Cover"
|
||||||
command_topic: "home-assistant/cover/set"
|
command_topic: "living-room-cover/set"
|
||||||
state_topic: "home-assistant/cover/state"
|
state_topic: "living-room-cover/state"
|
||||||
availability:
|
availability:
|
||||||
- topic: "home-assistant/cover/availability"
|
- topic: "living-room-cover/availability"
|
||||||
qos: 0
|
qos: 0
|
||||||
retain: true
|
retain: true
|
||||||
payload_open: "OPEN"
|
payload_open: "OPEN"
|
||||||
@ -382,11 +382,11 @@ The example below shows a full configuration for a cover without tilt with posit
|
|||||||
mqtt:
|
mqtt:
|
||||||
- cover:
|
- cover:
|
||||||
name: "MQTT Cover"
|
name: "MQTT Cover"
|
||||||
command_topic: "home-assistant/cover/set"
|
command_topic: "living-room-cover/set"
|
||||||
position_topic: "home-assistant/cover/position"
|
position_topic: "living-room-cover/position"
|
||||||
availability:
|
availability:
|
||||||
- topic: "home-assistant/cover/availability"
|
- topic: "living-room-cover/availability"
|
||||||
set_position_topic: "home-assistant/cover/set_position"
|
set_position_topic: "living-room-cover/set_position"
|
||||||
qos: 0
|
qos: 0
|
||||||
retain: true
|
retain: true
|
||||||
payload_open: "OPEN"
|
payload_open: "OPEN"
|
||||||
@ -413,11 +413,11 @@ The example below shows a full configuration for a cover with position, state &
|
|||||||
mqtt:
|
mqtt:
|
||||||
- cover:
|
- cover:
|
||||||
name: "MQTT Cover"
|
name: "MQTT Cover"
|
||||||
command_topic: "home-assistant/cover/set"
|
command_topic: "living-room-cover/set"
|
||||||
state_topic: "home-assistant/cover/state"
|
state_topic: "living-room-cover/state"
|
||||||
position_topic: "home-assistant/cover/position"
|
position_topic: "living-room-cover/position"
|
||||||
availability:
|
availability:
|
||||||
- topic: "home-assistant/cover/availability"
|
- topic: "living-room-cover/availability"
|
||||||
qos: 0
|
qos: 0
|
||||||
retain: true
|
retain: true
|
||||||
payload_open: "OPEN"
|
payload_open: "OPEN"
|
||||||
@ -432,8 +432,8 @@ mqtt:
|
|||||||
optimistic: false
|
optimistic: false
|
||||||
value_template: "{{ value.x }}"
|
value_template: "{{ value.x }}"
|
||||||
position_template: "{{ value.y }}"
|
position_template: "{{ value.y }}"
|
||||||
tilt_command_topic: "home-assistant/cover/tilt"
|
tilt_command_topic: "living-room-cover/tilt"
|
||||||
tilt_status_topic: "home-assistant/cover/tilt-state"
|
tilt_status_topic: "living-room-cover/tilt-state"
|
||||||
tilt_status_template: "{{ value_json["PWM"]["PWM1"] }}"
|
tilt_status_template: "{{ value_json["PWM"]["PWM1"] }}"
|
||||||
tilt_min: 0
|
tilt_min: 0
|
||||||
tilt_max: 180
|
tilt_max: 180
|
||||||
@ -454,11 +454,11 @@ The example below shows a full configuration for a cover using stopped state.
|
|||||||
mqtt:
|
mqtt:
|
||||||
- cover:
|
- cover:
|
||||||
name: "MQTT Cover"
|
name: "MQTT Cover"
|
||||||
command_topic: "home-assistant/cover/set"
|
command_topic: "living-room-cover/set"
|
||||||
state_topic: "home-assistant/cover/state"
|
state_topic: "living-room-cover/state"
|
||||||
position_topic: "home-assistant/cover/position"
|
position_topic: "living-room-cover/position"
|
||||||
availability:
|
availability:
|
||||||
- topic: "home-assistant/cover/availability"
|
- topic: "living-room-cover/availability"
|
||||||
qos: 0
|
qos: 0
|
||||||
retain: true
|
retain: true
|
||||||
payload_open: "OPEN"
|
payload_open: "OPEN"
|
||||||
@ -523,10 +523,10 @@ The example below shows an example of how to correct the state of the blind depe
|
|||||||
mqtt:
|
mqtt:
|
||||||
- cover:
|
- cover:
|
||||||
name: "MQTT Cover"
|
name: "MQTT Cover"
|
||||||
command_topic: "home-assistant/cover/set"
|
command_topic: "living-room-cover/set"
|
||||||
state_topic: "home-assistant/cover/state"
|
state_topic: "living-room-cover/state"
|
||||||
position_topic: "home-assistant/cover/position"
|
position_topic: "living-room-cover/position"
|
||||||
set_position_topic: "home-assistant/cover/position/set"
|
set_position_topic: "living-room-cover/position/set"
|
||||||
payload_open: "open"
|
payload_open: "open"
|
||||||
payload_close: "close"
|
payload_close: "close"
|
||||||
payload_stop: "stop"
|
payload_stop: "stop"
|
||||||
@ -569,11 +569,11 @@ Following variable might be used in `position_template`, `set_position_template`
|
|||||||
mqtt:
|
mqtt:
|
||||||
- cover:
|
- cover:
|
||||||
name: "MQTT Cover"
|
name: "MQTT Cover"
|
||||||
command_topic: "home-assistant/cover/set"
|
command_topic: "living-room-cover/set"
|
||||||
state_topic: "home-assistant/cover/state"
|
state_topic: "living-room-cover/state"
|
||||||
position_topic: "home-assistant/cover/position"
|
position_topic: "living-room-cover/position"
|
||||||
set_position_topic: "home-assistant/cover/position/set"
|
set_position_topic: "living-room-cover/position/set"
|
||||||
tilt_command_topic: "home-assistant/cover/position/set" # same as `set_position_topic`
|
tilt_command_topic: "living-room-cover/position/set" # same as `set_position_topic`
|
||||||
qos: 1
|
qos: 1
|
||||||
retain: false
|
retain: false
|
||||||
payload_open: "open"
|
payload_open: "open"
|
||||||
@ -625,5 +625,5 @@ mqtt:
|
|||||||
To test, you can use the command line tool `mosquitto_pub` shipped with `mosquitto` or the `mosquitto-clients` package to send MQTT messages. This allows you to operate your cover manually:
|
To test, you can use the command line tool `mosquitto_pub` shipped with `mosquitto` or the `mosquitto-clients` package to send MQTT messages. This allows you to operate your cover manually:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
mosquitto_pub -h 127.0.0.1 -t home-assistant/cover/set -m "CLOSE"
|
mosquitto_pub -h 127.0.0.1 -t living-room-cover/set -m "CLOSE"
|
||||||
```
|
```
|
||||||
|
|||||||
@ -714,6 +714,20 @@ Envoy Metered without installed CT, running older firmware versions, reportedly
|
|||||||
|
|
||||||
{% enddetails %}
|
{% enddetails %}
|
||||||
|
|
||||||
|
### Lifetime energy production decreases by 1.2 MWh
|
||||||
|
|
||||||
|
Envoy Standard (not Metered), running firmware 8.2.4264, reportedly decreases the **Lifetime energy production** value by 1.2 MWh at irregular times. The current hypothesis is that the step change occurs when one of the inverters exceeds a lifetime value of 1.2 MWh and resets to zero. This leads to the decrease with 1.2 MWh in the aggregated value for all inverters. It's not clear if this also happens for the metered Envoy.
|
||||||
|
|
||||||
|
{% details "History example for Envoy Lifetime energy production value decrease" %}
|
||||||
|
|
||||||
|
The example below shows decreases when multiple inverters reach a 1.2 MWh lifetime value over time. This would typically occur after some year(s) lifetime and then spread over some months based on individual solar panel production variations.
|
||||||
|
<figure>
|
||||||
|
<img src="/images/integrations/enphase_envoy/enphase_envoy_production_decrease.png" alt="envoy lifetime energy production decrease">
|
||||||
|
<figcaption>Envoy Lifetime energy production value decrease.</figcaption>
|
||||||
|
</figure>
|
||||||
|
|
||||||
|
{% enddetails %}
|
||||||
|
|
||||||
### Summed Voltage
|
### Summed Voltage
|
||||||
|
|
||||||
The Envoy Metered in multiphase setup, sums the voltages of the phases measured on the CT for the aggregated data. This may be valid for split-phase, but for 3-phase systems, use the individual phases rather than the summed value.
|
The Envoy Metered in multiphase setup, sums the voltages of the phases measured on the CT for the aggregated data. This may be valid for split-phase, but for 3-phase systems, use the individual phases rather than the summed value.
|
||||||
|
|||||||
@ -15,7 +15,11 @@ related:
|
|||||||
ha_quality_scale: legacy
|
ha_quality_scale: legacy
|
||||||
---
|
---
|
||||||
|
|
||||||
The `fail2ban` {% term integration %} allows for IPs banned by [fail2ban](https://www.fail2ban.org/wiki/index.php/Main_Page) to be displayed in the Home Assistant frontend.
|
The Fail2Ban {% term integration %} allows for IPs banned by [fail2ban](https://www.fail2ban.org/wiki/index.php/Main_Page) to be displayed in the Home Assistant frontend.
|
||||||
|
|
||||||
|
{% important %}
|
||||||
|
This integration is only available on {% term "Home Assistant Core" %} installation types. Unfortunately, it cannot be used with {% term "Home Assistant Operating System" %}, {% term "Home Assistant Supervised" %}, or {% term "Home Assistant Container" %}.
|
||||||
|
{% endimportant %}
|
||||||
|
|
||||||
{% important %}
|
{% important %}
|
||||||
|
|
||||||
|
|||||||
@ -5,6 +5,7 @@ ha_category:
|
|||||||
- Binary sensor
|
- Binary sensor
|
||||||
- Sensor
|
- Sensor
|
||||||
- Switch
|
- Switch
|
||||||
|
- Water management
|
||||||
ha_config_flow: true
|
ha_config_flow: true
|
||||||
ha_codeowners:
|
ha_codeowners:
|
||||||
- '@dmulcahey'
|
- '@dmulcahey'
|
||||||
|
|||||||
@ -103,7 +103,7 @@ The example above defines red color for open garage doors and brown color for in
|
|||||||
|
|
||||||
### Unsupported theme variables
|
### Unsupported theme variables
|
||||||
|
|
||||||
Although we do our best to keep things working, the behavior of other theme variables can change between releases. For a partial list of variables used by the main frontend see [ha-style.ts](https://github.com/home-assistant/frontend/blob/master/src/resources/ha-style.ts).
|
Although we do our best to keep things working, the behavior of other theme variables can change between releases. For a partial list of variables used by the main frontend see [color.globals.ts](https://github.com/home-assistant/frontend/blob/master/src/resources/theme/color.globals.ts).
|
||||||
|
|
||||||
### Dark mode support
|
### Dark mode support
|
||||||
|
|
||||||
|
|||||||
@ -23,7 +23,6 @@ To enable local control on your Govee device, refer to the instructions availabl
|
|||||||
## Supported devices
|
## Supported devices
|
||||||
|
|
||||||
H6008,
|
H6008,
|
||||||
H600D,
|
|
||||||
H6022,
|
H6022,
|
||||||
H6042,
|
H6042,
|
||||||
H6046,
|
H6046,
|
||||||
|
|||||||
@ -12,7 +12,7 @@ ha_integration_type: hardware
|
|||||||
|
|
||||||
The Home Assistant Green integration provides hardware information for the hardware configuration page.
|
The Home Assistant Green integration provides hardware information for the hardware configuration page.
|
||||||
|
|
||||||
For documentation on the Home Assistant Green, please visit the [documentation page](https://green.home-assistant.io/).
|
For documentation on the Home Assistant Green, please visit the [documentation page](https://support.nabucasa.com/hc/en-us/categories/24638797677853-Home-Assistant-Green).
|
||||||
If you are looking to buy one, please visit the [product page](https://home-assistant.io/green).
|
If you are looking to buy one, please visit the [product page](https://home-assistant.io/green).
|
||||||
|
|
||||||
## Configuration
|
## Configuration
|
||||||
|
|||||||
@ -16,7 +16,7 @@ ha_platforms:
|
|||||||
|
|
||||||
The Home Assistant Connect ZBT-1 integration provides hardware information for the hardware configuration page.
|
The Home Assistant Connect ZBT-1 integration provides hardware information for the hardware configuration page.
|
||||||
|
|
||||||
For documentation on the Home Assistant Connect ZBT-1, please visit the [documentation page](https://connectzbt1.home-assistant.io/documentation/).
|
For documentation on the Home Assistant Connect ZBT-1, please visit the [documentation page](https://support.nabucasa.com/hc/en-us/categories/24734620813469).
|
||||||
If you are looking to buy one, please visit the [product page](https://home-assistant.io/connectzbt1)
|
If you are looking to buy one, please visit the [product page](https://home-assistant.io/connectzbt1)
|
||||||
|
|
||||||
## Configuration
|
## Configuration
|
||||||
|
|||||||
@ -15,7 +15,7 @@ ha_platforms:
|
|||||||
|
|
||||||
The Home Assistant Yellow integration provides hardware information for the hardware configuration page.
|
The Home Assistant Yellow integration provides hardware information for the hardware configuration page.
|
||||||
|
|
||||||
For documentation on the Home Assistant Yellow, please visit the [documentation](https://yellow.home-assistant.io/documentation/).
|
For documentation on the Home Assistant Yellow, please visit the [documentation](https://support.nabucasa.com/hc/en-us/categories/24734575925149-Home-Assistant-Yellow).
|
||||||
If you are looking to buy one, please visit the [product page](https://home-assistant.io/yellow).
|
If you are looking to buy one, please visit the [product page](https://home-assistant.io/yellow).
|
||||||
|
|
||||||
## Configuration
|
## Configuration
|
||||||
|
|||||||
@ -425,7 +425,7 @@ The following integrations are currently supported:
|
|||||||
| Integration | Type Name | Description |
|
| Integration | Type Name | Description |
|
||||||
| ------------------------------------------------------------- | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
| ------------------------------------------------------------- | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||||
| alarm_control_panel | SecuritySystem | All security systems. |
|
| alarm_control_panel | SecuritySystem | All security systems. |
|
||||||
| automation / input_boolean / lawn_mower / remote / scene / script / vacuum | Switch | All represented as switches. |
|
| automation / button / input_boolean / input_button / lawn_mower / remote / scene / script / vacuum | Switch | All represented as switches. |
|
||||||
| input_select / select | Switch | Represented as a power strip with buttons for each option. |
|
| input_select / select | Switch | Represented as a power strip with buttons for each option. |
|
||||||
| binary_sensor | Sensor | Support for `co2`, `door`, `garage_door`, `gas`, `moisture`, `motion`, `occupancy`, `opening`, `smoke` and `window` device classes. Defaults to the `occupancy` device class for everything else. |
|
| binary_sensor | Sensor | Support for `co2`, `door`, `garage_door`, `gas`, `moisture`, `motion`, `occupancy`, `opening`, `smoke` and `window` device classes. Defaults to the `occupancy` device class for everything else. |
|
||||||
| camera | Camera | All camera devices. **HomeKit Secure Video is not supported at this time.** |
|
| camera | Camera | All camera devices. **HomeKit Secure Video is not supported at this time.** |
|
||||||
|
|||||||
@ -138,8 +138,8 @@ This section describes how to add it via Home Assistant's preferred {% term Thre
|
|||||||
- Make sure your Home Assistant device is on the same network (LAN) as the border router.
|
- Make sure your Home Assistant device is on the same network (LAN) as the border router.
|
||||||
- Make sure the {% term Thread %} network you'd like to use is known by Home Assistant and marked as **Preferred network** in the {% term Thread %} configuration.
|
- Make sure the {% term Thread %} network you'd like to use is known by Home Assistant and marked as **Preferred network** in the {% term Thread %} configuration.
|
||||||
- If you have a Home Assistant Yellow or Connect ZBT-1, you can enable Thread to set up an Open Thread border router and with that a {% term Thread %} network.
|
- If you have a Home Assistant Yellow or Connect ZBT-1, you can enable Thread to set up an Open Thread border router and with that a {% term Thread %} network.
|
||||||
- Documentation on [enabling Thread on Yellow](https://yellow.home-assistant.io/procedures/enable-thread/)
|
- Documentation on [enabling Thread on Yellow](https://support.nabucasa.com/hc/en-us/articles/25742476767517)
|
||||||
- Documentation on [enabling Thread on Connect ZBT-1](https://connectzbt1.home-assistant.io/procedures/enable-thread/)
|
- Documentation on [enabling Thread on Connect ZBT-1](https://support.nabucasa.com/hc/en-us/articles/26124710072861)
|
||||||
|
|
||||||
#### To add a HomeKit device to a Thread network via Home Assistant
|
#### To add a HomeKit device to a Thread network via Home Assistant
|
||||||
|
|
||||||
|
|||||||
@ -2475,7 +2475,7 @@ entity_category:
|
|||||||
|
|
||||||
## Known limitations
|
## Known limitations
|
||||||
|
|
||||||
- The integration aims to be compatible with a wide variety of KNX devices from different manufacturers and eras. However, there are some devices that use non-standard <abbr title="data point type">DPT</abbr> or use telegrams in a proprietary way. In these cases, you might not be able to configure {% term entities %} directly through this integration. However, you may still use [Template entities](integrations/template/) with the [KNX telegram trigger](#telegram-trigger) to work around this.
|
- The integration aims to be compatible with a wide variety of KNX devices from different manufacturers and eras. However, there are some devices that use non-standard <abbr title="data point type">DPT</abbr> or use telegrams in a proprietary way. In these cases, you might not be able to configure {% term entities %} directly through this integration. However, you may still use [Template entities](/integrations/template/) with the [KNX telegram trigger](#telegram-trigger) to work around this.
|
||||||
|
|
||||||
- USB bus interfaces are not directly supported by the underlying [`xknx` library](https://github.com/XKNX/xknx). However, you could try to run a software KNX router such as `Calimero` or `knxd` alongside Home Assistant to serve as a USB to IP bridge. For best reliability, using a certified KNX IP interface or router is recommended.
|
- USB bus interfaces are not directly supported by the underlying [`xknx` library](https://github.com/XKNX/xknx). However, you could try to run a software KNX router such as `Calimero` or `knxd` alongside Home Assistant to serve as a USB to IP bridge. For best reliability, using a certified KNX IP interface or router is recommended.
|
||||||
|
|
||||||
|
|||||||
@ -89,6 +89,7 @@ Support LG Appliances as follows:
|
|||||||
- Water Heater
|
- Water Heater
|
||||||
- Water Purifier
|
- Water Purifier
|
||||||
- Wine Cellar
|
- Wine Cellar
|
||||||
|
- Ventilator
|
||||||
|
|
||||||
## Platforms
|
## Platforms
|
||||||
|
|
||||||
@ -97,6 +98,7 @@ LG ThinQ represents devices as a set of properties. And these are mapped to enti
|
|||||||
A list of all Entity Platforms provided by LG ThinQ Integration:
|
A list of all Entity Platforms provided by LG ThinQ Integration:
|
||||||
|
|
||||||
- [Binary sensor](#binary-sensor)
|
- [Binary sensor](#binary-sensor)
|
||||||
|
- [Button](#button)
|
||||||
- [Climate](#climate)
|
- [Climate](#climate)
|
||||||
- [Event](#event)
|
- [Event](#event)
|
||||||
- [Fan](#fan)
|
- [Fan](#fan)
|
||||||
@ -122,6 +124,15 @@ A read-only property which has only two states that can be toggled is represente
|
|||||||
| Water Heater | Power |
|
| Water Heater | Power |
|
||||||
| Wine Cellar | Sabbath |
|
| Wine Cellar | Sabbath |
|
||||||
|
|
||||||
|
### Button
|
||||||
|
|
||||||
|
A writable property which has only two states that can be toggled is represented as a binary sensor platform.
|
||||||
|
|
||||||
|
| Device |Property |Action |
|
||||||
|
| ------ |-------- | ------ |
|
||||||
|
| Dish Washer | Operation | Start / Pause |
|
||||||
|
| Dryer<br>Styler<br>Washer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Operation | Start / Pause |
|
||||||
|
|
||||||
### Climate
|
### Climate
|
||||||
|
|
||||||
The properties for controlling both the temperature and wind strength of the appliance are represented as a climate platform.
|
The properties for controlling both the temperature and wind strength of the appliance are represented as a climate platform.
|
||||||
@ -177,6 +188,7 @@ A read-write property which has a numeric value is represented as a number platf
|
|||||||
| Dryer<br>Styler<br>Washer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Delayed start/end |
|
| Dryer<br>Styler<br>Washer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Delayed start/end |
|
||||||
| Water Heater | Temperature |
|
| Water Heater | Temperature |
|
||||||
| Wine Cellar | Light<br>Temperature |
|
| Wine Cellar | Light<br>Temperature |
|
||||||
|
| Ventilator | Sleep timer |
|
||||||
|
|
||||||
### Select
|
### Select
|
||||||
|
|
||||||
@ -187,14 +199,15 @@ A writable property which has a list of selectable values is represented as a se
|
|||||||
| Air Conditioner | Air purify<br>Air quality sensor |
|
| Air Conditioner | Air purify<br>Air quality sensor |
|
||||||
| Air Purifier| Operating mode<br>Speed |
|
| Air Purifier| Operating mode<br>Speed |
|
||||||
| Air Purifier Fan | Display brightness<br>Operating mode<br>Rotation<br>Speed |
|
| Air Purifier Fan | Display brightness<br>Operating mode<br>Rotation<br>Speed |
|
||||||
| Dehumidifier | Speed |
|
| Dehumidifier | Speed<br>Operation |
|
||||||
| Dish Washer | Operation |
|
| Dish Washer | Operation |
|
||||||
| Humidifier | Display brightness<br>Drying mode<br>Operating mode<br>Speed |
|
| Humidifier | Display brightness<br>Drying mode<br>Operating mode<br>Speed |
|
||||||
| Oven | Cook mode<br>Operation<br> |
|
| Oven | Cook mode<br>Operation |
|
||||||
| Refrigerator | Fresh air filter |
|
| Refrigerator | Fresh air filter |
|
||||||
| Dryer<br>Styler<br>Washer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Operation |
|
| Dryer<br>Styler<br>Washer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Operation |
|
||||||
| Water Heater | Operating mode |
|
| Water Heater | Operating mode |
|
||||||
| Wine Cellar | Light<br>Operating mode |
|
| Wine Cellar | Light<br>Operating mode |
|
||||||
|
| Ventilator | Speed<br>Operating mode |
|
||||||
|
|
||||||
### Switch
|
### Switch
|
||||||
|
|
||||||
@ -202,14 +215,17 @@ A read-write property which has only two states that can be toggled is represent
|
|||||||
|
|
||||||
| Device | Property |
|
| Device | Property |
|
||||||
| ------ | -------- |
|
| ------ | -------- |
|
||||||
| Air Conditioner | Power<br>Lighting<br>Energy saving |
|
| Air Conditioner | Power<br>Lighting<br>Energy saving<br>Air clean |
|
||||||
| Air Purifier | Power |
|
| Air Purifier | Power |
|
||||||
| Air Purifier Fan | Heating<br>Power<br>UVnano |
|
| Air Purifier Fan | Heating<br>Power<br>UVnano |
|
||||||
| Dehumidifier | Power |
|
| Dehumidifier | Power |
|
||||||
|
| Dish Washer | Power |
|
||||||
|
| Dryer<br>Styler<br>Washer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Power |
|
||||||
| Humidifier | Auto mode<br>Heating<br>Mood light<br>Power<br>Sleep mode |
|
| Humidifier | Auto mode<br>Heating<br>Mood light<br>Power<br>Sleep mode |
|
||||||
| Refrigerator | Express mode<br>Express cool<br>Quick freeze |
|
| Refrigerator | Express mode<br>Express cool<br>Quick freeze |
|
||||||
| System Boiler | Power<br>Hot water |
|
| System Boiler | Power<br>Hot water |
|
||||||
| Wine Cellar | Ventilation |
|
| Wine Cellar | Ventilation |
|
||||||
|
| Ventilator | Power |
|
||||||
|
|
||||||
### Vacuum
|
### Vacuum
|
||||||
|
|
||||||
@ -234,13 +250,13 @@ A read-only property which has states is represented as a sensor platform.
|
|||||||
| Device | Property |
|
| Device | Property |
|
||||||
| ------ | -------- |
|
| ------ | -------- |
|
||||||
| Air Conditioner | Filter remaining<br>Humidity<br>Odor<br>Overall air quality<br>PM1<br>PM10<br>PM2.5<br>Schedule turn-off<br>Schedule turn-on<br>Sleep timer |
|
| Air Conditioner | Filter remaining<br>Humidity<br>Odor<br>Overall air quality<br>PM1<br>PM10<br>PM2.5<br>Schedule turn-off<br>Schedule turn-on<br>Sleep timer |
|
||||||
| Air Purifier| Air quality sensor<br>Humidity<br>Odor<br>Operating mode<br>Overall air quality<br>Personal mode<br>PM1<br>PM10<br>PM2.5<br>Filter remaining<br>Schedule turn-off<br>Schedule turn-on |
|
| Air Purifier| Humidity<br>Odor<br>Operating mode<br>Overall air quality<br>Personal mode<br>PM1<br>PM10<br>PM2.5<br>Filter remaining<br>Schedule turn-off<br>Schedule turn-on |
|
||||||
| Air Purifier Fan | Air quality sensor<br>Humidity<br>Odor<br>Overall air quality<br>PM1<br>PM10<br>PM2.5<br>Sleep timer<br>Temperature<br>Schedule turn-off<br>Schedule turn-on |
|
| Air Purifier Fan | Humidity<br>Odor<br>Overall air quality<br>PM1<br>PM10<br>PM2.5<br>Sleep timer<br>Temperature<br>Schedule turn-off<br>Schedule turn-on |
|
||||||
| Cooktop | Current status<br>Power level |
|
| Cooktop | Current status<br>Power level<br>Remaining time |
|
||||||
| Dehumidifier | Humidity<br>Operating mode |
|
| Dehumidifier | Humidity<br>Operating mode |
|
||||||
| Dish Washer | Current cycle<br>Current status<br>Rinse aid dispenser level<br>Softening level<br>Delayed start<br>Remaining time<br>Total time |
|
| Dish Washer | Current cycle<br>Current status<br>Rinse aid dispenser level<br>Softening level<br>Delayed start<br>Remaining time<br>Total time |
|
||||||
| Home Brew| Brewing duration<br>Brewing period<br>Current status<br>First flavor<br>Second flavor<br>Homebrew recipe<br>First hop<br>Second hop<br>Recipe progress<br>Wort<br>Yeast |
|
| Home Brew| Brewing duration<br>Brewing period<br>Current status<br>First flavor<br>Second flavor<br>Homebrew recipe<br>First hop<br>Second hop<br>Recipe progress<br>Wort<br>Yeast |
|
||||||
| Humidifier | Air quality sensor<br>Humidity<br>Overall air quality<br>PM1<br>PM10<br>PM2.5<br>Schedule turn-off<br>Schedule turn-on<br>Sleep timer<br>Temperature |
|
| Humidifier | Humidity<br>Overall air quality<br>PM1<br>PM10<br>PM2.5<br>Schedule turn-off<br>Schedule turn-on<br>Sleep timer<br>Temperature |
|
||||||
| Kimchi Refrigerator | Fresh air filter<br>Temperature |
|
| Kimchi Refrigerator | Fresh air filter<br>Temperature |
|
||||||
| Microwave Oven | Current status |
|
| Microwave Oven | Current status |
|
||||||
| Oven | Current status<br>Temperature |
|
| Oven | Current status<br>Temperature |
|
||||||
@ -251,6 +267,7 @@ A read-only property which has states is represented as a sensor platform.
|
|||||||
| System Boiler | Indoor temperature<br>Inlet temperature<br>Outlet temperature |
|
| System Boiler | Indoor temperature<br>Inlet temperature<br>Outlet temperature |
|
||||||
| Water Purifier | High-temp sterilization<br>Type<br>UVnano|
|
| Water Purifier | High-temp sterilization<br>Type<br>UVnano|
|
||||||
| Dryer<br>Styler<br>Washer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Current status<br>Delayed start/end<br>Remaining time<br>Total time<br>Cycles |
|
| Dryer<br>Styler<br>Washer<br>Washcombo Main<br>Washcombo Mini<br>Washtower<br>Washtower Dryer<br>Washtower Washer | Current status<br>Delayed start/end<br>Remaining time<br>Total time<br>Cycles |
|
||||||
|
| Ventilator | Carbon dioxide<br>PM1<br>PM10<br>PM2.5<br>Sleep timer<br>Temperature<br>Schedule turn-off<br>Schedule turn-on |
|
||||||
|
|
||||||
## Automation example
|
## Automation example
|
||||||
|
|
||||||
|
|||||||
@ -224,22 +224,16 @@ When the configuration entry is loaded or after a streaming error (for example a
|
|||||||
|
|
||||||
## Troubleshooting
|
## Troubleshooting
|
||||||
|
|
||||||
### Unavailable entities for a device
|
{% details "Problem: Unavailable entities for a device" %}
|
||||||
|
|
||||||
#### Symptom: "The entities related to an appliance were available but no longer are"
|
|
||||||
|
|
||||||
After reloading the Miele integration, the entities related to an appliance that used to be available are no longer available.
|
After reloading the Miele integration, the entities related to an appliance that used to be available are no longer available.
|
||||||
|
|
||||||
##### Description
|
|
||||||
|
|
||||||
Unavailable entities can have multiple causes:
|
Unavailable entities can have multiple causes:
|
||||||
|
|
||||||
- The appliance is turned off. When it is turned off, the appliance is disconnected and the API does not retrieve information about the appliance.
|
- The appliance is turned off. When it is turned off, the appliance is disconnected and the API does not retrieve information about the appliance.
|
||||||
- The appliance is experiencing a network issue.
|
- The appliance is experiencing a network issue.
|
||||||
- The Miele API is experiencing issues.
|
- The Miele API is experiencing issues.
|
||||||
|
|
||||||
##### Resolution
|
|
||||||
|
|
||||||
To try to solve the above issues, follow these steps:
|
To try to solve the above issues, follow these steps:
|
||||||
|
|
||||||
1. Turn on the appliance and reload the Miele integration.
|
1. Turn on the appliance and reload the Miele integration.
|
||||||
@ -252,6 +246,16 @@ To try to solve the above issues, follow these steps:
|
|||||||
- [Miele service and contact](https://www.miele.com/)
|
- [Miele service and contact](https://www.miele.com/)
|
||||||
- [Miele developer Help & Support](https://www.miele.com/developer)
|
- [Miele developer Help & Support](https://www.miele.com/developer)
|
||||||
|
|
||||||
|
{% enddetails %}
|
||||||
|
|
||||||
|
{% details "Problem: Program or program phase is unknown" %}
|
||||||
|
|
||||||
|
The most common cause is that the code presented by the API is unknown to the integration. Details of the missing code can be found in the Home Assistant log or in the diagnostic file. Please open an issue on GitHub with the details from the logs. Please also include information on the program or program phase that was active when the message occurred.
|
||||||
|
|
||||||
|
Unknown can also be displayed if the state is reported as unknown by the API, usually caused by a temporary malfunction in the cloud service.
|
||||||
|
|
||||||
|
{% enddetails %}
|
||||||
|
|
||||||
## Removing the integration
|
## Removing the integration
|
||||||
|
|
||||||
This integration follows standard integration removal. If you have entered your own credentials, you will be asked if you want to keep them or delete them. If you want to delete them later you can do that from the tree-dot menu in {% my integrations title="**Settings** > **Devices & services**" %}.
|
This integration follows standard integration removal. If you have entered your own credentials, you will be asked if you want to keep them or delete them. If you want to delete them later you can do that from the tree-dot menu in {% my integrations title="**Settings** > **Devices & services**" %}.
|
||||||
|
|||||||
@ -24,6 +24,18 @@ The {% term integration %} provides the public market prices displayed on the [N
|
|||||||
|
|
||||||
Most European energy is traded via the Nord Pool Group marketplace. If your energy provider doesn't have a dedicated Home Assistant integration and you have a spot-price-based contract, you can use the **Nord Pool** {% term integration %}. This integration provides spot prices for your selected market, which you can, as an example, use in a {% term template %} to calculate prices for your [energy dashboard](#energy-dashboard).
|
Most European energy is traded via the Nord Pool Group marketplace. If your energy provider doesn't have a dedicated Home Assistant integration and you have a spot-price-based contract, you can use the **Nord Pool** {% term integration %}. This integration provides spot prices for your selected market, which you can, as an example, use in a {% term template %} to calculate prices for your [energy dashboard](#energy-dashboard).
|
||||||
|
|
||||||
|
{% important %}
|
||||||
|
|
||||||
|
The energy market is transitioning to 15-minute <abbr title="market time unit">MTU</abbr> instead of 60-minute MTU.
|
||||||
|
|
||||||
|
When this finally occurs, the **Nord Pool** {% term integration %} will automatically switch and use the 15-minute <abbr title="market time unit">MTU</abbr>. This means during the transition, you may have a current price which is hourly based and a future price that is a 15-minute price.
|
||||||
|
|
||||||
|
If you use this integration to calculate your own energy cost, it is advisable to see how this affects you. Check if any automations, templates, or other settings might need to be modified accordingly.
|
||||||
|
|
||||||
|
You can read more and monitor the timeline [on the page about the transition to 15-minute MTU by Nordpool](https://www.nordpoolgroup.com/en/trading/transition-to-15-minute-market-time-unit-mtu/)
|
||||||
|
|
||||||
|
{% endimportant %}
|
||||||
|
|
||||||
{% include integrations/config_flow.md %}
|
{% include integrations/config_flow.md %}
|
||||||
|
|
||||||
{% configuration_basic %}
|
{% configuration_basic %}
|
||||||
@ -125,7 +137,9 @@ Currency:
|
|||||||
|
|
||||||
The public API only allows us to see past pricing information for up to 2 months.
|
The public API only allows us to see past pricing information for up to 2 months.
|
||||||
|
|
||||||
Tomorrow's prices are typically released around 13:00 CET, and trying to get them before that time will generate an error that needs to be considered in such a case.
|
Although Nord Pool operates in the CET/CEST timezone, all data is returned in UTC. Depending on how the data is consumed or manipulated, you may need to consider this.
|
||||||
|
|
||||||
|
Tomorrow's prices are typically released around 13:00 CET/CEST, and trying to get them before that time will generate an error that needs to be considered in such a case.
|
||||||
|
|
||||||
{% endnote %}
|
{% endnote %}
|
||||||
|
|
||||||
|
|||||||
@ -35,9 +35,11 @@ The ntfy integration can be used to send push notifications from automations and
|
|||||||
- Use `https://ntfy.sh` for the official ntfy service.
|
- Use `https://ntfy.sh` for the official ntfy service.
|
||||||
- Provide the URL of an alternative public ntfy service or your self-hosted instance (for example, `https://your-ntfy-instance.com`).
|
- Provide the URL of an alternative public ntfy service or your self-hosted instance (for example, `https://your-ntfy-instance.com`).
|
||||||
|
|
||||||
2. **Authentication**
|
2. **Authentication (optional)**
|
||||||
|
|
||||||
Depending on whether the server is configured to support access control, some topics may be read/write protected so that only users with the correct credentials can subscribe or publish to them. To publish/subscribe to protected topics, you can provide a username and password.
|
Depending on whether the server is configured to support access control, some topics may be read/write protected so that only users with the correct credentials can subscribe or publish to them.
|
||||||
|
|
||||||
|
The **ntfy** integration uses **access token** authentication to access protected topics. When you provide your ntfy username and password, Home Assistant automatically generates and uses an access token for authentication.
|
||||||
|
|
||||||
3. **Adding a topic**
|
3. **Adding a topic**
|
||||||
|
|
||||||
@ -99,6 +101,20 @@ data:
|
|||||||
|
|
||||||
{% enddetails %}
|
{% enddetails %}
|
||||||
|
|
||||||
|
## Known limitations
|
||||||
|
|
||||||
|
**ntfy** imposes various rate and usage limits. The official [ntfy.sh](https://ntfy.sh/) service allows up to **60 messages in a burst**, with a **replenishment rate of one message every 5 seconds** (i.e., the full 60-message capacity refills in 5 minutes).
|
||||||
|
|
||||||
|
Additional usage limits depend on your account tier. To view your current limits, go to [**Account → Usage**](https://ntfy.sh/account).
|
||||||
|
|
||||||
|
Limits may vary when using other **ntfy** services. If you're using a self-hosted instance, you can configure higher limits or disable them entirely.
|
||||||
|
|
||||||
|
## Troubleshooting
|
||||||
|
|
||||||
|
The **ntfy** integration relies on an active internet connection to communicate with the ntfy service. If you encounter issues, verify that your network connection is stable and the ntfy service is reachable. Additionally, the ntfy service itself may experience downtime, whether unexpected or due to scheduled maintenance.
|
||||||
|
|
||||||
|
In any case, when reporting an issue, please enable [debug logging](/docs/configuration/troubleshooting/#debug-logs-and-diagnostics), restart the integration, and as soon as the issue reoccurs, stop the debug logging again (*download of debug log file will start automatically*). Further, if still possible, please also download the [diagnostics](/integrations/diagnostics) data. If you have collected the debug log and the diagnostics data, provide them with the issue report.
|
||||||
|
|
||||||
## Removing the integration
|
## Removing the integration
|
||||||
|
|
||||||
This integration can be removed by following these steps:
|
This integration can be removed by following these steps:
|
||||||
|
|||||||
@ -12,8 +12,6 @@ ha_platforms:
|
|||||||
- lock
|
- lock
|
||||||
ha_iot_class: Local Push
|
ha_iot_class: Local Push
|
||||||
ha_integration_type: virtual
|
ha_integration_type: virtual
|
||||||
works_with:
|
|
||||||
- matter
|
|
||||||
ha_iot_standard:
|
ha_iot_standard:
|
||||||
- matter
|
- matter
|
||||||
---
|
---
|
||||||
|
|||||||
@ -156,7 +156,7 @@ The following diagnostic sensors may be available:
|
|||||||
- **Battery current (A)**: Battery current
|
- **Battery current (A)**: Battery current
|
||||||
- **Battery date**: Battery installation or last change date (opaque by mfg)
|
- **Battery date**: Battery installation or last change date (opaque by mfg)
|
||||||
- **Battery manuf date**: Battery manufacturing date (opaque by mfg)
|
- **Battery manuf date**: Battery manufacturing date (opaque by mfg)
|
||||||
- **Battery runtime (secs)**: Battery runtime
|
- **Battery runtime (secs)**: Remaining battery runtime as estimated by the device
|
||||||
- **Battery temperature (°C)**: Battery temperature
|
- **Battery temperature (°C)**: Battery temperature
|
||||||
- **Battery voltage (V)**: Battery voltage
|
- **Battery voltage (V)**: Battery voltage
|
||||||
- **Beeper status**: UPS beeper status, with the available states: `enabled`, `disabled`, and `muted`
|
- **Beeper status**: UPS beeper status, with the available states: `enabled`, `disabled`, and `muted`
|
||||||
@ -337,7 +337,7 @@ automation:
|
|||||||
- trigger: state
|
- trigger: state
|
||||||
entity_id:
|
entity_id:
|
||||||
- sensor.ups_status
|
- sensor.ups_status
|
||||||
to: "On Battery Battery Discharging"
|
to: "On Battery, Battery Discharging"
|
||||||
actions:
|
actions:
|
||||||
- action: notify.notify
|
- action: notify.notify
|
||||||
data:
|
data:
|
||||||
|
|||||||
@ -15,8 +15,8 @@ The Open Thread Border Router integration allows calling an Open Thread Border R
|
|||||||
|
|
||||||
This integration is installed automatically when the **Open Thread Border Router** add-on is installed. For Home Assistant Yellow or Connect ZBT-1 refer to the following procedures:
|
This integration is installed automatically when the **Open Thread Border Router** add-on is installed. For Home Assistant Yellow or Connect ZBT-1 refer to the following procedures:
|
||||||
|
|
||||||
- [Enabling Thread on Home Assistant Yellow](https://yellow.home-assistant.io/procedures/enable-thread/)
|
- [Enabling Thread on Home Assistant Yellow](https://support.nabucasa.com/hc/en-us/articles/25742476767517)
|
||||||
- [Enabling Thread on Home Assistant Connect ZBT-1](https://connectzbt1.home-assistant.io/procedures/enable-thread/)
|
- [Enabling Thread on Home Assistant Connect ZBT-1](https://support.nabucasa.com/hc/en-us/articles/26124710072861)
|
||||||
|
|
||||||
Installing this integration manually is an advanced use case, for example if you run your own border router. If you do have such a use case, follow these steps:
|
Installing this integration manually is an advanced use case, for example if you run your own border router. If you do have such a use case, follow these steps:
|
||||||
|
|
||||||
|
|||||||
@ -25,19 +25,20 @@ related:
|
|||||||
title: PrusaLink installation guide for Prusa MK2.5/MK3 with Raspberry Pi 3/4
|
title: PrusaLink installation guide for Prusa MK2.5/MK3 with Raspberry Pi 3/4
|
||||||
---
|
---
|
||||||
|
|
||||||
The **PrusaLink** {% term integration %} allows you to monitor your [Prusa 3D printer](https://www.prusa3d.com) and its progress with your Home Assistant installation. This integration works with Prusa MINI/MINI+, Prusa MK3.9/MK4, Prusa XL, and with the older Raspberry Pi-based Prusa MK2.5/MK3.
|
The **PrusaLink** {% term integration %} allows you to monitor your [Prusa 3D printer](https://www.prusa3d.com) and its progress with your Home Assistant installation. This integration works with Prusa MINI/MINI+, Prusa MK3.9/MK4, Prusa XL, Prusa CORE One, and with the older Raspberry Pi-based Prusa MK2.5/MK3.
|
||||||
|
|
||||||
This integration has been updated to utilize the latest v1 API endpoints, which require firmware version 4.7.0 or later. If you own a Prusa MINI/MINI+, please make sure your printer is running firmware 5.1.0 or a more recent version. Firmware versions 4.7.x and 5.0.x are not available for this model. For Prusa MK2.5/MK3, this integration requires PrusaLink version 0.7.2 or later.
|
This integration has been updated to utilize the latest v1 API endpoints, which require firmware version 4.7.0 or later. If you own a Prusa MINI/MINI+, please make sure your printer is running firmware 5.1.0 or a more recent version. Firmware versions 4.7.x and 5.0.x are not available for this model. The Prusa CORE One works with its default firmware. For Prusa MK2.5/MK3, this integration requires PrusaLink version 0.7.2 or later.
|
||||||
|
|
||||||
Firmware update guides can be found here:
|
Firmware update guides can be found here:
|
||||||
|
|
||||||
- [Prusa MINI/MINI+](https://help.prusa3d.com/article/firmware-updating-mini-mini_124784)
|
- [Prusa MINI/MINI+](https://help.prusa3d.com/article/firmware-updating-mini-mini_124784)
|
||||||
- [Prusa MK3.9/MK4/XL](https://help.prusa3d.com/article/how-to-update-firmware-mk4-xl_453086)
|
- [Prusa MK3.9/MK4/XL](https://help.prusa3d.com/article/how-to-update-firmware-mk4-xl_453086)
|
||||||
|
- [Prusa CORE One](https://help.prusa3d.com/article/how-to-update-firmware-core-one-mk4-s-mk3-9-s-mk3-5-s-xl_453086)
|
||||||
- [Prusa MK2.5/MK3](https://help.prusa3d.com/guide/how-to-update-prusalink-mk2-5-s-mk3-s-_650837)
|
- [Prusa MK2.5/MK3](https://help.prusa3d.com/guide/how-to-update-prusalink-mk2-5-s-mk3-s-_650837)
|
||||||
|
|
||||||
## Obtaining hostname, username, and password
|
## Obtaining hostname, username, and password
|
||||||
|
|
||||||
### Prusa MINI/MINI+/MK3.9/MK4/XL
|
### Prusa MINI/MINI+/MK3.9/MK4/XL/CORE One
|
||||||
|
|
||||||
- On your printer, navigate to **Settings** > **Network** > **PrusaLink**.
|
- On your printer, navigate to **Settings** > **Network** > **PrusaLink**.
|
||||||
- Find the device's **IP address**. Alternatively, you can look for the printer's IP address or hostname on your router.
|
- Find the device's **IP address**. Alternatively, you can look for the printer's IP address or hostname on your router.
|
||||||
|
|||||||
@ -59,17 +59,48 @@ Status sensors provide information about the overall state of the generator.
|
|||||||
|
|
||||||
> **Note:** This list of values is not complete. If you observe new values, please report them by opening an issue.
|
> **Note:** This list of values is not complete. If you observe new values, please report them by opening an issue.
|
||||||
|
|
||||||
| Sensor ID | Values | Description |
|
#### Generator status
|
||||||
|-------------------|--------------------------------------|---------------------------------|
|
|
||||||
| `generator_status` | ReadyToRun, RunningExercise, ... | Indicates the current generator status. |
|
Provides the overall status of the generator.
|
||||||
| `engine_state` | Standby, PerformingVariableSpeedExercise, ... | Displays the current engine state. |
|
|
||||||
| `power_source` | Utility, ... | The source of power for the home. |
|
| Value | Description |
|
||||||
|
|--------------------------------------|---------------------------------|
|
||||||
|
| `ReadyToRun` | Generator is ready to run in case of a power outage. |
|
||||||
|
| `Running` | Generator is running. |
|
||||||
|
| `RunningExercise` | Generator is currently running its exercise program. |
|
||||||
|
| `SwitchStateOff` | Generator is turned off and **will not** run in case of a power outage. |
|
||||||
|
|
||||||
|
#### Engine state
|
||||||
|
|
||||||
|
Provides the detailed engine state.
|
||||||
|
|
||||||
|
| Value | Description |
|
||||||
|
|--------------------------------------|---------------------------------|
|
||||||
|
| `CrankOn` | Generator is currently cranking and trying to start up. |
|
||||||
|
| `Off` | Generator is turned off and **will not** run in case of a power outage. |
|
||||||
|
| `Running` | Generator is running. |
|
||||||
|
| `Standby` | Generator is ready to run in case of a power outage. |
|
||||||
|
| `Stopping` | Generator is stopping. |
|
||||||
|
| `PerformingFullSpeedDiagnostics` | Generator is running full speed diagnostics. |
|
||||||
|
| `PerformingUnloadedFullSpeedExercise` | Generator is running full speed exercise. |
|
||||||
|
| `PerformingVariableSpeedExercise` | Generator is running variable speed exercise. |
|
||||||
|
|
||||||
|
#### Power source
|
||||||
|
|
||||||
|
Provides an indication of power source for the home.
|
||||||
|
|
||||||
|
| Value | Description |
|
||||||
|
|--------------------------------------|---------------------------------|
|
||||||
|
| `Generator` | Generator is providing power to the home. |
|
||||||
|
| `Utility` | Utility power is providing power to the home. |
|
||||||
|
|
||||||
|
|
||||||
## Tested generators
|
## Tested generators
|
||||||
|
|
||||||
These are the generator models that have been tested:
|
These are the generator models that have been tested:
|
||||||
|
|
||||||
- [38RCLB](https://resources.kohler.com/power/kohler/residential/pdf/tp6908.pdf)
|
- [38RCLB](https://resources.kohler.com/power/kohler/residential/pdf/tp6908.pdf)
|
||||||
|
- [26RCA](https://www.kohlerhomeenergy.rehlko.com/products/home+generators/26rca)
|
||||||
- [20RESA](https://resources.kohler.com/power/kohler/residential/pdf/tp6804.pdf)
|
- [20RESA](https://resources.kohler.com/power/kohler/residential/pdf/tp6804.pdf)
|
||||||
- [20RCA](https://www.kohlerhomeenergy.rehlko.com/products/home+generators/20rca)
|
- [20RCA](https://www.kohlerhomeenergy.rehlko.com/products/home+generators/20rca)
|
||||||
- [14RESA](https://www.kohler.com/content/dam/kohler-com-NA/Lifestyle/PDF/PDF-tp6803.pdf)
|
- [14RESA](https://www.kohler.com/content/dam/kohler-com-NA/Lifestyle/PDF/PDF-tp6803.pdf)
|
||||||
|
|||||||
@ -30,8 +30,18 @@ The `slack` platform allows you to deliver notifications from Home Assistant to
|
|||||||
|
|
||||||
Find `Features/OAuth and Permissions/Scopes/Bot Token Scopes`
|
Find `Features/OAuth and Permissions/Scopes/Bot Token Scopes`
|
||||||
|
|
||||||
3. Add the `chat:write` and `dnd:read` scopes
|
3. Add the following OAuth scopes:
|
||||||
- To modify your Slack bot's username and icon, additionally add the `chat:write.customize` OAuth scope
|
- `chat:write`
|
||||||
|
- `dnd:read`
|
||||||
|
- `channels:manage`
|
||||||
|
- `channels:read`
|
||||||
|
- `groups:read`
|
||||||
|
- `groups:write`
|
||||||
|
- `im:read`
|
||||||
|
- `im:write`
|
||||||
|
- `mpim:read`
|
||||||
|
- `mpim:write`
|
||||||
|
- Optionally add `chat:write.customize` to modify your Slack bot's username and icon.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@ -23,6 +23,16 @@ The SMA Solar integration will poll a [SMA](http://www.sma-solar.com/) [(US)](ht
|
|||||||
|
|
||||||
{% include integrations/config_flow.md %}
|
{% include integrations/config_flow.md %}
|
||||||
|
|
||||||
|
### Installation details
|
||||||
|
|
||||||
|
When Home Assistant discovers a new SMA device, or when you manually add one, the following form is presented:
|
||||||
|
|
||||||
|
- **Host**: the hostname or IP address (if discovered via DHCP, this field will not be displayed as it's known via discovery)
|
||||||
|
- Use SSL certificate
|
||||||
|
- Verify SSL certificate
|
||||||
|
- **Group**: choose either **user** or **installer** (default: **user**). Ask your installer if you’re unsure which to use
|
||||||
|
- **Password**: use your password or ask your installer the default password that has been set up
|
||||||
|
|
||||||
## Supported Devices
|
## Supported Devices
|
||||||
|
|
||||||
Not all inverters, energy meters and batteries from SMA are supported.
|
Not all inverters, energy meters and batteries from SMA are supported.
|
||||||
|
|||||||
@ -165,11 +165,6 @@ data:
|
|||||||
|
|
||||||
## Supported functionality
|
## Supported functionality
|
||||||
|
|
||||||
### Switches
|
|
||||||
|
|
||||||
- **Alarm**: Enables a scheduled alarm to sound. Alarms must also be enabled on the associated player for the alarm to sound, using the Alarms Enabled switch or directly on the Lyrion Music Server for that player.
|
|
||||||
- **Alarms Enabled**: Enables a player to sound alarms. Disabling will prevent all alarms from sounding on that player, regardless of whether the individual alarm is enabled
|
|
||||||
|
|
||||||
### Binary sensors
|
### Binary sensors
|
||||||
|
|
||||||
The integration provides the following entities.
|
The integration provides the following entities.
|
||||||
|
|||||||
@ -115,6 +115,7 @@ For instructions on how to obtain the encryption key, see README in [PySwitchbot
|
|||||||
|
|
||||||
- [Color Bulb (WoBulb)](https://switch-bot.com/pages/switchbot-color-bulb)
|
- [Color Bulb (WoBulb)](https://switch-bot.com/pages/switchbot-color-bulb)
|
||||||
- [Light Strip (WoStrip)](https://www.switchbot.jp/products/switchbot-strip-light)
|
- [Light Strip (WoStrip)](https://www.switchbot.jp/products/switchbot-strip-light)
|
||||||
|
- [Smart Ceiling Light (WoCeiling)](https://www.switchbot.jp/products/switchbot-ceiling-light)
|
||||||
|
|
||||||
### Locks
|
### Locks
|
||||||
|
|
||||||
@ -366,7 +367,7 @@ Features:
|
|||||||
|
|
||||||
### Lights
|
### Lights
|
||||||
|
|
||||||
Light entities are added for Color Bulb and LED Strip Light.
|
Light entities are added for Color Bulb, LED Strip Light, and Ceiling Light.
|
||||||
|
|
||||||
#### Color Bulb
|
#### Color Bulb
|
||||||
|
|
||||||
|
|||||||
@ -47,7 +47,9 @@ When SSDP is activated on a NAS with two or more NICs with different IP addresse
|
|||||||
|
|
||||||
## Separate User Configuration
|
## Separate User Configuration
|
||||||
|
|
||||||
You must grant the user admin rights in order to access utilization information since it's stored in the core module.
|
{% note %}
|
||||||
|
You must grant the user administrator rights, as the basic functions of this integration require them due to the structure of the Synology DSM API.
|
||||||
|
{% endnote %}
|
||||||
|
|
||||||
When creating the user, it is possible to deny access to all locations and applications. By doing this, the user will not be able to login to the web interface or view any of the files on the Synology NAS. It is still able to read the utilization and storage information using the API.
|
When creating the user, it is possible to deny access to all locations and applications. By doing this, the user will not be able to login to the web interface or view any of the files on the Synology NAS. It is still able to read the utilization and storage information using the API.
|
||||||
|
|
||||||
|
|||||||
@ -44,7 +44,7 @@ You must have:
|
|||||||
|
|
||||||
- A [Tesla](https://tesla.com) account
|
- A [Tesla](https://tesla.com) account
|
||||||
- A [Developer Application](https://developer.tesla.com/en_US/dashboard)
|
- A [Developer Application](https://developer.tesla.com/en_US/dashboard)
|
||||||
- A web domain and host that you can serve your public key file from. Some free options include:
|
- A web domain and host that you can serve your public key file from. Either locally (see [NGINX Home Assistant SSL proxy Add-on](https://github.com/home-assistant/addons/blob/master/nginx_proxy/DOCS.md) instructions below), or alternatively, with some free web-options (ordered from easier to more complex):
|
||||||
- [FleetKey.cc](https://fleetkey.cc)
|
- [FleetKey.cc](https://fleetkey.cc)
|
||||||
- [MyTeslamate.com](https://app.myteslamate.com/fleet)
|
- [MyTeslamate.com](https://app.myteslamate.com/fleet)
|
||||||
- [AWS S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/WebsiteHosting.html)
|
- [AWS S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/WebsiteHosting.html)
|
||||||
@ -54,6 +54,22 @@ You must have:
|
|||||||
|
|
||||||
{% include integrations/config_flow.md %}
|
{% include integrations/config_flow.md %}
|
||||||
|
|
||||||
|
{% details "Hosting a Public/Private Key Pair with the NGINX Home Assistant SSL proxy Add-on" %}
|
||||||
|
|
||||||
|
While the [Tesla Fleet API documentation Step 3](https://developer.tesla.com/docs/fleet-api/getting-started/what-is-fleet-api#step-3-generate-a-public-private-key-pair) mentions this as a later step, it is recommended that you do this first to ensure key reachability before the rest of the integration.
|
||||||
|
With this method, it is assumed that the [NGINX Home Assistant SSL proxy Add-on](https://github.com/home-assistant/addons/blob/master/nginx_proxy/DOCS.md) is running as a reverse proxy for external access to your Home Assistant installation.
|
||||||
|
|
||||||
|
1. **Open an SSH Terminal** on your Home Assistant installation using the [Terminal & SSH Add-on](https://www.home-assistant.io/common-tasks/os#installing-and-using-the-ssh-add-on).
|
||||||
|
2. Run this command to **create a private key**: `openssl ecparam -name prime256v1 -genkey -noout -out private-key.pem`
|
||||||
|
3. Run this command to **create and associate a public key** with it: `openssl ec -in private-key.pem -pubout -out public-key.pem`
|
||||||
|
4. **Backup both these files** somewhere safe and private for access later.
|
||||||
|
5. **Copy the public key** file `public-key.pem` to `/share/tesla/.well-known/appspecific/com.tesla.3p.public-key.pem`. It needs to be exactly this location for Tesla's API to partner with your account correctly.
|
||||||
|
6. Create a **NGINX configuration file** `nginx_proxy_default_tesla.conf` in `/share` with: `echo 'location /.well-known/appspecific/com.tesla.3p.public-key.pem {\n root /share/tesla;\n}' > /share/nginx_proxy_default_tesla.conf`
|
||||||
|
7. Close the Terminal and go to Settings->Add-Ons->**NGINX Home Assistant SSL proxy**->Configuration page. Change the `customize.active` option from the default `false` to `true`. Leave the `config.default` option at its default value: `nginx_proxy_default*.conf`.
|
||||||
|
8. **Restart the NGINX Home Assistant SSL proxy Add-on** on the Settings->Add-Ons->NGINX Home Assistant SSL proxy->Info page and test if the public key file is accessible at `https://my.domain.com/.well-known/appspecific/com.tesla.3p.public-key.pem`
|
||||||
|
|
||||||
|
{% enddetails %}
|
||||||
|
|
||||||
{% details "Hosting a Public/Private Key Pair" %}
|
{% details "Hosting a Public/Private Key Pair" %}
|
||||||
|
|
||||||
While the [Tesla Fleet API documentation Step 3](https://developer.tesla.com/docs/fleet-api/getting-started/what-is-fleet-api#step-3-generate-a-public-private-key-pair) mentions this as a later step, it is recommended that you do this first to ensure key reachability before the rest of the integration.
|
While the [Tesla Fleet API documentation Step 3](https://developer.tesla.com/docs/fleet-api/getting-started/what-is-fleet-api#step-3-generate-a-public-private-key-pair) mentions this as a later step, it is recommended that you do this first to ensure key reachability before the rest of the integration.
|
||||||
|
|||||||
@ -25,9 +25,9 @@ related:
|
|||||||
title: Adding a Matter device to Home Assistant
|
title: Adding a Matter device to Home Assistant
|
||||||
- docs: /integrations/homekit_controller/#adding-a-homekit-device-through-thread
|
- docs: /integrations/homekit_controller/#adding-a-homekit-device-through-thread
|
||||||
title: Adding an Apple HomeKit device through Thread
|
title: Adding an Apple HomeKit device through Thread
|
||||||
- url: https://connectzbt1.home-assistant.io/procedures/enable-thread/
|
- url: https://support.nabucasa.com/hc/en-us/articles/26124710072861
|
||||||
title: Enabling Thread on Connect ZBT-1
|
title: Enabling Thread on Connect ZBT-1
|
||||||
- url: https://yellow.home-assistant.io/procedures/enable-thread/
|
- url: https://support.nabucasa.com/hc/en-us/articles/25742476767517
|
||||||
title: Enabling Thread on Yellow
|
title: Enabling Thread on Yellow
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -140,8 +140,8 @@ Follow these steps if you want to turn Home Assistant into a Thread border route
|
|||||||
#### To make Home Assistant your first Thread network
|
#### To make Home Assistant your first Thread network
|
||||||
|
|
||||||
1. To enable Thread support on your Home Assistant Yellow or Connect ZBT-1, you need to install the **OpenThread Border Router** add-on. Follow the corresponding procedure:
|
1. To enable Thread support on your Home Assistant Yellow or Connect ZBT-1, you need to install the **OpenThread Border Router** add-on. Follow the corresponding procedure:
|
||||||
- [Enable Thread on Home Assistant Yellow](https://yellow.home-assistant.io/procedures/enable-thread/).
|
- [Enable Thread on Home Assistant Yellow](https://support.nabucasa.com/hc/en-us/articles/25742476767517).
|
||||||
- [Enable Thread on Home Assistant Connect ZBT-1](https://connectzbt1.home-assistant.io/procedures/enable-thread/).
|
- [Enable Thread on Home Assistant Connect ZBT-1](https://support.nabucasa.com/hc/en-us/articles/26124710072861).
|
||||||
|
|
||||||
2. Make sure the Home Assistant Thread network is defined as preferred network.
|
2. Make sure the Home Assistant Thread network is defined as preferred network.
|
||||||
- This should happen automatically, but check to be sure.
|
- This should happen automatically, but check to be sure.
|
||||||
@ -194,8 +194,8 @@ Note: the steps and images here show the process with a Google Thread network. B
|
|||||||
|
|
||||||
|
|
||||||
5. To enable Thread support on your Home Assistant Yellow or Connect ZBT-1, you need to install the **OpenThread Border Router** add-on. Follow the corresponding procedure:
|
5. To enable Thread support on your Home Assistant Yellow or Connect ZBT-1, you need to install the **OpenThread Border Router** add-on. Follow the corresponding procedure:
|
||||||
- [Enable Thread on Home Assistant Yellow](https://yellow.home-assistant.io/procedures/enable-thread/).
|
- [Enable Thread on Home Assistant Yellow](https://support.nabucasa.com/hc/en-us/articles/25742476767517).
|
||||||
- [Enable Thread on Home Assistant Connect ZBT-1](https://connectzbt1.home-assistant.io/procedures/enable-thread/).
|
- [Enable Thread on Home Assistant Connect ZBT-1](https://support.nabucasa.com/hc/en-us/articles/26124710072861).
|
||||||
- **Result**: The network now shows as the preferred network, joined with the third-party network.
|
- **Result**: The network now shows as the preferred network, joined with the third-party network.
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@ -89,7 +89,7 @@ To run a Z-Wave network, you need the following elements:
|
|||||||
|
|
||||||
If you are running {% term "Home Assistant Operating System" %} or {% term "Home Assistant Supervised" %}, the easiest way to get started is by using the built-in Z-Wave JS add-on in Home Assistant.
|
If you are running {% term "Home Assistant Operating System" %} or {% term "Home Assistant Supervised" %}, the easiest way to get started is by using the built-in Z-Wave JS add-on in Home Assistant.
|
||||||
|
|
||||||
For other ways to setup a Z-Wave server, refer to the [advanced installation instructions](#advanced-installation-instructions).
|
For other ways to setup a Z-Wave server, refer to the [advanced installation instructions](#about-installation-instructions).
|
||||||
|
|
||||||
Follow these steps:
|
Follow these steps:
|
||||||
|
|
||||||
|
|||||||
@ -36,17 +36,17 @@ For certain power user needs CM5 might provide big improvements. Some Pi 5 users
|
|||||||
|
|
||||||
## Installing on CM5
|
## Installing on CM5
|
||||||
|
|
||||||
For the Home Assistant Yellow, we have [two ways to install Home Assistant OS](https://yellow.home-assistant.io/guides/reinstall-os/) onto the Compute Module. One is very easy and quick (using USB 2.0), while the other is more complex (using rpiboot). Unfortunately, due to firmware differences with CM5 it cannot boot off USB 2.0 devices (though the USB 2.0 ports work once the device is booted).
|
For the Home Assistant Yellow, we have two ways to install Home Assistant OS onto the Compute Module. One is very easy and quick (using USB 2.0), while the other is more complex (using rpiboot). Unfortunately, due to firmware differences with CM5 it cannot boot off USB 2.0 devices (though the USB 2.0 ports work once the device is booted).
|
||||||
|
|
||||||
If you already have a Yellow running Home Assistant OS, upgrading to CM5 can be a drop-in replacement, but in some circumstances it can be more complex,
|
If you already have a Yellow running Home Assistant OS, upgrading to CM5 can be a drop-in replacement, but in some circumstances it can be more complex,
|
||||||
|
|
||||||
- **CM4 Lite (no eMMC) with NVMe storage** - Update to the latest HAOS (version 14.0 or greater - as of writing 14.0 is still pre-release, we recommend you wait for the stable release, but if you want to get the pre-release today either [join the beta channel](https://www.home-assistant.io/common-tasks/os/#running-a-beta-version) or [explicitly install](https://www.home-assistant.io/common-tasks/os/#running-a-specific-version) `14.0.rc2`), power it down, swap the CM4 Lite for a CM5 Lite, and you're good to go.
|
- **CM4 Lite (no eMMC) with NVMe storage** - Update to the latest HAOS (version 14.0 or greater), power it down, swap the CM4 Lite for a CM5 Lite, and you're good to go.
|
||||||
|
|
||||||
- **CM4 with eMMC (regardless if you are using NVMe or not)** - Download a backup of your Home Assistant, power down your system, and install Home Assistant OS on the CM5 using [rpiboot](https://yellow.home-assistant.io/guides/reinstall-os/#:~:text=Option%202%3A%20Reinstall%20Home%20Assistant%20OS%20using%20rpiboot) (the more complex installation method). Once installed restore the backup.
|
- **CM4 with eMMC (regardless if you are using NVMe or not)** - Download a backup of your Home Assistant, power down your system, and install Home Assistant OS on the CM5 using [rpiboot](https://support.nabucasa.com/hc/en-us/articles/25485061432093-Reinstall-the-Home-Assistant-Operating-System-on-Raspberry-Pi-CM5) (the more complex installation method). Once installed restore the backup.
|
||||||
|
|
||||||
- **New Yellow with CM5**: You will need to install Home Assistant with [rpiboot](https://yellow.home-assistant.io/guides/reinstall-os/#:~:text=Option%202%3A%20Reinstall%20Home%20Assistant%20OS%20using%20rpiboot) (the more complex installation method).
|
- **New Yellow with CM5**: You will need to install Home Assistant with [rpiboot](https://support.nabucasa.com/hc/en-us/articles/25606333033501-Home-Assistant-Yellow-Kit-with-CM5) (the more complex installation method).
|
||||||
|
|
||||||
For full details on how to set up your Home Assistant Yellow [visit our documentation](https://yellow.home-assistant.io/).
|
For full details on how to set up your Home Assistant Yellow [visit our documentation](https://support.nabucasa.com/hc/en-us/categories/24734575925149-Home-Assistant-Yellow).
|
||||||
|
|
||||||
## CM4 is still great
|
## CM4 is still great
|
||||||
|
|
||||||
|
|||||||
@ -48,7 +48,7 @@ The [Open Home Foundation Matter Server](https://csa-iot.org/csa_product/open-ho
|
|||||||
|
|
||||||
If you're confused why we certified both Home Assistant and Open Home Foundation Matter Server, there are a couple of legal/procedural reasons, but it comes with some useful benefits. We certified the server as a standalone component to allow any project to use it. Each project that uses it, including Home Assistant, will have to go through a certification process to acknowledge that it uses a certified component as a "User Interface Component". Certification for the Open Home Foundation Matter Server means it properly connects and communicates with other Matter devices, while certification for Home Assistant is about being able to display the Matter trademark.
|
If you're confused why we certified both Home Assistant and Open Home Foundation Matter Server, there are a couple of legal/procedural reasons, but it comes with some useful benefits. We certified the server as a standalone component to allow any project to use it. Each project that uses it, including Home Assistant, will have to go through a certification process to acknowledge that it uses a certified component as a "User Interface Component". Certification for the Open Home Foundation Matter Server means it properly connects and communicates with other Matter devices, while certification for Home Assistant is about being able to display the Matter trademark.
|
||||||
|
|
||||||
This separation is important because it means that we won't need to go through recertification every time we update Home Assistant. This way we can keep the Matter-related backend isolated in both a software and certification sense. This is also why we will need to continue to have the Open Home Foundation Matter Server as an add-on, and it cannot be built into [Home Assistant Core](/installation/#advanced-installation-methods).
|
This separation is important because it means that we won't need to go through recertification every time we update Home Assistant. This way we can keep the Matter-related backend isolated in both a software and certification sense. This is also why we will need to continue to have the Open Home Foundation Matter Server as an add-on, and it cannot be built into [Home Assistant Core](/installation/#about-installation-methods).
|
||||||
|
|
||||||
## The road to certification
|
## The road to certification
|
||||||
|
|
||||||
|
|||||||
@ -76,6 +76,10 @@ Enjoy the release!
|
|||||||
- [Improved UI experience when using templates in automations \& scripts](#improved-ui-experience-when-using-templates-in-automations--scripts)
|
- [Improved UI experience when using templates in automations \& scripts](#improved-ui-experience-when-using-templates-in-automations--scripts)
|
||||||
- [Pasting automations and scripts YAML directly into the UI](#pasting-automations-and-scripts-yaml-directly-into-the-ui)
|
- [Pasting automations and scripts YAML directly into the UI](#pasting-automations-and-scripts-yaml-directly-into-the-ui)
|
||||||
- [Discover what Home Assistant is discovering](#discover-what-home-assistant-is-discovering)
|
- [Discover what Home Assistant is discovering](#discover-what-home-assistant-is-discovering)
|
||||||
|
- [Patch releases](#patch-releases)
|
||||||
|
- [2025.5.1 - May 9](#202551---may-9)
|
||||||
|
- [2025.5.2 - May 16](#202552---may-16)
|
||||||
|
- [2025.5.3 - May 23](#202553---may-23)
|
||||||
- [Need help? Join the community!](#need-help-join-the-community)
|
- [Need help? Join the community!](#need-help-join-the-community)
|
||||||
- [Backward-incompatible changes](#backward-incompatible-changes)
|
- [Backward-incompatible changes](#backward-incompatible-changes)
|
||||||
- [All changes](#all-changes)
|
- [All changes](#all-changes)
|
||||||
@ -583,6 +587,306 @@ You can find these new tools in **Settings** > **System** > **Network**. At the
|
|||||||
bottom of that page, you will find the ability to browse all the things
|
bottom of that page, you will find the ability to browse all the things
|
||||||
Home Assistant is seeing on your network for each of the discovery protocols.
|
Home Assistant is seeing on your network for each of the discovery protocols.
|
||||||
|
|
||||||
|
## Patch releases
|
||||||
|
|
||||||
|
We will also release patch releases for Home Assistant 2025.5 in May.
|
||||||
|
These patch releases only contain bug fixes. Our goal is to release a patch
|
||||||
|
release every Friday.
|
||||||
|
|
||||||
|
### 2025.5.1 - May 9
|
||||||
|
|
||||||
|
- Fix Z-Wave restore nvm command to wait for driver ready ([@MartinHjelmare] - [#144413])
|
||||||
|
- fix homekit air purifier temperature sensor to convert unit ([@tamwahba] - [#144435])
|
||||||
|
- Add LAP-V102S-AUSR to VeSync ([@DukeChocula] - [#144437])
|
||||||
|
- Bump pylamarzocco to 2.0.1 ([@zweckj] - [#144454])
|
||||||
|
- Fix Z-Wave reset accumulated values button entity category ([@MartinHjelmare] - [#144459])
|
||||||
|
- Fix point import error ([@fredrike] - [#144462])
|
||||||
|
- Ignore Fronius Gen24 firmware 1.35.4-1 SSL verification issue ([@farmio] - [#144463])
|
||||||
|
- Don't encrypt or decrypt unknown files in backup archives ([@emontnemery] - [#144495])
|
||||||
|
- Bump forecast-solar to 4.2.0 ([@bdraco] - [#144502])
|
||||||
|
- Fix removing of smarthome templates on startup of AVM Fritz!SmartHome integration ([@mib1185] - [#144506])
|
||||||
|
- Bump aiodns to 3.4.0 ([@bdraco] - [#144511])
|
||||||
|
- Fix statistics coordinator subscription for lamarzocco ([@zweckj] - [#144541])
|
||||||
|
- Update frontend to 20250509.0 ([@bramkragten] - [#144549])
|
||||||
|
- Reolink clean device registry mac ([@starkillerOG] - [#144554])
|
||||||
|
- Prevent errors during cleaning of connections/identifiers in device registry ([@starkillerOG] - [#144558])
|
||||||
|
|
||||||
|
[#144406]: https://github.com/home-assistant/core/pull/144406
|
||||||
|
[#144413]: https://github.com/home-assistant/core/pull/144413
|
||||||
|
[#144435]: https://github.com/home-assistant/core/pull/144435
|
||||||
|
[#144437]: https://github.com/home-assistant/core/pull/144437
|
||||||
|
[#144454]: https://github.com/home-assistant/core/pull/144454
|
||||||
|
[#144459]: https://github.com/home-assistant/core/pull/144459
|
||||||
|
[#144462]: https://github.com/home-assistant/core/pull/144462
|
||||||
|
[#144463]: https://github.com/home-assistant/core/pull/144463
|
||||||
|
[#144495]: https://github.com/home-assistant/core/pull/144495
|
||||||
|
[#144502]: https://github.com/home-assistant/core/pull/144502
|
||||||
|
[#144506]: https://github.com/home-assistant/core/pull/144506
|
||||||
|
[#144511]: https://github.com/home-assistant/core/pull/144511
|
||||||
|
[#144541]: https://github.com/home-assistant/core/pull/144541
|
||||||
|
[#144549]: https://github.com/home-assistant/core/pull/144549
|
||||||
|
[#144554]: https://github.com/home-assistant/core/pull/144554
|
||||||
|
[#144558]: https://github.com/home-assistant/core/pull/144558
|
||||||
|
[@DukeChocula]: https://github.com/DukeChocula
|
||||||
|
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||||
|
[@bdraco]: https://github.com/bdraco
|
||||||
|
[@bramkragten]: https://github.com/bramkragten
|
||||||
|
[@emontnemery]: https://github.com/emontnemery
|
||||||
|
[@farmio]: https://github.com/farmio
|
||||||
|
[@fredrike]: https://github.com/fredrike
|
||||||
|
[@frenck]: https://github.com/frenck
|
||||||
|
[@mib1185]: https://github.com/mib1185
|
||||||
|
[@starkillerOG]: https://github.com/starkillerOG
|
||||||
|
[@tamwahba]: https://github.com/tamwahba
|
||||||
|
[@zweckj]: https://github.com/zweckj
|
||||||
|
|
||||||
|
### 2025.5.2 - May 16
|
||||||
|
|
||||||
|
- Allow dns hostnames to be retained for SMLIGHT user flow. ([@tl-sl] - [#142514])
|
||||||
|
- Removed unused file_id param from open_ai_conversation request ([@cadavre] - [#143878])
|
||||||
|
- Doorbell Event is fired just once in homematicip_cloud ([@hahn-th] - [#144357])
|
||||||
|
- Don't scale Roborock mop Path ([@Lash-L] - [#144421])
|
||||||
|
- Reolink fix privacy mode availability for NVR IPC cams ([@starkillerOG] - [#144569])
|
||||||
|
- Bump aiodiscover to 2.7.0 ([@bdraco] - [#144571])
|
||||||
|
- Bump reolink_aio to 0.13.3 ([@starkillerOG] - [#144583])
|
||||||
|
- Mark inkbird coordinator as not needing connectable ([@bdraco] - [#144584])
|
||||||
|
- fix enphase_envoy diagnostics home endpoint name ([@catsmanac] - [#144634])
|
||||||
|
- Bump pylamarzocco to 2.0.2 ([@zweckj] - [#144635])
|
||||||
|
- bump pyenphase to 1.26.1 ([@catsmanac] - [#144641])
|
||||||
|
- Bump ical to 9.2.1 ([@allenporter] - [#144642])
|
||||||
|
- Bump python-linkplay to v0.2.5 ([@silamon] - [#144666])
|
||||||
|
- Close Octoprint aiohttp session on unload ([@RubenNL] - [#144670])
|
||||||
|
- Bump holidays to 0.72 ([@gjohansson-ST] - [#144671])
|
||||||
|
- Fix strings typo for Comelit ([@chemelli74] - [#144672])
|
||||||
|
- Avoid closing shared session for Comelit ([@chemelli74] - [#144682])
|
||||||
|
- Fix wrong state in Husqvarna Automower ([@Thomas55555] - [#144684])
|
||||||
|
- Bump voluptuous-openapi to 0.1.0 ([@allenporter] - [#144703])
|
||||||
|
- Bump ical to 9.2.2 ([@allenporter] - [#144713])
|
||||||
|
- Bump gcal-sync to 7.0.1 ([@oyvindwe] - [#144718])
|
||||||
|
- Bump aiocomelit to 0.12.1 ([@chemelli74] - [#144720])
|
||||||
|
- Fix Netgear handeling of missing MAC in device registry ([@starkillerOG] - [#144722])
|
||||||
|
- Repair Z-Wave unknown controller ([@MartinHjelmare] - [#144738])
|
||||||
|
- Fill in Plaato URL via placeholders ([@joostlek] - [#144754])
|
||||||
|
- Cleanup wrongly combined Reolink devices ([@starkillerOG] - [#144771])
|
||||||
|
- Do not show an empty component name on MQTT device subentries not as `None` if it is not set ([@jbouwh] - [#144792])
|
||||||
|
- Fix blocking call in azure storage ([@zweckj] - [#144803])
|
||||||
|
- Fix Z-Wave unique id after controller reset ([@MartinHjelmare] - [#144813])
|
||||||
|
- Fix blocking call in azure_storage config flow ([@zweckj] - [#144818])
|
||||||
|
- Bump pylamarzocco to 2.0.3 ([@zweckj] - [#144825])
|
||||||
|
- Bump python-snoo to 0.6.6 ([@Lash-L] - [#144849])
|
||||||
|
- Bump ical to 9.2.4 ([@allenporter] - [#144852])
|
||||||
|
- Fix wall connector states in Teslemetry ([@Bre77] - [#144855])
|
||||||
|
- Fix Reolink setup when ONVIF push is unsupported ([@starkillerOG] - [#144869])
|
||||||
|
- Fix some Home Connect translation strings ([@rjblake] - [#144905])
|
||||||
|
- Update Tibber lib 0.31.2 ([@Danielhiversen] - [#144908])
|
||||||
|
- Update mill library 0.12.5 ([@Danielhiversen] - [#144911])
|
||||||
|
- Fix unknown Pure AQI in Sensibo ([@gjohansson-ST] - [#144924])
|
||||||
|
- Ignore Fronius Gen24 firmware 1.35.4-1 SSL verification issue for new setups ([@farmio] - [#144940])
|
||||||
|
- Fix Home Assistant Yellow config entry data ([@emontnemery] - [#144948])
|
||||||
|
- Bump deebot-client to 13.2.0 ([@edenhaus] - [#144957])
|
||||||
|
- Fix ESPHome entities unavailable if deep sleep enabled after entry setup ([@oddstr13] - [#144970])
|
||||||
|
- Strip `_CLIENT` suffix from ZHA event `unique_id` ([@puddly] - [#145006])
|
||||||
|
- Bump pySmartThings to 3.2.2 ([@joostlek] - [#145033])
|
||||||
|
- Set SmartThings oven setpoint to unknown if its 1 Fahrenheit ([@joostlek] - [#145038])
|
||||||
|
- Fix climate idle state for Comelit ([@chemelli74] - [#145059])
|
||||||
|
- Map SmartThings auto mode correctly ([@joostlek] - [#145061])
|
||||||
|
- Update frontend to 20250516.0 ([@bramkragten] - [#145062])
|
||||||
|
- Only set suggested area for new SmartThings devices ([@joostlek] - [#145063])
|
||||||
|
- Fix fan AC mode in SmartThings AC ([@joostlek] - [#145064])
|
||||||
|
- Don't create entities for Smartthings smarttags ([@joostlek] - [#145066])
|
||||||
|
- Fix Ecovacs mower area sensors ([@edenhaus] - [#145071])
|
||||||
|
|
||||||
|
[#142514]: https://github.com/home-assistant/core/pull/142514
|
||||||
|
[#143878]: https://github.com/home-assistant/core/pull/143878
|
||||||
|
[#144357]: https://github.com/home-assistant/core/pull/144357
|
||||||
|
[#144406]: https://github.com/home-assistant/core/pull/144406
|
||||||
|
[#144421]: https://github.com/home-assistant/core/pull/144421
|
||||||
|
[#144564]: https://github.com/home-assistant/core/pull/144564
|
||||||
|
[#144569]: https://github.com/home-assistant/core/pull/144569
|
||||||
|
[#144571]: https://github.com/home-assistant/core/pull/144571
|
||||||
|
[#144583]: https://github.com/home-assistant/core/pull/144583
|
||||||
|
[#144584]: https://github.com/home-assistant/core/pull/144584
|
||||||
|
[#144634]: https://github.com/home-assistant/core/pull/144634
|
||||||
|
[#144635]: https://github.com/home-assistant/core/pull/144635
|
||||||
|
[#144641]: https://github.com/home-assistant/core/pull/144641
|
||||||
|
[#144642]: https://github.com/home-assistant/core/pull/144642
|
||||||
|
[#144666]: https://github.com/home-assistant/core/pull/144666
|
||||||
|
[#144670]: https://github.com/home-assistant/core/pull/144670
|
||||||
|
[#144671]: https://github.com/home-assistant/core/pull/144671
|
||||||
|
[#144672]: https://github.com/home-assistant/core/pull/144672
|
||||||
|
[#144682]: https://github.com/home-assistant/core/pull/144682
|
||||||
|
[#144684]: https://github.com/home-assistant/core/pull/144684
|
||||||
|
[#144703]: https://github.com/home-assistant/core/pull/144703
|
||||||
|
[#144713]: https://github.com/home-assistant/core/pull/144713
|
||||||
|
[#144718]: https://github.com/home-assistant/core/pull/144718
|
||||||
|
[#144720]: https://github.com/home-assistant/core/pull/144720
|
||||||
|
[#144722]: https://github.com/home-assistant/core/pull/144722
|
||||||
|
[#144738]: https://github.com/home-assistant/core/pull/144738
|
||||||
|
[#144754]: https://github.com/home-assistant/core/pull/144754
|
||||||
|
[#144771]: https://github.com/home-assistant/core/pull/144771
|
||||||
|
[#144792]: https://github.com/home-assistant/core/pull/144792
|
||||||
|
[#144803]: https://github.com/home-assistant/core/pull/144803
|
||||||
|
[#144813]: https://github.com/home-assistant/core/pull/144813
|
||||||
|
[#144818]: https://github.com/home-assistant/core/pull/144818
|
||||||
|
[#144825]: https://github.com/home-assistant/core/pull/144825
|
||||||
|
[#144849]: https://github.com/home-assistant/core/pull/144849
|
||||||
|
[#144852]: https://github.com/home-assistant/core/pull/144852
|
||||||
|
[#144855]: https://github.com/home-assistant/core/pull/144855
|
||||||
|
[#144869]: https://github.com/home-assistant/core/pull/144869
|
||||||
|
[#144905]: https://github.com/home-assistant/core/pull/144905
|
||||||
|
[#144908]: https://github.com/home-assistant/core/pull/144908
|
||||||
|
[#144911]: https://github.com/home-assistant/core/pull/144911
|
||||||
|
[#144924]: https://github.com/home-assistant/core/pull/144924
|
||||||
|
[#144940]: https://github.com/home-assistant/core/pull/144940
|
||||||
|
[#144948]: https://github.com/home-assistant/core/pull/144948
|
||||||
|
[#144957]: https://github.com/home-assistant/core/pull/144957
|
||||||
|
[#144970]: https://github.com/home-assistant/core/pull/144970
|
||||||
|
[#145006]: https://github.com/home-assistant/core/pull/145006
|
||||||
|
[#145033]: https://github.com/home-assistant/core/pull/145033
|
||||||
|
[#145038]: https://github.com/home-assistant/core/pull/145038
|
||||||
|
[#145059]: https://github.com/home-assistant/core/pull/145059
|
||||||
|
[#145061]: https://github.com/home-assistant/core/pull/145061
|
||||||
|
[#145062]: https://github.com/home-assistant/core/pull/145062
|
||||||
|
[#145063]: https://github.com/home-assistant/core/pull/145063
|
||||||
|
[#145064]: https://github.com/home-assistant/core/pull/145064
|
||||||
|
[#145066]: https://github.com/home-assistant/core/pull/145066
|
||||||
|
[#145071]: https://github.com/home-assistant/core/pull/145071
|
||||||
|
[@Bre77]: https://github.com/Bre77
|
||||||
|
[@Danielhiversen]: https://github.com/Danielhiversen
|
||||||
|
[@Lash-L]: https://github.com/Lash-L
|
||||||
|
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||||
|
[@RubenNL]: https://github.com/RubenNL
|
||||||
|
[@Thomas55555]: https://github.com/Thomas55555
|
||||||
|
[@allenporter]: https://github.com/allenporter
|
||||||
|
[@bdraco]: https://github.com/bdraco
|
||||||
|
[@bramkragten]: https://github.com/bramkragten
|
||||||
|
[@cadavre]: https://github.com/cadavre
|
||||||
|
[@catsmanac]: https://github.com/catsmanac
|
||||||
|
[@chemelli74]: https://github.com/chemelli74
|
||||||
|
[@edenhaus]: https://github.com/edenhaus
|
||||||
|
[@emontnemery]: https://github.com/emontnemery
|
||||||
|
[@farmio]: https://github.com/farmio
|
||||||
|
[@frenck]: https://github.com/frenck
|
||||||
|
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||||
|
[@hahn-th]: https://github.com/hahn-th
|
||||||
|
[@jbouwh]: https://github.com/jbouwh
|
||||||
|
[@joostlek]: https://github.com/joostlek
|
||||||
|
[@oddstr13]: https://github.com/oddstr13
|
||||||
|
[@oyvindwe]: https://github.com/oyvindwe
|
||||||
|
[@puddly]: https://github.com/puddly
|
||||||
|
[@rjblake]: https://github.com/rjblake
|
||||||
|
[@silamon]: https://github.com/silamon
|
||||||
|
[@starkillerOG]: https://github.com/starkillerOG
|
||||||
|
[@tl-sl]: https://github.com/tl-sl
|
||||||
|
[@zweckj]: https://github.com/zweckj
|
||||||
|
|
||||||
|
### 2025.5.3 - May 23
|
||||||
|
|
||||||
|
- Netatmo: do not fail on schedule updates ([@wuede] - [#142933])
|
||||||
|
- Fix QNAP fail to load ([@disforw] - [#144675])
|
||||||
|
- Allow image send with read-only access (matrix notify) ([@TheOneValen] - [#144819])
|
||||||
|
- Postpone update in WMSPro after service call ([@mback2k] - [#144836])
|
||||||
|
- Bump ESPHome stable BLE version to 2025.5.0 ([@bdraco] - [#144857])
|
||||||
|
- Fix album and artist returning "None" rather than None for Squeezebox media player. ([@peteS-UK] - [#144971])
|
||||||
|
- Bump aiontfy to 0.5.2 ([@tr4nt0r] - [#145044])
|
||||||
|
- Fix proberly Ecovacs mower area sensors ([@edenhaus] - [#145078])
|
||||||
|
- Map auto to heat_cool for thermostat in SmartThings ([@joostlek] - [#145098])
|
||||||
|
- Add missing device condition translations to lock component ([@jpbede] - [#145104])
|
||||||
|
- Fix history_stats with sliding window that ends before now ([@karwosts] - [#145117])
|
||||||
|
- Bump sense-energy to 0.13.8 ([@kbickar] - [#145156])
|
||||||
|
- Improve Z-Wave config flow tests ([@MartinHjelmare] - [#144871])
|
||||||
|
- Fix Z-Wave unique id update during controller migration ([@MartinHjelmare] - [#145185])
|
||||||
|
- Bump velbusaio to 2025.5.0 ([@cereal2nd] - [#145198])
|
||||||
|
- Bump aiocomelit to 0.12.3 ([@chemelli74] - [#145209])
|
||||||
|
- Fix Z-Wave config entry unique id after NVM restore ([@MartinHjelmare] - [#145221])
|
||||||
|
- Bump holidays to 0.73 ([@gjohansson-ST] - [#145238])
|
||||||
|
- Bump pyaprilaire to 0.9.0 ([@chamberlain2007] - [#145260])
|
||||||
|
- Add cloud as after_dependency to onedrive ([@zweckj] - [#145301])
|
||||||
|
- Handle more exceptions in azure_storage ([@zweckj] - [#145320])
|
||||||
|
- Fix limit of shown backups on Synology DSM location ([@mib1185] - [#145342])
|
||||||
|
- Add initial coordinator refresh for players in Squeezebox ([@peteS-UK] - [#145347])
|
||||||
|
- Fix: Revert Ecovacs mower total_stats_area unit to square meters ([@Augar] - [#145380])
|
||||||
|
- Bump pysqueezebox to v0.12.1 ([@rajlaud] - [#145384])
|
||||||
|
- OTBR: remove links to obsolete multiprotocol docs ([@c0ffeeca7] - [#145394])
|
||||||
|
- Bump pylamarzocco to 2.0.4 ([@zweckj] - [#145402])
|
||||||
|
- Bump py-synologydsm-api to 2.7.2 ([@mib1185] - [#145403])
|
||||||
|
- Mark backflush binary sensor not supported for GS3 MP in lamarzocco ([@zweckj] - [#145406])
|
||||||
|
- Bump yt-dlp to 2025.05.22 ([@joostlek] - [#145441])
|
||||||
|
- Reolink fix device migration ([@starkillerOG] - [#145443])
|
||||||
|
- Bump pysmartthings to 3.2.3 ([@joostlek] - [#145444])
|
||||||
|
- Bump opower to 0.12.1 ([@tronikos] - [#145464])
|
||||||
|
- Make Gemma models work in Google AI ([@tronikos] - [#145479])
|
||||||
|
- Fix strings related to Google search tool in Google AI ([@tronikos] - [#145480])
|
||||||
|
- Bump pyfibaro to 0.8.3 ([@rappenze] - [#145488])
|
||||||
|
- Bump deebot-client to 13.2.1 ([@edenhaus] - [#145492])
|
||||||
|
|
||||||
|
[#142933]: https://github.com/home-assistant/core/pull/142933
|
||||||
|
[#144406]: https://github.com/home-assistant/core/pull/144406
|
||||||
|
[#144564]: https://github.com/home-assistant/core/pull/144564
|
||||||
|
[#144675]: https://github.com/home-assistant/core/pull/144675
|
||||||
|
[#144819]: https://github.com/home-assistant/core/pull/144819
|
||||||
|
[#144836]: https://github.com/home-assistant/core/pull/144836
|
||||||
|
[#144857]: https://github.com/home-assistant/core/pull/144857
|
||||||
|
[#144871]: https://github.com/home-assistant/core/pull/144871
|
||||||
|
[#144971]: https://github.com/home-assistant/core/pull/144971
|
||||||
|
[#145044]: https://github.com/home-assistant/core/pull/145044
|
||||||
|
[#145072]: https://github.com/home-assistant/core/pull/145072
|
||||||
|
[#145078]: https://github.com/home-assistant/core/pull/145078
|
||||||
|
[#145098]: https://github.com/home-assistant/core/pull/145098
|
||||||
|
[#145104]: https://github.com/home-assistant/core/pull/145104
|
||||||
|
[#145117]: https://github.com/home-assistant/core/pull/145117
|
||||||
|
[#145156]: https://github.com/home-assistant/core/pull/145156
|
||||||
|
[#145185]: https://github.com/home-assistant/core/pull/145185
|
||||||
|
[#145198]: https://github.com/home-assistant/core/pull/145198
|
||||||
|
[#145209]: https://github.com/home-assistant/core/pull/145209
|
||||||
|
[#145221]: https://github.com/home-assistant/core/pull/145221
|
||||||
|
[#145238]: https://github.com/home-assistant/core/pull/145238
|
||||||
|
[#145260]: https://github.com/home-assistant/core/pull/145260
|
||||||
|
[#145301]: https://github.com/home-assistant/core/pull/145301
|
||||||
|
[#145320]: https://github.com/home-assistant/core/pull/145320
|
||||||
|
[#145342]: https://github.com/home-assistant/core/pull/145342
|
||||||
|
[#145347]: https://github.com/home-assistant/core/pull/145347
|
||||||
|
[#145380]: https://github.com/home-assistant/core/pull/145380
|
||||||
|
[#145384]: https://github.com/home-assistant/core/pull/145384
|
||||||
|
[#145394]: https://github.com/home-assistant/core/pull/145394
|
||||||
|
[#145402]: https://github.com/home-assistant/core/pull/145402
|
||||||
|
[#145403]: https://github.com/home-assistant/core/pull/145403
|
||||||
|
[#145406]: https://github.com/home-assistant/core/pull/145406
|
||||||
|
[#145441]: https://github.com/home-assistant/core/pull/145441
|
||||||
|
[#145443]: https://github.com/home-assistant/core/pull/145443
|
||||||
|
[#145444]: https://github.com/home-assistant/core/pull/145444
|
||||||
|
[#145464]: https://github.com/home-assistant/core/pull/145464
|
||||||
|
[#145479]: https://github.com/home-assistant/core/pull/145479
|
||||||
|
[#145480]: https://github.com/home-assistant/core/pull/145480
|
||||||
|
[#145488]: https://github.com/home-assistant/core/pull/145488
|
||||||
|
[#145492]: https://github.com/home-assistant/core/pull/145492
|
||||||
|
[@Augar]: https://github.com/Augar
|
||||||
|
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||||
|
[@TheOneValen]: https://github.com/TheOneValen
|
||||||
|
[@bdraco]: https://github.com/bdraco
|
||||||
|
[@c0ffeeca7]: https://github.com/c0ffeeca7
|
||||||
|
[@cereal2nd]: https://github.com/cereal2nd
|
||||||
|
[@chamberlain2007]: https://github.com/chamberlain2007
|
||||||
|
[@chemelli74]: https://github.com/chemelli74
|
||||||
|
[@disforw]: https://github.com/disforw
|
||||||
|
[@edenhaus]: https://github.com/edenhaus
|
||||||
|
[@frenck]: https://github.com/frenck
|
||||||
|
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||||
|
[@joostlek]: https://github.com/joostlek
|
||||||
|
[@jpbede]: https://github.com/jpbede
|
||||||
|
[@karwosts]: https://github.com/karwosts
|
||||||
|
[@kbickar]: https://github.com/kbickar
|
||||||
|
[@mback2k]: https://github.com/mback2k
|
||||||
|
[@mib1185]: https://github.com/mib1185
|
||||||
|
[@peteS-UK]: https://github.com/peteS-UK
|
||||||
|
[@rajlaud]: https://github.com/rajlaud
|
||||||
|
[@rappenze]: https://github.com/rappenze
|
||||||
|
[@starkillerOG]: https://github.com/starkillerOG
|
||||||
|
[@tr4nt0r]: https://github.com/tr4nt0r
|
||||||
|
[@tronikos]: https://github.com/tronikos
|
||||||
|
[@wuede]: https://github.com/wuede
|
||||||
|
[@zweckj]: https://github.com/zweckj
|
||||||
|
|
||||||
## Need help? Join the community!
|
## Need help? Join the community!
|
||||||
|
|
||||||
Home Assistant has a great community of users who are all more than willing
|
Home Assistant has a great community of users who are all more than willing
|
||||||
|
|||||||
139
source/_posts/2025-05-09-roadmap-2025h1.markdown
Normal file
139
source/_posts/2025-05-09-roadmap-2025h1.markdown
Normal file
@ -0,0 +1,139 @@
|
|||||||
|
---
|
||||||
|
layout: post
|
||||||
|
title: "Roadmap 2025: A Truly Smart Home through Collective Intelligence"
|
||||||
|
description: "Having achieved the goals of our first-year roadmap, we're now introducing an ambitious new project."
|
||||||
|
date: 2025-05-09 00:00:01
|
||||||
|
date_formatted: "May 9, 2025"
|
||||||
|
author: Madelena Mak
|
||||||
|
comments: true
|
||||||
|
categories: Announcements Roadmap
|
||||||
|
og_image: /images/blog/2025-05-roadmap-2025h1/art.jpg
|
||||||
|
---
|
||||||
|
<img alt="Devices, Automations, Dashboards, Voice & Music, Frontend" src="/images/blog/2025-05-roadmap-2025h1/roadmap-2025-cover.png" class='no-shadow'/>
|
||||||
|
|
||||||
|
It's been a year since we launched [our first roadmap](/blog/2024/06/12/roadmap-2024h1/) for Home Assistant, which means it's time to launch this year's first update! In 2025, we're building on our direction to make Home Assistant easier to use for everyone in your household, and taking it to the next level by making smart homes more intuitive, proactive, and user-friendly. 🚀
|
||||||
|
|
||||||
|
This centers on helping Home Assistant understand devices in their context, and cataloging every device that works with Home Assistant through a new project, Device Database. And we will do this the Home Assistant way --- through the power of our community and our collective intelligence. (...but that's not all! The roadmap also covers many product areas we are aiming to work on from automation to voice to dashboard [and more](#and-thats-not-all-for-this-year)!)
|
||||||
|
|
||||||
|
If you're new to our roadmaps or curious about how they guide the development of Home Assistant, be sure to check out [our introduction](/blog/2024/06/12/roadmap-introduction/) to Home Assistant roadmaps. As always, your feedback is incredibly valuable, so please give us your thoughts in the comments.
|
||||||
|
<!-- TOC -->
|
||||||
|
|
||||||
|
- [One year on the road](#one-year-on-the-road)
|
||||||
|
- [The smart home administrator as an inventor](#the-smart-home-administrator-as-an-inventor)
|
||||||
|
- [From shared wisdom to collective intelligence](#from-shared-wisdom-to-collective-intelligence)
|
||||||
|
- [Putting Devices in Context](#putting-devices-in-context)
|
||||||
|
- [Introducing the Device Database](#introducing-the-device-database)
|
||||||
|
- [And that's not all for this year!](#and-thats-not-all-for-this-year)
|
||||||
|
- [Laying the Groundwork for a Truly Smart Home](#laying-the-groundwork-for-a-truly-smart-home)
|
||||||
|
|
||||||
|
<!-- /TOC -->
|
||||||
|
<!--more-->
|
||||||
|
## One year on the road
|
||||||
|
|
||||||
|
Last year, we introduced [our very first roadmap](/blog/2024/06/12/roadmap-2024h1/)---and it wasn't just plans on paper. It marked a new chapter for Home Assistant: one where we made our direction clear, set ambitious goals, and invited the whole community along for the ride.
|
||||||
|
|
||||||
|
In [2024](/blog/2024/06/12/roadmap-2024h1/), we focused on building a smart home that has a high Home Approval Factor: helping both the maintainer and residents of the smart home unlock more value from Home Assistant without needing to be an expert. This was done by improving the touchpoints that all members of the household will interact with, such as automations, dashboards, and voice interactions, while maintaining the power and depth of the platform for our power users and admins.
|
||||||
|
|
||||||
|
The real challenge lay in building a roadmap from scratch. That meant not only poring through and prioritizing every single feature request, but also increasing transparency and building trust in the roadmap within our organization and our community as a beacon that can help guide the development of the project. Thanks to the feedback, energy, and contributions from our global community, we've made huge strides. In the past year, we tackled some of the biggest pain points, such as drag-and-drop dashboard improvements, automation grouping, standard voice assistant hardware, better automated backups, and more.
|
||||||
|
|
||||||
|
Now, in 2025, we are ready to lay the groundwork for the next big step forward: Making Home Assistant *truly smart* through our collective effort and intelligence.
|
||||||
|
|
||||||
|
## The smart home administrator as an inventor
|
||||||
|
|
||||||
|
Home Approval Factor means that a successful smart home isn't just great for the person who set it up, but for everyone who lives there. Whether it's your partner, kids, or roommates, we want Home Assistant to feel intuitive and supportive for the whole household.
|
||||||
|
|
||||||
|
In some ways, being a smart home administrator is like being an inventor (or, as we would say, a product manager). To be a great inventor, you need to understand your users. What are their needs? What solutions can you invent to solve their problems? How do you know you solved their problems? Can you improve upon the solution?
|
||||||
|
|
||||||
|
Home Assistant provides all the building blocks for our administrators to build whatever they want and let their imaginations run wild, and better yet, it's easier than ever with the improvements we made last year! However, that's also the curse of a blank slate. Inventing fun and hyper-personalized solutions for niche problems is a major appeal of Home Assistant, but sometimes, maintenance of a smart home can be a chore --- not every single problem requires reinventing the wheel.
|
||||||
|
|
||||||
|
The reality today is that, according to our [community survey](/blog/2025/04/16/state-of-the-open-home-recap/#research), just 46% of partners and only 27% of children of long-time Home Assistant users are directly interacting with Home Assistant. That's a big gap, and it highlights a broader challenge: Even the most experienced smart home administrators don't always have the complete picture of their household's needs. They may not realize what would help until something goes wrong. And it's unreasonable to expect everyone to be an expert in everything --- from automations to dashboards to onboarding new users.
|
||||||
|
|
||||||
|
## From shared wisdom to collective intelligence
|
||||||
|
|
||||||
|
<p class='img'><img alt="wisdom spread across social, chats, and videos" src="/images/blog/2025-05-roadmap-2025h1/shared-wisdom.jpg"/></p>
|
||||||
|
|
||||||
|
Right now, if a smart home admin wants to improve their setup, they have to go hunting---through our community forums, GitHub repos, Reddit threads, YouTube videos, Discord chats... you name it---trying to find tips and tricks that apply to their specific case. You share incredible wisdom with each other every day, but much of it is scattered, short-lived, or hard to apply without lots of customization.
|
||||||
|
|
||||||
|
We believe it's time for a smarter system.
|
||||||
|
|
||||||
|
What if Home Assistant could learn from our community's best ideas and use that knowledge to proactively suggest improvements? What if it could guide users based on what others have done in similar situations? That's the vision we're working toward: using collective intelligence to power a truly smart home.
|
||||||
|
|
||||||
|
<p class='img'><img alt="organized shared wisdom is collective intelligence" src="/images/blog/2025-05-roadmap-2025h1/collective-intelligence.jpg"/></p>
|
||||||
|
|
||||||
|
To get there, Home Assistant needs to *understand* what's in the home. Inside each home, there are the people, the spaces, and the devices. This year, we will start with helping Home Assistant understand devices in terms of (1) **context**: what each device is and how it is used, and (2) **information**: every device that works with Home Assistant and how it is supported.
|
||||||
|
|
||||||
|
## Putting Devices in Context
|
||||||
|
|
||||||
|
Today, most devices in Home Assistant show up as a bundle of entities: a temperature sensor here, a switch there. This is by design --- we want to provide the ultimate flexibility in configuring your system, and will continue to do so. However, it is not without disadvantages.
|
||||||
|
|
||||||
|
<p class='img'><img alt="Fridge as a series of entities" src="/images/blog/2025-05-roadmap-2025h1/devices-without-context.jpg"/></p>
|
||||||
|
|
||||||
|
For example, we don't always know that those entities together form, say, a fridge, which is essentially a mini house of its own: It may have temperature sensors, a door sensor, a light, and so on, but Home Assistant cannot assume them as any other sensors or lights within a room. Without that context, Home Assistant can't do much beyond letting users build their own dashboards and automations from scratch.
|
||||||
|
|
||||||
|
As you add more devices, entities pile up, and Home Assistant starts to lose the thread of what's actually in the home. Your smart home should become more powerful as you add more devices, but at the cost of the difficulty of maintaining them also increasing exponentially.
|
||||||
|
|
||||||
|
When we **put devices in context**, everything changes. A fridge becomes more than a list of entities --- it becomes an actual device that can have a dedicated dashboard, default automations, and contextual voice commands.
|
||||||
|
|
||||||
|
<p class='img'><img alt="Dashboards, Automation and Voice in context" src="/images/blog/2025-05-roadmap-2025h1/device-context.jpg"/></p>
|
||||||
|
|
||||||
|
Here's how context unlocks a more streamlined experience across the platform:
|
||||||
|
|
||||||
|
- **Voice:** Assist can currently source the right sensor if it knows the area of the device. In the future, we can also intelligently exclude irrelevant sensors from a voice query. For example, "What's the temperature in the kitchen?" shouldn't return the freezer's internal temperature.
|
||||||
|
- **Dashboards:** Integrations can provide customized cards and dashboards right from the start, providing a much more streamlined experience. For example, we can provide a fridge dashboard. It works with other devices, too. Imagine a car dashboard or a 3D printer dashboard.
|
||||||
|
- **Automations:** By understanding what devices a user has and how they are commonly used, we can intelligently suggest automations created by our community. For example, "fridge door left open" or "fridge water leakage" alerts can be provided without building them manually from scratch.
|
||||||
|
|
||||||
|
This will be a core architectural change that will be proposed and discussed in the coming months. We're building on what our contributors already share in integrations: knowledge about how devices are structured and how they should behave. My hope is that this will provide the framework for our contributors to contribute dashboards and automation blueprints to our code in exciting new ways.
|
||||||
|
|
||||||
|
## Introducing the Device Database
|
||||||
|
|
||||||
|
To make all this work, we also need a centralized, structured place to store and share device knowledge. That's where the Device Database---a brand new project from the Open Home Foundation---comes in.
|
||||||
|
|
||||||
|
Think of it as a source of truth created, curated, and validated by the community. A place where we gather everything from metadata (like power usage or infrared codes) to factual information (setup instructions such as how to add or reset a device) to real-world setup insights and community creations (such as automation examples). It will contain information users intentionally submit to the database, nothing will be collected automatically without your explicit consent.
|
||||||
|
|
||||||
|
It's more than just having all device documentation in one place. We want to universalize all our collective experiences about devices in one place, which is more accessible, centralized, and structured than online websites and chat rooms.
|
||||||
|
|
||||||
|
With the Device Database, users both old and new can easily make well-informed choices and pick the best Home Assistant-compatible devices for them based on real usage experiences, allowing them to easily make decisions based on open home values --- privacy, choice, and sustainability.
|
||||||
|
|
||||||
|
The data will be used and cross-referenced in Home Assistant and other Open Home Foundation projects, and acts as the backbone of their integrations. For example, a future infrared integration can hypothetically benefit from having access to readily available infrared codes from the database.
|
||||||
|
|
||||||
|
<p class='img'><img alt="Protocols, device database, feeding choice" src="/images/blog/2025-05-roadmap-2025h1/working-together.png"/></p>
|
||||||
|
|
||||||
|
This isn't something we can build alone. We're relying on the strength of our global community to turn this vision into reality, and we're backing it up with our infrastructure, engineering efforts, and partnerships:
|
||||||
|
|
||||||
|
- The [Open Home Foundation](https://www.openhomefoundation.org/) is here to provide the framework to help us collect and collaborate on knowledge easily and safely.
|
||||||
|
- We're working with [Nabu Casa](https://www.nabucasa.com/)---our commercial partner---to create the most reliable hardware antennas that support more open protocols, such as Z-Wave, Zigbee, Bluetooth, and more, to expand the Home Assistant ecosystem.
|
||||||
|
- The [Works with Home Assistant program](https://works-with.home-assistant.io/) is being strengthened to make it easier to find trusted, high-quality devices for the platform, as you may have witnessed with the [numerous new partners](/blog/categories/works-with-home-assistant/) joining in the past few months.
|
||||||
|
|
||||||
|
The result? A system where no admin has to figure everything out in isolation on their own. Home Assistant can suggest, guide, adapt, and point users in the right direction, by drawing from the collective intelligence of the community (instead of scraping user data involuntarily like what Big Tech does).
|
||||||
|
|
||||||
|
## And that's not all for this year!
|
||||||
|
|
||||||
|
<p class='img'><img alt="Devices, Automations, Dashboards, Voice & Music, Frontend" src="/images/blog/2025-05-roadmap-2025h1/roadmap-2025.png"/></p>
|
||||||
|
|
||||||
|
While device context and the Device Database are the major themes of this year's roadmap, it doesn't mean that we are dropping everything else that does not fit. We're continuing work on other parts of the product experience:
|
||||||
|
|
||||||
|
- A complete revamp of our automation triggers and conditions to make them both easier to use and more powerful.
|
||||||
|
- A navigation and design system overhaul to improve feature discovery.
|
||||||
|
- Continued improvements to make dashboards easier to use out of the box, including a new default dashboard and more.
|
||||||
|
- Enhanced privacy controls for users, guests, and public access (Yes, I am aware of that.)
|
||||||
|
- Easier setup for Music Assistant.
|
||||||
|
- Make Assist more conversational, such as the ability to confirm and clarify a query.
|
||||||
|
- Continued explorations in using LLMs to improve the overall user experience beyond voice.
|
||||||
|
|
||||||
|
In the meantime, we are working on making our roadmap more publicly accessible, so that you can discuss and track our progress with us! Stay tuned.
|
||||||
|
|
||||||
|
## Laying the Groundwork for a Truly Smart Home
|
||||||
|
|
||||||
|
This roadmap isn't about the flashy latest tech fad (what is it now anyway?) or abstract features. It's about creating the enduring foundation to allow our community to build something greater than all of us together: a smart home platform that learns, grows, and adapts --- with full respect for privacy, choice, and sustainability.
|
||||||
|
|
||||||
|
The central theme of the roadmap is that making Home Assistant smarter starts with understanding context, such as knowing what devices are and how they're used, and we will use this collective intelligence to supercharge the main pillars of the user experience --- automations, voice, and dashboards.
|
||||||
|
|
||||||
|
We're making maintenance of a smart home easier, by making it less like a mandatory chore while still keeping the fun of tinkering (say, you wanna go wild on YAML), and by creating tools to help admins solve problems they don't even know they have yet. We believe that, as our advanced users continue to tinker with their systems, their creations and discoveries will also benefit and elevate every user's smart home.
|
||||||
|
|
||||||
|
We can't wait to work on these initiatives for the rest of this year! Let's build it together! 🚀👩🏻🚀👩🏼🚀👨🏼🚀
|
||||||
|
|
||||||
|
\- [Madelena], [JLo], & [Laura]
|
||||||
|
|
||||||
|
[Madelena]: https://github.com/Madelena
|
||||||
|
[JLo]: https://github.com/jlpouffier
|
||||||
|
[Laura]: https://github.com/laupalombi
|
||||||
@ -0,0 +1,121 @@
|
|||||||
|
---
|
||||||
|
layout: post
|
||||||
|
title: "Deprecating Core and Supervised installation methods, and 32-bit systems"
|
||||||
|
description: "This deprecation will help focus support efforts and streamline development."
|
||||||
|
date: 2025-05-22 00:00:00
|
||||||
|
date_formatted: "May 22, 2025"
|
||||||
|
author: Franck Nijhof
|
||||||
|
author_twitter: frenck
|
||||||
|
comments: true
|
||||||
|
categories: Public-Service-Announcement
|
||||||
|
og_image: /images/blog/2025-05-deprecation/art.png
|
||||||
|
---
|
||||||
|
|
||||||
|
<img src='/images/blog/2025-05-deprecation/art.png' style='border: 0;box-shadow: none;' alt="Deprecating Core and Supervised installation methods, and 32-bit systems">
|
||||||
|
|
||||||
|
We are today officially deprecating two installation methods and three legacy CPU architectures. We always strive to have Home Assistant run on almost anything, but sometimes we must make difficult decisions to keep the project moving forward. Though these changes will only affect a small percentage of Home Assistant users, we want to do everything in our power to make this easy for those who may need to migrate.
|
||||||
|
|
||||||
|
Beginning with Home Assistant 2025.6, affected systems will display a notification after updating, indicating that **support will end in six months (with release 2025.12)** and include a recommendation to [migrate to a supported system](#how-to-migrate). In this post, we'll go into our thinking on these deprecations and our findings after consulting the community on these changes.
|
||||||
|
|
||||||
|
We have deprecated the following installation methods:
|
||||||
|
|
||||||
|
- **Home Assistant Core** installation method, where you run your system in a Python environment, not to be confused with Container (for example, running your system in Docker).
|
||||||
|
- **Home Assistant's Supervised** installation method, which involves running your own operating system, then installing the Supervisor and other requirements on top of that.
|
||||||
|
|
||||||
|
These are advanced installation methods, with only a small percentage of the community opting to use them. If you are using these methods, you can continue to do so (you can even continue to update your system), but in six months time, you will no longer be supported, which I'll explain the impacts of in the next section. References to these installation methods will be removed from our documentation after our next release (2025.6). Going forward [Home Assistant OS](https://github.com/home-assistant/operating-system) and [Home Assistant Container](https://hub.docker.com/r/homeassistant/home-assistant) will become the only supported installation methods.
|
||||||
|
|
||||||
|
In the future, only the currently supported 64-bit architectures (aarch64 and amd64) will be used. The following legacy architectures are being deprecated:
|
||||||
|
|
||||||
|
- **i386** (32-bit x86) is an architecture used by Intel and AMD predominantly before 2003, but some later processors still utilized it (e.g., early Intel Atom models).
|
||||||
|
- **armhf** (32-bit ARM hard-float) was used by very early single-board computers, notably the original Raspberry Pi.
|
||||||
|
- **armv7** (32-bit ARM) was used by a number of early single-board computers, most notably the Raspberry Pi 2.
|
||||||
|
|
||||||
|
If you are one of the few with a system using these architectures, you will receive a notification after updating to 2025.6, and it will describe how to migrate your system. In six months, your system will become unsupported and will no longer receive updates.
|
||||||
|
|
||||||
|
[Check our guide to see if your current Home Assistant installation is affected.](#check-if-youre-affected)<!--more-->
|
||||||
|
|
||||||
|
## What does deprecated and unsupported mean
|
||||||
|
|
||||||
|
In the simplest terms, deprecation is where you stop recommending a certain feature to users as you intend to remove it soon. As we deprecated the Core and Supervised installations methods today, that means we are now working to remove all references to them from our documentation. The goal is to guide new users towards installation methods we plan to support long term, and discourage the use of those that are being phased out.
|
||||||
|
|
||||||
|
Even though they are being deprecated, we are committing to support them for a further six months (until release 2025.12), giving existing users time to migrate to Home Assistant OS or Container. During this time we will ensure these installation types keep functioning as normal during the deprecation period. However, after those six months have elapsed, these methods will become unsupported, which means issue reports will no longer be accepted. As these installation methods are used for the development of Home Assistant, it will still be technically possible to update them. We still would recommend migrating to a supported method, but that's your choice.
|
||||||
|
|
||||||
|
As i386, armhf, and armv7 architectures have also been deprecated, we are currently removing references to them from our documentation. More importantly, they will also be subject to a six-month support window. After that support ends (from release 2025.12 onwards), we will no longer build or release distributions or containers targeting these platforms. This will mean that in six months' time, there will be no more updates for these systems, and if users encounter issues, they will no longer be able to ask for support from Home Assistant maintainers.
|
||||||
|
|
||||||
|
## Why we made this decision
|
||||||
|
|
||||||
|
### Core and Supervised
|
||||||
|
|
||||||
|
<p class='img'><img src='/images/blog/2025-05-deprecation/analytics.png' alt="OS and Container represent the vast majority of installation methods">From our <a href="https://analytics.home-assistant.io/">opt-in analytics</a></p>
|
||||||
|
|
||||||
|
The Core and Supervised installation methods are not only complex for users to install and maintain --- they're also challenging for the Home Assistant team to support. In the past, there were compelling reasons, outside Home Assistant development, to run these installation methods, but for most people those reasons are disappearing. Home Assistant OS is very capable with a rich ecosystem of add-ons, while also being easy to run in a virtual machine. Container adoption has become mainstream, now being widely available along with systems having more resources to run them. Steadily, we've seen year-on-year reductions in the percentage of Core and Supervised installations (currently standing at 2.5% and 3.3% respectively).
|
||||||
|
|
||||||
|
As Core and Supervised are more complex to maintain, they generate more issues that are more difficult to solve. This complexity places a disproportionate burden on our community-driven support system, where volunteers generously give their time to help others. It also takes time away from assisting the vast majority of users who are on the simpler to maintain installation methods. Along with this, new users could sometimes be swayed into running Core or Supervised, and have a bad experience that could cause them to give up on the best way to automate their home. By focusing our support and documentation on OS and Container methods, we can greatly improve the onboarding experience and ensure a smoother start for new users.
|
||||||
|
|
||||||
|
### Legacy 32-bit architectures
|
||||||
|
|
||||||
|
Though Home Assistant is very lean and can run great on older or low-spec hardware, the architectures we're deprecating are definitely on the leaner side of the spectrum. That probably explains why we see such low usage figures, with i386 and armhf architectures representing less than 0.5% of installations each, and armv7 at only 0.95% of installations. More than half of Home Assistant systems using armv7 have hardware that is capable of running 64-bit operating systems, like Raspberry Pi 3 and 4. This hardware can actually upgrade and migrate to a supported 64-bit version of our Home Assistant Operating System
|
||||||
|
|
||||||
|
The broader software and hardware industries have also shifted away from these older 32-bit systems. Most have adopted 64-bit architectures such as amd64 and aarch64, and we are seeing more projects we depend on no longer supporting these 32-bit architectures. There have already been several instances where keeping support for these architectures has held back the development of new features.
|
||||||
|
|
||||||
|
## Your feedback
|
||||||
|
|
||||||
|
For any major change, it is our goal to make sure the community guides this decision-making. When our maintainers initially proposed these deprecations, we shared this plan with the community (in our forum, GitHub, Discord, Reddit, and other social channels), using it to gather feedback. It was a constructive, civil discussion, and we learned a couple of interesting things that have helped us move this decision forward.
|
||||||
|
|
||||||
|
First, our current wording is confusing to the community. Core and Supervisor are components of Home Assistant OS, but are also similar---or the same---as the names of installation methods, which is not super clear for new users. We also found these installation methods being used in ways we never expected, and there are a good number of people who were already running Home Assistant in custom and unsupported ways, not even realizing they were unsupported.
|
||||||
|
|
||||||
|
Many of those impacted asked for better guidance on how to migrate. A good number were unaware of our expansion of backup and restore features to all installation methods, significantly smoothing their transition to a new platform.
|
||||||
|
|
||||||
|
## Check if you're affected
|
||||||
|
|
||||||
|
<p class='img'><img src='/images/blog/2025-05-deprecation/system-information.png' alt="what the system information dialog looks like">The blue arrow shows your installation type, and the red arrow displays the architecture.</p>
|
||||||
|
|
||||||
|
If you are unsure which **installation method** you are running:
|
||||||
|
|
||||||
|
- Select [this link](https://my.home-assistant.io/redirect/system_health/) OR Navigate to ***Settings > System > Repairs***, select the three-dotted menu in the top right corner, and select ***System information***.
|
||||||
|
- Check the Installation type field. If you are running Home Assistant OS, or Container, you are fine as the installation method deprecation doesn't apply to you.
|
||||||
|
|
||||||
|
In this [same window](https://my.home-assistant.io/redirect/system_health/), you can find the **architecture** as well:
|
||||||
|
|
||||||
|
- The CPU architecture field will tell you exactly which architecture you are using. If you are seeing aarch64 or x86_64 here, you are fine as the architecture deprecation doesn't apply to you.
|
||||||
|
|
||||||
|
## How to migrate
|
||||||
|
|
||||||
|
<p class='img'><img src='/images/blog/2025-05-deprecation/methods.png' alt="Installation methods and their functionality">Green are staying, and red are deprecated.</p>
|
||||||
|
|
||||||
|
If it's been a while since you've migrated Home Assistant systems, a lot has improved over the past several years. Switching systems is as easy as [making a backup](/common-tasks/general/#backups), downloading it, and [restoring](/common-tasks/general/#restoring-a-backup) it during the initialization of your new system (Home Assistant Cloud subscribers using off-site backups can restore [with just their password](/blog/2025/04/02/release-20254/#onboarding-with-a-home-assistant-cloud-backup)). Every Home Assistant installation method now has backups, and you can restore backups from any method onto another regardless of the differences in architecture. In many cases, very little needs to be done once the restore is successful ([to the dismay of tinkerers online](https://www.reddit.com/r/homeassistant/comments/1kdip17/are_you_kidding_me/)). Our documentation has a full list of guides on [how to install Home Assistant on different hardware](/installation/).
|
||||||
|
|
||||||
|
Before you think about migrating to a different installation method, you can always choose to stick with what you have. Just because it becomes unsupported by the Home Assistant project, it doesn't mean you can't keep running it like you do today. That choice is up to you.
|
||||||
|
|
||||||
|
| Need | Currently using | Migrate to |
|
||||||
|
| ------------------------------------------ | --------------- | -------------------------------------------------------------------------- |
|
||||||
|
| Home Assistant with add-ons | Supervised | Home Assistant OS |
|
||||||
|
| A system without Home Assistant OS support | Supervised | Container (many add-ons can be run as containers alongside Home Assistant) |
|
||||||
|
| Full control of the host system | Supervised | Run Home Assistant OS in a VM, or Container (alongside add-on containers) |
|
||||||
|
| Lightweight solution | Core | Container |
|
||||||
|
|
||||||
|
For **Home Assistant Core** users, the closest alternative is Home Assistant Container, which is most commonly used with Docker. If you can dedicate a device exclusively to Home Assistant, the recommended installation method is Home Assistant OS, which gives an appliance-like setup.
|
||||||
|
|
||||||
|
For **Home Assistant Supervised** users, we recommend migrating to Home Assistant OS---it supports everything Supervised does, including add-ons. If you want more control over the OS, you can also run Home Assistant OS in a virtual machine, like with Proxmox, or go the Home Assistant Container path alternatively.
|
||||||
|
|
||||||
|
For **deprecated architectures**, there is generally no supported migration path using your existing hardware. You will therefore need to find alternative hardware compatible with Home Assistant OS or Container. Second-hand single-board computers and recycled small-form-factor office machines are affordable and sustainable options. In some cases, your system may be running a 32-bit operating system, but is capable of running a 64-bit one (Raspberry Pi 3 and 4 are examples of systems often running a 32-bit OS despite being capable of running 64-bit). In this case, you will need to install a 64-bit capable operating system and restore Home Assistant on that system.
|
||||||
|
|
||||||
|
## Frequently asked questions
|
||||||
|
|
||||||
|
- ***If Home Assistant Core is used for development, and part of the developer docs, why not just offer it to end-users?***\
|
||||||
|
This is not just about technical viability, it is also about helping and supporting people with their issues, problems, and questions, in our forums and chat. Having these options available to less technical people leads to support queries, and if they have a bad first experience that reflects poorly on the project. Users are free to continue running their systems the way they would like.
|
||||||
|
|
||||||
|
- ***No support for Core or Supervised---can I still use them?***\
|
||||||
|
You can still use them even if we no longer support them. There are many users running Home Assistant in all kinds of unofficial ways. This change just means we are removing it from our end-user documentation and will no longer recommend using these installation methods from an official standpoint.
|
||||||
|
|
||||||
|
- ***Will the developer documentation on these things remain?***\
|
||||||
|
Yes, those will remain. The developer documentation for running Home Assistant's Core Python application directly in a Python virtual environment will remain. This is how we develop. This proposal is about removing end-user documentation and support.
|
||||||
|
|
||||||
|
- ***Can I start maintaining these installation methods?***\
|
||||||
|
While maintaining these methods will require effort, the community is free to move documentation and code to new independent projects. Our maintainers will no longer accept issues or provide end-user documentation, but that shouldn't stop anyone passionate about them from continuing to run them, or helping others to do the same.
|
||||||
|
|
||||||
|
- ***Can I reproduce any of the installations you offer?***\
|
||||||
|
Yes, of course! All our pipelines are open source and transparent, you can always recreate any of our pipelines and release artifacts; either automated or manual.
|
||||||
|
|
||||||
|
- ***Is this the first step towards making Home Assistant closed source/proprietary/commercial?***\
|
||||||
|
No, that is impossible. Home Assistant will always remain open source. Home Assistant is owned by the [Open Home Foundation](https://www.openhomefoundation.org/), a Swiss non-profit foundation that is audited and governed, and---by law---bound by its mission. This means it will always be open source and cannot be bought or sold.
|
||||||
@ -33,8 +33,7 @@ layout: null
|
|||||||
/energy /home-energy-management
|
/energy /home-energy-management
|
||||||
/integrations/energy /docs/energy 301!
|
/integrations/energy /docs/energy 301!
|
||||||
|
|
||||||
/amber https://yellow.home-assistant.io
|
/amber https://support.nabucasa.com/hc/en-us/categories/24734575925149-Home-Assistant-Yellow 301!
|
||||||
/yellow https://yellow.home-assistant.io
|
|
||||||
/blog/2021/09/13/home-assistant-amber/ /blog/2021/09/13/home-assistant-yellow/
|
/blog/2021/09/13/home-assistant-amber/ /blog/2021/09/13/home-assistant-yellow/
|
||||||
|
|
||||||
# Design & User research
|
# Design & User research
|
||||||
|
|||||||
@ -1179,6 +1179,300 @@ For a summary in a more readable format:
|
|||||||
- Add more missing device_class translations for template helper ([@MindFreeze] - [#144399])
|
- Add more missing device_class translations for template helper ([@MindFreeze] - [#144399])
|
||||||
- Bump intents to 2025.5.7 ([@synesthesiam] - [#144404])
|
- Bump intents to 2025.5.7 ([@synesthesiam] - [#144404])
|
||||||
|
|
||||||
|
## Release 2025.5.1 - May 9
|
||||||
|
|
||||||
|
- Fix Z-Wave restore nvm command to wait for driver ready ([@MartinHjelmare] - [#144413])
|
||||||
|
- fix homekit air purifier temperature sensor to convert unit ([@tamwahba] - [#144435])
|
||||||
|
- Add LAP-V102S-AUSR to VeSync ([@DukeChocula] - [#144437])
|
||||||
|
- Bump pylamarzocco to 2.0.1 ([@zweckj] - [#144454])
|
||||||
|
- Fix Z-Wave reset accumulated values button entity category ([@MartinHjelmare] - [#144459])
|
||||||
|
- Fix point import error ([@fredrike] - [#144462])
|
||||||
|
- Ignore Fronius Gen24 firmware 1.35.4-1 SSL verification issue ([@farmio] - [#144463])
|
||||||
|
- Don't encrypt or decrypt unknown files in backup archives ([@emontnemery] - [#144495])
|
||||||
|
- Bump forecast-solar to 4.2.0 ([@bdraco] - [#144502])
|
||||||
|
- Fix removing of smarthome templates on startup of AVM Fritz!SmartHome integration ([@mib1185] - [#144506])
|
||||||
|
- Bump aiodns to 3.4.0 ([@bdraco] - [#144511])
|
||||||
|
- Fix statistics coordinator subscription for lamarzocco ([@zweckj] - [#144541])
|
||||||
|
- Update frontend to 20250509.0 ([@bramkragten] - [#144549])
|
||||||
|
- Reolink clean device registry mac ([@starkillerOG] - [#144554])
|
||||||
|
- Prevent errors during cleaning of connections/identifiers in device registry ([@starkillerOG] - [#144558])
|
||||||
|
|
||||||
|
[#144406]: https://github.com/home-assistant/core/pull/144406
|
||||||
|
[#144413]: https://github.com/home-assistant/core/pull/144413
|
||||||
|
[#144435]: https://github.com/home-assistant/core/pull/144435
|
||||||
|
[#144437]: https://github.com/home-assistant/core/pull/144437
|
||||||
|
[#144454]: https://github.com/home-assistant/core/pull/144454
|
||||||
|
[#144459]: https://github.com/home-assistant/core/pull/144459
|
||||||
|
[#144462]: https://github.com/home-assistant/core/pull/144462
|
||||||
|
[#144463]: https://github.com/home-assistant/core/pull/144463
|
||||||
|
[#144495]: https://github.com/home-assistant/core/pull/144495
|
||||||
|
[#144502]: https://github.com/home-assistant/core/pull/144502
|
||||||
|
[#144506]: https://github.com/home-assistant/core/pull/144506
|
||||||
|
[#144511]: https://github.com/home-assistant/core/pull/144511
|
||||||
|
[#144541]: https://github.com/home-assistant/core/pull/144541
|
||||||
|
[#144549]: https://github.com/home-assistant/core/pull/144549
|
||||||
|
[#144554]: https://github.com/home-assistant/core/pull/144554
|
||||||
|
[#144558]: https://github.com/home-assistant/core/pull/144558
|
||||||
|
[@DukeChocula]: https://github.com/DukeChocula
|
||||||
|
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||||
|
[@bdraco]: https://github.com/bdraco
|
||||||
|
[@bramkragten]: https://github.com/bramkragten
|
||||||
|
[@emontnemery]: https://github.com/emontnemery
|
||||||
|
[@farmio]: https://github.com/farmio
|
||||||
|
[@fredrike]: https://github.com/fredrike
|
||||||
|
[@frenck]: https://github.com/frenck
|
||||||
|
[@mib1185]: https://github.com/mib1185
|
||||||
|
[@starkillerOG]: https://github.com/starkillerOG
|
||||||
|
[@tamwahba]: https://github.com/tamwahba
|
||||||
|
[@zweckj]: https://github.com/zweckj
|
||||||
|
|
||||||
|
## Release 2025.5.2 - May 16
|
||||||
|
|
||||||
|
- Allow dns hostnames to be retained for SMLIGHT user flow. ([@tl-sl] - [#142514])
|
||||||
|
- Removed unused file_id param from open_ai_conversation request ([@cadavre] - [#143878])
|
||||||
|
- Doorbell Event is fired just once in homematicip_cloud ([@hahn-th] - [#144357])
|
||||||
|
- Don't scale Roborock mop Path ([@Lash-L] - [#144421])
|
||||||
|
- Reolink fix privacy mode availability for NVR IPC cams ([@starkillerOG] - [#144569])
|
||||||
|
- Bump aiodiscover to 2.7.0 ([@bdraco] - [#144571])
|
||||||
|
- Bump reolink_aio to 0.13.3 ([@starkillerOG] - [#144583])
|
||||||
|
- Mark inkbird coordinator as not needing connectable ([@bdraco] - [#144584])
|
||||||
|
- fix enphase_envoy diagnostics home endpoint name ([@catsmanac] - [#144634])
|
||||||
|
- Bump pylamarzocco to 2.0.2 ([@zweckj] - [#144635])
|
||||||
|
- bump pyenphase to 1.26.1 ([@catsmanac] - [#144641])
|
||||||
|
- Bump ical to 9.2.1 ([@allenporter] - [#144642])
|
||||||
|
- Bump python-linkplay to v0.2.5 ([@silamon] - [#144666])
|
||||||
|
- Close Octoprint aiohttp session on unload ([@RubenNL] - [#144670])
|
||||||
|
- Bump holidays to 0.72 ([@gjohansson-ST] - [#144671])
|
||||||
|
- Fix strings typo for Comelit ([@chemelli74] - [#144672])
|
||||||
|
- Avoid closing shared session for Comelit ([@chemelli74] - [#144682])
|
||||||
|
- Fix wrong state in Husqvarna Automower ([@Thomas55555] - [#144684])
|
||||||
|
- Bump voluptuous-openapi to 0.1.0 ([@allenporter] - [#144703])
|
||||||
|
- Bump ical to 9.2.2 ([@allenporter] - [#144713])
|
||||||
|
- Bump gcal-sync to 7.0.1 ([@oyvindwe] - [#144718])
|
||||||
|
- Bump aiocomelit to 0.12.1 ([@chemelli74] - [#144720])
|
||||||
|
- Fix Netgear handeling of missing MAC in device registry ([@starkillerOG] - [#144722])
|
||||||
|
- Repair Z-Wave unknown controller ([@MartinHjelmare] - [#144738])
|
||||||
|
- Fill in Plaato URL via placeholders ([@joostlek] - [#144754])
|
||||||
|
- Cleanup wrongly combined Reolink devices ([@starkillerOG] - [#144771])
|
||||||
|
- Do not show an empty component name on MQTT device subentries not as `None` if it is not set ([@jbouwh] - [#144792])
|
||||||
|
- Fix blocking call in azure storage ([@zweckj] - [#144803])
|
||||||
|
- Fix Z-Wave unique id after controller reset ([@MartinHjelmare] - [#144813])
|
||||||
|
- Fix blocking call in azure_storage config flow ([@zweckj] - [#144818])
|
||||||
|
- Bump pylamarzocco to 2.0.3 ([@zweckj] - [#144825])
|
||||||
|
- Bump python-snoo to 0.6.6 ([@Lash-L] - [#144849])
|
||||||
|
- Bump ical to 9.2.4 ([@allenporter] - [#144852])
|
||||||
|
- Fix wall connector states in Teslemetry ([@Bre77] - [#144855])
|
||||||
|
- Fix Reolink setup when ONVIF push is unsupported ([@starkillerOG] - [#144869])
|
||||||
|
- Fix some Home Connect translation strings ([@rjblake] - [#144905])
|
||||||
|
- Update Tibber lib 0.31.2 ([@Danielhiversen] - [#144908])
|
||||||
|
- Update mill library 0.12.5 ([@Danielhiversen] - [#144911])
|
||||||
|
- Fix unknown Pure AQI in Sensibo ([@gjohansson-ST] - [#144924])
|
||||||
|
- Ignore Fronius Gen24 firmware 1.35.4-1 SSL verification issue for new setups ([@farmio] - [#144940])
|
||||||
|
- Fix Home Assistant Yellow config entry data ([@emontnemery] - [#144948])
|
||||||
|
- Bump deebot-client to 13.2.0 ([@edenhaus] - [#144957])
|
||||||
|
- Fix ESPHome entities unavailable if deep sleep enabled after entry setup ([@oddstr13] - [#144970])
|
||||||
|
- Strip `_CLIENT` suffix from ZHA event `unique_id` ([@puddly] - [#145006])
|
||||||
|
- Bump pySmartThings to 3.2.2 ([@joostlek] - [#145033])
|
||||||
|
- Set SmartThings oven setpoint to unknown if its 1 Fahrenheit ([@joostlek] - [#145038])
|
||||||
|
- Fix climate idle state for Comelit ([@chemelli74] - [#145059])
|
||||||
|
- Map SmartThings auto mode correctly ([@joostlek] - [#145061])
|
||||||
|
- Update frontend to 20250516.0 ([@bramkragten] - [#145062])
|
||||||
|
- Only set suggested area for new SmartThings devices ([@joostlek] - [#145063])
|
||||||
|
- Fix fan AC mode in SmartThings AC ([@joostlek] - [#145064])
|
||||||
|
- Don't create entities for Smartthings smarttags ([@joostlek] - [#145066])
|
||||||
|
- Fix Ecovacs mower area sensors ([@edenhaus] - [#145071])
|
||||||
|
|
||||||
|
[#142514]: https://github.com/home-assistant/core/pull/142514
|
||||||
|
[#143878]: https://github.com/home-assistant/core/pull/143878
|
||||||
|
[#144357]: https://github.com/home-assistant/core/pull/144357
|
||||||
|
[#144406]: https://github.com/home-assistant/core/pull/144406
|
||||||
|
[#144421]: https://github.com/home-assistant/core/pull/144421
|
||||||
|
[#144564]: https://github.com/home-assistant/core/pull/144564
|
||||||
|
[#144569]: https://github.com/home-assistant/core/pull/144569
|
||||||
|
[#144571]: https://github.com/home-assistant/core/pull/144571
|
||||||
|
[#144583]: https://github.com/home-assistant/core/pull/144583
|
||||||
|
[#144584]: https://github.com/home-assistant/core/pull/144584
|
||||||
|
[#144634]: https://github.com/home-assistant/core/pull/144634
|
||||||
|
[#144635]: https://github.com/home-assistant/core/pull/144635
|
||||||
|
[#144641]: https://github.com/home-assistant/core/pull/144641
|
||||||
|
[#144642]: https://github.com/home-assistant/core/pull/144642
|
||||||
|
[#144666]: https://github.com/home-assistant/core/pull/144666
|
||||||
|
[#144670]: https://github.com/home-assistant/core/pull/144670
|
||||||
|
[#144671]: https://github.com/home-assistant/core/pull/144671
|
||||||
|
[#144672]: https://github.com/home-assistant/core/pull/144672
|
||||||
|
[#144682]: https://github.com/home-assistant/core/pull/144682
|
||||||
|
[#144684]: https://github.com/home-assistant/core/pull/144684
|
||||||
|
[#144703]: https://github.com/home-assistant/core/pull/144703
|
||||||
|
[#144713]: https://github.com/home-assistant/core/pull/144713
|
||||||
|
[#144718]: https://github.com/home-assistant/core/pull/144718
|
||||||
|
[#144720]: https://github.com/home-assistant/core/pull/144720
|
||||||
|
[#144722]: https://github.com/home-assistant/core/pull/144722
|
||||||
|
[#144738]: https://github.com/home-assistant/core/pull/144738
|
||||||
|
[#144754]: https://github.com/home-assistant/core/pull/144754
|
||||||
|
[#144771]: https://github.com/home-assistant/core/pull/144771
|
||||||
|
[#144792]: https://github.com/home-assistant/core/pull/144792
|
||||||
|
[#144803]: https://github.com/home-assistant/core/pull/144803
|
||||||
|
[#144813]: https://github.com/home-assistant/core/pull/144813
|
||||||
|
[#144818]: https://github.com/home-assistant/core/pull/144818
|
||||||
|
[#144825]: https://github.com/home-assistant/core/pull/144825
|
||||||
|
[#144849]: https://github.com/home-assistant/core/pull/144849
|
||||||
|
[#144852]: https://github.com/home-assistant/core/pull/144852
|
||||||
|
[#144855]: https://github.com/home-assistant/core/pull/144855
|
||||||
|
[#144869]: https://github.com/home-assistant/core/pull/144869
|
||||||
|
[#144905]: https://github.com/home-assistant/core/pull/144905
|
||||||
|
[#144908]: https://github.com/home-assistant/core/pull/144908
|
||||||
|
[#144911]: https://github.com/home-assistant/core/pull/144911
|
||||||
|
[#144924]: https://github.com/home-assistant/core/pull/144924
|
||||||
|
[#144940]: https://github.com/home-assistant/core/pull/144940
|
||||||
|
[#144948]: https://github.com/home-assistant/core/pull/144948
|
||||||
|
[#144957]: https://github.com/home-assistant/core/pull/144957
|
||||||
|
[#144970]: https://github.com/home-assistant/core/pull/144970
|
||||||
|
[#145006]: https://github.com/home-assistant/core/pull/145006
|
||||||
|
[#145033]: https://github.com/home-assistant/core/pull/145033
|
||||||
|
[#145038]: https://github.com/home-assistant/core/pull/145038
|
||||||
|
[#145059]: https://github.com/home-assistant/core/pull/145059
|
||||||
|
[#145061]: https://github.com/home-assistant/core/pull/145061
|
||||||
|
[#145062]: https://github.com/home-assistant/core/pull/145062
|
||||||
|
[#145063]: https://github.com/home-assistant/core/pull/145063
|
||||||
|
[#145064]: https://github.com/home-assistant/core/pull/145064
|
||||||
|
[#145066]: https://github.com/home-assistant/core/pull/145066
|
||||||
|
[#145071]: https://github.com/home-assistant/core/pull/145071
|
||||||
|
[@Bre77]: https://github.com/Bre77
|
||||||
|
[@Danielhiversen]: https://github.com/Danielhiversen
|
||||||
|
[@Lash-L]: https://github.com/Lash-L
|
||||||
|
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||||
|
[@RubenNL]: https://github.com/RubenNL
|
||||||
|
[@Thomas55555]: https://github.com/Thomas55555
|
||||||
|
[@allenporter]: https://github.com/allenporter
|
||||||
|
[@bdraco]: https://github.com/bdraco
|
||||||
|
[@bramkragten]: https://github.com/bramkragten
|
||||||
|
[@cadavre]: https://github.com/cadavre
|
||||||
|
[@catsmanac]: https://github.com/catsmanac
|
||||||
|
[@chemelli74]: https://github.com/chemelli74
|
||||||
|
[@edenhaus]: https://github.com/edenhaus
|
||||||
|
[@emontnemery]: https://github.com/emontnemery
|
||||||
|
[@farmio]: https://github.com/farmio
|
||||||
|
[@frenck]: https://github.com/frenck
|
||||||
|
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||||
|
[@hahn-th]: https://github.com/hahn-th
|
||||||
|
[@jbouwh]: https://github.com/jbouwh
|
||||||
|
[@joostlek]: https://github.com/joostlek
|
||||||
|
[@oddstr13]: https://github.com/oddstr13
|
||||||
|
[@oyvindwe]: https://github.com/oyvindwe
|
||||||
|
[@puddly]: https://github.com/puddly
|
||||||
|
[@rjblake]: https://github.com/rjblake
|
||||||
|
[@silamon]: https://github.com/silamon
|
||||||
|
[@starkillerOG]: https://github.com/starkillerOG
|
||||||
|
[@tl-sl]: https://github.com/tl-sl
|
||||||
|
[@zweckj]: https://github.com/zweckj
|
||||||
|
|
||||||
|
## Release 2025.5.3 - May 23
|
||||||
|
|
||||||
|
- Netatmo: do not fail on schedule updates ([@wuede] - [#142933])
|
||||||
|
- Fix QNAP fail to load ([@disforw] - [#144675])
|
||||||
|
- Allow image send with read-only access (matrix notify) ([@TheOneValen] - [#144819])
|
||||||
|
- Postpone update in WMSPro after service call ([@mback2k] - [#144836])
|
||||||
|
- Bump ESPHome stable BLE version to 2025.5.0 ([@bdraco] - [#144857])
|
||||||
|
- Fix album and artist returning "None" rather than None for Squeezebox media player. ([@peteS-UK] - [#144971])
|
||||||
|
- Bump aiontfy to 0.5.2 ([@tr4nt0r] - [#145044])
|
||||||
|
- Fix proberly Ecovacs mower area sensors ([@edenhaus] - [#145078])
|
||||||
|
- Map auto to heat_cool for thermostat in SmartThings ([@joostlek] - [#145098])
|
||||||
|
- Add missing device condition translations to lock component ([@jpbede] - [#145104])
|
||||||
|
- Fix history_stats with sliding window that ends before now ([@karwosts] - [#145117])
|
||||||
|
- Bump sense-energy to 0.13.8 ([@kbickar] - [#145156])
|
||||||
|
- Improve Z-Wave config flow tests ([@MartinHjelmare] - [#144871])
|
||||||
|
- Fix Z-Wave unique id update during controller migration ([@MartinHjelmare] - [#145185])
|
||||||
|
- Bump velbusaio to 2025.5.0 ([@cereal2nd] - [#145198])
|
||||||
|
- Bump aiocomelit to 0.12.3 ([@chemelli74] - [#145209])
|
||||||
|
- Fix Z-Wave config entry unique id after NVM restore ([@MartinHjelmare] - [#145221])
|
||||||
|
- Bump holidays to 0.73 ([@gjohansson-ST] - [#145238])
|
||||||
|
- Bump pyaprilaire to 0.9.0 ([@chamberlain2007] - [#145260])
|
||||||
|
- Add cloud as after_dependency to onedrive ([@zweckj] - [#145301])
|
||||||
|
- Handle more exceptions in azure_storage ([@zweckj] - [#145320])
|
||||||
|
- Fix limit of shown backups on Synology DSM location ([@mib1185] - [#145342])
|
||||||
|
- Add initial coordinator refresh for players in Squeezebox ([@peteS-UK] - [#145347])
|
||||||
|
- Fix: Revert Ecovacs mower total_stats_area unit to square meters ([@Augar] - [#145380])
|
||||||
|
- Bump pysqueezebox to v0.12.1 ([@rajlaud] - [#145384])
|
||||||
|
- OTBR: remove links to obsolete multiprotocol docs ([@c0ffeeca7] - [#145394])
|
||||||
|
- Bump pylamarzocco to 2.0.4 ([@zweckj] - [#145402])
|
||||||
|
- Bump py-synologydsm-api to 2.7.2 ([@mib1185] - [#145403])
|
||||||
|
- Mark backflush binary sensor not supported for GS3 MP in lamarzocco ([@zweckj] - [#145406])
|
||||||
|
- Bump yt-dlp to 2025.05.22 ([@joostlek] - [#145441])
|
||||||
|
- Reolink fix device migration ([@starkillerOG] - [#145443])
|
||||||
|
- Bump pysmartthings to 3.2.3 ([@joostlek] - [#145444])
|
||||||
|
- Bump opower to 0.12.1 ([@tronikos] - [#145464])
|
||||||
|
- Make Gemma models work in Google AI ([@tronikos] - [#145479])
|
||||||
|
- Fix strings related to Google search tool in Google AI ([@tronikos] - [#145480])
|
||||||
|
- Bump pyfibaro to 0.8.3 ([@rappenze] - [#145488])
|
||||||
|
- Bump deebot-client to 13.2.1 ([@edenhaus] - [#145492])
|
||||||
|
|
||||||
|
[#142933]: https://github.com/home-assistant/core/pull/142933
|
||||||
|
[#144406]: https://github.com/home-assistant/core/pull/144406
|
||||||
|
[#144564]: https://github.com/home-assistant/core/pull/144564
|
||||||
|
[#144675]: https://github.com/home-assistant/core/pull/144675
|
||||||
|
[#144819]: https://github.com/home-assistant/core/pull/144819
|
||||||
|
[#144836]: https://github.com/home-assistant/core/pull/144836
|
||||||
|
[#144857]: https://github.com/home-assistant/core/pull/144857
|
||||||
|
[#144871]: https://github.com/home-assistant/core/pull/144871
|
||||||
|
[#144971]: https://github.com/home-assistant/core/pull/144971
|
||||||
|
[#145044]: https://github.com/home-assistant/core/pull/145044
|
||||||
|
[#145072]: https://github.com/home-assistant/core/pull/145072
|
||||||
|
[#145078]: https://github.com/home-assistant/core/pull/145078
|
||||||
|
[#145098]: https://github.com/home-assistant/core/pull/145098
|
||||||
|
[#145104]: https://github.com/home-assistant/core/pull/145104
|
||||||
|
[#145117]: https://github.com/home-assistant/core/pull/145117
|
||||||
|
[#145156]: https://github.com/home-assistant/core/pull/145156
|
||||||
|
[#145185]: https://github.com/home-assistant/core/pull/145185
|
||||||
|
[#145198]: https://github.com/home-assistant/core/pull/145198
|
||||||
|
[#145209]: https://github.com/home-assistant/core/pull/145209
|
||||||
|
[#145221]: https://github.com/home-assistant/core/pull/145221
|
||||||
|
[#145238]: https://github.com/home-assistant/core/pull/145238
|
||||||
|
[#145260]: https://github.com/home-assistant/core/pull/145260
|
||||||
|
[#145301]: https://github.com/home-assistant/core/pull/145301
|
||||||
|
[#145320]: https://github.com/home-assistant/core/pull/145320
|
||||||
|
[#145342]: https://github.com/home-assistant/core/pull/145342
|
||||||
|
[#145347]: https://github.com/home-assistant/core/pull/145347
|
||||||
|
[#145380]: https://github.com/home-assistant/core/pull/145380
|
||||||
|
[#145384]: https://github.com/home-assistant/core/pull/145384
|
||||||
|
[#145394]: https://github.com/home-assistant/core/pull/145394
|
||||||
|
[#145402]: https://github.com/home-assistant/core/pull/145402
|
||||||
|
[#145403]: https://github.com/home-assistant/core/pull/145403
|
||||||
|
[#145406]: https://github.com/home-assistant/core/pull/145406
|
||||||
|
[#145441]: https://github.com/home-assistant/core/pull/145441
|
||||||
|
[#145443]: https://github.com/home-assistant/core/pull/145443
|
||||||
|
[#145444]: https://github.com/home-assistant/core/pull/145444
|
||||||
|
[#145464]: https://github.com/home-assistant/core/pull/145464
|
||||||
|
[#145479]: https://github.com/home-assistant/core/pull/145479
|
||||||
|
[#145480]: https://github.com/home-assistant/core/pull/145480
|
||||||
|
[#145488]: https://github.com/home-assistant/core/pull/145488
|
||||||
|
[#145492]: https://github.com/home-assistant/core/pull/145492
|
||||||
|
[@Augar]: https://github.com/Augar
|
||||||
|
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||||
|
[@TheOneValen]: https://github.com/TheOneValen
|
||||||
|
[@bdraco]: https://github.com/bdraco
|
||||||
|
[@c0ffeeca7]: https://github.com/c0ffeeca7
|
||||||
|
[@cereal2nd]: https://github.com/cereal2nd
|
||||||
|
[@chamberlain2007]: https://github.com/chamberlain2007
|
||||||
|
[@chemelli74]: https://github.com/chemelli74
|
||||||
|
[@disforw]: https://github.com/disforw
|
||||||
|
[@edenhaus]: https://github.com/edenhaus
|
||||||
|
[@frenck]: https://github.com/frenck
|
||||||
|
[@gjohansson-ST]: https://github.com/gjohansson-ST
|
||||||
|
[@joostlek]: https://github.com/joostlek
|
||||||
|
[@jpbede]: https://github.com/jpbede
|
||||||
|
[@karwosts]: https://github.com/karwosts
|
||||||
|
[@kbickar]: https://github.com/kbickar
|
||||||
|
[@mback2k]: https://github.com/mback2k
|
||||||
|
[@mib1185]: https://github.com/mib1185
|
||||||
|
[@peteS-UK]: https://github.com/peteS-UK
|
||||||
|
[@rajlaud]: https://github.com/rajlaud
|
||||||
|
[@rappenze]: https://github.com/rappenze
|
||||||
|
[@starkillerOG]: https://github.com/starkillerOG
|
||||||
|
[@tr4nt0r]: https://github.com/tr4nt0r
|
||||||
|
[@tronikos]: https://github.com/tronikos
|
||||||
|
[@wuede]: https://github.com/wuede
|
||||||
|
[@zweckj]: https://github.com/zweckj
|
||||||
|
|
||||||
[#126150]: https://github.com/home-assistant/core/pull/126150
|
[#126150]: https://github.com/home-assistant/core/pull/126150
|
||||||
[#126775]: https://github.com/home-assistant/core/pull/126775
|
[#126775]: https://github.com/home-assistant/core/pull/126775
|
||||||
[#127875]: https://github.com/home-assistant/core/pull/127875
|
[#127875]: https://github.com/home-assistant/core/pull/127875
|
||||||
|
|||||||
@ -203,7 +203,7 @@ frontpage_image: /images/frontpage/feature-zbt1.jpg
|
|||||||
When we launched this device, we announced our intent to release firmware supporting multiprotocol, which allows the device's Silicon Labs chip to connect to both Zigbee and Thread networks with one radio. <br /><br />
|
When we launched this device, we announced our intent to release firmware supporting multiprotocol, which allows the device's Silicon Labs chip to connect to both Zigbee and Thread networks with one radio. <br /><br />
|
||||||
This experimental firmware has been available since December 2022. Through extensive testing, we have found that although it works in some circumstances, it has technical limitations that lead to a worse user experience. We now do not recommend using this firmware, and it will be experimental for the foreseeable future. Instead, we will focus on making sure the dedicated Zigbee and Thread firmwares for Home Assistant Connect ZBT-1 deliver the best experience to users.<br /><br />
|
This experimental firmware has been available since December 2022. Through extensive testing, we have found that although it works in some circumstances, it has technical limitations that lead to a worse user experience. We now do not recommend using this firmware, and it will be experimental for the foreseeable future. Instead, we will focus on making sure the dedicated Zigbee and Thread firmwares for Home Assistant Connect ZBT-1 deliver the best experience to users.<br /><br />
|
||||||
|
|
||||||
If you currently have the multiprotocol firmware installed but don't actively use it to connect to Thread devices, we recommend that you <a href="https://connectzbt1.home-assistant.io/procedures/disable-multiprotocol/">disable multiprotocol</a>. <br /><br />
|
If you currently have the multiprotocol firmware installed but don't actively use it to connect to Thread devices, we recommend that you <a href="https://support.nabucasa.com/hc/en-us/articles/26124969612445">disable multiprotocol</a>. <br /><br />
|
||||||
Nothing changes for current users of the multiprotocol firmware who are happy with their experience. The experimental multiprotocol firmware will remain available, but we will not recommend it to new users.
|
Nothing changes for current users of the multiprotocol firmware who are happy with their experience. The experimental multiprotocol firmware will remain available, but we will not recommend it to new users.
|
||||||
{% enddetails %}
|
{% enddetails %}
|
||||||
|
|
||||||
@ -218,7 +218,7 @@ frontpage_image: /images/frontpage/feature-zbt1.jpg
|
|||||||
1: Relies on the experimental EmberZNet support in Zigbee2MQTT.
|
1: Relies on the experimental EmberZNet support in Zigbee2MQTT.
|
||||||
</div>
|
</div>
|
||||||
<div class="material-card text spaced-card" style="margin-top: 72px;">
|
<div class="material-card text spaced-card" style="margin-top: 72px;">
|
||||||
<a href="https://connectzbt1.home-assistant.io/" target="_blank"
|
<a href="https://support.nabucasa.com/hc/en-us/categories/24734620813469" target="_blank"
|
||||||
class="documentation-card">
|
class="documentation-card">
|
||||||
<div class="content-container">
|
<div class="content-container">
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
@ -26,8 +26,8 @@ After Home Assistant has been [installed](/installation/) on your device, there
|
|||||||
- Select **Create account**.
|
- Select **Create account**.
|
||||||
|
|
||||||
- **Option 2: restore from backup**: If you want to restore a backup of a previous installation, follow the steps on [restoring from backup](/common-tasks/general/#restoring-a-backup).
|
- **Option 2: restore from backup**: If you want to restore a backup of a previous installation, follow the steps on [restoring from backup](/common-tasks/general/#restoring-a-backup).
|
||||||
- If you have a Home Assistant Yellow, follow the [Yellow documentation on restoring from backup](https://yellow.home-assistant.io/guides/restore-backup/).
|
- If you have a Home Assistant Yellow, follow the [Yellow documentation on restoring from backup](https://support.nabucasa.com/hc/en-us/articles/25454643790237).
|
||||||
- If you have a Home Assistant Green, follow the [Green documentation on restoring from backup](https://green.home-assistant.io/guides/restore-backup/).
|
- If you have a Home Assistant Green, follow the [Green documentation on restoring from backup](https://support.nabucasa.com/hc/en-us/articles/25160431579165).
|
||||||
|
|
||||||
3. Enter the location of your home.
|
3. Enter the location of your home.
|
||||||
- The home location is used to configure the time zone, unit system, and currency.
|
- The home location is used to configure the time zone, unit system, and currency.
|
||||||
|
|||||||
@ -481,7 +481,7 @@ dark_header: true
|
|||||||
<h2 class="heading-large">Great quality yet affordable.<br /></h2>
|
<h2 class="heading-large">Great quality yet affordable.<br /></h2>
|
||||||
</div>
|
</div>
|
||||||
<div class="uppercase-xxl text-green">
|
<div class="uppercase-xxl text-green">
|
||||||
$99<span class="text-span-3">*</span>
|
$119 / €99 <span class="text-span-3">*</span>
|
||||||
</div>
|
</div>
|
||||||
<div class="heading-wrapper-min">
|
<div class="heading-wrapper-min">
|
||||||
<p>
|
<p>
|
||||||
@ -490,7 +490,7 @@ dark_header: true
|
|||||||
the love with family and friends.
|
the love with family and friends.
|
||||||
</p>
|
</p>
|
||||||
<p class="small-legal-text">
|
<p class="small-legal-text">
|
||||||
* Recommended MSRP. Pricing subject to individual retailers.
|
* Recommended MSRP. Prices differ between regions due to varying local market costs and conditions, and subject to individual retailers.
|
||||||
</p>
|
</p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
@ -2280,7 +2280,7 @@ dark_header: true
|
|||||||
device.
|
device.
|
||||||
</p>
|
</p>
|
||||||
<a
|
<a
|
||||||
href="https://green.home-assistant.io"
|
href="https://support.nabucasa.com/hc/en-us/categories/24638797677853-Home-Assistant-Green"
|
||||||
class="button black w-inline-block"
|
class="button black w-inline-block"
|
||||||
><div>Get started</div>
|
><div>Get started</div>
|
||||||
<img
|
<img
|
||||||
|
|||||||
@ -1628,7 +1628,7 @@ h4.heading-small {
|
|||||||
text-transform: uppercase !important;
|
text-transform: uppercase !important;
|
||||||
margin-top: 0;
|
margin-top: 0;
|
||||||
margin-bottom: 0;
|
margin-bottom: 0;
|
||||||
font-size: 24em;
|
font-size: 14em;
|
||||||
font-weight: 300;
|
font-weight: 300;
|
||||||
line-height: 0.84;
|
line-height: 0.84;
|
||||||
display: flex;
|
display: flex;
|
||||||
@ -2489,7 +2489,7 @@ h4.heading-small {
|
|||||||
}
|
}
|
||||||
|
|
||||||
.uppercase-xxl {
|
.uppercase-xxl {
|
||||||
font-size: 10em;
|
font-size: 7em;
|
||||||
}
|
}
|
||||||
|
|
||||||
#w-node-_89c945ba-f261-0dc0-ba82-c8df58a88488-3f61e7c1,
|
#w-node-_89c945ba-f261-0dc0-ba82-c8df58a88488-3f61e7c1,
|
||||||
@ -3047,7 +3047,7 @@ h4.heading-small {
|
|||||||
}
|
}
|
||||||
|
|
||||||
.uppercase-xxl {
|
.uppercase-xxl {
|
||||||
font-size: 80px;
|
font-size: 70px;
|
||||||
}
|
}
|
||||||
|
|
||||||
.spin-section {
|
.spin-section {
|
||||||
|
|||||||
Binary file not shown.
|
Before Width: | Height: | Size: 221 KiB After Width: | Height: | Size: 260 KiB |
BIN
source/images/blog/2025-05-deprecation/analytics.png
Normal file
BIN
source/images/blog/2025-05-deprecation/analytics.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 76 KiB |
BIN
source/images/blog/2025-05-deprecation/art.png
Normal file
BIN
source/images/blog/2025-05-deprecation/art.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 113 KiB |
BIN
source/images/blog/2025-05-deprecation/methods.png
Normal file
BIN
source/images/blog/2025-05-deprecation/methods.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 30 KiB |
BIN
source/images/blog/2025-05-deprecation/system-information.png
Normal file
BIN
source/images/blog/2025-05-deprecation/system-information.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 76 KiB |
BIN
source/images/blog/2025-05-roadmap-2025h1/art.jpg
Normal file
BIN
source/images/blog/2025-05-roadmap-2025h1/art.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 47 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 63 KiB |
BIN
source/images/blog/2025-05-roadmap-2025h1/device-context.jpg
Normal file
BIN
source/images/blog/2025-05-roadmap-2025h1/device-context.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 65 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 77 KiB |
BIN
source/images/blog/2025-05-roadmap-2025h1/roadmap-2025-cover.png
Normal file
BIN
source/images/blog/2025-05-roadmap-2025h1/roadmap-2025-cover.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 65 KiB |
BIN
source/images/blog/2025-05-roadmap-2025h1/roadmap-2025.png
Normal file
BIN
source/images/blog/2025-05-roadmap-2025h1/roadmap-2025.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 66 KiB |
BIN
source/images/blog/2025-05-roadmap-2025h1/shared-wisdom.jpg
Normal file
BIN
source/images/blog/2025-05-roadmap-2025h1/shared-wisdom.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 60 KiB |
BIN
source/images/blog/2025-05-roadmap-2025h1/working-together.png
Normal file
BIN
source/images/blog/2025-05-roadmap-2025h1/working-together.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 42 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 207 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 32 KiB |
@ -9,4 +9,3 @@ Included sections for this page is located under source/_includes/installation
|
|||||||
|
|
||||||
{% include installation/operating_system.md %}
|
{% include installation/operating_system.md %}
|
||||||
{% include installation/container.md %}
|
{% include installation/container.md %}
|
||||||
{% include installation/core.md %}
|
|
||||||
|
|||||||
@ -35,7 +35,7 @@ Included sections for this page is located under source/_includes/installation
|
|||||||
<div class="content-container">
|
<div class="content-container">
|
||||||
<div>
|
<div>
|
||||||
<p>For installation instructions, check out the <a
|
<p>For installation instructions, check out the <a
|
||||||
href="https://green.home-assistant.io/">Home Assistant Green documentation</a></p>
|
href="https://support.nabucasa.com/hc/en-us/categories/24638797677853-Home-Assistant-Green">Home Assistant Green documentation</a></p>
|
||||||
<p><img src="/images/installation/green_docs.png" style="margin-bottom: 16px;"></p>
|
<p><img src="/images/installation/green_docs.png" style="margin-bottom: 16px;"></p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|||||||
@ -53,7 +53,7 @@ toc: true
|
|||||||
%}</a
|
%}</a
|
||||||
>
|
>
|
||||||
<a
|
<a
|
||||||
href="https://green.home-assistant.io"
|
href="https://support.nabucasa.com/hc/en-us/categories/24638797677853-Home-Assistant-Green"
|
||||||
class="button"
|
class="button"
|
||||||
target="_blank"
|
target="_blank"
|
||||||
>View tutorial {% include assets/chevron_right.html %}</a
|
>View tutorial {% include assets/chevron_right.html %}</a
|
||||||
@ -157,7 +157,7 @@ toc: true
|
|||||||
%}</a
|
%}</a
|
||||||
>
|
>
|
||||||
<a
|
<a
|
||||||
href="https://yellow.home-assistant.io"
|
href="https://support.nabucasa.com/hc/en-us/categories/24734575925149-Home-Assistant-Yellow"
|
||||||
class="button"
|
class="button"
|
||||||
target="_blank"
|
target="_blank"
|
||||||
>View tutorial {% include assets/chevron_right.html %}</a
|
>View tutorial {% include assets/chevron_right.html %}</a
|
||||||
@ -254,73 +254,51 @@ toc: true
|
|||||||
|
|
||||||
<span class="label expert">Expert</span>
|
<span class="label expert">Expert</span>
|
||||||
|
|
||||||
<h2>Advanced installation methods</h2>
|
<h2>About installation methods</h2>
|
||||||
<p>
|
<p>
|
||||||
Home Assistant offers four different installation methods. We recommend
|
Home Assistant offers two different installation methods:
|
||||||
using Home Assistant Operating System. Other methods are available for
|
|
||||||
experienced users for their specific needs, for example, running Home
|
|
||||||
Assistant in a virtualized environment (e.g. Proxmox), or on top of an
|
|
||||||
existing operating system (e.g. Windows, macOS, Linux):
|
|
||||||
</p>
|
</p>
|
||||||
<ul>
|
<ul>
|
||||||
|
<li><b>Home Assistant Operating System</b>: An embedded,
|
||||||
|
minimalistic operating system designed to run the Home Assistant ecosystem
|
||||||
|
on single board computers (like the Home Assistant Green or a Raspberry Pi) or Virtual Machines. It
|
||||||
|
is the most convenient option in terms of installation and maintenance and it supports
|
||||||
|
{% term "add-ons" %}. Home Assistant Operating System is
|
||||||
|
the recommended installation method for most users.</li>
|
||||||
<li>
|
<li>
|
||||||
<b>Home Assistant Container:</b> Standalone container-based installation
|
<b>Home Assistant Container:</b>Container-based installation of Home Assistant. You need to bring your own system (such as Linux) with container orchestration (like Docker), and manually handle updates. Home Assistant Container installations don’t have access to {% term "add-ons" %}.
|
||||||
of Home Assistant Core (e.g. Docker).
|
|
||||||
</li>
|
|
||||||
<li>
|
|
||||||
<b>Home Assistant Supervised:</b> Manual installation of the Supervisor.
|
|
||||||
</li>
|
|
||||||
<li>
|
|
||||||
<b>Home Assistant Core:</b> Manual installation using Python virtual
|
|
||||||
environment.
|
|
||||||
</li>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
<p>
|
|
||||||
Note that while these installation methods may provide some
|
|
||||||
features for advanced users, they may also have some major limitations.
|
|
||||||
For example, add-ons and other important Home Assistant features may not be available.
|
|
||||||
</p>
|
|
||||||
<div class="compare-installations">
|
<div class="compare-installations">
|
||||||
<table>
|
<table>
|
||||||
<th></th>
|
<th></th>
|
||||||
<th>HA OS<sup>1</sup></th>
|
<th>HA OS<sup>1</sup></th>
|
||||||
<th>Container<sup>1</sup></th>
|
<th>Container<sup>1</sup></th>
|
||||||
<th>Core<sup>1</sup></th>
|
|
||||||
<th>Supervised<sup>1</sup></th>
|
|
||||||
<tr>
|
<tr>
|
||||||
<td><a href="/docs/automation" target="_blank">Automations</a></td>
|
<td><a href="/docs/automation" target="_blank">Automations</a></td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
<td>{% icon "openmoji:check-mark" %}</td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
<td>{% icon "openmoji:check-mark" %}</td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td><a href="/dashboards" target="_blank">Dashboards</a></td>
|
<td><a href="/dashboards" target="_blank">Dashboards</a></td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
<td>{% icon "openmoji:check-mark" %}</td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
<td>{% icon "openmoji:check-mark" %}</td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td><a href="/integrations" target="_blank">Integrations</a></td>
|
<td><a href="/integrations" target="_blank">Integrations</a></td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
<td>{% icon "openmoji:check-mark" %}</td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
<td>{% icon "openmoji:check-mark" %}</td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td><a href="/addons" target="_blank">Add-ons</a></td>
|
<td><a href="/addons" target="_blank">Add-ons</a></td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
<td>{% icon "openmoji:check-mark" %}</td>
|
||||||
<td>{% icon "openmoji:cross-mark" %}</td>
|
<td>{% icon "openmoji:cross-mark" %}</td>
|
||||||
<td>{% icon "openmoji:cross-mark" %}</td>
|
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td><a href="/docs/blueprint" target="_blank">Blueprints</a></td>
|
<td><a href="/docs/blueprint" target="_blank">Blueprints</a></td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
<td>{% icon "openmoji:check-mark" %}</td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
<td>{% icon "openmoji:check-mark" %}</td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td>
|
<td>
|
||||||
@ -328,15 +306,11 @@ toc: true
|
|||||||
</td>
|
</td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
<td>{% icon "openmoji:check-mark" %}</td>
|
||||||
<td>{% icon "openmoji:cross-mark" %}</td>
|
<td>{% icon "openmoji:cross-mark" %}</td>
|
||||||
<td>{% icon "openmoji:cross-mark" %}</td>
|
|
||||||
<td>{% icon "noto-v1:check-mark" %}<sup>2</sup></td>
|
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td><a href="/common-tasks/general/#backups" target="_blank">Backups</a></td>
|
<td><a href="/common-tasks/general/#backups" target="_blank">Backups</a></td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
<td>{% icon "openmoji:check-mark" %}</td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
<td>{% icon "openmoji:check-mark" %}</td>
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
|
||||||
<td>{% icon "openmoji:check-mark" %}</td>
|
|
||||||
</tr>
|
</tr>
|
||||||
</table>
|
</table>
|
||||||
</div>
|
</div>
|
||||||
@ -346,15 +320,23 @@ toc: true
|
|||||||
<ul>
|
<ul>
|
||||||
<li style="margin-top: 0.4em">Home Assistant Operating System</li>
|
<li style="margin-top: 0.4em">Home Assistant Operating System</li>
|
||||||
<li style="margin-top: 15px">Home Assistant Container</li>
|
<li style="margin-top: 15px">Home Assistant Container</li>
|
||||||
<li style="margin-top: 15px">Home Assistant Core</li>
|
|
||||||
<li style="margin-top: 15px">Home Assistant Supervised</li>
|
|
||||||
</ul></sub
|
</ul></sub
|
||||||
>
|
>
|
||||||
<p>
|
<p>
|
||||||
<sub
|
|
||||||
>2: Home Assistant Supervised requires users to maintain their own operating system.</sub
|
|
||||||
>
|
|
||||||
</p>
|
</p>
|
||||||
|
<h3>Deprecated installation methods</h3>
|
||||||
|
<p>
|
||||||
|
Home Assistant used to offer two additional installation methods for advanced users: <b>{% term "Home Assistant Core" %}</b> and <b>{% term "Home Assistant Supervised" %}</b>. These two methods are now <a href="https://www.home-assistant.io/blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/">deprecated and no longer recommended for new users</a>.
|
||||||
|
</p>
|
||||||
|
<ul>
|
||||||
|
<li>
|
||||||
|
<b>Home Assistant Supervised:</b> Manual installation of the Supervisor.
|
||||||
|
</li>
|
||||||
|
<li>
|
||||||
|
<b>Home Assistant Core:</b> Manual installation using Python virtual
|
||||||
|
environment.
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
<p></p>
|
<p></p>
|
||||||
<div class="installations-card">
|
<div class="installations-card">
|
||||||
<div class="material-card text">
|
<div class="material-card text">
|
||||||
@ -407,7 +389,7 @@ toc: true
|
|||||||
</div>
|
</div>
|
||||||
<div class="content">
|
<div class="content">
|
||||||
<h3>Install Home Assistant on Linux</h3>
|
<h3>Install Home Assistant on Linux</h3>
|
||||||
<p>Use Home Assistant OS, Container, Supervised, or Core</p>
|
<p>Use Home Assistant OS, Container</p>
|
||||||
<div class="columns">
|
<div class="columns">
|
||||||
<div>
|
<div>
|
||||||
<b>SKILLS REQUIRED</b>
|
<b>SKILLS REQUIRED</b>
|
||||||
@ -442,7 +424,7 @@ toc: true
|
|||||||
</div>
|
</div>
|
||||||
<div class="content">
|
<div class="content">
|
||||||
<h3>Install Home Assistant on macOS</h3>
|
<h3>Install Home Assistant on macOS</h3>
|
||||||
<p>Use Home Assistant OS on a VM, or install Core</p>
|
<p>Use Home Assistant OS on a VM</p>
|
||||||
<div class="columns">
|
<div class="columns">
|
||||||
<div>
|
<div>
|
||||||
<b>SKILLS REQUIRED</b>
|
<b>SKILLS REQUIRED</b>
|
||||||
@ -476,7 +458,7 @@ toc: true
|
|||||||
</div>
|
</div>
|
||||||
<div class="content">
|
<div class="content">
|
||||||
<h3>Install Home Assistant on Windows</h3>
|
<h3>Install Home Assistant on Windows</h3>
|
||||||
<p>Use Home Assistant OS on a VM, or Core on WSL</p>
|
<p>Use Home Assistant OS on a VM</p>
|
||||||
<div class="columns">
|
<div class="columns">
|
||||||
<div>
|
<div>
|
||||||
<b>SKILLS REQUIRED</b>
|
<b>SKILLS REQUIRED</b>
|
||||||
@ -491,7 +473,6 @@ toc: true
|
|||||||
<ul>
|
<ul>
|
||||||
<li>Machine with Windows installed</li>
|
<li>Machine with Windows installed</li>
|
||||||
<li>VirtualBox (for VM)</li>
|
<li>VirtualBox (for VM)</li>
|
||||||
<li>Windows Subsystem for Linux (for Core)</li>
|
|
||||||
</ul>
|
</ul>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
@ -527,7 +508,6 @@ toc: true
|
|||||||
<ul>
|
<ul>
|
||||||
<li>Machine with Windows installed</li>
|
<li>Machine with Windows installed</li>
|
||||||
<li>VirtualBox (for VM)</li>
|
<li>VirtualBox (for VM)</li>
|
||||||
<li>Windows Subsystem for Linux (for Core)</li>
|
|
||||||
</ul>
|
</ul>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|||||||
@ -9,8 +9,6 @@ Included sections for this page is located under source/_includes/installation
|
|||||||
|
|
||||||
{% include installation/operating_system.md %}
|
{% include installation/operating_system.md %}
|
||||||
{% include installation/container.md %}
|
{% include installation/container.md %}
|
||||||
{% include installation/core.md %}
|
|
||||||
{% include installation/supervised.md %}
|
|
||||||
|
|
||||||
## Troubleshooting
|
## Troubleshooting
|
||||||
|
|
||||||
|
|||||||
@ -8,4 +8,3 @@ Included sections for this page is located under source/_includes/installation
|
|||||||
{% endcomment %}
|
{% endcomment %}
|
||||||
|
|
||||||
{% include installation/operating_system.md %}
|
{% include installation/operating_system.md %}
|
||||||
{% include installation/core.md %}
|
|
||||||
|
|||||||
@ -9,6 +9,5 @@ Included sections for this page is located under source/_includes/installation
|
|||||||
|
|
||||||
{% include installation/operating_system.md %}
|
{% include installation/operating_system.md %}
|
||||||
{% include installation/container.md %}
|
{% include installation/container.md %}
|
||||||
{% include installation/core.md %}
|
|
||||||
|
|
||||||
_We get commissions for purchases made through links in this post._
|
_We get commissions for purchases made through links in this post._
|
||||||
|
|||||||
@ -11,7 +11,7 @@ Included section for this page is located under source/_includes/installation
|
|||||||
{% assign board = "Raspberry Pi" %}
|
{% assign board = "Raspberry Pi" %}
|
||||||
{% assign installation_media = "SD card" %}
|
{% assign installation_media = "SD card" %}
|
||||||
|
|
||||||
While we recommend Home Assistant OS, there are also alternative ways to install Home Assistant. Before you continue, be aware of the limitations and differences compared to Home Assistant OS. You can find more information on the [installation page](/installation/#advanced-installation-methods). Most notably,
|
While we recommend Home Assistant OS, there are also alternative ways to install Home Assistant. Before you continue, be aware of the limitations and differences compared to Home Assistant OS. You can find more information on the [installation page](/installation/#about-installation-methods). Most notably,
|
||||||
<a href="/addons">add-ons</a> are only available with the Home Assistant Operating System.
|
<a href="/addons">add-ons</a> are only available with the Home Assistant Operating System.
|
||||||
|
|
||||||
{% include installation/container.md %}
|
{% include installation/container.md %}
|
||||||
|
|||||||
@ -14,7 +14,7 @@ Included section for this page is located under source/_includes/installation
|
|||||||
|
|
||||||
We will need a few things to get started with installing Home Assistant.
|
We will need a few things to get started with installing Home Assistant.
|
||||||
|
|
||||||
- [Raspberry Pi 5](https://amzn.to/3UH6TcD) or [Raspberry Pi 4](https://amzn.to/2S0Gcl1) with [power supply](https://amzn.to/2ReZ2Vq) (neither the Raspberry Pi 3 Model A nor Model B have enough RAM to be stable).
|
- [Raspberry Pi 5](https://amzn.to/3UH6TcD) or [Raspberry Pi 4](https://amzn.to/2S0Gcl1) with [power supply](https://amzn.to/2ReZ2Vq) (make sure to choose a model with at least 2 GB of RAM).
|
||||||
- [Micro SD Card](https://amzn.to/2X0Z2di).
|
- [Micro SD Card](https://amzn.to/2X0Z2di).
|
||||||
- Ideally get one that is [Application Class 2](https://www.sdcard.org/developers/overview/application/index.html). Check for the label **A2** on the card. Application Class 2 cards perform better especially on small read and write operations and are better suited to host applications.
|
- Ideally get one that is [Application Class 2](https://www.sdcard.org/developers/overview/application/index.html). Check for the label **A2** on the card. Application Class 2 cards perform better especially on small read and write operations and are better suited to host applications.
|
||||||
- Make sure to use a card that provides at least 32 GB.
|
- Make sure to use a card that provides at least 32 GB.
|
||||||
|
|||||||
@ -39,8 +39,8 @@ To resolve this issue, try the following steps:
|
|||||||
6. Check your router's web interface to see what IP address is assigned to your Home Assistant installation.
|
6. Check your router's web interface to see what IP address is assigned to your Home Assistant installation.
|
||||||
- Enter this IP address (`http://x.x.x.x:8123`) directly into your browser.
|
- Enter this IP address (`http://x.x.x.x:8123`) directly into your browser.
|
||||||
7. If you still can’t reach Home Assistant, connect keyboard and monitor to the device Home Assistant is running on to access the console and see where Home Assistant gets stuck.
|
7. If you still can’t reach Home Assistant, connect keyboard and monitor to the device Home Assistant is running on to access the console and see where Home Assistant gets stuck.
|
||||||
- If you are using a Home Assistant Green, follow these steps [to access the console](https://green.home-assistant.io/guides/use-terminal/).
|
- If you are using a Home Assistant Green, follow these steps [to access the console](https://support.nabucasa.com/hc/en-us/articles/25153288092829).
|
||||||
- If you are using a Home Assistant Yellow, follow these steps [to access the console from Windows](https://yellow.home-assistant.io/guides/use-serial-console-windows/), or [to access the console from Linux or macOS](https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/).
|
- If you are using a Home Assistant Yellow, follow these steps [to access the console from Windows](https://support.nabucasa.com/hc/en-us/articles/25454894609693), or [to access the console from Linux or macOS](https://support.nabucasa.com/hc/en-us/articles/25454972435357).
|
||||||
8. [Reach out to our community for help](https://www.home-assistant.io/help/).
|
8. [Reach out to our community for help](https://www.home-assistant.io/help/).
|
||||||
|
|
||||||
## "Error installing Home Assistant"
|
## "Error installing Home Assistant"
|
||||||
|
|||||||
@ -8,4 +8,3 @@ Included sections for this page is located under source/_includes/installation
|
|||||||
{% endcomment %}
|
{% endcomment %}
|
||||||
|
|
||||||
{% include installation/operating_system.md %}
|
{% include installation/operating_system.md %}
|
||||||
{% include installation/core.md %}
|
|
||||||
|
|||||||
@ -36,7 +36,7 @@ Included sections for this page is located under source/_includes/installation
|
|||||||
<div>
|
<div>
|
||||||
<p>Already have the hardware?</p>
|
<p>Already have the hardware?</p>
|
||||||
<p>For installation instructions, check out the <a
|
<p>For installation instructions, check out the <a
|
||||||
href="https://yellow.home-assistant.io/">Home Assistant Yellow documentation</a></p>
|
href="https://support.nabucasa.com/hc/en-us/categories/24734575925149-Home-Assistant-Yellow">Home Assistant Yellow documentation</a></p>
|
||||||
<p><img src="/images/installation/yellow-docs.png" style="margin-bottom: 16px;"></p>
|
<p><img src="/images/installation/yellow-docs.png" style="margin-bottom: 16px;"></p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|||||||
@ -8,7 +8,7 @@ related:
|
|||||||
title: Add network storage
|
title: Add network storage
|
||||||
- docs: /common-tasks/os/#using-external-data-disk
|
- docs: /common-tasks/os/#using-external-data-disk
|
||||||
title: Using an external data disk
|
title: Using an external data disk
|
||||||
- URL: https://yellow.home-assistant.io/guides/add-ssd-existing-installation/
|
- URL: https://support.nabucasa.com/hc/en-us/articles/25549332241949
|
||||||
title: Adding an SSD to Home Assistant Yellow
|
title: Adding an SSD to Home Assistant Yellow
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|||||||
@ -27,7 +27,7 @@ frontpage_image: /images/frontpage/voice-pe-frontpage.jpg
|
|||||||
<a href="#features">Features</a>
|
<a href="#features">Features</a>
|
||||||
<a href="#specs">Specs</a>
|
<a href="#specs">Specs</a>
|
||||||
<a href="#faq">FAQ</a>
|
<a href="#faq">FAQ</a>
|
||||||
<a href="https://voice-pe.home-assistant.io/" target="_blank" rel="noopener">Docs</a>
|
<a href="https://support.nabucasa.com/hc/en-us/categories/24451727188125-Home-Assistant-Voice-Preview-Edition" target="_blank" rel="noopener">Docs</a>
|
||||||
<a href="#" class="cta buy">Buy now</a>
|
<a href="#" class="cta buy">Buy now</a>
|
||||||
</div>
|
</div>
|
||||||
<div class="burger">
|
<div class="burger">
|
||||||
@ -40,7 +40,7 @@ frontpage_image: /images/frontpage/voice-pe-frontpage.jpg
|
|||||||
<a href="#features">Features</a>
|
<a href="#features">Features</a>
|
||||||
<a href="#specs">Specs</a>
|
<a href="#specs">Specs</a>
|
||||||
<a href="#faq">FAQ</a>
|
<a href="#faq">FAQ</a>
|
||||||
<a href="https://voice-pe.home-assistant.io/" target="_blank" rel="noopener">Docs</a>
|
<a href="https://support.nabucasa.com/hc/en-us/categories/24451727188125-Home-Assistant-Voice-Preview-Edition" target="_blank" rel="noopener">Docs</a>
|
||||||
<a href="#" class="cta buy">Buy now</a>
|
<a href="#" class="cta buy">Buy now</a>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
@ -771,7 +771,7 @@ frontpage_image: /images/frontpage/voice-pe-frontpage.jpg
|
|||||||
<p class="subtitle">Be part of building Assist and preview the future of voice control in the home.</p>
|
<p class="subtitle">Be part of building Assist and preview the future of voice control in the home.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="buttons">
|
<div class="buttons">
|
||||||
<a target="_blank" href="https://voice-pe.home-assistant.io/resources/" rel="noopener"
|
<a target="_blank" href="https://support.nabucasa.com/hc/en-us/sections/24980381645213" rel="noopener"
|
||||||
class="button clear clear-secondary">Explore resources</a>
|
class="button clear clear-secondary">Explore resources</a>
|
||||||
<a target="_blank" href="https://community.home-assistant.io/" rel="noopener"
|
<a target="_blank" href="https://community.home-assistant.io/" rel="noopener"
|
||||||
class="button clear clear-navy">Join our
|
class="button clear clear-navy">Join our
|
||||||
|
|||||||
@ -7,7 +7,7 @@ related:
|
|||||||
title: Best practices with Assist
|
title: Best practices with Assist
|
||||||
- url: https://companion.home-assistant.io/docs/getting_started/
|
- url: https://companion.home-assistant.io/docs/getting_started/
|
||||||
title: Home Assistant Companion App
|
title: Home Assistant Companion App
|
||||||
- url: https://voice-pe.home-assistant.io/
|
- url: https://support.nabucasa.com/hc/en-us/categories/24451727188125-Home-Assistant-Voice-Preview-Edition
|
||||||
title: Voice Preview Edition
|
title: Voice Preview Edition
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|||||||
@ -7,7 +7,7 @@ related:
|
|||||||
title: Best practices with Assist
|
title: Best practices with Assist
|
||||||
- url: https://companion.home-assistant.io/docs/getting_started/
|
- url: https://companion.home-assistant.io/docs/getting_started/
|
||||||
title: Home Assistant Companion App
|
title: Home Assistant Companion App
|
||||||
- url: https://voice-pe.home-assistant.io/
|
- url: https://support.nabucasa.com/hc/en-us/categories/24451727188125-Home-Assistant-Voice-Preview-Edition
|
||||||
title: Voice Preview Edition
|
title: Voice Preview Edition
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|||||||
@ -11,7 +11,7 @@ related:
|
|||||||
title: Sentences starter kit
|
title: Sentences starter kit
|
||||||
- url: https://www.nabucasa.com/config/
|
- url: https://www.nabucasa.com/config/
|
||||||
title: Home Assistant Cloud
|
title: Home Assistant Cloud
|
||||||
- url: https://voice-pe.home-assistant.io/
|
- url: https://support.nabucasa.com/hc/en-us/categories/24451727188125-Home-Assistant-Voice-Preview-Edition
|
||||||
title: Voice Preview Edition
|
title: Voice Preview Edition
|
||||||
---
|
---
|
||||||
There are a few things you should do to get the most out of the voice assistant experience.
|
There are a few things you should do to get the most out of the voice assistant experience.
|
||||||
|
|||||||
@ -7,7 +7,7 @@ related:
|
|||||||
title: Custom sentences with Assist
|
title: Custom sentences with Assist
|
||||||
- url: https://www.nabucasa.com/config/
|
- url: https://www.nabucasa.com/config/
|
||||||
title: Home Assistant Cloud
|
title: Home Assistant Cloud
|
||||||
- url: https://voice-pe.home-assistant.io/
|
- url: https://support.nabucasa.com/hc/en-us/categories/24451727188125-Home-Assistant-Voice-Preview-Edition
|
||||||
title: Voice Preview Edition
|
title: Voice Preview Edition
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|||||||
@ -11,7 +11,7 @@ related:
|
|||||||
title: Best practices with Assist
|
title: Best practices with Assist
|
||||||
- url: https://www.nabucasa.com/config/assist/
|
- url: https://www.nabucasa.com/config/assist/
|
||||||
title: Home Assistant Cloud
|
title: Home Assistant Cloud
|
||||||
- url: https://voice-pe.home-assistant.io/
|
- url: https://support.nabucasa.com/hc/en-us/categories/24451727188125-Home-Assistant-Voice-Preview-Edition
|
||||||
title: Voice Preview Edition
|
title: Voice Preview Edition
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|||||||
@ -9,7 +9,7 @@ related:
|
|||||||
title: Creating a local assistant
|
title: Creating a local assistant
|
||||||
- docs: /voice_control/voice_remote_expose_devices/
|
- docs: /voice_control/voice_remote_expose_devices/
|
||||||
title: Exposing devices to Assist
|
title: Exposing devices to Assist
|
||||||
- url: https://voice-pe.home-assistant.io/documentation/
|
- url: https://support.nabucasa.com/hc/en-us/categories/24451727188125-Home-Assistant-Voice-Preview-Edition
|
||||||
title: Voice Preview Edition - Documentation
|
title: Voice Preview Edition - Documentation
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -50,6 +50,6 @@ To have the fastest processing voice assistant experience, follow these steps:
|
|||||||
|
|
||||||
|
|
||||||
## Next steps
|
## Next steps
|
||||||
Once Assist is configured, now can now start using it. You can now talk through your device ([Android](/voice_control/android/), [iOS](/voice_control/apple/) or [Voice Preview edition](https://voice-pe.home-assistant.io/getting-started/)).
|
Once Assist is configured, now can now start using it. You can now talk through your device ([Android](/voice_control/android/), [iOS](/voice_control/apple/) or [Voice Preview edition](https://support.nabucasa.com/hc/en-us/categories/24451727188125-Home-Assistant-Voice-Preview-Edition).
|
||||||
|
|
||||||
To get the best out of the voice interaction, don't forget to check the [best practices](/voice_control/best_practices/).
|
To get the best out of the voice interaction, don't forget to check the [best practices](/voice_control/best_practices/).
|
||||||
|
|||||||
@ -9,7 +9,7 @@ related:
|
|||||||
title: Creating a local assistant
|
title: Creating a local assistant
|
||||||
- docs: /voice_control/voice_remote_expose_devices/
|
- docs: /voice_control/voice_remote_expose_devices/
|
||||||
title: Exposing devices to Assist
|
title: Exposing devices to Assist
|
||||||
- url: https://voice-pe.home-assistant.io/documentation/
|
- url: https://support.nabucasa.com/hc/en-us/categories/24451727188125-Home-Assistant-Voice-Preview-Edition
|
||||||
title: Voice Preview Edition - Documentation
|
title: Voice Preview Edition - Documentation
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -111,7 +111,7 @@ View some of the options in the video below. Explained by Mike Hansen, creator o
|
|||||||
|
|
||||||
The options are also documented in the add-on itself. Go to the {% my supervisor_addon addon="core_whisper" title="**Whisper**" %} or the {% my supervisor_addon addon="core_piper" title="**Piper**" %} add-on and open the **Documentation** page.
|
The options are also documented in the add-on itself. Go to the {% my supervisor_addon addon="core_whisper" title="**Whisper**" %} or the {% my supervisor_addon addon="core_piper" title="**Piper**" %} add-on and open the **Documentation** page.
|
||||||
|
|
||||||
Also be sure to check the specific tutorial for [using Piper in Automations](voice_control/using_tts_in_automation/)
|
Also be sure to check the specific tutorial for [using Piper in Automations](/voice_control/using_tts_in_automation/)
|
||||||
|
|
||||||
## Learning more about Speech-to-Phrase
|
## Learning more about Speech-to-Phrase
|
||||||
|
|
||||||
@ -120,6 +120,6 @@ You can check out [Voice Chapter 9](/blog/2025/02/13/voice-chapter-9-speech-to-p
|
|||||||
<lite-youtube videoid="k6VvzDSI8RU" videotitle="Voice Chapter 9"></lite-youtube>
|
<lite-youtube videoid="k6VvzDSI8RU" videotitle="Voice Chapter 9"></lite-youtube>
|
||||||
|
|
||||||
## Next steps
|
## Next steps
|
||||||
Once Assist is configured, now can now start using it. You can now talk through your device ([Android](/voice_control/android/), [iOS](/voice_control/apple/) or [Voice Preview edition](https://voice-pe.home-assistant.io/getting-started/)).
|
Once Assist is configured, now can now start using it. You can now talk through your device ([Android](/voice_control/android/), [iOS](/voice_control/apple/) or [Voice Preview edition](https://support.nabucasa.com/hc/en-us/categories/24451727188125-Home-Assistant-Voice-Preview-Edition)).
|
||||||
|
|
||||||
To get the best out of the voice interaction, don't forget to check the [best practices](/voice_control/best_practices/).
|
To get the best out of the voice interaction, don't forget to check the [best practices](/voice_control/best_practices/).
|
||||||
|
|||||||
@ -161,7 +161,7 @@ frontpage_image: /images/frontpage/yellow-frontpage.jpg
|
|||||||
</div>
|
</div>
|
||||||
|
|
||||||
<div class="material-card spaced-card">
|
<div class="material-card spaced-card">
|
||||||
<a href="https://yellow.home-assistant.io/yellow-v1.2-standard/" target="_blank"><img src="/images/yellow/home-assistant-yellow-exploded-and-labeled.png"></a>
|
<a href="https://support.nabucasa.com/hc/en-us/categories/24734575925149-Home-Assistant-Yellow" target="_blank"><img src="/images/yellow/home-assistant-yellow-exploded-and-labeled.png"></a>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
<div class="material-card text spaced-card">
|
<div class="material-card text spaced-card">
|
||||||
@ -170,7 +170,7 @@ frontpage_image: /images/frontpage/yellow-frontpage.jpg
|
|||||||
<div><img src="/images/yellow/yellow-kit-poe-2d.jpg" alt="2D overview of the content of the Home Assistant Yellow Kit Power-over-Ethernet variant"></div>
|
<div><img src="/images/yellow/yellow-kit-poe-2d.jpg" alt="2D overview of the content of the Home Assistant Yellow Kit Power-over-Ethernet variant"></div>
|
||||||
<div>
|
<div>
|
||||||
<b>Yellow Kit with Power-over-Ethernet</b><br>
|
<b>Yellow Kit with Power-over-Ethernet</b><br>
|
||||||
<a href="https://yellow.home-assistant.io/poe/">Some assembly required!</a> This kit supports Power-over-Ethernet (PoE) but is otherwise almost the same as the flagship version. Custom enclosure, custom heat sink, and Ethernet cable included. <b>Without the Raspberry Pi Compute Module 4</b>.
|
<a href="https://support.nabucasa.com/hc/en-us/sections/25293966429597">Some assembly required!</a> This kit supports Power-over-Ethernet (PoE) but is otherwise almost the same as the flagship version. Custom enclosure, custom heat sink, and Ethernet cable included. <b>Without the Raspberry Pi Compute Module 4</b>.
|
||||||
<br><br>
|
<br><br>
|
||||||
<b>Not included</b>: You must provide your own Raspberry Pi Compute Module 4 and install Home Assistant on it. This allows you to pick the compute module with the memory and eMMC storage to fit your needs. This kit also does not include a power supply (because power comes from PoE). The router or switch must supply Power-over-Ethernet. Typically, PoE capable ports are labelled as such.
|
<b>Not included</b>: You must provide your own Raspberry Pi Compute Module 4 and install Home Assistant on it. This allows you to pick the compute module with the memory and eMMC storage to fit your needs. This kit also does not include a power supply (because power comes from PoE). The router or switch must supply Power-over-Ethernet. Typically, PoE capable ports are labelled as such.
|
||||||
</div>
|
</div>
|
||||||
@ -179,7 +179,7 @@ frontpage_image: /images/frontpage/yellow-frontpage.jpg
|
|||||||
<div><img src="/images/yellow/yellow-kit-2d.jpg" alt="2D overview of the content of the Home Assistant Yellow Kit"></div>
|
<div><img src="/images/yellow/yellow-kit-2d.jpg" alt="2D overview of the content of the Home Assistant Yellow Kit"></div>
|
||||||
<div>
|
<div>
|
||||||
<b>Yellow Kit with power supply</b><br>
|
<b>Yellow Kit with power supply</b><br>
|
||||||
<a href="https://yellow.home-assistant.io/power-supply/">Some assembly required!</a> This kit is almost the same as the flagship version. Custom enclosure, custom heat sink, and Ethernet cable included.<b> Without the Raspberry Pi Compute Module 4</b>.
|
<a href="https://support.nabucasa.com/hc/en-us/sections/25293966429597">Some assembly required!</a> This kit is almost the same as the flagship version. Custom enclosure, custom heat sink, and Ethernet cable included.<b> Without the Raspberry Pi Compute Module 4</b>.
|
||||||
<br><br>
|
<br><br>
|
||||||
<b>Not included</b>: You must provide your own Raspberry Pi Compute Module 4 and install Home Assistant on it. This allows you to pick the compute module with the memory and eMMC storage to fit your needs. This kit comes with a power supply, but does not support Power-over-Ethernet.
|
<b>Not included</b>: You must provide your own Raspberry Pi Compute Module 4 and install Home Assistant on it. This allows you to pick the compute module with the memory and eMMC storage to fit your needs. This kit comes with a power supply, but does not support Power-over-Ethernet.
|
||||||
</div>
|
</div>
|
||||||
@ -199,7 +199,7 @@ frontpage_image: /images/frontpage/yellow-frontpage.jpg
|
|||||||
<h1>Open hardware</h1>
|
<h1>Open hardware</h1>
|
||||||
<p>
|
<p>
|
||||||
We spend a lot of time and resources on fine-tuning our products. We want other people to be able to study our work and be able to make their own great smart home products. For this reason, we've released the schematics of Home Assistant Yellow as open-source.
|
We spend a lot of time and resources on fine-tuning our products. We want other people to be able to study our work and be able to make their own great smart home products. For this reason, we've released the schematics of Home Assistant Yellow as open-source.
|
||||||
<a href="https://yellow.home-assistant.io/hardware/yellow-v1.3-poe/">Explore the board</a> and <a href="https://github.com/NabuCasa/yellow/">view the source.</a>
|
<a href="https://github.com/NabuCasa/yellow/">View the source.</a>
|
||||||
</p>
|
</p>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
@ -319,7 +319,7 @@ frontpage_image: /images/frontpage/yellow-frontpage.jpg
|
|||||||
{% enddetails %}
|
{% enddetails %}
|
||||||
|
|
||||||
<div class="material-card text spaced-card">
|
<div class="material-card text spaced-card">
|
||||||
<a href="https://yellow.home-assistant.io/" target="_blank"
|
<a href="https://support.nabucasa.com/hc/en-us/categories/24734575925149" target="_blank"
|
||||||
class="documentation-card">
|
class="documentation-card">
|
||||||
<div class="content-container">
|
<div class="content-container">
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user