-
-
Notifications
You must be signed in to change notification settings - Fork 704
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EVCC Version V0.131.0 or newer getting timeout issues when connecting to EM2GO Home #17879
Comments
Can be closed, solved. This happens in connection with a Power-LAN WLAN adapter if it is connected to a socket in whose circuit an interfering power supply is connected. |
With version 0.131.12, the process has to be restarted several times before the wallbox adapter can be read correctly. There seems to be a synchronization or time problem with the connection to the EM2GO Home. These connection attempts should become more robust (longer timeout, multiple attempts before abort) |
After a successful start, however, the error messages described above no longer appear. The only critical thing is the launch of EVCC. |
That sounds like a network problem.
vs
Which is true? Please add trace logs of working and non-working. |
It's true that the first reason was my notebook ac adapter disturbing the Power-LAN traffic because it was plugged-in the socket directly beside the Power-LAN-WLAN adapter. I moved the Power-LAN-WLAN adapter to another socket and it works without any message. Only the startup process fails by random and requires 2 or 3 attempts to run. Because this is a timeout, I assume that the timeout limits should be adjusted or it should try it several times before aborting the connection attempts with an error message. |
Did a restart |
Please reproduce this with a wired LAN connection. |
That's not possible. There isn't any socket in the vicinity of the EM2GO Home. And the EM2GO Home doesn't have a LAN socket too. It's only usable with WLAN. And I had to configure an own WLAN because EM2GO Home has password limits of 30 digits but my WLAN password has 32 digits. And I can't change all settings of over 20 devices because one piece of hardware seems not to consider network standards. |
I assume that the Firmware is weak. It fails at smallest connection issues. Now I can't get it to start again after the test for creating the TRACE. I already rebooted the network parts and the EM2GO. I've a lot of work and will abort it at this point. I'm short before sending back the EM2GO. |
Now I set the display time to 5 minutes, which was my last change to reduce it to 1 minute. Don't know if that was the reason. I switched off modbus, load-control and WLAN on the box, switched everything on again and did a cold restart. Know I got it to run again. From my view as IT engineer it's a bad implementation of network traffic in the box itself. But how to deal with it? I already informed D-Parts. But maybe there is a possibility to improve the handshake from outside too. |
Additional test:
I tried it, because I did the migration today morning and after failing I restored it too, but it works only if there are the additional steps on the EM2GO Home. It seems that the connection attempts cause an internal module crash in the wallbox which even wasn't fixed by cold restart, because during the first case today morning I tried only a cold restart and this didn't help. During last test I didn't perform a cold restart, only the above commands and it worked. Can reproduce this. |
Describe the bug
Tested different versions now to connect to EM2GO Home.
Hardware Version: E22_1.2
Software Version: A03C_1.3
UI Version: 010.5
App connection works immediately without problems. Network connection is stable.
Steps to reproduce
...
Configuration details
Log details
What type of operating system are you running?
Windows
Nightly build
Version
evcc version 0.131.0
The text was updated successfully, but these errors were encountered: