-
-
- {% active_link /docs/assist/android/ Assist for Android %} -
- {% active_link /docs/assist/apple/ Assist for Apple devices %} -
- {% active_link /docs/assist/builtin_sentences/ Built-in sentences %} -
- {% active_link /docs/assist/custom_sentences/ Custom sentences %} -
- {% active_link /docs/assist/voice_remote_expose_devices/ Exposing devices to your voice assistant %} -
- {% active_link /docs/assist/voice_remote_local_assistant/ Configuring a local assistant %} -
- {% active_link /docs/assist/troubleshooting/ Troubleshooting Assist %} -
- {% active_link /docs/assist/voice_remote_local_assistant/ Configuring a local assistant %} -
- {% active_link /projects/worlds-most-private-voice-assistant/ Tutorial: World's most private voice assistant %} -
- {% active_link /projects/thirteen-usd-voice-remote/ Tutorial: $13 voice remote %} - -
-
diff --git a/source/_includes/asides/voice_navigation.html b/source/_includes/asides/voice_navigation.html
new file mode 100644
index 00000000000..b08c7938cb7
--- /dev/null
+++ b/source/_includes/asides/voice_navigation.html
@@ -0,0 +1,32 @@
+
- Dashboards +
- + Voice control +
Devices
+ +Voice assistants
+ +Projects
+ +
+ 
+
+ 
+
+2 _Options prefixed with `[CIFS]` is only available for CIFS targets._ + +### Change default backup location + +By default, the first network storage of type **Backup** that you add will be set as your default backup target. + +If you want to change the default backup target, you can do the following: + +1. Go to **{% my backup title="Settings > System > Backups" %}** in the UI. +1. Select the menu in the top right of the screen and select the **Change default backup location** option. +1. In the dialog, there is a single option to set the default backup target. +1. Choose the one you want from the list. +1. Select **Save**. + +This list will contain all the network storage targets you have added of usage type **Backup**. It also contains another option to set it back to use `/backup` again. + +
+ 
+
Custom slot values with synonyms.
@@ -217,6 +219,8 @@ intent_script:
service: scene.turn_on
target:
entity_id: scene.{{ Scene | replace(" ", "_") }}
+ data:
+ id: {{ Scene_Id }}
speech:
type: plain
text: OK
diff --git a/source/_integrations/amazon_polly.markdown b/source/_integrations/amazon_polly.markdown
index ba7f4004f82..204df6c3bf0 100644
--- a/source/_integrations/amazon_polly.markdown
+++ b/source/_integrations/amazon_polly.markdown
@@ -16,7 +16,7 @@ Polly is a paid service via Amazon Web Services. There is a [free tier](https:/
## Setup
-For more information, please read the [AWS General Reference regarding Security Credentials](https://docs.aws.amazon.com/general/latest/gr/aws-security-credentials.html) to get the needed details. Also, check the [boto3 Documentation](https://boto3.readthedocs.io/en/latest/guide/configuration.html#shared-credentials-file) about the profiles and the [AWS Regions and Endpoints Reference](https://docs.aws.amazon.com/general/latest/gr/rande.html#pol_region) for available regions.
+For more information, please read the [AWS General Reference regarding Security Credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/security-creds.html) to get the needed details. Also, check the [boto3 Documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/guide/credentials.html#shared-credentials-file) about the profiles and the [AWS Regions and Endpoints Reference](https://docs.aws.amazon.com/general/latest/gr/rande.html#regional-endpoints) for available regions.
Available voices are listed in the [Amazon Documentation](https://docs.aws.amazon.com/polly/latest/dg/voicelist.html).
diff --git a/source/_integrations/androidtv_remote.markdown b/source/_integrations/androidtv_remote.markdown
index 259b6c5b35b..6b233ddcbf2 100644
--- a/source/_integrations/androidtv_remote.markdown
+++ b/source/_integrations/androidtv_remote.markdown
@@ -1,23 +1,26 @@
---
title: Android TV Remote
-description: Instructions on how to integrate Android TV remotes into Home Assistant.
+description: Instructions on how to integrate Android TV Remote into Home Assistant.
ha_category:
+ - Media Player
- Remote
ha_release: 2023.5
ha_iot_class: Local Push
ha_config_flow: true
ha_codeowners:
- '@tronikos'
+ - '@Drafteed'
ha_quality_scale: platinum
ha_domain: androidtv_remote
ha_zeroconf: true
ha_platforms:
- diagnostics
+ - media_player
- remote
ha_integration_type: device
---
-The Android TV Remote integration allows you to control an Android TV device by sending [commands](https://github.com/tronikos/androidtvremote2/blob/main/TvKeys.txt) and launching apps. For this to work, the Android TV device needs to have [Android TV Remote Service](https://play.google.com/store/apps/details?id=com.google.android.tv.remote.service) which is pre-installed on most devices.
+The Android TV Remote integration allows you to control an Android TV and launching apps. For this to work the Android TV device needs to have [Android TV Remote Service](https://play.google.com/store/apps/details?id=com.google.android.tv.remote.service) which is pre-installed on most devices.
For a quick introduction on how to get started with Android TV Remote, check out this video:
@@ -25,21 +28,17 @@ For a quick introduction on how to get started with Android TV Remote, check out
{% include integrations/config_flow.md %}
-## Entity
+## Media player
-This integration adds a `remote` entity which turns on/off the Android TV device.
-The entity has the `current_activity` attribute that shows the current foreground app on the Android TV.
+This integration adds a `media_player` with basic playback and volume controls. The media player provides volume information and display name of current active app on the Android TV. Due to API limitations, the integration will not display the playback status. It is recommended to use this integration together with [Google Cast integration](https://www.home-assistant.io/integrations/cast/). Two media players can be combined into one using the [Universal Media Player](https://www.home-assistant.io/integrations/universal/) integration.
-## Services
+Using the `media_player.play_media` service, you can launch applications via `Deep Links` and switch channels.
-You can use the `remote.turn_off`, `remote.turn_on`, `remote.toggle`, and `remote.send_command` services from the [remote](/integrations/remote/) platform.
+### Launching apps
-For a list of the most common commands that you can send to the Android TV via `remote.send_command`, see: [TvKeys](https://github.com/tronikos/androidtvremote2/blob/main/TvKeys.txt).
-For a full list, see [here](https://github.com/tronikos/androidtvremote2/blob/main/src/androidtvremote2/remotemessage.proto#L90).
+You can pass any URL to the device to open it in the built-in browser. Using `Deep Links` you can launch some applications.
-If `activity` is specified in `remote.turn_on`, it will open the specified URL in the associated app.
-
-Examples of URLs to pass as activity for some popular apps:
+Examples of some `Deep Links` for popular applications:
| App | URL |
| --- | --- |
@@ -48,6 +47,132 @@ Examples of URLs to pass as activity for some popular apps:
| Prime Video | https://app.primevideo.com
| Disney+ | https://www.disneyplus.com
+Examples:
+
+```yaml
+# Launch the Netflix app
+service: media_player.play_media
+data:
+ media_content_type: url
+ media_content_id: https://www.netflix.com/title
+target:
+ entity_id: media_player.living_room_tv
+```
+
+```yaml
+# Open a specific YouTube video:
+service: media_player.play_media
+data:
+ media_content_type: url
+ media_content_id: https://www.youtube.com/watch?v=dQw4w9WgXcQ
+target:
+ entity_id: media_player.living_room_tv
+```
+
+### Switch channels
+
+You can pass the channel number to switch the channel. The channel number must be an integer.
+
+Example:
+
+```yaml
+# Change channel to number 15:
+service: media_player.play_media
+data:
+ media_content_type: channel
+ media_content_id: 15
+target:
+ entity_id: media_player.living_room_tv
+```
+
+## Remote
+
+The remote allows you to send key commands to your Android TV device with the `remote.send_command` service.
+The entity has the `current_activity` attribute that shows the current foreground app on the Android TV.
+
+{% details "List of the most common commands" %}
+
+Navigation:
+- DPAD_UP
+- DPAD_DOWN
+- DPAD_LEFT
+- DPAD_RIGHT
+- DPAD_CENTER
+- BUTTON_A
+- BUTTON_B
+- BUTTON_X
+- BUTTON_Y
+
+Volume Control:
+- VOLUME_DOWN
+- VOLUME_UP
+- VOLUME_MUTE
+- MUTE
+
+Media Control:
+- MEDIA_PLAY_PAUSE
+- MEDIA_PLAY
+- MEDIA_PAUSE
+- MEDIA_NEXT
+- MEDIA_PREVIOUS
+- MEDIA_STOP
+- MEDIA_RECORD
+- MEDIA_REWIND
+- MEDIA_FAST_FORWARD
+
+TV Control:
+- 0
+- 1
+- 2
+- 3
+- 4
+- 5
+- 6
+- 7
+- 8
+- 9
+- DEL
+- ENTER
+- CHANNEL_UP
+- CHANNEL_DOWN
+- F1
+- F2
+- F3
+- F4
+- F5
+- F6
+- F7
+- F8
+- F9
+- F10
+- F11
+- F12
+- TV
+- PROG_RED
+- PROG_GREEN
+- PROG_YELLOW
+- PROG_BLUE
+
+Other:
+- BUTTON_MODE
+- EXPLORER
+- MENU
+- INFO
+- GUIDE
+- TV_TELETEXT
+- CAPTIONS
+- DVR
+- MEDIA_AUDIO_TRACK
+- SETTINGS
+- SEARCH
+- ASSIST
+
+{% enddetails %}
+
+For a full list see [here](https://github.com/tronikos/androidtvremote2/blob/main/src/androidtvremote2/remotemessage.proto#L90).
+
+If `activity` is specified in `remote.turn_on` it will open the specified URL in the associated app. See [Launching apps section](#launching-apps).
+
Examples of service calls:
```yaml
@@ -87,7 +212,7 @@ target:
entity_id: remote.living_room_tv
```
-## Dashboard example
+### Dashboard example
You have to manually create buttons in Lovelace to send commands to the Android TV device or launch apps on it.
diff --git a/source/_integrations/assist_pipeline.markdown b/source/_integrations/assist_pipeline.markdown
index 080fda04907..edff2cd5347 100644
--- a/source/_integrations/assist_pipeline.markdown
+++ b/source/_integrations/assist_pipeline.markdown
@@ -15,7 +15,7 @@ ha_platforms:
- select
---
-The Assist pipeline integration provides the foundation for the [Assist](/docs/assist/) voice assistant in Home Assistant.
+The Assist pipeline integration provides the foundation for the [Assist](/voice_control/) voice assistant in Home Assistant.
For most users, there is no need to install this integration manually. The Assist pipeline integration is part of the default configuration and is set up automatically if needed by other integrations.
If you are not using the default integration, you need to add the following to your `configuration.yaml` file:
@@ -25,4 +25,4 @@ If you are not using the default integration, you need to add the following to y
assist_pipeline:
```
-For more information, refer to the procedure on [configuring a pipeline](/docs/assist/voice_remote_local_assistant/).
+For more information, refer to the procedure on [configuring a pipeline](/voice_control/voice_remote_local_assistant/).
diff --git a/source/_integrations/aws.markdown b/source/_integrations/aws.markdown
index 55975493d39..2d2f7254208 100644
--- a/source/_integrations/aws.markdown
+++ b/source/_integrations/aws.markdown
@@ -15,7 +15,7 @@ The `aws` integration provides a single place to interact with [Amazon Web Servi
## Setup
-You have to have an AWS account to use Amazon Web Services, create one [here](https://aws.amazon.com/free/) with a 12 months free tier benefit. Please note, even in the first 12-months, you may still be billed if you use more resources than offered in the free tier. We advise you to monitor your costs in the [AWS Billing Console](https://console.aws.amazon.com/billing/) closely. You can read the [Control your AWS costs](https://aws.amazon.com/getting-started/tutorials/control-your-costs-free-tier-budgets/) guide for more information.
+You have to have an AWS account to use Amazon Web Services, create one [here](https://aws.amazon.com/free/) with a 12 months free tier benefit. Please note, even in the first 12-months, you may still be billed if you use more resources than offered in the free tier. We advise you to monitor your costs in the [AWS Billing Console](https://console.aws.amazon.com/billing/) closely. You can read the [Control your AWS costs](https://aws.amazon.com/getting-started/hands-on/control-your-costs-free-tier-budgets/) guide for more information.
The `lambda`, `sns`, `sqs`, and `events` services, used in the `aws` component, all provide an **Always Free** tier for all users even after the 12-month period. The general usage in Home Automation will most likely not reach the free tier limit. Please read [Lambda Pricing](https://aws.amazon.com/lambda/pricing/), [SNS Pricing](https://aws.amazon.com/sns/pricing/), [SQS Pricing](https://aws.amazon.com/sqs/pricing/), and [EventBridge Pricing](https://aws.amazon.com/eventbridge/pricing/) for more details.
@@ -104,7 +104,7 @@ context:
## Lambda Notify Usage
-AWS Lambda is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will invoke a Lambda for all targets given in the notification payload. A target can be formatted as a function name, an entire ARN ([Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)) or a partial ARN. For more information, please see the [botocore documentation](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/lambda.html#Lambda.Client.invoke).
+AWS Lambda is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will invoke a Lambda for all targets given in the notification payload. A target can be formatted as a function name, an entire ARN ([Amazon Resource Name](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html)) or a partial ARN. For more information, please see the [botocore documentation](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/lambda/client/invoke.html).
The Lambda event payload will contain everything passed in the service call payload. Here is an example payload that would be sent to Lambda:
@@ -132,7 +132,7 @@ The context will look like this:
## SNS Notify Usage
-AWS SNS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to all targets given in the notification payload. A target must be a SNS topic or endpoint ARN ([Amazon Resource Name](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)). For more information, please see the [botocore documentation](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sns.html#SNS.Client.publish).
+AWS SNS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to all targets given in the notification payload. A target must be a SNS topic or endpoint ARN ([Amazon Resource Name](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html)). For more information, please see the [botocore documentation](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sns/client/publish.html).
If one exists, the SNS Subject will be set to the title. All attributes from the payload, except the message, will be sent as stringified message attributes.
@@ -158,7 +158,7 @@ If you do not download them, you will lose them and will have to recreate a new
## SQS Notify Usage
-AWS SQS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to the queue for all targets given in the notification payload. A target must be a SQS topic URL. For more information, please see the [SQS documentation](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/ImportantIdentifiers.html) and [bototcore documentation](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sqs.html#SQS.Client.send_message)
+AWS SQS is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to the queue for all targets given in the notification payload. A target must be a SQS topic URL. For more information, please see the [SQS documentation](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-message-identifiers.html) and [botocore documentation](https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/sqs/client/send_message.html)
The SQS event payload will contain everything passed in the service call payload. SQS payloads will be published as stringified JSON. All attributes from the payload, except message, will also be sent as stringified message attributes. Here is an example message that would be published to the SQS queue:
@@ -174,7 +174,7 @@ The SQS event payload will contain everything passed in the service call payload
```
## EventBridge Notify Usage
-AWS EventBridge is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to the event bus for all targets given in the notification payload. A target must be a name of an event bus accessible by the given credentials. A target is not required, and the default event bus will be used if none are specified. For more information, please see the [EventBridge documentation](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-event-bus.html) and [bototcore documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/events.html#EventBridge.Client.put_events)
+AWS EventBridge is a notification platform and thus can be controlled by calling the `notify` service [as described here](/integrations/notify/). It will publish a message to the event bus for all targets given in the notification payload. A target must be a name of an event bus accessible by the given credentials. A target is not required, and the default event bus will be used if none are specified. For more information, please see the [EventBridge documentation](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-event-bus.html) and [botocore documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/events/client/put_events.html)
There are two options for generating the event detail based on the service call payload. If the `detail` attribute is specified, then its value will be serialized as a JSON object and used for the event detail. If the attribute is not specified, then the value of the `message` attribute is serialized as a simple JSON object with a single key named `message` and the value of the message supplied to the service call.
diff --git a/source/_integrations/azure_event_hub.markdown b/source/_integrations/azure_event_hub.markdown
index f2355779316..2d253115cdb 100644
--- a/source/_integrations/azure_event_hub.markdown
+++ b/source/_integrations/azure_event_hub.markdown
@@ -12,15 +12,15 @@ ha_config_flow: true
ha_integration_type: integration
---
-The `Azure Event Hub` integration allows you to hook into the Home Assistant event bus and send events to [Azure Event Hub](https://azure.microsoft.com/en-us/services/event-hubs/) or to an [Azure IoT Hub](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-read-builtin).
+The `Azure Event Hub` integration allows you to hook into the Home Assistant event bus and send events to [Azure Event Hub](https://azure.microsoft.com/products/event-hubs/) or to an [Azure IoT Hub](https://learn.microsoft.com/azure/iot-hub/iot-hub-devguide-messages-read-builtin).
## First time setup
-This assumes you already have an Azure account. Otherwise create a Free account [here](https://azure.microsoft.com/en-us/free/).
+This assumes you already have an Azure account. Otherwise create a Free account [here](https://azure.microsoft.com/free/).
-You need to create an Event Hub namespace and an Event Hub in that namespace, you can follow [this guide](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create). Alternatively you can directly deploy an ARM template with the namespace and the Event Hub [from here](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.eventhub/event-hubs-create-event-hub-and-consumer-group).
+You need to create an Event Hub namespace and an Event Hub in that namespace, you can follow [this guide](https://learn.microsoft.com/azure/event-hubs/event-hubs-create). Alternatively you can directly deploy an ARM template with the namespace and the Event Hub [from here](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.eventhub/event-hubs-create-event-hub-and-consumer-group).
-You must then create a Shared Access Policy for the Event Hub with 'Send' claims or use the RootManageAccessKey from your namespace (this key has additional claims, including managing the event hub and listening, which are not needed for this purpose), for more details on the security of Event Hubs [go here](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-authentication-and-security-model-overview).
+You must then create a Shared Access Policy for the Event Hub with 'Send' claims or use the RootManageAccessKey from your namespace (this key has additional claims, including managing the event hub and listening, which are not needed for this purpose), for more details on the security of Event Hubs [go here](https://learn.microsoft.com/azure/event-hubs/authenticate-shared-access-signature).
Once you have the name of your namespace, instance, Shared Access Policy and the key for that policy, you can setup the integration itself.
@@ -94,10 +94,10 @@ filter:
## Using the data in Azure
-There are a number of ways to stream the data that comes into the Event Hub into storages in Azure, the easiest way is to use the built-in Capture function and this allows you to capture the data in Azure Blob Storage or Azure Data Lake store, [details here](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-capture-overview).
+There are a number of ways to stream the data that comes into the Event Hub into storages in Azure, the easiest way is to use the built-in Capture function and this allows you to capture the data in Azure Blob Storage or Azure Data Lake store, [details here](https://learn.microsoft.com/azure/event-hubs/event-hubs-capture-overview).
-Other storages in Azure (and outside) are possible with an [Azure Stream Analytics job](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-define-inputs#stream-data-from-event-hubs), for instance for [Cosmos DB](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-documentdb-output), [Azure SQL DB](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-sql-output-perf), [Azure Table Storage](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-define-outputs#table-storage), custom writing to [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-custom-path-patterns-blob-storage-output) and [Topic and Queues](https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-quick-create-portal#configure-job-output).
+Other storages in Azure (and outside) are possible with an [Azure Stream Analytics job](https://learn.microsoft.com/azure/stream-analytics/stream-analytics-define-inputs#stream-data-from-event-hubs), for instance for [Cosmos DB](https://learn.microsoft.com/azure/stream-analytics/stream-analytics-documentdb-output), [Azure SQL DB](https://learn.microsoft.com/azure/stream-analytics/stream-analytics-sql-output-perf), [Azure Table Storage](https://learn.microsoft.com/azure/stream-analytics/stream-analytics-define-outputs), custom writing to [Azure Blob Storage](https://learn.microsoft.com/azure/stream-analytics/stream-analytics-custom-path-patterns-blob-storage-output) and [Topic and Queues](https://learn.microsoft.com/azure/stream-analytics/stream-analytics-quick-create-portal#configure-job-output).
-On the analytical side, Event Hub can be directly fed into [Azure Databricks Spark](https://docs.microsoft.com/en-us/azure/azure-databricks/databricks-stream-from-eventhubs?toc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fevent-hubs%2FTOC.json&bc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fbread%2Ftoc.json), [Azure Time Series Insights](https://docs.microsoft.com/en-us/azure/time-series-insights/time-series-insights-how-to-add-an-event-source-eventhub) and [Microsoft Power BI](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-tutorial-visualize-anomalies).
+On the analytical side, Event Hub can be directly fed into [Azure Databricks Spark](https://learn.microsoft.com/azure/databricks/structured-streaming/streaming-event-hubs), [Azure Time Series Insights](https://learn.microsoft.com/azure/time-series-insights/how-to-ingest-data-event-hub) and [Microsoft Power BI](https://learn.microsoft.com/azure/stream-analytics/stream-analytics-real-time-fraud-detection).
-The final way to use the data in Azure is to connect an Azure Function to the Event Hub using the [Event Hub trigger binding](https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-event-hubs).
+The final way to use the data in Azure is to connect an Azure Function to the Event Hub using the [Event Hub trigger binding](https://learn.microsoft.com/azure/azure-functions/functions-bindings-event-hubs).
diff --git a/source/_integrations/azure_service_bus.markdown b/source/_integrations/azure_service_bus.markdown
index c2c7aeccc9b..25ae9f72c34 100644
--- a/source/_integrations/azure_service_bus.markdown
+++ b/source/_integrations/azure_service_bus.markdown
@@ -13,15 +13,15 @@ ha_platforms:
ha_integration_type: integration
---
-The `Azure Service Bus` integration allows you to send messages to [Azure Service Bus](https://azure.microsoft.com/en-us/services/service-bus/) from within Home Assistant.
+The `Azure Service Bus` integration allows you to send messages to [Azure Service Bus](https://azure.microsoft.com/products/service-bus/) from within Home Assistant.
## First-time setup
-This assumes you already have an Azure account. Otherwise, create a free account [here](https://azure.microsoft.com/en-us/free/).
+This assumes you already have an Azure account. Otherwise, create a free account [here](https://azure.microsoft.com/free/).
-You need to create a Service Bus namespace; you can follow [this guide](https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-create-namespace-portal).
+You need to create a Service Bus namespace; you can follow [this guide](https://learn.microsoft.com/azure/service-bus-messaging/service-bus-quickstart-portal#create-a-namespace-in-the-azure-portal).
-You must then create a Shared Access Policy for the Service Bus with `Send` claims or use the RootManageAccessKey from your namespace (this key has additional claims, including managing the event hub and listening, which are not needed for this purpose), for more details on the security of Service Bus [go here](https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-authentication-and-authorization#shared-access-signature). Alternatively you can create a dedicated key for only one queue or topic, to restrict access to only that queue or topic.
+You must then create a Shared Access Policy for the Service Bus with `Send` claims or use the RootManageAccessKey from your namespace (this key has additional claims, including managing the event hub and listening, which are not needed for this purpose), for more details on the security of Service Bus [go here](https://learn.microsoft.com/azure/service-bus-messaging/service-bus-authentication-and-authorization#shared-access-signature). Alternatively you can create a dedicated key for only one queue or topic, to restrict access to only that queue or topic.
Once you have the connection string with `Send` policy, you can set up the integration itself.
diff --git a/source/_integrations/binary_sensor.mqtt.markdown b/source/_integrations/binary_sensor.mqtt.markdown
index e7a4757ea19..347cb372845 100644
--- a/source/_integrations/binary_sensor.mqtt.markdown
+++ b/source/_integrations/binary_sensor.mqtt.markdown
@@ -69,7 +69,7 @@ availability_topic:
required: false
type: string
device:
- description: "Information about the device this binary sensor is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
+ description: "Information about the device this binary sensor is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/device_registry_index/). Only works through [MQTT discovery](/integrations/mqtt/#mqtt-discovery) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device."
required: false
type: map
keys:
@@ -129,7 +129,7 @@ encoding:
type: string
default: "utf-8"
entity_category:
- description: The [category](https://developers.home-assistant.io/docs/core/entity#generic-properties) of the entity.
+ description: The [category](https://developers.home-assistant.io/docs/core/entity/#generic-properties) of the entity.
required: false
type: string
default: None
diff --git a/source/_integrations/bmw_connected_drive.markdown b/source/_integrations/bmw_connected_drive.markdown
index a79cf8cf53e..b14b7d35b54 100644
--- a/source/_integrations/bmw_connected_drive.markdown
+++ b/source/_integrations/bmw_connected_drive.markdown
@@ -11,6 +11,7 @@ ha_category:
- Presence Detection
- Select
- Sensor
+ - Switch
ha_release: 0.64
ha_iot_class: Cloud Polling
ha_config_flow: true
@@ -28,6 +29,7 @@ ha_platforms:
- number
- select
- sensor
+ - switch
ha_integration_type: integration
---
@@ -50,6 +52,7 @@ This integration provides the following platforms:
- [Notifications](/integrations/bmw_connected_drive/#notifications): Send Points of Interest (POI) to your car.
- [Buttons](/integrations/bmw_connected_drive/#buttons): Turn on air condition, sound the horn, flash the lights, update the vehicle location and update the state.
- [Selects](/integrations/bmw_connected_drive/#selects): Display and control charging related settings for (PH)EVs.
+- [Switches](/integrations/bmw_connected_drive/#switches): Display and toggle settings on your car.
- [Numbers](/integrations/bmw_connected_drive/#numbers): Display and control numeric charging related settings for (PH)EVs.
## Configuration
@@ -107,10 +110,6 @@ The air conditioning of the vehicle can be activated with the `button.
-You must [restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. After restarting, navigate to the **Settings** -> **Devices & Services** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the app according to the above **Automatic Configuration**, starting at step 2.
+You must [restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. After restarting, go to {% my integrations title="**Settings** > **Devices & Services**" %} and select the cogwheel. Then, select **Configure** and continue to authorize the app according to the above **Automatic Configuration**, starting at step 2.
## Notifications
diff --git a/source/_integrations/electrasmart.markdown b/source/_integrations/electrasmart.markdown
new file mode 100644
index 00000000000..d64e97c0ace
--- /dev/null
+++ b/source/_integrations/electrasmart.markdown
@@ -0,0 +1,23 @@
+---
+title: Electra Smart
+description: Instructions for how to integrate Electra Air Conditioners within Home Assistant.
+ha_category:
+ - Climate
+ha_release: 2023.6
+ha_iot_class: Cloud Polling
+ha_config_flow: true
+ha_codeowners:
+ - '@jafar-atili'
+ha_domain: electrasmart
+ha_platforms:
+ - climate
+ha_integration_type: integration
+---
+
+[Electra Air](https://www.electra-air.co.il), is a company which manufactures and sells Air Conditioners.
+
+To set up this integration, you must have access to the phone number used to register in the Electra Smart mobile app.
+
+Air Conditioners configured in your Electra Smart mobile app will be discovered by Home Assistant after the Electra Smart integration is configured.
+
+{% include integrations/config_flow.md %}
diff --git a/source/_integrations/ezviz.markdown b/source/_integrations/ezviz.markdown
index 77ec77c44bf..94a93153fc2 100644
--- a/source/_integrations/ezviz.markdown
+++ b/source/_integrations/ezviz.markdown
@@ -4,6 +4,7 @@ description: Integrate EZVIZ camera within Home Assistant.
ha_release: 0.107
ha_category:
- Camera
+ - Update
ha_iot_class: Cloud Polling
ha_domain: ezviz
ha_codeowners:
@@ -13,8 +14,10 @@ ha_config_flow: true
ha_platforms:
- binary_sensor
- camera
+ - number
- sensor
- switch
+ - update
ha_integration_type: integration
---
@@ -91,6 +94,14 @@ To enable/disable motion detection, use the Home Assistant built in services.
| -----------------------| ----------- |
| `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
+### OTA update
+
+Trigger device OTA firmware update process for latest stable version.
+
+### Motion Detection Sensitivity
+
+The motion detection sensitivity can be adjusted using the "Detection sensitivity" Number entity. It's important to note that this entity fetches information from the device and will not update if your battery-powered camera is in sleep mode, as this measure is implemented to preserve battery life and prevent excessive drainage.
+
## Troubleshooting
- `authentication failed`: The authentication requires an EZVIZ account with two-step verification disabled. Google, Facebook, TikTok, or other Oauth-based accounts will not work.
diff --git a/source/_integrations/faa_delays.markdown b/source/_integrations/faa_delays.markdown
index a89ce7d1cf4..25e9e16250e 100644
--- a/source/_integrations/faa_delays.markdown
+++ b/source/_integrations/faa_delays.markdown
@@ -15,7 +15,7 @@ ha_integration_type: integration
---
The FAA Delays integration collects and displays information about delays at US Airports based on the
-[FAA's National Airspace System Status](https://www.fly.faa.gov/ois/).
+[FAA's National Airspace System Status](https://nasstatus.faa.gov/).
Data measured includes:
diff --git a/source/_integrations/facebook.markdown b/source/_integrations/facebook.markdown
index defe59dd9c4..0cd1eb90557 100644
--- a/source/_integrations/facebook.markdown
+++ b/source/_integrations/facebook.markdown
@@ -25,7 +25,7 @@ notify:
{% configuration %}
page_access_token:
- description: "Access token for your Facebook page. Checkout [Facebook Messenger Platform](https://developers.facebook.com/docs/messenger-platform/guides/setup) for more information."
+ description: "Access token for your Facebook page. Checkout [Facebook Messenger Platform](https://developers.facebook.com/docs/messenger-platform/webhooks) for more information."
required: true
type: string
name:
@@ -37,8 +37,8 @@ name:
### Usage
-With Facebook notify service, you can send your notifications to your Facebook messenger with help of your Facebook page. You have to create a [Facebook Page and App](https://developers.facebook.com/docs/messenger-platform/guides/quick-start) for this service. You can control it by calling the notify service [as described here](/integrations/notify/). It will send a message on messenger to user specified by **target** on behalf of your page. See the [quick start](https://developers.facebook.com/docs/messenger-platform/guides/quick-start) guide for more information.
-The phone number used in **target** should be registered with Facebook messenger. Phone number of the recipient should be in +1(212)555-2368 format. If your app is not approved by Facebook then the recipient should by either admin, developer or tester for your Facebook app. [More information](https://developers.facebook.com/docs/messenger-platform/send-api-reference#phone_number) about the phone number.
+With Facebook notify service, you can send your notifications to your Facebook messenger with help of your Facebook page. You have to create a [Facebook Page and App](https://developers.facebook.com/docs/messenger-platform/getting-started/quick-start) for this service. You can control it by calling the notify service [as described here](/integrations/notify/). It will send a message on messenger to user specified by **target** on behalf of your page. See the [quick start](https://developers.facebook.com/docs/messenger-platform/getting-started/quick-start) guide for more information.
+The phone number used in **target** should be registered with Facebook messenger. Phone number of the recipient should be in +1(212)555-2368 format. If your app is not approved by Facebook then the recipient should by either admin, developer or tester for your Facebook app. [More information](https://developers.facebook.com/docs/messenger-platform/reference/send-api#phone_number) about the phone number.
```yaml
# Example automation notification entry
@@ -102,7 +102,7 @@ if (preg_match('/get my id/', strtolower($message))) {
```
### Rich messages
-You could also send rich messing (cards, buttons, images, videos, etc). [Info](https://developers.facebook.com/docs/messenger-platform/send-api-reference) to which types of messages and how to build them.
+You could also send rich messing (cards, buttons, images, videos, etc). [Info](https://developers.facebook.com/docs/messenger-platform/reference/send-api) to which types of messages and how to build them.
```yaml
# Example script with a notification entry with a rich message
diff --git a/source/_integrations/feedreader.markdown b/source/_integrations/feedreader.markdown
index dcc44b604d0..9052eaa6c05 100644
--- a/source/_integrations/feedreader.markdown
+++ b/source/_integrations/feedreader.markdown
@@ -89,6 +89,11 @@ automation:
Any field under the `
-
Connecting a phone to Home Assistant requires an adapter.
diff --git a/source/_integrations/waze_travel_time.markdown b/source/_integrations/waze_travel_time.markdown
index 226c3f8842d..99f88931caa 100644
--- a/source/_integrations/waze_travel_time.markdown
+++ b/source/_integrations/waze_travel_time.markdown
@@ -27,7 +27,7 @@ Notes:
## Manual Polling
-Some users want more control over polling intervals. To use more granular polling, you can disable automated polling. Go to {% my integrations title="**Settings** > **Devices & Services**" %}, and on the **Waze Travel Time** integration, select the 3 dots. Then, select **System options** and toggle the button to disable polling. To manually trigger a polling request, call the [`homeassistant.update_entity` service](/integrations/homeassistant/#service-homeassistantupdate_entity) as needed, either manually or via automations.
+Some users want more control over polling intervals. To use more granular polling, you can disable automated polling. Go to {% my integrations title="**Settings** > **Devices & Services**" %}, and on the **Waze Travel Time** integration, select the cogwheel. On the integration entry, select the three dots. Then, select **System options** and toggle the button to disable polling. To manually trigger a polling request, call the [`homeassistant.update_entity` service](/integrations/homeassistant/#service-homeassistantupdate_entity) as needed, either manually or via automations.
## Example using dynamic destination
diff --git a/source/_integrations/whisper.markdown b/source/_integrations/whisper.markdown
new file mode 100644
index 00000000000..7c497e78460
--- /dev/null
+++ b/source/_integrations/whisper.markdown
@@ -0,0 +1,21 @@
+---
+title: Whisper
+description: Connect and control your Whisper devices using the Wyoming Protocol integration
+ha_category:
+ - Voice
+ha_domain: whisper
+ha_release: '2023.5'
+ha_integration_type: virtual
+ha_supporting_domain: wyoming
+ha_supporting_integration: Wyoming Protocol
+ha_codeowners:
+ - '@balloob'
+ - '@synesthesiam'
+ha_config_flow: true
+ha_platforms:
+ - stt
+ - tts
+ha_iot_class: Local Push
+---
+
+{% include integrations/supported_brand.md %}
diff --git a/source/_integrations/wiz.markdown b/source/_integrations/wiz.markdown
index fcd79394edb..310903f511e 100644
--- a/source/_integrations/wiz.markdown
+++ b/source/_integrations/wiz.markdown
@@ -37,7 +37,7 @@ These devices have been sold under at least the following brands:
- [Atom Lighting](https://atomlighting.com.au/)
- [ATX LED](https://atxledinc.com/)
- [Brilliant](https://www.brilliantlightsource.com/)
-- [Designers Fountain](https://designersftn.com/default.dmx)
+- [Designers Fountain](https://designersfountain.com/)
- [Evoluziona](https://tecnolite.mx/)
- [Fischer & Honsel](https://fischer-honsel.com/)
- [Gauss](https://gauss.ru/smartlight/products/)
@@ -47,12 +47,12 @@ These devices have been sold under at least the following brands:
- [Lednify](https://lednify.com/)
- [Leyton](https://www.leyton-lighting.co.uk/)
- [Liteline](https://www.liteline.com/page/oncloud)
-- [Lutec](https://www.lutec.com/highlight/wiz)
+- [Lutec](https://www.lutec.com/segments/connected)
- [Philips Smart LED lights with WiZ Connected](https://www.usa.lighting.philips.com/consumer/smart-wifi-led)
- [Spex](https://spexlighting.com/pages/smart-lights)
- [SLV](https://www.slv.com/)
- [Trenz](https://trenzlighting.com/pages/smart-lights)
-- [Trio](https://wiz.trio-lighting.com/en/)
+- [Trio](https://wiz.trio-lighting.com/)
- [Wofi](https://wofi-wiz.com/)
The integration can report the state of occupancy sensors that have been linked to a device.
@@ -61,8 +61,8 @@ The integration can report the state of occupancy sensors that have been linked
## Connect WiZ devices to your network
-To connect a WiZ device to your Wi-Fi network, please follow the instructions in the [WiZ app](https://www.wizconnected.com/en/consumer/app/) (available for iOS and Android).
-If you have further questions, please have a look at the [WiZ Support Page](https://www.wizconnected.com/en/consumer/support/).
+To connect a WiZ device to your Wi-Fi network, please follow the instructions in the [WiZ app](https://www.wizconnected.com/en-us/explore-wiz/app) (available for iOS and Android).
+If you have further questions, please have a look at the [WiZ Support Page](https://www.wizconnected.com/en-us/support/faq).
### Enable local connectivity
diff --git a/source/_integrations/workday.markdown b/source/_integrations/workday.markdown
index db41fed3a51..f84f5351c91 100644
--- a/source/_integrations/workday.markdown
+++ b/source/_integrations/workday.markdown
@@ -47,6 +47,8 @@ Add holidays will only take dates formatted with `YYYY-MM-DD`.
Remove holidays will take dates formatted with `YYYY-MM-DD` or partial of name, for example, `christmas` will exclude `Christmas Day`.
+The offset can be used to see if future days are workdays. For example, put `1` to see if tomorrow is a workday.
+
## Automation example
Example usage for automation:
diff --git a/source/_integrations/wyoming.markdown b/source/_integrations/wyoming.markdown
index 6ea6b53f066..5edb8a8adc9 100644
--- a/source/_integrations/wyoming.markdown
+++ b/source/_integrations/wyoming.markdown
@@ -16,7 +16,7 @@ ha_platforms:
ha_config_flow: true
---
-The Wyoming integration connects external voice services to Home Assistant using a [small protocol](https://github.com/rhasspy/rhasspy3/blob/master/docs/wyoming.md). This enables [Assist](/docs/assist) to use a variety of local [speech-to-text](/integrations/stt/) and [text-to-speech](/integrations/tts/) systems, such as:
+The Wyoming integration connects external voice services to Home Assistant using a [small protocol](https://github.com/rhasspy/rhasspy3/blob/master/docs/wyoming.md). This enables [Assist](/voice_control/) to use a variety of local [speech-to-text](/integrations/stt/) and [text-to-speech](/integrations/tts/) systems, such as:
* Whisper {% my supervisor_addon badge addon="core_whisper" %}
* Piper {% my supervisor_addon badge addon="core_piper" %}
diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown
index 2f3a4b48422..69b4071e394 100644
--- a/source/_integrations/xiaomi_miio.markdown
+++ b/source/_integrations/xiaomi_miio.markdown
@@ -219,12 +219,12 @@ Supported devices:
| Air Purifier 2S | zhimi.airpurifier.mc1 | |
| Air Purifier Super | zhimi.airpurifier.sa1 | |
| Air Purifier Super 2 | zhimi.airpurifier.sa2 | |
-| Air Purifier 3 (2019) | zhimi.airpurifier.ma4 | |
+| Air Purifier 3 (2019) | zhimi.airpurifier.ma4 | AC-M6-SC |
| Air Purifier 3H (2019) | zhimi.airpurifier.mb3 | |
| Air Purifier 3C | zhimi.airpurifier.mb4 | |
| Air Purifier ZA1 | zhimi.airpurifier.za1 | |
-| Air Purifier 4 | zhimi.airp.mb5 | |
-| Air Purifier 4 PRO | zhimi.airp.vb4 | |
+| Air Purifier 4 | zhimi.airp.mb5 | AC-M16-SC |
+| Air Purifier 4 PRO | zhimi.airp.vb4 | AC-M15-SC |
| Air Fresh A1 | dmaker.airfresh.a1 | MJXFJ-150-A1 |
| Air Fresh VA2 | zhimi.airfresh.va2 | |
| Air Fresh VA4 | zhimi.airfresh.va4 | |
diff --git a/source/_integrations/yale_home.markdown b/source/_integrations/yale_home.markdown
new file mode 100644
index 00000000000..71a1b5ab8ce
--- /dev/null
+++ b/source/_integrations/yale_home.markdown
@@ -0,0 +1,30 @@
+---
+title: Yale Home
+description: Connect and control your Yale Home devices using the August integration
+ha_category:
+ - Binary Sensor
+ - Button
+ - Camera
+ - Doorbell
+ - Lock
+ - Sensor
+ha_release: 0.64
+ha_domain: yale_home
+ha_integration_type: virtual
+ha_supporting_domain: august
+ha_supporting_integration: August
+ha_codeowners:
+ - '@bdraco'
+ha_config_flow: true
+ha_platforms:
+ - binary_sensor
+ - button
+ - camera
+ - diagnostics
+ - lock
+ - sensor
+ha_iot_class: Cloud Push
+ha_dhcp: true
+---
+
+{% include integrations/supported_brand.md %}
diff --git a/source/_integrations/yalexs_ble.markdown b/source/_integrations/yalexs_ble.markdown
index 8533280f507..76363ad7e38 100644
--- a/source/_integrations/yalexs_ble.markdown
+++ b/source/_integrations/yalexs_ble.markdown
@@ -50,26 +50,35 @@ These devices do not send updates, but can be locked and unlocked.
- MD-04I (Yale Conexis L1, Yale Conexis L2)
- YRCB-490 (Yale Smart Cabinet Lock)
+## Troubleshooting
+
+Lock operation requires setting up an encrypted connection highly sensitive to latency. It is recommended to use a [High-Performance Bluetooth adapter](/integrations/bluetooth/#known-working-high-performance-adapters) or [ESPHome Bluetooth proxy](/integrations/bluetooth/#remote-adapters-bluetooth-proxies) for stable operation.
+
## Push updates
Some locks only send push updates when they have an active HomeKit pairing. If your lock is not sending push updates, ensure it's paired with a HomeKit using an iOS device or the HomeKit controller integration. The lock cannot be paired via HomeKit Controller and the Yale Access Bluetooth integration on the same Home Assistant instance as they will both try to access the lock simultaneously and fail.
One easy way to fix this is to create a new/second home in the Apple Home app and add the lock to that new home. Push updates should occur as intended after the lock is added.
-Alternatively, call the `homeassistant.update_entity` service to force the integration to update the lock state.
+Alternatively, call the `homeassistant.update_entity` service to force the integration to update the lock state, or enable the always connected option.
+
+{% include integrations/option_flow.md %}
+
+If the lock does not support push updates via advertisements or you want lock operation to be more responsive, you can enable always connected mode. Always connected will cause the lock to stay connected to Home Assistant via Bluetooth, which will use more battery.
+
+If the lock does not support push updates via advertisements or you want lock operation to be more responsive, you can enable always connected mode. Always connected will cause the lock to stay connected to Home Assistant via Bluetooth, which will use more battery.
## Door Sensors
The lock must be calibrated in the Yale Access App for the door sensors to function correctly. If the door sensor has an unknown state or is not updating, try recalibrating the lock in the app.
-
## Obtaining the offline key
The offline key and slot number are required to operate the lock. These credentials can be found in multiple places depending on the lock brand and model.
-### Yale Access or August Cloud
+### Yale Access, Yale Home, or August Cloud
-The [August](/integrations/august) integration can automatically provision the offline key if the configured account has the key loaded. You may need to create or use a non-primary existing account with owner-level access to the lock, as not all accounts will have the key loaded.
+The [August](/integrations/august) integration can automatically provision the offline key if the configured account has the key loaded. You may need to create or use a non-primary existing account with owner-level access to the lock, as not all accounts will have the key loaded. If the lock was not discovered by Home Assistant when the cloud integration was loaded, reload the cloud integration once the lock has been discovered.
If the offline key can automatically be provisioned, you will not be asked to enter it and the integration should be automatically added, configured and running.
diff --git a/source/_integrations/yamaha_musiccast.markdown b/source/_integrations/yamaha_musiccast.markdown
index ef5c542ace0..b175ea27823 100644
--- a/source/_integrations/yamaha_musiccast.markdown
+++ b/source/_integrations/yamaha_musiccast.markdown
@@ -34,7 +34,7 @@ The Yamaha MusicCast integration implements the grouping services. There are som
## Play Media functionality
-The MusicCast integration supports the Home Assistant media browser for all streaming services, your device supports. For services such as Deezer, you have to log in using the official MusicCast app. In addition, local HTTP URLs can be played back using this service. This includes the Home Assistant text to speech services.
+The MusicCast integration supports the Home Assistant media browser for all streaming services, your device supports. For services such as Deezer, you have to log in using the official MusicCast app. In addition, local HTTP URLs can be played back using this service. This includes the Home Assistant text-to-speech services.
It is also possible to recall NetUSB presets using the play media service. To do so "presets:
diff --git a/source/_posts/2022-05-04-release-20225.markdown b/source/_posts/2022-05-04-release-20225.markdown
index 71c8e9e874d..ec992e35922 100644
--- a/source/_posts/2022-05-04-release-20225.markdown
+++ b/source/_posts/2022-05-04-release-20225.markdown
@@ -1562,7 +1562,7 @@ Home Assistant startup, instead of to "unknown".
{% enddetails %}
-{% details "Text-to-Speech (TTS)" %}
+{% details "text-to-speech (TTS)" %}
The TTS `base_url` option is deprecated. Please, configure internal/external
URL instead.
diff --git a/source/_posts/2022-12-20-year-of-voice.markdown b/source/_posts/2022-12-20-year-of-voice.markdown
index 7d7093d095a..90b98e262e7 100644
--- a/source/_posts/2022-12-20-year-of-voice.markdown
+++ b/source/_posts/2022-12-20-year-of-voice.markdown
@@ -44,7 +44,7 @@ With Home Assistant we want to make a privacy and locally focused smart home ava
With Home Assistant we prefer to get the things we’re building in the user's hands as early as possible. Even basic functionality allows users to find things that work and don’t work, allowing us to address the direction if needed.
-A voice assistant has a lot of different parts: hot word detection, speech to text, intent recognition, intent execution, text to speech. Making each work in every language is a lot of work. The most important part is the intent recognition and intent execution. We need to be able to understand your commands and execute them.
+A voice assistant has a lot of different parts: hot word detection, speech-to-text, intent recognition, intent execution, text-to-speech. Making each work in every language is a lot of work. The most important part is the intent recognition and intent execution. We need to be able to understand your commands and execute them.
We started gathering these command sentences in our new [intents repository](https://github.com/home-assistant/intents). It will soon power the existing [conversation integration](/integrations/conversation) in Home Assistant, allowing you to use our app to write and say commands.
diff --git a/source/_posts/2023-01-26-year-of-the-voice-chapter-1.markdown b/source/_posts/2023-01-26-year-of-the-voice-chapter-1.markdown
index 01e67f1e223..67fb3bf7159 100644
--- a/source/_posts/2023-01-26-year-of-the-voice-chapter-1.markdown
+++ b/source/_posts/2023-01-26-year-of-the-voice-chapter-1.markdown
@@ -32,7 +32,7 @@ We want Assist to be as accessible to as many people as possible. To do this, we
Assist is enabled by default in the Home Assistant 2023.2 release. Tap the new Assist icon 
at the top right of the dashboard to use it.
-[Assist documentation.](https://www.home-assistant.io/docs/assist/)
+[Assist documentation.](https://www.home-assistant.io/voice_control/)
@@ -40,7 +40,7 @@ Assist is enabled by default in the Home Assistant 2023.2 release. Tap the new A
We want to make it as easy as possible to use Assist. To enable this for Android users, we have added a new tile to the Android Wear app. A simple swipe from the clock face will show the assist button and allows you to send voice commands.
-[Assist on Android Wear documentation.](https://www.home-assistant.io/docs/assist/android/)
+[Assist on Android Wear documentation.](https://www.home-assistant.io/voice_control/android/)
_The tile is available in [Home Assistant Companion for Android 2023.1.1](https://play.google.com/store/apps/details?id=io.homeassistant.companion.android&pcampaignid=pcampaignidMKT-Other-global-all-co-prtnr-py-PartBadge-Mar2515-1&pcampaignid=pcampaignidMKT-Other-global-all-co-prtnr-py-PartBadge-Mar2515-1)._
@@ -50,7 +50,7 @@ _The tile is available in [Home Assistant Companion for Android 2023.1.1](https:
For Apple devices we have been able to create a fully hands-free experience by integrating with Siri. This is powered by a new Apple Shortcut action called Assist, which is part of the Home Assistant app. This shortcut action can also be manually triggered from your Mac taskbar, iPhone home screen or Apple Watch complication. We have two ready-made shortcuts that users can import from the documentation with a single tap to unlock these features.
-[Assist via Siri and Apple Shortcuts documentation.](https://www.home-assistant.io/docs/assist/apple/)
+[Assist via Siri and Apple Shortcuts documentation.](https://www.home-assistant.io/voice_control/apple/)
_The Assist shortcut is available in [Home Assistant Companion for iOS 2023.2](https://apps.apple.com/us/app/home-assistant/id1099568401?itsct=apps_box_badge&itscg=30200). Mac version is awaiting approval._
@@ -66,7 +66,7 @@ With Home Assistant we believe that every home is uniquely yours and that [techn
Assist includes support for custom sentences, responses and intents, allowing you to achieve all of the above, and more. We've designed the custom sentence format in a way that it can be easily shared with the community.
-Read [the documentation](https://www.home-assistant.io/docs/assist/custom_sentences) on how to get started.
+Read [the documentation](https://www.home-assistant.io/voice_control/custom_sentences) on how to get started.
_In a future release we're planning on adding a user interface to customize and import sentences._
@@ -92,8 +92,7 @@ For Year of the Voice - Chapter 1 we focused on building intent recognition into
We will continue collecting home automation sentences for all languages ([anyone can help!](https://developers.home-assistant.io/docs/voice/intent-recognition/)). Updates will be included with every major release of Home Assistant.
-Our next step is integrating Speech-to-Text and Text-to-Speech with Assist. We don't have a timeline yet when that will be ready. Stay tuned!
-
+Our next step is integrating speech-to-text and text-to-speech with Assist. We don't have a timeline yet when that will be ready. Stay tuned!
## Credits
A lot of people have worked very hard to make all of the above possible.
diff --git a/source/_posts/2023-02-01-release-20232.markdown b/source/_posts/2023-02-01-release-20232.markdown
index 1e60a072aaa..99ee1998b6e 100644
--- a/source/_posts/2023-02-01-release-20232.markdown
+++ b/source/_posts/2023-02-01-release-20232.markdown
@@ -89,7 +89,7 @@ Go ahead, it is enabled by default; just tap the new Assist icon
at the top right of your dashboard to start using it.
Oh, and we are also releasing some fun stuff we've cooked up along the way!
-[Read more about Assist](/docs/assist/) and other released voice features in the
+[Read more about Assist](/voice_control/) and other released voice features in the
[Chapter 1: Assist](/blog/2023/01/26/year-of-the-voice-chapter-1/) blogpost
and a [video presentation (including live demos) on YouTube](https://www.youtube.com/live/ixgNT3RETPg).
diff --git a/source/_posts/2023-04-27-year-of-the-voice-chapter-2.markdown b/source/_posts/2023-04-27-year-of-the-voice-chapter-2.markdown
index 5da1c972739..383050a3a2a 100644
--- a/source/_posts/2023-04-27-year-of-the-voice-chapter-2.markdown
+++ b/source/_posts/2023-04-27-year-of-the-voice-chapter-2.markdown
@@ -27,7 +27,7 @@ _To watch the video presentation of this blog post, including live demos, check
[Chapter 1]: https://www.home-assistant.io/blog/2023/01/26/year-of-the-voice-chapter-1/
[45 languages]: https://home-assistant.github.io/intents/
[live-stream]: https://youtube.com/live/Tk-pnm7FY7c?feature=share
-[assist]: /docs/assist/
+[assist]: /voice_control/
@@ -52,7 +52,7 @@ Screenshot of the new Assist debug tool.
[Assist Pipeline integration]: https://www.home-assistant.io/integrations/assist_pipeline/
-[Assist dialog]: /docs/assist/
+[Assist dialog]: /voice_control/
## Voice Assistant powered by Home Assistant Cloud
@@ -131,7 +131,7 @@ Today we’re launching support for building voice assistants using ESPHome. Con
We’ve been focusing on the [M5STACK ATOM Echo][atom-echo] for testing and development. For $13 it comes with a microphone and a speaker in a nice little box. We’ve created a tutorial to turn this device into a voice remote directly from your browser!
-[Tutorial: create a $13 voice remote for Home Assistant.](https://www.home-assistant.io/projects/thirteen-usd-voice-remote/)
+[Tutorial: create a $13 voice remote for Home Assistant.](https://www.home-assistant.io/voice_control/thirteen-usd-voice-remote/)
[ESPHome Voice Assistant documentation.](https://esphome.io/components/voice_assistant.html)
@@ -152,7 +152,7 @@ By configuring off-hook autodial, your phone will automatically call Home Assist
We’ve focused our initial efforts on supporting [the Grandstream HT801 Voice-over-IP box][ht801]. It works with any phone with an RJ11 connector, and connects directly to Home Assistant. There is no need for an extra server.
-[Tutorial: create your own World’s Most Private Voice Assistant](https://www.home-assistant.io/projects/worlds-most-private-voice-assistant/)
+[Tutorial: create your own World’s Most Private Voice Assistant](https://www.home-assistant.io/voice_control/worlds-most-private-voice-assistant/)
-This currently supports our [Assist](/docs/assist), and Amazon Alexa and
+This currently supports our [Assist](/voice_control/), and Amazon Alexa and
Google Assistant via Home Assistant Cloud.
## Improved entity setting
@@ -275,7 +277,7 @@ findability. This one is new:
[@tronikos]: https://github.com/tronikos
[android tv remote]: /integrations/androidtv_remote
[Anova]: /integrations/anova
-[assist]: /docs/assist
+[assist]: /voice_control/
[Intellifire]: /integrations/intellifire
[Monessen]: /integrations/monessen
[RAPT Bluetooth]: /integrations/rapt_ble
@@ -406,6 +408,239 @@ The following integrations are now available via the Home Assistant UI:
[transmission docs]: /integrations/transmission/
[zha docs]: /integrations/zha/
+## Release 2023.5.3 - May 14
+
+- Roborock continue on failed mqtt disconnect ([@Lash-L] - [#92502]) ([roborock docs])
+- Bump bimmer_connected to 0.13.3 ([@rikroe] - [#92648]) ([bmw_connected_drive docs])
+- Fix parallel_updates being acquired too late for entity executor jobs ([@bdraco] - [#92681])
+- Always request at least one zone for multi-zone LIFX devices ([@bdraco] - [#92683]) ([lifx docs])
+- Fix onvif reauth when device returns a http 401/403 error ([@bdraco] - [#92690]) ([onvif docs])
+- Bump `aionotion` to 2023.05.1 ([@bachya] - [#92697]) ([notion docs])
+- Bump pyoverkiz to 1.7.8 ([@iMicknl] - [#92702]) ([overkiz docs])
+- Bump aiowebostv to 0.3.3 to fix Python 3.11 support ([@thecode] - [#92736]) ([webostv docs])
+- Update deprecated functions in SIA ([@eavanvalkenburg] - [#92737]) ([sia docs])
+- Bump aioesphomeapi to 3.7.4 to fix proxied BLE connections not retrying right away on error ([@bdraco] - [#92741]) ([esphome docs])
+- Increase timeout to 30 seconds for Mazda integration ([@bdr99] - [#92744]) ([mazda docs])
+- Fix zwave_js services example data ([@karwosts] - [#92748]) ([zwave_js docs])
+- Bump asyncsleepiq to 1.3.5 ([@kbickar] - [#92759]) ([sleepiq docs])
+- Update aioairzone to v0.5.3 ([@Noltari] - [#92780]) ([airzone docs])
+- Fix race in Alexa async_enable_proactive_mode ([@emontnemery] - [#92785]) ([alexa docs])
+- Fix Airzone Auto operation mode ([@Noltari] - [#92796]) ([airzone docs])
+- Update aioairzone to v0.5.5 ([@Noltari] - [#92812]) ([airzone docs])
+- Don't try to restore unavailable nor unknown states ([@dgomes] - [#92825]) ([integration docs])
+- Bump sonos-websocket to 0.1.1 ([@jjlawren] - [#92834]) ([sonos docs])
+- Allow "no" to match "nb" in language util ([@synesthesiam] - [#92862])
+- Bump ZHA dependencies ([@puddly] - [#92870]) ([zha docs])
+- Add ONVIF services to diagnostics ([@bdraco] - [#92878]) ([onvif docs])
+- Bump UPB integration library to 0.5.4 ([@gwww] - [#92879]) ([upb docs])
+- Bump bluetooth-auto-recovery to 1.2.0 ([@bdraco] - [#92893]) ([bluetooth docs])
+- Fix already_configured string in workday ([@gjohansson-ST] - [#92901]) ([workday docs])
+- Fix uptime sensor deviation detection in Fritz!Tools ([@mib1185] - [#92907]) ([fritz docs])
+- Bump volvooncall to 0.10.3 to fix sensor type error ([@decompil3d] - [#92913]) ([volvooncall docs])
+- Bump eternalegypt to 0.0.16 ([@tkdrob] - [#92919]) ([netgear_lte docs])
+- Bump python-vehicle to 1.0.1 ([@joostlek] - [#92933]) ([rdw docs])
+- Fix remove of device when surveillance station is not used in Synology DSM ([@mib1185] - [#92957]) ([synology_dsm docs])
+- Bump reolink-aio to 0.5.15 ([@starkillerOG] - [#92979]) ([reolink docs])
+- Bump bellows to 0.35.5 to fix Aqara Zigbee connectivity issue ([@puddly] - [#92999]) ([zha docs])
+- Disable cleanup_closed for aiohttp.TCPConnector with cpython 3.11.1+ ([@bdraco] - [#93013])
+- Fix sslv2/sslv3 with unverified connections ([@bdraco] - [#93037])
+- Fix a series of bugs due to Notion API changes ([@bachya] - [#93039]) ([notion docs])
+
+[#92422]: https://github.com/home-assistant/core/pull/92422
+[#92502]: https://github.com/home-assistant/core/pull/92502
+[#92513]: https://github.com/home-assistant/core/pull/92513
+[#92610]: https://github.com/home-assistant/core/pull/92610
+[#92648]: https://github.com/home-assistant/core/pull/92648
+[#92681]: https://github.com/home-assistant/core/pull/92681
+[#92683]: https://github.com/home-assistant/core/pull/92683
+[#92690]: https://github.com/home-assistant/core/pull/92690
+[#92697]: https://github.com/home-assistant/core/pull/92697
+[#92702]: https://github.com/home-assistant/core/pull/92702
+[#92736]: https://github.com/home-assistant/core/pull/92736
+[#92737]: https://github.com/home-assistant/core/pull/92737
+[#92741]: https://github.com/home-assistant/core/pull/92741
+[#92744]: https://github.com/home-assistant/core/pull/92744
+[#92748]: https://github.com/home-assistant/core/pull/92748
+[#92759]: https://github.com/home-assistant/core/pull/92759
+[#92780]: https://github.com/home-assistant/core/pull/92780
+[#92785]: https://github.com/home-assistant/core/pull/92785
+[#92796]: https://github.com/home-assistant/core/pull/92796
+[#92812]: https://github.com/home-assistant/core/pull/92812
+[#92825]: https://github.com/home-assistant/core/pull/92825
+[#92834]: https://github.com/home-assistant/core/pull/92834
+[#92862]: https://github.com/home-assistant/core/pull/92862
+[#92870]: https://github.com/home-assistant/core/pull/92870
+[#92878]: https://github.com/home-assistant/core/pull/92878
+[#92879]: https://github.com/home-assistant/core/pull/92879
+[#92893]: https://github.com/home-assistant/core/pull/92893
+[#92901]: https://github.com/home-assistant/core/pull/92901
+[#92907]: https://github.com/home-assistant/core/pull/92907
+[#92913]: https://github.com/home-assistant/core/pull/92913
+[#92919]: https://github.com/home-assistant/core/pull/92919
+[#92933]: https://github.com/home-assistant/core/pull/92933
+[#92957]: https://github.com/home-assistant/core/pull/92957
+[#92979]: https://github.com/home-assistant/core/pull/92979
+[#92999]: https://github.com/home-assistant/core/pull/92999
+[#93013]: https://github.com/home-assistant/core/pull/93013
+[#93037]: https://github.com/home-assistant/core/pull/93037
+[#93039]: https://github.com/home-assistant/core/pull/93039
+[@Lash-L]: https://github.com/Lash-L
+[@Noltari]: https://github.com/Noltari
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@bdr99]: https://github.com/bdr99
+[@bdraco]: https://github.com/bdraco
+[@decompil3d]: https://github.com/decompil3d
+[@dgomes]: https://github.com/dgomes
+[@eavanvalkenburg]: https://github.com/eavanvalkenburg
+[@emontnemery]: https://github.com/emontnemery
+[@frenck]: https://github.com/frenck
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+[@gwww]: https://github.com/gwww
+[@iMicknl]: https://github.com/iMicknl
+[@jjlawren]: https://github.com/jjlawren
+[@joostlek]: https://github.com/joostlek
+[@karwosts]: https://github.com/karwosts
+[@kbickar]: https://github.com/kbickar
+[@mib1185]: https://github.com/mib1185
+[@puddly]: https://github.com/puddly
+[@rikroe]: https://github.com/rikroe
+[@starkillerOG]: https://github.com/starkillerOG
+[@synesthesiam]: https://github.com/synesthesiam
+[@thecode]: https://github.com/thecode
+[@tkdrob]: https://github.com/tkdrob
+[accuweather docs]: /integrations/accuweather/
+[advantage_air docs]: /integrations/advantage_air/
+[airzone docs]: /integrations/airzone/
+[alexa docs]: /integrations/alexa/
+[bluetooth docs]: /integrations/bluetooth/
+[bmw_connected_drive docs]: /integrations/bmw_connected_drive/
+[cloud docs]: /integrations/cloud/
+[esphome docs]: /integrations/esphome/
+[fritz docs]: /integrations/fritz/
+[frontend docs]: /integrations/frontend/
+[integration docs]: /integrations/integration/
+[lifx docs]: /integrations/lifx/
+[mazda docs]: /integrations/mazda/
+[netgear_lte docs]: /integrations/netgear_lte/
+[notion docs]: /integrations/notion/
+[onvif docs]: /integrations/onvif/
+[overkiz docs]: /integrations/overkiz/
+[rdw docs]: /integrations/rdw/
+[reolink docs]: /integrations/reolink/
+[roborock docs]: /integrations/roborock/
+[sia docs]: /integrations/sia/
+[sleepiq docs]: /integrations/sleepiq/
+[sonos docs]: /integrations/sonos/
+[synology_dsm docs]: /integrations/synology_dsm/
+[upb docs]: /integrations/upb/
+[volvooncall docs]: /integrations/volvooncall/
+[webostv docs]: /integrations/webostv/
+[workday docs]: /integrations/workday/
+[zha docs]: /integrations/zha/
+[zwave_js docs]: /integrations/zwave_js/
+
+## Release 2023.5.4 - May 23
+
+- Fix weather handling in zamg ([@killer0071234] - [#85635]) ([zamg docs])
+- Fix onvif cameras that cannot parse relative time ([@bdraco] - [#92711]) ([onvif docs]) (dependency)
+- Update solax state class for sensors with no units ([@MichaelMraka] - [#92914]) ([solax docs])
+- Fix NWS error with no observation ([@MatthewFlamm] - [#92997]) ([nws docs])
+- Increase timeout to 30 seconds for homeassistant_alerts integration ([@N3rdix] - [#93089]) ([homeassistant_alerts docs])
+- Fix ONVIF cameras that change the xaddr for the pull point service ([@bdraco] - [#93104]) ([onvif docs])
+- Bump pyunifiprotect to 4.9.0 ([@bdraco] - [#93106]) ([unifiprotect docs]) (dependency)
+- Fix last imap message is not reset on empty search ([@jbouwh] - [#93119]) ([imap docs])
+- Bump `accuweather` to version 0.5.2 ([@bieniu] - [#93130]) ([accuweather docs]) (dependency)
+- Better handling of source sensor unavailability in Riemman Integration ([@dgomes] - [#93137]) ([integration docs])
+- Bump `regenmaschine` to 2023.05.1 ([@bachya] - [#93139]) ([rainmachine docs]) (dependency)
+- Bump pyatv to 0.11.0 ([@bdraco] - [#93172]) ([apple_tv docs])
+- Fix china login for bmw_connected_drive ([@rikroe] - [#93180]) ([bmw_connected_drive docs])
+- Add Fan and Dry HVAC modes to Advantage Air MyTemp preset ([@Bre77] - [#93189]) ([advantage_air docs])
+- Disconnect yale access locks at the stop event ([@bdraco] - [#93192]) ([august docs]) ([yalexs_ble docs]) (dependency)
+- Add support for Yale Home brand to august ([@bdraco] - [#93214]) ([august docs])
+- Bump async-upnp-client to 0.33.2 ([@StevenLooman] - [#93329]) (dependency)
+- Bump `aionotion` to 2023.05.5 ([@bachya] - [#93334]) ([notion docs])
+- Bump zwave-js-server-python to 0.48.1 ([@raman325] - [#93342]) ([zwave_js docs]) (dependency)
+- Bump glances_api to 0.4.2 ([@freeDom-] - [#93352]) ([glances docs])
+- Fix august configuration url with Yale Home brand ([@bdraco] - [#93361]) ([august docs]) (dependency)
+- Bump httpx to 0.24.1 ([@epenet] - [#93396]) (dependency)
+- Fix non threadsafe call xiaomi_aqara ([@bdraco] - [#93405]) ([xiaomi_aqara docs])
+- Bump Matter server library to 3.4.1 and address changes ([@marcelveldt] - [#93411]) ([matter docs]) (dependency)
+- Fix race in tracking pending writes in recorder ([@bdraco] - [#93414]) ([recorder docs])
+
+[#85635]: https://github.com/home-assistant/core/pull/85635
+[#92422]: https://github.com/home-assistant/core/pull/92422
+[#92513]: https://github.com/home-assistant/core/pull/92513
+[#92610]: https://github.com/home-assistant/core/pull/92610
+[#92711]: https://github.com/home-assistant/core/pull/92711
+[#92914]: https://github.com/home-assistant/core/pull/92914
+[#92997]: https://github.com/home-assistant/core/pull/92997
+[#93066]: https://github.com/home-assistant/core/pull/93066
+[#93089]: https://github.com/home-assistant/core/pull/93089
+[#93104]: https://github.com/home-assistant/core/pull/93104
+[#93106]: https://github.com/home-assistant/core/pull/93106
+[#93119]: https://github.com/home-assistant/core/pull/93119
+[#93130]: https://github.com/home-assistant/core/pull/93130
+[#93137]: https://github.com/home-assistant/core/pull/93137
+[#93139]: https://github.com/home-assistant/core/pull/93139
+[#93172]: https://github.com/home-assistant/core/pull/93172
+[#93180]: https://github.com/home-assistant/core/pull/93180
+[#93189]: https://github.com/home-assistant/core/pull/93189
+[#93192]: https://github.com/home-assistant/core/pull/93192
+[#93214]: https://github.com/home-assistant/core/pull/93214
+[#93329]: https://github.com/home-assistant/core/pull/93329
+[#93334]: https://github.com/home-assistant/core/pull/93334
+[#93342]: https://github.com/home-assistant/core/pull/93342
+[#93352]: https://github.com/home-assistant/core/pull/93352
+[#93361]: https://github.com/home-assistant/core/pull/93361
+[#93396]: https://github.com/home-assistant/core/pull/93396
+[#93405]: https://github.com/home-assistant/core/pull/93405
+[#93411]: https://github.com/home-assistant/core/pull/93411
+[#93414]: https://github.com/home-assistant/core/pull/93414
+[@Bre77]: https://github.com/Bre77
+[@MatthewFlamm]: https://github.com/MatthewFlamm
+[@MichaelMraka]: https://github.com/MichaelMraka
+[@N3rdix]: https://github.com/N3rdix
+[@StevenLooman]: https://github.com/StevenLooman
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@bdraco]: https://github.com/bdraco
+[@bieniu]: https://github.com/bieniu
+[@dgomes]: https://github.com/dgomes
+[@epenet]: https://github.com/epenet
+[@freeDom-]: https://github.com/freeDom-
+[@frenck]: https://github.com/frenck
+[@jbouwh]: https://github.com/jbouwh
+[@killer0071234]: https://github.com/killer0071234
+[@marcelveldt]: https://github.com/marcelveldt
+[@raman325]: https://github.com/raman325
+[@rikroe]: https://github.com/rikroe
+[accuweather docs]: /integrations/accuweather/
+[advantage_air docs]: /integrations/advantage_air/
+[apple_tv docs]: /integrations/apple_tv/
+[august docs]: /integrations/august/
+[bluetooth docs]: /integrations/bluetooth/
+[bmw_connected_drive docs]: /integrations/bmw_connected_drive/
+[cloud docs]: /integrations/cloud/
+[frontend docs]: /integrations/frontend/
+[glances docs]: /integrations/glances/
+[homeassistant_alerts docs]: /integrations/homeassistant_alerts/
+[imap docs]: /integrations/imap/
+[integration docs]: /integrations/integration/
+[lifx docs]: /integrations/lifx/
+[matter docs]: /integrations/matter/
+[notion docs]: /integrations/notion/
+[nws docs]: /integrations/nws/
+[onvif docs]: /integrations/onvif/
+[rainmachine docs]: /integrations/rainmachine/
+[recorder docs]: /integrations/recorder/
+[solax docs]: /integrations/solax/
+[unifiprotect docs]: /integrations/unifiprotect/
+[xiaomi_aqara docs]: /integrations/xiaomi_aqara/
+[yalexs_ble docs]: /integrations/yalexs_ble/
+[zamg docs]: /integrations/zamg/
+[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
diff --git a/source/_posts/2023-06-07-release-20236.markdown b/source/_posts/2023-06-07-release-20236.markdown
new file mode 100644
index 00000000000..e7979838c3d
--- /dev/null
+++ b/source/_posts/2023-06-07-release-20236.markdown
@@ -0,0 +1,869 @@
+---
+layout: post
+title: "2023.6: Network storage, favorite light colors, new integrations dashboard"
+description: "Add and use network storage, the integrations dashboard got a revamp, add your favorite colors to your lights, copy & paste support for automations, blazing speed through Python 3.11, and Matter and Z-Wave updates."
+date: 2023-06-07 00:00:00
+date_formatted: "June 7, 2023"
+author: Franck Nijhof
+author_twitter: frenck
+comments: true
+categories:
+ - Release-Notes
+ - Core
+og_image: /images/blog/2023-06/social.png
+---
+
+
+
+Even better: You can use it as a target for your backups so that when
+Home Assistant creates a backup for you, it will store it directly on
+your network storage.
+
+Multiple network storages are also supported; if you like, you can
+easily add more.
+
+## Integrations dashboard & pages
+
+The integrations dashboard has gotten a major overhaul!
+
+There have been quite some usability issues with the previous version of the
+integration dashboard. For example, if you use [ESPHome] with many devices,
+you are undoubtedly familiar with the annoying scrolling in that little card. Or,
+big error messages stretching those cards out, messing up the whole page.
+
+This release brings in a whole new integrations dashboard that addresses many
+of these issues, aiming to provide a cleaner and more consistent experience.
+
+
+
+Device based integrations, like ESPHome, are combined: no more scrolling.
+A failing integration no longer stretches the layout or makes the
+layout "jump" during retries. Custom integrations and integrations relying
+on the cloud are now more visibly marked.
+
+Selecting the cog icon on the integration card will bring you to a brand new
+integrations page, showing all information about the integration:
+
+
+
+In the above example, the ESPHome integration page shows all devices
+this integration has. All the information and options, previously squashed into
+the integration dashboard, are now available here.
+
+These brand new integration pages are helpful in other places in Home Assistant.
+For example, the device pages can now link back directly to the integration
+that provided it.
+
+[ESPHome]: https://esphome.io
+
+## Light entity dialog improvements: favorite colors
+
+Recently we introduced new controls in the light entity dialog, and this release
+iterates on the design by adding the current brightness, new controls,
+and adding favorite colors! 🎨
+
+
+
+Each light (or light group) has its own set of colors. These colors can
+be added, changed, removed, and reorganized using drag-and-drop. To enter
+edit mode, select and hold one of the colors:
+
+
+
+## Added to the entity dialog: last changed
+
+By popular request, the information on when an entity was last changed has
+been added back to the new entity information dialogs.
+
+Not only that, [@piitaya] added a very nice easter egg! You can click on it
+to toggle between the relative and absolute format!
+
+
+
+Notice how it nicely links back to the new integration page here too!
+
+## Copy 'n paste support in the automation editor
+
+An amazing contribution by [@karwosts] in this release that adds cut, copy
+& paste capabilities to the automation and script editors!
+
+You can now copy and paste any trigger, condition, and action into different
+places of your automation and even paste it into a different automation
+altogether!
+
+
+
+[@karwosts]: https://github.com/karwosts
+
+## Python 3.11 and significant performance upgrades
+
+This release ships running on Python 3.11! In case you are wondering, what is
+that? Well, Python is the language the Core of Home Assistant is written in.
+
+Why it matters? It is seriously faster! 🚀
+
+If you run the Home Assistant Operating System or are using the Home Assistant
+Container installation type: You won't have to do anything as we handle the
+upgrade to Python 3.11 for you.
+
+And that is not all in terms of performance. We've also upgraded internal parts,
+including a newer SQLite version that should be faster. Oh! And, of course,
+[@bdraco] has been all over the place to optimize a lot (a lot lot).
+
+This release can be expected to be a lot faster (or less consuming) of resources
+at runtime.
+
+[@bdraco]: https://github.com/bdraco
+
+## Matter 1.1
+
+The Matter implementation within Home Assistant is now based on the freshly
+released 1.1 version of the Matter standard. This brings a ton of stability
+fixes and improvements, but unfortunately, no new features.
+
+Thanks to [@Diegorro98], we do now have support for tilt covers! Besides that,
+this Home Assistant release ships with several generic bugfixes and
+optimizations; we've managed to squeeze out some additional performance to
+make state updates for your Matter devices lightning-fast 🚀
+
+All these stability improvements to both the Matter stack and our
+implementation did not go unnoticed:
+
+
+How the new time, date, and date/time entities will look like on your dashboards.
+
-Assist is our feature to allow you to control Home Assistant using natural language. It is built on top of an open voice foundation and powered by knowledge provided by our community. You can use the [built-in sentences](/docs/assist/builtin_sentences) to control entities and areas, or [create your own](/docs/assist/custom_sentences).
+Assist is our feature to allow you to control Home Assistant using natural language. It is built on top of an open voice foundation and powered by knowledge provided by our community.
+
+_Want to use Home Assistant with Google Assistant or Amazon Alexa? Get started with [Home Assistant Cloud](https://www.nabucasa.com/config/)._
+
+With Assist, you can use the [built-in sentences](/voice_control/builtin_sentences) to control entities and areas, or [create your own](/voice_control/custom_sentences).
[List of supported languages.](https://developers.home-assistant.io/docs/voice/intent-recognition/supported-languages)
Assist is available to use on most platforms that can interface with Home Assistant. Look for the Assist icon