Agile slots now being skipped during a contiguous block

johalareewi

I had a block of slots selected from 12:30 to 15:00. The charge command fired up OK but part way through the block, WW started to skip slots and stopped the charge. I think this might be related to the lrecent change made for <0.00p testing?
neighboring-volume

admin

johalareewi Yeah that's related to the re-evaluation logic.

But this falls within your 13:30-16:00 Agile charge window, for which the SocLess Than is set to 60% hence those slots were skipped, as per design?

Ultimately this will work better for Agile users. Contiguous blocks will be re-evaluated every half hour and depending on current SOC, tariff and Agile Window settings, instruction will be determined.

As per discussion here: https://community.wonderwatt.com/d/946-agile-octopus-price-below-advanced-setting-improvement/8

johalareewi

admin But this falls within your 13:30-16:00 Agile charge window, for which the SocLess Than is set to 60% hence those slots were skipped, as per design?

I guessed that was what happened. Just wasn't expecting it.

Will the slot keep charging if the target SOC hasn't been reached or is it just the start SOC that is retested?

Going forward, this re-evaluation is what I expected Agile slots to do in the first place so I like it.

Yes I have seen the other discussion but the revaluation change there just mentioned the price <0.00p and I didn't spot that it also included everything else.

admin

johalareewi Will the slot keep charging if the target SOC hasn't been reached or is it just the start SOC that is retested?

Just re-tested at the start, yes.

admin

johalareewi Going forward, this re-evaluation is what I expected Agile slots to do in the first place so I like it.

I think it will also fix the issue where you add a half hour slot to the end of an already started charge block and it would not get actioned.

johalareewi

admin
It should do and also if i remove a slot from the end.
Crossing an Agile Window boundary should change too.

johalareewi

This is what happened this afternoon with a contiguous charging block.

GE commands

I can see that at each test, the Charge start time was advanced 30 minutes and a command sent to the inverter. This isn't really required and maybe this command can be skipped to reduce the comms traffic and the inverter register writes?

admin

johalareewi Based on what logic? You mean simply if the charge instruction (SOC target) is still the same as current?

johalareewi

Also, when it got to 15:00, the activity log said

but the command to stop the AC charge was never sent and the inverter kept charging

neighboring-volume

Update:
At 15:30, WW did clear the AC charge command from the inverter. So WW skipped the 3pm skip.

admin

johalareewi This looks like that's been an issue before these changes? We'll get a fix out.

johalareewi

admin This looks like that's been an issue before these changes? We'll get a fix out.

Did it again today at 15:30pm
WW Activity log says skip slot but GE inverter still has AC Charge from 15:00 to 16:00.
I guess this fix wasn't in the batch you did for the beta testing?

johalareewi

admin Based on what logic?

The original AC charge command to the inverter was 13:00-15:30
At the next 30 minute re-evaluation, the SOC logic determines that charging is still required so it changes the AC start time on the inverter (now 13:30 - 15:30).
But there is no need to change the AC charge start time it is still set to 13:00-15:30 at the inverter and that covers 13:30-15:30.
I was thinking it could just be left alone and save inverter writes and some comms to the inverter.

admin

johalareewi Fix for that being deployed at the moment, should be live in the next 10 mins or so. Instruction won't be sent if target SOC hasn't changed. If contiguous, next check will be pushed 30 mins on.

Kevin

Overnight, none of my export slots ran.

And now the exportt slots are locked. Telling me they have been selected for both export and charging,

admin

Kevin We'll create a quick 'Reset export slots' button for that, so you can 'fix' this if this happens again, as well as we'll delete export slots, prior to repopulation of agile charge slots.

Kevin

Balderdash!
This should gave been in the other thread!

admin

johalareewi The AC Charge Enable flag should be reset at the end of the contiguous block. Let us know if that's not the case.

johalareewi

admin
Not sure if the fix was for this...
Had a block of 3 slots last night 02:30 to 04:00.
It all fired off fine.
At the 30 minute re-evaluations, commands were sent to the inverter to update the start time.
At 03:00 and 03:30

admin

johalareewi Should be resolved now.

johalareewi

admin

That bit works but when it is time to stop charging, WW doesn't stop the inverter charging.

The SKIP at 14:30 left the inverter charging.

johalareewi

The next SKIP re-evaluations didn't stop the charge either.
But the charge did get stopped at the end of the contiguous block at 16:00.