The Insteon company has shut down and turned off their cloud as of April 2022.
diff --git a/source/_integrations/intellifire.markdown b/source/_integrations/intellifire.markdown index 3ccfb8ce402..e1a5979ecc1 100644 --- a/source/_integrations/intellifire.markdown +++ b/source/_integrations/intellifire.markdown @@ -88,4 +88,3 @@ In some cases, this will restore control to the fireplace, but if it doesn't you #### Power Cycle The sure fire way to reset the IFT module is to just power-cycle it. This will work just about every time. - diff --git a/source/_integrations/knx.markdown b/source/_integrations/knx.markdown index 245199b6142..69199908f58 100644 --- a/source/_integrations/knx.markdown +++ b/source/_integrations/knx.markdown @@ -23,7 +23,7 @@ ha_codeowners: - '@farmio' - '@marvin-w' ha_domain: knx -ha_quality_scale: silver +ha_quality_scale: platinum ha_platforms: - binary_sensor - button diff --git a/source/_integrations/lifx.markdown b/source/_integrations/lifx.markdown index c97d022da0b..be8803f50d7 100644 --- a/source/_integrations/lifx.markdown +++ b/source/_integrations/lifx.markdown @@ -11,6 +11,8 @@ ha_homekit: true ha_platforms: - light ha_integration_type: integration +ha_codeowners: + - '@Djelibeybi' --- The `lifx` integration allows you to integrate your [LIFX](https://www.lifx.com) bulbs into Home Assistant. diff --git a/source/_integrations/meater.markdown b/source/_integrations/meater.markdown index 561efe67c25..4c94f85c073 100644 --- a/source/_integrations/meater.markdown +++ b/source/_integrations/meater.markdown @@ -1,5 +1,5 @@ --- -title: Meater Smart Meat Thermometer +title: Meater description: Instructions on how to integrate the Meater Temperature Probe within Home Assistant. ha_category: - Sensor @@ -8,7 +8,11 @@ ha_iot_class: Cloud Polling ha_config_flow: true ha_codeowners: - '@Sotolotl' + - '@emontnemery' ha_domain: meater +ha_platforms: + - sensor +ha_integration_type: integration --- The Meater Smart Meat Thermometer integration allows for communicating with the [Meater Temperature Probe](https://meater.com/) from Apption Labs. @@ -25,4 +29,4 @@ Devices will only be returned from the Meater Cloud API after the following crit - Device must be seen by the Meater Cloud. Ensure you've completed a cook while connected to Meater Cloud. - The Meater app or Block must have an active Bluetooth connection with the device. -- The Meater app or Block must have an active Meater Cloud connection. \ No newline at end of file +- The Meater app or Block must have an active Meater Cloud connection. diff --git a/source/_integrations/mpd.markdown b/source/_integrations/mpd.markdown index 62d747328aa..d69fbfc48eb 100644 --- a/source/_integrations/mpd.markdown +++ b/source/_integrations/mpd.markdown @@ -5,8 +5,6 @@ ha_category: - Media Player ha_release: pre 0.7 ha_iot_class: Local Polling -ha_codeowners: - - '@fabaff' ha_domain: mpd ha_platforms: - media_player diff --git a/source/_integrations/no_ip.markdown b/source/_integrations/no_ip.markdown index ca64b636e41..040c40b5dbb 100644 --- a/source/_integrations/no_ip.markdown +++ b/source/_integrations/no_ip.markdown @@ -5,8 +5,6 @@ ha_category: - Network ha_iot_class: Cloud Polling ha_release: 0.57 -ha_codeowners: - - '@fabaff' ha_domain: no_ip ha_integration_type: integration --- diff --git a/source/_integrations/onvif.markdown b/source/_integrations/onvif.markdown index 663afbf7ddf..24ae0535fb2 100644 --- a/source/_integrations/onvif.markdown +++ b/source/_integrations/onvif.markdown @@ -13,6 +13,7 @@ ha_platforms: - binary_sensor - button - camera + - diagnostics - sensor ha_integration_type: integration --- diff --git a/source/_integrations/pi_hole.markdown b/source/_integrations/pi_hole.markdown index 5dc54da18bb..338db2ba5d8 100644 --- a/source/_integrations/pi_hole.markdown +++ b/source/_integrations/pi_hole.markdown @@ -10,7 +10,6 @@ ha_iot_class: Local Polling ha_config_flow: true ha_release: 0.28 ha_codeowners: - - '@fabaff' - '@johnluetke' - '@shenxn' ha_domain: pi_hole diff --git a/source/_integrations/pvoutput.markdown b/source/_integrations/pvoutput.markdown index dd47223ca7c..34eee9326e0 100644 --- a/source/_integrations/pvoutput.markdown +++ b/source/_integrations/pvoutput.markdown @@ -6,7 +6,6 @@ ha_category: ha_release: 0.33 ha_iot_class: Cloud Polling ha_codeowners: - - '@fabaff' - '@frenck' ha_config_flow: true ha_domain: pvoutput diff --git a/source/_integrations/sabnzbd.markdown b/source/_integrations/sabnzbd.markdown index 3a96c20ffc3..dce689ba6fe 100644 --- a/source/_integrations/sabnzbd.markdown +++ b/source/_integrations/sabnzbd.markdown @@ -10,6 +10,9 @@ ha_domain: sabnzbd ha_platforms: - sensor ha_integration_type: integration +ha_codeowners: + - '@shaiu' +ha_config_flow: true --- The `sabnzbd` integration will allow you to monitor and control your downloads with [SABnzbd](https://sabnzbd.org) from within Home Assistant and setup automations based on the information. diff --git a/source/_integrations/sensibo.markdown b/source/_integrations/sensibo.markdown index ec35e006bd2..7412ad23e02 100644 --- a/source/_integrations/sensibo.markdown +++ b/source/_integrations/sensibo.markdown @@ -8,6 +8,7 @@ ha_category: - Number - Select - Sensor + - Updates ha_release: 0.44 ha_iot_class: Cloud Polling ha_config_flow: true @@ -22,6 +23,7 @@ ha_platforms: - number - select - sensor + - update ha_homekit: true ha_dhcp: true ha_integration_type: integration diff --git a/source/_integrations/senz.markdown b/source/_integrations/senz.markdown index 35754ca6505..501052f90b6 100644 --- a/source/_integrations/senz.markdown +++ b/source/_integrations/senz.markdown @@ -11,6 +11,7 @@ ha_codeowners: ha_domain: senz ha_platforms: - climate +ha_integration_type: integration --- The SENZ integration allows you to control and monitor your nVent RAYCHEM SENZ-WIFI thermostats. diff --git a/source/_integrations/slimproto.markdown b/source/_integrations/slimproto.markdown index 2b6b4147efa..1ece1666b79 100644 --- a/source/_integrations/slimproto.markdown +++ b/source/_integrations/slimproto.markdown @@ -1,5 +1,5 @@ --- -title: SlimProto (Squeezebox Players) +title: SlimProto (Squeezebox players) description: Instructions on how to integrate a SlimProto-based player (e.g., Squeezebox) into Home Assistant without the need for a media server. ha_category: - Media Player @@ -7,10 +7,11 @@ ha_release: 2022.5 ha_iot_class: Local Push ha_domain: slimproto ha_codeowners: - - "@marcelveldt" + - '@marcelveldt' ha_config_flow: true ha_platforms: - media_player +ha_integration_type: integration --- The SlimProto integration allows you to control a [Squeezebox](https://en.wikipedia.org/wiki/Squeezebox_%28network_music_player%29) music player directly from Home Assistant, without the need for an external Media Server such as Logitech Media Server. This lets you control Squeezebox hardware like the Classic, Transporter, Duet, Boom, Radio, and Touch and software players like [Squeezelite](https://github.com/ralph-irving/squeezelite), [PiCorePlayer](https://www.picoreplayer.org/) or [Max2Play](https://www.max2play.com/en/). For the real DIY enthusiast, [there even is a player for the ESP32](https://github.com/sle118/squeezelite-esp32). diff --git a/source/_integrations/smtp.markdown b/source/_integrations/smtp.markdown index cda7a604723..f9e5f1391cf 100644 --- a/source/_integrations/smtp.markdown +++ b/source/_integrations/smtp.markdown @@ -5,8 +5,6 @@ ha_category: - Notifications ha_iot_class: Cloud Push ha_release: pre 0.7 -ha_codeowners: - - '@fabaff' ha_domain: smtp ha_platforms: - notify diff --git a/source/_integrations/squeezebox.markdown b/source/_integrations/squeezebox.markdown index ff4c0802baa..1d47aaf0ae8 100644 --- a/source/_integrations/squeezebox.markdown +++ b/source/_integrations/squeezebox.markdown @@ -1,5 +1,5 @@ --- -title: Logitech Squeezebox +title: Squeezebox (Logitech Media Server) description: Instructions on how to integrate a Logitech Squeezebox player into Home Assistant. ha_category: - Media Player diff --git a/source/_integrations/steam_online.markdown b/source/_integrations/steam_online.markdown index 25b7ac87ab9..a84000b164a 100644 --- a/source/_integrations/steam_online.markdown +++ b/source/_integrations/steam_online.markdown @@ -9,6 +9,9 @@ ha_domain: steam_online ha_platforms: - sensor ha_integration_type: integration +ha_codeowners: + - '@tkdrob' +ha_config_flow: true --- The `steam` sensor platform will allow you to track the online status of public [Steam](https://steamcommunity.com) accounts. diff --git a/source/_integrations/syslog.markdown b/source/_integrations/syslog.markdown index e282e25dfb6..2a8b5853c3c 100644 --- a/source/_integrations/syslog.markdown +++ b/source/_integrations/syslog.markdown @@ -5,8 +5,6 @@ ha_category: - Notifications ha_release: pre 0.7 ha_iot_class: Local Push -ha_codeowners: - - '@fabaff' ha_domain: syslog ha_platforms: - notify diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown index 2f11a431118..6bc9842a832 100644 --- a/source/_integrations/tplink.markdown +++ b/source/_integrations/tplink.markdown @@ -12,6 +12,7 @@ ha_config_flow: true ha_codeowners: - '@rytilahti' - '@thegardenmonkey' + - '@bdraco' ha_domain: tplink ha_platforms: - diagnostics diff --git a/source/_integrations/tractive.markdown b/source/_integrations/tractive.markdown index 09f98daa0bf..43b5295a5f9 100644 --- a/source/_integrations/tractive.markdown +++ b/source/_integrations/tractive.markdown @@ -14,6 +14,7 @@ ha_domain: tractive ha_platforms: - binary_sensor - device_tracker + - diagnostics - sensor - switch ha_integration_type: integration diff --git a/source/_integrations/tradfri.markdown b/source/_integrations/tradfri.markdown index 2a53507bec2..f5ff6b91448 100644 --- a/source/_integrations/tradfri.markdown +++ b/source/_integrations/tradfri.markdown @@ -57,4 +57,4 @@ Please make sure you have `autoconf` installed (`$ sudo apt-get install autoconf ## Known limitations - The TRÅDFRI Shortcut button, Remotes and motion sensor only send information about their battery status, no events, to Home Assistant and thus can't be used to automate with. If you want to automate with these devices, you need to use something like [ZHA](/integrations/zha/). -- The groups you find in the app are not imported into Home Assistant as they are known to cause stability issues. We recommend that you use the native [light groups](/integrations/light.group/) instead. \ No newline at end of file +- The groups you find in the app are not imported into Home Assistant as they are known to cause stability issues. We recommend that you use the native [light groups](/integrations/light.group/) instead. diff --git a/source/_integrations/tuya.markdown b/source/_integrations/tuya.markdown index f84fd554d47..b7fa1a7f1f2 100644 --- a/source/_integrations/tuya.markdown +++ b/source/_integrations/tuya.markdown @@ -23,7 +23,6 @@ ha_domain: tuya ha_codeowners: - '@Tuya' - '@zlinoliver' - - '@METISU' - '@frenck' ha_platforms: - alarm_control_panel diff --git a/source/_integrations/version.markdown b/source/_integrations/version.markdown index bea539baad4..db6b36af93b 100644 --- a/source/_integrations/version.markdown +++ b/source/_integrations/version.markdown @@ -8,7 +8,6 @@ ha_iot_class: Local Push ha_release: 0.52 ha_quality_scale: internal ha_codeowners: - - '@fabaff' - '@ludeeus' ha_domain: version ha_platforms: diff --git a/source/_integrations/vicare.markdown b/source/_integrations/vicare.markdown index 8d5caf2ead2..30e82e7d36d 100644 --- a/source/_integrations/vicare.markdown +++ b/source/_integrations/vicare.markdown @@ -13,6 +13,7 @@ ha_platforms: - binary_sensor - button - climate + - diagnostics - sensor - water_heater ha_dhcp: true diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown index ef5968dcbc8..4e56625875a 100644 --- a/source/_integrations/xiaomi_miio.markdown +++ b/source/_integrations/xiaomi_miio.markdown @@ -26,6 +26,7 @@ ha_platforms: - binary_sensor - button - device_tracker + - diagnostics - fan - humidifier - light diff --git a/source/_integrations/yamaha_musiccast.markdown b/source/_integrations/yamaha_musiccast.markdown index a601a7a425c..6ab154fc491 100644 --- a/source/_integrations/yamaha_musiccast.markdown +++ b/source/_integrations/yamaha_musiccast.markdown @@ -15,6 +15,7 @@ ha_platforms: - media_player - number - select + - switch ha_integration_type: integration --- diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index 71dc60afbb7..b12b3998afd 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -31,6 +31,7 @@ ha_platforms: - climate - cover - device_tracker + - diagnostics - fan - light - lock diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown index 4a1bdc965e2..f95724822a1 100644 --- a/source/_integrations/zwave_js.markdown +++ b/source/_integrations/zwave_js.markdown @@ -39,6 +39,7 @@ ha_platforms: - siren - switch ha_integration_type: integration +ha_zeroconf: true --- This integration allows you to control a Z-Wave network via the [Z-Wave JS](https://zwave-js.github.io/node-zwave-js/#/) driver. This is our recommended Z-Wave integration for Home Assistant. If you're migrating from the deprecated `zwave`, see [our migration instructions](#migrating-from-previous-z-wave-implementations). diff --git a/source/_posts/2022-05-04-release-20225.markdown b/source/_posts/2022-05-04-release-20225.markdown new file mode 100644 index 00000000000..c5382108152 --- /dev/null +++ b/source/_posts/2022-05-04-release-20225.markdown @@ -0,0 +1,1314 @@ +--- +layout: post +title: "2022.5: Beta release notes" +description: "Beta release notes for Home Assistant Core 2022.5" +date: 2022-04-27 00:00:00 +date_formatted: "May 04, 2022" +author: Franck Nijhof +author_twitter: frenck +comments: true +categories: +- Release-Notes +- Core +og_image: /images/blog/2022-05/social.png +--- + +
+
+These are the beta release notes for Home Assistant Core 2022.5 (and is thus a
+work in progress).
+
+If you encounter any issues with the beta release, please report them on GitHub:
+
+- Issues with integrations, automations and such (Core related):
+
+Are you running Home Assistant OS or Supervised? The Supervisor has been fully
+merged into the configuration menu, to provide a seamless/unified experience.
+This removes weirdness like having a network section in the system menu
+and the Supervisor section.
+
+Blueprints are now moved to the automations & scenes section, and by popular
+request: Helpers have moved to the devices & services page. Areas & Zone are
+now nicely brought together in a single menu, and there is now an extensive
+System menu.
+
+## Find entities even quicker than before
+
+Looking to access that one entity quickly? But it isn't on your dashboard?
+
+The [Quick Bar](/docs/tools/quick-bar/) is actually really helpful for that;
+just press `e` anywhere you are in Home Assistant. But what if you are on
+mobile or a tablet?
+
+This release adds a quick search button to the dashboards, so you can look up
+and access any entity you need, even when it is not on your current dashboard.
+
+
+
+## Gauge card segment colors
+
+A excellent addition by [@Netzwerkfehler] in this release is the ability to
+freely define the the number of segments, and their colors, for the gauge card!
+
+
+
+Screenshot of the gauge card with multiple colored segments.
+
+
+An example in YAML:
+
+```yaml
+actions:
+ - if:
+ - alias: "If no one is home"
+ condition: state
+ entity_id: zone.home
+ state: 0
+ then:
+ - alias: "Then start cleaning already!"
+ service: vacuum.start
+ target:
+ area_id: living_room
+ # The `else` is fully optional and can be omitted
+ else:
+ - service: notify.notify
+ data:
+ message: "Skipped cleaning, someone is home!"
+```
+
+[More information can be found in the scripts documentation](/docs/scripts/#if-then)
+
+### Calendar trigger
+
+This release [@allenporter] gave the [Calendar] integration (and the
+[Google Calendars] integration lots of love. In the process, a new Calendar
+trigger was added, which is available for use in your automations.
+
+
+
+This brand new trigger is a little more flexible compared to the (previously
+only other option) state trigger. It is available for automation in YAML as well,
+and the trigger provides [a lot of trigger variables](/docs/automation/templating/#calendar)
+you can use in your templates.
+
+[More information can be found in the Calendar integration documentation](/integrations/calendar/#automation)
+
+[@allenporter]: https://github.com/allenporter
+[Calendar]: /integrations/calendar/
+[Google Calendars]: /integrations/google
+
+### For each
+
+We had a number of options available to repeat a [group of actions]. For
+example, repeating based on a count, repeating while a condition passes, and
+repeating until a condition passes.
+
+These have been very powerful, but repeating a sequence for each item in a list
+was also requested and voted for. This release implements: For each.
+
+This is an advanced feature and is only available for use in YAML right now.
+Here is an example of a for each that sends out two notifications in different
+languages:
+
+{% raw %}
+
+```yaml
+repeat:
+ for_each:
+ - language: English
+ message: Hello World
+ - language: Dutch
+ hello: Hallo Wereld
+ sequence:
+ - service: notify.phone
+ data:
+ title: "Message in {{ repeat.item.language }}"
+ message: "{{ repeat.item.message }}!"
+```
+
+{% endraw %}
+
+Each item in the list will be run against a sequence of actions, and the item
+is available as a variable you can use in your templates. The list of
+items you can provide to `for_each` can be mappings, lists of just strings,
+and even complex templates that provide a list as a result.
+
+[More information can be found in the scripts documentation](/docs/scripts/#for-each)
+
+[group of actions]: /docs/scripts/#repeat-a-group-of-actions
+
+### Continue on error
+
+An automation and script run a sequence of actions. One of the comments and
+questions we often see/read/get is: "If one of the actions fails, why does
+the whole automation stop?"
+
+Good question! To answer this, we have added a new feature: Continue on error.
+This will enable you to allow certain steps in an automation or script sequence
+to fail, without interrupting the whole sequence.
+
+This is an example of a script that will always run the second action, even
+if the first action fails with an error.
+
+```yaml
+sequence:
+ - alias: "If this one fails..."
+ continue_on_error: true
+ service: notify.super_unreliable_service_provider
+ data:
+ message: "I'm going to error out..."
+
+ - alias: "This one will still run!"
+ service: persistent_notification.create
+ data:
+ title: "Hi there!"
+ message: "I'm fine..."
+```
+
+This is an advanced feature, currently only availble for automations in YAML.
+
+[More information can be found in the scripts documentation](/docs/scripts/#continuing-on-error)
+
+### Stopping a script or automation
+
+You can now stop a script or automation halfway using the Stop action.
+Combined with the previously mentioned new If-then action, this can be used
+to stop an automation or script conditionally.
+
+For example, this can be helpful if you want just part of an automation to
+run when you are home and run it at full when you are away.
+
+This feature is available both via the UI and YAML.
+
+
+
+Additionally, the stop-action can be set as an "error" which gives
+you a way to stop an automation or script and mark it as an error (for
+example, if you detected something unexpected).
+
+[More information can be found in the scripts documentation](/docs/scripts/#stopping-a-script-sequence)
+
+### Parallelizing actions
+
+This release introduces a highly advanced feature, that provides a way to
+parallelize actions (or groups of actions).
+
+By default, all sequences of actions in Home Assistant run sequentially.
+This means the next action is started after the current action has been
+completed.
+
+This is not always needed, for example, if the sequence of actions
+doesn’t rely on each other and order doesn’t matter. For those cases, the
+parallel action can be used to run the actions in the sequence in parallel,
+meaning all the actions are started simultaneously.
+
+```yaml
+automation:
+ - trigger:
+ - platform: state
+ entity_id: binary_sensor.motion
+ to: "on"
+ action:
+ - parallel:
+ - service: notify.person1
+ data:
+ message: "These messages are sent at the same time!"
+ - service: notify.person2
+ data:
+ message: "These messages are sent at the same time!"
+```
+
+As said, this is quite an powerful and advanced feature, and it comes with
+caveats. Be sure to check out the [script documentation on parallizing actions](/docs/scripts/#parallelizing-actions)
+before you decide on using it.
+
+### And there is even more!
+
+These items still need to be processed for the release notes, or might just
+be summed up.
+
+- **Allow any entity to match state condition** ([@frenck] - [#69763])
+
+ If any of the entities matches a certain condition, instead of all of them:
+
+ ```yaml
+ condition:
+ condition: state
+ entity_id:
+ - binary_sensor.motion_sensor_left
+ - binary_sensor.motion_sensor_right
+ match: any
+ state: "on"
+ ```
+
+ YAML only capability.
+
+ [More information can be found on the state condition documentation](/docs/scripts/conditions#state-condition)
+
+- **Trigger on not matching to/from states** ([@frenck] - [#69760])
+
+ Adds support for `not_from` and `not_to` in the state trigger:
+
+ ```yaml
+ automation:
+ trigger:
+ - platform: state
+ entity_id: light.living_room
+ not_from:
+ - "unavailable"
+ - "unknown"
+ to: "on"
+ ```
+
+ ```yaml
+ automation:
+ trigger:
+ - alias: "Trigger on any alarm state, except when it is disarmed"
+ platform: state
+ entity_id: alarm_control_panel.home
+ not_to: "disarmed"
+ ```
+
+ YAML only capability.
+
+ [More information can be found on the state condition documentation](/docs/scripts/conditions#state-condition)
+
+- **Allow disabling specific triggers/actions/conditions** ([@frenck] - [#70082])
+
+ Adds support to disable/enable any trigger, action or condition; without
+ removing it from the automation or script.
+
+ ```yaml
+ # Example automation with a disabled trigger
+ automation:
+ trigger:
+ # This trigger will not trigger, as it is disabled.
+ # This automation does not run when the sun is set.
+ - enabled: false
+ platform: sun
+ event: sunset
+
+ # This trigger will fire, as it is not disabled.
+ - platform: time
+ at: "15:32:00"
+ ```
+
+ Currently only supported by YAML, but supposed to be a UI driven feature
+ (as well, in YAML you can just comment out). UI feature hasn't landed yet.
+
+ - Triggers: 
+
+## Database optimizations
+
+{% details "TODO" %}
+
+- Add automatic monthly repacking to section?
+ - Auto repack the database on the second sunday of the month ([@bdraco] - [#69314]) ([recorder docs]) (breaking-change) (noteworthy)
+
+{% enddetails %}
+
+The last release focused on reducing the size of the database and optimizing
+the writing of data to the database.
+
+While there are some additional optimizations in this release to further reduce
+the amount of data that needs to be written, in this release, we focused on how
+often data is read from the database and optimizing its scale for larger setups.
+
+This release is for you if you have many sensors generating statistics, as
+compiling statistics now takes 30-100x less time.
+
+Are you using the [History Stats] integration? The number of database queries
+needed for most sensors with a fixed start time is 99% less.
+
+Even if your instance is small and you don’t record many states, you’ll benefit
+from the recorder optimizations to avoid waking up when there is no new
+data to commit.
+
+We have made additional improvements to the history APIs to speed up retrieving
+from the database, reducing API response times by 15-35% on average.
+
+Finally, we have reduced the memory used during database migrations to smooth
+future migrations.
+
+[History Stats]: /integrations/history_stats
+
+## Update entity updates
+
+{% details "TODO" %}
+
+- Add screenshot
+- Improve story
+- Link some blueprints from the community?
+
+{% enddetails %}
+
+In the [previous release, we introduced update entities](/blog/2022/04/06/release-20224/#introducing-update-entities).
+It was a well received concept and this release, we added a couple of
+improvements to it, based on the feedback we've received from you all.
+
+Almost all feedback involved "Skipping an update"-related functionality. How
+to see which updates I have skipped? Can I unskip an update?
+
+To help with these we added:
+
+- The possibility to view all skipped update from the UI.
+- Added an "unskip" button to the updates that have been skipped.
+- Added a {% my developer_call_service service="update.clear_skipped" %}
+ service that can be used in automation or scripts to unskip updates.
+
+This will give you full insight, control and automation capabilities to "unskip"
+any update you have previously skipped.
+
+Additionally, this release two new integrations have implemented the update
+entity:
+
+- [Sensibo], done by [@gjohansson-ST]
+- [AVM FRITZ!Box Tools], done by [@Mask3007]
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[@Mask3007]: https://github.com/Mask3007
+[AVM FRITZ!Box Tools]: /integrations/fritz
+[Sensibo]: /integrations/sensibo
+
+## Template selector
+
+{% details "TODO" %}
+
+- Revisit story
+- Replace screenshot
+- Make smaller item?
+
+{% enddetails %}
+
+A new [selector](/docs/blueprint/selectors/) has been added this release:
+The [Template selector].
+
+This new selector can be used in, for example, Blueprints to ask the user
+for a template input; providing a nice code editor with Jinja syntax
+highlighting and entity auto-completion.
+
+This release adds the template editor to the automation and script editors,
+in case of the template conditions and wait template action.
+
+
+
+Selectors are not just available for Blueprints, but also for your script fields
+and (custom) integration and dashboard card developers.
+
+[Template selector]: /docs/blueprint/selectors/#template-selector
+
+## Other noteworthy changes
+
+{% details "TODO" %}
+
+- Revisit / recheck for other, newer and/or better items
+- Check contents/spelling/grammar/order
+
+{% enddetails %}
+
+There is much more juice in this release; here are some of the other
+noteworthy changes this release:
+
+- Every script now automatically gets an unique ID, which means you can edit
+ their name, icon, and assign them to areas straight from the UI!
+ Thanks, [@frenck]!
+- If you run Z-Wave JS server manually in for example, a Docker container, it
+ will now be automatically discovered on your network. Thanks [@raman325]!
+- Template entities now have a `this` variable availble, which is reference
+ to state of the template entity itself. Awesome work [@akloeckner] and
+ [@emontnemery]!
+- Running Home Assistant Core or Container? [@frenck] added the
+ {% my developer_call_service service="backup.create" %} service to the
+ [backup] integration allowing you to create an automation to create backups
+ on a schedule.
+- [@sisimomo] added Markdown support to Blueprint input descriptions, allow
+ you to add links to e.g., documentation in your Blueprints.
+- [Sonos] now has a favorites sensor, so you can access and use your favorites
+ in your automations, scripts and templates. Thanks [@jjlawren]!
+- [@dmulcahey] added support for configuring the power on state, of devices
+ that have this configuration option, to [ZHA]. Nice!
+- Sensors now have a new device class available: "duration". Thanks, [@bdraco]!
+- The output of [Media Selector] can now be directly used with play media
+ service calls in your Blueprints. Awesome, [@emontnemery]!
+- [@raman325] added frontend support for Sirens, so you can actually turn one
+ on from the UI. 🚨 Alarming news [@raman325]!
+- [@frenck] added an persons attribute to zones, which indicates who is
+ currently in a zone.
+- When customizing the device class / "Show as" of an entity in the UI, you can
+ now set it to nothing/emtpy as well. Thanks, [@zsarnett]!
+- [@rdfurman] Added support to the [Honeywell] Total Connect Comfort (US)
+ integration for outdoor sensors. Awesome!
+- [Philips TV] now provides a switch to turn on/off the "Ambilight+Hue" syncing
+ if your TV model supports that. Thanks, [@bramstroker]!
+
+[@akloeckner]: https://github.com/akloeckner
+[@bdraco]: https://github.com/bdraco
+[@bramstroker]: https://github.com/bramstroker
+[@dmulcahey]: https://github.com/dmulcahey
+[@emontnemery]: https://github.com/emontnemery
+[@frenck]: https://github.com/frenck
+[@jjlawren]: https://github.com/jjlawren
+[@raman325]: https://github.com/raman325
+[@rdfurman]: https://github.com/rdfurman
+[@sisimomo]: https://github.com/sisimomo
+[@zsarnett]: https://github.com/zsarnett
+[backup]: /integrations/backup
+[Honeywell]: /integrations/honeywell
+[Media Selector]: /docs/blueprint/selectors/#media-selector
+[Philips TV]: /integrations/philips_js
+[Sonos]: /integrations/sonos
+[ZHA]: /integrations/zha
+
+## New Integrations
+
+We welcome the following new integrations this release:
+
+- [Meater], added by[@Sotolotl]
+- [QNAP QSW], added by [@Noltari]
+- [SENZ], added by [@milanmeu]
+- [SlimProto (Squeezebox Players)], added by [@marcelveldt]
+- [Trafikverket Ferry], added by [@gjohansson-ST]
+
+[@marcelveldt]: https://github.com/marcelveldt
+[@milanmeu]: https://github.com/milanmeu
+[@Noltari]: https://github.com/Noltari
+[@Sotolotl]: https://github.com/Sotolotl
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[Meater]: /integrations/meater
+[QNAP QSW]: /integrations/qnap_qsw
+[SENZ]: /integrations/senz
+[SlimProto (Squeezebox Players)]: /integrations/slimproto
+[Trafikverket Ferry]: /integrations/trafikverket_ferry
+
+
+## Integrations now available to set up from the UI
+
+The following integrations are now available via the Home Assistant UI:
+
+- [SABnzbd], done by [@shaiu]
+- [SQL], done by [@gjohansson-ST]
+- [Tautulli], done by [@tkdrob]
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[@shaiu]: https://github.com/shaiu
+[@tkdrob]: https://github.com/tkdrob
+[SABnzbd]: /integrations/sabnzbd
+[SQL]: /integrations/sql
+[Tautulli]: /integrations/tautulli
+
+## Need help? Join the community!
+
+Home Assistant has a great community of users who are all more than willing
+to help each other out. So, join us!
+
+Our very active [Discord chat server](/join-chat) is an excellent place to be
+at, and don't forget to join our amazing [forums](https://community.home-assistant.io/).
+
+Found a bug or issue? Please report it in our [issue tracker](https://github.com/home-assistant/core/issues),
+to get it fixed! Or, check [our help page](/help) for guidance for more
+places you can go.
+
+Are you more into email? [Sign-up for our Building the Open Home Newsletter](/newsletter)
+to get the latest news about features, things happening in our community and
+other news about building an Open Home; straight into your inbox.
+
+## Breaking Changes
+
+Below is a listing of the breaking change for this release, per subject or
+integration. Click on one of those to read more about the breaking change
+for that specific item.
+
+{% details "AVM FRITZ!Box Call Monitor" %}
+
+The previously deprecated YAML configuration of theAVM FRITZ!Box Call Monitor
+integration has been removed.
+
+AVM FRITZ!Box Call Monitor is now configured via the UI, any existing YAML
+configuration has been imported in previous releases and can now be safely
+removed from your YAML configuration files.
+
+([@cdce8p] - [#70829]) ([documentation](/integrations/fritzbox_callmonitor))
+
+[@cdce8p]: https://github.com/cdce8p
+[#70829]: https://github.com/home-assistant/core/pull/70829
+
+{% enddetails %}
+
+{% details "AVM FRITZ!Box Tools" %}
+
+The binary sensor entity showing that an update is available for the FRITZ!Box
+firmware has been deprecated and will be removed in Home Assistant 2022.7.
+
+The AVM FRITZ!Box Tools integration now provides an `update` entity as a
+replacement.
+
+([@Mask3007] - [#70096]) ([documentation](/integrations/fritz))
+
+[@Mask3007]: https://github.com/Mask3007
+[#70096]: https://github.com/home-assistant/core/pull/70096
+
+{% enddetails %}
+
+{% details "BMW Connected Drive" %}
+
+All `bmw_connected_drive.*` services are removed (deprecated since 2022.2).
+Please use the new button entities with the `button.press` service instead.
+
+([@rikroe] - [#69808]) ([documentation](/integrations/bmw_connected_drive))
+
+[@rikroe]: https://github.com/rikroe
+[#69808]: https://github.com/home-assistant/core/pull/69808
+
+---
+
+The `button.