home-assistant · jherby2k · Jul 7, 2022 · Jul 7, 2022 · Jul 7, 2022 · Jul 7, 2022
diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
@@ -10,7 +10,7 @@ jobs:
       - name: Check out files from GitHub
         uses: actions/checkout@v3.0.2
       - name: Setting up Node.js
-        uses: actions/setup-node@v3.3.0
+        uses: actions/setup-node@v3.4.1
         with:
           node-version: 16.x
           cache: "npm"
@@ -27,7 +27,7 @@ jobs:
       - name: Check out files from GitHub
         uses: actions/checkout@v3.0.2
       - name: Setting up Node.js
-        uses: actions/setup-node@v3.3.0
+        uses: actions/setup-node@v3.4.1
         with:
           node-version: 16.x
           cache: "npm"

diff --git a/Gemfile b/Gemfile
@@ -19,8 +19,8 @@ group :jekyll_plugins do
   gem 'jekyll-toc', '0.17.1'
 end
 
-gem 'sinatra', '2.2.0'
-gem 'nokogiri', '1.13.6'
+gem 'sinatra', '2.2.1'
+gem 'nokogiri', '1.13.7'
 
 # Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
 # and associated library

diff --git a/Gemfile.lock b/Gemfile.lock
@@ -28,7 +28,7 @@ GEM
     ffi (1.15.5-x64-mingw32)
     forwardable-extended (2.6.0)
     http_parser.rb (0.8.0)
-    i18n (1.10.0)
+    i18n (1.12.0)
       concurrent-ruby (~> 1.0)
     jekyll (4.2.2)
       addressable (~> 2.4)
@@ -68,19 +68,19 @@ GEM
     mercenary (0.4.0)
     mini_portile2 (2.8.0)
     multi_json (1.15.0)
-    mustermann (1.1.1)
+    mustermann (1.1.2)
       ruby2_keywords (~> 0.0.1)
-    nokogiri (1.13.6)
+    nokogiri (1.13.7)
       mini_portile2 (~> 2.8.0)
       racc (~> 1.4)
-    nokogiri (1.13.6-x64-mingw32)
+    nokogiri (1.13.7-x64-mingw32)
       racc (~> 1.4)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
     public_suffix (4.0.7)
     racc (1.6.0)
     rack (2.2.4)
-    rack-protection (2.2.0)
+    rack-protection (2.2.1)
       rack
     rake (13.0.6)
     rb-fsevent (0.11.1)
@@ -97,10 +97,10 @@ GEM
       ffi (~> 1.9)
     sassc (2.1.0-x64-mingw32)
       ffi (~> 1.9)
-    sinatra (2.2.0)
+    sinatra (2.2.1)
       mustermann (~> 1.0)
       rack (~> 2.2)
-      rack-protection (= 2.2.0)
+      rack-protection (= 2.2.1)
       tilt (~> 2.0)
     stringex (2.8.5)
     terminal-table (2.0.0)
@@ -123,11 +123,11 @@ DEPENDENCIES
   jekyll-paginate (= 1.1.0)
   jekyll-sitemap (= 1.4.0)
   jekyll-toc (= 0.17.1)
-  nokogiri (= 1.13.6)
+  nokogiri (= 1.13.7)
   rake (= 13.0.6)
   sass-globbing (= 1.1.5)
   sassc (= 2.1.0)
-  sinatra (= 2.2.0)
+  sinatra (= 2.2.1)
   stringex (= 2.8.5)
   tzinfo (~> 2.0)
   tzinfo-data

diff --git a/_config.yml b/_config.yml
@@ -107,8 +107,8 @@ social:
 # Home Assistant release details
 current_major_version: 2022
 current_minor_version: 7
-current_patch_version: 0
-date_released: 2022-07-06
+current_patch_version: 5
+date_released: 2022-07-14
 
 # 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/source/_dashboards/gauge.markdown b/source/_dashboards/gauge.markdown
@@ -61,7 +61,7 @@ max:
   default: 100
 needle:
   required: false
-  description: Show the gauge as a needle gauge.
+  description: Show the gauge as a needle gauge. Required to be set to true, if using segments.
   type: boolean
   default: false
 severity:
@@ -83,7 +83,7 @@ severity:
       type: integer
 segments:
   required: false
-  description: List of colors and their corresponding start values. Segments will override the severity settings.
+  description: List of colors and their corresponding start values. Segments will override the severity settings. Needle required to be true.
   type: list
   keys:
     from:

diff --git a/source/_docs/energy/faq.markdown b/source/_docs/energy/faq.markdown
@@ -13,7 +13,7 @@ Electrical Power is measured in Watts (W) and Electrical Energy is measured in k
 
 Think of this in a parallel to speed and distance: Power is the speed you are going and Energy is the distance driven.
 
-Therefore Energy (kiloWatt-hour) is not an average of the Power you are consuming over a given period of time (that would be kiloWatt/hour). Energy is the integral (mathematical operation) of the Power function.
+Therefore Energy (kiloWatt-hour) is not an average of the Power you are consuming over a given period of time (the unit of the average power would be Watt or kiloWatt again). Energy is the integral (mathematical operation) of the Power function.
 
 This difference is very important as you need to use the proper entities in our Energy Panel.
 

diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown
@@ -363,7 +363,7 @@ mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/binary_sensor/garden/config
 
 For more details please refer to the [MQTT testing section](/docs/mqtt/testing/).
 
-### Sensors with multiple values
+### Sensors
 
 Setting up a sensor with multiple measurement values requires multiple consecutive configuration topic submissions.
 
@@ -373,9 +373,9 @@ Setting up a sensor with multiple measurement values requires multiple consecuti
 - Configuration payload no2: `{"device_class": "humidity", "name": "Humidity", "state_topic": "homeassistant/sensor/sensorBedroom/state", "unit_of_measurement": "%", "value_template": "{% raw %}{{ value_json.humidity}}{% endraw %}" }`
 - Common state payload: `{ "temperature": 23.20, "humidity": 43.70 }`
 
-### Switches
+### Entities with command topics
 
-Setting up a switch is similar but requires a `command_topic` as mentioned in the [MQTT switch documentation](/integrations/switch.mqtt/).
+Setting up a light, switch etc. is similar but requires a `command_topic` as mentioned in the [MQTT switch documentation](/integrations/switch.mqtt/).
 
 - Configuration topic: `homeassistant/switch/irrigation/config`
 - State topic: `homeassistant/switch/irrigation/state`
@@ -394,7 +394,7 @@ Set the state.
 mosquitto_pub -h 127.0.0.1 -p 1883 -t "homeassistant/switch/irrigation/set" -m ON
 ```
 
-### Abbreviating topic names
+### Using abbreviations and base topic
 
 Setting up a switch using topic prefix and abbreviated configuration variable names to reduce payload length.
 
@@ -403,7 +403,7 @@ Setting up a switch using topic prefix and abbreviated configuration variable na
 - State topic: `homeassistant/switch/irrigation/state`
 - Configuration payload: `{"~": "homeassistant/switch/irrigation", "name": "garden", "cmd_t": "~/set", "stat_t": "~/state"}`
 
-### Lighting
+### Another example using abbreviations topic name and base topic
 
 Setting up a [light that takes JSON payloads](/integrations/light.mqtt/#json-schema), with abbreviated configuration variable names:
 
@@ -425,78 +425,6 @@ Setting up a [light that takes JSON payloads](/integrations/light.mqtt/#json-sch
   }
   ```
 
-### Climate control
-
-Setting up a climate integration (heat only):
-
-- Configuration topic: `homeassistant/climate/livingroom/config`
-- Configuration payload:
-
-```json
-{
-  "name":"Livingroom",
-  "mode_cmd_t":"homeassistant/climate/livingroom/thermostatModeCmd",
-  "mode_stat_t":"homeassistant/climate/livingroom/state",
-  "mode_stat_tpl":"{{value_json.mode}}",
-  "avty_t":"homeassistant/climate/livingroom/available",
-  "pl_avail":"online",
-  "pl_not_avail":"offline",
-  "temp_cmd_t":"homeassistant/climate/livingroom/targetTempCmd",
-  "temp_stat_t":"homeassistant/climate/livingroom/state",
-  "temp_stat_tpl":"{{value_json.target_temp}}",
-  "curr_temp_t":"homeassistant/climate/livingroom/state",
-  "curr_temp_tpl":"{{value_json.current_temp}}",
-  "min_temp":"15",
-  "max_temp":"25",
-  "temp_step":"0.5",
-  "modes":["off", "heat"]
-}
-```
-
-- State topic: `homeassistant/climate/livingroom/state`
-- State payload:
-
-```json
-{
-  "mode":"off",
-  "target_temp":"21.50",
-  "current_temp":"23.60"
-}
-```
-
-### Presence detection (device tracker)
-
-Setting up a device tracker:
-
-- Configuration topic: `homeassistant/device_tracker/paulus/config`
-- Example configuration payload:
-
-```json
-{
-  "name":"Paulus",
-  "state_topic": "homeassistant/device_tracker/paulus/state",
-  "payload_home": "home",
-  "payload_not_home": "not_home",
-  "source_type": "bluetooth"
- }
-```
-
-- State topic: `homeassistant/device_tracker/paulus/state`
-- Example state payload: `home` or `not_home` or `location name`
-
-If the device supports GPS coordinates then they can be sent to Home Assistant by specifying an attributes topic (i.e. "json_attributes_topic") in the configuration payload:
-
-- Attributes topic: `homeassistant/device_tracker/paulus/attributes`
-- Example attributes payload:
-
-```json
-{
-  "latitude": 32.87336,
-  "longitude": -117.22743,
-  "gps_accuracy": 1.2
- }
-```
-
 ### Use object_id to influence the entity id
 
 

diff --git a/source/_includes/installation/container.md b/source/_includes/installation/container.md
@@ -8,7 +8,7 @@ These below instructions are for an installation of Home Assistant Container run
 
 This guide assumes that you already have an operating system setup and a container runtime installed (like Docker).
 
-If you are using Docker then you need to be on at least version 19.03.9, ideally an even higher version, and `libseccomp` 2.42 or newer.
+If you are using Docker then you need to be on at least version 19.03.9, ideally an even higher version, and `libseccomp` 2.4.2 or newer.
 </div>
 
 ### Platform Installation

diff --git a/source/_includes/installation/operating_system.md b/source/_includes/installation/operating_system.md
@@ -165,7 +165,7 @@ This can be accomplished either by using a live operating system (e.g. Ubuntu) a
 
   ```text
   efibootmgr --create --disk /dev/<drivename> --part 1 --label "HAOS" \
-     --loader \EFI\BOOT\bootx64.efi
+     --loader "\EFI\BOOT\bootx64.efi"
   ```
 
 Or else, the BIOS might provide you with a tool to add boot options, there you can specify the path to the EFI file:

diff --git a/source/_integrations/amcrest.markdown b/source/_integrations/amcrest.markdown
@@ -48,7 +48,7 @@ host:
   required: true
   type: string
 username:
-  description: The username for accessing your camera.
+  description: The username for accessing your camera. Most Amcrest devices use "admin" for the username, even if you've configured another username in their app.
   required: true
   type: string
 password:

@@ -47,7 +47,7 @@ counter:
       required: false
       type: string
     initial:
-      description: Initial value when Home Assistant starts or the counter is reset.
+      description: Initial value (0 or positive integer) when Home Assistant starts or the counter is reset.
       required: false
       type: integer
       default: 0

diff --git a/source/_integrations/denon.markdown b/source/_integrations/denon.markdown
@@ -11,7 +11,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The `denon` platform allows you to control a [Denon Network Receiver](https://www.denon.com/category/homecinema/avreceiver) from Home Assistant. It might be that your device is supported by the [Denon AVR] platform.
+The `denon` platform allows you to control a Denon Network Receiver from Home Assistant. It might be that your device is supported by the [Denon AVR] platform.
 
 Supported devices:
 

@@ -16,7 +16,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The `denonavr` platform allows you to control [Denon Network Receivers](https://www.denon.com/en-gb/shop/networkmusicsystem/ceolpiccolon4) from Home Assistant. It might be that your device is supported by the [Denon] platform.
+The `denonavr` platform allows you to control [Denon Network Receivers](https://www.denon.com/category/heos) from Home Assistant. It might be that your device is supported by the [Denon] platform.
 
 Known supported devices:
 
@@ -51,6 +51,7 @@ Known supported devices:
 - Denon AVR-X6500H
 - Denon AVR-X6700H
 - Denon AVR-1912
+- Denon AVR-2112CI
 - Denon AVR-2312CI
 - Denon AVR-3311CI
 - Denon AVR-3312
@@ -61,6 +62,7 @@ Known supported devices:
 - Denon AVR-S720W
 - Denon AVR-S750H
 - Denon AVR-S760H
+- Denon AVR-S950H
 - Denon AVR-S960H
 - Denon DN-500AV
 - Marantz AV7702
@@ -118,7 +120,7 @@ A few notes:
 - The `denonavr` platform supports some additional functionalities like album covers, custom input source names and auto discovery.
 - Marantz receivers seem to a have quite a similar interface. Thus if you own one, give it a try.
 - To remotely power on Marantz receivers with Home Assistant, the Auto-Standby feature must be enabled in the receiver's settings.
-- Sound mode: The command to set a specific sound mode is different from the value of the current sound mode reported by the receiver (sound_mode_raw). There is a key-value structure (sound_mode_dict) that matches the raw sound mode to one of the possible commands to set a sound mode (for instance {'MUSIC':['PLII MUSIC']}. If you get a "Not able to match sound mode" warning, please open an issue on the [denonavr library](https://github.com/scarface-4711/denonavr), stating which raw sound mode could not be matched so it can be added to the matching dictionary. You can find the current raw sound mode under **Developer Tools** -> **States**.
+- Sound mode: The command to set a specific sound mode is different from the value of the current sound mode reported by the receiver (sound_mode_raw). There is a key-value structure (sound_mode_dict) that matches the raw sound mode to one of the possible commands to set a sound mode (for instance {'MUSIC':['PLII MUSIC']}. If you get a "Not able to match sound mode" warning, please open an issue on the [denonavr library](https://github.com/ol-iver/denonavr), stating which raw sound mode could not be matched so it can be added to the matching dictionary. You can find the current raw sound mode under **Developer Tools** -> **States**.
 
 #### Service `denonavr.get_command`
 

diff --git a/source/_integrations/device_tracker.mqtt.markdown b/source/_integrations/device_tracker.mqtt.markdown
@@ -234,7 +234,7 @@ You can use the command line tool `mosquitto_pub` shipped with `mosquitto` or th
 To create the device_tracker:
 
 ```bash
-mosquitto_pub -h 127.0.0.1 -t home-assistant/device_tracker/a4567d663eaf/config -m '{"state_topic": "a4567d663eaf/state", "name": "My Tracker", "payload_home": "home", "payload_not_home": "not_home"}'
+mosquitto_pub -h 127.0.0.1 -t homeassistant/device_tracker/a4567d663eaf/config -m '{"state_topic": "a4567d663eaf/state", "name": "My Tracker", "payload_home": "home", "payload_not_home": "not_home"}'
 ```
 
 To set the state of the device tracker to "home":
@@ -243,6 +243,38 @@ To set the state of the device tracker to "home":
 mosquitto_pub -h 127.0.0.1 -t a4567d663eaf/state -m 'home'
 ```
 
+To set the state of the device tracker to a named location:
+
+```bash
+mosquitto_pub -h 127.0.0.1 -t a4567d663eaf/state -m 'location_name'
+```
+
+If the device supports GPS coordinates then they can be sent to Home Assistant by specifying an attributes topic (i.e. "json_attributes_topic") in the configuration payload:
+
+- Attributes topic: `a4567d663eaf/attributes`
+- Example attributes payload:
+
+```json
+{
+  "latitude": 32.87336,
+  "longitude": -117.22743,
+  "gps_accuracy": 1.2
+ }
+```
+
+To create the device_tracker with GPS coordinates support:
+
+```bash
+mosquitto_pub -h 127.0.0.1 -t homeassistant/device_tracker/a4567d663eaf/config -m '{"state_topic": "a4567d663eaf/state", "name": "My Tracker", "payload_home": "home", "payload_not_home": "not_home", "json_attributes_topic": "a4567d663eaf/attributes"}'
+```
+
+To set the state of the device tracker to specific coordinates:
+
+```bash
+mosquitto_pub -h 127.0.0.1 -t a4567d663eaf/state -m '{"latitude": 32.87336, "longitude": -117.22743, "gps_accuracy": 1.2}'
+```
+
+
 ### YAML configuration
 
 The following example shows how to configure the same device tracker through configuration.yaml

diff --git a/source/_integrations/ecobee.markdown b/source/_integrations/ecobee.markdown
@@ -34,7 +34,7 @@ The `ecobee` integration lets you control and view sensor data from [ecobee](htt
 You will need to obtain an API key from ecobee's [developer site](https://www.ecobee.com/developers/) to use this integration. To get the key, your thermostat must be registered on ecobee's website (which you likely would have already done while installing your thermostat). Once you have done that, perform the following steps.
 
 1. Click on the **Become a developer** link on the [developer site](https://www.ecobee.com/home/developer/loginDeveloper.jsp).
-2. Log in with your ecobee credentials. (Make sure your password is at most 16 characters and multifactor authentication is disabled to meet the developer login form's limits. If you've already enabled MFA, the web portal and iOS apps don't support disabling it. The Android app does under Account > Account Security. You can re-enable MFA after becoming a developer.)
+2. Log in with your ecobee credentials. (Make sure multifactor authentication is disabled to meet the developer login form's limits. If you've already enabled MFA, the web portal doesn't support disabling it. The iOS and Android apps do under Account > Account Security. You can re-enable MFA after becoming a developer.)
 3. Accept the SDK agreement.
 4. Fill in the fields.
 5. Click **save**.