mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-18 23:06:58 +00:00
move configuration redirects (#14744)
* move configuration redirects from source files in source\_docs\configuration into the dedicated source\_redirects file * ✏️ Tweak * ✏️ Tweak Co-authored-by: Klaas Schoute <klaas_schoute@hotmail.com>
This commit is contained in:
Jenny
GitHub
parent
8b4188ec9b
commit
131a435c3d
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "Setup basic information"
|
||||
description: "Setting up the basic info of Home Assistant."
|
||||
redirect_from: /getting-started/basic/
|
||||
---
|
||||
|
||||
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 Configuration -> General.
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "Customizing entities"
|
||||
description: "Simple customization for entities in the frontend."
|
||||
redirect_from: /getting-started/customizing-devices/
|
||||
---
|
||||
|
||||
## Changing the entity_id
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "Adding devices to Home Assistant"
|
||||
description: "Steps to help you get your devices in Home Assistant."
|
||||
redirect_from: /getting-started/devices/
|
||||
---
|
||||
|
||||
Home Assistant will be able to automatically discover many devices and services available on your network if you have [the discovery component](/integrations/discovery/) enabled (the default setting).
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "Events"
|
||||
description: "Describes all there is to know about events in Home Assistant."
|
||||
redirect_from: /topics/events/
|
||||
---
|
||||
|
||||
The core of Home Assistant is the event bus. The event bus allows any integration to fire or listen for events. It is the core of everything. For example, any state change will be announced on the event bus as a `state_changed` event containing the previous and the new state of an entity.
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "Packages"
|
||||
description: "Describes all there is to know about configuration packages in Home Assistant."
|
||||
redirect_from: /topics/packages/
|
||||
---
|
||||
|
||||
Packages in Home Assistant provide a way to bundle different component's configuration together. We already learned about the two configuration styles (specifying platforms entries together or individually) on the [adding devices](/docs/configuration/devices/) page. Both of these configuration methods require you to create the integration key in the main `configuration.yaml` file. With packages we have a way to include different components, or different configuration parts using any of the `!include` directives introduced in [splitting the configuration](/docs/configuration/splitting_configuration).
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "Entity integration platform options"
|
||||
description: "Shows how to customize polling interval for any integration via configuration.yaml."
|
||||
redirect_from: /topics/platform_options/
|
||||
---
|
||||
|
||||
<div class='note info'>
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "Storing secrets"
|
||||
description: "Storing secrets outside of your configuration.yaml."
|
||||
redirect_from: /topics/secrets/
|
||||
---
|
||||
|
||||
The `configuration.yaml` file is a plain-text file, thus it is readable by anyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. By using `!secret` you can remove any private information from your configuration files. This separation can also help you to keep easier track of your passwords and API keys, as they are all stored at one place and no longer spread across the `configuration.yaml` file or even multiple YAML files if you [split up your configuration](/docs/configuration/splitting_configuration/).
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "Securing"
|
||||
description: "Instructions on how to secure your Home Assistant installation."
|
||||
redirect_from: /getting-started/securing/
|
||||
---
|
||||
|
||||
One major advantage of Home Assistant is that it's not dependent on cloud services. Even if you're only using Home Assistant on a local network, you should take steps to secure your instance.
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "Splitting up the configuration"
|
||||
description: "Splitting the configuration.yaml into several files."
|
||||
redirect_from: /topics/splitting_configuration/
|
||||
---
|
||||
|
||||
So you've been using Home Assistant for a while now and your `configuration.yaml` file brings people to tears or you simply want to start off with the distributed approach, here's how to split the `configuration.yaml` into more manageable (read: humanly readable) pieces.
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "State Objects"
|
||||
description: "Describes all there is to know about state objects in Home Assistant."
|
||||
redirect_from: /topics/state_object/
|
||||
---
|
||||
|
||||
Your devices are represented in Home Assistant as entities. The entities will write their current state to the state machine for other entities/templates/frontend to access. States are a current representation of the entity.
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "Templating"
|
||||
description: "Instructions on how to use the templating feature of Home Assistant."
|
||||
redirect_from: /topics/templating/
|
||||
---
|
||||
|
||||
This is an advanced feature of Home Assistant. You'll need a basic understanding of:
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "Troubleshooting your configuration"
|
||||
description: "Common problems with tweaking your configuration and their solutions."
|
||||
redirect_from: /getting-started/troubleshooting-configuration/
|
||||
---
|
||||
|
||||
It can happen that you run into trouble while configuring Home Assistant. Perhaps an integration is not showing up or is acting strangely. This page will discuss a few of the most common problems.
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "YAML"
|
||||
description: "Details about YAML to configure Home Assistant."
|
||||
redirect_from: /getting-started/yaml/
|
||||
---
|
||||
|
||||
Home Assistant uses the [YAML](https://yaml.org/) syntax for configuration. YAML might take a while to get used to but is really powerful in allowing you to express complex configurations.
|
||||
|
||||
@ -2066,6 +2066,19 @@
|
||||
/integrations/switch.knx /integrations/knx#switch
|
||||
/integrations/weather.knx /integrations/knx#weather
|
||||
/integrations/zigbee /integrations/xbee
|
||||
/getting-started/basic /docs/configuration/basic
|
||||
/getting-started/customizing-devices /docs/configuration/customizing-devices
|
||||
/getting-started/devices /docs/configuration/devices
|
||||
/getting-started/securing /docs/configuration/securing
|
||||
/getting-started/troubleshooting-configuration /docs/configuration/troubleshooting
|
||||
/getting-started/yaml /docs/configuration/yaml
|
||||
/topics/events /docs/configuration/events
|
||||
/topics/packages /docs/configuration/packages
|
||||
/topics/platform_options /docs/configuration/platform_options
|
||||
/topics/secrets /docs/configuration/secrets
|
||||
/topics/splitting_configuration /docs/configuration/splitting_configuration
|
||||
/topics/state_object /docs/configuration/state_object
|
||||
/topics/templating /docs/configuration/templating
|
||||
|
||||
# Migrated Community Guides
|
||||
/cookbook/apache_configuration https://community.home-assistant.io/t/reverse-proxy-with-apache/196942
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user