I am mostly only tracking sensors. I am wondering if the sensor domain is excluded by default? There is just 1 switch explicity included in the recorder (because I need to count the number of times switched).
Actually, according to the doc’s logbook is locked to recorder. I would assume it would be locked to history as well. That means those may drive what logbook prints out.
I just now noticed that I have history: and logbook: configured in both configuration.yamland the recorder package. I will fix this tonight and see if that makes a difference.
I have removed all customization of recorder, history and logbook. Everything is showing as expected. I noticed that frequently updated sensors (like CPU usage) are excluded from the logbook (but are visible in history).
I will try to re-add inclusions and exclusions to see when things don’t work as expected again.
This is my config and it works like i would expect:
# Enables support for tracking state changes over time
history:
include:
entities:
- binary_sensor.hallway_ms_sensor
- sensor.main_door_hindge
- sensor.entry_door_hindge
- sensor.speedtest_download
- sensor.speedtest_upload
- sensor.speedtest_ping
- sensor.cpu_load_total
- sensor.disk_free
- sensor.processor_use
- sensor.average_disk_temp_volume_1
- sensor.hallway_ms_temperature
domains:
- light
- switch
- fan
exclude:
entities:
- switch.inside
- switch.outside
- switch.upstairs
- switch.downstairs
- switch.dining_room
- switch.kitchen
- switch.master
- switch.basement
recorder:
db_url: !secret recorder_url
# View all events in a logbook
logbook:
Logbook still doesn’t show the sensors that update all the time. Pretty much only shows binary_sensor.hallway_ms_sensor, sensor.main_door_hindge, sensor.entry_door_hindge, and sensor.hallway_ms_temperature in the logbook (sensor wise).