Hi Wim @"admin"#1, I hope that you are well, it has been a while - sorry there has been a lot going on. I have mentioned this previously but during the winter when I was using all of my AIO it wasn't a problem, but now as we move to the warmer months, my desired value is now more relevant. Unfortunately, whatever value I set this to, the AIO charges to 100% SoC rather than the desired value - in my case 85% [URL=https://imgapi.wonderwatt.com/i/us7l4lD.png][IMG]https://imgapi.wonderwatt.com/i/us7l4lDh.png[/IMG][/URL] I can see in my invertor logs, however, that WW is setting both the Enable AC Charge Upper % Limit to True and the value of AC Charge Upper % Limit to 85, so in theory, it should be all good. But every time, the AIO just blasts past this value and charges to 100%. I have also seen when it says in the logs, "Keeping battery at SOC level:88%" this is the outcome: [URL=https://imgapi.wonderwatt.com/i/J9dFsFg.png][IMG]https://imgapi.wonderwatt.com/i/J9dFsFg.png[/IMG][/URL] So, something is not quite working right with WW and GivEnergy in this regard. WW ID: zany-sound

@"MrMessy"#p7270 That would be very useful to narrow it down, thank you!

@"admin"#p7271 OK, have set this. Should be done at approx 04:30 (no EV tonight). Will report back in the morning. [URL=https://imgapi.wonderwatt.com/i/blK3ZEK.png][IMG]https://imgapi.wonderwatt.com/i/blK3ZEK.png[/IMG][/URL]

@"KristianS"#135 @"admin"#1 [URL=https://imgapi.wonderwatt.com/i/MTyTtm6.png][IMG]https://imgapi.wonderwatt.com/i/MTyTtm6h.png[/IMG][/URL] [URL=https://imgapi.wonderwatt.com/i/0mllLIn.png][IMG]https://imgapi.wonderwatt.com/i/0mllLInh.png[/IMG][/URL] Times didn't need changing, as they were already at 23:30 and 05:30. If you need to check exactly which registers were issued commands: primary-hotel

[URL=https://imgapi.wonderwatt.com/i/sjYroex.png][IMG]https://imgapi.wonderwatt.com/i/sjYroexh.png[/IMG][/URL]

[URL=https://imgapi.wonderwatt.com/i/QiBzxvX.png][IMG]https://imgapi.wonderwatt.com/i/QiBzxvXh.png[/IMG][/URL]

Smart Charging - Switched to Use Fixed Charge to X % being ignored

admin

KristianS That’s weird. Sounds like an issue at the Giv side, no?

Have you been able to use the Giv app or desktop site for setting a similar schedule with target SOC and repeat the same behaviour?

KristianS

admin Yes, weird indeed.
To be fair, I haven't tried that recently since being on IOG, but I will have done in my early days of testing when I got the AIO

MrMessy

If it's any help, I can test this tonight for my G2 hybrid, to see if it's a general issue or specific to AIO.

admin

MrMessy That would be very useful to narrow it down, thank you!

MrMessy

admin OK, have set this. Should be done at approx 04:30 (no EV tonight). Will report back in the morning.

KristianS

Cheers MrMessy
I will be interested in your results. Fingers crossed it is not just mine.... or it could still be unique to AIO.....?

MrMessy

@KristianS @admin

Times didn't need changing, as they were already at 23:30 and 05:30.

If you need to check exactly which registers were issued commands:
primary-hotel

KristianS

Thanks... It's good to know that your GivEnergy setup is doing as expected.

Now that I don't need to charge my car this evening, I am tempted to set a manual setting via the GivEnergy app to prove that my setup will do the same, with the same expected outcome. I will disable WW IOG for tonight and set a manual for a 90% value [my AIO is currently at 88% so an 85% SoC would not charge at all].

KristianS

This is the value that the App has changed:

which is the AC Charge 1 Upper SOC % Limit, but that is not the value that is set by WW, normally. This is AC Charge Upper % Limit instead.

So, looking through the logs, WW alters these registers:
Enable AC Charge Upper % Limit
AC Charge Upper % Limit
AC Charge 1 Start Time
AC Charge 1 End Time

So, I guess this is by design, but in the AIO we appear to be getting different outcomes.
I will report back tomorrow AM - work allowing

MrMessy

KristianS Are you saying the AIO has 2 registers controlling the SOC % Limit?
Namely:
AC Charge Upper % Limit
and
AC Charge 1 Upper SOC % Limit

My G2H definitely does not, as far as I can see. I have only this...

KristianS

As expected. Charged at ~ 800W until SoC = 90% and then maintained that SoC

admin

MrMessy I presume this is likely to do with firmware version etc.

How on earth are we supposed to know what to use? It's bizarre that Giv don't have a consistent implementation and inverter and FW differences effectively bleed out into the public API, which then makes it hard for any and all consuming services/apps that are using the Giv API.

@KristianS Could you see what Giv suggest here? They really should make sure there's a much more consistent implementation, ie. for your flavour of AIO and fw version, setting the main AC Charge Upper % Limit should simply result in setting the underlying AC Charge 1 Upper % Limit register (if that's the only one that seems to have an effect). The mapping should happen on their side, rather than push this upstream.

KristianS

MrMessy So there are two types of registers.

Global ones, as per your image:

and then Charge / Discharge Schedule Settings - which I suspect you have also.

The GivEnergy Mobile app alters Slot 1 = Charge 1 Settings, Slot 2 = Charge 2 Settings and so on....
I concur, you would think that by setting the Global this would take precendent. It would appear not.....

KristianS

admin I am happy to raise a case with GivEnergy as to what they suggest is the best way forward on this. As per my previous response to Mr Messy, you would think that setting the Global values, this would supercede any setting set on the charge schedules..... but on the face of it, that appears not to be the case. I will also review the online API documentation - but nothing has been udpated on the portal for a while at GivEnergy in their 'What's New' section..... so whether this has been documented for the different firmwares..... Anyones guess.

MrMessy

admin How on earth are we supposed to know what to use? It's bizarre that Giv don't have a consistent implementation and inverter and FW differences effectively bleed out into the public API, which then makes it hard for any and all consuming services/apps that are using the Giv API.

I agree. It seem very poor implementation that a) it's inconsistent across different FW and b) there are duplicate/conflicting registers at all.

MrMessy

KristianS

KristianS and then Charge / Discharge Schedule Settings - which I suspect you have also.

I don't have those, as you can see, which is why I was a little confused...

KristianS I am also now temtped to set a Charge 1, Charge 2 and Charge 3 settings and see if I can control the SoC using these registers and timings manually. @MrMessy I wonder if you too wouldn't mind delving into your GivEnergy Charge/Discharge schecdules and see if you can also 'control' your system the same as I think I can. You up for that?

...... which is going to be tricky, obviously.

I think it was added for Gen2 briefly, about a year ago, but was rather hastily withdrawn, reasons unknown. I believe Gen3 may also have the 10 charge/discharge slots available, presumably also with the additional SoC % registers.

KristianS

I am also now temtped to set a Charge 1, Charge 2 and Charge 3 settings and see if I can control the SoC using these registers and timings manually. @MrMessy I wonder if you too wouldn't mind delving into your GivEnergy Charge/Discharge schecdules and see if you can also 'control' your system the same as I think I can. You up for that?

BTW - I have done a 'Reset to Defaults' in the app before making any alterations to clear any anomoly entries first

KristianS

MrMessy
So, whilst I agree the implementation is a challenge, the ability to have flexibility of the differing Slots makes sense from a manual perspective. Which is exactly what I am going to enact this evening...
But to my point earlier, if a Charge / Discharge slot 1- 10 [for each] is set, then the Global values should take precedent, IMO

KristianS

Interestingly.... Reset to Defaults, doesn't actually reset everything to default values.... Seriously....

As you can see, Charge 1 Settings have been reset from a time values, but the AC Charge 1 upper SOC limit is stuck at 80%..... Weird

admin

KristianS At this point you almost wonder whether they accidentally pick the wrong AC Charge 1 Upper SOC limit and it's just a mapping issue.