mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-10 02:46:53 +00:00
Minor typos (#24364)
This commit is contained in:
parent
928732ac95
commit
fb5cb354e3
@ -9,4 +9,4 @@ Home Assistant offers a data disk feature that offloads all data to an attached
|
||||
|
||||
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.
|
||||
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 experimentation.
|
||||
|
@ -112,7 +112,7 @@ To add or remove entities from an existing group, click on `Group options`, all
|
||||
|
||||
## YAML Configuration
|
||||
|
||||
Alternatlively, this integration can be configured and set up manually via YAML
|
||||
Alternatively, this integration can be configured and set up manually via YAML
|
||||
instead. Here are example of how to configure groups when using the `configuration.yaml` file.
|
||||
|
||||
Example YAML configuration of a binary sensor group:
|
||||
|
@ -86,7 +86,7 @@ It is preferred to pick an icon to use for your zone. Pick any icon that you can
|
||||
|
||||
## State
|
||||
|
||||
The state of a zone is a number, which represends the number of
|
||||
The state of a zone is a number, which represents the number of
|
||||
{% my people title="persons" %} that are currently in a zone.
|
||||
|
||||
The number of persons in a zone can be helpful for automations, for example,
|
||||
|
@ -16,7 +16,7 @@ New users may sign up using *Web Auth* without issue. Follow the [documentation]
|
||||
|
||||
If you previously successfully configured Nest and Home Assistant with *App Auth* then follow the instructions for [Deprecated App Auth Credentials](https://www.home-assistant.io/integrations/nest/#deprecated-app-auth-credentials).
|
||||
|
||||
Nest is now configured entirely from the UI using [Application Credentials](https://www.home-assistant.io/integrations/application_credentials/) and the configuration flow will walk you through the steps of creating new credentails the right way.
|
||||
Nest is now configured entirely from the UI using [Application Credentials](https://www.home-assistant.io/integrations/application_credentials/) and the configuration flow will walk you through the steps of creating new credentials the right way.
|
||||
|
||||
You will need to upgrade to *Web Auth* before October to avoid interruption.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user