OK, I’ll think I’ll try this as having upgraded from 4.1.6 to 4.1.7 it seems a bit flakey.
I have the wired and wireless board - later version - but there seems to be two versions available.
Which do I need?
As written in the first post, files ending with gui-v2 for new UI.
Ok, it was the fact that one mentions WiFi and the other doesn’t that confused me - presumably both do!
However, I assume the Lifetime kWhrs" displayed on the OEVSE two line display will then likely be wrong (for those who mix 1ph and 3ph charging). Presumably this can be fixed, longer term? However this minor glitch should not stop the overall improvements being made.
Not sure but I think the displayed kWh comes from a Rapi command from the wifi module. If it is the case then the displayed value should be good.
I noticed some more builds, the most recent 10hrs ago. Are there improvements or fixes?
@doggy Not on fw side, it’s just because I’ve pushed UI commits and it generate new builds with it.
But I’m actually working on another branch of the fw and it’s not on those builds
edit: here is my actual build if you want to play with
It has new energyMeter to test + latest network stack from jeremy.
With this build there’s no difference having threephase or normal openEvse fw. Just use the is_threephase switch from wifi fw.
It will import the old evse counter the first time it creates the energyMeter data file.
If you want to clear it without import you can send an HTTP DELETE to /emeter endpoint with { “hard”: 1, “import”: 0 } ( I have not made the UI part yet, so you have to query manually using Curl, or Boomerang chrome app ( more user friendly ) )
it adds in /status new properties:
- session_elapsed (sec)
- session_energy (wh)
- total_energy ( kwh )
- total_day (kwh )
- total_week (kwh )
- total_month (kwh)
- total_year (kwh)
- total_switches ( number of time the relay has been switched )
total_switches and total_energy can only be reset by using “hard”: 1 , adding “import”: 1 force the old evse counter import
Thanks. I think I’ll stick with what is working now, for a while because I’ll be using it a lot for my cars and daughter’s EV and travelling through areas without much EV charging. So having something working well will be essential over the next few weeks.
I updated to the (then) latest build sometime yesterday and immediately afterwards the time displayed was out and still is now after upgrading to the latest (at the time of writing).
I’m on the Europe/London TZ and hence confluent with UTC right now but the UI thinks it’s an hour ahead for some bizarre reason.
I wasn’t charging a car last night but my wife’s needs a charge tonight as she’s working tomorrow hence I’ve got to stay up and possibly initiate a manual charge just in case.
Why has this been broken?
have you checked your time zone settings has not been reset ?
There was a bug with config reset after firmware flash from few weeks. Looks like it is solved with today builds
Has something changed recently in the beta that altered published mqtt feeds?
For example the wh feed which is used in the total energy delivered accumulator hasn’t come through for 2 1/2 days.
Definitely updated to the latest firmware once or twice since then.
@greentangerine watthour and wattsec has been deprecated for a while, it has been removed.in dev builds.
Please use new energyMeter data ::
- session_elapsed ( sec )
- session_energy ( wh )
- total_energy (kwh)
- total_day (kwh)
- total_week (kwh)
- total_month (kwh)
- total_year (kwh)
yeah it’s normal for the time problem, I’ve pushed an update on the UI before the time/schedule fix from jeremy has been merged on master, because I’m leaving for a week.
Should happend soon.
I’ll need to check when I’m back for the weekly/monthly. Saw womething strange happening too.
Have to figure out first which one is wrong.
Given my wife’s Zoe has taken about the same the last two nights and assuming week begins Monday then the daily and week values are correct.
Month is someway off what it should be given we usually charge every night and it is generally between 20kWh and 28kWh and so therefore is year (but I guess depends on when it started).
If you have tested different buids the last days, I’ve perhaps already fixed it but your counter has not reseted yet.
You can manually reset energymeter if you want to try again:
https://openevse.stoplight.io/docs/openevse-wifi-v4/718f0f0931c65-reset-energy-meter
Interesting, the time shown in the web browser in the UI is correct but the time shown on the display of my OEVSE box is one hour earlier!
Jeremy fixed some timezone issue,.it was merged yesterday I think. I need to update the UI to the new /time endpoint when I’m back
Okay. Thanks.