OpenEVSE
OpenEVSE | |
---|---|
Name | OpenEVSE car charger |
Zone | Infrastructure
|
Owner | i3Detroit |
Make Model | OpenEVSE v4 and nodemcu |
Part Number | n/a |
Date Acquired | 2015-01 |
Storage Location | By the bay door |
Authorization Required | No |
Status | Running |
Value | $350 |
IP Address | 10.13.107.80 |
MAC Address | 2C:3A:E8:35:D9:7C |
Hostname | ESP_35D97C |
Documentation | https://openev.freshdesk.com/support/home
https://github.com/OpenEVSE/ESP8266_WiFi_v2.x#openevse-status-via-mqtt |
Other References | http://files.openevse.com/OpenEVSE_Plus_v4.pdf
https://dozuki-guide-pdfs.s3.amazonaws.com/pdf/openevse/guide_14_en.pdf https://openevse.dozuki.com/Guide/Testing+Basic+and+Advanced/12 https://openevse.dozuki.com/Guide/Serial+Communications+with+OpenEVSE/13 |
Intro
DIY car charger for the space. Built from a kit, works great.
Rules
Instructions
If there is garbage on the screen, reboot using the fuse box above the device
Maintenance Info
wifi module is running https://github.com/OpenEVSE/ESP8266_WiFi_v2.x/commit/53443e2075fa1c7b32db4b261981f7f82df47cf2 The value on line 133 of src.ino is chagned from 30000 to 120000 to lower the frequency of mqtt status updates
NB It needed to be compiled with this version of the ESPAsyncTCP library: https://github.com/me-no-dev/ESPAsyncTCP/commit/9b0cc37cd7bdf4b7d17a363141d2e988aa46652c
FAQ
MQTT Data Reporting
- amp: reports Amps * 100
- wh: reports Watt-seconds
- state:
- 1:"Not Connected"
- 2:"EV Connected"
- 3:"Charging"
- 4:"Vent Required"
- 5:"Diode Check Failed"
- 6:"GFCI Fault"
- 7:"No Earth Ground"
- 8:"Stuck Relay"
- 9:"GFCI Self Test Failed"
- 10:"Over Temperature"
- 254:"Sleeping"
- 255:"Disabled"
ToDo
Maybe replace the i2c cable with something better. There are parts to build another one that has not been completed.