Replies: 1 comment
-
Answered via PM |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
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!
Beta Was this translation helpful? Give feedback.
All reactions