admin it's effectively the same as using the Pause button on the Giv app
The app pause button pauses charging and discharging but for the WW hold feature, you just want to pause discharging so you could just change the discharge settings and leave the charge settings alone.
It's interesting that despite the discharge setting being zero, there was still some discharging (a few Watts). Couldn't test the EV bit because the EV charge was during selected slots only. One night it will happen..
The app pause button pauses charging and discharging but for the WW hold feature, you just want to pause discharging so you could just change the discharge settings and leave the charge settings alone.
Right, but equally we know we don't want the battery AC charging during hold-charge either, right? So not sure it matters much tbh. Unless I'm missing some elaborate scenario?
admin Its just that on the screen it says it prevents discharge.
Although HOLD implies no charge or discharge.
It is also interesting that the HOLD instruction is sent at the start of the first hold slot but is not released until the end of the charge window (see my inverter log). I would expect the hold to removed at the end of each hold slot block.
It is also interesting that the HOLD instruction is sent at the start of the first hold slot but is not released until the end of the charge window (see my inverter log). I would expect the hold to removed at the end of each hold slot block.
Yeah, made sense to implement like this, and then any charge slots will modify charge power again if it's 0.
Mat would be helpful if you could charge from the pv if a hold was set during the day?
Good point.
Worked fine last night. EV charger didn't get any GE battery during a hold slot.
But from the logs, it looks like Battery Discharge is set to zero for pretty much all of the charge window rather than just the hold slots.
johalareewi Yeah, with the idea being that it's being reset at the end. Do you see the reset for charge/discharge power in your Giv log?
admin Do you see the reset for charge/discharge power in your Giv log?
Last night breakdown...
Agile Charge Window is from 00:00 to 06:30
Selected slots are:-
First slot at 00:00 all OK.
First hold at 00:30 both charge and discharge set to zero
Next charge at 01:30 Charge is restored to 2600 but discharge remains at zero.
Next hold at 02:30 - Nothing received by inverter
Next charge at 03:00 no change to charge or discharge values
Next hold at 04:00 charge set to zero
Next charge at 05:30 charge resotored to 2600
Next hold at 06:00 charge set to zero
Window ends 06:30 - nothing in WW activity log but inverter has this
Battery charge and discharge both restored.
johalareewi Thanks for the detailed breakdown, you can see the values that were sent but weren’t changed, by toggling one of the sliders at the bottom of the Giv log.
All in all, went OK then? Note that the latest release does not reduce charge power in a charge hold slot anymore.
admin Simple one last night.
GE Inverter log
Looks cleaner just using the Battery Discharge Power setting.
Just had an interesting situation.
Battery was at 96% and there were a few cheap slots coming up just before the peak period.
Tumble drier was on so using the GE app, I paused the battery so the tunble dryer would use the cheap electricity and save the battery for the peak slot. This was OK but half an hour later, Wonderwatt issued a PLAY command sequence. There is nothing in the WW activity log (apart from the skipping charge) and the GE app said battery was still paused even though it wasn't.
GE log
johalareewi So that command was issued as part of the 'disable charge slot', which had just passed.
Part of disabling a charge slot (whether a charge happened or not) is to reinstate discharge power (and charge power - gets reset too if it's less than max)
Not sure how we could decide not to, and know about other external ways that users might well interact with their Giv systems that we can't possibly all cater for?
GE app said battery was still paused even though it wasn't.
The GE app is quite prone to still having stale or cached values.
admin So that command was issued as part of the 'disable charge slot', which had just passed.
Ah. Didn't realide that still happened when a charge slot was skipped due to high SOC value.
Still learning how this works.
johalareewi It’s all good. I guess we saw it as something that wouldn’t cause any issues at that point. Most logical is to set those values back, as only occasionally you might mean them to be at 0.
Hi, relatively new to this and seems a great product. One thing is during the 'gap' periods on agile my battery seems to be half on hold, half not, in that according to the giv portal it's trickling out c.300w with the rest of the load being met by the grid, rather than holding on whatever SOC it's got to in the previous charging window. Could you look into it? I'm tremendous-control. TVM
I think some Giv inverters will allow small battery discharge even when Battery Discharge Power = 0. I have a Gen 1 HY3.6 inverter and it doesn't discharge at all but on the Giv community, others have said thier inverter allows around 300W to discharge. Would be interesting to see which inverters people have who are using the Agile Hold feature, and what happens.
freakouthtesquares Looks like we do just send the 0 discharge power and the Giv response acknowledges that it has been set, see below - but your Giv HY5.0 inverter still discharges somewhat.
As @johalareewi says, and I read similar things in Giv forums, some inverters are still discharging somewhat, despite discharge power being set to 0.
Our alternative approach to set SOC target to current SOC had a similar effect, which is why we switched away from that.
All in all, it's something that's unfortunately out of our control.
Thanks both. Bit odd as it would maintain a steady SOC under the schedules I had set up via the portal, i.e. if charging window was 2-7am and it got to 100% SOC by 5am, it would remain there until 7am.
Also FWIW my inverter is definitely HY3.6 but for some reason in the portal it is marked as HY5.0
