@checking12@TexTown You can assume that all suppliers have stopped selling the old ECU-R models (out of stock). So if you buy an ECU-R check the box if the ID starts with 2162xxxxxxx. Then you are good.
Judging from articles in the news, it is currently best to take a dynamic contract.
If you decide to switch to Tibber you can get €50 Tibber credit if you use my invite code: x88h9drn
Some explanation about the origin of the ECU-R-Pro naming: At some point APsystems released a new version of the ECU-R. Instead of ECU-ID 2160xxxxxxx these new ECU-R models have ECU-ID 2162xxxxxxx. These new models have firmware version: ECU_R_PRO_2.1.23 and that’s how the name ECU-R-Pro came about.
i was indeed checking dynamic providers, however saw only one of them not having ‘terugleverkosten’ which i thought was weird. But having control over per inverter activity, i can plan good things and never export again (or limit to certain value) when the time comes
I have been looking for an ECU with serial starting with 2162. I finally manage to get one and the software is working excellent. I can control the inverters now.
I have been in contact with some suppliers and one told me that they had 3 ecu’s starting with the number 2163xxxxxxx. So, it seems there is an even newer version available. Not sure what firmware it runs. But perhaps something to keep an eye out for.
Yes, that’s the ECU-B - this model only supports max four panels. If you plan to add panels in the future, you’d better buy an ECU-R or ECU-C (3-phase).
Hello everyone. Cool integration. Thanks for the hard work. I’m just planning my future setup. Small apartment with space for only two panels (not yet bought) attached to one APsystems DS3-H 960W microinverter (already bought). I’m now in the process to buy the ECU. I would like to avoid injection to the net so the ECU should adapt the solar production to the house consumption. Correct me if I’m wrong but I think that ECU-C is able to do that (zero injection) but it is much more expensive than ECU-R or ECU-B.
So the question is: do you know if R or B models can perform “zero injection”? Which ECU would you buy in this small setup? Thanks for your feedback.
B definitly not.
R newer version you will be able to control yourself.
C can do more on its own by using clamps (2nd hand around 200 Eur i’ve seen), still thinking if i like that more then new R type and do it myself
However, they had a hard time delivering it. They said it was in stock, when it wasn’t. I eventually received the correct one. Tried many other shops as well, but none of them were able to deliver it.
Unfortunately, jbsolar.nl is explicitly advertising the ECU-R as " APS ECU-R monitoring unit, model 2160". I guess they had enough of inquiries.
I received a 2160 of winkelman-zonnepanelen.nl and haven’t called them yet. I’ll reach out in the morning whether they can swap it into a 2162. Did you try them as well?
Man, I am having bad luck with Dutch webshops, they stocked the 2160XXX ECU-Rs and all dependent on their supplier. They basically tell the same story: they sometimes get 2162XXX but not that often. It seems like a lottery.
So far I tried:
winkelman-zonnepanelen, jbsolar, elektrototaalmarkt, sellectzonnepanelen.
I bought my ECU-R 2162 at WD Solar, all other Dutch webshops sucks saying they have the right one, but they didn’t.
If you are still looking for a ECU-R 2162xxxx try:
(Do not forget to ask for the 2162 model)
I asked WD Solar, and he will get back at my inquiry. In return, he asked why people are looking particularly for the 2162 model. So I explained.
It seems that there are about 3 suppliers, whereof one big supplier that does closely business with APSystems. It’s intransparant how to ensure a 2162 model can be obtained. One of the webshops is going to inquire the big supplier, but I probably can’t wait that long for a new batch…
I’m testing the “APsystems ECU Reader” integration with my ECU-R 2160 (firmware V1.3.18) and I’ve run into an issue: I can’t add the ECU to my Home Assistant monitoring.
The ECU is connected via Wi-Fi to my local network with a fixed IP address. I can successfully “ping” it and even execute the command APS1100160001END, receiving the expected response on line 4 as per the integration’s website.
However, when I try to add the integration in Home Assistant using the ECU’s IP, even after waiting more than 10 minutes, I get the message: “No ECU found at this IP-address or ECU is recovering from restart”.
Currently, I don’t have any microinverters installed, and consequently, there’s no production data in the EMA App. I also haven’t created an EMA account. I’ve only borrowed this ECU-R from a friend initially to see if I could integrate it with Home Assistant for monitoring purposes using your (HAEdwin- APsystems ECU Reader) integration.My main question is whether the absence of data or a registered EMA account could be causing this error.
Also, I have another question regarding future expansion. For controlling, sending energy, power on/off microinverter, and other more advanced functions, would it be better to purchase an ECU-R or an ECU-C (which has the advantage of Ethernet connectivity)? And for the ECU-C, should I try to get one from the 2162 series?
Any help or guidance would be greatly appreciated!
This will prevent the ECU from shutting down when it doesn’t find a cloud/internet connection. I don’t like little Chinese blackboxes in my home network that call home with me not having control over it. And when you deny internet access to the ECU unit, it stops working after 2 or 3 days.
This proxy works around that, you just need to set a few custom DNS rules in your router or pihole instance for example
That’s indeed my first implementation of this proxy method. However, a few weeks ago, I discovered that the data is now encrypted (which is better, of course), so this method was discarded. I’ve already hidden my own repositories for that reason. If you’d like to test the proxy method again, let me know, and I’ll temporarily open the repository of the final implementation.
I’m currently experimenting with full Modbus integration but am running into incompatibility issues. For example, the ability to switch off individual inverters via Modbus isn’t implemented. The firmware still needs significant improvements to become fully functional.
Oh interesting. Your old method still seems to work fine on a ECU-B-EU box. I threw that proxy up on a local device with the correct DNS entries and the ECU-B-EU started responding/working again with the cloud LED back on.
