Strange. My pre-selected slots have not pre-selected today. The same happened on Monday, but it all worked fine yesterday. Any ideas what is going on? My Watt ID is "coordinated-success" if this is needed to investigate.

@"palaceben"#p1689 Odd - looking at this now, there are slots selected? Or did you select those manually now?

We did make a change in release 400, related to agile slots. Basically, when the auto pre-selection runs, it checks whether any slots are already selected in the future for the remainder of today or tomorrow. If that is the case, we do not prepopulate, because this means you have already pre-selected other slots. Perhaps this logic will need to change and check if these other slots are selected within the Agile Charge window and if none are, then add them. Can you confirm this was the case? Workaround for now would be to go into your Agile Charge window settings and Save without making any changes.

@"admin"#p1692 In my case I had a slot preselected in my 21.30 to midnight window, but none in my midnight to 7am window. In the past it would happily handle this and populate the midnight to 7am window … but not any more. Terrible-guidance here. … but the Copy function from the Watt ID does not work!

@"kerregan"#p1693 > In my case I had a slot preselected in my 21.30 to midnight window, but none in my midnight to 7am window. In the past it would happily handle this and populate the midnight to 7am window … but not any more. Yep - all fixed now, from release v0.3.404 onwards. Yeah - copy of WattID doesn't currently work on mobile/iOS.

@"admin"#p1692 My overnight window is 19:30-08:30, so it is entirely possible I'd made some changes to the slots before midnight before the automation tried to kick in to do my pre-selections. Do I need to split the windows do you think? 19:30-23:00 and 23:00 to 08:30 (as I clearly couldn't make any changes to that second window before automation tried ☺️)

@"palaceben"#p1703 The windows should be fine and will get populated for the today/next day at around 16:15, so your 19:30-08:30 should be pre populated then, provided you have not already selected a slot within that window, sat at 20:00, before we run the schedule population at 16:15, in which case we don't touch it, and assume you are manually picking slots, as you've already done. Does that make sense?

Just been to check and I don't have any pre selected slots this evening either at 16:40 open-departure

No pre selected slots for me either for tomorrows 00:00 to 07:00 window. Not done any manual selections. neighboring-volume

@"admin"#p1711 Yes, it does make sense. As I'm quite likely to have done SOMETHING to my slots between 19:30 and 23:00 I have split the window in two, to ensure 23:00-08:30 gets populated every day, and I'll see what happens in the pre 23:00 window - it might turn out I don't need it at all, as it is all so fiddly in there with the falling trend through the evening, while not always a consecutive fall in prices, that I'll end up doing it manually anyway. At least the programming is easier than with the Growatt interface!

No Pre-Selected Slots

johalareewi

admin and because that is inside the new agile charge window

How about indicating which of the slots are in an active charge window (maybe different coloured background) then it is quick and easy to see if we are manually selecting (or deselcting) slots in a window.

kerregan

johalareewi I think it would also be helpful to show different colours for slots that have been automatically selected and those which have been manually selected by the user.

admin

kerregan We currently cannot distinguish between that, without backend changes, and it might get a bit messy in terms of the UI.

Agreed that we could do something to highlight current windows on the tariff sections.

kerregan

admin Understood.

Here’s one reason why I asked to be able to see the difference between automatic and manual slots:

If I make a change to any charge window(s), I think the system overwrites and recreates the slot selections for all windows. Since it does this even for a charge window that has not been changed, it is unnecessarily undoing my carefully thought out (!) manual slot selection.

Could you perhaps only recalculate slots in the charge window that has been changed.

Thanks

admin

kerregan There is a reason why we overwrite the lot when one agile charge window is changed.

It's easier and causes less other problems. For instance:

What if you have manually selected a slot outside of charge windows and adjust or widen a window's time from-to?
What if you have existing slots and you change your window and narrow the window's time from-to?

We could bake conditions in to say, OK so if the window time from/to remains the same, recalc just that window only.
But if not, then recalculate the whole lot? That logic seems even more tricky to explain to users, and rather inconsistent.

So, in the end, we decided it's easier for people to redo their manual selections after a window change anyway, because the result may equally influence whether you need a hand picked slot or not.

Basically, re-evaluate your slots after you update/save an agile charge window.

Happy to hear any good alternatives that take the scenarios above in mind.

kerregan

admin Thanks for the quick and clear response.

You say that people may want to ‘redo their manual selections after a window change anyway, because the result may equally influence whether you need a hand picked slot or not.’ But for me at least it is mainly the other way round.

Each day I look first at slot prices and tweak the automatic selections, perhaps in anticipation of solar generation the next day. I also look to hold my overnight battery charge until the slot where the import price per unit significantly increases. But the time at which this happens changes day by day.

So in my case I first change the slots to optimise the cost of the required charging and then change the window end time to set the time to start discharging.

Similarly I might change the SOC target in the light of slot pricing.

So slots and windows are tightly entangled and ideally would be manipulated together on a single screen. However, I can’t quite envisage a clear and elegant way of achieving this!

johalareewi

I manually tweak the automated selections because there might be a couple of cheaper slots just outside the window so I do manual swaps.

What is annoying is if i edit one agile charge winfow, the other windows also get reprocessed rather than just the one I changed.

I haven't tested it yet but will editing a not-active window also trigger a reprocessing?

johalareewi

johalareewi I haven't tested it yet but will editing a not-active window also trigger a reprocessing?

Just tested. Yes it does.
Creating or editing a not-active window causes all the windows to be reprocessed.
Not what you would expect.

admin

johalareewi

Creating or editing a not-active window causes all the windows to be reprocessed.
Not what you would expect.

So yeah, that's easy enough to solve.

Apart from that though, this is a tricky nut to crack in a way that is sensible and keeps everyone happy. Users are clearly having their own ways of using the Agile charge windows and some update/modify more than others.

I manually tweak the automated selections because there might be a couple of cheaper slots just outside the window so I do manual swaps.

That shouldn't mean changing your agile charge window though, should it? Would you not simply select the slots manually that are outside your charge window for selection and Save those selected slots?

kerregan

admin

That shouldn't mean changing your agile charge window though, should it? Would you not simply select the slots manually that are outside your charge window for selection and Save those selected slots?

But you would have to edit the charge window to change the time to which the charge is held

johalareewi

admin That shouldn't mean changing your agile charge window though, should it?

No it doesn't.
My Active agile windows are stable at the moment and I don't envisage many changes in the future.

The thing that threw me was that all windows got reprocessed when I only changed one.

admin

johalareewi Yeah that's fair enough, this is the main point.

We envisage Agile Charge windows not changing day to day, and the system isn't designed with that use case in mind.

As you say, now and then, you'd reduce the number of slots you need, due to longer daylight hours etc.

kerregan

But you would have to edit the charge window to change the time to which the charge is held.

It sounds like you may need to broaden your Agile Charge window, which would mean you'd need to make fewer changes to your Agile Charge window going forward.

If you then make changes within the window and select the odd slot here and there, the window settings like hold charge automatically apply.

kerregan

admin I change the width of my charge window because the time at which the Agile Octopus price per unit ramps up (and hence the time at which I want to start using battery) changes from day to day.

Scott

I think I'm having similar issues. I had a window between 23:00 and 16:00. If the 22:30 slot ended up being cheap i wanted to add this on at start of charging the bat. However this then wiped the whole next day up to 14:00 randomly and left the 23:30 the previous night. This phenonmenon only seemed to happen when adding the 22:30 slot, not the 22:00. Is this something to do with it being the last slot from the previous day? I've added before and after pics. I thought it would be ok as i haven't changed a slot in the charge window. I have now changed the window to start at 22:30 until a fix is in place.

The last 22:30 is due to having auto charge for below 8p. feline-enthusiasm

admin

Scott I don't understand or can replicate what the issue is here.

I just did the same thing just now, see Loom recording here:
https://www.loom.com/share/4cc585ee962946d6be5b3eff2a08e580?sid=35c28380-2a77-4907-b0e3-d1ba9c931e2a

Unless this is somehow related to your auto selected charge slot < 8p at 22:30 tomorrow?

Also note that once the agile charge window start is in the past, auto selection will not take place.

Scott

The window was set from 23:00 or 23:30. When i added the 22:30 slot manually to add it on, this wiped the pre selected slots up until 14:00, but kept the22:30. I did this change at around 6pm and multiple attempts after trying to fault find. I ended up changing the window from 22:30 to 16:00.

After 4pm today however, no pre selected slots were filled for over night/tomorrow. Until i just went in now and opened and re-saved the agile window. The only anomally i can see here is the 22:30 being selected due to being less than 8p?

« Previous Page Next Page »