Recorder exclusion

Configuration
1

I have been reconfiguring my record settings and now it is almost usefull and possible to work with, but I have an issue with my climate entities.

When I add my climate entities I get 3 values from them - Heating, Current temperature and Target temperature.
The Heating value makes no sense in my case, since I can not set it to cool or anything else and it will always follow the value of Current temperature, although with that slight difference that the graph will have a almost solid field filled below the graph for the Heating values.
This solid field distort the graphs, so I have to click off the Heating values every time I need to use them.

Is there a way to either disable the filling of the area below the graph or simply disable these Heating values all together?

2

What card are you using, or is it in Grafana ?

3

Its just the History page

4

Ok, thou in my History i don’t have any “Fill” … and i really can’t remember if i have “removed it” my self or what :upside_down_face:
PS: i think you can use configuration.yaml

History:
  exclude:
     entities:
´´´
PS: i didnt use correct indented here, just example( it's pretty much like recorder, include/exclude)
5

Ok, I need to add some info. :slight_smile:

recorder part in configuration.yaml:

recorder:
  auto_purge: true
  purge_keep_days: 15
  commit_interval: 1
  include:
    entity_globs:
      - climate.bedroomthermometer
      - climate.guestroomthermometer
      - climate.kitchenthermometer
      - climate.livingroomthermometer
      - climate.officethermometer

This result in this graph:

current
current2252×466 129 KB

If I turn of all the Heating values, then I get the graph is would like to have.

want
want2259×473 160 KB

6

Just noticed I had entity_globs instead of entities, but I do not think that does any difference though.

7

wow… yeah , mine looks like the 2nd pic … the above looks pretty weird :slight_smile: … you can remove them (Heating Values) from History, but still have in Recorder, with above … then maybe use a graph-card for the Heating-values, and see how it behave there

8

I guess it is because my wall thermostats directly controls the valve thermostats, so they actually have heating and cooling as a state.

9

ok, but still looks crazy, as it seems to “fill/color” everything, i mean even the “top” in the middle, that is also present below (maybe living-room temperature)

10

No its just the heating from all the climate entities that overlaps.
Here is one with just the sensors from bedroom selected.

bedroom
bedroom2259×479 128 KB

11

ahh ok, you had 4 “disabled” in 2nd pic, i see now … remove those in config…yaml , until you figure out why they behave like this … 1 of the reasons i don’t like History … they just shuffle everything into 1 graph, as long as it’s same “measurement” … so % is a mix of Humidity and Batteri level , CPU, DISK etc … lol, i try to avoid clicking on History :slight_smile:

12

I guess making a Grafana view or a lovelace card would give some more control over the graphs.
It might be the solution I choose if noone else can get rid of that fill.

I can’t remove the disabled graphs, since they are automatically part of the climate entities.
Thanks for trying though. :slight_smile:

13

? you mean they don’t have an “individual” entity_id ?

14

nope. It is just climate.something

15

But as the “system” categorize" them as Temperature, and your not in control of where they end in History, i feel it look like a Bug …

16

I am actually not sure where it gets that Heating value from.

If I look in Developer Tools I only get this:

State

  • Heat

Attributes

  • hvac_modes: auto, heat, off
  • min_temp: 4.5
  • max_temp: 30.5
  • target_temp_step: 0.5
  • preset_modes: boost
  • current_temperature: 21.3
  • temperature: 19
  • current_humidity: 40
  • preset_mode: none
  • id: 00265BE98E7FA1
  • interface: ip
  • battery: High
  • rssi_device: -65
  • mode: null
  • voltage: 2.7
  • friendly_name: Bedroom Thermometer
  • supported_features: 17
17

Maybe it is a bug.

18

It Depends which “Device_Class” it is, most likely your Climate falls under “Temperature” Device_class … you can find out looking in configuration/device&entities, then click the devices tab find the device, click it, and click “Download Diagnostic” … Or in “core.entity_registry” … but be careful in there, is a “running” system file

19

Its part of an integration, so I have no device listed, only entities. :frowning:

20

core.entity_registry did not help much either.

core-entity_registry
core-entity_registry336×501 50.8 KB