Also I’ve noticed that the webUI is now remember settings such as ‘Energy Limit’. It also correctly reports the values in a browser on a different device. 
Thanks a lot for testing.
I think this will work after the OpenEVSE controller is rebooted.
That’s interesting, maybe the config got messed-up / incomplete during the update. Maybe @jeremypoulter could comment on this. If Emoncms is enabled the checkbox should be selected .
Timer limit should be visible on the UI. It’s only possible to set a time limit when an EV is charging. This is a limitation of the OpenEVSE controller. The timer and energy limit are only valid for the current charging session, both will be cleared when the next charging session begins.
Should be working, we will investigate. I’ve opened a git issue: Check safety error reporting · Issue #93 · OpenEVSE/ESP8266_WiFi_v2.x · GitHub
Yes, @jeremypoulter has really done a good job optimising in the latest update, all the laggy issues seem to be thing of the past. Edge doesn’t matter to me either but it should work, it’s important to support Edge, even if it is a pain! I’ve opened a git issue Investigate Edge compatibility · Issue #92 · OpenEVSE/ESP8266_WiFi_v2.x · GitHub
The first UI box should show all the current session charging options as well as icons being displayed on the LCD to indicate charge timer / energy limit.
Almost always when you get missing values it is because the /config and/or /status endpoint are returning invalid JSON, which in turn is almost always because the serial comms between the WiFi module and OpenEVSE have got out of sync. There is still some work to do to make the comms more robust.
If a reboot of the WiFi module does not fix the issue can you post the content of http://openevse.local/config and http://openevse.local/status?
By reboot, do you just mean turn the open EVSE off and on again? Or on the board?
“The first UI box should show all the current session charging options as well as icons being displayed on the LCD to indicate charge timer / energy limit.”
Can you post a screenshot of what you mean?
Thanks,
By reboot, do you just mean turn the open EVSE off and on again? Or on the board?
Yeah, just turning the OpenEVSE on and off will do it, or there is a restart button in the WiFi UI, on the System tab.
So from a fresh power up :
http://openevse.local/config :
{“firmware”:“3.11.3”,“protocol”:“1.0.3”,“espflash”:4194304,“version”:“2.3.0”,“diodet”:0,“gfcit”:0,“groundt”:0,“relayt”:0,“ventt”:0,“tempt”:0,“service”:2,“scale”:220,“offset”:0,“gfcicount”:fe,“nogndcount”:2,“stuckcount”:0,“ssid”:“EE-79q7nc”,“pass”:“DUMMY_PASSWORD”,“emoncms_enabled”:true,“emoncms_server”:“emoncms.org”,“emoncms_node”:“30”,“emoncms_apikey”:“DUMMY_PASSWORD”,“emoncms_fingerprint”:"",“mqtt_enabled”:true,“mqtt_server”:“emonpi”,“mqtt_topic”:"",“mqtt_user”:"",“mqtt_pass”:"",“mqtt_solar”:"",“mqtt_grid_ie”:"",“www_username”:"",“www_password”:"",“ohm_enabled”:false}
http://openevse.local/status :
{“mode”:“STA”,“srssi”:-77,“ipaddress”:“192.168.1.252”,“emoncms_connected”:1,“packets_sent”:8,“packets_success”:8,“mqtt_connected”:0,“ohm_hour”:“NotConnected”,“free_heap”:20592,“comm_sent”:139,“comm_success”:135,“amp”:0,“pilot”:10,“temp1”:255,“temp2”:0,“temp3”:230,“state”:1,“elapsed”:0,“wattsec”:0,“watthour”:50866,“divertmode”:1}
That is the problem, I think I need some hex to decimal conversions on the error counters.
I can see the firmware info in there too. Can you see why its not being displayed? Do you see it in your build?
Also is there any notes / documentation on how I configure the MQTT for the solar divert?
That one error invalidates the whole file, so that will cause a bunch of values to not be displayed.
There should be some blue 'i’s that pop up some help
Yes I changed the line in open_evse.h
#define VOLTS_FOR_L1 120 (to 240)
This gives 1amp increments. Easier than trying to find the increments setting as I don’t have 120v. Sorry for the late reply.
1 Like
Hi @sean_fosberry, @jeremypoulter has just pushed an update to fix the issue with the version and stuck relay count not being displayed. Could you test the latest update and check it’s working for you. Here is the firmware to upload:
firmware.bin (648.1 KB)
Could you confirm this has fixed the issues for you?
See the built-in docs, click the little info button:
A busy evening… Have my leaf battery posting to emoncms now but thats for a different thread! I’ve just applied the update.
Here are the results :
Looks good but not sure why I have 254 GFCI errors though …?
That is what the OpenEVSE was reporting in the JSON you posted earlier, so I don’t think this is a WiFi module issue. You can check using the GF RAPI command: http://OpenEVSE.local/r?rapi=$GF. I don’t see a way to reset the fault counts so may need to factory reset the OpenEVSE to reset the count.
Oh no looks like I’m out of luck again, finally got a chance to build another WiFi chip and load with Arduino thanks again for keeping Arduino support. But I get build tag error on the evse display when scanning for a network which I assume is because I’m running openevse 4.8 something?
Looks more likely to do with compiling with Arduino as I’ve noticed even when disconnected from openevse WiFi version just says build_tag not 2.3.0
Yes, that issue is due to compiling with Arduino. You can either use Platformio (highly recommended) or manually enter the built tag into Arduino.