mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-21 16:27:19 +00:00
Adjust navigation changes for 2022.5 (#22623)
This commit is contained in:
Joakim Sørensen
GitHub
parent
88d1e8993b
commit
33d1212231
@ -113,7 +113,7 @@ homeassistant:
|
||||
- group: system-users
|
||||
```
|
||||
|
||||
First note, for `trusted_users` configuration you need to use `user id`, which you can find through {% my users title="Configuration -> Users" %} -> View User Detail. The `trusted_users` configuration will not validate the existence of the user, so please make sure you have put in the correct user id by yourself.
|
||||
First note, for `trusted_users` configuration you need to use `user id`, which you can find through {% my users title="Settings -> People" %} -> View User Detail. The `trusted_users` configuration will not validate the existence of the user, so please make sure you have put in the correct user id by yourself.
|
||||
|
||||
Second note, a trusted user with an IPv6 address must put the IPv6 address in quotes as shown.
|
||||
|
||||
|
||||
@ -35,7 +35,7 @@ Please note that if you click on **Trigger** of an automation in the frontend, *
|
||||
All this makes that Trigger feature pretty limited and nearly useless for debugging purposes so you need to find another way.
|
||||
Make sure you check and adapt to your circumstances appropriate examples from Automation Trigger, Conditions and Actions.
|
||||
|
||||
It is also useful to go to **{% my server_controls title="Configuration -> Server Control" %}** and click on **Check Configuration** button in Configuration validation section to make sure there are no syntax errors before restarting Home Assistant. In order for **Check configuration** to be visible, you must enable **Advanced Mode** on {% my profile title="your user profile" %}.
|
||||
It is also useful to go to **{% my server_controls title="Developer Tools -> YAML" %}** and click on **Check Configuration** button in Configuration validation section to make sure there are no syntax errors before restarting Home Assistant. In order for **Check configuration** to be visible, you must enable **Advanced Mode** on {% my profile title="your user profile" %}.
|
||||
|
||||
If your automation uses templates in any part, you can do the following to make sure it works as expected:
|
||||
|
||||
|
||||
@ -266,6 +266,6 @@ If you want to migrate your manual automations to use the editor, you'll have to
|
||||
|
||||
When automations remain visible in the Home Assistant Dashboard, even after having deleted in the YAML file, you have to delete them in the UI.
|
||||
|
||||
To delete them completely, go to UI **{% my entities title="Configuration -> Devices & Services -> Entities" %}** and find the automation in the search field or by scrolling down.
|
||||
To delete them completely, go to UI **{% my entities title="Settings -> Devices & Services -> Entities" %}** and find the automation in the search field or by scrolling down.
|
||||
|
||||
Check the square box aside of the automation you wish to delete and from the top-right of your screen, select 'REMOVE SELECTED'.
|
||||
|
||||
@ -13,7 +13,7 @@ The easiest option to edit `configuration.yaml` is to use the {% my supervisor_a
|
||||
|
||||
If you prefer to use a file editor on your computer, use the {% my supervisor_addon title="Samba add-on" addon="core_samba" %} to access the files as a network share.
|
||||
|
||||
The path to your configuration directory can be found in the Home Assistant frontend by going to {% my info title="Configuration > Settings > Info" %}
|
||||
The path to your configuration directory can be found in the Home Assistant frontend by going to {% my info title="Settings > About" %}
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/panel_config_info.png' alt='Screenshot showing the top of the info panel'>
|
||||
@ -28,13 +28,13 @@ _If you use Home Assistant Core, you can find `configuration.yaml` in the config
|
||||
|
||||
## Reloading changes
|
||||
|
||||
Most integrations in Home Assistant that do not interact with devices or services can reload changes made to their configuration in `configuration.yaml`. To do this, go to {% my server_controls title="Configuration > Server Control" %} and scroll down to the YAML configuration reloading section (alternatively, hit "c" anywhere in the UI and search for it).
|
||||
Most integrations in Home Assistant that do not interact with devices or services can reload changes made to their configuration in `configuration.yaml`. To do this, go to {% my server_controls title="Developer Tools > YAML" %} and scroll down to the YAML configuration reloading section (alternatively, hit "c" anywhere in the UI and search for it).
|
||||
|
||||
If you can't see your integration listed there, you will need to restart Home Assistant for changes to take effect.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
To test any changes to your configuration files from the command line, check out the common tasks for [operating system](/common-tasks/os/#configuration-check), [supervised](/common-tasks/supervised/#configuration-check), [container](/common-tasks/container/#configuration-check), [core](/common-tasks/core/#configuration-check) for how to do that. Configuration changes can also be tested using the UI by navigating to {% my server_controls title="Configuration > Settings > Server Control" %} and clicking "Check Configuration". For the button to be visible, you must enable "Advanced Mode" on your {% my profile title="User Profile" %}.
|
||||
To test any changes to your configuration files from the command line, check out the common tasks for [operating system](/common-tasks/os/#configuration-check), [supervised](/common-tasks/supervised/#configuration-check), [container](/common-tasks/container/#configuration-check), [core](/common-tasks/core/#configuration-check) for how to do that. Configuration changes can also be tested using the UI by navigating to {% my server_controls title="Developer Tools > YAML" %} and clicking "Check Configuration". For the button to be visible, you must enable "Advanced Mode" on your {% my profile title="User Profile" %}.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@ title: "Setup basic information"
|
||||
description: "Setting up the basic info of Home Assistant."
|
||||
---
|
||||
|
||||
As part of the default onboarding process, Home Assistant can detect your location from IP address geolocation. Home Assistant will automatically select a temperature unit and time zone based on this location. You may adjust this during onboarding, or afterwards at {% my general title="Configuration > General" %}.
|
||||
As part of the default onboarding process, Home Assistant can detect your location from IP address geolocation. Home Assistant will automatically select a temperature unit and time zone based on this location. You may adjust this during onboarding, or afterwards at {% my general title="Settings > System > General" %}.
|
||||
|
||||
If you prefer YAML, you can add the following information to your `configuration.yaml`:
|
||||
|
||||
@ -31,7 +31,7 @@ homeassistant:
|
||||
|
||||
<div class='note'>
|
||||
|
||||
You will not be able to edit anything in {% my general title="Configuration > General" %} in the UI if you are using YAML configuration for any of the following: name, latitude, longitude, elevation, unit_system, temperature_unit, time_zone, external_url, internal_url. Additionally, some options are only visible after "Advanced Mode" is enabled on your {% my profile title="User Profile" %}.
|
||||
You will not be able to edit anything in {% my general title="Settings > System > General" %} in the UI if you are using YAML configuration for any of the following: name, latitude, longitude, elevation, unit_system, temperature_unit, time_zone, external_url, internal_url. Additionally, some options are only visible after "Advanced Mode" is enabled on your {% my profile title="User Profile" %}.
|
||||
|
||||
</div>
|
||||
|
||||
@ -109,4 +109,4 @@ legacy_templates:
|
||||
|
||||
## Reload Core Service
|
||||
|
||||
Home Assistant offers a service to reload the core configuration while Home Assistant is running called {% my developer_call_service service="homeassistant.reload_core_config" %}. This allows you to change any of the above sections and see it being applied without having to restart Home Assistant. To call this service, go to the "{% my developer_services %}" tab under {% my developer_services title="Developer Tools" %}, select the {% my developer_call_service service="homeassistant.reload_core_config" %} service and click the "CALL SERVICE" button. Alternatively, you can press the "Reload Location & Customizations" button under {% my server_controls title="Configuration > Server Control" %}.
|
||||
Home Assistant offers a service to reload the core configuration while Home Assistant is running called {% my developer_call_service service="homeassistant.reload_core_config" %}. This allows you to change any of the above sections and see it being applied without having to restart Home Assistant. To call this service, go to the "{% my developer_services %}" tab under {% my developer_services title="Developer Tools" %}, select the {% my developer_call_service service="homeassistant.reload_core_config" %} service and click the "CALL SERVICE" button. Alternatively, you can press the "Reload Location & Customizations" button under {% my server_controls title="Developer Tools > YAML" %}.
|
||||
|
||||
@ -115,7 +115,7 @@ homeassistant:
|
||||
|
||||
Home Assistant offers a service to reload the core configuration while Home Assistant is running. This allows you to change your customize section and see your changes being applied without having to restart Home Assistant.
|
||||
|
||||
To reload customizations, navigate to Configuration > Server Controls and then press the "Reload Location & Customizations" button. If you don't see this, enable Advanced Mode on your user profile page first.
|
||||
To reload customizations, navigate to Developer Tools > YAML and then press the "Reload Location & Customizations" button. If you don't see this, enable Advanced Mode on your user profile page first.
|
||||
|
||||
You can also use the [Quick bar](/docs/tools/quick-bar/#command-palette), and choose "Reload Location & Customizations".
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ Type these from anywhere in the application to launch the dialog.
|
||||
|
||||
*Hotkey: `e`*
|
||||
|
||||
Similar to {% my entities title="Configuration -> Entities" %}, but more lightweight and accessible from anywhere in the frontend.
|
||||
Similar to {% my entities title="Settings -> Devices & Services -> Entities" %}, but more lightweight and accessible from anywhere in the frontend.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/docs/quick-bar/quick-bar-entity-filter.gif' alt='Quick Bar'>
|
||||
|
||||
@ -3,6 +3,6 @@ title: "Why does the start button for an add-on flash red when I click it?"
|
||||
ha_category: Home Assistant
|
||||
---
|
||||
|
||||
If you are looking for more information about add-ons, which won't start or install, navigate to {% my supervisor_logs title="Configuration > Add-ons & Backups > System" %} in the UI and check the logs.
|
||||
If you are looking for more information about add-ons, which won't start or install, navigate to {% my supervisor_logs title="Settings > Add-ons > System" %} in the UI and check the logs.
|
||||
|
||||
The logs on this page are the same you would see using `su logs` in the custom CLI.
|
||||
|
||||
@ -14,7 +14,7 @@ A partial backup consists of any number of the above default directories and ins
|
||||
|
||||
### Making a Backup from the UI
|
||||
|
||||
1. Go to {% my supervisor_backups title="Configuration > Add-ons & Backups > Backups" %} in the UI.
|
||||
1. Go to {% my supervisor_backups title="Settings > System > Backups" %} in the UI.
|
||||
2. Provide a name for the backup.
|
||||
3. Choose full or partial.
|
||||
4. Choose to password protect or not. Password-protected backups cannot easily be browsed outside of Home Assistant OS.
|
||||
|
||||
@ -9,10 +9,11 @@ If you would like to test next release before anyone else, you can install the b
|
||||
- title: From the UI
|
||||
content: |
|
||||
|
||||
1. In your Home Assistant UI navigate to {% my supervisor_info title="Configuration > Add-ons & Backups > System" %}
|
||||
2. Click the link that says "Join beta"
|
||||
3. Navigate to Configuration panel
|
||||
4. Install the update that is presented to you
|
||||
1. In your Home Assistant UI navigate to {% my updates title="System > Updates" %}
|
||||
2. Click the operflow menu in the top right corner
|
||||
3. Click "Join beta"
|
||||
4. Navigate to Configuration panel
|
||||
5. Install the update that is presented to you
|
||||
|
||||
- title: From the CLI
|
||||
content: |
|
||||
|
||||
@ -27,8 +27,8 @@ The data disk feature can be used on an existing installation without losing dat
|
||||
### Using UI to move the data partition
|
||||
|
||||
1. Connect the data disk to your system.
|
||||
2. Go to **{% my supervisor_info title="Configuration > Add-ons & Backups > System" %}** in the UI.
|
||||
3. Press the three dots on the bottom right of the Host card and choose "Move datadisk"
|
||||
2. Go to **{% my storage title="Settings > System > Storage" %}** in the UI.
|
||||
3. Press the three dots on the top right and choose "Move datadisk"
|
||||
4. Select the data disk from the list of available devices.
|
||||
5. Press "Move".
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
## Configuring access to files
|
||||
|
||||
Your Home Assistant Operating server includes two repositories by default: The official core add-on repository, and the community add-on repository. All of the add-ons mentioned here can be installed by navigating to the add-on store using {% my supervisor_store title="Configuration > Add-ons & Backups > Add-on Store" %} in the UI.
|
||||
Your Home Assistant Operating server includes two repositories by default: The official core add-on repository, and the community add-on repository. All of the add-ons mentioned here can be installed by navigating to the add-on store using {% my supervisor_store title="Settings > Add-ons > Add-on Store" %} in the UI.
|
||||
|
||||
One of the first things to take care of after installing Home Assistant OS is to provide yourself access to files. There are several add-ons commonly used for this, and most users employ a mix of various add-ons. Default directories on the host are mapped to the add-ons so that they can be accessed by the services any particular add-on might provide. On the host system these directories exist on the `/data` partition at `/mnt/data/supervisor/`.
|
||||
|
||||
@ -21,7 +21,7 @@ The Samba add-on creates smb shares which can be accessed from another computer.
|
||||
|
||||
To configure the Samba add-on, you only need to set a user and password of your choice on the configuration page, save, and then start the add-on. The add-on will not start without setting a password!
|
||||
|
||||
To connect to the Samba server from another device, you will use the IP address or hostname of your server. Either of these can be found on the {% my supervisor_info title="Configuration > Add-ons & Backups > System" %} page of your UI within the Host card.
|
||||
To connect to the Samba server from another device, you will use the IP address or hostname of your server. Either of these can be found on the {% my network title="Settings > System > Network" %} page of your UI.
|
||||
|
||||
For connecting from Windows 10, you can enter the IP address or hostname in File Explorer's address bar with two backslashes, as shown in the example screenshot.
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ Home Assistant cannot guarantee the quality or security of third-party add-ons.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/hassio/screenshots/dashboard.png' />
|
||||
From {% my supervisor title="Configuration > Add-ons & Backups" %} open the add-on store.
|
||||
From {% my supervisor title="Settings > Add-ons" %} open the add-on store.
|
||||
</p>
|
||||
|
||||
<p class='img'>
|
||||
@ -22,4 +22,4 @@ Add the URL of the repository and then press "Add". A new card for the repositor
|
||||
|
||||
### Help: Repository is not showing up
|
||||
|
||||
If you have added a repository, but it's not showing up, it means that the repository contains invalid configuration. Go to {% my supervisor_logs title="Configuration > Add-ons & Backups > System" %} to find the System log. It should tell you what went wrong. Report this information to the repository author.
|
||||
If you have added a repository, but it's not showing up, it means that the repository contains invalid configuration. Go to {% my logs title="Settings > System > Logs" %} to find the System log. It should tell you what went wrong. Report this information to the repository author.
|
||||
|
||||
@ -23,7 +23,7 @@ To update Home Assistant Core when you run Home Assistant {{ page.installation_n
|
||||
2. Navigate to the Configuration panel
|
||||
3. On the top you will be presented with an update notification
|
||||
|
||||
_If you do not see that notification you can navigate to the {% my supervisor_logs title="Configuration > Add-ons & Backups > System" %} panel. and click the "Reload Supervisor" button._
|
||||
_If you do not see that notification you can click the overflow menu in the top right and select "Check for updates"._
|
||||
|
||||
- title: Using the CLI
|
||||
content: |
|
||||
|
||||
@ -41,7 +41,7 @@ You will be prompted to select a protocol (i.e. `socket` or `serial`). Depending
|
||||
|
||||
## Settings
|
||||
|
||||
Once AlarmDecoder has been set up according to the instructions above, the arming settings and zones can be configured by selecting _Options_ on the _AlarmDecoder_ card on the **{% my integrations title="Configuration -> Integrations" %}** page.
|
||||
Once AlarmDecoder has been set up according to the instructions above, the arming settings and zones can be configured by selecting _Options_ on the _AlarmDecoder_ card on the **{% my integrations title="Settings -> Devices & Services" %}** page.
|
||||
|
||||
### Arming Settings
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ Home Assistant allows users to share their usage data via the analytics integrat
|
||||
|
||||
## Data Collection
|
||||
|
||||
The information sent depends on what options you opt-in to. You can opt-in during onboarding and by going to **{% my general title="Configuration >> General" %}** .
|
||||
The information sent depends on what options you opt-in to. You can opt-in during onboarding and by going to **{% my analytics title="Settings > System > Analytics" %}** .
|
||||
|
||||
{% my general badge %}
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@ The `counter` integration allows one to count occurrences fired by automations.
|
||||
## Configuration
|
||||
|
||||
The preferred way to configure counter helpers is via the user interface. To add one, go to
|
||||
**{% my helpers title="Configuration -> Helpers" %}** and click the add button;
|
||||
**{% my helpers title="Settings -> Devices & Services -> Helpers" %}** and click the add button;
|
||||
next choose the "**Counter**" option.
|
||||
|
||||
To be able to add **Helpers** via the user interface you should have
|
||||
|
||||
@ -51,7 +51,7 @@ You may configure multiple Firmata boards. Each board has the following options:
|
||||
|
||||
{% configuration %}
|
||||
serial_port:
|
||||
description: The port where your board is connected to your Home Assistant host. It is recommended to use the `by-id` reference (instead of numerical like `/dev/ttyACM0` or `/dev/ttyUSB0`) since these will never change after a reboot. If you are using Home Assistant Operating System, you can find a list of connected serial devices in the Hardware dialog on the {% my supervisor_logs title="Configuration > Add-ons & Backups > System" %} panel.
|
||||
description: The port where your board is connected to your Home Assistant host. It is recommended to use the `by-id` reference (instead of numerical like `/dev/ttyACM0` or `/dev/ttyUSB0`) since these will never change after a reboot. If you are using Home Assistant Operating System, you can find a list of connected serial devices in the Hardware dialog on the {% my hardware title="Settings > System > Hardware" %} panel.
|
||||
required: true
|
||||
type: string
|
||||
serial_baud_rate:
|
||||
|
||||
@ -132,7 +132,7 @@ These devices have been sold under at least the following brands:
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
After the devices have been added they can be configured with different effects listed below. These settings can be accessed by navigating to the integration settings in Configuration -> Integrations and selecting the "Magic Home" configuration for the bulb or controller.
|
||||
After the devices have been added they can be configured with different effects listed below. These settings can be accessed by navigating to the integration settings in Settings -> Integrations and selecting the "Magic Home" configuration for the bulb or controller.
|
||||
|
||||
**Custom Effect**\
|
||||
A list of RGB colors can be entered to create an effect. The effect speed can be adjusted using the slider underneath.
|
||||
|
||||
@ -26,7 +26,7 @@ When you have authorized the integration, you select repositories you want to mo
|
||||
|
||||
## Remove authorization
|
||||
|
||||
After you have removed the integration from {% my integrations title="Configuration -> Devices & Services" %}, you need to manually revoke OAuth app authorization.
|
||||
After you have removed the integration from {% my integrations title="Settings -> Devices & Services" %}, you need to manually revoke OAuth app authorization.
|
||||
|
||||
1. Go to your [Authorized OAuth Apps][github_apps]
|
||||
2. Find the "Home Assistant GitHub Integration" application
|
||||
|
||||
@ -323,7 +323,7 @@ When exposing a Camera, Activity based remote (a `remote` that supports activiti
|
||||
|
||||
To quickly add all accessory mode entities in the UI:
|
||||
|
||||
1. Create a new bridge via the UI (i.e., **{% my config_flow_start title="Configuration >> Integrations" domain=page.ha_domain %}**).
|
||||
1. Create a new bridge via the UI (i.e., **{% my config_flow_start title="Settings >> Devices & Services" domain=page.ha_domain %}**).
|
||||
2. Select `media_player`, `remote`, `lock`, and `camera` domains.
|
||||
3. Complete the flow as normal.
|
||||
4. Additional HomeKit entries for each entity that must operate in accessory mode will be created for each entity that does not already have one.
|
||||
@ -332,7 +332,7 @@ To quickly add all accessory mode entities in the UI:
|
||||
|
||||
To add a single entity in accessory mode:
|
||||
|
||||
1. Create a new bridge via the UI (i.e., **{% my config_flow_start title="Configuration >> Integrations" domain=page.ha_domain %}**)
|
||||
1. Create a new bridge via the UI (i.e., **{% my config_flow_start title="Settings >> Devices & Services" domain=page.ha_domain %}**)
|
||||
2. Before pairing the bridge, access the options for the bridge.
|
||||
3. Change the mode to `accessory`
|
||||
4. Select the entity.
|
||||
@ -434,7 +434,7 @@ The following integrations are currently supported:
|
||||
|
||||
# Device Triggers
|
||||
|
||||
Devices that support triggers can be added to the bridge by accessing options for the bridge in **{% my integrations title="Configuration >> Integrations" %}**. To use this feature, Advanced Mode must be enabled in your user profile.
|
||||
Devices that support triggers can be added to the bridge by accessing options for the bridge in **{% my integrations title="Settings >> Devices & Services" %}**. To use this feature, Advanced Mode must be enabled in your user profile.
|
||||
|
||||
Bridged device triggers are represented as a single press button on stateless programmable switches. This allows a HomeKit automation to run when a device trigger fires. Because the Apple Home app currently only shows the number of the button and not the name, users may find it easier to identify the name of the button in the `Eve for HomeKit` app.
|
||||
|
||||
|
||||
@ -41,7 +41,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
The Hue concept is based on Rooms and Zones. Although the underlying Hue lights are exposed directly to Home Assistant it might also be useful to interact with the `grouped lights` of the Hue ecosystem, for example to turn all lights in a Hue group on/off at the same time.
|
||||
|
||||
Home Assistant creates lights for each Hue zone/room automatically but disables them by default.
|
||||
If you'd like to use those `grouped lights`, you can enable them from Configuration --> Integrations --> Hue --> entities.
|
||||
If you'd like to use those `grouped lights`, you can enable them from Settings --> Integrations --> Hue --> entities.
|
||||
|
||||
## Scenes
|
||||
|
||||
|
||||
@ -21,7 +21,7 @@ automations by using them in their conditions.
|
||||
|
||||
The preferred way to configure input boolean helpers is via the user interface,
|
||||
in which they are known as Toggle Helpers. To add one, go to
|
||||
**{% my helpers title="Configuration -> Helpers" %}** and click the add button;
|
||||
**{% my helpers title="Settings -> Devices & Services -> Helpers" %}** and click the add button;
|
||||
next choose the "**Toggle**" option.
|
||||
|
||||
To be able to add **Helpers** via the user interface you should have
|
||||
|
||||
@ -19,7 +19,7 @@ like an automation.
|
||||
## Configuration
|
||||
|
||||
The preferred way to configure button helpers is via the user interface.
|
||||
To add one, go to **{% my helpers title="Configuration -> Helpers" %}**
|
||||
To add one, go to **{% my helpers title="Settings -> Devices & Services -> Helpers" %}**
|
||||
and click the add button; next choose the "**Button**" option.
|
||||
|
||||
To be able to add **Helpers** via the user interface you should have
|
||||
|
||||
@ -55,7 +55,7 @@ To use HomeKit Controller:
|
||||
|
||||
### Pairing with Home Assistant
|
||||
|
||||
- Go to {% my integrations title="Configuration >> Integrations" %} in the Home Assistant UI.
|
||||
- Go to {% my integrations title="Settings >> Devices & Services" %} in the Home Assistant UI.
|
||||
- Click the button with + sign, and from the list of integrations, select ***HomeKit Controller***.
|
||||
- Select the `MyQ-...` bridge.
|
||||
- Enter the pairing code that is physically printed on a sticker on the bridge.
|
||||
@ -63,7 +63,7 @@ To use HomeKit Controller:
|
||||
|
||||
If you want the devices to be accessible via HomeKit, create a HomeKit Bridge using the following steps:
|
||||
|
||||
- Go to {% my integrations title="Configuration >> Integrations" %} in the Home Assistant UI.
|
||||
- Go to {% my integrations title="Settings >> Devices & Servicess" %} in the Home Assistant UI.
|
||||
- Click the button with + sign, and from the list of integrations, select ***HomeKit***.
|
||||
- Create a bridge for the `cover` domain.
|
||||
- Follow the instructions to pair with the bridge.
|
||||
|
||||
@ -562,7 +562,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
* Use "[Home Assistant] [Edit] [For Home Automation]" as the description as it is not super important.
|
||||
8. Click "Create Product"
|
||||
9. Once the new product page opens the "Product ID" and "Product Secret" are located on the right side. These will be used as `client_id` and `client_secret` below.
|
||||
10. Add the Nest integration to your `configuration.yaml` and restart Home Assistant. Then, go to `Configuration > Integrations` and select `CONFIGURE` next to `Nest`. Click the link in the configurator pop up to log into your Nest account and complete the OAuth. Copy the resulting PIN code into the pop up.
|
||||
10. Add the Nest integration to your `configuration.yaml` and restart Home Assistant. Then, go to `Settings > Devices & Services` and select `CONFIGURE` next to `Nest`. Click the link in the configurator pop up to log into your Nest account and complete the OAuth. Copy the resulting PIN code into the pop up.
|
||||
|
||||
Connecting to the Nest Developer API requires outbound port 9553 on your firewall. The configuration will fail if this is not accessible.
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ ha_codeowners:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
This integration provides network configuration for integrations such as [Zeroconf](/integrations/zeroconf/). It is managed by going to **{% my general title="Configuration >> General" %}** and is only available to users that have "Advanced Mode" enabled on their {% my profile title="user profile" %}.
|
||||
This integration provides network configuration for integrations such as [Zeroconf](/integrations/zeroconf/). It is managed by going to **{% my network title="Settings >> System >> Network" %}** and is only available to users that have "Advanced Mode" enabled on their {% my profile title="user profile" %}.
|
||||
|
||||
**{% my general badge %}**
|
||||
|
||||
|
||||
@ -58,7 +58,7 @@ turn_on_action:
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
When you restart Home Assistant, make sure the TV is turned on and connected to your local network. If your TV needs to be paired, you'll need to go to **Configuration > Integrations** to type the PIN code that will be displayed on it and finish the setup.
|
||||
When you restart Home Assistant, make sure the TV is turned on and connected to your local network. If your TV needs to be paired, you'll need to go to **Settings > Devices & Services** to type the PIN code that will be displayed on it and finish the setup.
|
||||
|
||||
### Example `turn_on_action`
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ The `ps4` integration allows you to control a
|
||||
Read the section "Granting Port Access" below before continuing.
|
||||
</div>
|
||||
|
||||
2. Navigate to `Configuration -> Integrations` and press the plus button in the bottom right corner. Select `PlayStation 4` from the list of integrations.
|
||||
2. Navigate to `Settings -> Integrations` and press the plus button in the bottom right corner. Select `PlayStation 4` from the list of integrations.
|
||||
|
||||
3. Follow instructions displayed to generate user credentials. You will know this step is completed when a form with fields appears.
|
||||
|
||||
|
||||
@ -69,7 +69,7 @@ smappee:
|
||||
client_secret: YOUR_CLIENT_SECRET
|
||||
```
|
||||
|
||||
Once Home Assistant restarted, go to Configuration > Integrations and select the Smappee integration. You will be redirected to a login page and be able to select the locations you would like to use within Home Assistant.
|
||||
Once Home Assistant restarted, go to Settings > Devices & Services and select the Smappee integration. You will be redirected to a login page and be able to select the locations you would like to use within Home Assistant.
|
||||
|
||||
Using the Smappee cloud integration allows you to access your Smappee monitor and other shared devices from outside your local network. Additionally a number of (binary) sensor entities become available as well.
|
||||
|
||||
|
||||
@ -262,18 +262,6 @@ sensors:
|
||||
|
||||
The list of sensors can be any sensor, not just temperature or humidity.
|
||||
|
||||
## Sensor specific location
|
||||
|
||||
The [SpaceAPI specification](http://spaceapi.net/documentation) requires every sensor to provide a location.
|
||||
In order to set a sensor specific location do the following steps:
|
||||
|
||||
1. Go to Configuration -> Customization
|
||||
2. Select the sensor entity
|
||||
3. Pick "Other" from the attribute override pulldown
|
||||
4. Set the attribute name to location and the attribute value to your desired location
|
||||
|
||||
If no location is set, the location defined in the HA configuration is used.
|
||||
|
||||
## Examples
|
||||
|
||||
In this section you find some real-life examples of how to use this component.
|
||||
|
||||
@ -52,4 +52,4 @@ Tasmota Buttons, Fans, Lights, relays, Sensors, Shutters and Switches are suppor
|
||||
|
||||
You must also configure each Tasmota device's MQTT settings to communicate with whatever MQTT broker you are using. Enter the broker address under host and enter a username/password combination that allows access to the broker.
|
||||
|
||||
If using the Mosquitto Broker add-on for Home Assistant, first create a new Home Assistant user under {% my users title="Configuration > Users" %}. Then, in Tasmota > Configure MQTT under "Host" enter the address of your Home Assistant instance and under "User" and "Password" enter the Home Assistant user you just created.
|
||||
If using the Mosquitto Broker add-on for Home Assistant, first create a new Home Assistant user under {% my users title="Settings > People" %}. Then, in Tasmota > Configure MQTT under "Host" enter the address of your Home Assistant instance and under "User" and "Password" enter the Home Assistant user you just created.
|
||||
|
||||
@ -15,7 +15,7 @@ When a timer finishes or gets canceled the corresponding events are fired. This
|
||||
|
||||
|
||||
## Configuration
|
||||
The preferred way to configure timer helpers is via the user interface. To add one, go to Configuration -> Automations & Scenes, select the "Helpers" tab and click the add button; next choose the “Timer” option.
|
||||
The preferred way to configure timer helpers is via the user interface. To add one, go to Settings -> Automations & Scenes, select the "Helpers" tab and click the add button; next choose the “Timer” option.
|
||||
|
||||
You can also click the following button to be redirected to the Helpers page of your Home Assistant instance.
|
||||
|
||||
|
||||
@ -300,7 +300,7 @@ xbox:
|
||||
client_secret: YOUR_CLIENT_SECRET
|
||||
```
|
||||
|
||||
Finish setup in the UI through **Configuration -> Integrations -> Xbox**.
|
||||
Finish setup in the UI through **Settings -> Integrations -> Xbox**.
|
||||
|
||||
{% configuration %}
|
||||
client_id:
|
||||
|
||||
@ -151,7 +151,7 @@ radio type. In the pop-up:
|
||||
Most devices need at the very least the serial device path, like `/dev/ttyUSB0`, but it is recommended to use
|
||||
device path from `/dev/serial/by-id` folder,
|
||||
e.g., `/dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_C0F003D3-if01-port0`
|
||||
A list of available device paths can be found in {% my supervisor_logs title="Configuration > Add-ons & Backups > System" %} > **Host** > **dot menu** > **Hardware**.
|
||||
A list of available device paths can be found in {% my hardware title="Settings > System > HArdware" %} > **dot menu** > **All Hardware**.
|
||||
|
||||
Press `Submit`. The success dialog will appear or an error will be displayed in the popup. An error is likely if Home Assistant can't access the USB device or your device is not up to date. Refer to [Troubleshooting](#troubleshooting) below for more information.
|
||||
|
||||
|
||||
@ -14,7 +14,7 @@ ha_integration_type: integration
|
||||
|
||||
Zones allow you to specify certain regions on earth (for now). When a device tracker sees a device to be within a zone, the state will take the name from the zone. Zones can also be used as a [trigger](/getting-started/automation-trigger/#zone-trigger) or [condition](/getting-started/automation-condition/#zone-condition) inside automation setups.
|
||||
|
||||
Zones can be added and managed through the user interface at **{% my zones title="Configuration -> Zones" %}**.
|
||||
Zones can be added and managed through the user interface at **{% my zones title="Settings -> Areas & Zones" %}**.
|
||||
|
||||
Zones can also be configured via `configuration.yaml`:
|
||||
|
||||
|
||||
@ -584,7 +584,7 @@ Some entities may not be able to migrate automatically and you will need to rena
|
||||
|
||||
<div class='note info'>Make a list of what node ID belongs to each device. Your network (Nodes and their config etc) is stored on the stick but the names you gave your devices and entities are not. This step is optional but will save you a lot of time later.</div>
|
||||
|
||||
2) Remove the Z-Wave integration from Home Assistant: Configuration --> Integrations --> Z-Wave (or OpenZWave) --> Press the three dots and click Delete.
|
||||
2) Remove the Z-Wave integration from Home Assistant: Settings --> Devices & Services --> Z-Wave (or OpenZWave) --> Press the three dots and click Delete.
|
||||
|
||||
<div class='note info'>
|
||||
|
||||
@ -783,7 +783,7 @@ Names set in Home Assistant will not import into Zwavejs2Mqtt.
|
||||
|
||||
#### How can I add (include) a new device to my Z-Wave network?
|
||||
|
||||
1. In Home Assistant: open Configuration -> Integrations -> Z-Wave JS -> Configure.
|
||||
1. In Home Assistant: open Settings -> Devices & Services -> Z-Wave JS -> Configure.
|
||||
2. Press `+ ADD DEVICE`.
|
||||
3. The Z-Wave controller is now in inclusion mode and will not respond to other commands.
|
||||
4. Put the device you want to add in inclusion mode. Refer to its manual how this is done.
|
||||
@ -807,7 +807,7 @@ S2 security does not impose additional network traffic and provides additional b
|
||||
|
||||
#### How do I remove (exclude) a device from my Z-Wave network?
|
||||
|
||||
1. In Home Assistant: open Configuration -> Integrations -> Z-Wave JS -> Configure.
|
||||
1. In Home Assistant: open Settings -> Devices & Services -> Z-Wave JS -> Configure.
|
||||
2. Press `REMOVE DEVICE`.
|
||||
3. Press `START EXCLUSION`. The Z-Wave controller is now in exclusion mode and will not respond to other commands.
|
||||
4. Put the device you want to remove in exclusion mode. Refer to its manual how this is done.
|
||||
|
||||
@ -11,7 +11,7 @@ regenerate: false
|
||||
<p>
|
||||
This can be running an application that Home Assistant can integrate with
|
||||
(like an MQTT broker) or to share the configuration via Samba for easy editing
|
||||
from other computers. Add-ons can be configured via the {% my supervisor title="Configuration > Add-ons & Backups" %} panel in Home
|
||||
from other computers. Add-ons can be configured via the {% my supervisor title="Settings > Add-ons" %} panel in Home
|
||||
Assistant.
|
||||
</p>
|
||||
|
||||
@ -21,7 +21,7 @@ regenerate: false
|
||||
</p>
|
||||
|
||||
<p>
|
||||
To install add-ons, navigate to the {% my supervisor title="Configuration > Add-ons & Backups" %} panel in your Home Assistant
|
||||
To install add-ons, navigate to the {% my supervisor title="Settings > Add-ons" %} panel in your Home Assistant
|
||||
frontend, and click on the "Add-on store" tab. All add-ons, including their documentation, are available right from the store.
|
||||
Some advanced add-ons will only be visible after you opt-in to "Advanced Mode" which can be changed on your user profile page.
|
||||
Click on an add-on you are interested in, to read the documentation or to install the add-on.
|
||||
|
||||
@ -11,11 +11,11 @@ The steps below do not apply to Home Assistant Core & Container installations, f
|
||||
|
||||
</div>
|
||||
|
||||
We are going to help you make your first changes to `configuration.yaml`. To do this, we are going to install an add-on from the Home Assistant add-on store: the File editor. To get to the add-on store, click on the menu icon in the top left, then open {% my supervisor title="Configuration > Add-ons & Backups" %}. On the new page, open the add-on store tab.
|
||||
We are going to help you make your first changes to `configuration.yaml`. To do this, we are going to install an add-on from the Home Assistant add-on store: the File editor. To get to the add-on store, click on the menu icon in the top left, then open {% my supervisor title="Settings > Add-ons" %}. On the new page, open the add-on store tab.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/hassio/screenshots/dashboard.png' />
|
||||
From the {% my supervisor title="Configuration > Add-ons & Backups" %} panel, open the add-on store.
|
||||
From the {% my supervisor title="Settings > Add-ons" %} panel, open the add-on store.
|
||||
</p>
|
||||
|
||||
Under the "Official add-ons" section you will find the File editor add-on.
|
||||
|
||||
@ -22,7 +22,7 @@ _If you do not have a Docker Hub account [you can create one here][dockerhub-sig
|
||||
To use your Docker Hub credentials with the Supervisor:
|
||||
|
||||
- You need to have the advanced user toggle enabled in your user profile setting.
|
||||
- Go to the {% my supervisor title="Configuration > Add-ons & Backups" %} in the Home Assistant UI.
|
||||
- Go to the {% my supervisor title="Settings > Add-ons" %} in the Home Assistant UI.
|
||||
- Click on "Add-on Store".
|
||||
- Click the three dots in the top right corner of the screen, and select "Registries".
|
||||
|
||||
|
||||
@ -24,17 +24,16 @@ the database, and even change how long it stores the data
|
||||
|
||||
## Delete old backups
|
||||
|
||||
Open the Home Assistant UI and go to {% my supervisor title="Configuration > Add-ons & Backups" %}, and then to
|
||||
the "Backups" tab, here you will see all your backups, these can be
|
||||
downloaded and placed somewhere safe. When you have done that, you can delete
|
||||
Open the Home Assistant UI and go to {% my backups title="Settings > System > Backups" %}, here you will see all your backups,
|
||||
these can be downloaded and placed somewhere safe. When you have done that, you can delete
|
||||
them in the UI and it will free up some space for you.
|
||||
|
||||
## Uninstall unused add-ons
|
||||
|
||||
Add-ons can take a lot of space, not just the add-on itself but also their data.
|
||||
|
||||
Open the Home Assistant UI and go to {% my supervisor title="Configuration > Add-ons & Backups" %} in the sidebar, you will be
|
||||
on the "Dashboard" tab when you click on {% my supervisor title="Configuration > Add-ons & Backups" %}, here you will see
|
||||
Open the Home Assistant UI and go to {% my supervisor title="Settings > Add-ons" %} in the sidebar, you will be
|
||||
on the "Dashboard" tab when you click on {% my supervisor title="Settings > Add-ons" %}, here you will see
|
||||
all your installed add-ons, maybe you have some that you no longer use, if
|
||||
you do those can be uninstalled to free up some space.
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ If you are running Home Assistant OS or Supervised, you can access your
|
||||
(automatically) created media folder using the Samba add-on.
|
||||
|
||||
If you haven't installed the Samba add-on yet, you can do so by browsing to
|
||||
the {% my supervisor title="Configuration > Add-ons & Backups" %} panel. Next, click on
|
||||
the {% my supervisor title="Settings > Add-ons" %} panel. Next, click on
|
||||
the "Add-on store" tab and search for "Samba" and click on it.
|
||||
|
||||
On the Samba add-on page, you can find a tab called "Documentation" with
|
||||
|
||||
@ -12,7 +12,6 @@ This happens when any of the setup tasks fails to complete, this can be due to t
|
||||
If the issue is related to DBUS, you will see an unsupported message about that as well; You can have a look [here][DBUS] on how to resolve that.
|
||||
|
||||
If DBUS is not the problem, the first thing you should try is to restart the Supervisor.
|
||||
This can be done from {% my supervisor_logs title="Configuration > Add-ons & Backups" > System" %}. On the card for "Supervisor", there is a button to restart the Supervisor.
|
||||
|
||||
This can also be done with the CLI, by running the following command:
|
||||
|
||||
@ -23,6 +22,6 @@ ha supervisor restart
|
||||
If this does not help, you can try to reboot the host.
|
||||
If you are running Home Assistant Operating System, this can be done from the "System" tab in the Supervisor panel. On the card for "Host System", there is a button to reboot the host.
|
||||
|
||||
To help us make the setup more robust, please enable the sharing of diagnostics and crash logs on the {% my supervisor_logs title="Configuration > Add-ons & Backups > System" %} panel.
|
||||
To help us make the setup more robust, please enable the sharing of diagnostics and crash logs on the {% my analytics title="Settings > System > Analytics" %} panel.
|
||||
|
||||
[DBUS]: /more-info/unsupported/dbus
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user