From 43b465cf111668f4cc9b17f9038ce7e9b60e3e2d Mon Sep 17 00:00:00 2001 From: Ashton Lafferty Date: Tue, 2 Nov 2021 12:12:36 -0600 Subject: [PATCH 1/5] Update usb_boot.markdown again (#20123) --- source/_faq/usb_boot.markdown | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/source/_faq/usb_boot.markdown b/source/_faq/usb_boot.markdown index 0966b502292..f12de8219f3 100644 --- a/source/_faq/usb_boot.markdown +++ b/source/_faq/usb_boot.markdown @@ -3,7 +3,10 @@ title: "Is USB Boot for the Raspberry Pi 4 supported?" ha_category: Home Assistant --- -Due to the complexity of USB and the USB mass storage device class, booting from a USB device is brittle. When booting from a USB drive this process has to be done multiple times (firmware/boot loader and the operating system), and there is a high chance that this process doesn't complete during one of these stages. In general, the Linux USB stack is solid, so it is recommended to boot Home Assistant OS from an SD card and use a USB attached flash drive as data partition only. The data move can be accomplished through the `datactl` command on the host or through the UI. For more information, see [Using external Data Disk](/common-tasks/os/#using-external-data-disk) +Home Assistant offers a data disk feature that offloads all data to an attached USB hard drive. The SD card is still in use but is only used to serve the Home Assistant OS. [Learn more about the data disk feature.](/common-tasks/os/#using-external-data-disk) +**Booting from USB** -That said, booting Home Assistant OS completely from a USB drive (SSD or any other USB mass storage device) works with *some* USB devices. USB Devices that are known to work with Raspberry Pi OS (check the Raspberry Pi Forum) are more likely to work with Home Assistant OS. However, because Home Assistant OS has also U-Boot in the boot chain, there are devices which are known to work with Raspberry Pi OS but do *not* work with Home Assistant OS. +Due to the complexity of USB and the USB mass storage device class, booting from a USB device is delicate. When booting from a USB drive this process has to be done multiple times (firmware/boot loader and the operating system), and there is a high chance that it doesn't complete during one of these stages. + +That said, booting Home Assistant OS completely from a USB drive (SSD or any other USB mass storage device) works with *some* USB devices. USB Devices that are known to work with Raspberry Pi OS (check the Raspberry Pi Forum) are more likely to work with Home Assistant OS. However, because Home Assistant OS also has U-Boot in the boot chain, there are devices which are known to work with Raspberry Pi OS but do *not* work with Home Assistant OS. Finding the right combination of hardware can require expirimentation. From fefca175b31bc24d5467a734eca3b1aee68d7dbf Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Wed, 3 Nov 2021 08:28:18 +0100 Subject: [PATCH 2/5] Bump actions/checkout from 2.3.5 to 2.4.0 (#20131) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- .github/workflows/test.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index 8a4460ea66e..5a3f6a3285a 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -8,7 +8,7 @@ jobs: runs-on: ubuntu-latest steps: - name: Check out files from GitHub - uses: actions/checkout@v2.3.5 + uses: actions/checkout@v2.4.0 - name: Setting up Node.js uses: actions/setup-node@v2.4.1 with: @@ -25,7 +25,7 @@ jobs: runs-on: ubuntu-latest steps: - name: Check out files from GitHub - uses: actions/checkout@v2.3.5 + uses: actions/checkout@v2.4.0 - name: Setting up Node.js uses: actions/setup-node@v2.4.1 with: From bd16b0218f1de194c90ef905f98932e2531e8366 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Wed, 3 Nov 2021 08:28:40 +0100 Subject: [PATCH 3/5] Bump i18n from 1.8.10 to 1.8.11 (#20130) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- Gemfile.lock | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Gemfile.lock b/Gemfile.lock index 017425a245c..66a37b4305d 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -29,7 +29,7 @@ GEM ffi (1.15.4-x64-mingw32) forwardable-extended (2.6.0) http_parser.rb (0.6.0) - i18n (1.8.10) + i18n (1.8.11) concurrent-ruby (~> 1.0) jekyll (4.2.1) addressable (~> 2.4) From 030ce9ec119c73de98630e2d6b855d40cd6e2b69 Mon Sep 17 00:00:00 2001 From: Matheson Steplock Date: Wed, 3 Nov 2021 03:34:18 -0400 Subject: [PATCH 4/5] Additional info for Flashing an Odroid-N2+ (#19828) --- source/_includes/common-tasks/flashing_n2_otg.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/source/_includes/common-tasks/flashing_n2_otg.md b/source/_includes/common-tasks/flashing_n2_otg.md index 3cf25919146..f4cb0d8aa49 100644 --- a/source/_includes/common-tasks/flashing_n2_otg.md +++ b/source/_includes/common-tasks/flashing_n2_otg.md @@ -37,13 +37,21 @@ After The ODROID-N2+ is set to SPI boot mode and powered on, it boots into a ter ![Exit to shell](/images/hassio/screenshots/exit-shell.png) -1. Use the following command at the console to confirm the storage device node: +
+ +When using the command line, it may return the following message: +`can't access tty; job control turned off.` +You can safely ignore this message and proceed with the installation + +
+ +2. Use the following command at the console to confirm the storage device node: ```bash ls /dev/mmc* ``` -1. Set the storage device on the ODROID-N2+ as a mass storage device using the `ums` command (USB Mass storage mode). +3. Set the storage device on the ODROID-N2+ as a mass storage device using the `ums` command (USB Mass storage mode). This will configure the ODROID-N2+ and OTG to act as a memory card reader: ```bash From 8ede9ebf10834fd0d6906aa3a7f33e573d89d549 Mon Sep 17 00:00:00 2001 From: Erik Montnemery Date: Wed, 3 Nov 2021 09:05:05 +0100 Subject: [PATCH 5/5] Remove documentation for deprecated MQTT sensor last_reset (#20133) --- source/_integrations/sensor.mqtt.markdown | 4 ---- 1 file changed, 4 deletions(-) diff --git a/source/_integrations/sensor.mqtt.markdown b/source/_integrations/sensor.mqtt.markdown index 9cac92062ff..1e382953f78 100644 --- a/source/_integrations/sensor.mqtt.markdown +++ b/source/_integrations/sensor.mqtt.markdown @@ -119,10 +119,6 @@ json_attributes_topic: description: The MQTT topic subscribed to receive a JSON dictionary payload and then set as sensor attributes. Implies `force_update` of the current sensor state when a message is received on this topic. required: false type: string -last_reset_topic: - description: "The MQTT topic subscribed to receive timestamps for when an accumulating sensor such as an energy meter was reset. If the sensor never resets, set `last_reset_topic` to same as `state_topic` and set the `last_reset_value_template` to a constant valid timstamp, for example UNIX epoch 0: `1970-01-01T00:00:00+00:00`." - required: false - type: string last_reset_value_template: description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the last_reset. Available variables: `entity_id`. The `entity_id` can be used to reference the entity's attributes." required: false