-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: MQTT EVSE Status Enhancements #24
Comments
Hi, this repo has been moved. I recomend posting the feature request to the new repo: https://github.com/OpenEVSE/ESP8266_WiFi_v2.x/issues Are you referring to a charging timer being set on the EV or the EVSE? I don't believe the EVSE can determine if the EV has a charging timer set (via the pilot signal). @chris1howell will be able to confirm. Here are the list of states openEVSE MQTT supports : https://github.com/OpenEVSE/ESP8266_WiFi_v2.x/blob/master/src/input.cpp#L133 |
Hi Chris,
The latest development OpenEVSE firmware has a new RAPI command to get plug state.
G0 - get EV connect state
response: $OK connectstate
connectstate: 0=not connected, 1=connected, 2=unknown
-> connectstate is unknown when EVSE pilot is -12VDC
Here is the RAPI documentation for the latest devolopment version.
https://github.com/lincomatic/open_evse/blob/development/firmware/open_evse/rapi_proc.h
Chris
On Thu, Mar 23, 2017 at 1:28 PM, Glyn Hudson <[email protected]<mailto:[email protected]>> wrote:
Hi, this repo has been moved. I recomend posting the feature request to the new repo:
https://github.com/OpenEVSE/ESP8266_WiFi_v2.x/issues
Are you referring to a charging timer being set on the EV or the EVSE? I don't believe the EVSE can determine if the EV has a charging timer set (via the pilot signal). @chris1howell<https://github.com/chris1howell> will be able to confirm.
Here are the list of states openEVSE MQTT supports : https://github.com/OpenEVSE/ESP8266_WiFi_v2.x/blob/master/src/input.cpp#L133
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#24 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABvYHzLqNOaMSXNlok3jBLP_Xb-TFkUJks5rotXlgaJpZM4Mmn7F>.
|
@chris1howell - Ok sounds good. I will have to try out the dev branch. Hopefully the MQTT code will poll and broadcast connection state to the broker. Now I just need to go unbolt the EVSE from the wall and upgrade 👍 @glynhudson - I was referring to the EVSE scheduler. Thanks all. |
Sorry is this is the wrong place to post a Feature Request, so feel free to close if this is the wrong avenue for communicating this.
I have integrated the MQTT status into my Home automation system and have rules set up that if the EVSE is not plugged into the car to alert me (State 2 or 3 indicate the EVSE is plugged in). However when you set up a charge timer, the status is always 596 while not charging. Is there a way to create an additional state to include scheduled and plugged in, vs. only scheduled?
The text was updated successfully, but these errors were encountered: