From 1c6eb26c0f0b868bcb3cce70a36356dbaad65d11 Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Tue, 23 Jun 2020 15:54:06 -0500 Subject: [PATCH] Remove deprecated hidden attributes from logbook (#13820) --- source/_integrations/logbook.markdown | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/source/_integrations/logbook.markdown b/source/_integrations/logbook.markdown index 30fb4655693..b718018d155 100644 --- a/source/_integrations/logbook.markdown +++ b/source/_integrations/logbook.markdown @@ -100,10 +100,8 @@ logbook: ### Exclude Events -Entities customized as hidden are excluded from the logbook by default, -but sometimes you want to show the entity in the UI and not in the logbook. -For instance you use the `sensor.date`to show the current date in the UI, -but you do not want a logbook entry for that sensor every day. +If you have `sensor.date` to show the current date in the UI, +but you do not want a logbook entry for that sensor every day it can be excluded. To exclude these entities just add them to the `exclude` > `entities` list in the configuration of the logbook. @@ -112,6 +110,9 @@ list. For instance you use the `sun` domain only to trigger automations on the `azimuth` attribute, then you possible are not interested in the logbook entries for sun rise and sun set. +Excluded entities still take up space in the database. It may be advisable to +exclude them in `recorder` instead. + ### Custom Entries It is possible to add custom entries to the logbook by using the script