From 2a47c819d6299e67267b214eedfba8d94cacd1c1 Mon Sep 17 00:00:00 2001 From: Sven Serlier <85389871+wrt54g@users.noreply.github.com> Date: Sat, 27 May 2023 07:27:37 +0200 Subject: [PATCH] Update URLs (#27540) * Update amazon polly URLs * Update URLs * Update URL * Update another URL * Update even more URLs * Update more URLs * Update even more URLs * Update URLs in azure service bus * Update URLs * Update URLs * Update URLs * Update another URL * Update URL * hassio-addons to addons on redirects file --- source/_integrations/amazon_polly.markdown | 2 +- source/_integrations/aws.markdown | 10 +++--- source/_integrations/azure_event_hub.markdown | 16 ++++----- .../_integrations/azure_service_bus.markdown | 8 ++--- source/_integrations/cloudflare.markdown | 2 +- source/_integrations/faa_delays.markdown | 2 +- source/_integrations/facebook.markdown | 8 ++--- source/_integrations/microsoft.markdown | 10 +++--- source/_integrations/microsoft_face.markdown | 6 ++-- .../microsoft_face_detect.markdown | 8 ++--- .../microsoft_face_identify.markdown | 8 ++--- source/_integrations/msteams.markdown | 2 +- source/_redirects | 36 +++++++++---------- 13 files changed, 59 insertions(+), 59 deletions(-) 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/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/cloudflare.markdown b/source/_integrations/cloudflare.markdown index 39c228b59ab..3a15802a7bd 100644 --- a/source/_integrations/cloudflare.markdown +++ b/source/_integrations/cloudflare.markdown @@ -23,7 +23,7 @@ The setup requires an API Token created with `Zone:Zone:Read` and `Zone:DNS:Edit An easy way to create this is to start with the "Edit zone DNS" template then add `Zone:Zone:Read` to the permissions. -[Cloudflare API Tokens Guide](https://developers.cloudflare.com/api/tokens/create) +[Cloudflare API Tokens Guide](https://developers.cloudflare.com/fundamentals/api/get-started/create-token/) {% include integrations/config_flow.md %} 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/microsoft.markdown b/source/_integrations/microsoft.markdown index f5be4789b09..d06220d1d2f 100644 --- a/source/_integrations/microsoft.markdown +++ b/source/_integrations/microsoft.markdown @@ -11,7 +11,7 @@ ha_platforms: ha_integration_type: integration --- -The `microsoft` text-to-speech platform uses the [TTS engine of the Microsoft Speech Service](https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/text-to-speech) to read a text with natural sounding voices. This integration uses an API that is part of the Cognitive Services offering and is known as the Microsoft Speech API. For this integration to work, you need a free API key. You can use your [Azure subscription](https://azure.microsoft.com) to create an [Azure Speech resource](https://portal.azure.com/#create/Microsoft.CognitiveServicesSpeechServices). +The `microsoft` text-to-speech platform uses the [TTS engine of the Microsoft Speech Service](https://learn.microsoft.com/azure/cognitive-services/speech-service/text-to-speech) to read a text with natural sounding voices. This integration uses an API that is part of the Cognitive Services offering and is known as the Microsoft Speech API. For this integration to work, you need a free API key. You can use your [Azure subscription](https://azure.microsoft.com) to create an [Azure Speech resource](https://portal.azure.com/#create/Microsoft.CognitiveServicesSpeechServices). ## Configuration @@ -40,7 +40,7 @@ gender: type: string default: "`Female`" type: - description: "The voice type you want to use. Accepted values are listed as the service name mapping [in the documentation](https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/language-support#text-to-speech)." + description: "The voice type you want to use. Accepted values are listed as the service name mapping [in the documentation](https://learn.microsoft.com/azure/cognitive-services/speech-service/language-support?tabs=tts)." required: false type: string default: "`JennyNeural`" @@ -64,7 +64,7 @@ contour: required: false type: string region: - description: "The region of your API endpoint. See [documentation](https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/regions)." + description: "The region of your API endpoint. See [documentation](https://learn.microsoft.com/azure/cognitive-services/speech-service/regions)." required: false type: string default: "`eastus`" @@ -72,9 +72,9 @@ region:
-Not all Azure regions support high-quality neural voices. Use [this overview](https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/regions#neural-and-standard-voices) to determine the availability of standard and neural voices by region/endpoint. +Not all Azure regions support high-quality neural voices. Use [this overview](https://learn.microsoft.com/azure/cognitive-services/speech-service/regions) to determine the availability of standard and neural voices by region/endpoint. -New users ([any newly created Azure Speech resource after August 31st, 2021](https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/text-to-speech#migrate-to-neural-voice)) can only use neural voices. Existing resources can continue using standard voices through August 31st, 2024. +New users ([any newly created Azure Speech resource after August 31st, 2021](https://learn.microsoft.com/azure/cognitive-services/speech-service/text-to-speech#more-about-neural-text-to-speech-features)) can only use neural voices. Existing resources can continue using standard voices through August 31st, 2024.
diff --git a/source/_integrations/microsoft_face.markdown b/source/_integrations/microsoft_face.markdown index 4ea089778cf..9a8ac714e33 100644 --- a/source/_integrations/microsoft_face.markdown +++ b/source/_integrations/microsoft_face.markdown @@ -11,17 +11,17 @@ ha_integration_type: integration The `microsoft_face` integration platform is the main integration for Microsoft Azure Cognitive service -[Face](https://azure.microsoft.com/en-us/services/cognitive-services/face/). +[Face](https://azure.microsoft.com/products/cognitive-services/vision-services). All data are stored in your own private instance in the Azure cloud. ## Setup You need an API key, which is free, but requires an -[Azure registration](https://azure.microsoft.com/en-us/free/) using your +[Azure registration](https://azure.microsoft.com/free/) using your Microsoft ID. The free resource (*F0*) is limited to 20 requests per minute and 30k requests in a month. If you don't want to use the Azure cloud, you can also get an API key by registering with -[cognitive-services](https://azure.microsoft.com/en-us/try/cognitive-services/). +[cognitive-services](https://azure.microsoft.com/try/cognitive-services/). Please note that all keys on cognitive services must be recreated every 90 days. ## Configuration diff --git a/source/_integrations/microsoft_face_detect.markdown b/source/_integrations/microsoft_face_detect.markdown index fcf5baef9b9..04fa1ef6675 100644 --- a/source/_integrations/microsoft_face_detect.markdown +++ b/source/_integrations/microsoft_face_detect.markdown @@ -10,19 +10,19 @@ ha_integration_type: integration --- The `microsoft_face_detect` image processing platform allows you to use the -[Microsoft Face Identify](https://www.microsoft.com/cognitive-services/en-us/) +[Microsoft Face Identify](https://azure.microsoft.com/products/cognitive-services/) API through Home Assistant. This platform enables you to detect face on camera and fire an event with attributes. -Please refer to the [Microsoft Face component](/integrations/microsoft_face/) configuration on +Please refer to the [Microsoft Face integration](/integrations/microsoft_face/) configuration on how to setup the API key. For using the result inside an automation rule, -take a look at the [Image Processing component](/integrations/image_processing/) page. +take a look at the [Image Processing integration](/integrations/image_processing/) page.
-The free version of the Microsoft Face identify API limits the number of requests possible per month. Therefore, it is strongly recommended that you limit the `scan_interval` when setting up an instance of this entity as detailed on the main [Image Processing component](/integrations/image_processing/) page. +The free version of the Microsoft Face identify API limits the number of requests possible per month. Therefore, it is strongly recommended that you limit the `scan_interval` when setting up an instance of this entity as detailed on the main [Image Processing integration](/integrations/image_processing/) page.
diff --git a/source/_integrations/microsoft_face_identify.markdown b/source/_integrations/microsoft_face_identify.markdown index 5a561eb1ce4..66646455ca3 100644 --- a/source/_integrations/microsoft_face_identify.markdown +++ b/source/_integrations/microsoft_face_identify.markdown @@ -10,19 +10,19 @@ ha_integration_type: integration --- The `microsoft_face_identify` image processing platform lets you use -[Microsoft Face identify](https://www.microsoft.com/cognitive-services/en-us/) +[Microsoft Face identify](https://azure.microsoft.com/products/cognitive-services/) API through Home Assistant. This platform allow you do identify persons on camera and fire an event with attributes. -Please refer to the [Microsoft Face component](/integrations/microsoft_face/) configuration on +Please refer to the [Microsoft Face integration](/integrations/microsoft_face/) configuration on how to setup the API key. For using the result inside an automation rule, -take a look at the [Image Processing component](/integrations/image_processing/) page. +take a look at the [Image Processing integration](/integrations/image_processing/) page.
-The free version of the Microsoft Face identify API limits the number of requests possible per month. Therefore, it is strongly recommended that you limit the `scan_interval` when setting up an instance of this entity as detailed on the main [Image Processing component](/integrations/image_processing/) page. +The free version of the Microsoft Face identify API limits the number of requests possible per month. Therefore, it is strongly recommended that you limit the `scan_interval` when setting up an instance of this entity as detailed on the main [Image Processing integration](/integrations/image_processing/) page.
diff --git a/source/_integrations/msteams.markdown b/source/_integrations/msteams.markdown index e571f8376bb..83af0d261c5 100644 --- a/source/_integrations/msteams.markdown +++ b/source/_integrations/msteams.markdown @@ -13,7 +13,7 @@ ha_platforms: ha_integration_type: integration --- -The `Microsoft Teams` platform allows you to send notifications from Home Assistant to a team channel in [Microsoft Teams](https://products.office.com/en-us/microsoft-teams/group-chat-software). +The `Microsoft Teams` platform allows you to send notifications from Home Assistant to a team channel in [Microsoft Teams](https://www.microsoft.com/microsoft-teams/group-chat-software). ## Setup diff --git a/source/_redirects b/source/_redirects index 9e7e5b5c2bc..7a2b5732910 100644 --- a/source/_redirects +++ b/source/_redirects @@ -376,24 +376,24 @@ layout: null /getting-started/autostart-systemd https://community.home-assistant.io/t/autostart-using-systemd/199497 # Add-ons -/addons/cec_scan https://github.com/home-assistant/hassio-addons/blob/master/cec_scan/README.md -/addons/check_config https://github.com/home-assistant/hassio-addons/blob/master/check_config/README.md -/addons/configurator https://github.com/home-assistant/hassio-addons/blob/master/configurator/README.md -/addons/dhcp_server https://github.com/home-assistant/hassio-addons/blob/master/dhcp_server/README.md -/addons/dnsmasq https://github.com/home-assistant/hassio-addons/blob/master/dnsmasq/README.md -/addons/duckdns https://github.com/home-assistant/hassio-addons/blob/master/duckdns/README.md -/addons/git_pull https://github.com/home-assistant/hassio-addons/blob/master/git_pull/README.md -/addons/google_assistant https://github.com/home-assistant/hassio-addons/blob/master/google_assistant/README.md -/addons/homematic https://github.com/home-assistant/hassio-addons/blob/master/homematic/README.md -/addons/lets_encrypt https://github.com/home-assistant/hassio-addons/blob/master/letsencrypt/README.md -/addons/mariadb https://github.com/home-assistant/hassio-addons/blob/master/mariadb/README.md -/addons/mosquitto https://github.com/home-assistant/hassio-addons/blob/master/mosquitto/README.md -/addons/nginx_proxy https://github.com/home-assistant/hassio-addons/blob/master/nginx_proxy/README.md -/addons/rpc_shutdown https://github.com/home-assistant/hassio-addons/blob/master/rpc_shutdown/README.md -/addons/samba https://github.com/home-assistant/hassio-addons/blob/master/samba/README.md -/addons/snips https://github.com/home-assistant/hassio-addons/blob/master/snips/README.md -/addons/ssh https://github.com/home-assistant/hassio-addons/blob/master/ssh/README.md -/addons/tellstick https://github.com/home-assistant/hassio-addons/blob/master/tellstick/README.md +/addons/cec_scan https://github.com/home-assistant/addons/blob/master/cec_scan/README.md +/addons/check_config https://github.com/home-assistant/addons/blob/master/check_config/README.md +/addons/configurator https://github.com/home-assistant/addons/blob/master/configurator/README.md +/addons/dhcp_server https://github.com/home-assistant/addons/blob/master/dhcp_server/README.md +/addons/dnsmasq https://github.com/home-assistant/addons/blob/master/dnsmasq/README.md +/addons/duckdns https://github.com/home-assistant/addons/blob/master/duckdns/README.md +/addons/git_pull https://github.com/home-assistant/addons/blob/master/git_pull/README.md +/addons/google_assistant https://github.com/home-assistant/addons/blob/master/google_assistant/README.md +/addons/homematic https://github.com/home-assistant/addons/blob/master/homematic/README.md +/addons/lets_encrypt https://github.com/home-assistant/addons/blob/master/letsencrypt/README.md +/addons/mariadb https://github.com/home-assistant/addons/blob/master/mariadb/README.md +/addons/mosquitto https://github.com/home-assistant/addons/blob/master/mosquitto/README.md +/addons/nginx_proxy https://github.com/home-assistant/addons/blob/master/nginx_proxy/README.md +/addons/rpc_shutdown https://github.com/home-assistant/addons/blob/master/rpc_shutdown/README.md +/addons/samba https://github.com/home-assistant/addons/blob/master/samba/README.md +/addons/snips https://github.com/home-assistant/addons/blob/master/snips/README.md +/addons/ssh https://github.com/home-assistant/addons/blob/master/ssh/README.md +/addons/tellstick https://github.com/home-assistant/addons/blob/master/tellstick/README.md # Redirect old /demo to new demo page /demo https://demo.home-assistant.io