home-assistant · Aeroid · Dec 30, 2021 · Dec 30, 2021 · Dec 31, 2021 · Dec 31, 2021
diff --git a/Gemfile b/Gemfile
@@ -21,7 +21,7 @@ group :jekyll_plugins do
 end
 
 gem 'sinatra', '2.1.0'
-gem 'nokogiri', '1.12.5'
+gem 'nokogiri', '1.13.0'
 
 # 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
@@ -70,14 +70,14 @@ GEM
       rb-fsevent (~> 0.10, >= 0.10.3)
       rb-inotify (~> 0.9, >= 0.9.10)
     mercenary (0.4.0)
-    mini_portile2 (2.6.1)
+    mini_portile2 (2.7.1)
     multi_json (1.15.0)
     mustermann (1.1.1)
       ruby2_keywords (~> 0.0.1)
-    nokogiri (1.12.5)
-      mini_portile2 (~> 2.6.1)
+    nokogiri (1.13.0)
+      mini_portile2 (~> 2.7.0)
       racc (~> 1.4)
-    nokogiri (1.12.5-x64-mingw32)
+    nokogiri (1.13.0-x64-mingw32)
       racc (~> 1.4)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
@@ -130,7 +130,7 @@ DEPENDENCIES
   jekyll-sitemap (= 1.4.0)
   jekyll-time-to-read (= 0.1.2)
   jekyll-toc (= 0.17.1)
-  nokogiri (= 1.12.5)
+  nokogiri (= 1.13.0)
   rake (= 13.0.6)
   sass-globbing (= 1.1.5)
   sassc (= 2.1.0)

diff --git a/_config.yml b/_config.yml
@@ -108,8 +108,8 @@ social:
 # Home Assistant release details
 current_major_version: 2021
 current_minor_version: 12
-current_patch_version: 7
-date_released: 2021-12-29
+current_patch_version: 8
+date_released: 2022-01-04
 
 # 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/_docs/configuration/devices.markdown b/source/_docs/configuration/devices.markdown
@@ -59,25 +59,3 @@ switch 1:
 switch 2:
   platform: vera
 ```
-
-## Grouping entities
-
-Once you have several entities set up, it is time to organize them into groups.
-Each group consists of a name and a list of entity IDs. Entity IDs can be
-retrieved from the web interface by using the
-{% my developer_states title="States page in the Developer Tools" %}.
-
-```yaml
-# Example configuration.yaml entry
-group:
-  living_room:
-    entities:
-      - light.table_lamp
-      - switch.ac
-  bedroom:
-    entities:
-      - light.bedroom
-      - media_player.nexus_player
-```
-
-For more details please check the [Group](/integrations/group/) page.
diff --git a/source/_docs/configuration/splitting_configuration.markdown b/source/_docs/configuration/splitting_configuration.markdown
@@ -183,6 +183,9 @@ This (large) sensor configuration gives us another example:
 
 You'll notice that this example includes a secondary parameter section (under the steam section) as well as a better example of the way comments can be used to break down files into sections.
 
+All of the above can be applied when splitting up files using packages. To
+learn more about packages, see the [Packages](/docs/configuration/packages) page.
+
 That about wraps it up.
 
 If you have issues checkout `home-assistant.log` in the configuration directory as well as your indentations. If all else fails, head over to our [Discord chat server][discord] and ask away.

diff --git a/source/_docs/locked_out.md b/source/_docs/locked_out.md
@@ -23,13 +23,13 @@ Connect a keyboard and monitor to your device.
 
 #### To reset a user's password, via the container command line
 
-If you are running Home Assistant in a container, you can use the command line in the container with the `hass` command to change your password. The steps below refer to a Home Assistant container in Docker named `ha`. Note that while working in the container, commands will take a few moments to execute.
+If you are running Home Assistant in a container, you can use the command line in the container with the `hass` command to change your password. The steps below refer to a Home Assistant container in Docker named `homeassistant`. Note that while working in the container, commands will take a few moments to execute.
 
-1. `docker exec -it ha bash` to open to the container command line
+1. `docker exec -it homeassistant bash` to open to the container command line
 2. `hass` to create a default user, if this is your first time using the tool
 3. `hass --script auth --config /config change_password existing_user new_password` to change the password
 4. `exit` to exit the container command line
-5. `docker restart ha` to restart the container
+5. `docker restart homeassistant` to restart the container
 
 #### To reset a user's password, as an administrator via the web interface
 

diff --git a/source/_docs/tools/dev-tools.markdown b/source/_docs/tools/dev-tools.markdown
@@ -61,7 +61,7 @@ The Template Editor provides a way to quickly test templates prior to placing th
 
 By default, this will contain sample code that illustrates how templates can be written and tested. This sample code can be removed and replaced with your own. You can restore the default example by pressing the "Reset to Demo Template" button beneath the code editor.
 
-For more information about Jinja2, visit [Jinja2 documentation](http://jinja.pocoo.org/docs/dev/templates/), and also read templating document [here](/topics/templating/).
+For more information about Jinja2, visit [Jinja2 documentation](https://jinja.palletsprojects.com/en/latest/templates/), and also read templating document [here](/docs/configuration/templating).
 
 ## Events
 

diff --git a/source/_includes/installation/container.md b/source/_includes/installation/container.md
@@ -74,6 +74,10 @@ Start it by running:
 docker-compose up -d
 ```
 
+Once the Home Assistant Container is running Home Assistant should be accessible using `http://<host>:8123` (replace <host> with the hostname or IP of the system). You can continue with onboarding.
+
+{% include getting-started/next_step.html step="Onboarding" link="/getting-started/onboarding/" %}
+
 ### Exposing Devices
 
 In order to use Z-Wave, Zigbee or other integrations that require access to devices, you need to map the appropriate device into the container. Ensure the user that is running the container has the correct privileges to access the `/dev/tty*` file, then add the device mapping to your container instructions:

diff --git a/source/_integrations/alarmdecoder.markdown b/source/_integrations/alarmdecoder.markdown
@@ -132,10 +132,14 @@ Using a combination of the available services and attributes, you can create swi
       value_template: "{{ is_state_attr('alarm_control_panel.alarm_panel', 'chime', true) }}"
       turn_on:
         service: alarmdecoder.alarm_toggle_chime
+        target:
+          entity_id: alarm_control_panel.alarm_panel
         data:
           code: !secret alarm_code
       turn_off:
         service: alarmdecoder.alarm_toggle_chime
+        target:
+          entity_id: alarm_control_panel.alarm_panel
         data:
           code: !secret alarm_code
       icon_template: >-

@@ -35,8 +35,9 @@ The `august` integration allows you to integrate your [August](https://august.co
 | August Smart Lock (Gen 1) | no |
 | August Doorbell Cam (Gen 1, Gen2) | no |
 | August View | no |
-| Yale Assure Locks with August/Yale Connect Module | yes |
-| Yale Conexis L1 with August/Yale Connect Module | yes |
+| Yale Assure Lock | yes |
+| Yale Conexis L1 | yes |
+| Yale Linus | yes |
 
 There is currently support for the following device types within Home Assistant:
 

diff --git a/source/_integrations/blockchain.markdown b/source/_integrations/blockchain.markdown
@@ -14,6 +14,9 @@ The `Blockchain` sensor platform displays Bitcoin wallet balances from [blockcha
 
 To add the Blockchain sensor to your installation, specify a list of bitcoin addresses to watch in the `configuration.yaml` file. The sensor state will be the sum of the balances of all addresses listed.
 
+Currently, the original Bitcoin address format is supported.
+For example, the newer Segwit and Taproot format are not supported.
+
 ```yaml
 # Example configuration.yaml entry
 sensor:

@@ -79,7 +79,7 @@ Pick an icon that you can find on [materialdesignicons.com](https://materialdesi
 
 This integration will automatically restore the state it had prior to Home Assistant stopping as long as your entity has `restore` set to `true`, which is the default. To disable this feature, set `restore` to `false`.
 
-If `restore` is set to `false`, the `initial` value will only be used when no previous state is found or when the counter is reset.
+If `restore` is set to `true`, the `initial` value will only be used when no previous state is found or when the counter is reset.
 
 ## Services
 

@@ -28,6 +28,10 @@ The way these sensors are displayed in the frontend can be modified in the [cust
 - **shutter**: Control of shutters, which are linked slats that swing out/in to covering an opening or may be tilted to partially cover an opening, such as indoor or exterior window shutters.
 - **window**: Control of a physical window that opens and closes or may tilt.
 
+Here are a few examples of this representation in the UI:
+
+<p class='img'><img src='/images/screenshots/cover_classes_icons.png' />Example of various device classes icons in `open` and `closed` state. The open image in this example has `state_color: true` specified in the Entities card configuration to receive the icon coloring.</p>
+
 ## Services
 
 ### Cover control services

diff --git a/source/_integrations/daikin.markdown b/source/_integrations/daikin.markdown
@@ -5,6 +5,7 @@ ha_category:
   - Climate
   - Sensor
   - Switch
+  - Energy
 ha_release: 0.59
 ha_iot_class: Local Polling
 ha_config_flow: true

diff --git a/source/_integrations/dsmr.markdown b/source/_integrations/dsmr.markdown
@@ -17,7 +17,7 @@ ha_platforms:
 
 A sensor platform for Belgian, Dutch, Luxembourg and Swedish Smart Meters which comply to DSMR (Dutch Smart Meter Requirements), also known as 'Slimme meter' or 'P1 poort'. Swedish meters with a 'HAN port' are not supported by this integration.
 
-- Currently support DSMR V2.2, V3, V4, V5, Belgian V5 variant, Luxembourg V5 variant (Smarty) and the Swedish V5 variant through the [dsmr_parser](https://github.com/ndokter/dsmr_parser) module by Nigel Dokter.
+- Currently support DSMR V2.2, V3, V4, V5, Belgian V5 variant, Luxembourg V5 variant (Smarty), Swedish V5 variant and the EasyMeter Q3D (Germany) through the [dsmr_parser](https://github.com/ndokter/dsmr_parser) module by Nigel Dokter.
 - For official information about DSMR refer to: [DSMR Document](https://www.netbeheernederland.nl/dossiers/slimme-meter-15)
 - For official information about the P1 port refer to: [P1 Companion Standard](https://www.netbeheernederland.nl/_upload/Files/Slimme_meter_15_a727fce1f1.pdf)
 - For unofficial hardware connection examples refer to: [Domoticx](http://domoticx.com/p1-poort-slimme-meter-hardware/)
@@ -33,6 +33,7 @@ A sensor platform for Belgian, Dutch, Luxembourg and Swedish Smart Meters which
 - For Dutch meters, choose DSMR version `2.2`, `4`, or `5`
 - For Luxembourg meters, choose DSMR version `5L`
 - For Swedish meters, choose DSMR version `5S`
+- For EasyMeter Q3D, choose DSMR version `Q3D`
 
 ### Options
 
@@ -59,6 +60,7 @@ This integration is known to work for:
 - Sagemcom XS210 ESMR5
 - Sagemcom T211 
 - Ziv E0058 ESMR5
+- EasyMeter Q3D
 
 ### Connecting to the meter
 
@@ -80,6 +82,7 @@ $ docker run --device /dev/ttyUSB0:/dev/ttyUSB0 -d --name="home-assistant" -v /h
 #### Serial to network proxies:
 
 - [ser2net](http://ser2net.sourceforge.net)
+- [WIZnet WIZ110SR](https://www.wiznet.io/product-item/wiz110sr/)
 
 DIY solutions (ESP8266 based):
 

diff --git a/source/_integrations/edl21.markdown b/source/_integrations/edl21.markdown
@@ -20,12 +20,14 @@ Compatible transceivers:
 
 - [DIY](https://wiki.volkszaehler.org/hardware/controllers/ir-schreib-lesekopf-rs232-ausgang)
 - [Weidmann Elektronik Schreib-/Lesekopf USB](https://shop.weidmann-elektronik.de/index.php?page=product&info=24)
+- [USB IR Lesekopf EHZ Lese-Schreib-Kopf Volkszähler Hichi Smartmeter](https://www.ebay.de/itm/313455434998)
 
 Tested smart meters:
 
 - APATOR Norax 3D (enable InF Mode as described in manual to retrieve full data)
 - DZG DWS76 (enable InF as described in manual to retrieve full data)
 - Iskraemeco MT175 (ISKRA MT175-D2A51-V22-K0t)
+- EMH metering eHZ Generation K (enable InF as described in manual to retrieve full data)
 
 ## Configuration
 

diff --git a/source/_integrations/eight_sleep.markdown b/source/_integrations/eight_sleep.markdown
@@ -56,12 +56,47 @@ partner:
 
 ### Supported features
 
-Sensors:
+Sensors and associated attributes:
 
 - eight_left/right_bed_state
+  - Attributes:
+    - Target Heating Level
+    - Heating Active
+    - Heating Time Remaining
 - eight left/right_sleep_fitness
+  - Attributes:
+    - Fitness Date
+    - Fitness Duration Score
+    - Fitness Asleep Score
+    - Fitness Out-of-Bed Score
+    - Fitness Wakeup Score
 - eight_left/right_sleep_session
+  - Attributes:
+    - Session Start
+    - Tosses & Turns
+    - Processing (True/False)
+    - Time Slept (s)
+    - Light Sleep %
+    - Deep Sleep %
+    - REM Sleep %
+    - Respiratory Rate
+    - Heart Rate
+    - Sleep Stage
+    - Room Temperature
+    - Bed Temperature
 - eight_left/right_previous_sleep_session
+  - Attributes:
+    - Session Start
+    - Tosses & Turns
+    - Processing (True/False)
+    - Time Slept (s)
+    - Light Sleep %
+    - Deep Sleep %
+    - REM Sleep %
+    - Average Respiratory Rate
+    - Average Heart Rate
+    - Average Room Temperature
+    - Average Bed Temperature
 - eight_left/right_bed_temperature
 - eight_left/right_sleep_stage
 - eight_room_temperature
@@ -93,3 +128,7 @@ script:
           target: 35
           duration: 3600
 ```
+
+### Notice
+
+Please note this component relies on an undocumented API utilized by the Eight Sleep mobile app to communicate with the Eight Sleep servers.  It is not supported by Eight Sleep and may malfunction if changes are made to either the mobile app operation or the API format.
diff --git a/source/_integrations/firmata.markdown b/source/_integrations/firmata.markdown
@@ -142,7 +142,7 @@ binary_sensor:
       required: true
       type: string
     pin:
-      description: The digital or analog pin number on the board.
+      description: The digital or analog pin number on the board. For analog pins the corresponding digital number must be used. Please use the pinout that corresponds to your board. For example, on the Arduino Uno, pin A2 corresponds to the digital pin number 16.
       required: true
       type: [integer, string]
     pin_mode:
@@ -232,7 +232,7 @@ firmata:
         negate: true
       - name: my_other_door
         pin_mode: INPUT
-        pin: A1
+        pin: 16   # A2
         negate: true
     sensors:
       - name: my_sensor
-Original file line number
+Diff line change
@@ Expand Up / @@ -5,6 +5,7 @@ ha_category: @@
       - Climate
       - Sensor
       - Switch
+      - Energy
     ha_release: 0.59
     ha_iot_class: Local Polling
     ha_config_flow: true
@@ Expand Down @@