Hello there!
APsystems ECU Reader is a custom integration for APsystems inverters except for the EZ series. Previously this integration was called homeassistant-apsystems_ecur.
Because I notice that issues are sometimes better or easier handled via this forum I am starting this new topic. I hope you enjoy the integration. If you like it, support me via https://buymeacoffee.com/haedwin or rate the integration by giving it a star. Many thanks!
Volgensmij bent u nederlands dus ga het gewoon proberen. Zou jij mij even kunnen helpen met dit opzetten want ik heb het nu al een paar keer geprobeerd maar hij kan hem maar niet vinden. Is het een must dat hij verbonden is via wifi of mag ethernet ook?
Hallo Nick,
Sorry to hear it doesn’t work. Your question about WiFi or Ethernet suggests you haven’t read the documentation. Depending on the model, you can find the answer here.
At this moment I can not provide you with the right answer, you give too little information for that. If the manual does not work, I would like to know what type of ECU you have. I will be happy to help you further.
Guys, please keep the conversation in English, otherwise I’m afraid the moderator will lock this thread.
So right, I thought it was a PM.
Hello, I just had an ECU-R setup. I’ve got it connected via Ethernet, not wireless and it has a statically assigned IP (via Static DHCP on my Firewall). I’ve read through the Readme docs and looked at the code. It looks like it’s expecting the ECU-R to have port 8899 open, however, my ECU-R only has TCP ports 502 and 4540 open.
I read somewhere that if connected via wired ethernet it does not use port 8899, and uses 4540. However, the port is hard configured to 8899 in the code. I also confirmed that the HA install can see and connect to the ECU-R successfully from the command line. Also, using netcat (nc) I sent the test string “APS1100160001END” from the readme to the ECU-R but nothing returned.
Does this mean that this software is not compatible with my ECU-R? or do I just manually change the port number in the code and try again?
Please provide the first 4 digits of your ECU-R (2160 or 2162) depending on this follow the connection table. I’m pretty sure you should be able to get it working because more than 850 people did. Also provide the firmware version just to make sure. Common mistake with people having more IoT devices is that they try to connect to another device not the ECU because the interface might be ESP also.
I know it’s the correct device, that part I’ve confirmed.
The first 4 digits are 2160. That was the first problem, I didn’t realize the model wasn’t a standalone number so I was missing it when searching for it on the bottom of the unit. I had assumed it was the 2162 since it was new, that was incorrect. According to the connection table it will not work via a wired connection. So that answers that question. This afternoon I’ll set it up via wireless on that VLAN and I’m sure it’ll be fine from there.
Indeed, from what I’ve read, there’s still a whole batch of (older) ECU-R models on the market. The newer version 2162 has more options in the firmware like shutting down inverters.
Just to close off the loop. I switched over to Wireless (and disconnected the Ethernet) and the requisite ports became available. Everything else from that point worked as the README.md described.
Thanks!
I hope to find some help here. I used to have 11 active inverters. 22 panels. Suddenly one became unavailable in HA only.
In an attempt to repair I deleted the inverter and I’ve removed and reloaded the ecu entirely. Doesn’t work unfortunately. Since deletion the inverter is not only unavailable but nowhere to be found.
Any tips are appreciated. I need to have all in HA so they switch off with negative energy prices.
@BkSteen When you are using the latest version of GitHub - HAEdwin/homeassistant-apsystems_ecu_reader: APsystems ECU Local Query Integration for Home Assistant you can enable debug logging (Settings > Devices & Services, select the APsystems ECU Reader integration and at the right upper corner you can find the hamburger menu, klick on it to enable Debug Logging). You can send me a DMS for the part where the logline contains “raw inverter data:”. So I can further look into it. Also please mention the type of ECU you are using.
Thanks, i’m learning HA. I’ve enabled debugging. I take it I just copy/paste that from the HA Settings > systems > Logs area? It will probably then only be updated when the ECU actually starts receiving data from solar.
Type of ECU is 2162 ECU-R. I’ll review the logs after some sun and see whats what. Thanks for helping out!
@BkSteen Welcome to the HA community! The debug logging is not visible in the system log. Best thing you can do is install File editor. You can do that by going to: [Settings] > [Add-ons] and from the lower right corner choose [Add-on store] under the Official add-ons you can find the “File editor”, “Simple browser-based file editor for Home Assistant”. After installing this add-on you should be able to find the File editor in the left side-menu, start it and in the folder view navigate to “homeassistant/” in that folder you will find the “home-assistant.log”, single click to open it. Now you will be able to find the logline I mentioned earlier.
HA is great! In the beginning you have to find your way and acquire some basic knowledge, but after that it becomes more and more fun and you discover all kinds of new features and possibilities.
I’ve restored to the old situation where the specific inverter is still there, enabled debug logging (agian, forgot to redo it after restoring a backup) and now i have the logging visible. Will report when i have the line in my home-assistant.log.
Edit: Feel like a bit of a tool but i have one example of the line now. Can I just post it here or is that a security risk, if not, how do i safely share.
@BkSteen The issue is very similar to YC1000 inverter Unavailable efter updating to 2.12.1 · Issue #106 · HAEdwin/homeassistant-apsystems_ecu_reader · GitHub
It was fixed in the latest 2.14.0 release I just did.
You don’t really need the EMA manager, the ECU app is also still fine. After configuring the ECU you should be able to use this integration for Home Assistant to monitor the ECU.
Thanks. I just figured it out. I was trying to connect the device and it wouldn’t connect. It’s called Altenergy Power and is hard wired which wouldn’t work. Then I found the esp on my network connected to WiFi and that connected. Thanks!
