core: entity_glob entities in recorder no longer functional

The problem

all of the entities that are included in recorder via entity_glob: are showing flatlines. History is working, for the individually included entities

Environment

  • Home Assistant Core release with the issue: 117.0b2
  • Last working Home Assistant Core release (if known): 116.4
  • Operating environment (OS/Container/Supervised/Core): OS
  • Integration causing this issue: Recorder (or history)
  • Link to integration documentation on our website: https://www.home-assistant.io/integrations/recorder/

Problem-relevant configuration.yaml

part of the logging/recorder.yaml:

db_url: !secret db_url
purge_keep_days: 5

include:
  !include included_entities.yaml

exclude:
#  !include excluded_entities.yaml

  entities:
    - sensor.solaredge_last_updatetime
    - sensor.solaredge_last_changed

  event_types:
    - service_removed
    - service_executed
    - platform_discovered
    - homeassistant_start
    - homeassistant_stop
    - feedreader
    - service_registered
    - call_service
    - component_loaded
    - logbook_entry
    - system_log_event
    - automation_triggered
    - script_started
    - timer_out_of_sync

included entities.yaml:

entity_globs:

  - device_tracker.life360_*
  - sensor.*_power_daystart
  - sensor.*_usage_daystart
  - sensor.*_calibrated_temperature
  - sensor.*_actueel
  - sensor.*_state
  - sensor.*_totaal
  - sensor.calculated*
  - sensor.l1*
  - sensor.l2*
  - sensor.l3*
  - sensor.teller*

  - sensor.zp*
  - sensor.solaredge_*
  - sensor.speedtest*

  - switch.*

entities:

  - binary_sensor.family_home
  - binary_sensor.daughters_home

  - sensor.family_home
  - sensor.daughters_home

configuration.yaml:


history:
logbook:
recorder: !include logging/recorder.yaml

Traceback/Error logs


Additional information

history: Schermafbeelding 2020-10-23 om 17 01 42

more-info: Schermafbeelding 2020-10-23 om 17 02 12

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 16 (10 by maintainers)

Most upvoted comments

The problem was caused by incorrect configuration:

  • Excluding the sensor domain has higher priority than trying to add a sensor through a glob
  • The event_types exclude configuration excluded state_changed events