OpenEVSE with Wifi Build V2 and Testing

sean_fosberry · 2017-09-18T19:57:13.147Z

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.

glyn.hudson · 2017-09-19T10:16:26.781Z

Hi @sean_fosberry

Thanks a lot for testing.

sean_fosberry:

None of the information on Firmware of the OpenEVSE or the WiFi module is reported :

I think this will work after the OpenEVSE controller is rebooted.

sean_fosberry:

For the ‘services’ page, its not clear what is connected. I thought the update had wiped the emoncms connection but when I click the ‘enable’ tick box I can see its is connected and posting. It would be better to have this in view to begin with.

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 .

sean_fosberry:

Timer : Previously I’d set a timer for 5 mins for a test. This isn’t visible in the web UI, only on the unit. There

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.

sean_fosberry:

Safety : Is this section working? I have recorded several ground faults (deliberately) but the count reads zero?

Should be working, we will investigate. I’ve opened a git issue: Check safety error reporting · Issue #93 · OpenEVSE/ESP8266_WiFi_v2.x · GitHub

sean_fosberry:

In summary, it works, much better! It’s now very snappy from my phone or desktop PC running Chrome. It still doesn’t load in Edge though, not that Edge immediately matters to me!

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

sean_fosberry:

Did you have any thoughts on my comments on providing a summary of what the unit is currently tasked with doing? Such as ‘Charging for 1 hour’ or ‘Charging to 1 kWh limit’?

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.

jeremypoulter · 2017-09-19T12:10:17.870Z

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?

sean_fosberry · 2017-09-19T12:24:07.544Z

By reboot, do you just mean turn the open EVSE off and on again? Or on the board?

sean_fosberry · 2017-09-19T12:25:19.386Z

“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,

jeremypoulter · 2017-09-19T12:32:41.394Z

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.

sean_fosberry · 2017-09-19T16:12:46.152Z

So from a fresh power up :

image846×902 41.7 KB

image805×529 25.5 KB

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}

jeremypoulter · 2017-09-19T19:04:55.962Z

sean_fosberry:

“gfcicount”:fe

That is the problem, I think I need some hex to decimal conversions on the error counters.

sean_fosberry · 2017-09-19T19:22:55.302Z

I can see the firmware info in there too. Can you see why its not being displayed? Do you see it in your build?

sean_fosberry · 2017-09-19T20:46:22.484Z

Also is there any notes / documentation on how I configure the MQTT for the solar divert?

jeremypoulter · 2017-09-19T22:05:24.175Z

That one error invalidates the whole file, so that will cause a bunch of values to not be displayed.

jeremypoulter · 2017-09-19T22:06:54.702Z

There should be some blue 'i’s that pop up some help

roy13 · 2017-09-21T00:30:26.802Z

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.

glyn.hudson · 2017-09-21T10:43:49.395Z

A post was split to a new topic: OLEV EVSE Reporting

glyn.hudson · 2017-09-22T13:13:00.499Z

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?

sean_fosberry:

Also is there any notes / documentation on how I configure the MQTT for the solar divert?

See the built-in docs, click the little info button:

02870×847 141 KB

sean_fosberry · 2017-09-22T20:17:26.214Z

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 …?

jeremypoulter · 2017-09-23T12:58:01.780Z

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.

roy13 · 2017-09-27T10:11:24.224Z

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?

roy13 · 2017-09-28T21:06:30.930Z

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

glyn.hudson · 2017-09-28T23:26:07.242Z

Yes, that issue is due to compiling with Arduino. You can either use Platformio (highly recommended) or manually enter the built tag into Arduino.