Update logbook.markdown (#1824)

Elaborated the fact that the "recorder" component storage settings have an effect on the "logbook" component. It was unclear to me before. See https://community.home-assistant.io/t/history-with-mysql/10027 for details.
This commit is contained in:
nodomain 2017-02-13 11:46:29 +01:00 committed by Fabian Affolter
parent e59ce8b3e7
commit bae50112a6

View File

@ -11,7 +11,7 @@ logo: logbook.png
ha_category: "History"
---
<img src='/images/screenshots/logbook.png' style='margin-left:10px; float: right;' height="100" /> The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in reverse chronological order. [See the demo for a live example](/demo/).
<img src='/images/screenshots/logbook.png' style='margin-left:10px; float: right;' height="100" /> The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in reverse chronological order. [See the demo for a live example](/demo/). It depends on the `recorder` component for storing the data. This means that if the `recorder` component is set up to use e.g. mySQL as data store, the `logbook` component 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: