Hello
I am finding at times after that when I send start to the charger via a node red node that sometimes the EVCS sits in “waiting to start”
I’ve even added a delay after setting parameters of 15 seconds.
If I send a second start payload the charger will then start charging.
This does not happen often but as you can Imagine waking up to an uncharged EV is not so good.
I’ve attached some screenshots
I am using 1.30 on my EVCS
Thank you for any help.
Rhys
Sounds like a communication issue.
You can configure that node-red to have checked mechanism and if the command was not received, to send it again
Hello
Yes, it does.
Seems to be a new problem though.
I’m connected via lan too.
Another clue is it only seems to happen when I connect the cable.
So.
Car is away, charger is waiting.
Car arrived home, plugged in, fires command to reset charge setting, send stop (just in case) wait 15 seconds, send start.
Thanks
Try debugging the communication with the EVCS, ping it and see how good it is.
Make sure you are running the latest FW on the EVCS.
What is the EVCS Wi-Fi signal level?
Hello
V1.30
Wifi great at - 57
Full modulation.
But…. Ping is terrible, 30 - 100ms !
I changed channel no better.
I changed AP no better.
Evcs web access is fast though.
Ping from router to Cerbo <1ms (wired)
Ahhhhh I found the problem.
Thanks for pointing me in the right direction.
Turned Bluetooth off on the EVCS and perfect ping times!
If wifi fails I’ll need to factory reset to turn Bluetooth on?
Thanks again
Wifi and bt are shared on the same module and antenna, it’s normal to have increased response time with both active, but it shouldn’t cause issues.
If the EVCS can’t connect to a Wi-Fi, it will switch to AP mode