Make Recorder Logbook and History Includes avaialable for editing on the entities page

Feature Requests
21

You wouldn’t remove existing functionality, you would add an additional filter after the existing filter in the pipeline that could override the global behavior

Regular filter still work

   exclude:
       entities_glob: sensors.*

on the entity provide a setting that can add it back into the list if its filtered out, or ignore it
some entity:
Logbook Override: dropdown-> Default, Always, Never

or, for the power user, allow setting when the filter is applied, before or after global filter (the before would be applied in code as if they were put in the existing “include → entities” list or “exclude → entities” list from yaml.
some entity:
Logbook: dropdown-> Default, Always, Never , include, exclude

No reason to break anything. There would possibly be the issue that you double listed an entity (one in include and one in exclude for example) but that issue is possible and exists today so its not a new problem. It can be handled the same way or improved upon.

1 Like
22

Bumping an old thread but very curious if this is on the roadmap… would absolutely use it

23

:+1:
bumping up a really useful feature.

24

Bumping!! Could ABSOLUTELY use this feature!

1 Like
25

Another bump, I don’t want to log history or anything for bulbs and even some appliance status, I don’t need to know that my washing machine was 70% compete at midday 3 weeks ago :smiley:

1 Like
26

I just thought of another great use for this feature. Sometimes I’d like to keep an eye on a particular entity for a day or a few days. Maybe I’m changing something, maybe I want to verify that an automation has been running correctly, flipping switches or whatever which I typically don’t care about monitoring.

Wouldn’t it be great if we could go into the UI, check a box and start recording all that data which is typically useless? Then when I’m finished debugging, un-check it just as easily.

As far as I know, right now the only way to do this is to modify the YAML and restart HA.

27

This would be a great addition, hopefully implemented soon.

28

:rofl: Don’t hold your breath. Look when I started this request.

3 Likes
29

Hope is all we have left, lol.

30

I was looking for how to exclude entities from the history in order to avoid logging unnecessary data and the database growing unnecessarily, but I understand here that it simply doesn’t exist? :open_mouth:

31

Yes it does, but you have to manually configure it in configuration.yaml

32

As part of the system itself this has to be already implemented. There are many other FR with lot more votes. But many are integrations.

I think this is something useful as part of HA itself.

33

Please! My logs are inundated with useless information.

34

If not possible to implement for backward compatibility, then break compatibility after certain version? :slight_smile:
Other simple approach could be a GUI for the recorder.yaml file. Where it shows all the entities with a toggle switch, and a few filters so you can find the entities you want. Also the entries count in the DB for that particular entity would help a lot so you dont have to manually check the DB to see what is taking up most of your space.