jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-22 00:36:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Patch 5 (#10824)

Browse Source 
* Update history.markdown

mentioned that this is included in default_config

* Update automation.markdown

mentioned that this is included in default_config

* Update cloud.markdown

mentioned that this is included in default_config

* Update config.markdown

mentioned that this is included in default_config

* Update frontend.markdown

mentioned that this is included in default_config

* Update logbook.markdown

mentioned that this is included in default_config

* Update map.markdown

mentioned that this is included in default_config

* Update person.markdown

mentioned that this is included in default_config

* Update ssdp.markdown

mentioned that this is included in default_config

* Update sun.markdown

mentioned that this is included in default_config

* Update system_health.markdown

made default_config blurb more consistent

* Update updater.markdown

mentioned that this is included in default_config

* Update zeroconf.markdown

mentioned that this is included in default_config

* Update automation.markdown

linked default_config

* Update cloud.markdown

linked default_config

* Update config.markdown

linked default_config

* Update frontend.markdown

linked default_config

* Update history.markdown

linked default_config

* Update logbook.markdown

linked default_config

* Update map.markdown

linked default_config

* Update mobile_app.markdown

linked default_config

* Update person.markdown

linked default_config

* Update ssdp.markdown

linked default_config

* Update sun.markdown

linked default_config

* Update light.mqtt.markdown

typo fix
This commit is contained in:
1DontEx1st 2019-10-16 15:15:47 -04:00 committed by Fabian Affolter
parent 9d11f18f5c
commit 0090ae5789
15 changed files with 28 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
source/_integrations/automation.markdown
View File

@ -31,3 +31,12 @@ automation:
- platform: state
...
```
## Configuration
This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
```yaml
# Example configuration.yaml entry
automation:
```

4
source/_integrations/cloud.markdown
View File

@ -10,6 +10,10 @@ ha_iot_class: Cloud Push
The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services like Amazon Alexa and Google Assistant. [Learn more.](/cloud)
## Configuration
This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
```yaml
# Example configuration.yaml entry to enable the cloud component
cloud:

2
source/_integrations/config.markdown
View File

@ -10,7 +10,7 @@ ha_qa_scale: internal
The `config` integration is designed to display panels in the frontend to configure and manage parts of Home Assistant.
To enable the configuration panel, add the following to your `configuration.yaml` file:
This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
```yaml
# Example configuration.yaml entry

2
source/_integrations/frontend.markdown
View File

@ -8,7 +8,7 @@ ha_qa_scale: internal
ha_release: 0.7
---
This offers the official frontend to control Home Assistant.
This offers the official frontend to control Home Assistant. This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
```yaml
# Example configuration.yaml entry

3
source/_integrations/history.markdown
View File

@ -14,8 +14,7 @@ component for storing the data and uses the same database setting.
If any entities are excluded from being recorded,
no history will be available for these entities.
To enable the history option in your installation,
add the following to your `configuration.yaml` file:
This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
```yaml
# Basic configuration.yaml entry

2
source/_integrations/light.mqtt.markdown
View File

@ -8,7 +8,7 @@ ha_iot_class: Configurable
ha_release: 0.8
---
The `mqtt` light platform with lets you control your MQTT enabled lights through one of the supported message schemas.
The `mqtt` light platform lets you control your MQTT enabled lights through one of the supported message schemas.
## Comparison of light MQTT schemas

3
source/_integrations/logbook.markdown
View File

@ -17,8 +17,7 @@ the `recorder` integration for storing the data. This means that if the
PostgreSQL as data store, the `logbook` integration does not use the default
SQLite database to store data.
To enable the logbook in your installation,
add the following to your `configuration.yaml` file:
This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
```yaml
# Example configuration.yaml entry

2
source/_integrations/map.markdown
View File

@ -8,7 +8,7 @@ ha_qa_scale: internal
ha_release: 0.56
---
This offers a map on the frontend to display the location of tracked devices. To set up tracked devices, look at the [device tracker](/integrations/device_tracker/) documentation.
This offers a map on the frontend to display the location of tracked devices. To set up tracked devices, look at the [device tracker](/integrations/device_tracker/) documentation. This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
```yaml
# Example configuration.yaml entry

3
source/_integrations/mobile_app.markdown
View File

@ -16,8 +16,7 @@ If you are a mobile app developer, see the [developer documentation](https://dev
## Configuration
This integration is by default enabled, unless you've disabled or removed the `default_config:` line from your configuration.
If that is the case, the following example shows you how to enable this integration manually:
This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
```yaml
# Example configuration.yaml entry

2
source/_integrations/person.markdown
View File

@ -32,7 +32,7 @@ You can manage persons via the UI from the person page inside the configuration
## Configuring the `person` integration via the Home Assistant configuration panel
If you prefer to use the configuration panel to configure the `person` integration simply add one line to your `configuration.yaml` file and restart Home Assistant.
This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
```yaml
person:

2
source/_integrations/ssdp.markdown
View File

@ -12,7 +12,7 @@ Integrations can opt-in to be found by adding [an SSDP section](https://develope
## Configuration
To integrate this into Home Assistant, add the following section to your `configuration.yaml` file:
This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
```yaml
# Example configuration.yaml entry

2
source/_integrations/sun.markdown
View File

@ -17,6 +17,8 @@ below the horizon. The sun can be used within automation as
## Configuration
This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
```yaml
# Example configuration.yaml entry
sun:

3
source/_integrations/system_health.markdown
View File

@ -10,9 +10,10 @@ ha_release: 0.87
The System Health integration provides an API to offer information on the system and its components. It also allows to run diagnostic tools to diagnose problems.
System health is included as part of the [default config](https://www.home-assistant.io/integrations/default_config/) starting with Home Assistant 0.88. If you do not wish to use the default config, you can add the following to your configuration.yaml file.
This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
```yaml
# Example configuration.yaml entry
system_health:
```

2
source/_integrations/updater.markdown
View File

@ -20,7 +20,7 @@ The `updater` binary sensor will wait one hour after startup until it performs t
## Configuration
To integrate this into Home Assistant, add the following section to your `configuration.yaml` file:
This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
```yaml
updater:

2
source/_integrations/zeroconf.markdown
View File

@ -13,7 +13,7 @@ Integrations can opt-in to be found by adding either [a Zeroconf section](https:
## Configuration
To have Home Assistant scan for integrations using zeroconf and HomeKit, add the following section to your `configuration.yaml` file:
This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, and you wish to have Home Assistant scan for integrations using zeroconf and HomeKit, the following example shows you how to enable this integration manually:
```yaml
# Example configuration.yaml entry