Hello Frederic.
Can you please try to update the FW of your EVCS to v2.01.
There were some improvements in communication with GX.
If that does not help - please write me PM, and I will check your system to find the problems.
Hello Frederic.
Can you please try to update the FW of your EVCS to v2.01.
There were some improvements in communication with GX.
If that does not help - please write me PM, and I will check your system to find the problems.
Hello,
So I have the same issue I think.
The EVCS is fully updated and I installed a wifi point almost next to it.
It is connected, signal is full and it is stating OK.
But it is completely not responding.
Removing wifi credentials, reboot, add credentials, reboot and then it works for a bit.
Or well works, it doesnāt throw an error. (104)
Now it seems to work, but no idea for how long.
Before reboot and re enter credentials
equest timeout for icmp_seq 158
Request timeout for icmp_seq 159
64 bytes from 192.168.31.49: icmp_seq=121 ttl=64 time=39444.863 ms
Request timeout for icmp_seq 161
64 bytes from 192.168.31.49: icmp_seq=122 ttl=64 time=40586.225 ms
64 bytes from 192.168.31.49: icmp_seq=123 ttl=64 time=39930.214 ms
Request timeout for icmp_seq 164
Request timeout for icmp_seq 165
64 bytes from 192.168.31.49: icmp_seq=124 ttl=64 time=42375.020 ms
Request timeout for icmp_seq 167
Request timeout for icmp_seq 168
After reboot
64 bytes from 192.168.31.49: icmp_seq=841 ttl=64 time=302.396 ms
64 bytes from 192.168.31.49: icmp_seq=842 ttl=64 time=238.868 ms
64 bytes from 192.168.31.49: icmp_seq=843 ttl=64 time=87.968 ms
64 bytes from 192.168.31.49: icmp_seq=844 ttl=64 time=88.994 ms
64 bytes from 192.168.31.49: icmp_seq=845 ttl=64 time=13.308 ms
64 bytes from 192.168.31.49: icmp_seq=846 ttl=64 time=232.013 ms
64 bytes from 192.168.31.49: icmp_seq=847 ttl=64 time=146.810 ms
64 bytes from 192.168.31.49: icmp_seq=848 ttl=64 time=70.189 ms
Request timeout for icmp_seq 850
Request timeout for icmp_seq 851
64 bytes from 192.168.31.49: icmp_seq=851 ttl=64 time=1591.819 ms
64 bytes from 192.168.31.49: icmp_seq=852 ttl=64 time=1635.070 ms
64 bytes from 192.168.31.49: icmp_seq=853 ttl=64 time=1404.572 ms
64 bytes from 192.168.31.49: icmp_seq=854 ttl=64 time=404.685 ms
64 bytes from 192.168.31.49: icmp_seq=855 ttl=64 time=195.597 ms
64 bytes from 192.168.31.49: icmp_seq=856 ttl=64 time=1128.520 ms
64 bytes from 192.168.31.49: icmp_seq=857 ttl=64 time=161.029 ms
With 2.01 occasionally the problem is still there.
I have the same issue since the last firmware and very important an upgrade of my unifi access Point to the latest Wifi7 standard. Before I had Unifi acces point UAP 6 Pro , now UAP 7 Pro & outdoor AP
Seems like time is not important - sometimes lost connection after a day - sometimes 3 days . cannot take consistency out of it . But I wonder if the EVCS cannot do a sheduled reboot every night if you want to do that or during the day . would be great to have such an option @Lpopescu
Hello Kenny Buntinx.
Can you please share more details about the problem?
So for me:
Network still shows āOKā on the network settings page when connection via BT.
And it is sometimes able to connect again, since I see it connected to vrm/gx from time to time.
Now it has 4 hours ago last check-in.
When it is connected wifi is at 56-60dbm. (also previously there was another car charger at the same spot, also using an esp32 and that worked)
What also is interesting is the ping.
A lot of request timeouts, then one or few hits (slow) and then timeout.
But when rebooting it shows host down, so there is some communication
Hello hvdb.
Ok, thanks for the detailed feedback. It seems like EVCS is going into AP mode. Can you please check two things when it happens:
Additionally, can you please describe which router you are using and any specific settings for it?
I donāt think it is going in AP mode.
As when I force that, the ping will fail (host down)
So now I cannot access the web interface for instance.
The ping is working 1 in 50times (with high latency)
VRM shows the last contact was 23m ago.
(before it was 4hours or more)
It is still shown in the GX devices as well.
Now during typing this: in the Ping I see a host down a few times.
(no AP network is active)
Is there a way to see the uptime?
Or how busy the esp is?
I am using a wifi6 router with a satelite (wired) nearly behind the charger.
It is combined network (2.4 & 5)
Let me see if I can get some old wifi point and set that to 2.4 only.
I used to have a thermostat that was really not working when the channels are combined and it would even need channel 6. Else it would not work
ok. Yes, it will be great if you can try with only a 2.4GHz network.
Alright it took a bit longer ![]()
But good news!
It works perfectly on a dedicated 2.4 network.
No high ping, no connection issues nothing. It is always connected it seems.
Although wifi is at -80 (while previously with combined wifi it was -60)
So it seems that it doesnāt like (at least mine) combined 2.4/5 network (wifi6)
It seems like this evcs has the same problems as my old Atag One hadā¦
It doesnāt like channel 11.
With that channel I had the same issues as earlier, moved to 6 and it is working fine.
Will do some testing if the same applies on a combined network.
Hello, freshly joined here.
Mine was installed 2 days ago, with the entire system. Lost WiFi in the afternoon, and now is no longer accessible, not even from the EVCS screen itself⦠I did change it from Auto to Scheduled start, cause it wasnāt starting the charge ā¦
Hello @WLZ_AX79 .
Do you still have a problems with your EVCS?
What do you mean by āno longer accessible, not even from the EVCS screen itselfā? The screen is not reacting to your clicks?
Hello, In finaly I used a wifi repeater edited in Mesh network and I have solved the problem
For what itās worth, Iām having similar problems. Iāve just updated the EVCS to version 2.03 (was on 2.01), so Iāll see if that makes a difference, though Iām guessing it wonāt.
Interestingly, when trying to update the firmware, I got the message: āAn error occurred during the update process. Please try again later! Error Message: device-update: Connection error. Error: 733ā Power cycling the EVCS got it online well enough to get the update through.
The W-104 GX communication warning occurs very regularly for me; when it happens, I canāt access the EVCS web interface. Havenāt tested using Bluetooth. It does seem to come good eventually - I probably should set up some monitoring to see when the device drops off and comes back on.
Hardware:
Wifi is an Asus ZenWifi AX mesh router. Setting up a dedicated 2.4 GHz link is on the list of things to do, along with segregating all the IoT hardware (āThe S in IoT stands for Securityā) into a separate VLAN.
The concern for me is somewhat mitigated by the fact that Iām currently charging on a schedule, rather than purely on excess solar (thank you, Ovo Energy, for the three hours of free energy between 11am and 2pm.) Iād still like to get to the bottom of it, though.
Sadly, it didnāt work for me - I just noticed this morning that itās offline. Again. The web window that I have open was displaying the W-104 warning, and when I tried to refresh it, it timed out.
Iād disabled Bluetooth through the web interface, so I couldnāt check that side of things. Iāve just re-enabled it and changed the PIN, so I can poke at it a bit more the next time it happens.
Iām on the verge of heading to a local computer store and picking up a $AU60 access point (802.11 n/b/g), just to rule out that particular possible concern. (I need to do that anyway at some point as part of the VLAN segregation, since my current wifi access points donāt do VLAN tagging.)
parfois Ƨa arrive encore chez moi mais beaucoup moins quāavant et aussi activer le Scan auto des appareils modus dans lāappareil gx
After turning Bluetooth on, it happened again. Connected to it using Bluetooth, and it came good. This morning I noticed it was once again offline; I connected to it using Bluetooth, but it didnāt come good (so much for that theory).
I have an 802.11b/g/n access point set up and ready to go, so when I get a chance, Iāll try connecting it through that (I need to drill a hole in the DC breaker box to access a loose Ethernet cable thatās no longer connected to anything - itās a whole side project) and see if that helps. If it does, itāll suggest that the issue might be with using a mesh wifi AP - possibly the EVCS is seeing multiple SSIDs with the same name and getting confused? (Need to test the idea before I call that a major possibility, though.)
The communication module is handling both wifi and bluetooth as the frequencies are close to each other.
With some (dubious) communication modules, disabling bluetooth makes the wifi comms more stable.