From 873ca99af27002ac60276a23a0d71b7509d101e0 Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Fri, 23 May 2025 13:50:58 +0200 Subject: [PATCH 01/16] Add docs for Backblaze B2 integration --- .vscode/cSpell.json | 1 + source/_integrations/backblaze_b2.markdown | 96 ++++++++++++++++++++++ 2 files changed, 97 insertions(+) create mode 100644 source/_integrations/backblaze_b2.markdown diff --git a/.vscode/cSpell.json b/.vscode/cSpell.json index 8fd7b5cbd2f3..3e70c11caa2c 100644 --- a/.vscode/cSpell.json +++ b/.vscode/cSpell.json @@ -11,6 +11,7 @@ "autodiscovery", "autoheal", "automations", + "Backblaze", "balloob", "bloomsky", "Bluesound", diff --git a/source/_integrations/backblaze_b2.markdown b/source/_integrations/backblaze_b2.markdown new file mode 100644 index 000000000000..133d9ce04aee --- /dev/null +++ b/source/_integrations/backblaze_b2.markdown @@ -0,0 +1,96 @@ +--- +title: Backblaze B2 +description: Instructions on how to setup a Backblaze B2 bucket to be used as a backup location. +ha_release: 2025.6 +ha_category: + - Backup +ha_iot_class: Cloud Push +ha_config_flow: true +ha_domain: backblaze_b2 +ha_codeowners: + - '@hugo-vrijswijk' +ha_integration_type: service +ha_quality_scale: bronze +--- + +The **Backblaze B2** {% term integration %} allows you to use a [Backblaze B2](https://www.backblaze.com/cloud-storage) bucket for use with Home Assistant Backups. + +## Prerequisites + +This integration requires an existing B2 bucket and application key that has access to that bucket. It is recommended to create a key that only has access to the required bucket and prefix (if desired). + +{% details "Create a new B2 bucket" %} + +1. Log in to the [B2 Console](https://secure.backblaze.com/b2_buckets.htm). +2. Navigate to **Buckets** from the sidebar menu. +3. Click **Create bucket**. +4. Choose a unique **bucket name** (e.g., `home-assistant-backups-123456`). +5. Adjust the settings: + - ✅ **Set bucket to private** (enabled by default, recommended) + - ⚠️ **Encryption** This enables Backblaze's server-side encryption. This is separate from the Home Assistant backup encryption. This is optional. If Home Assistant backups are configured to use encryption, you can disable this. +6. Click **Create bucket**. + +Make a note of the bucket name — you’ll need it later. + +{% enddetails %} + +{% details "Create an application key" %} + +To create a application key that can access the bucket: + +1. Go to [**Application Keys**](https://secure.backblaze.com/app_keys.htm) in the sidebar. +2. Click **Add a New Application Key**. +3. Use a name like `home-assistant-backup`. +4. Limit access to the bucket you created earlier by selecting it from the **Choose a bucket** dropdown. +5. Type of access should be **Read and Write**. +6. **Allow List All Bucket Names** can be left unchecked. +7. Optionally, you can limit the key to a specific prefix (e.g., `home-assistant-backups`) if you want to save backups in a specific folder within the bucket. +8. Click **Create New Key**. + +Save the **Key ID** and **Application Key** — you'll need these when setting up the Backblaze B2 integration in Home Assistant. + +{% enddetails %} + +{% note %} + +- By limiting credentials to a specific bucket, you reduce risk and help keep your Backblaze account secure. + +{% endnote %} + +{% include integrations/config_flow.md %} + +{% configuration_basic %} +Key ID: + description: "The access key ID for your Backblaze B2 account." +Application Key: + description: "The application key for your Backblaze B2 account." +Bucket Name: + description: "B2 bucket name to store the backups. Bucket must already exist and be writable by the provided credentials." +Prefix: + description: "Optional prefix for the backups. This is useful if you want to store backups in a specific folder within the bucket." +{% endconfiguration_basic %} + +## Setting up the Backblaze B2 integration in Home Assistant + +1. In Home Assistant, go to **Settings > Devices & Services**. +1. Click **Add Integration** and search for **Backblaze B2**. +1. Enter the following details: + - Access Key ID and Application Key from the B2 Console + - Your bucket name + - (Optional) Prefix for the backups +1. Click **Submit**. + +The integration will test the connection and confirm access to your bucket. + +## Known limitations + +The Backblaze integration has the following limitations: + +- Expired keys: If the application key expires, you will need to create a new one and update the integration in Home Assistant. +- Prefix: If you set a prefix, all backups will be stored under that prefix in the bucket. Ensure that the prefix is unique to avoid overwriting other files. Changing the prefix will not move existing backups. + +## Removing the integration + +This integration follows standard integration removal. No extra steps are required. + +{% include integrations/remove_device_service.md %} From a4ffc9b9f697799d1485d8d86e28fc632ff580c1 Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Fri, 23 May 2025 14:24:37 +0200 Subject: [PATCH 02/16] Update source/_integrations/backblaze_b2.markdown Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- source/_integrations/backblaze_b2.markdown | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/source/_integrations/backblaze_b2.markdown b/source/_integrations/backblaze_b2.markdown index 133d9ce04aee..7a6528c1fa29 100644 --- a/source/_integrations/backblaze_b2.markdown +++ b/source/_integrations/backblaze_b2.markdown @@ -72,14 +72,15 @@ Prefix: ## Setting up the Backblaze B2 integration in Home Assistant +## Setting up the Backblaze B2 integration in Home Assistant + 1. In Home Assistant, go to **Settings > Devices & Services**. -1. Click **Add Integration** and search for **Backblaze B2**. -1. Enter the following details: +2. Click **Add Integration** and search for **Backblaze B2**. +3. Enter the following details: - Access Key ID and Application Key from the B2 Console - Your bucket name - (Optional) Prefix for the backups -1. Click **Submit**. - +4. Click **Submit**. The integration will test the connection and confirm access to your bucket. ## Known limitations From 7021ec1f57e3bb62617b42f96c3553cadb5ef9d3 Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Fri, 23 May 2025 12:30:13 +0000 Subject: [PATCH 03/16] Remove duplicate heading added by AI suggestion --- source/_integrations/backblaze_b2.markdown | 2 -- 1 file changed, 2 deletions(-) diff --git a/source/_integrations/backblaze_b2.markdown b/source/_integrations/backblaze_b2.markdown index 7a6528c1fa29..60475ed5b745 100644 --- a/source/_integrations/backblaze_b2.markdown +++ b/source/_integrations/backblaze_b2.markdown @@ -72,8 +72,6 @@ Prefix: ## Setting up the Backblaze B2 integration in Home Assistant -## Setting up the Backblaze B2 integration in Home Assistant - 1. In Home Assistant, go to **Settings > Devices & Services**. 2. Click **Add Integration** and search for **Backblaze B2**. 3. Enter the following details: From 252a280813fa3f78635a6d980da725435ad97ddd Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Fri, 23 May 2025 12:38:43 +0000 Subject: [PATCH 04/16] Minor language changes --- source/_integrations/backblaze_b2.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_integrations/backblaze_b2.markdown b/source/_integrations/backblaze_b2.markdown index 60475ed5b745..211ffeb23c18 100644 --- a/source/_integrations/backblaze_b2.markdown +++ b/source/_integrations/backblaze_b2.markdown @@ -13,11 +13,11 @@ ha_integration_type: service ha_quality_scale: bronze --- -The **Backblaze B2** {% term integration %} allows you to use a [Backblaze B2](https://www.backblaze.com/cloud-storage) bucket for use with Home Assistant Backups. +The **Backblaze B2** {% term integration %} enables you to use a [Backblaze B2](https://www.backblaze.com/cloud-storage) bucket as a backup location in Home Assistant. ## Prerequisites -This integration requires an existing B2 bucket and application key that has access to that bucket. It is recommended to create a key that only has access to the required bucket and prefix (if desired). +This integration requires an existing B2 bucket and an application key that has access to that bucket. It is recommended to create a key that only has access to the required bucket and prefix (if desired). {% details "Create a new B2 bucket" %} @@ -36,13 +36,13 @@ Make a note of the bucket name — you’ll need it later. {% details "Create an application key" %} -To create a application key that can access the bucket: +To create an application key that can access the bucket: 1. Go to [**Application Keys**](https://secure.backblaze.com/app_keys.htm) in the sidebar. 2. Click **Add a New Application Key**. 3. Use a name like `home-assistant-backup`. 4. Limit access to the bucket you created earlier by selecting it from the **Choose a bucket** dropdown. -5. Type of access should be **Read and Write**. +5. The type of access should be **Read and Write**. 6. **Allow List All Bucket Names** can be left unchecked. 7. Optionally, you can limit the key to a specific prefix (e.g., `home-assistant-backups`) if you want to save backups in a specific folder within the bucket. 8. Click **Create New Key**. From 2f73c96565e67e3a64ae56c40853b4ae3553cf22 Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Mon, 26 May 2025 07:30:57 +0000 Subject: [PATCH 05/16] Rename backblaze_b2 to backblaze --- ...ckblaze_b2.markdown => backblaze.markdown} | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) rename source/_integrations/{backblaze_b2.markdown => backblaze.markdown} (79%) diff --git a/source/_integrations/backblaze_b2.markdown b/source/_integrations/backblaze.markdown similarity index 79% rename from source/_integrations/backblaze_b2.markdown rename to source/_integrations/backblaze.markdown index 211ffeb23c18..649842ba860e 100644 --- a/source/_integrations/backblaze_b2.markdown +++ b/source/_integrations/backblaze.markdown @@ -1,19 +1,19 @@ --- -title: Backblaze B2 +title: Backblaze description: Instructions on how to setup a Backblaze B2 bucket to be used as a backup location. ha_release: 2025.6 ha_category: - Backup ha_iot_class: Cloud Push ha_config_flow: true -ha_domain: backblaze_b2 +ha_domain: backblaze ha_codeowners: - '@hugo-vrijswijk' ha_integration_type: service ha_quality_scale: bronze --- -The **Backblaze B2** {% term integration %} enables you to use a [Backblaze B2](https://www.backblaze.com/cloud-storage) bucket as a backup location in Home Assistant. +The **Backblaze** {% term integration %} enables you to use a [Backblaze B2](https://www.backblaze.com/cloud-storage) bucket as a backup location in Home Assistant. ## Prerequisites @@ -21,7 +21,7 @@ This integration requires an existing B2 bucket and an application key that has {% details "Create a new B2 bucket" %} -1. Log in to the [B2 Console](https://secure.backblaze.com/b2_buckets.htm). +1. Log in to the [Backblaze Console](https://secure.backblaze.com/b2_buckets.htm). 2. Navigate to **Buckets** from the sidebar menu. 3. Click **Create bucket**. 4. Choose a unique **bucket name** (e.g., `home-assistant-backups-123456`). @@ -47,7 +47,7 @@ To create an application key that can access the bucket: 7. Optionally, you can limit the key to a specific prefix (e.g., `home-assistant-backups`) if you want to save backups in a specific folder within the bucket. 8. Click **Create New Key**. -Save the **Key ID** and **Application Key** — you'll need these when setting up the Backblaze B2 integration in Home Assistant. +Save the **Key ID** and **Application Key** — you'll need these when setting up the Backblaze integration in Home Assistant. {% enddetails %} @@ -61,21 +61,21 @@ Save the **Key ID** and **Application Key** — you'll need these when setting u {% configuration_basic %} Key ID: - description: "The access key ID for your Backblaze B2 account." + description: "The access key ID for your Backblaze account." Application Key: - description: "The application key for your Backblaze B2 account." + description: "The application key for your Backblaze account." Bucket Name: - description: "B2 bucket name to store the backups. Bucket must already exist and be writable by the provided credentials." + description: "Bucket name to store the backups. Bucket must already exist and be writable by the provided credentials." Prefix: description: "Optional prefix for the backups. This is useful if you want to store backups in a specific folder within the bucket." {% endconfiguration_basic %} -## Setting up the Backblaze B2 integration in Home Assistant +## Setting up the Backblaze integration in Home Assistant 1. In Home Assistant, go to **Settings > Devices & Services**. -2. Click **Add Integration** and search for **Backblaze B2**. +2. Click **Add Integration** and search for **Backblaze**. 3. Enter the following details: - - Access Key ID and Application Key from the B2 Console + - Access Key ID and Application Key from the Backblaze Console - Your bucket name - (Optional) Prefix for the backups 4. Click **Submit**. From 4185e440d0f391c99cc154a0d37fd7745c1be72e Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Mon, 26 May 2025 07:31:36 +0000 Subject: [PATCH 06/16] Update ha_release to 2025.7 --- source/_integrations/backblaze.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/backblaze.markdown b/source/_integrations/backblaze.markdown index 649842ba860e..b4c32e9828c7 100644 --- a/source/_integrations/backblaze.markdown +++ b/source/_integrations/backblaze.markdown @@ -1,7 +1,7 @@ --- title: Backblaze description: Instructions on how to setup a Backblaze B2 bucket to be used as a backup location. -ha_release: 2025.6 +ha_release: 2025.7 ha_category: - Backup ha_iot_class: Cloud Push From 5da25f8985632aa6ec8138864e5e7468178ef0c0 Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Thu, 25 Sep 2025 09:53:04 +0200 Subject: [PATCH 07/16] Apply suggestion from @c0ffeeca7 Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/backblaze.markdown | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/source/_integrations/backblaze.markdown b/source/_integrations/backblaze.markdown index b4c32e9828c7..5c350375f253 100644 --- a/source/_integrations/backblaze.markdown +++ b/source/_integrations/backblaze.markdown @@ -22,15 +22,12 @@ This integration requires an existing B2 bucket and an application key that has {% details "Create a new B2 bucket" %} 1. Log in to the [Backblaze Console](https://secure.backblaze.com/b2_buckets.htm). -2. Navigate to **Buckets** from the sidebar menu. -3. Click **Create bucket**. -4. Choose a unique **bucket name** (e.g., `home-assistant-backups-123456`). -5. Adjust the settings: - - ✅ **Set bucket to private** (enabled by default, recommended) - - ⚠️ **Encryption** This enables Backblaze's server-side encryption. This is separate from the Home Assistant backup encryption. This is optional. If Home Assistant backups are configured to use encryption, you can disable this. -6. Click **Create bucket**. - -Make a note of the bucket name — you’ll need it later. +2. [Create a bucket](https://www.backblaze.com/docs/cloud-storage-create-and-manage-buckets). + - Choose a unique **bucket name** (such as, `home-assistant-backups-123456`). + - Make a note of the bucket name — you’ll need it later. +3. Adjust the settings: + - **Set bucket to private**: Enabled by default, recommended. + - **Encryption**: This enables Backblaze's server-side encryption. This is separate from the Home Assistant backup encryption. This is optional. If Home Assistant backups are configured to use encryption, you can disable this. {% enddetails %} From b6bfbe495a7d2a25599dd84813d5fda26732ce60 Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Thu, 25 Sep 2025 09:53:16 +0200 Subject: [PATCH 08/16] Apply suggestion from @c0ffeeca7 Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/backblaze.markdown | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/source/_integrations/backblaze.markdown b/source/_integrations/backblaze.markdown index 5c350375f253..996c15bae91e 100644 --- a/source/_integrations/backblaze.markdown +++ b/source/_integrations/backblaze.markdown @@ -36,15 +36,13 @@ This integration requires an existing B2 bucket and an application key that has To create an application key that can access the bucket: 1. Go to [**Application Keys**](https://secure.backblaze.com/app_keys.htm) in the sidebar. -2. Click **Add a New Application Key**. -3. Use a name like `home-assistant-backup`. -4. Limit access to the bucket you created earlier by selecting it from the **Choose a bucket** dropdown. -5. The type of access should be **Read and Write**. -6. **Allow List All Bucket Names** can be left unchecked. -7. Optionally, you can limit the key to a specific prefix (e.g., `home-assistant-backups`) if you want to save backups in a specific folder within the bucket. -8. Click **Create New Key**. - -Save the **Key ID** and **Application Key** — you'll need these when setting up the Backblaze integration in Home Assistant. +2. [Create a new application key](https://www.backblaze.com/docs/cloud-storage-create-and-manage-app-keys). + - Use a name like `home-assistant-backup`. + - Limit access to the bucket by selecting it from the **Choose a bucket** dropdown. + - The type of access should be **Read and Write**. + - **Allow List All Bucket Names** can be left unchecked. + - Optionally, you can limit the key to a specific prefix (such as `home-assistant-backups`) if you want to save backups in a specific folder within the bucket. +3. Save the **Key ID** and **Application Key**. You'll need these when setting up the Backblaze integration in Home Assistant. {% enddetails %} From 5b877feb8a71ab1a02e4a3bcc3f45100719bc9c6 Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Thu, 25 Sep 2025 09:53:27 +0200 Subject: [PATCH 09/16] Apply suggestion from @c0ffeeca7 Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/backblaze.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/backblaze.markdown b/source/_integrations/backblaze.markdown index 996c15bae91e..b2b8251a5bbc 100644 --- a/source/_integrations/backblaze.markdown +++ b/source/_integrations/backblaze.markdown @@ -76,7 +76,7 @@ Prefix: 4. Click **Submit**. The integration will test the connection and confirm access to your bucket. -## Known limitations +## Troubleshooting The Backblaze integration has the following limitations: From d028fbae7970a499b5e635e43449942397d253ac Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Thu, 25 Sep 2025 09:53:51 +0200 Subject: [PATCH 10/16] Apply suggestion from @c0ffeeca7 Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/backblaze.markdown | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/_integrations/backblaze.markdown b/source/_integrations/backblaze.markdown index b2b8251a5bbc..2261fa9a5888 100644 --- a/source/_integrations/backblaze.markdown +++ b/source/_integrations/backblaze.markdown @@ -80,7 +80,9 @@ The integration will test the connection and confirm access to your bucket. The Backblaze integration has the following limitations: -- Expired keys: If the application key expires, you will need to create a new one and update the integration in Home Assistant. +### Expired keys + +If the application key expires, you will need to create a new one and update the integration in Home Assistant. - Prefix: If you set a prefix, all backups will be stored under that prefix in the bucket. Ensure that the prefix is unique to avoid overwriting other files. Changing the prefix will not move existing backups. ## Removing the integration From 08ada36ab0fe9b2040a45f1740dddb709010039f Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Thu, 25 Sep 2025 09:54:13 +0200 Subject: [PATCH 11/16] Apply suggestion from @c0ffeeca7 Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/backblaze.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/_integrations/backblaze.markdown b/source/_integrations/backblaze.markdown index 2261fa9a5888..a9c7440daa6a 100644 --- a/source/_integrations/backblaze.markdown +++ b/source/_integrations/backblaze.markdown @@ -78,7 +78,6 @@ The integration will test the connection and confirm access to your bucket. ## Troubleshooting -The Backblaze integration has the following limitations: ### Expired keys From 23f9163e9fe38d41f30998b7b721c14d62fdf296 Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Thu, 25 Sep 2025 09:54:27 +0200 Subject: [PATCH 12/16] Apply suggestion from @c0ffeeca7 Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/backblaze.markdown | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/_integrations/backblaze.markdown b/source/_integrations/backblaze.markdown index a9c7440daa6a..874d285d9733 100644 --- a/source/_integrations/backblaze.markdown +++ b/source/_integrations/backblaze.markdown @@ -82,7 +82,9 @@ The integration will test the connection and confirm access to your bucket. ### Expired keys If the application key expires, you will need to create a new one and update the integration in Home Assistant. -- Prefix: If you set a prefix, all backups will be stored under that prefix in the bucket. Ensure that the prefix is unique to avoid overwriting other files. Changing the prefix will not move existing backups. +### Files are being overwritten due to non-unique bucket prefix + +If you set a prefix, all backups will be stored under that prefix in the bucket. Ensure that the prefix is unique to avoid overwriting other files. Changing the prefix will not move existing backups. ## Removing the integration From 2dbbfbcb90fda0cd47d2f3705a080d2d3e692851 Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Thu, 25 Sep 2025 09:54:48 +0200 Subject: [PATCH 13/16] Apply suggestion from @c0ffeeca7 Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/backblaze.markdown | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/source/_integrations/backblaze.markdown b/source/_integrations/backblaze.markdown index 874d285d9733..239d6ddf4835 100644 --- a/source/_integrations/backblaze.markdown +++ b/source/_integrations/backblaze.markdown @@ -65,16 +65,6 @@ Prefix: description: "Optional prefix for the backups. This is useful if you want to store backups in a specific folder within the bucket." {% endconfiguration_basic %} -## Setting up the Backblaze integration in Home Assistant - -1. In Home Assistant, go to **Settings > Devices & Services**. -2. Click **Add Integration** and search for **Backblaze**. -3. Enter the following details: - - Access Key ID and Application Key from the Backblaze Console - - Your bucket name - - (Optional) Prefix for the backups -4. Click **Submit**. -The integration will test the connection and confirm access to your bucket. ## Troubleshooting From 3c89742d4af8b24c4a3e929371838e059f4aea34 Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Thu, 25 Sep 2025 09:58:39 +0200 Subject: [PATCH 14/16] Rename to backblaze_b2 --- ...ackblaze.markdown => backblaze_b2.markdown} | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) rename source/_integrations/{backblaze.markdown => backblaze_b2.markdown} (87%) diff --git a/source/_integrations/backblaze.markdown b/source/_integrations/backblaze_b2.markdown similarity index 87% rename from source/_integrations/backblaze.markdown rename to source/_integrations/backblaze_b2.markdown index 239d6ddf4835..4d8ce9024bbe 100644 --- a/source/_integrations/backblaze.markdown +++ b/source/_integrations/backblaze_b2.markdown @@ -1,13 +1,14 @@ --- -title: Backblaze +title: Backblaze B2 description: Instructions on how to setup a Backblaze B2 bucket to be used as a backup location. -ha_release: 2025.7 +ha_release: 2025.10 ha_category: - Backup ha_iot_class: Cloud Push ha_config_flow: true -ha_domain: backblaze +ha_domain: backblaze_b2 ha_codeowners: + - 'ElCruncharino' - '@hugo-vrijswijk' ha_integration_type: service ha_quality_scale: bronze @@ -56,22 +57,21 @@ To create an application key that can access the bucket: {% configuration_basic %} Key ID: - description: "The access key ID for your Backblaze account." +description: "The access key ID for your Backblaze account." Application Key: - description: "The application key for your Backblaze account." +description: "The application key for your Backblaze account." Bucket Name: - description: "Bucket name to store the backups. Bucket must already exist and be writable by the provided credentials." +description: "Bucket name to store the backups. Bucket must already exist and be writable by the provided credentials." Prefix: - description: "Optional prefix for the backups. This is useful if you want to store backups in a specific folder within the bucket." +description: "Optional prefix for the backups. This is useful if you want to store backups in a specific folder within the bucket." {% endconfiguration_basic %} - ## Troubleshooting - ### Expired keys If the application key expires, you will need to create a new one and update the integration in Home Assistant. + ### Files are being overwritten due to non-unique bucket prefix If you set a prefix, all backups will be stored under that prefix in the bucket. Ensure that the prefix is unique to avoid overwriting other files. Changing the prefix will not move existing backups. From 6351ad5acfabfca8f1a08bbe2c2d65b413877a99 Mon Sep 17 00:00:00 2001 From: Hugo van Rijswijk Date: Thu, 25 Sep 2025 08:12:49 +0000 Subject: [PATCH 15/16] Remove single item bullet list --- source/_integrations/backblaze_b2.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/backblaze_b2.markdown b/source/_integrations/backblaze_b2.markdown index 4d8ce9024bbe..2880c52e27d6 100644 --- a/source/_integrations/backblaze_b2.markdown +++ b/source/_integrations/backblaze_b2.markdown @@ -49,7 +49,7 @@ To create an application key that can access the bucket: {% note %} -- By limiting credentials to a specific bucket, you reduce risk and help keep your Backblaze account secure. +By limiting credentials to a specific bucket, you reduce risk and help keep your Backblaze account secure. {% endnote %} From 134986598b560df7bf2fed6c072f829ed78a7c14 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 30 Oct 2025 08:49:11 +0100 Subject: [PATCH 16/16] fix indent in an attempt to fix build --- source/_integrations/backblaze_b2.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_integrations/backblaze_b2.markdown b/source/_integrations/backblaze_b2.markdown index 2880c52e27d6..021650bbc6d5 100644 --- a/source/_integrations/backblaze_b2.markdown +++ b/source/_integrations/backblaze_b2.markdown @@ -57,13 +57,13 @@ By limiting credentials to a specific bucket, you reduce risk and help keep your {% configuration_basic %} Key ID: -description: "The access key ID for your Backblaze account." + description: "The access key ID for your Backblaze account." Application Key: -description: "The application key for your Backblaze account." + description: "The application key for your Backblaze account." Bucket Name: -description: "Bucket name to store the backups. Bucket must already exist and be writable by the provided credentials." + description: "Bucket name to store the backups. Bucket must already exist and be writable by the provided credentials." Prefix: -description: "Optional prefix for the backups. This is useful if you want to store backups in a specific folder within the bucket." + description: "Optional prefix for the backups. This is useful if you want to store backups in a specific folder within the bucket." {% endconfiguration_basic %} ## Troubleshooting