We've just rolled out an initial version of Intelligent Octopus Go, enabled for a handful of users. Please DM or drop us a line at labs@wonderwatt.com with your WattID or registered Gmail email address if you would like to try this out.

Exciting. Is it just for compatible cars or chargers though, or for any car or charger?

@"Gazzagreen"#p3146 I'm in the beta if you can you have the tariff I believe it will work as its pulling from the Octopus API and controlling your inverter so has nothing to do with the car or charger. It's found my slots first time so really impressive.

Yes I’m interested please: impassioned-spirit

@"Gazzagreen"#p3146 Not related to car charger control. Mainly verifying the mapped charges for your EV and creating a hold/charge for your solar battery to match the dynamic slots, to prevent your battery draining into the EV.

@"psiloc"#p3148 Enabled for you.

I see. I'm happy on flux atm, but if I was to try this later, what I'm trying to ask is I am able to get the intelligent Go tariff from Octopus? I ask because as far as I understand it, they require a car or a charger they can control or you can't get the tariff. e.g a tesla as they can control the charging on the car, or compatible charger. Is this agreed with octopus to be able to use the WW-tariff with a non-compliant car or charger?

@"Gazzagreen"#p3151 Without a compatible EV - for which they will perform a test charge, I don't think you can get OIG. We simply check the dynamic charge slots that Octopus has assigned to your Octopus account. If you haven't got Octopus Intelligent Go, we won't retrieve any smart charge slots from Octopus when we query your account.

@"Gazzagreen"#p3151 Yep you need a car or charger that is compatible.

I might be getting a (2nd hand) Tesla later this year with Pension money :D

Hi there, impassioned-spirit First usage of IOG last night by plugging my car in and I don't think it quite went to plan! :) [URL=https://i.imgur.com/5qtopBZ.png][IMG]https://i.imgur.com/5qtopBZh.png[/IMG][/URL] So at first it picked up my smart charge of 23:30 - 06:30 and had a target of 86% at a rate of 33%, which is fine. It then, from somewhere, picked three more half hour blocks and mapped those. The problem is that in between those half hour blocks, the battery was discharged to power the house. This is not only in contradiction to the proper mapped charge but was unnecessary anyway as IOG always has off-peak rates between 23:30 and 05:30 - in fact of course the battery should still have been charging from the grid due to the dismal forecast. I don't know what happened with those additional blocks but if I check my Octopus app, those blocks are shown there right now too, so WW hasn't pulled them out of nowhere. I do know that in reality Octopus was charging my car as per the original mapped charge of 11:30 - 06:30 and this didn't get interrupted. One thing I recall, yesterday when I plugged my car in, the charge target was just 10% additional, and I _think_ it's possible that the original smart charge schedule was these three blocks. I subsequently changed the charge target to be 60% additional, and it mapped the new proper schedule. I wonder if both sets of instructions were still in the API? Is there something you need to be checking to know whether you have the latest schedule? In any case would it be possible to configure WW so that it always "knows" about the basic 23:30 - 05:30 off peak, and only does something with smart charges in addition to that? Love that you're doing this by the way, please don't take any of this as a moan!

Intelligent Octopus Go - limited beta

admin

patrickjanssens You could split your export schedules up into multiples with the relevant min SOC condition to work around his for now.

patrickjanssens

admin Thanks. Splitting the export schedules into 3 seems to have resolved the issue . Is it correct that the maximum have 5 schedules. I have another 2 for night discharge resp. recharge the battery, and can't add any more.

However I have one more issue. It seems after the discharge schedule is completed the systems enables Eco mode again. But in this case the batteries will immediately start charging at full capacity again. However when my solar production starts exceeding my inverter capacity (abt. 5.3 kW in my case). I attach the curves of todays session for your info. You can see the battery starts charging again from 10 am whilst nothing is exported to the grid. As soon as the battery reaches full charge (after 1 pm) the solar production drops to the maximum inverter capacity.
I only want to send the excess DC to my battery, whilst any AC produced should go to the home consumers and any excess thereoff I want to export to the grid. In this way I maximise the time I can keep storing the excess DC from the solar panels.
I found that if I manually disable Eco mode in the GivEnergy remote control the charging will be taking surplus solar DC power only, which is exactly what I'm trying to achieve.

Any chance to automate this? If I could just add an item in the schedule that switches off the eco mode that would do the trick.

patrickjanssens

One more thing with respect to splitting up the schedules. It seems I need to leave some space between concurrent sessions in order for this to work. I initially started the 2nd session at the same time the first one ended. But this resulted in the second session being ignored (At least the battery resumed to charging rather than discharging). I guess this is because the instruction to start a session is sent a few minutes prior to its starting time? So the instruction to terminate the first session was sent after the second one was starting resulting in the system reverting in Eco mode? Is my understanding correct.
At least it seems that leaving 5 minutes between sessions resolved this. (Will do further testing of this tomorrow)

admin

patrickjanssens Yeah, good observation. Your understanding is correct. And it’s good to leave a 5 min gap or so between custom schedules for this reason.

This is basically because we cannot guarantee to run all instructions within on minute due to retries etc., and simply the sheer amount of instructions we send out regularly.

As such, we run instructions every couple of minutes.

paul_stanyon

admin hi! Please could I be added to the beta: bumpy-drama

admin

paul_stanyon Done!

PeteC

"Yeah we'll look into that. It's a real pain as to why Octopus even send dynamic slots within this period though!"

admin I think it's because it's cheaper for Octopus to charge the EV during those slots. They need to make money somehow!

extraneous-pattern

I’d love to try this new feature, thanks.
ID: extraneous-pattern

admin

extraneous-pattern All sorted.

Monkey

I had a charging schedule that was due to start at 0230 and end at 0630. However WW only picked up the standard 2330-0530 slot. This resulted in my battery being drained by the car between 0530-0630. Any ideas why. WW didn't see my early morning charging schedule? Car was plugged in by 2300.
I have integrated my Ohme charger to IOG so schedules are created by Ohme.

admin

Monkey We'll have a look, thanks for reporting.

extraneous-pattern

admin
I think I also experienced this last night. Woke up to a 50% drained battery. Charging schedule was set to complete 0400 and immersion went on between 0430 and 0530. Was expecting the WW IOG setup to keep battery charged to 100% until 0530?

extraneous-pattern

admin

extraneous-pattern Yeah we’ll get this sorted next. We need to normalise those slots into one.

admin

@PeteC @extraneous-pattern This glitch should now be fixed as part of Release 637. We now normalise the schedules correctly even if dispatch slots get mapped that are within (part) of the main IOG window 23:30-05:30.

Let us know how you get on, thanks!

PeteC

Wonderful. I've re-enabled IO on Wonder Watt. We'll see how it goes.

MrMessy

Hi Wim/All,

Thanks for letting me join the IOG beta program. All signed up yesterday afternoon.

I'm hoping this will achieve 2 things for me, namely deal with the IOG smart charging slots (so far, so good, more in a minute) and manage my solar clipping.
For context, we have:
Giv 5kW Hy
2 x 9.5kWh batteries
7.6kWp EW solar
Zappi
ASHP

A couple of questions...

what's the best way to deal with an East/West array? For the moment, I've just put in an equivalent South array, which is OK for summer, but massively overestimates for winter.
how do you deal with clipping?
up until now, what I've been doing is charging batteries to full overnight, checking the forecast in the morning and creating some space if necessary and setting a low charge rate in the giv app to then soak up only the xs.
I also use the timed pause function in the giv portal (05:30-19:30) so that ALL solar is exported to maximise income.
This has been pretty successful, but requires constant manual intervention and is quite frankly becoming tiring.

Back to the smart charging thing and a couple of observations.
Firstly, after last night's charging, I noticed this morning that I was pulling power from the grid, ie Eco hadn't been re-enabled.
Secondly, my batteries started charging from the grid at 22:30 last night, initiated by WW and a schedule from Octopus. All good except there was no EV plugged in. WTF?

Anyway, apologies for the rambling post. No chance of any clipping today, the weather's shocking. ⛈️😅

admin

MrMessy Firstly, after last night's charging, I noticed this morning that I was pulling power from the grid, ie Eco hadn't been re-enabled.

We don't touch Eco for charge slots. Only for export where it gets disabled and at the end we re-enable Eco again.

MrMessy what's the best way to deal with an East/West array? For the moment, I've just put in an equivalent South array, which is OK for summer, but massively overestimates for winter.

It's a bit of trial and error really, I guess for summer, you would simply reduce your PV peak a bit.

We don't currently deal with clipping very well, happy to hear of suggestions on how we can automate something that works for everyone.

MrMessy Secondly, my batteries started charging from the grid at 22:30 last night, initiated by WW and a schedule from Octopus. All good except there was no EV plugged in. WTF?

We did get a 22:30 schedule mapped from Octopus. Which was then later adjusted to a 23:00-5:30 schedule.

MrMessy

admin

OK, so the 1 and 3 was probably my fault, spotted battery had started charging at 22:30 and panicked as the car wasn't plugged in, so stopped the charge before I'd realised.
Had a quick check on a few FB groups and appears I wasn't the only one with an unexpected schedule and MyEnergi were doing some site maintenance.
On the plus side, WW did exactly what it is supposed to.👍

I could do a flow chart for managing clipping, showing what I currently do manually, if that's any help?
I think I've pretty much nailed it with various if/then/else based around predicted solar.

Switching off Eco (as suggested by @patrickjanssens ) does work for picking up the clipping exactly but, has a fatal flaw in that if the solar dips below the house load you start drawing from the grid, which in my eyes defeats the point.

BTW, is the switching off/on Eco when setting a scheduled discharge a legacy for Gen1 inverters?
I didn't think it was necessary for Gen2 and newer. I know Octopus R&D had an issue where it wouldn't automatically switch Eco back on in certain scenarios.

admin

MrMessy BTW, is the switching off/on Eco when setting a scheduled discharge a legacy for Gen1 inverters?
I didn't think it was necessary for Gen2 and newer. I know Octopus R&D had an issue where it wouldn't automatically switch Eco back on in certain scenarios.

Good question, I think we have seen a similar thing with Gen2 though, but would be good to have this confirmed by Gen2 owners.

Initially we used to use the Discharge preset, which automatically turned eco off.

MrMessy

@admin
Spotted a minor issue.

If a smart charge slot overlaps a previous scheduled force discharge, the discharge script doesn't complete and therefore Eco isn't switched back on.

See attached from 16th (no smart charge) and 17th (with smart EV charge)

WattID primary-hotel

admin

MrMessy Good spot, we have seen that happen before, usually we suggest to keep say 5 mins between an export slot end and charge start.

We could however always make sure we turn Eco-mode on when issuing a charge cmd?

« Previous Page Next Page »