Skip to content
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

Replicate OpenEVSE local (LCD) controls on web UI #34

Closed
6 tasks done
jeremypoulter opened this issue May 28, 2017 · 3 comments
Closed
6 tasks done

Replicate OpenEVSE local (LCD) controls on web UI #34

jeremypoulter opened this issue May 28, 2017 · 3 comments
Assignees

Comments

@jeremypoulter
Copy link
Collaborator

jeremypoulter commented May 28, 2017

All the controls on the OpenEVSE LCD should be available on the web UI with a focus on;

  • Change charge current limit
  • Set the time limit
  • Set energy limit
  • Set charging timer
  • Setting the current time, see WiFi should be used to keep correct time #15
  • Set the service Level
    • Use location to set appropriately for the region?
@glynhudson
Copy link
Contributor

Yes, service level will always be L2 in countries that have 240V. In The USA is could be L1 or L2 depending on the outlet it's plugged into. However, I guessing most (if not all) users will be using L2 from 240V outlets since much of the benefit of using a unit like the OpeneEVSE if it's connected 110V outlet. What do you think @chris1howell

@chris1howell
Copy link
Member

chris1howell commented May 31, 2017 via email

@jeremypoulter
Copy link
Collaborator Author

All changes now implemented in #51

jeremypoulter added a commit to jeremypoulter/ESP8266_WiFi_v2.x that referenced this issue Dec 5, 2019
There there a few issues:
 - The button GPIO was configured incorrectly
 - The default random seed channel is 0, so that clashed with the the button
 - The default state was incorrect for whena button is triggered low

Fixes OpenEVSE#34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants