ECUB data is reset every night to the value of the night before.

[HAEdwin]

ECUB data is reset every night to the value of the night before. In my case it is reset every night to 600 kWh.

This gives me a negative yield in HA every morning.

If I connect directly to the ECUB I see that the value there also starts at 600 every day.

So this is a problem with the ECUB and not with the HA integration.

I have reported this to APSystemsema but I don't think they will do anything about it.

Now I wonder if more people are experiencing these problems.

[Woetter22]

ksheumaker/homeassistant-apsystems_ecur#284 (reply in thread)

After the advice to redownload the package and then replace the sensor.py the error messages are gone.

When the sun shines I am unfortunately not at home so I hope I have the chance to log in remotely today.

[Woetter22]

the results of today

[HAEdwin]

Today Energy is not equal with Lifetime Energy Produced - do you know why Today Energy is zero?

[Woetter22]

Today's energy is always zero for me since the daily resets started
In the ECU it is always set to 0.

[TexTown]

I think the daily reset of 'Lifetime Energy' and 'Today Energy' being 0 all the time are both firmware issues.
I have both issues as well, but on an ECU_R running FW version 1.2.31

[Woetter22]

I think so too, these are purely firmware issues.

[HAEdwin]

@TexTown From your last screendump I can see that the Lifetime Energy is not being reset and the previous screendump suggests that it is the Lifetime Energy but are you sure you didn't label it wrong? Isn't that the Today Energy entity? @Woetter22 you might want to take a look at this also, I didn't thought of that earlier but the label and entity ID might not match up.

[TexTown]

Iv'e been using utility_meter sensors (based on the 'Lifetime Energy' ) to calculate daily (but also monthly and yearly) solar usage.
So I'm working around the 'Today Energy' being 0 all the time.

[HAEdwin]

Yeah, it's a great integration but there's no "lifetime" cycle option from what I understand. I asked Diogo Gomes if it is currently possible to create a lifetime sensor and if not, would it be possible to add the "lifetime" cycle option.

Reason for me asking this is because I realize that for 98% of the users, the additional lifetime_enery_produced sensor might not add anything - so I really have to explain why this sensor is introduced in the next release. The lifetime cycle option would make the utility_meter integration so much more applicable don't you think?

To compensate for this new sensor, I created an additional lifetime_maximum_power sensor (that's something I'd like to keep an eye on to track what the PV is capable of producing at its maximum).

[Woetter22]

Iv'e been using utility_meter sensors (based on the 'Lifetime Energy' ) to calculate daily (but also monthly and yearly) solar usage. So I'm working around the 'Today Energy' being 0 all the time.

How did you get those bars so nicely colored and scaled?

[TexTown]

Here's part of the code, it uses a HACS custom card

type: vertical-stack
cards:
  - type: custom:bar-card
    height: 25px
    decimal: 1
    max: 50
    positions:
      name: inside
      icon: "off"
    entities:
      - entity: sensor.daily_solar_energy
        color: orange
        name: Vandaag - Zonnepanelen
        icon: mdi:solar-power
      - entity: sensor.daily_energy_production
        color: green
        name: Vandaag - Teruglevering
      - entity: sensor.daily_energy
        color: darkred
        name: Vandaag - Net Gebruik
      - entity: sensor.daily_energy_usage_total
        name: Vandaag - Totaal Gebruik

[TexTown]

The month and Year blocks have a different 'max'

I use another version of this custom:bar-card to have a visual view of all solar panels as layed out on my roof, showing their current Watt and colourred per inverter. I'll take a screenshot on a sunny day and post it here.

[HAEdwin]

@TexTown and @Woetter22 I allready got an anwer from Diogo: "The utility meter can indeed be setup without any cycle, therefore becoming a lifetime sensor. just skip the definition of cycle".

Considering the above I think a more generic solution is to use the utility_meter. I refer to my comment that I realized the extra lifetime_energy_produced might confuse other users, not adding anything for those with working firmware. So I'd prefer to leave the sensor out. Will that work for you both?

[Woetter22]

@HAEdwin your attempt in the new sensor.py is indeed not going to be of use for many.
is it an idea to add this sensor as disabled?
Then the interested parties can turn this on. That should be explained in the manual I think.

[TexTown]

The utility_meter sensor without the cycle parameter works fine. Yesterday 10Kwh, and today continuing from 10Kwh, currently at 14.4 (10+4.4)


Next step: adding the missing value using a 'Counter Helper' to get the real lifetime value.

[TexTown]

@HAEdwin your attempt in the new sensor.py is indeed not going to be of use for many. is it an idea to add this sensor as disabled? Then the interested parties can turn this on. That should be explained in the manual I think.

I'm not in favor of adding a disabled sensor to the integration. It will only be useful if you start from scratch (new ECU). If you start later and enable the sensor for an existing system you are missing the produced value. Very confusing, specifically for new users.
Using the utility_meter approach and a helper works better for me.

[TexTown]

I've reported the 'reset' problem to APSystems and keep you updated in this thread.

[Woetter22]

I'm curious, I hope they treat you with more respect.