It would be a shame not to keep trying. If you abandon the fixed IP address assignment and simply let the ECU obtain an IP address via DHCP, will ping work? Is the ECU on the same (IoT?) network?
So Sorry I was a bit busy these last days…
I know it would be a shame but I can’t make it work whatever I try. So I try this :
- I disconnected the ethernet cable.
- Pressed the button on the ECU
- Connected to the wifi ECU_R216…
- went to network options in ema manager app
- accepted “obtain an ip adress automaticaly”
- connected to my wifi network
- Obtained an IP adress : 192.168.131.228
- Rebooted
- got no answers when I ping 192.168.131.228
It’s only connected to my local network when I connect it by cable.
I really don"t know what to do.
It’s difficult to determine exactly where the problem lies remotely. However, if you’ve obtained an IP address wirelessly and you restart the ECU, it can take a while before you receive a response to a ping. However, since the Wi-Fi interface obtains an IP address, I don’t assume it’s broken. Once you do receive a response to the ping, try turning off the ECU and see if the response stops. If so, you’ve at least connected to the correct node. Then turn the ECU back on and wait 10 minutes. Then configure the integration, and everything should work fine. Do read the available documentation Installation using HACS (Recommended) · HAEdwin/homeassistant-apsystems_ecu_reader Wiki · GitHub
Could this be caused by a firmware issue?
Is the 2160 running the latest firmware version?
The solution proposed by Apsystems is to use TCP MODBUS.
but it’s the same. I cannot communicate with the ECU
I finally managed to do it with Modbus TCP ! That was not easy but I did it with the help of copilot. You need to follow apsystems instructions. You must activate modbus in ema manager and put some yaml in configuration and it’s good.
Thank for your help @HAEdwin.
Unfortunately the modbus options are very limited but reading is indeed possible.