Is SOC less than 100% test actually tested?

johalareewi

I have an Agile window which has SOC% less than test set to 100%.
Does this mean that the SOC is never tested and the charge always goes ahead, or is the SOC tested and if it is 100% the charge is skipped?
There isn't an option to activate or deactivate the SOC test so was wondering if 100% did that instead.

admin

johalareewi Yeah, if the battery is at 100%, or 'SOC less than' value is less or equal to actual SOC it is skipped.

Bouff34

Not sure I'm understanding how or if mine is working correctly at the moment??

I have a 1300x1500 agile slot which should only trigger if SOC below 65% and then should only charge to target of 80%.

Today's activity log shows SOC was already at 92% but nevertheless a charge instruction was still sent to charge up to 100%???

Watt- ID 'optimal-body' !!

admin

Bouff34 Having a look now.

admin

Bouff34 Your condensed charge slot was set to this:

So from 13:30 - 16:00.

However, this condensed slot does not fit completely in any of your Agile charge windows.

You have 3 charge windows:
15:00-16:00
13:00-15:00
00:00-06:00

As a result of this we cannot match this condensed charge slot to an Agile charge window, and therefore the agile charge window settings cannot be applied, so are defaulted.

Bouff34

admin

So are you saying I can't have two adjacent slots as technically they overlap by a minute? Is that what is causing the issue?? Not sure I'm understanding...? Or more to the point that if they run together WW treats them as one continuous slot which causes an issue because it runs across the two charging windows??

admin

Bouff34 I see, yeah you have two agile charge windows that are adjacent.

We need to think this one through a bit! Perhaps we should not condense the charging slots if it spans multiple charge windows, actually.

Bouff34

admin
what I’m trying to achieve is that I want a full battery by 1600 but don’t want to charge unnecessary if there is solar input! I thought that a stepped approach would do this with an input on the first slot to get up to say 80%… I then have a second slot to finish things off to get to 100%… kind of a work in process but obviously isn’t working as I was expecting! I think I’m right in saying the agile WW process doesn’t currently factor in solar for me??

As a second point I have a charging slot overnight but I often choose to override it. What I would love WW to be able to do is to look at the agile pricing and determine whether it is worth me paying to charge. If it costs me say 12p overnight but the rates are only 14p early morning then I probably lose the 2p in efficiency losses through charging and then discharging. Is it possible to have a feature that says the average cost to charge must be 80% (this is a figure picked out of the air but one I have seen suggested as realistic) less than the price that will prevail for the following four hours ( or whatever I choose to set).

Hopefully this makes sense??