[OTHER] Energy Date Selection on secondary obj want update sensor info

[flyzet-prog]

Hello dear developer. I Have been tested secondary info with my sensors, and it won’t track them every hour, day etc. always see zero. Energy date selection enabled. The sensors updates as should be.
please help me to resolve this issue.
Tried in different ways, no luck

[flixlix]

Can you try setting the same entity for the solar field and secondary info? That way, you can make sure if the current secondary info. entity has any statistics being recorded

[flyzet-prog]

If entity the same they shows the same values and updates both, but as soon if i chose different sensors secondary object sensor wan’t update and always shows zero. Hope this helps some how

[flixlix]

Alright, this means that the entity that doesn't work is not being saved to statistics.
For it to be tracked, make sure the entity follows the requirements:
https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics

[flyzet-prog]

Alright, this means that the entity that doesn't work is not being saved to statistics.
For it to be tracked, make sure the entity follows the requirements:
https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics

It’s obvious that my sensors is saved to statistic. Kindly check my screenshots bellow. Bellow you can see energy devices graph Jun 10(emty), and today Jun 11 already populating. Btw it’s only works if i chose 2 identical entities on main and secondary info. Also secondary info not clickable on home obj. I would be much appreciated if you can resolve this bug please

[flixlix]

Can you send me the code you are using?

[flyzet-prog]

Of course, here is the code bellow

type: custom:energy-flow-card-plus
entities:
  grid:
    entity:
      consumption: sensor.z_merezhi_za_den
    display_state: one_way
    power_outage: {}
    secondary_info:
      entity: sensor.s3
      unit_of_measurement: Uah
      energy_date_selection: true
      display_zero: false
      icon: mdi:currency-uah
      unit_white_space: false
    invert_state: false
  solar:
    entity: sensor.pv_energy_today
    secondary_info:
      unit_of_measurement: Uah
      icon: mdi:currency-uah
      display_zero: false
      unit_white_space: false
      entity: sensor.s1
      energy_date_selection: true
    display_zero_state: true
  battery:
    entity:
      consumption: sensor.battery_consumption
      production: sensor.battery_production
  home:
    override_state: true
    entity: sensor.house
    secondary_info:
      icon: mdi:currency-uah
      display_zero: false
      clickable_entitie: true
      unit_white_space: false
      entity: sensor.s2
      unit_of_measurement: Uah
      energy_date_selection: true
  individual1:
    entity: sensor.boiler_socket_energy_meter
    name: Water heater
    color_icon: true
    color_value: false
    display_zero_state: true
    decimals: 2
    icon: mdi:water-boiler
    use_metadata: false
    color:
      - 63
      - 132
      - 198
    display_zero: true
    secondary_info:
      unit_of_measurement: Uah
      unit_white_space: false
      display_zero: false
      icon: mdi:currency-uah
      energy_date_selection: true
      entity: sensor.s4
  individual2:
    entity: sensor.conditioner_socket_energy_meter
    display_zero: true
    use_metadata: false
    icon: mdi:air-conditioner
    name: Air conditioner
    inverted_animation: false
    decimals: 2
    display_zero_state: true
    color_value: false
    secondary_info:
      unit_of_measurement: Uah
      display_zero: false
      unit_white_space: false
      icon: mdi:currency-uah
      energy_date_selection: true
      entity: sensor.s5
kwh_decimals: 2
energy_date_selection: true
clickable_entities: true
use_new_flow_rate_model: true
display_zero_lines: false
wh_decimals: 2

[flixlix]

Hmm, you don't have any display_zero_tolerance in there. I thought that was it, that's why I asked for your code.
Otherwise, can you swap the secondary info entity and the main entity to see if that changes the behavior?
And what is getting printed in the browser console?

[flyzet-prog]

Hmm, you don't have any display_zero_tolerance in there. I thought that was it, that's why I asked for your code. Otherwise, can you swap the secondary info entity and the main entity to see if that changes the behavior? And what is getting printed in the browser console?

If I chose the same sensor(SOLAR) in the main and secondary info it's showing as in the screenshot below. If I swap them up, the main is working as usual, and the secondary shows always zero.

[flixlix]

I'm sorry, but I don't think I can help you fix this issue, since it seems to be working with some entities and not with others 😔

[flyzet-prog]

Unfortunately, it doesn't work with any entity when energy_date_selection: is true on secondary info. It can be a very cool feature if we can track both different sensors at one obj. I believe you can try to fix it in the future. Anyway, thank you for your efforts.

[mmyrfield]

I'm having what looks like the same issue. Energy Date Selection is on in the "Advanced Options".

I've added utility meter sensors to the individual 1 and individual 2 main entities, and other utility meter sensors as the "secondary info" entities. When setting Energy Date Selection to "on" in the secondary info sections, only 0 displays regardless of the date selected, like so:

When turning the Energy Date Selection to "off" in the secondary info sections, today's values are displayed regardless of date selected, like so:

Note the same is true for the secondary info in the Fossil Fuel section. These entities are not utility meters, but do have statistics entries in the statistics table.

If I move the entities around, whichever one is in the main entity slot works properly, but the one that goes in the "Secondary Information" entity exhibits the behaviour above; displaying zero if "Energy date selection" is on, and only the current date value if off.
See here switching the main vs secondary entities in Individual 1 with energy date selection off (bottom right circle):

and with date selector on in the secondary for the same:

I'm wondering if this is a bug in how the card retrieves the secondary information entity values?