Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

exclude not applied? #252

Open
michalk-k opened this issue Jan 20, 2025 · 0 comments
Open

exclude not applied? #252

michalk-k opened this issue Jan 20, 2025 · 0 comments

Comments

@michalk-k
Copy link

Here is my ltss config:

ltss:
  db_url: postgresql://ha:ha@77b2833f-timescaledb/ha_timescale
  chunk_time_interval: 2592000000000
  include:
    entities:
      - sensor.glances_cpu_load
      - sensor.glances_cpu_used
      - sensor.glances_cpu_percent
      - sensor.glances_cpu_thermal_0_temperature
      - sensor.glances_ram_free
      - sensor.glances_ram_used
      - sensor.glances_ram_used_percent
      - sensor.glances_swap_free
      - sensor.glances_swap_used
      - sensor.glances_data_free
      - sensor.glances_swap_used
      - sensor.glances_data_used_percent
    entity_globs:
      - sensor.wattsonic*
      - sensor.*energy
      - sensor.*power
      - sensor.*temperature
      - sensor.*memory_percent
      - sensor.*cpu_percent
      - sensor.*memory_percent
  exclude:
    entity_globs:
      - sensor.shelly_3em_cube*

The include adds sensors matching sensor.*power which matches many sensors. I would like to exclude a few from this bunch, thus excluding sensor.shelly_3em_cube*

Unfortunately following sensors are still being stored to timescaleDB:

  • sensor.shelly_3em_cube_phase_3_power
  • sensor.shelly_3em_cube_phase_1_power
  • sensor.shelly_3em_cube_phase_2_power
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant