Remove actions from logbook

Configuration
1

How can i remove events from the logger? I know you can specify, but how can i remove these ones:

image
image496×1229 125 KB

As you can see its just constantly ready/sleep/ready/sleep. I don’t have to see that :stuck_out_tongue: only makes my logbook that much slower as it is i would presume (besides that it has less value with all this in it)

Txs

2

You can exclude that sensor from being logged.

Example configuration.yaml entry with include and exclude

recorder:
  include:
    domains:
      - sensor
      - switch
      - media_player
  exclude:
    entities:
     - sensor.last_boot
     - sensor.date

EDIT: My mistake, use logger and not recorder as squirtbrnr mentioned to remove from logbook

3

If you want to remove any kind of state history, follow what RobDYI posted. If you want to keep state history (the history that shows when you click on the entity or state card) but you don’t want it to show in the logbook, then apply the same include/exclude to the logbook: section of your configuration. Same goes for the history too.

4

You can disable a sensor like that, but this is the zwave ‘actions’ ? the sleep/ready?
The normal Motion sensor action i do want to keep.

So in example below, should i disable zwave.thermostaat_evi? Because if the example of the recorder/logbook that would just remove all z-wave actions. Is there any ‘good practice’ examples on this? If i add the example from RobDYI would i still have the normal things that a person would want? I mean, sensors/switches/media_players only does make sense now that i look into it. Would also help improve speed i would think. Thanks so far both guys :slight_smile:

image
image968×382 42.9 KB

5

I would just exclude the entire zwave domain from recorder and/or logbook - that will get rid of those messages, but still keep the entries for lights and such being turned on and off (as those entities fall under the light and switch domains)

6

I excluded/included as the example, added a few sensors like power generation of the solar panels to the exclude too, ones that change often but has no real value as history. Will wait a few days and see if it all improves, lets hope so. :slight_smile:

7

@RobDYI
As recorder and logbook use the same database, doesn’t that also mean they use the same data? Logbook is just another perspective of what the recorder records?

So excluding a domain/entity in recorder is also indirectly excluded in logbook?

Of course if you still want it in recorder you should exclude it separately in logbook.yaml, but otherwise recorder is the better option to prevent maintaining two files, one for recorder and one for logbook?
Can you confirm my understanding is correct?
It’s not yet clearly stated in the docs for logbook

8

Yes. That’s what I posted right after…

Excluding from Recorder removes all state history, period.
Excluding from Logbook removes the state history from the Logbook, but leaves it in the recorder so you can still click on an entity and see the history.

9

ahh sorry, I missed that reply! I’ll try to submit a change in the docs so it’s more clear there as well