Simple HTML user interface to control OpenEVSE

[Bobby Chung]

Hi Everyone,

Recently, I completed coding a simple HTML only UI so that you can use any browser to control the EVSE using RAPI by typing <IP address>/home .  Instructions and source are at https://github.com/Energybrain/openevse-wifi-ui.  Here are some screen captures.

[Danny ter Haar]

Very nice ! thank you!

[lincomatic]

Cool! Thanks for sharing.

 

From: open...@googlegroups.com [mailto:open...@googlegroups.com] On Behalf Of Bobby Chung
Sent: Wednesday, July 6, 2016 8:08 AM
To: OpenEVSE
Subject: Simple HTML user interface to control OpenEVSE

 

Hi Everyone,

 

Recently, I completed coding a simple HTML only UI so that you can use any browser to control the EVSE using RAPI by typing <IP address>/home .  Instructions and source are at https://github.com/chungmiester/openevse-wifi-ui.  Here are some screen captures.

 

 

 

 

--
You received this message because you are subscribed to the Google Groups "OpenEVSE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openevse+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[chris1howell .]

Great... I have made a lot of progress on the Development branch of wifi firmware. I will integrate your improvements.

On Jul 6, 2016 11:07 PM, "Bobby Chung" <bobby...@gmail.com> wrote:

Hi Everyone,

Recently, I completed coding a simple HTML only UI so that you can use any browser to control the EVSE using RAPI by typing <IP address>/home .  Instructions and source are at https://github.com/chungmiester/openevse-wifi-ui.  Here are some screen captures.

[Bobby Chung]

Hi  Everyone,

I made a couple of improvements/bug fixes - One is UI related and the other is related to making the Limits work when the Delay Timer is Set.  The UI related one is fixing the Time Limit drop down box to be correct and a more usable selection of time limits (30 min increments).  Changes are marked with my initials //bhc.  The Limits working when Delay Timer is set problem happens because as soon as a limit is reached the OpenEVSE sleeps but because it's within the delay timer, an override happens so it enabled again.  So basically I added another condition that won't let it enable if the LimitSleepIsSet() is true.  I also had to add SetLimitSleep(0) where appropriate to allow the limit to be reset for cases when someone doesn't unplug the charger as in for solar and grid charging. As a consequence to this use case, the kWH recording would not work properly so I changed that as well to save to EEPROM ONLY when the chargingOff function is called and clear the current session ONLY when chargingOn function is called. All my changes are marked with //bhc.

[Bobby Chung]

Hi Everyone,

I'm including screen captures of my latest improvements.  I've basically added two features which makes using the limits and timer more user friendly.  I have brought the volatile flags out via RAPI so that it can be incorporated into the UI.  This will tell the user if the a session has ended because a limit has been reached by reporting the state set by SetLimitSleep.  Also, I have added a volatile flag that always reports the state of the connector at the beginning of the update loop.  I figure this reporting is useful in that someone can use it to write a script to send a reminder email that the EVSE is not plugged into the car when it should be for overnight charging.  The first screen capture is the UI while the car is charging and there is a time limit of 15 minutes and it is triggered by the delay timer start time.

[Bobby Chung]

This next screen capture shows the UI when the charging time limit has been reached and the EVSE is in the sleep state.  Note the indicator of it is plugged in.

On Monday, July 25, 2016 at 10:55:09 AM UTC-4, Bobby Chung wrote:

Hi Everyone,

I'm including screen captures of my latest improvements.  I've basically added two features which makes using the limits and timer more user friendly.  I have brought the volatile flags out via RAPI so that it can be incorporated into the UI.  This will tell the user if the a session has ended because a limit has been reached by reporting the state set by SetLimitSleep.  Also, I have added a volatile flag that always reports the state of the connector at the beginning of the update loop.  I figure this reporting is useful in that someone can use it to write a script to send a reminder email that the EVSE is not plugged into the car when it should be for overnight charging.  The first screen capture is the UI while the car is charging and there is a time limit of 15 minutes.

[Bobby Chung]

This next screen capture shows what happens when I unplug the connector.  Because it is still within the delay timer zone, it is ready for charging once the plug is unplugged.  Also note the energy usage for the session is not cleared and added and stored to the lifetime.  It won't clear until chargingOn is called which is when charging starts.

[Bobby Chung]

This next screen capture shows what happen if I move the delay timer window so that it is outside the window and connector unplugged.

[Bobby Chung]

And finally, the last screen capture shows what happens when I plug in the connector while it is waiting for the start time (sleeping).

[lincomatic]

Awesome work, Bobby!

[Bobby Chung]

Thanks lincomatic!

Hi Everyone,

I just made a major update (I'm calling v1.0) which makes the wireless configuration much more user friendly.   I added an additional server as a backup.  The host, directory and an external link are user customizable.  I basically made the EVSE able to run in a "headless" mode i.e. without the display and button to change the settings, setup and view status.  All you need is a browser.  It can run with or without a network.  In other words, configuration and control can be done in AP mode.  Here are a couple screen captures.

Bobby

[chris1howell .]

Hi Bobby,

Great work... There is a TON of development going on right now with the Wifi software. I have been working with Trystan Lea and Glyn Hudson from the emoncms development team.They used the OpenEVSE firmware for their EmonESP and made a ton of improvements such as MQTT and SPIFSS file system. I have made a ton of visual improvements to the UI as well as added a lot of the EmonESP code to the development branch. At some point we should start moving your changes over to the development branch.

Here is a screen shot of the Development branch.

To unsubscribe from this group and stop receiving emails from it, send an email to openevse+unsubscribe@googlegroups.com.

[Bobby]

Hi Chris,

Love it!  I've been seeing your progress and you ain't kidding about the amount of work.  I'm a beginner at this html stuff and initially I just needed something quick and dirty for my clipper creek hybrid.  The more I got into, the more I was hooked and just added more and more features.  It's so fun!  It makes me really appreciate the work you and the team have contributed so far.  Go Open Source!!  Thanks for everything.

[lincomatic]

Wow, that’s some serious progress!

Is this all running on the ESP?

I notice you have a firmware upgrade feature. How’s that being done?

Linky to the repo?

[chris1howell .]

Yep, all on the ESP, the interface is HTML, JS and CSS. Upload to EmonCMS is vis HTTP or HTTPS if you save the SHA Fingerprint key. MQTT was just added. OpenEVSE configs are read via RAPI and then sent via JSON.

Firmware upgrade is for WiFi firmware is simple Over the Air OTA, pick a new bin file and go... (there are libraries for ISP and serial loading to an AVR).

Repo is here... https://github.com/chris1howell/OpenEVSE_RAPI_WiFi_ESP8266/tree/Devolopment

To unsubscribe from this group and stop receiving emails from it, send an email to openevse+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "OpenEVSE" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openevse+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "OpenEVSE" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openevse+unsubscribe@googlegroups.com.

[Bobby]

Yes, the ESP is an amazing little chip.  It's a very powerful and low cost.  Not sure what the emoncms developers are doing with the ESP, but I was able to successfully use the ESP to basically replace the emonTx and emonPi as a current sensor for both my usage and solar generation and voltage measurements.  The ESP is able to sample about 150 times in 1 cycle of 60 Hz or 16.667 ms. This is effectively about 50 samples for each waveform, more than enough to get accurate enough measurements.

Enter code here...

On Tuesday, August 16, 2016 at 5:25:22 PM UTC-4, Chris wrote:Yep, all on the ESP, the interface is HTML, JS and CSS. Upload to EmonCMS is vis HTTP or HTTPS if you save the SHA Fingerprint key. MQTT was just added. OpenEVSE configs are read via RAPI and then sent via JSON.

[lincomatic]

Bobby,

Do you have your voltage/current project posted somewhere?

Sent from my iCrap

On Aug 16, 2016, at 6:07 PM, Bobby <bobby...@gmail.com> wrote:

Yes, the ESP is an amazing little chip.  It's a very powerful and low cost.  Not sure what the emoncms developers are doing with the ESP, but I was able to successfully use the ESP to basically replace the emonTx and emonPi as a current sensor for both my usage and solar generation and voltage measurements.  The ESP is able to sample about 150 times in 1 cycle of 60 Hz or 16.667 ms. This is effectively about 50 samples for each waveform, more than enough to set an accurate enough measurements.

[Bobby]

Not yet.  I will shortly after some more testing and documentation.  Bobby

[Bobby]

Released v1.1 of my wifi firmware - OpenEVSE-WiFi-esp8266-ui.ino.  Added a "not plugged in and charging notifications via Emoncms" feature.   This feature will add two inputs OpenEVSE_P_NOTIFY and OpenEVSE_C_NOTIFY that will increment from 1 to 9.  1 is the initial notification and 2-9 are 8 reminders.  For example, one can use a home automation software or some scripting to link to an email server to send email notifiations or trigger any device when the OpenEVSE is not plugged into a car and/or charging by the set time(s).  Notifications will stop when it is plugged in or charging or both depending on user setting and will reset at the end of a 24-hour period.  Also cleaned up code by reorganizing things a bit for better readabilty and troubleshooting.

[Bobby]

@lincomatic,

Just published it at https://github.com/Energybrain/ESP8266-WiFi-Home-Energy-Monitoring-with-Solar

Bobby

On Wednesday, August 17, 2016 at 2:00:29 PM UTC-4, lincomatic wrote:

[Jake Kooser]

What if you want to use this but you're dumb?  I cannot seem to find "development version 4.3.2 from lincomatic/open_evse " at https://github.com/lincomatic/open_evse even under the "development" branch.

Jake

On Fri, Sep 23, 2016 at 2:28 PM, Bobby <bobby...@gmail.com> wrote:

@lincomatic,

Just published it at https://github.com/chungmiester/ESP8266-WiFi-Home-Energy-Monitoring-with-Solar

To unsubscribe from this group and stop receiving emails from it, send an email to openevse+unsubscribe@googlegroups.com.

[Bobby]

Try this.  https://github.com/lincomatic/open_evse/tree/a4ec64b708b1461405699eb7a00aea509b77c08e  I've also updated some files and the instructions so please get the latest.  Thanks.