I’m happy and sad for you. But it will all get better now
Thank you so much for sharing/feedback, I would have never expected that this could also be the cause of issues when using the integration.
Yeah, maybe because it’s frequently reading and writing from and to the drive which caused odd behavior when the system had intermittent issues communicating with the drive. Perhaps retrying in the background but not sure on what to do when retries where exhausted or something. I just now start to realize how much work I put into HAOS over the past year, because I’m now recreating automations and such and it’s a hell of a lot of work TBH. Well it’s the bigger fails from which we learn the most.
hello everyone, I have a quick question and im sorry if it was already responded but this treat is very large and impossible to read all, I did several searches and still cannot find confirmation, I have an ECU-R 2160xxxxxxxx but its connected via wired because I have no stable wifi signal where the ECU is located and I cannot relocated, so my only option is wired. I know the table says for this model the connection needs to be wireless. The question is if there is any way this integration can work via wired? appreciate any help given. Thanks in advance
Hi jsalva23,
Unfortunately, port 8899 is only open on the WiFi interface and not on the Ethernet interface. I don’t think APSystems will change that in the firmware. I personally do not actively monitor whether a new firmware version may offer support, there are no release notes associated with new APSystems firmware, which in itself is of course a downside in quality.
That’s a shame , I wont be able to use this integration then…. Thanks a lot for your response.
The next version of Home Assistant (2024.6, release date june 5th) includes a core APSystems integration, but this new integration will only support the APsystems EZ1 microinverter. These Wifi/Bluetooth models apparently have a local API…
Yes, I know and it was expected. I personally have never had the ambition to have the integration included in the core because the developed approach has not been officially recognized by APSystems. They can end the “exploit” at any time, but that will of course disappoint around 580 active users of this integration who don’t have an alternative to include data in HA. The new path that APsystems is taking with the EZ series is a wise choice IMHO.
My installer contacted me today that data on the apsystems site wasn’t being updated anymore. I restarted my ECU and it worked again for a few hours. Seems this started since my ECU updated to the 1.2.31 firmware.
Even after a reboot, it only works for a short while.
Anyone else seeing the same issue?
The good news is that the Home assistant integration is not affected. Getting data from the ECU locally works perfectly.
I have no issues after the firmware upgrade on my ECU-R 2160-------- checked EMA. Still sad APsystems does not publish any release notes with the firmware!
Had some duplicate entities after September update. Any one else seeing the same?
Hi Sander, no issues with double entities here.
For me either, no problems.
After DB update ha restarted, seems fine again…weird
Calculation is not accurate but how to correct…
I’m not able to get the same values EMA calculates. Here’s the case:
I downloaded all yesterdays ECU data from the EMA site (column A & B) converted the values to kW (column C), multiplied each value by 5/60 (column D) which results in column F values. These values differ from the G column which are the hourly values downloaded report from the EMA site.
Sorry about the small representation but to indicate, the 11th hour is way off from the value EMA reports.
Anyone who’s good at maths?
are you sure the EMA site calculates instead of harvesting the data from the ECU?
The thing is that power over 5 minute period will not be stable and inverters can report kwh better if measured there at device. If you watch increas of the ‘daily kwh’ in HA, does the delta in hour 11 match the EMA or the calculated from column F?
Column B are the Power values that are being sent by the ECU to EMA. In fact the ECU does not send kWh values to EMA but now you mention it, the ECU does send it’s Lifetime Energy values to EMA and these are also in kWh so maybe I have to focus on that. This would result in 4,8 kWh total for this day which comes closer to the value EMA shows. I’ll have to collect data again to see if it matches, had some errors on the day I downloaded the data. Btw Lifetime Energy displayed on the EMA site is way of from the Lifetime Energy the ECU holds…
Will look into it when I’ve got time, thanks for your response.
got some warnings in the log regarding this integration
* ENERGY_KILO_WATT_HOUR was used from apsystems_ecur, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfEnergy.KILO_WATT_HOUR instead, please report it to the author of the 'apsystems_ecur' custom integration
* POWER_WATT was used from apsystems_ecur, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfPower.WATT instead, please report it to the author of the 'apsystems_ecur' custom integration
* ELECTRIC_POTENTIAL_VOLT was used from apsystems_ecur, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfElectricPotential.VOLT instead, please report it to the author of the 'apsystems_ecur' custom integration
* TEMP_CELSIUS was used from apsystems_ecur, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please report it to the author of the 'apsystems_ecur' custom integration
* FREQUENCY_HERTZ was used from apsystems_ecur, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfFrequency.HERTZ instead, please report it to the author of the 'apsystems_ecur' custom integration
anyone else seen it, or is it just me being on a wrong version?
I see now, thats some time ago and now I see it, i do remember applying those fixes too.
Things are getting back to me now. I also turned log level to error only to get better idea of what real errors i had (looong time ago). Didnt turn it back to warning until recently.
I know what to do now, thx!