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-05-29 06:16:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Recorder page - rename component to integration (#9953)

Browse Source 
Changes 4 mentions of "component" to "integration"
This commit is contained in:
Sean Mooney 2019-07-23 06:21:22 -04:00 committed by Franck Nijhof
parent a902ed8281
commit b1c42a1b43
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
source/_components/recorder.markdown
View File

@ -8,7 +8,7 @@ ha_release: pre 0.7
ha_qa_scale: internal
---
The `recorder` integration is responsible for storing details in a database, which then are handled by the [`history` component](/components/history/).
The `recorder` integration is responsible for storing details in a database, which then are handled by the [`history` integration](/components/history/).
Home Assistant uses [SQLAlchemy](http://www.sqlalchemy.org/), which is an Object Relational Mapper (ORM). This means that you can use **any** SQL backend for the recorder that is supported by SQLAlchemy, like [MySQL](https://www.mysql.com/), [MariaDB](https://mariadb.org/), [PostgreSQL](https://www.postgresql.org/), or [MS SQL Server](https://www.microsoft.com/en-us/sql-server/).
@ -23,7 +23,7 @@ recorder:
{% configuration %}
recorder:
description: Enables the recorder component. Only allowed once.
description: Enables the recorder integration. Only allowed once.
required: true
type: map
keys:
@ -115,7 +115,7 @@ recorder:
- sensor.date
```
If you only want to hide events from your history, take a look at the [`history` component](/components/history/). The same goes for the [logbook](/components/logbook/). But if you have privacy concerns about certain events or want them in neither the history or logbook, you should use the `exclude`/`include` options of the `recorder` component. That way they aren't even in your database, you can reduce storage and keep the database small by excluding certain often-logged events (like `sensor.last_boot`).
If you only want to hide events from your history, take a look at the [`history` integration](/components/history/). The same goes for the [logbook](/components/logbook/). But if you have privacy concerns about certain events or want them in neither the history or logbook, you should use the `exclude`/`include` options of the `recorder` integration. That way they aren't even in your database, you can reduce storage and keep the database small by excluding certain often-logged events (like `sensor.last_boot`).
### Service `purge`