home-assistant · SeraphicRav · Aug 8, 2024 · Aug 8, 2024 · Aug 8, 2024 · Aug 8, 2024
diff --git a/Gemfile b/Gemfile
@@ -11,7 +11,7 @@ group :development do
   # > 2.1.0 causes slowdowns https://github.com/sass/sassc-ruby/issues/189
   gem 'sassc', '2.1.0'
   gem 'rubocop', '1.65.1'
-  gem 'ruby-lsp', '0.17.11'
+  gem 'ruby-lsp', '0.17.13'
   gem 'rackup', '2.1.0'
 end
 

diff --git a/Gemfile.lock b/Gemfile.lock
@@ -21,7 +21,7 @@ GEM
       sass (>= 3.3.0, < 3.5)
     compass-import-once (1.0.5)
       sass (>= 3.2, < 3.5)
-    concurrent-ruby (1.3.3)
+    concurrent-ruby (1.3.4)
     em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0)
@@ -75,12 +75,12 @@ GEM
     logger (1.6.0)
     mercenary (0.4.0)
     multi_json (1.15.0)
-    mustermann (3.0.1)
+    mustermann (3.0.2)
       ruby2_keywords (~> 0.0.1)
     nokogiri (1.16.7-x86_64-linux)
       racc (~> 1.4)
-    parallel (1.25.1)
-    parser (3.3.4.1)
+    parallel (1.26.2)
+    parser (3.3.4.2)
       ast (~> 2.4.1)
       racc
     pathutil (0.16.2)
@@ -105,7 +105,7 @@ GEM
     rbs (3.5.2)
       logger
     regexp_parser (2.9.2)
-    rexml (3.3.4)
+    rexml (3.3.5)
       strscan
     rouge (4.3.0)
     rubocop (1.65.1)
@@ -121,7 +121,7 @@ GEM
       unicode-display_width (>= 2.4.0, < 3.0)
     rubocop-ast (1.32.0)
       parser (>= 3.3.1.0)
-    ruby-lsp (0.17.11)
+    ruby-lsp (0.17.13)
       language_server-protocol (~> 3.17.0)
       prism (>= 0.29.0, < 0.31)
       rbs (>= 3, < 4)
@@ -142,7 +142,7 @@ GEM
       rack-protection (= 4.0.0)
       rack-session (>= 2.0.0, < 3)
       tilt (~> 2.0)
-    sorbet-runtime (0.5.11514)
+    sorbet-runtime (0.5.11525)
     stringex (2.8.6)
     strscan (3.1.0)
     terminal-table (3.0.2)
@@ -169,7 +169,7 @@ DEPENDENCIES
   rackup (= 2.1.0)
   rake (= 13.2.1)
   rubocop (= 1.65.1)
-  ruby-lsp (= 0.17.11)
+  ruby-lsp (= 0.17.13)
   sass-globbing (= 1.1.5)
   sassc (= 2.1.0)
   sinatra (= 4.0.0)

diff --git a/_config.yml b/_config.yml
@@ -108,8 +108,8 @@ social:
 # Home Assistant release details
 current_major_version: 2024
 current_minor_version: 8
-current_patch_version: 0
-date_released: 2024-08-07
+current_patch_version: 1
+date_released: 2024-08-10
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

diff --git a/plugins/details.rb b/plugins/details.rb
@@ -40,29 +40,17 @@ def render(context)
       end
 
       <<~MARKUP
-        <script>
-        function showDetails(el) {
-          const content = el.parentElement.querySelector(".details-block-content");
-          const up = el.querySelector("svg#up");
-          const down = el.querySelector("svg#down");
-          const shouldExpand = down.style.display === "block";
-          up.style.display = shouldExpand ? "block" : "none";
-          down.style.display = !shouldExpand ? "block" : "none";
-          content.hidden = !shouldExpand;
-          el.ariaExpanded = shouldExpand;
-        }
-        </script>
         <div class="details-block">
-          <div class='details-block-item'>
-            <button class='details-block-title' onclick='showDetails(this)' aria-controls="content_#{idx}" aria-expanded="false">
+          <details class='details-block-item'>
+            <summary class='details-block-title'
7802
>
               <span>#{icon}#{title}</span>
               <div class='details-block-arrow'>
-              <svg id="down" style="display: block;" width="24" height="24" viewBox="0 0 24 24"><path d="M7.41,8.58L12,13.17L16.59,8.58L18,10L12,16L6,10L7.41,8.58Z" /></svg>
-              <svg id="up" style="display: none;" width="24" height="24" viewBox="0 0 24 24"><path d="M7.41,15.41L12,10.83L16.59,15.41L18,14L12,8L6,14L7.41,15.41Z" /></svg>
+              <svg class="down" width="24" height="24" viewBox="0 0 24 24"><path d="M7.41,8.58L12,13.17L16.59,8.58L18,10L12,16L6,10L7.41,8.58Z" /></svg>
+              <svg class="up" width="24" height="24" viewBox="0 0 24 24"><path d="M7.41,15.41L12,10.83L16.59,15.41L18,14L12,8L6,14L7.41,15.41Z" /></svg>
               </div>
-            </button>
-            <div class='details-block-content' id="content_#{idx}" hidden>#{contents}</div>
-          </div>
+            </summary>
+            <div class='details-block-content' id="content_#{idx}">#{contents}</div>
+          </details>
         </div>
       MARKUP
     end

diff --git a/sass/homeassistant/plugins/_details.scss b/sass/homeassistant/plugins/_details.scss
@@ -10,6 +10,16 @@ div.details-block {
     border: 1px solid rgba(0, 0, 0, .12);
     border-radius: 16px;
 
+    &
93C6
amp;[open] .details-block-title {
+      .up {
+        display: block;
+      }
+
+      .down {
+        display: none;
+      }
+    }
+
     .details-block-title {
       font-weight: bold;
       font-size: 18px;
@@ -23,6 +33,14 @@ div.details-block {
       border: 0px;
       width: 100%;
       padding: 0;
+
+      .up {
+        display: none;
+      }
+
+      .down {
+        display: block;
+      }
     }
     .details-block-content {
       margin: 4px 0 12px 0;

diff --git a/source/_data/glossary.yml b/source/_data/glossary.yml
@@ -155,6 +155,9 @@
     Covers are devices such as blinds, garage doors, etc that can be opened and
     closed and optionally set to a specific position.
   link: /integrations/cover
+- term: Custom integration
+  definition: >-
+    A custom integration is an integration that has been created by someone from the Home Assistant community and has been published for others to use at their own risk. Custom integrations are not supported by the Home Assistant project. They are not reviewed or tested by the Home Assistant development team and thus may negatively impact the stability of your Home Assistant instance. An example of a custom integration is the [Spook](https://spook.boo/) integration.
 - term: Customize
   definition: >-
     Customization allows you to overwrite the default parameters of your devices
@@ -350,7 +353,7 @@
   excerpt: >
     Integrations connect and integrate Home Assistant with your devices,
     services, and more.
-  link: /integrations/
+  link: /getting-started/concepts-terminology/#integrations
   aliases:
     - integrations
 - term: Intent
@@ -489,7 +492,7 @@
     entities for organic, paper, and packaging waste. In terms of functionality,
     the information service is like a device. It is called *service* to avoid
     confusion, as it does not come with a piece of hardware.
-  link: /docs/scripts/service-calls/
+  link: /docs/scripts/perform-actions/
   aliases:
     - services
 - term: State

diff --git a/source/_docs/blueprint/tutorial.markdown b/source/_docs/blueprint/tutorial.markdown
@@ -63,7 +63,7 @@ action:
 
 The options that can be used with the `trigger` object are listed under [automation trigger variables](/docs/automation/templating/#available-trigger-data).
 In this example, a [state trigger](/docs/automation/templating/#state) is used.
-`turn_on` and `turn_off` are [`homeassistant` actions](/docs/scripts/service-calls/#homeassistant-actions). They are not tied to a specific domain. You can use them on lights, switches, and other domains.
+`turn_on` and `turn_off` are [`homeassistant` actions](/docs/scripts/perform-actions/#homeassistant-actions). They are not tied to a specific domain. You can use them on lights, switches, and other domains.
 
 ### Creating the blueprint file
 

diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown
@@ -1006,7 +1006,7 @@ will not be used by anything.
 [Script integration]: /integrations/script/
 [automations]: /docs/automation/action/
 [Alexa/Amazon Echo]: /integrations/alexa/
-[actions page]: /docs/scripts/service-calls/
+[actions page]: /docs/scripts/perform-actions/
 [conditions page]: /docs/scripts/conditions/
 [shorthand-template]: /docs/scripts/conditions/#template-condition-shorthand-notation
 [script variables]: /integrations/script/#configuration-variables
@@ -41,7 +41,7 @@
       {% icon "mdi:script-text" %} {% active_link /docs/scripts/ Scripts %}
       {% if doc == 'scripts' or include.docs_index %}
       <ul>
-        <li>{% active_link /docs/scripts/service-calls/ Actions %}</li>
+        <li>{% active_link /docs/scripts/perform-actions/ Actions %}</li>
         <li>{% active_link /docs/scripts/conditions/ Conditions %}</li>
       </ul>
       {% endif %}

@@ -12,14 +12,10 @@ As an alternative, Home Assistant OS can be installed in a Linux guest VM. Runni
 This is an advanced installation process, and some steps might differ on your system. Considering the nature of this installation type, we assume you can handle subtle differences between this document and the system configuration you are using. When in doubt, please consider one of the [other installation methods](/installation/), as they might be a better fit instead.
 {% endcaution %}
 
-{% important %}
-
-<b>Prerequisites</b>
+### Prerequisites
 
 This guide assumes that you already have an operating system setup and have installed Python {{site.installation.versions.python}} (including the package `python3-dev`) or newer.
 
-{% endimportant %}
-
 ### Install dependencies
 
 Before you start, make sure your system is fully updated, all packages in this guide are installed with `apt`, if your OS does not have that, look for alternatives.
@@ -86,6 +82,8 @@ Once you have installed the required Python package, it is now time to install H
 pip3 install homeassistant=={{ site.current_major_version }}.{{ site.current_minor_version }}.{{ site.current_patch_version }}
 ```
 
+**Troubleshooting**: If you do not see the above version of Home Assistant package in your environment, make sure you have the correct Python version installed, as defined under the [Prerequisites](#prerequisites).
+
 Start Home Assistant Core for the first time. This will complete the installation for you, automatically creating the `.homeassistant` configuration directory in the `/home/homeassistant` directory, and installing any basic dependencies.
 
 ```bash