Hello Lucian,
I just discovered that there is a C027 hardware version (v2) that isn’t on sale yet. Could you answer the following questions?
I’ve spent too much time working around issues with the C026, hence these questions.
ok, BT can connect again, I wil now wait and see if BT can still connect if wifi disconnects
No, same chip
Yes
There is nothing producing heat inside the unit, not sure what heat dispation are we talking about
V1 is already certified for that
What is the curent version not doing properly offgrid?
What issues?
Hi Lucian
Ok my Charger lost connection again while it was auto charging today, I logged in with BT and got an error comunication message. screenshots attached. I also attached screenshot from the wifi controller. The wifi didn’t drop but the ip was not accesible. While I stood in front of the charger it just restored the connection and started charging, it was offline for about 5 minutes. In that time I couldn’t ping it from the network or acces the webpage and the instance dissappeared from the gerbo’s screen. You will see that the connection was up for 20 plus hours and after the charger started working again withour a power cycle it shows the wifi connection wasn’t severed. this is the first time I see this before I had to powercycle it.
ok, but no issues with BT
What about power cycle the AP when there are issues with communication?
What kind of AP are you using? there are reports regarding the IOT integration for Unifi, especialy in mesh mode
Have you checked for firmware updates for your Access Point / Wi-Fi Router ?
I had a problem with unreliable connections, and after updating the firmware in the AP, everything worked.
Yes, I read the whole thread from beginning to end. I now have a dedicated wifi accespoint for the charger at 20mhz channel width, -47dbm signal. I had an openevse charger connected to the same accespoint for 3 years no issues. Out of my previous post you will see that the charger never lost wifi connection it just stopped comunicating on the ip.
I presume the mikrotik is restaring, not the EVCS. The EVCS was testes in extreme conditions and it should not be restarting.
Yes, the cybersecurity ceritfication will be shared. But I can confirm already that we have it.
Check the modbus tcp, you can finetune the auto mode behaviour - https://www.victronenergy.com/upload/documents/EVCS-Modbus-TCP-register-list-v3.9.xlsx
We are working on a different Auto mode, controlled by the GX, that will use the data from the solar sense, the power prediction, the energy prices etc
So lots of cool things are coming 
not yet
I am using Tplink which is basically Unify and it uses the same controller. It is not in mesh mode and and I turned of any dynamic settings.
I will reboot ap next time it goes offline.
you can add a ping node to monitor the real state
Also, in VenusOS 3.80, we are swithching from ModbusTCP communciation between EVCS and GX to MQTT.
That will make the communciation way more reliable
You can already test it if you want, just enable beta on your GX and we can put your EVCS to beta as well
tell me what is your portal ID, I will enable it
c0619ab8e561
Just to report on this. It became unreachable again, I reboot the ap and the chargers wifi reconnected again but the comunication didn’t get restored. It can’t be reached via ip. I did login in via bluetooth, shows wifi connected shows ip but can’t comunicate. A reboot is only thing that fixes it.
done, I configured both devices to communicate over MQTT
There are many other things on the new fw, play with it
also related to this, you can test it as well - BETA: Connect your Electrical Vehicle to VRM
my car is not supported yet. Can the victron ev charger not see the soc of the car? Public charger report my soc?
