Merge branch 'current' into next

CODEOWNERS

@@ -60,6 +60,7 @@ source/_integrations/assist_pipeline.markdown @balloob @synesthesiam
 source/_integrations/asuswrt.markdown @kennedyshead @ollo69
 source/_integrations/atag.markdown @MatsNL
 source/_integrations/aten_pe.markdown @mtdcr
+source/_integrations/atlanticcityelectric.markdown @tronikos
 source/_integrations/atome.markdown @baqs
 source/_integrations/august.markdown @bdraco
 source/_integrations/august_ble.markdown @bdraco
@@ -79,6 +80,7 @@ source/_integrations/baf.markdown @bdraco @jfroy
 source/_integrations/balboa.markdown @garbled1 @natekspencer
 source/_integrations/bayesian.markdown @HarvsG
 source/_integrations/beewi_smartclim.markdown @alemuro
+source/_integrations/bge.markdown @tronikos
 source/_integrations/binary_sensor.markdown @home-assistant/core
 source/_integrations/bizkaibus.markdown @UgaitzEtxebarria
 source/_integrations/blebox.markdown @bbx-a @riokuu
@@ -111,7 +113,7 @@ source/_integrations/button.markdown @home-assistant/core
 source/_integrations/calendar.markdown @home-assistant/core
 source/_integrations/camera.markdown @home-assistant/core
 source/_integrations/cast.markdown @emontnemery
-source/_integrations/cert_expiry.markdown @Cereal2nd @jjlawren
+source/_integrations/cert_expiry.markdown @jjlawren
 source/_integrations/circuit.markdown @braam
 source/_integrations/cisco_ios.markdown @fbradyirl
 source/_integrations/cisco_mobility_express.markdown @fbradyirl
@@ -121,6 +123,7 @@ source/_integrations/cloud.markdown @home-assistant/cloud
 source/_integrations/cloudflare.markdown @ludeeus @ctalkington
 source/_integrations/coinbase.markdown @tombrien
 source/_integrations/color_extractor.markdown @GenericStudent
+source/_integrations/comed.markdown @tronikos
 source/_integrations/comfoconnect.markdown @michaelarnauts
 source/_integrations/command_line.markdown @gjohansson-ST
 source/_integrations/compensation.markdown @Petro31
@@ -143,6 +146,7 @@ source/_integrations/debugpy.markdown @frenck
 source/_integrations/deconz.markdown @Kane610
 source/_integrations/default_config.markdown @home-assistant/core
 source/_integrations/delijn.markdown @bollewolle @Emilv2
+source/_integrations/delmarva.markdown @tronikos
 source/_integrations/deluge.markdown @tkdrob
 source/_integrations/demo.markdown @home-assistant/core
 source/_integrations/denonavr.markdown @ol-iver @starkillerOG
@@ -172,6 +176,7 @@ source/_integrations/dremel_3d_printer.markdown @tkdrob
 source/_integrations/dsmr.markdown @Robbie1221 @frenck
 source/_integrations/dsmr_reader.markdown @depl0y @glodenox
 source/_integrations/dunehd.markdown @bieniu
+source/_integrations/duotecno.markdown @cereal2nd
 source/_integrations/dwd_weather_warnings.markdown @runningman84 @stephan192 @Hummel95 @andarotajo
 source/_integrations/dynalite.markdown @ziv1234
 source/_integrations/easyenergy.markdown @klaasnicolaas
@@ -183,6 +188,7 @@ source/_integrations/efergy.markdown @tkdrob
 source/_integrations/egardia.markdown @jeroenterheerdt
 source/_integrations/eight_sleep.markdown @mezz64 @raman325
 source/_integrations/electrasmart.markdown @jafar-atili
+source/_integrations/electric_kiwi.markdown @mikey0000
 source/_integrations/elgato.markdown @frenck
 source/_integrations/elkm1.markdown @gwww @bdraco
 source/_integrations/elmax.markdown @albertogeniola
@@ -209,6 +215,8 @@ source/_integrations/escea.markdown @lazdavila
 source/_integrations/esera_onewire.markdown @garbled1 @epenet
 source/_integrations/esphome.markdown @OttoWinter @jesserockz @bdraco
 source/_integrations/eufylife_ble.markdown @bdr99
+source/_integrations/event.markdown @home-assistant/core
+source/_integrations/evergy.markdown @tronikos
 source/_integrations/evil_genius_labs.markdown @balloob
 source/_integrations/evohome.markdown @zxdavb
 source/_integrations/ezviz.markdown @RenierM26 @baqs
@@ -245,6 +253,7 @@ source/_integrations/frontend.markdown @home-assistant/frontend
 source/_integrations/frontier_silicon.markdown @wlcrs
 source/_integrations/fully_kiosk.markdown @cgarwood
 source/_integrations/garages_amsterdam.markdown @klaasnicolaas
+source/_integrations/gardena_bluetooth.markdown @elupus
 source/_integrations/gaviota.markdown @starkillerOG
 source/_integrations/gdacs.markdown @exxamalte
 source/_integrations/generic.markdown @davet2001
@@ -509,6 +518,7 @@ source/_integrations/opentherm_gw.markdown @mvn23
 source/_integrations/openuv.markdown @bachya
 source/_integrations/openweathermap.markdown @fabaff @freekode @nzapponi
 source/_integrations/opnsense.markdown @mtreinish
+source/_integrations/opower.markdown @tronikos
 source/_integrations/oralb.markdown @bdraco @Lash-L
 source/_integrations/oru.markdown @bvlaicu
 source/_integrations/otbr.markdown @home-assistant/core
@@ -519,7 +529,11 @@ source/_integrations/panel_custom.markdown @home-assistant/frontend
 source/_integrations/panel_iframe.markdown @home-assistant/frontend
 source/_integrations/pcs_lighting.markdown @gwww
 source/_integrations/peco.markdown @IceBotYT
+source/_integrations/peco_opower.markdown @tronikos
+source/_integrations/pegel_online.markdown @mib1185
+source/_integrations/pepco.markdown @tronikos
 source/_integrations/persistent_notification.markdown @home-assistant/core
+source/_integrations/pge.markdown @tronikos
 source/_integrations/philips_js.markdown @elupus
 source/_integrations/pi_hole.markdown @johnluetke @shenxn
 source/_integrations/picnic.markdown @corneyl
@@ -539,6 +553,7 @@ source/_integrations/prosegur.markdown @dgomes
 source/_integrations/proxmoxve.markdown @jhollowe @Corbeno
 source/_integrations/prusalink.markdown @balloob
 source/_integrations/ps4.markdown @ktnrg45
+source/_integrations/pse.markdown @tronikos
 source/_integrations/pure_energie.markdown @klaasnicolaas
 source/_integrations/purpleair.markdown @bachya
 source/_integrations/push.markdown @dgomes
@@ -566,7 +581,7 @@ source/_integrations/rainmachine.markdown @bachya
 source/_integrations/random.markdown @fabaff
 source/_integrations/rapt_ble.markdown @sairon
 source/_integrations/raven_rock_mfg.markdown @starkillerOG
-source/_integrations/rdw.markdown @frenck
+source/_integrations/rdw.markdown @frenck @joostlek
 source/_integrations/recollect_waste.markdown @bachya
 source/_integrations/recorder.markdown @home-assistant/core
 source/_integrations/rejseplanen.markdown @DarkFox

_config.yml

@@ -109,9 +109,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 2023
-current_minor_version: 7
-current_patch_version: 3
-date_released: 2023-07-21
+current_minor_version: 8
+current_patch_version: 0
+date_released: 2023-08-02
 
 # 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/atlanticcityelectric.markdown

@@ -5,16 +5,16 @@ ha_category:
   - Energy
   - Sensor
 ha_release: 2023.8
-ha_iot_class: Cloud Polling
-ha_codeowners:
-  - '@tronikos'
 ha_domain: atlanticcityelectric
-ha_config_flow: true
-ha_platforms:
-  - sensor
 ha_integration_type: virtual
 ha_supporting_domain: opower
 ha_supporting_integration: Opower
+ha_codeowners:
+  - '@tronikos'
+ha_config_flow: true
+ha_platforms:
+  - sensor
+ha_iot_class: Cloud Polling
 ---
 
 {% include integrations/supported_brand.md %}

source/_integrations/bge.markdown

@@ -5,16 +5,16 @@ ha_category:
   - Energy
   - Sensor
 ha_release: 2023.8
-ha_iot_class: Cloud Polling
-ha_codeowners:
-  - '@tronikos'
 ha_domain: bge
-ha_config_flow: true
-ha_platforms:
-  - sensor
 ha_integration_type: virtual
 ha_supporting_domain: opower
 ha_supporting_integration: Opower
+ha_codeowners:
+  - '@tronikos'
+ha_config_flow: true
+ha_platforms:
+  - sensor
+ha_iot_class: Cloud Polling
 ---
 
 {% include integrations/supported_brand.md %}

source/_integrations/broadlink.markdown

@@ -157,7 +157,7 @@ When the LED blinks for the first time, press the button you want to learn. Then
 
 #### Learned codes storage location
 
-The learned codes are stored in `/configuration/.storage/` in a JSON file called `broadlink_remote_MACADDRESS_codes`. You can open this file with a text editor and copy the codes to set up [custom IR/RF switches](#setting-up-custom-irrf-switches) or to send them as [base64 codes](#sending-a-base64-code), but beware: the files in the .storage folder _should never be edited manually_.
+The learned codes are stored in `/configuration/.storage/` or `/config/.storage/` in a JSON file called `broadlink_remote_MACADDRESS_codes`. You can open this file with a text editor and copy the codes to set up [custom IR/RF switches](#setting-up-custom-irrf-switches) or to send them as [base64 codes](#sending-a-base64-code), but beware: the files in the .storage folder _should never be edited manually_.
 
 ### Sending commands
 

source/_integrations/bsblan.markdown

@@ -13,7 +13,7 @@ ha_domain: bsblan
 ha_platforms:
   - climate
   - diagnostics
-ha_integration_type: integration
+ha_integration_type: device
 ---
 
 This integration integrates [BSBLan](https://github.com/fredlcore/BSB-LAN) devices into Home Assistant.

source/_integrations/cert_expiry.markdown

@@ -7,7 +7,6 @@ ha_release: 0.44
 ha_iot_class: Cloud Polling
 ha_config_flow: true
 ha_codeowners:
-  - '@Cereal2nd'
   - '@jjlawren'
 ha_domain: cert_expiry
 ha_platforms:

source/_integrations/co2signal.markdown

@@ -2,15 +2,15 @@
 title: Electricity Maps
 description: Instructions on how to use the Electricity Maps (formerly known as CO2Signal) data within Home Assistant
 ha_category:
-    - Climate
-    - Energy
-    - Environment
+  - Climate
+  - Energy
+  - Environment
 ha_release: 0.87
 ha_iot_class: Cloud Polling
 ha_domain: co2signal
 ha_platforms:
-    - diagnostics
-    - sensor
+  - diagnostics
+  - sensor
 ha_config_flow: true
 ha_integration_type: integration
 ---

source/_integrations/comed.markdown

@@ -5,16 +5,16 @@ ha_category:
   - Energy
   - Sensor
 ha_release: 2023.8
-ha_iot_class: Cloud Polling
-ha_codeowners:
-  - '@tronikos'
 ha_domain: comed
-ha_config_flow: true
-ha_platforms:
-  - sensor
 ha_integration_type: virtual
 ha_supporting_domain: opower
 ha_supporting_integration: Opower
+ha_codeowners:
+  - '@tronikos'
+ha_config_flow: true
+ha_platforms:
+  - sensor
+ha_iot_class: Cloud Polling
 ---
 
 {% include integrations/supported_brand.md %}

source/_integrations/delmarva.markdown

@@ -5,16 +5,16 @@ ha_category:
   - Energy
   - Sensor
 ha_release: 2023.8
-ha_iot_class: Cloud Polling
-ha_codeowners:
-  - '@tronikos'
 ha_domain: delmarva
-ha_config_flow: true
-ha_platforms:
-  - sensor
 ha_integration_type: virtual
 ha_supporting_domain: opower
 ha_supporting_integration: Opower
+ha_codeowners:
+  - '@tronikos'
+ha_config_flow: true
+ha_platforms:
+  - sensor
+ha_iot_class: Cloud Polling
 ---
 
 {% include integrations/supported_brand.md %}

source/_integrations/demo.markdown

@@ -19,7 +19,9 @@ ha_platforms:
   - camera
   - climate
   - cover
+  - date
   - device_tracker
+  - event
   - fan
   - geo_location
   - humidifier
@@ -35,13 +37,12 @@ ha_platforms:
   - stt
   - switch
   - text
+  - time
   - tts
   - update
   - vacuum
   - water_heater
   - weather
-  - date
-  - time
 ha_integration_type: integration
 ---
 

source/_integrations/duotecno.markdown

@@ -7,12 +7,12 @@ ha_iot_class: Local Push
 ha_release: '2023.8'
 ha_config_flow: true
 ha_codeowners:
-  - '@Cereal2nd'
+  - '@cereal2nd'
 ha_domain: duotecno
 ha_platforms:
-  - switch
   - cover
-ha_integration_type: hub
+  - switch
+ha_integration_type: integration
 ---
 
 The Duotecno integration can be used to control [Duotecno](https://www.duotecno.be/) nodes in Home Assistant.

source/_integrations/electric_kiwi.markdown

@@ -3,7 +3,7 @@ title: Electric Kiwi
 description: Instructions on how to set up the Electric Kiwi service in Home Assistant.
 ha_category:
   - Energy
-ha_release: "2023.8"
+ha_release: '2023.8'
 ha_iot_class: Cloud Polling
 ha_codeowners:
   - '@mikey0000'
@@ -11,10 +11,10 @@ ha_domain: electric_kiwi
 ha_config_flow: true
 ha_platforms:
   - sensor
-ha_integration_type: service
+ha_integration_type: hub
 ---
 
-[Electric Kiwi](https://www.electrickiwi.co.nz/) is an independent power and broadband company in New Zealand, offering variable rates for peak, shoulder, and off-peak pricing with a selectable hour of free power. This integration uses the official [Electric Kiwi API](https://developer.electrickiwi.co.nz) to get your account balance and show and select the hour of free power. 
+[Electric Kiwi](https://www.electrickiwi.co.nz/) is an independent power and broadband company in New Zealand, offering variable rates for peak, shoulder, and off-peak pricing with a selectable hour of free power. This integration uses the official [Electric Kiwi API](https://developer.electrickiwi.co.nz) to show the hour of free power. 
 
 {% include integrations/config_flow.md %}
 

source/_integrations/event.mqtt.markdown

@@ -58,14 +58,6 @@ availability_topic:
   description: The MQTT topic subscribed to receive availability (online/offline) updates. Must not be used together with `availability`.
   required: false
   type: string
-command_template:
-  description: Defines a [template](/docs/configuration/templating/#using-templates-with-the-mqtt-integration) to generate the payload to send to `command_topic`.
-  required: false
-  type: template
-command_topic:
-  description: The MQTT topic to publish commands to trigger the event.
-  required: false
-  type: string
 device:
   description: "Information about the device this event is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
   required: false

source/_integrations/evergy.markdown

@@ -5,16 +5,16 @@ ha_category:
   - Energy
   - Sensor
 ha_release: 2023.8
-ha_iot_class: Cloud Polling
-ha_codeowners:
-  - '@tronikos'
 ha_domain: evergy
-ha_config_flow: true
-ha_platforms:
-  - sensor
 ha_integration_type: virtual
 ha_supporting_domain: opower
 ha_supporting_integration: Opower
+ha_codeowners:
+  - '@tronikos'
+ha_config_flow: true
+ha_platforms:
+  - sensor
+ha_iot_class: Cloud Polling
 ---
 
 {% include integrations/supported_brand.md %}

source/_integrations/ezviz.markdown

@@ -12,9 +12,11 @@ ha_codeowners:
   - '@baqs'
 ha_config_flow: true
 ha_platforms:
+  - alarm_control_panel
   - binary_sensor
   - button
   - camera
+  - image
   - light
   - number
   - select

source/_integrations/freebox.markdown

@@ -15,11 +15,11 @@ ha_codeowners:
 ha_config_flow: true
 ha_domain: freebox
 ha_platforms:
+  - binary_sensor
   - button
   - camera
   - device_tracker
   - sensor
-  - binary_sensor
   - switch
 ha_zeroconf: true
 ha_integration_type: integration

source/_integrations/fritz.markdown

@@ -21,10 +21,10 @@ ha_platforms:
   - button
   - device_tracker
   - diagnostics
+  - image
   - sensor
   - switch
   - update
-  - image
 ha_ssdp: true
 ha_integration_type: integration
 ---

source/_integrations/gardena_bluetooth.markdown

@@ -14,9 +14,11 @@ ha_domain: gardena_bluetooth
 ha_config_flow: true
 ha_platforms:
   - binary_sensor
+  - button
   - number
   - sensor
   - switch
+ha_integration_type: integration
 ---
 
 The Gardena Bluetooth integration allows users to integrate their [Gardena Smart](https://www.gardena.com/int/products/smart/) devices using Bluetooth into Home Assistant.

source/_integrations/google_assistant_sdk.markdown

@@ -107,6 +107,8 @@ The easiest way to check if the integration is working is to check [My Google Ac
 - If you see the issued commands in [My Google Activity](https://myactivity.google.com/myactivity), the integration is working fine. If the commands don't have the expected outcome, don't open an issue in the Home Assistant Core project or the [underlying library](https://github.com/tronikos/gassist_text). You should instead report the issue directly to Google [here](https://github.com/googlesamples/assistant-sdk-python/issues). Examples of known Google Assistant API issues:
   - Media playback commands (other than play news, play podcast, play white noise, or play rain sounds) don't work.
   - Routines don't work.
+  - Broadcast doesn't work with IPv6.
+  - Broadcast to specific rooms often doesn't work for non-English languages.
 
 ## Configuration
 

source/_integrations/homekit_controller.markdown

@@ -31,6 +31,7 @@ ha_platforms:
   - climate
   - cover
   - diagnostics
+  - event
   - fan
   - humidifier
   - light

source/_integrations/hue.markdown

@@ -17,6 +17,7 @@ ha_homekit: true
 ha_platforms:
   - binary_sensor
   - diagnostics
+  - event
   - light
   - scene
   - sensor

source/_integrations/kitchen_sink.markdown

@@ -10,9 +10,10 @@ ha_codeowners:
 ha_domain: kitchen_sink
 ha_iot_class: Calculated
 ha_platforms:
+  - image
   - lock
   - sensor
-  - image
+  - weather
 ha_integration_type: integration
 ---
 

source/_integrations/knx.markdown

@@ -44,8 +44,8 @@ ha_platforms:
   - sensor
   - switch
   - text
-  - weather
   - time
+  - weather
 ha_config_flow: true
 ha_integration_type: hub
 ---
@@ -73,6 +73,10 @@ There is currently support for the following device types within Home Assistant:
 - [Time](#time)
 - [Weather](#weather)
 
+## Free KNX online training
+
+As a Home Assistant KNX user, you can start a FREE KNX online training and get a discounted ETS Home license on the [KNX website](https://www.knx.org/knx-en/for-your-home/home-assistant/).
+
 {% include integrations/config_flow.md %}
 
 ## Basic Configuration

source/_integrations/litterrobot.markdown

@@ -22,9 +22,9 @@ ha_platforms:
   - select
   - sensor
   - switch
+  - time
   - update
   - vacuum
-  - time
 ha_integration_type: hub
 ---
 

source/_integrations/loqed.markdown

@@ -10,6 +10,7 @@ ha_codeowners:
 ha_domain: loqed
 ha_platforms:
   - lock
+  - sensor
 ha_config_flow: true
 ha_integration_type: integration
 ha_zeroconf: true

source/_integrations/matter.markdown

@@ -20,6 +20,7 @@ ha_platforms:
   - climate
   - cover
   - diagnostics
+  - event
   - light
   - lock
   - sensor

source/_integrations/microsoft.markdown

@@ -1,5 +1,5 @@
 ---
-title: Microsoft text-to-speech (TTS)
+title: Microsoft Text-to-Speech (TTS)
 description: Instructions on how to set up Microsoft text-to-speech with Home Assistant.
 ha_category:
   - Text-to-speech

source/_integrations/mqtt.markdown

@@ -21,8 +21,10 @@ ha_platforms:
   - cover
   - device_tracker
   - diagnostics
+  - event
   - fan
   - humidifier
+  - image
   - light
   - lock
   - number
@@ -31,12 +33,11 @@ ha_platforms:
   - sensor
   - siren
   - switch
-  - text
   - tag
+  - text
   - update
   - vacuum
   - water_heater
-  - image
 ha_integration_type: integration
 ha_quality_scale: gold
 ---

source/_integrations/onvif.markdown

@@ -14,6 +14,7 @@ ha_platforms:
   - button
   - camera
   - diagnostics
+  - event
   - sensor
   - switch
 ha_integration_type: integration

source/_integrations/opensky.markdown

@@ -11,6 +11,7 @@ ha_platforms:
 ha_integration_type: integration
 ha_codeowners:
   - '@joostlek'
+ha_config_flow: true
 ---
 
 The OpenSky integration allows one to track overhead flights in a given region. It uses crowd-sourced data from the [OpenSky Network](https://opensky-network.org/) public API. It will also fire Home Assistant events when flights enter and exit the defined region.

source/_integrations/opower.markdown

@@ -68,10 +68,12 @@ For electricity:
 
 1. Select **Add consumption** for the **Electricity grid**.
 2. Select **Opower {utility name} elec {account number} consumption** for the **consumed energy**.
-3. Select **Opower {utility name} elec {account number} cost** for the **entity with the total costs**.
+3. Select the radio button to **Use an entity tracking the total costs**.
+4. Select **Opower {utility name} elec {account number} cost** for the **entity with the total costs**.
 
 For gas:
 
 1. Select **Add gas source** for the **Gas consumption**.
 2. Select **Opower {utility name} gas {account number} consumption** for the **gas usage**.
-3. Select **Opower {utility name} gas {account number} cost** for the **entity with the total costs**.
+3. Select the radio button to **Use an entity tracking the total costs**.
+4. Select **Opower {utility name} gas {account number} cost** for the **entity with the total costs**.

source/_integrations/peco_opower.markdown

@@ -5,16 +5,16 @@ ha_category:
   - Energy
   - Sensor
 ha_release: 2023.8
-ha_iot_class: Cloud Polling
-ha_codeowners:
-  - '@tronikos'
 ha_domain: peco_opower
-ha_config_flow: true
-ha_platforms:
-  - sensor
 ha_integration_type: virtual
 ha_supporting_domain: opower
 ha_supporting_integration: Opower
+ha_codeowners:
+  - '@tronikos'
+ha_config_flow: true
+ha_platforms:
+  - sensor
+ha_iot_class: Cloud Polling
 ---
 
 {% include integrations/supported_brand.md %}

source/_integrations/pegel_online.markdown

@@ -7,7 +7,7 @@ ha_category:
 ha_release: 2023.8
 ha_config_flow: true
 ha_iot_class: Cloud Polling
-ha_domain: 'pegel_online'
+ha_domain: pegel_online
 ha_platforms:
   - sensor
 ha_codeowners:

source/_integrations/pepco.markdown

@@ -5,16 +5,16 @@ ha_category:
   - Energy
   - Sensor
 ha_release: 2023.8
-ha_iot_class: Cloud Polling
-ha_codeowners:
-  - '@tronikos'
 ha_domain: pepco
-ha_config_flow: true
-ha_platforms:
-  - sensor
 ha_integration_type: virtual
 ha_supporting_domain: opower
 ha_supporting_integration: Opower
+ha_codeowners:
+  - '@tronikos'
+ha_config_flow: true
+ha_platforms:
+  - sensor
+ha_iot_class: Cloud Polling
 ---
 
 {% include integrations/supported_brand.md %}

source/_integrations/pge.markdown

@@ -5,16 +5,16 @@ ha_category:
   - Energy
   - Sensor
 ha_release: 2023.8
-ha_iot_class: Cloud Polling
-ha_codeowners:
-  - '@tronikos'
 ha_domain: pge
-ha_config_flow: true
-ha_platforms:
-  - sensor
 ha_integration_type: virtual
 ha_supporting_domain: opower
 ha_supporting_integration: Opower
+ha_codeowners:
+  - '@tronikos'
+ha_config_flow: true
+ha_platforms:
+  - sensor
+ha_iot_class: Cloud Polling
 ---
 
 {% include integrations/supported_brand.md %}

source/_integrations/pse.markdown

@@ -5,16 +5,16 @@ ha_category:
   - Energy
   - Sensor
 ha_release: 2023.8
-ha_iot_class: Cloud Polling
-ha_codeowners:
-  - '@tronikos'
 ha_domain: pse
-ha_config_flow: true
-ha_platforms:
-  - sensor
 ha_integration_type: virtual
 ha_supporting_domain: opower
 ha_supporting_integration: Opower
+ha_codeowners:
+  - '@tronikos'
+ha_config_flow: true
+ha_platforms:
+  - sensor
+ha_iot_class: Cloud Polling
 ---
 
 {% include integrations/supported_brand.md %}

source/_integrations/rdw.markdown

@@ -11,6 +11,7 @@ ha_config_flow: true
 ha_quality_scale: platinum
 ha_codeowners:
   - '@frenck'
+  - '@joostlek'
 ha_domain: rdw
 ha_platforms:
   - binary_sensor

source/_integrations/reolink.markdown

@@ -17,6 +17,7 @@ ha_platforms:
   - light
   - number
   - select
+  - sensor
   - siren
   - switch
   - update

source/_integrations/roborock.markdown

@@ -17,9 +17,11 @@ ha_codeowners:
 ha_domain: roborock
 ha_platforms:
   - diagnostics
+  - number
   - select
   - sensor
   - switch
+  - time
   - vacuum
 ha_integration_type: integration
 ---
@@ -72,7 +74,7 @@ data:
     - segments:
         - 22
         - 23
-    - repeat: 1
+      repeat: 2
 target:
   entity_id: vacuum.s7_roborock
 

source/_integrations/scene.markdown

@@ -1,5 +1,5 @@
 ---
-title: Scene
+title: Scenes
 description: Instructions on how to setup scenes within Home Assistant.
 ha_category:
   - Organization

source/_integrations/scrape.markdown

@@ -283,4 +283,3 @@ scrape:
         select: "div.nk-tb-item:nth-child(3) > div:nth-child(3) > span:nth-child(1) > span:nth-child(1)"
 
 ```
-

source/_integrations/template.markdown

@@ -22,6 +22,7 @@ ha_platforms:
   - button
   - cover
   - fan
+  - image
   - light
   - lock
   - number
@@ -30,7 +31,6 @@ ha_platforms:
   - switch
   - vacuum
   - weather
-  - image
 ha_integration_type: integration
 ---
 

source/_integrations/unifi.markdown

@@ -19,6 +19,7 @@ ha_ssdp: true
 ha_platforms:
   - device_tracker
   - diagnostics
+  - image
   - sensor
   - switch
   - update

source/_integrations/unifiprotect.markdown

@@ -22,8 +22,8 @@ ha_iot_class: Local Push
 ha_config_flow: true
 ha_quality_scale: platinum
 ha_codeowners:
-  - "@AngellusMortis"
-  - "@bdraco"
+  - '@AngellusMortis'
+  - '@bdraco'
 ha_domain: unifiprotect
 ha_platforms:
   - binary_sensor

source/_integrations/youtube.markdown

@@ -10,6 +10,7 @@ ha_codeowners:
   - '@joostlek'
 ha_domain: youtube
 ha_platforms:
+  - diagnostics
   - sensor
 ha_integration_type: service
 ---

source/_integrations/zodiac.markdown

@@ -12,6 +12,7 @@ ha_domain: zodiac
 ha_platforms:
   - sensor
 ha_integration_type: integration
+ha_config_flow: true
 ---
 
 The Zodiac integration tracks the current zodiac sign.

source/_posts/2023-08-02-release-20238.markdown

@@ -0,0 +1,548 @@
+---
+layout: post
+title: "2023.8: Translated services, events, and wildcards!"
+description: "Sentence triggers can now contain wildcards, a brand new event entity, all services are now translated into your language, generate images with OpenAI's DALL-E using Assist, and more!"
+date: 2023-08-02 00:00:00
+date_formatted: "August 2, 2023"
+author: Franck Nijhof
+author_twitter: frenck
+comments: true
+categories:
+  - Release-Notes
+  - Core
+og_image: /images/blog/2023-08/social.png
+---
+
+<a href='/integrations/#version/2023.8'><img src='/images/blog/2023-08/social.png' style='border: 0;box-shadow: none;'></a>
+
+Home Assistant Core 2023.8! 🎉
+
+Another month, another fine release of Home Assistant! This release is a bit more
+conservative after two absolutely packed releases in [June](/blog/2023/06/30/release-20236/)
+and [July](/blog/2023/06/07/release-20236/). Many of us are enjoying summer holidays 🏖️.
+
+Pretty much all features in this release are absolutely amazing, and it is hard
+to pick a favorite. Great translation improvements that help with the user
+experience, a new entity to capture events from things like remotes, and the
+new Assist features are, again, mind-blowing!
+
+Talking about Assist, have you seen the blog on [Year of the Voice - Chapter 3](/blog/2023/07/20/year-of-the-voice-chapter-3/)?
+Or, check [the live stream recording on YouTube](https://www.youtube.com/watch?v=sXzItFksYFA),
+where the new features have been demonstrated.
+
+Some new integrations have been added too. Most notably [Opower](/integrations/opower)!
+This integration can pull in energy usage data from many utility companies in
+the United States. For example, it supports [PG&E](/integrations/pge),
+[ComEd](/integrations/comed), [BGE](/integrations/bge), and many more! ⚡️
+Very good news for all our American friends!
+
+Enjoy the release!
+
+../Frenck
+
+<!--more-->
+
+- [Translated services](#translated-services)
+- [Introducing the event entity](#introducing-the-event-entity)
+- [Improving the first experience with Home Assistant](#improving-the-first-experience-with-home-assistant)
+- [Add items to your shopping list using Assist](#add-items-to-your-shopping-list-using-assist)
+- [Wildcard support for sentence triggers](#wildcard-support-for-sentence-triggers)
+- [Generate an image with OpenAI's DALL-E](#generate-an-image-with-openais-dall-e)
+- [Condition selector](#condition-selector)
+- [Other noteworthy changes](#other-noteworthy-changes)
+- [New integrations](#new-integrations)
+- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
+- [Need help? Join the community!](#need-help-join-the-community)
+- [Breaking changes](#breaking-changes)
+- [Farewell to the following](#farewell-to-the-following)
+- [All changes](#all-changes)
+
+Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=4EpUgLW03Pg)
+2 August 2023, at 12:00 PDT / 21:00 CEST!
+
+<lite-youtube videoid="4EpUgLW03Pg" videotitle="Home Assistant 2023.8 Release Party"></lite-youtube>
+
+## Translated services
+
+All services in Home Assistant are now translatable! 🌎
+
+Services are the actions you can call, like turning on a light. This was one of
+the bigger parts of Home Assistant that still was only available in English.
+Odd, as the Home Assistant interface can be used in 60+ languages!
+
+In this release, translations for these services have been added to drastically
+improve the experience when English is not your primary language. For example,
+when you use the Dutch language (as used in the screenshot below), the service
+to turn on a light is now also translated into Dutch.
+
+<img class="no-shadow" src='/images/blog/2023-08/translated-services.png' alt='Screenshot showing the Home Assistant interface in the Dutch language, showcasing the translations for service calls.'>
+
+A big step forward! Implementing this change has resulted in a substantial
+increase in the number of translations. They have doubled! 😅
+
+Because of that, translating all services might take some time; however… 
+You can help! You don’t have to be a developer to help with this; you can do this
+from the comfort of your browser. Check out our documentation on
+[how to contribute translations](https://developers.home-assistant.io/docs/translations).
+
+## Introducing the event entity
+
+Events are signals that are emitted when something happens, for example, when
+someone presses a physical button like a doorbell or when a button on a remote
+control is pressed.
+
+If you have ever tried to work with events in Home Assistant, you probably
+noticed that it was not the easiest thing to do. You need to know the event name,
+and then you need to know the data that is being sent with it. Before you know it,
+you'll start fiddling with the developer tools to figure out what is going on.
+
+To make this all easier, we are introducing a new entity type in this release:
+[The event entity](/integrations/event).
+
+The event entity can capture these events in the physical world and makes them
+available in Home Assistant as an entity. Take for example, this Hue remote:
+
+<img class="no-shadow" src='/images/blog/2023-08/events-hue-dimmer-switch.png' alt='Screenshot showing the new event entities provided by a Philips Hue remote.'>
+
+The beauty of the event entity is that they can be used like any other entity
+in Home Assistant: They will show up in the UI, can be used directly in the
+automations editor, and provide historical information in the logbook.
+
+Besides [Matter](/integrations/matter), the event entity is also supported by
+[HomeKit Devices](/integrations/homekit_controller), [MQTT](/integrations/mqtt),
+and [Philips Hue](/integrations/hue). We expect to see more integrations
+supporting this new entity type soon.
+
+## Improving the first experience with Home Assistant
+
+Onboarding is a user's first experience with Home Assistant. The onboarding
+screens are the first you see, and steps you take when you access Home Assistant
+for the first time, setting up things like your account and language preferences.
+The goal is to ensure this process is seamless, which is why we've made
+improvements to the onboarding experience.
+
+To achieve this, we have implemented a search field on the map during
+onboarding. Instead of endlessly dragging the pin on the map around,
+you can now easily search for your location.
+
+<img class="no-shadow" src='/images/blog/2023-08/onboarding-openstreetmap.png' alt='Screenshot showing you can now enter your address to quickly find your location on the map.'>
+
+This is powered by [OpenStreetMap](https://www.openstreetmap.org/) ❤️
+
+## Add items to your shopping list using Assist
+
+What if you could ask [Assist](/integrations/assist) to add items to your
+Home Assistant [shopping list](/integrations/shopping_list)? Well, now you can!
+
+> Add milk to my shopping list!
+
+<img class="no-shadow" src='/images/blog/2023-08/assist-shopping-list.png' alt='Screenshot showing asking assist to add milk to the shopping list.'>
+
+In case you are wondering, the shopping list integration adds a handy page to
+your Home Assistant interface to which everyone in your household can add items.
+It is a great way to keep track of what you need to buy, and now you can
+add items to it with your voice using Assist!
+
+<img class="no-shadow" src='/images/blog/2023-08/shopping-list.png' alt='Screenshot showing the shopping list integration in Home Assistant.'>
+
+To be able to use this feature, you need to have the shopping list integration
+set up, which is as easy as clicking the My Home Assistant button below:
+
+{% my config_flow_start badge domain="shopping_list" %}
+
+## Generate an image with OpenAI's DALL-E
+
+In the last release, we added [the ability for services to respond with data](/blog/2023/07/05/release-20237/#services-can-now-respond),
+and now we added a service that allows you to generate an image using
+[OpenAI's DALL-E](https://openai.com/dall-e-2).
+
+All you need is to set up the [OpenAI conversation agent](/integrations/openai_conversation)
+integration on your instance, and you will get a new service:
+{% my developer_call_service service="openai_conversation.generate_image" %}.
+
+Call this service describing the image you'd like the AI to generate, and
+it will respond with an image URL you can use in your automations.
+
+<img class="no-shadow" src='/images/blog/2023-08/openai-generate-image.png' alt='Screenshot showing the new generate image service with DALL-E from OpenAI, asking to generate an image of an astronaut riding a unicorn.'>
+
+You could, for example, use this to generate an image of a city that matches
+the weather conditions outside of your home, let the AI generate an image
+about the latest news headline to show on your dashboard, or maybe generate
+a fun image of someone putting out garbage on garbage day.
+
+{% my developer_call_service badge service="openai_conversation.generate_image" %}
+
+You could even combine it with the wildcard support for sentence triggers so you
+could ask Home Assistant to generate an image using your voice...
+
+## Wildcard support for sentence triggers
+
+[Sentence triggers](/docs/automation/trigger/#sentence-wildcards) now support
+wildcards! This means you can now partially match a sentence, and use the
+matched part in your actions. This is what powers the above
+[shopping list feature](#add-items-to-your-shopping-list-using-assist)
+too, and it can be used for many other things as well.
+
+You could, for example, create a sentence trigger that matches when you say:
+
+> Play the white album by the Beatles
+
+Using the wildcard support, you can get the album and artist name from the spoken
+sentence and use those in your actions. To trigger on the above example sentence,
+you would use the following command in your sentence trigger:
+
+<img class="no-shadow" src='/images/blog/2023-08/sentence-trigger-wildcard-music.png' alt='Screenshot showing an automation that uses a sentence trigger that has wildcards in it.'>
+
+This will make the `album` and `artist` available as trigger variables that you
+can use in your actions; for example, to start playing the music requested.
+
+These wildcards are interesting and open up a lot of possibilities!
+[Read more about sentence triggers in our documentation](/docs/automation/trigger/#sentence-trigger).
+
+[JLo] realized he could use these wildcards, combined with the new
+[generate image service](#generate-an-image-with-openais-dall-e), to let
+Home Assistant generate an image and show it on his Chrome Cast-enabled device
+just by using his voice! 😎 You could ask it:
+
+> Show me a picture of an astronaut riding a unicorn!
+
+He put this together in an automation blueprint, which you can use to do the
+same thing in your own Home Assistant instance:
+
+<img class="no-shadow" src='/images/blog/2023-08/assist-wildcard-dall-e-blueprint.png' alt='Screenshot showing how the blueprint by JLo looks like in Home Assistant.'>
+
+Provide the sentence you like to trigger on and the media player you want to
+show the image at, and you're good to go! You can import his blueprint using
+the My Home Assistant button below:
+
+{% my blueprint_import badge blueprint_url="https://www.home-assistant.io/blueprints/blog/2023-08/cast_dall_e.yaml" %}
+
+[JLo]: https://github.com/jlpouffier
+
+## Condition selector
+
+A new selector is available for use in, for example, blueprints:
+[The condition selector](/docs/blueprint/selectors/#condition-selector).
+
+This selector takes and shows the condition part of the automation editor,
+and allows blueprint creators to use a user-provided condition in their
+blueprinted automations and scripts.
+
+<p class='img'>
+<img src='/images/blog/2023-08/condition-selector.png'></a>
+This blueprint allows one to set a custom condition using the new condition selector.
+</p>
+
+## Other noteworthy changes
+
+There are many more improvements in this release; here are some of the other
+noteworthy changes this release:
+
+- Tons of performance upgrades again this month (thanks [@bdraco]), these
+  include a much faster ingress experience when visiting add-on web interfaces. 🚀
+- [@emontnemery] added filters to many of the services Home Assistant provides,
+  meaning only options relevant to the entity you are calling the service on
+  will be shown in the UI. Nice!
+- CO2Signal changed its name to [Electricity Maps]. The integration
+  has been renamed to match that. Thanks, [@madsnedergaard]!
+- [@Lash-L] keeps extending the [Roborock] integration, adding many new entities
+  in this release. This includes an error sensor, volume controls,
+  and DnD setting times. Awesome!
+- [EZVIZ] received a big update, adding support for alarm control panels, buttons,
+  and select entities. Thanks [@RenierM26]!
+- [@farmio] added support for adding [date] and [date/time] entities to [KNX]! Great!
+- The [Xiaomi BLE] now supports the MiScale (V1 and V2). Thanks, [@Ernst79]!
+- [UniFi Network] now has controls to turn an UniFi WLAN on and off and added
+  image entities for QR codes for WLAN access. Thanks, [@Kane610]!
+
+
+[@bdraco]: https://github.com/bdraco
+[@emontnemery]: https://github.com/emontnemery
+[@Ernst79]: https://github.com/Ernst79
+[@farmio]: https://github.com/farmio
+[@Kane610]:https://github.com/Kane610
+[@Lash-L]: https://github.com/Lash-L
+[@madsnedergaard]: https://github.com/madsnedergaard
+[@RenierM26]:https://github.com/RenierM26
+[date]: /integrations/date
+[date/time]: /integrations/datetime
+[Electricity Maps]: /integrations/co2signal
+[EZVIZ]: /integrations/ezviz
+[KNX]: /integrations/knx
+[UniFi Network]: /integrations/unifi
+[Xiaomi BLE]: /integrations/xiaomi_ble
+[Roborock]: /integrations/roborock
+
+## New integrations
+
+We welcome the following new integrations in this release:
+
+- **[Electric Kiwi]**, added by [@mikey0000]<br />
+  Integrate with the independent power and broadband company [Electric Kiwi](https://www.electrickiwi.co.nz/) from New Zealand.
+- **[Event]**, added by [@frenck]<br />
+  A new event entity that other integrations can provide to show detected events in the physical world.
+- **[Duotecno]**, added by [@Cereal2nd]<br />
+  Integrate with the [Duotecno](https://www.duotecno.be/) nodes.
+- **[Gardena Bluetooth]**, added by [@elupus]<br />
+  Integrate your [Gardena Smart](https://www.gardena.com/int/products/smart/) devices using Bluetooth.
+- **[Opower]**, added by [@tronikos]<br />
+  Read out energy information from utilities that use [Opower](https://www.oracle.com/industries/utilities/opower-energy-efficiency/).
+  See the virtual integrations below for which utility providers those are.
+- **[PEGELONLINE]**, added by [@mib1185]<br />
+  Provides water level sensors from the [German Federal Waterways and Shipping Administration](https://www.pegelonline.wsv.de/).
+
+This release also has a new virtual integration. Virtual integrations
+are stubs that are handled by other (existing) integrations to help with
+findability. These are new:
+
+- **[Atlantic City Electric]** provided by [Opower]
+- **[Baltimore Gas and Electric (BGE)]** provided by [Opower]
+- **[Commonwealth Edison (ComEd)]** provided by [Opower]
+- **[Delmarva Power]** provided by [Opower]
+- **[Evergy]** provided by [Opower]
+- **[Pacific Gas & Electric (PG&E)]** provided by [Opower]
+- **[PECO Energy Company (PECO)]** provided by [Opower]
+- **[Potomac Electric Power Company (Pepco)]** provided by [Opower]
+- **[Puget Sound Energy (PSE)]** provided by [Opower]
+
+[@Cereal2nd]: https://github.com/Cereal2nd
+[@elupus]: https://github.com/elupus
+[@frenck]: https://github.com/frenck
+[@mib1185]: https://github.com/mib1185
+[@mikey0000]: https://github.com/mikey0000
+[@tronikos]: https://github.com/tronikos
+[Atlantic City Electric]: /integrations/atlanticcityelectric
+[Baltimore Gas and Electric (BGE)]: /integrations/bge
+[Commonwealth Edison (ComEd)]: /integrations/comed
+[Delmarva Power]: /integrations/delmarva
+[Duotecno]: /integrations/duotecno
+[Electric Kiwi]: /integrations/electric_kiwi
+[Event]: /integrations/event
+[Evergy]: /integrations/evergy
+[Gardena Bluetooth]: /integrations/gardena_bluetooth
+[Opower]: /integrations/opower
+[Pacific Gas & Electric (PG&E)]: /integrations/pge
+[PECO Energy Company (PECO)]: /integrations/peco_opower
+[PEGELONLINE]: /integrations/pegel_online
+[Potomac Electric Power Company (Pepco)]: /integrations/pepco
+[Puget Sound Energy (PSE)]: /integrations/pse
+
+## Integrations now available to set up from the UI
+
+The following integrations are now available via the Home Assistant UI:
+
+- **[OpenSky]**, done by [@joostlek]
+- **[Zodiac]**, done by [@joostlek]
+
+[@joostlek]: https://github.com/jooostlek
+[OpenSky]: /integrations/opensky
+[Zodiac]: /integrations/zodiac
+
+## 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
+
+{% details "Python 3.10 support has been removed" %}
+
+Python 3.10 support has previously been deprecated and has now been removed.
+Home Assistant now requires Python 3.11 to run.
+
+You don't have to do anything if you are using Home Assistant OS,
+Home Assistant Container, or Home Assistant Supervised installation method.
+In those cases, we handle this all for you.
+
+Your system has been using Python 3.11 for quite some time already.
+
+([@frenck] - [#97007])
+
+[@frenck]: https://github.com/frenck
+[#97007]: https://github.com/home-assistant/core/pull/97007
+
+{% enddetails %}
+
+
+{% details "Discovery" %}
+
+The legacy discovery integration has been removed. This only affects the
+automatic discovery of Enigma2, Yamaha Network Receivers, and Bluesound.
+
+These can still be manually configured as per usual.
+
+Note this is for our very, very old discovery logic. This does not affect the
+discovery of any other integration/device/service.
+
+If you still have `discovery:` listed in your YAML configuration, you can
+safely remove it.
+
+([@frenck] - [#96856])
+
+[@frenck]: https://github.com/frenck
+[#96856]: https://github.com/home-assistant/core/pull/96856
+
+{% enddetails %}
+
+{% details "Ecovacs" %}
+
+The Ecovacs integration has been migrated to the new "StateVacuumEntity"
+under the hood.
+
+The states of the vacuum entity now report not only on or off,
+instead `cleaning`, `paused`, `docked` (_implicit mean charging_),
+`returning` (_to base_), `idle` and `error`. Further, the actions `turn_on`
+(_start cleaning_), and `turn_off` (_stop cleaning and return to base_) were
+superseded by three single actions `start`, `stop` and `return_to_base`.
+
+([@mib1185] - [#95920]) ([documentation](/integrations/ecovacs))
+
+[@mib1185]: https://github.com/mib1185
+[#95920]: https://github.com/home-assistant/core/pull/95920
+
+{% enddetails %}
+
+{% details "MQTT" %}
+
+It's no longer allowed for an MQTT RGB light without a `brighness_state_topic`
+to report an RGB value of `RGB=0,0,0`. The reason is that for such lights,
+the light's brightness is derived from the RGB value, and an RGB value
+of `RGB=0,0,0` corresponds to a brightness of 0 which is not allowed.
+
+In case an MQTT RGB light without a `brighness_state_topic` reports `0,0,0`
+for R, G, and B, that update will be ignored.
+
+([@jbouwh] - [#96286]) ([documentation](/integrations/mqtt))
+
+[@jbouwh]: https://github.com/jbouwh
+[#96286]: https://github.com/home-assistant/core/pull/96286
+
+---
+
+The MQTT climate `CONF_POWER_STATE_TOPIC` and `CONF_POWER_STATE_TEMPLATE` were
+deprecated in HA Core 2023.2.0 and are now removed. Please remove these options
+from your configuration. The options were not implemented but will break your
+MQTT configuration if they are still present in your config.
+
+([@jbouwh] - [#96771]) ([documentation](/integrations/mqtt))
+
+[@jbouwh]: https://github.com/jbouwh
+[#96771]: https://github.com/home-assistant/core/pull/96771
+
+---
+
+The way MQTT entities are named and how device configuration can be shared
+between discovered entities has changed.
+
+**Sharing of device configuration**
+
+Discovered MQTT entities can share device configuration, meaning one entity
+can include the full device configuration, and other entities can link to that
+device by only setting mandatory fields.
+
+The mandatory fields were previously limited to at least one of
+`connection` and `identifiers`, but have now been extended to at least
+one of `connection` and `identifiers` as well as the `name`.
+
+**Naming of MQTT entities**
+
+The naming of MQTT entities has been changed to be aligned with the
+[entity naming guidelines](https://developers.home-assistant.io/docs/core/entity/#entity-naming):
+
+- The `has_entity_name` entity will be set to `True` on all MQTT entities.
+- This means any MQTT entity which is part of a device will [automatically have its `friendly_name` attribute prefixed with the device name](https://developers.home-assistant.io/docs/core/entity/#has_entity_name-true-mandatory-for-new-integrations).
+- Unnamed `binary_sensor`, `button`, `event`, `number`, and `sensor` entities will
+  now be named by their device class instead of being named "MQTT binary sensor" etc.
+- It's now allowed to set an MQTT entity's name to `None` to mark it as the
+  main feature of a device.
+
+([@jbouwh] - [#95159]) ([documentation](/integrations/mqtt))
+
+[@jbouwh]: https://github.com/jbouwh
+[#95159]: https://github.com/home-assistant/core/pull/95159
+
+{% enddetails %}
+
+{% details "Philips Dynalite" %}
+
+The Dynalite configuration panel, which previously was on the Home Assistant
+sidebar, has moved. It can now be accessed via the integration page in
+**Settings** -> **Device & services** -> **Dynalite** -> **Configure**.
+
+([@frenck] - [#95920]) ([documentation](/integrations/dynalite))
+
+[@frenck]: https://github.com/frenck
+[#96853]: https://github.com/home-assistant/core/pull/96853
+
+{% enddetails %}
+
+{% details "Renson" %}
+
+The state values of the Reason Ventilation integration have been changed to
+be more consistent with other integrations and are now lowercase. Additionally,
+it can now provide translations for the state values in the UI.
+
+This means that the following state values have changed:
+
+- `Off` -> `off`
+- `Level1` -> `level1`
+- `Level2` -> `level2`
+- `Level3` -> `level3`
+- `Level4` -> `level4`
+- `Breeze` -> `breeze`
+- `Holiday` -> `holiday`
+
+Please update any automations where you are using the state of this Renson sensor.
+
+[@joostlek]: https://github.com/joostlek
+[#96040]: https://github.com/home-assistant/core/pull/96040
+
+{% enddetails %}
+
+If you are a custom integration developer and want to learn about breaking
+changes and new features available for your integration: Be sure to follow our
+[developer blog][devblog]. The following are the most notable for this release:
+
+- [Action event for custom cards](https://developers.home-assistant.io/blog/2023/07/07/action-event-custom-cards)
+- [The naming of MQTT entities changes to correspond with HA guidelines](https://developers.home-assistant.io/blog/2023-057-21-change-naming-mqtt-entities)
+- [Translating services](https://developers.home-assistant.io/blog/2023/07/11/translating-services)
+- [Updates to the Vacuum entity integration](https://developers.home-assistant.io/blog/2023/07/10/vacuum-updates)
+
+[devblog]: https://developers.home-assistant.io/blog/
+
+## Farewell to the following
+
+The following integrations are also no longer available as of this release:
+
+- **Discovery** has been removed. This is the old legacy discovery integration.
+  See the breaking changes above for more information.  
+  ([@frenck] - [#96856])
+- **Mi Flora** has been removed. This integration was replaced by the
+  [Xiaomi BLE] integration a long time ago and was in a non-functional state.  
+  ([@frenck] - [#96868])
+- **Xiaomi Mijia BLE T&H Sensor** has been removed. This integration was
+  replaced by the [Xiaomi BLE] integration  a long time ago and was in a
+  non-functional state.  
+  ([@frenck] - [#96869])
+
+[@frenck]: https://github.com/frenck
+[#96856]: https://github.com/home-assistant/core/pull/96856
+[#96868]: https://github.com/home-assistant/core/pull/96868
+[#96869]: https://github.com/home-assistant/core/pull/96869
+[Xiaomi BLE]: /integations/xiaomi_ble
+
+## All changes
+
+Of course, there is a lot more in this release. You can find a list of
+all changes made here: [Full changelog for Home Assistant Core 2023.8](/changelogs/core-2023.8)

source/blueprints/blog/2023-08/cast_dall_e.yaml

@@ -0,0 +1,72 @@
+blueprint:
+  name: Cast Dall-E generated images
+  description: |
+    Generate an image using your voice and show it on a screen.
+    Requirements:
+      - OpenAI Conversation configured
+      - A Cast-compatible media player
+  domain: automation
+  author: JLo
+  homeassistant:
+    min_version: 2023.7.99
+  input:
+    assist_command:
+      name: Assist Command
+      description: |
+        The Assist command you will use to generate the picture. 
+        You can change the overall sentence to match your style and language. 
+        **WARNING** you **MUST** include `{prompt}` in order to pass that variable to OpenAI.
+      default: "Show me a picture of {prompt}"
+      selector:
+        text:
+    open_ai_generation_size:
+      name: Image Size (px)
+      description: "Note: Bigger images take more time to generate"
+      default: "512"
+      selector:
+        select:
+          options:
+            - "256"
+            - "512"
+            - "1024"
+    open_ai_config_entry:
+      name: OpenAI Configuration
+      description: The OpenAI configuration entry to generate the image
+      selector:
+        config_entry:
+          integration: "openai_conversation"
+    media_player:
+      name: Media player
+      description: Media player to show the picture
+      selector:
+        entity:
+          filter:
+            integration: "cast"
+            domain: "media_player"
+    additional_conditions:
+      name: Additional conditions
+      description: |
+        Extra conditions you may want to add to this automation 
+        (Example: Home occupied, TV on, etc)
+      default: []
+      selector:
+        condition:
+
+trigger:
+  - platform: conversation
+    command: !input assist_command
+condition: !input additional_conditions
+action:
+  - service: openai_conversation.generate_image
+    data:
+      size: !input open_ai_generation_size
+      config_entry: !input open_ai_config_entry
+      prompt: "{{trigger.slots.prompt}}"
+    response_variable: generated_image
+  - service: media_player.play_media
+    data:
+      media_content_type: image/jpeg
+      media_content_id: "{{generated_image.url}}"
+    target:
+      entity_id: !input media_player
+mode: single

source/getting-started/onboarding.markdown

@@ -20,26 +20,34 @@ In this step, you will create the owner account of Home Assistant. This account
 
     ![Set your username and password.](/images/getting-started/username.png)
 
-2. Enter a name for your home and define the location specific settings and the language of the user interface. 
-   - To automatically populate these settings, select **Detect**.
-   - If you'd rather not send your location, you can set these values manually.
+2. Enter a name for your home.
+3. Enter the location of your home.
+   - The location is used to populate settings such as time zone, unit system, and currency.
+   - It is also used for location-based information and automations: for example showing the weather-forecast, opening the shades at sunrise, or starting the vacuum when you leave the home.
+   - If you'd rather not send your location, you can choose a location far away from where you live.
+   - You can always change this information later in the settings.
 
-    ![Define your location specific settings.](/images/getting-started/onboarding_location.png)
+    ![Define your location.](/images/getting-started/onboarding_location.png)
     
-3. Select which information you are willing to share. 
-    - Sharing is disabled by default. However, we would like to encourage you to share some of this data. 
+4. Check if the location based information is correct and change if necessary.
+   - You can always change this information later in the settings.
+
+   ![Define your location specific settings.](/images/getting-started/location_based_settings.png)
+
+5. Select which information you are willing to share.
+    - Sharing is disabled by default. However, we would like to encourage you to share some of this data.
     - This information helps us to find out which platforms we need to support and where to focus our efforts.
-    - The data is anonymized and aggregated. To see the charts we generate out of this data, take a look at our [analytics page](https://analytics.home-assistant.io/). 
+    - The data is anonymized and aggregated. To see the charts we generate out of this data, take a look at our [analytics page](https://analytics.home-assistant.io/).
     
-   ![Share anonymized data](/images/getting-started/onboarding_share_anonymized_info.png) 
+   ![Share anonymized data](/images/getting-started/onboarding_share_anonymized_info.png)
 
-4. Once you are done, select **Next**. 
+6. Once you are done, select **Next**.
     - Home Assistant will then show any {% term devices %} it has discovered on your network.
     - Don't be alarmed if you see fewer items than shown below; you can always manually add devices later.
 
     ![Discovery of devices on your network.](/images/getting-started/onboarding_devices.png)
 
-5. Finally, select **Finish**. 
+7. Finally, select **Finish**.
    - Now you're brought to the Home Assistant web interface. This screen will show all of your devices.
 
-{% include getting-started/next_step.html step="Concepts & Terminologies" link="/getting-started/concepts-terminology/" %}
+{% include getting-started/next_step.html step="Concepts & Terminology" link="/getting-started/concepts-terminology/" %}