Merge branch 'current' into next

_config.yml

@@ -107,8 +107,8 @@ social:
 # Home Assistant release details
 current_major_version: 2022
 current_minor_version: 6
-current_patch_version: 5
-date_released: 2022-06-10
+current_patch_version: 6
+date_released: 2022-06-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.

source/_integrations/calendar.markdown

@@ -99,8 +99,10 @@ automation:
         - "{{ trigger.event == 'start' }}"
       then:
         - service: light.turn_on
+          entity_id: light.front
       else:
         - service: light.turn_off
+          entity_id: light.front
   mode: queued
 ```
 {% endraw %}

source/_integrations/cast.markdown

@@ -25,7 +25,7 @@ Support for mDNS discovery in your local network is mandatory for automatic disc
 Known hosts:
   description: "A comma-separated list of hostnames or IP-addresses of cast devices, use if mDNS discovery is not working"
 Allowed UUIDs:
-  description: A comma-separated list of UUIDs of Cast devices to add to Home Assistant. **Use only if you don't want to add all available devices.** The device won't be added until discovered through either mDNS or if it's included in the list of known hosts. In order to find the UUID for your device use a mDNS browser or advanced users can use the following Python command (adjust friendly names as required) - `python3 -c "import pychromecast; print(pychromecast.get_listed_chromecasts(friendly_names=['Living Room TV', 'Bedroom TV', 'Office Chromecast']))`. This option is only visible if advanced mode is enabled in your user profile.
+  description: A comma-separated list of UUIDs of Cast devices to add to Home Assistant. **Use only if you don't want to add all available devices.** The device won't be added until discovered through either mDNS or if it's included in the list of known hosts. In order to find the UUID for your device use a mDNS browser or advanced users can use the following Python command (adjust friendly names as required) - `python3 -c "import pychromecast; print(pychromecast.get_listed_chromecasts(friendly_names=['Living Room TV', 'Bedroom TV', 'Office Chromecast']))"`. This option is only visible if advanced mode is enabled in your user profile.
 Ignore CEC:
   description: A comma-separated list of Chromecasts that should ignore CEC data for determining the
         active input. [See the upstream documentation for more information](https://github.com/home-assistant-libs/pychromecast#ignoring-cec-data). This option is only visible if advanced mode is enabled in your user profile.

source/_integrations/dsmr.markdown

@@ -89,6 +89,7 @@ $ docker run --device /dev/ttyUSB0:/dev/ttyUSB0 -d --name="home-assistant" -v /h
 DIY solutions (ESP8266 based):
 
 - [esp8266_p1meter (daniel-jong)](https://github.com/daniel-jong/esp8266_p1meter)
+- [DSMR reader for ESPHome (mmakaay)](https://github.com/mmakaay/dsmr-reader-for-esphome)
 
 {% include integrations/config_flow.md %}
 

source/_integrations/envisalink.markdown

@@ -70,11 +70,11 @@ panel_type:
   required: true
   type: string
 user_name:
-  description: Which username to authenticate with when connecting to the device. On a Honeywell alarm panel, the username/password are the same.
+  description: Which username to authenticate with when connecting to the device. This must be the username for connecting directly to the device and not the username for your EyezOn account. On a Honeywell alarm panel, the username/password are the same.
   required: true
   type: string
 password:
-  description: Which password to authenticate with when connecting to the device. EVL3 only works with max. 6 characters.
+  description: Which password to authenticate with when connecting to the device. This must be the password for connceting directly to the device and not the password for your EyezOn account. EVL3 only works with max. 6 characters.
   required: true
   type: string
 code:

source/_integrations/group.markdown

@@ -42,20 +42,59 @@ Home Assistant can group multiple binary sensors, covers, fans, lights, locks, m
 
 ## Group behavior
 
-By default, when any group member entity is `on`, the group will also be `on`. A complete overview of how groups behave:
+### Binary sensor, light, and switch groups
 
-- The group state is `on` if at least one group member is `on`.
-- Otherwise, the group state is `unavailable` if all group members are `unavailable`.
+In short, when any group member entity is `on`, the group will also be `on`. A complete overview of how groups behave:
+
+- The group state is `unavailable` if all group members are `unavailable`.
 - Otherwise, the group state is `unknown` if all group members are `unknown`.
+- Otherwise, the group state is `on` if at least one group member is `on`.
 - Otherwise, the group state is `off`.
 
-Some groups, like the binary sensors and lights, allow you set the "All entities" option. When enabled, this behavior is inverted, and all members of the group have to be `on` for the group to turn `on` as well. A complete overview of how groups behave when the "All entities" option is enabled:
+Binary sensor, light, and switch groups allow you set the "All entities" option. When enabled, the group behavior is inverted, and all members of the group have to be `on` for the group to turn `on` as well. A complete overview of how groups behave when the "All entities" option is enabled:
 
-- The group state is `off` if at least one group member is `off`.
-- Otherwise, the group state is `unavailable` if all group members are `unavailable`.
+- The group state is `unavailable` if all group members are `unavailable`.
 - Otherwise, the group state is `unknown` if at least one group member is `unknown` or `unavailable`.
+- Otherwise, the group state is `off` if at least one group member is `off`.
 - Otherwise, the group state is `on`.
 
+### Cover groups
+In short, when any group member entity is `open`, the group will also be `open`. A complete overview of how cover groups behave:
+
+- The group state is `unknown` if all group members are `unknown` or `unavailable`.
+- Otherwise, the group state is `opening` if at least one group member is `opening`.
+- Otherwise, the group state is `closing` if at least one group member is `closing`.
+- Otherwise, the group state is `open` if at least one group member is `open`.
+- Otherwise, the group state is `closed`.
+
+### Fan groups
+Fan groups don't support `unavailable` or `unknown` states.
+
+- The group state is `on` if at least one group member is `on`.
+- Otherwise, the group state is `off`.
+
+### Lock groups
+In short, when any group member entity is `unlocked`, the group will also be `unlocked`. A complete overview of how fan groups behave:
+
+- The group state is `unavailable` if all group members are `unavailable`.
+- Otherwise, the group state is `unknown` if at least one group member is `unknown` or `unavailable`.
+- Otherwise, the group state is `jammed` if at least one group member is `jammed`.
+- Otherwise, the group state is `locking` if at least one group member is `locking`.
+- Otherwise, the group state is `unlocking` if at least one group member is `unlocking`.
+- Otherwise, the group state is `unlocked` if at least one group member is `unlocked`.
+- Otherwise, the group state is `locked`.
+
+### Media player groups
+
+- The group state is `unavailable` if all group members are `unavailable`.
+- Otherwise, the group state is `unknown` if all group members are `unknown`.
+- Otherwise, the group state is `buffering` if all group members are `buffering`.
+- Otherwise, the group state is `idle` if all group members are `idle`.
+- Otherwise, the group state is `paused` if all group members are `paused`.
+- Otherwise, the group state is `playing` if all group members are `playing`.
+- Otherwise, the group state is `on` if at least one group member is not `off`, `unavailable` or `unknown`.
+- Otherwise, the group state is `off`.
+
 ## Managing groups
 
 To edit a group, **{% my helpers title="Settings -> Devices & Services -> Helpers" %}**. Find and select the group from the list.

source/_integrations/integration.markdown

@@ -46,7 +46,7 @@ Integration time:
 
 ## YAML Configuration
 
-Alternatlively, this integration can be configured and set up manually via YAML
+Alternatively, this integration can be configured and set up manually via YAML
 as well. To enable the Integration sensor in your installation, add the
 following to your `configuration.yaml` file:
 

source/_integrations/owntracks.markdown

@@ -112,7 +112,7 @@ owntracks:
 
 ## Using Owntracks regions
 
-Owntracks can track regions, and send region entry and exit information to Home Assistant. You set up a region in the Owntracks app which you should name the same as your Home Assistant Zone, and then make sure to turn on the `share` option for the region in the owntracks app. Please see the [owntracks documentation](https://owntracks.org/booklet/guide/waypoints/).
+Owntracks can track regions, and send region entry and exit information to Home Assistant. You set up a region in the Owntracks app which you should name the same as your Home Assistant Zone. Please see the [owntracks documentation](https://owntracks.org/booklet/guide/waypoints/).
 
 Home Assistant will use the enter and leave messages to set your zone location. Your location will be set to the center of zone when you enter. Location updates from OwnTracks will be ignored while you are inside a zone.
 
@@ -150,7 +150,7 @@ You can use iBeacons of both types together, so if you have a Zone `drive` with
 
 ## Importing Owntracks waypoints as zones
 
-By default, any Owntracks user connected to Home Assistant can export their waypoint definitions (from the *Export - Export to Endpoint* menu item) which will then be translated to zone definitions in Home Assistant. The zones will be named `<user>-<device> - <waypoint name>`. This functionality can be controlled in 2 ways:
+By default, any Owntracks user connected to Home Assistant can export their waypoint definitions (from the *Export - Export to Endpoint* menu item) which will then be translated to zone definitions in Home Assistant. The zones will be named `<user>-<device> - <region name>:<region uuid>`. This functionality can be controlled in 2 ways:
 
 1. The configuration variable `waypoints` can be set to `false` which will disable importing waypoints for all users.
 2. The configuration variable `waypoint_whitelist` can contain a list of users who are allowed to import waypoints.

source/_integrations/rachio.markdown

@@ -58,7 +58,7 @@ panel_iframe:
   rachio:
     title: Rachio
     url: "https://app.rach.io"
-    icon: mdi:water-pump
+    icon: mdi:sprinkler-variant
 ```
 
 ## Switch

source/_integrations/solaredge_local.markdown

@@ -72,7 +72,7 @@ In case you would like to convert the values for example to kWh instead of the d
 # Example configuration.yaml entry for sensor template platform
 template:
   - sensor:
-    - name: solaredge_energy_this_year_template:
+    - name: solaredge_energy_this_year_template
       state: "{{ (states('sensor.solaredge_energy_this_year') | float / 1000) | round(2) }}"
       unit_of_measurement: "KWh"
       icon: "mdi:solar-power"

source/_integrations/template.markdown

@@ -340,9 +340,9 @@ If you are using the state of a platform that might not be available during star
 
 ## Examples
 
-In this section, you find some real-life examples of how to use this sensor.
+In this section, you find some real-life examples of how to use template sensors.
 
-### Storing webhook information
+### Trigger based sensor and binary sensor storing webhook information
 
 Template entities can be triggered using any automation trigger, including webhook triggers. Use a trigger-based template entity to store this information in template entities.
 
@@ -379,7 +379,7 @@ curl --header "Content-Type: application/json" \
   http://homeassistant.local:8123/api/webhook/my-super-secret-webhook-id
 ```
 
-### Turning an event into a binary sensor
+### Turning an event into a trigger based binary sensor
 
 You can use a trigger-based template entity to convert any event or other automation trigger into a binary sensor. The below configuration will turn on a binary sensor for 5 seconds when the automation trigger triggers.
 
@@ -394,7 +394,7 @@ template:
         state: "true"
 ```
 
-### Sun Angle
+### State based sensor exposing sun angle
 
 This example shows the sun angle in the frontend.
 
@@ -410,7 +410,7 @@ template:
 
 {% endraw %}
 
-### Renaming Sensor Output
+### State based sensor modyfying another sensor's output
 
 If you don't like the wording of a sensor output, then the Template Sensor can help too. Let's rename the output of the [Sun component](/integrations/sun/) as a simple example:
 
@@ -430,7 +430,7 @@ template:
 
 {% endraw %}
 
-### Multiline Example With an `if` Test
+### State based sensor with multiline template with an `if` test
 
 This example shows a multiple line template with an `if` test. It looks at a sensing switch and shows `on`/`off` in the frontend, and shows 'standby' if the power use is less than 1000 watts.
 
@@ -454,7 +454,7 @@ template:
 
 {% endraw %}
 
-### Change The Unit of Measurement
+### State based sensor changing the unit of measurement of another sensor
 
 With a Template Sensor, it's easy to convert given values into others if the unit of measurement doesn't fit your needs.
 
@@ -474,7 +474,7 @@ template:
 
 {% endraw %}
 
-### Washing Machine Running
+### State based binary sensor - Washing Machine Running
 
 This example creates a washing machine "load running" sensor by monitoring an
 energy meter connected to the washer. During the washer's operation, the energy meter will fluctuate wildly, hitting zero frequently even before the load is finished. By utilizing `delay_off`, we can have this sensor only turn off if there has been no washer activity for 5 minutes.
@@ -494,7 +494,7 @@ template:
 
 {% endraw %}
 
-### Is Anyone Home
+### State based binary sensor - Is Anyone Home
 
 This example is determining if anyone is home based on the combination of device tracking and motion sensors. It's extremely useful if you have kids/baby sitter/grand parents who might still be in your house that aren't represented by a trackable device in Home Assistant. This is providing a composite of Wi-Fi based device tracking and Z-Wave multisensor presence sensors.
 
@@ -516,7 +516,7 @@ template:
 
 {% endraw %}
 
-### Device Tracker sensor with Latitude and Longitude Attributes
+### State based binary sensor - Device Tracker sensor with Latitude and Longitude Attributes
 
 This example shows how to combine a non-GPS (e.g., NMAP) and GPS device tracker while still including latitude and longitude attributes
 
@@ -546,7 +546,7 @@ template:
 
 {% endraw %}
 
-### Change the icon when a state changes
+### State based binary sensor - Change the icon when a state changes
 
 This example demonstrates how to use template to change the icon as its state changes. This icon is referencing its own state.
 
@@ -592,6 +592,30 @@ template:
 
 {% endraw %}
 
+### State based select - Control Day/Night mode of a camera
+
+This show how a state based template select can be used to call a service.
+
+{% raw %}
+
+
+```yaml
+template:
+  select:
+    - name: "Porch Camera Day-Night Mode"
+      unique_id: porch_camera_day_night_mode
+      state: "{{ state_attr('camera.porch_camera_sd', 'day_night_mode') }}"
+      options: "{{ ['off', 'on', 'auto'] }}"
+      select_option:
+        - service: tapo_control.set_day_night_mode
+          data:
+            day_night_mode: "{{ option }}"
+          target:
+            entity_id: camera.porch_camera_sd
+```
+
+{% endraw %}
+
 ### Self referencing
 
 This example demonstrates how the `this` variable can be used in templates for self-referencing.

source/_integrations/threshold.markdown

@@ -17,7 +17,7 @@ ha_platforms:
 ha_integration_type: helper
 ---
 
-The threshold integration observes the state of another sensor. If the value is below or higher than the given threshold then state of the threshold sensor is changed. It support also a range both the upper and lower limits are given.
+The threshold integration observes the state of another sensor. If the value is below or higher than the given threshold, then the state of the threshold sensor is changed. It also supports a range if both the upper and lower limits are given.
 
 If the sensor is configured with no hysteresis and the sensor value is equal to the threshold, the sensor is turned off since it is not upper or lower with respect to the threshold.
 

source/_integrations/timer.markdown

@@ -16,7 +16,7 @@ When a timer finishes or gets canceled the corresponding events are fired. This
 
 
 ## Configuration
-The preferred way to configure timer helpers is via the user interface. To add one, go to Settings -> Automations & Scenes, select the "Helpers" tab and click the add button; next choose the “Timer” option.
+The preferred way to configure timer helpers is via the user interface at **Settings** -> **Devices & Services** -> **Helpers** and click the add button; next choose the **Timer** option.
 
 You can also click the following button to be redirected to the Helpers page of your Home Assistant instance.
 

source/_integrations/yeelight.markdown

@@ -203,8 +203,9 @@ This integration is tested to work with the following models. If you have a diff
 | `ceiling10`| YLDL01YL     | Yeelight Meteorite Pendant Light                 |
 | `ceiling13`| YLXD01YL     | Yeelight LED Ceiling Light                       |
 | `ceil26`   | YLXD76YL     | Yeelight Ceiling Light - Updated HomeKit 23w     |
-| ?          | YLXD013-B    | Yeelight Arwen Ceiling Light 450C                |
-| ?          | YLXD013-C    | Yeelight Arwen Ceiling Light 550C                |
+| ?, may be `ceilb` | YLXD013-B    | Yeelight Arwen Ceiling Light 450C         |
+| ?, may be `ceilb` | YLXD013-C    | Yeelight Arwen Ceiling Light 550C         |
+| `ceilb`    | YLXD013      | Yeelight Arwen Ceiling Light 450S                |
 
 ## Services
 

source/_posts/2022-05-29-matter-in-home-assistant-workshop-announcement.markdown

@@ -14,6 +14,10 @@ og_image: /images/blog/2022-05-matter-in-home-assistant-workshop-announcement/so
 
 <img src='/images/blog/2022-05-matter-in-home-assistant-workshop-announcement/header.png' alt="Decorative header." class='no-shadow'>
 
+## [The workshop instructions can be found here.](/matter-june-22)
+
+## [Home Assistant SkyConnect interest form](/skyconnect-interest)
+
 Matter is a new [smart home standard](https://csa-iot.org/all-solutions/matter/) that is scheduled to launch in fall. Across the industry, companies like Hue, IKEA, Google and Apple are working together to try and solve connectivity, ease of setup and interoperability once and for all. Development is happening as part of the [Connectivity Standards Alliance](https://csa-iot.org/) (CSA) of which we ([Nabu Casa](https://www.nabucasa.com)) are also a participating member.
 
 <center><img src='/images/supported_brands/matter.png' alt='Matter logo' class='no-shadow'></center><br>

source/_posts/2022-06-01-release-20226.markdown

@@ -64,6 +64,7 @@ Enjoy the release (and upcoming events)!
 - [Release 2022.6.3 - June 6](#release-202263---june-6)
 - [Release 2022.6.4 - June 7](#release-202264---june-7)
 - [Release 2022.6.5 - June 10](#release-202265---june-10)
+- [Release 2022.6.6 - June 14](#release-202266---june-14)
 - [Need help? Join the community!](#need-help-join-the-community)
 - [Breaking Changes](#breaking-changes)
 - [Farewell to the following](#farewell-to-the-following)
@@ -595,6 +596,47 @@ The following integrations are now available via the Home Assistant UI:
 [wallbox docs]: /integrations/wallbox/
 [yolink docs]: /integrations/yolink/
 
+## Release 2022.6.6 - June 14
+
+- Filter out forced updates in live logbook when the state has not changed ([@bdraco] - [#73335]) ([logbook docs])
+- Fix zwave_js add node schemas ([@raman325] - [#73343]) ([zwave_js docs])
+- Hive Bump pyhiveapi to 0.5.10 for credentials fix ([@KJonline] - [#73365]) ([hive docs])
+- Fix reload race in yeelight when updating the ip address ([@bdraco] - [#73390]) ([yeelight docs])
+- Only update unifiprotect ips from discovery when the console is offline ([@bdraco] - [#73411]) ([unifiprotect docs])
+- Fix smart by bond detection with v3 firmware ([@marciogranzotto] - [#73414]) ([bond docs])
+- Bump aiohue to 4.4.2 ([@balloob] - [#73420]) ([hue docs])
+- Fix fan support in nest, removing FAN_ONLY which isn't supported ([@allenporter] - [#73422]) ([nest docs])
+- Guard withings accessing hass.data without it being set ([@balloob] - [#73454]) ([withings docs])
+- Fix max_value access for number platform in Overkiz ([@tetienne] - [#73479]) ([overkiz docs])
+
+[#73335]: https://github.com/home-assistant/core/pull/73335
+[#73343]: https://github.com/home-assistant/core/pull/73343
+[#73365]: https://github.com/home-assistant/core/pull/73365
+[#73390]: https://github.com/home-assistant/core/pull/73390
+[#73411]: https://github.com/home-assistant/core/pull/73411
+[#73414]: https://github.com/home-assistant/core/pull/73414
+[#73420]: https://github.com/home-assistant/core/pull/73420
+[#73422]: https://github.com/home-assistant/core/pull/73422
+[#73454]: https://github.com/home-assistant/core/pull/73454
+[#73479]: https://github.com/home-assistant/core/pull/73479
+[@KJonline]: https://github.com/KJonline
+[@allenporter]: https://github.com/allenporter
+[@balloob]: https://github.com/balloob
+[@bdraco]: https://github.com/bdraco
+[@marciogranzotto]: https://github.com/marciogranzotto
+[@raman325]: https://github.com/raman325
+[@tetienne]: https://github.com/tetienne
+[bond docs]: /integrations/bond/
+[hive docs]: /integrations/hive/
+[hue docs]: /integrations/hue/
+[logbook docs]: /integrations/logbook/
+[nest docs]: /integrations/nest/
+[overkiz docs]: /integrations/overkiz/
+[unifiprotect docs]: /integrations/unifiprotect/
+[withings docs]: /integrations/withings/
+[yeelight docs]: /integrations/yeelight/
+[zwave_js docs]: /integrations/zwave_js/
+
 ## Need help? Join the community!
 
 Home Assistant has a great community of users who are all more than willing

source/_redirects

@@ -9,6 +9,10 @@
 /get-blueprints https://community.home-assistant.io/c/blueprints-exchange/53
 /latest-security-alert /blog/2021/01/23/security-disclosure2/
 
+# Matter workshop June 2022
+/skyconnect-interest https://docs.google.com/forms/d/e/1FAIpQLScEjHSBJszUZfgO3MIDO51IHr3Oeohcs8BLpRIjY1liJ58IpA/viewform?usp=sf_link
+/matter-june-22 https://docs.google.com/document/d/1MldgA337wHTEx-vPkoxlCqKHrhVm5QIcHV32iLsv_2k/edit?usp=sharing
+
 # Redirect for Energy
 /energy /home-energy-management
 /integrations/energy /docs/energy 301!