-
-
Notifications
You must be signed in to change notification settings - Fork 6
Description
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!