Retire Proof of Concept and develop LCD display graphics.

[chris1howell]

This is an example from SquareLine Studio GUI tool. I think it is a good reference and discussion topic.

[chris1howell]

Here are the screens I think we need.

-Boot Logo
-WiFi Portal SSID and Password QR code
-WiFi Connected IP address
-Home Screen
-Connected Screen
-Auth Screen Scan RFID card or QR (station ID) if RFID and/or OCPP enabled
-Waiting for Timer
-Charging
-Connected Charging ended Session Stats
-Error Screen

[TommySharpNZ]

I’m assuming there’d also need to be a touchscreen to accomodate these mockups? Or at least some physical buttons…

[zymurgic]

There's some interesting concepts here. One of which is tariff / pricing information, which although more useful in a multi-user / commercial deployment, is also very useful in a single user/residential environment where the electricity supply tariff is variable, it could be useful to have a price per kWh displayed.
If you're doing that sort of thing, and local cost calculation, it would be good to align with the concepts in OCPP 2.1, or at least OCPP 2.0.1 (which allows display messages to be triggered from a CSMS), even if the display updates are fed over MQTT rather than OCPP.
State of Charge... currently that depends on individual vehicle integration, since the standard J.1172 PWM pilot signal doesn't communicate that information, and OpenEVSE doesn't (yet?) do ISO15118 comms with the vehicle due to lack of powerline networking hardware.