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

[Woetter22]

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]

[Woetter22]

[TexTown]

I have the exact same issue, but with an ECU-R. It has been going on for months.

[HAEdwin]

I have not seen this happen on my ECU-R or my ECU-R-Pro. I don't think it should happen on the ECU-B either. Is it stil going on with the latest firmware?

[TexTown]

Sometimes this is also visible in the logs

Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:317
integration: Sensor (documentation, issues)
First occurred: 04:50:10 (1 occurrences)
Last logged: 04:50:10

Entity sensor.ecu_lifetime_energy from integration apsystems_ecur has state class total_increasing, but its state is not strictly increasing. Triggered by state 18967.3 (18969.8) with last_updated set to 2025-02-09T03:49:37.109175+00:00. Please create a bug report at https://github.com/ksheumaker/homeassistant-apsystems_ecur/issues

[Woetter22]

Is it worth filing a bug report here? Since it is a problem within the hardware of apsystems. And not necessarily with this software

[Woetter22]

Another note, between January 5th and January 25th it worked fine spontaneously

[TexTown]

I had a correct increasing value from 5-dec-2024 to 2-jan-2025, so indeed sometimes it is OK.
But currently it resets every night.
Did you get a response from AP Systems?

[Woetter22]

My original ticket was closed. I created a new ticket asking if there was a solution regarding my previous ticket. Now they responded that they want my password so they can look into my account.

[TexTown]

Curious what they will find and report back.

I've started using automations to not query the ECU during the night, to see what happens when I skip the usual reset time. That didn't help. As soon as I started queuering the ECU again, the first value I got was the reset value. So the ECU actually does something (or gets instructed by AP Systems) that decreases this value back to the same as the day before.

[Woetter22]

That could be right,
HA reads the data from the ECU. And it resets itself to a certain value every night so it doesn't matter when you read or don't you will get a minus in production.

I am working on an automation with a counter. The counter only counts the positive change and does not look at the value.
Then I use a conferter that converts the counted to KWH. And then another conferter that converts that to a value that the energy dashboard can read. (in the last step I add the generated so far so that the values ​​are correct.)

But this is a temporary solution that I am not happy with. so I sincerely hope the manufacturer comes up with a solution

I also hope that more people will create a ticket at apsystems so that it is given more urgency.

[Woetter22]

I have the results of the contact with the manufacturer. After a lot of email contact and logging of data they have come to the conclusion that the data in their app and web portal are displayed correctly. That the data on the ECU is reset every night does not seem to be important to them. In every email I was addressed more and more unfriendly and less professional. They have not responded to my last questions for more than a week now so I expect that they are turning their backs on me and with that the community. In the last email I asked if something is possible to solve the problem in the ECU. A reset has not yielded anything for me. After a reset all data is still the same except the wifi password. and the inverters are disconnected. But they do not want to answer that question. I also did not receive a response to the question whether buying a new ECU would solve the problem. So I am afraid that we have to find a solution ourselves based on the daily registered production and then add that up to a lifetime production.

[HAEdwin]

Yes I was thinking to do that.

• a new entity called: "lifetime energy produced"
• an option to enter the current lifetime energy as stated on the EMA website via the configuration settings
• daily energy will then be added to "lifetime energy produced" (there can still be a difference between EMA and HA. This also has to do with the moments at which the samples are made).
• of course the "lifetime energy produced" entity must be preserved after a HA reboot

But in the end this behavior of a daily lifetime energy reset is of course not good. Apparently a firmware update does not solve it either, very strange. Of course I do not see this behavior on my ECU-R or ECU-R-Pro. I can also not give any guarantee that a new ECU will solve the problem. APsystems has only intended the function to be used as a short term troubleshooting option during installation, not as a continuous monitoring option. In the meantime more than 720 people use this option on Home Assistant alone, let alone the other home automation solutions.

[Woetter22]

It would be great if this function would be built into the program. Then we don't have to search for a solution individually. But I also understand that it is not a priority if it only affects a few of many.

[TexTown]

Very disappointing responses from APSystems.

One possible direction for a solution: I have the 'utility meter' integration that records daily/monthly/yearly solar production based on that same 'lifetime' ECU sensor. Strangly, that utility meter sensor is working just fine, adding up each day.

yearly_solar_energy:
source: sensor.ecu_lifetime_energy
cycle: yearly

We'll have to figure out if utility meter could handle a cycle which is 'indefinitely'

[HAEdwin]

Other solutions are:

• Scraping the built-in website (not suitable for ECU-R and ECU-B)
• Using Modbus (not suitable for ECU-R and ECU-B)
• Proxy method (not suitable for ECU-R-Pro and ECU-C)
• ECU-reader https://github.com/HAEdwin/homeassistant-apsystems_ecu_reader (suitable for all ECUs, with sometimes different results due to firmware, home network connectivity issues, firmware instability)

One not explored is the serial port but this one can only be activated on the ECU-R-Pro and ECU-C because I don't think it is activated on the ECU-R and ECU-B.

[Woetter22]

I will test the ECU-reader https://github.com/HAEdwin/homeassistant-apsystems_ecu_reader (suitable for all ECUs, with sometimes different results

[TexTown]

As mentioned earlier in this thread, I do see the problem with an ECU-R (2160) running firmware version ECU_R_1.2.31

Could this reset be coming from (during?) the connection with Apsystems?
Might be worth to try blocking network access from the ECU during the night.

[HAEdwin]

Worth a try, ecu.apsystemsema.com is the datacenter. I've blocked access in the past but this had some unwanted effects on the ECU which thinks there is something wrong with the internet connection. But the ECU will recover from that when the datacenter is not being blocked anymore. ecueu.apsema.com is the (firmware) update center (for Europe)

[TexTown]

I have a firewall rule in place now that blocks apsystemsema.com access for the ECU between 22:00 and 06:00.
Let's see if that makes a difference.
@Woetter22 I've already migrated to the new 'ECU-reader' and experience the same issue. Still a reset every night somewhere between 4 and 5 AM

[Woetter22]

I think I made a mistake somewhere when replacing the sensor.py
I'll try again tomorrow when the sun is shining

[TexTown]

It worked for me, but have to wait for sun to get a valid value i guess...
(indeed we should take this discussion to the correct repository)

[TexTown]

https://docs.github.com/en/discussions/managing-discussions-for-your-community/managing-discussions#transferring-a-discussion

[HAEdwin]

Can't move the discussion because Kyle is no collaborator of my repository (I could make him collaborator but might have to bother him then) and I only have collaborator rights on his.

[HAEdwin]

@Woetter22 I'd advise a redownload of the latest version then replace the sensor.py and then restart Home Assistant. Let's continue the discussion here: HAEdwin/homeassistant-apsystems_ecu_reader#10