Connection to ECU_R refused during configuration

[RastaChaum]

Requirements for submitting a bug

Help us by sharing us the relevant home-assistant.log part.

Cette erreur provient d'une intégration personnalisée

Enregistreur: custom_components.apsystems_ecu_reader.config_flow
Source: custom_components/apsystems_ecu_reader/config_flow.py:121
intégration: APsystems ECU Reader (documentation, problèmes)
S'est produit pour la première fois: 11:20:33 (3 occurrences)
Dernier enregistrement: 13:34:33

APsystemsInvalidData exception: failed to claim socket after 5 attempts

Expected Behavior

Should connect to AP System ECU_R

Current Behavior

When validating ECU Confirguration, saying : Aucune ECU trouvée à cette adresse IP ou l'ECU est en train de récupérer d'un redémarrage

Possible Solution

Steps to Reproduce

Just adding the integration and following step by step configuration manual...

Home Assistant hardware

• Raspberry Pi
• Docker container
• Virtual Machine
  - Core : 2025.4.4
  - Supervisor : 2025.04.1
  - Operating System: 15.2
  - Interface utilisateur: 20250411.0
• Other

PV-hardware

Providing context helps us come up with a solution that is most useful in the real world

• ECU-B

• ECU-R (2160 series)

• ECU-R-Pro (2162 series)

• ECU-C

• ECU-3

• DS3 series

• QS series

• QT series

• YC series

APsystems ECU Reader v2.7.2

Notes

For now, i used the previous unmaintened integration : https://github.com/ksheumaker. I never had problem to connect to ùy ECU_R.
But, like i saw that this integration isn't maintened anymore, i try to migrate to this new one :

• i removed the old
• i downloaded the new
• and now, i'm trying to configure my ECU system without success ! :( :(

I'm sure of my IP. When scanning open port, i have just 2 opened ports (but not the one specifiy in the doc) :

nc -z -v 192.168.1.88 1-65535 2>&1 | grep -v 'Connection refused' 
Connection to 192.168.1.88 502 port [tcp/*] succeeded!
Connection to 192.168.1.88 4540 port [tcp/*] succeeded!

[HAEdwin]

I converted this to a discussion because it is not a bug. When you use the nc -v {ip-address} 8899 command you should get a prompt immediately and you can input the APS command.

If you don't get this prompt, you don't have the correct IP address of your ECU or since you are running HA on a VM I think the port is not open. Check the VM configuration.

[HAEdwin]

So when you opened Terminal in HA and use the NC command, you get no response. Make sure you've got the IP-address right. Ping the ECU using ping {ip-address} -t and turn off the ECU, when it still replies you have the wrong IP-address. I have an ECU-R 2160 also, no issues.

[RastaChaum]

Yes, no response in the terminal (from anywhere : HA VM, PC, ...). I'm sure this is the good IP because :

• this is the IP that i used with the previous integration and i configured this IP as static in my router
• if i power off the ECU, this IP is no longer reacheable with ping
• with the EMA Manager App, this is the IP displayed when i go to Desktop > Network Settings

[RastaChaum]

Another informations :

• my ECU is connect to the LAN via RJ45 wire
• i remember (BUT not sure !) that in the previous integation, the NC command on port 8899 didn't work too... (don't know why)

[RastaChaum]

I back to the previous integation to test.
And surprised : i can't to connect to my ECU now !!

APSystemsInvalidData exception: [Errno 111] Connection refused

I don't explain why, because it worked before. BUT when looking my Energy Dashboard, i see that i didn't receive data from the ECU since the 24th April 2025.... Diging again... (perhaps an update of HA or firmeware)

[RastaChaum]

Find the problem ! It's my bad.

I finally found that my ECU model has 2 IP !

• the first assign to the RJ45 connection !
• the second assign for the wifi connection !

It seems that they don't have the same role. With the second IP, it works !

I will disconnect the RJ45 to avoid such mistake in the future !

Really sorry for this thread ! But it could be usefull for other person with the same config. Perhaps adding a warning in doc to explain this situation ?

[HAEdwin]

No problem, I have actually encountered this situation before with someone. On the issue form I will add a question how the ECU is connected, that might help with the many options that exist in case of connection problems.