From bae50112a6b895fb4aa1ae0f9ebcaa0d40f9134e Mon Sep 17 00:00:00 2001 From: nodomain Date: Mon, 13 Feb 2017 11:46:29 +0100 Subject: [PATCH] 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. --- source/_components/logbook.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/logbook.markdown b/source/_components/logbook.markdown index bd3d2743755..df888657269 100644 --- a/source/_components/logbook.markdown +++ b/source/_components/logbook.markdown @@ -11,7 +11,7 @@ logo: logbook.png ha_category: "History" --- - 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/). + 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: