Apstorage Integration

[FabTribe68]

Hello everyone,
I installed an APS Apstorage to add batteries to my installation.
In the apstorage there is an ECU-C but I cannot integrate it.
The ECU-C of the Apstorage has a different firmware than the ECU-C of my first installation. I have access to the 2 ECU-Cs with the IP addresses.
The integration of the first ECU-C went without problems.
I would like you to have the battery data in home assistant.
Regards,
Fab

[HAEdwin]

If APsystems is kind enough to provide me with a storage system ❤️ and some inside info, I might be able to help you. Without reference hardware, that is an impossible task 😞 (unless another Python programmer steps up that is)

[luispb]

Hello everyone, I installed an APS Apstorage to add batteries to my installation. In the apstorage there is an ECU-C but I cannot integrate it. The ECU-C of the Apstorage has a different firmware than the ECU-C of my first installation. I have access to the 2 ECU-Cs with the IP addresses. The integration of the first ECU-C went without problems. I would like you to have the battery data in home assistant. Regards, Fab

@FabTribe68, can you share more details on what happens when you use this integration with the APstorage ECU-C? What error are you getting?

[FabTribe68]

Hi luispb,
He is unable to connect to the ECU-C.
The Apstorage has an ECU-C integrated with a different firmware than the one I have for the solar installation.
I can view the data from the EMA App or the EMA website. I can also access the data from the hidden menus of the Apstorage ECU-C.
The CTs are connected to the Apstorage and not to integrated the ECU-C

[luispb]

Thank you @FabTribe68. What happens exactly when you try to configure the ecu-reader integration pointing it to the IP of the ECU-C that's inside the APstorage? Can you share screenshots/logs of the error you get? Can you also share the exact APstorage model that you have? Is it the ELS-5K inversor?

[FabTribe68]

Yes, it is the ELS-5K.
The error:
"Aucune ECU trouvée à cette adresse IP ou l'ECU est entrain de récupérer d'un redémarrage"
Translate:
"No ECU found at this IP address, or the ECU is recovering from a restart."
I think this ECU is using another port.
I can send you the logs tonight when I am back home.

[FabTribe68]

If I test the connection, I can connect, but I don't get a response.
Test with LAN and WLAN:

[luispb]

Thanks for the update, @FabTribe68 — that's really helpful. Hopefully someone else can chime in with further insights. > @HAEdwin, even if you don’t have direct access to a storage unit, is there anything we could test for you that might help identify how to support these units in the integration?

[HAEdwin]

So on both ECU-C's the 8899 port seems to be available and both ECU-C's can still be configured using the EMA manager App? The "nc: too many output retries" is somewhat concerning and the lack of response on the 1.142 also. Though if you are still able to use the EMA manager app there may still be a small chance that it will work after a hardware restart of the ECU. Be patient after a restart because it might take up to ten minutes before valid data is again passed through. I'll investigate if there are any changes in the EMA manager app later and will get back to you.

[FabTribe68]

Hi HAEdwin,
the 2 ECU-Cs have been restarted.
Solar ECU-C:

Apstorage ECU-C on both IPs:

I can use both on EMA manager App

But there are differences between the two.

Solar ECU-C Firmware C1.2.19

Apstorage ECU-C Firmware C1.3.20

The Apstorage ECU-C do not see the DS3 MOs and i have no Power or production graph.
The Data are not in the same place:

Apstorage:

Bye
Fab

[HAEdwin]

What are the first three digits the DS3's start with?
Mind putting the integration into debug mode and post the data here together with matching current parameters from the ECU/HA GUI?
It's hard to anticipate on firmware 1.3.20 is that the ECU which came with the APStorage?

[FabTribe68]

The integration work with solar ECU-C, but not Apstorage ECU-C. I see all the data except that of the CTs in the integration.
1.3.20 is the ecu-c integrated into apstorage. The ECU-C ID start with 2152xxxxxxxx

Solar ECU-C DS3's

[FabTribe68]

and the logs if i try to integrate the Apstorage:

2025-06-22 10:21:55.015 DEBUG (MainThread) [custom_components.apsystems_ecu_reader.ecu_api] Socket successfully claimed
2025-06-22 10:21:55.019 DEBUG (MainThread) [custom_components.apsystems_ecu_reader.ecu_api] Socket resources released
2025-06-22 10:21:55.019 WARNING (MainThread) [custom_components.apsystems_ecu_reader.config_flow] APsystems invalid data exception for ECU None: received data is none

[HAEdwin]

Ok, thank you. In summary the problem is in the specific ECU-C mounted in the APstorage, it does seem to open the connection on 8899 but it does not respond on the APS command like you showed and you pressed Ctrl+C to interrupt the proces:

The other ECU-C is working fine, right?

I do not hope APsystems is hardening their systems because it would mean an end to this integration for all users. I couldn't find any info on the 1.3.20 firmware. You could try if other ports are open and accept the APS command or more advanced install BlueStacks and the EMA manager app and see using WireShark if the traffic is encrypted or now running on a different port. I'm afraid I can't help without owning an APstorage system, might even never get it to work. Hopefully APsystems will support HA in the future. Homebatteries are overall better secured i.e. communication.