Still have not worked out the "current" issue, so for now, it is way off, I have a question about the temp sendors, all my ones show zero on the web page, do I have to add them?
@troy You can add this sensor here: https://store.openevse.com/collections/all-products/products/temperature-sensor
Temp 1 is an older Real Time Clock Chip that is no longer supported.
Temp 2 is MCP9808 sensor connected to the Controller. When installed it is used for enclosure temperature throttling and Emergency Cutoff.
Temp 3 is an IR sensor that is no longer supported.
Temp 4 is MCP9808 sensor connected to WiFi, It is for situational awareness and logging.
For your current issue you can update the firmware to the development version. the Settings => EVSE has Current Calibration in there. The default value is 220, you can change this to get it dialed in.
Thanks great support
Where on the board would this plugin, Can I use any other temp sensor? Can I suggest you add the extra add ons to the text of the shop page, I would have added them to the basket when I ordered the board. Shipping costs are a killer. Your great board looked like it had all the bits on it ... :)
Sorry to say after only 2 charges this board has now stopped working.
Seems to be stuck in "Starting" mode and will not detect the car.
I restarted via power off, waiting 5 min and starting the unit, I got the GFCI Error, then switched to manual mode and the error went away. However, it will not go past the starting mode. Of note the 2 LEDs, flash red with the GFCI error, then purple then off.
I then tried the DEV firmware update to see if that would fix it, no luck.
Looking for suggestions, could I have a faulty board?
I have attached my debug export.json file, do you need anything else?
Looking forward to getting this unit back in working order.
Here is my status
{"mode":"STA","wifi_client_connected":1,"eth_connected":0,"net_connected":1,"ipaddress":"192.168.xx.xx","macaddress":"x","emoncms_connected":0,"packets_sent":0,"packets_success":0,"mqtt_connected":1,"ocpp_connected":0,"rfid_failure":0,"ohm_hour":"NotConnected","free_heap":177000,"comm_sent":5846,"comm_success":5846,"rapi_connected":1,"evse_connected":1,"amp":0,"voltage":249.1000061,"power":0,"pilot":6,"max_current":6,"temp":0,"temp_max":false,"temp1":false,"temp2":false,"temp3":0,"temp4":false,"state":0,"status":"active","flags":512,"vehicle":0,"colour":0,"manual_override":1,"freeram":177000,"divertmode":1,"srssi":-37,"time":"2025-05-22T13:43:18Z","local_time":"2025-05-22T23:13:18+0930","offset":"+0930","uptime":5443,"session_elapsed":0,"session_energy":0,"total_energy":102.0949909,"total_day":0,"total_week":33.51429103,"total_month":102.0687103,"total_year":102.0687103,"total_switches":38,"elapsed":0,"wattsec":0,"watthour":102094.9909,"gfcicount":0,"nogndcount":2,"stuckcount":0,"solar":0,"grid_ie":0,"charge_rate":0,"divert_update":5443,"divert_active":false,"shaper":0,"shaper_live_pwr":0,"shaper_cur":0,"shaper_updated":false,"service_level":2,"limit":false,"ota_update":0,"config_version":1,"claims_version":3,"override_version":3,"schedule_version":2,"schedule_plan_version":2,"limit_version":1,"vehicle_state_update":5443,"tesla_vehicle_count":false,"tesla_vehicle_id":false,"tesla_vehicle_name":false}
@Troy
Are you sure your error is GFCI and not No Ground which is expected when the station powers off? Your export has GFCI count 0.
It does also look like you have MQTT and Solar Divet on plus a couple timers. Purple indicates the station is sleeping. If you have set Sleep Mode to Disabled, then the station can not detect a vehicle until the timer activated and goes from Disabled to Enabled.
I have removed all timers and no solar divert, the MQTT is just to set the voltage value. I also get the No Ground fault but have checked all parts that need ground and all are valid.
When you change from start to manual mode faults are cleared.
As noted it has worked twice but now will not with no changes to the hardware setup.
I just restarted the unit and get the following, no count on the GFCI error but it is displayed.
Fault will go away, but will no longer detect car or change from starting
Sorry for all the posts - an update.
After I disable the GFCI and Ground test the unit is working as it should.
Can you suggest why this may be the reason?
Do you have some suggestions on what I can do to test that the board is working?
Any reason why it would work okay first and then start showing this fault?
@Troy
Ground Test can be re-enabled. There is a known issue where false positive is detected as the unit loses power when unplugged. It does not affect any functionality.
GFCI Error and GFCI self Test Error are different. GFCI error is an actual ground fault detected. Self test error is the controller tickles the coil before charging to see if it trips on purpose.
Disabling GFCI Test does not disable GFCI it just does not self test GFCI every time before each charge. It is possible the GFCI or test coil came unplugged. We would recommend checking both are securely connected.
Both connections are securely connected, I have also changed the stock test wire from one loop to 5 as recommended by your build instructions.
Happy that it is still safe and I can confirm the car charged overnight :)
I have a question about the "Current Scale" and "current offset". I know how to change it and can see the effect however to get the readings close to what my car is showing my current scale is set to 83. Do you have a link to explain the calculations around this or do I need to jump into the code.
openev. freshdesk. com@redsails. net
I am considering buying the new juicebox retrofit board to get myself started in the OpenEVSE world. I have exactly zero experience with OpenEVSE, and some experience with DIY electronics (ESP-home).
Could someone help me figure out, before I jump in:
* Is that board all-inclusive, or is any additional hardware required?
* Is it compatible with a screen, or at least a button?
* Is it pre-flashed, or do I need to get a programmer too? Which one?
Thanks in advance.