New user with GivEnergy All In One (two batteries) and Octopus Agile.
I had it working on 24-Aug with the charge slots triggering a charge, which is reflected in the WW logs.
Slots scheduled after midnight 25-Aug failed, with nothing in the WW logs, but still showing on the WW Agile Octopus Integration screen.
Am I doing something wrong?

Running manual charge windows on the GivEnergy inverter for now.

WattID:
mortified-test

We have all these in your WW activity log for 25th, which you should see:

    admin
    You are correct, my mistake for reading the logs wrong.
    It doesn't appear to be charging very much from the grid for these times though (as per the SOC levels in the logs). What sort of things would limit the charging?
    The batteries were at 4% at 8am this morning.

    2024-08-25 05:58:41 6 %
    Charge instruction set to 100% for 06:00 - 06:30 - Agile Octopus
    2024-08-25 04:58:37 7 %
    Charge instruction set to 100% for 05:00 - 05:30 - Agile Octopus
    2024-08-25 02:29:18 6 %
    Charge instruction set to 100% for 02:30 - 03:00 - Agile Octopus
    2024-08-25 00:29:42 4 %
    Charge instruction set to 100% for 00:30 - 02:00 - Agile Octopus

        DualAIO Hard to say, but nothing at our end by the looks of things.

        These are half hour slots, and as you can see we are setting the charge rate to 6000:

        So in theory, your battery should get a 3kWh charge added in 30 mins.

        Perhaps your battery needs calibration? Might be worth asking over on the GivEnergy forums: https://community.givenergy.cloud/

            admin
            It's weird as it was working initially.
            Failed to import after the comms below too. I'll check out the GivEnergy forums as suggested - thanks.

            2024-08-25 18:58:08 70 %
            Charge instruction set to 100% for 19:00 - 20:00 - Agile Octopus

              No response from the community yet, but I do have a question:
              Is there a way to view the API response codes (200, 201, 400, etc) in the activity logs (or elsewhere)?

              admin
              GivEnergy have advised that the WonderWatt service is sending the calls to the Inverter1 - this is INCORRECT

              All charge calls should be sent to the Gateway serial number.
              Looking at my Settings, the serial number that has been pulled back using the "connect" button, ends with G142. That is indeed the serial number for one of my All-In-One units. The Gateway serial number ends in G177.

              How do we go about correcting this?

                  DualAIO Ah, OK - let us dig into this, will report back here. Thanks for providing those details.

                    DualAIO We have updated this manually for you in the backend, which means instructions will now get sent to your GW serial.

                    Let us know how it goes, thank you!

                        admin Unfortunately this is still not working. I've reached out to the GivEnergy team to see if they can spot anything.

                          admin Actually, looking at the logs, WonderWatt is still sending the charge commands to the AIO and not the gateway.

                              admin
                              If it helps (and I've only recently discovered this myself) - if you have a GivEnergy system with one All-In-One battery, the charge commands should be sent directly to the AIO. If you have multiple AIOs, then the charge commands should be sent to the Gateway.

                                  DualAIO This should now work fine in Release 720. Please Connect with your API key in settings and Save.

                                  Thanks for working through this with us.

                                      admin I've pressed the reconnect button and the correct serial number is shown, however, according to the Wonder Watt Activity Log, no charge instructions are being sent at all now.

                                          DualAIO Looks like there was an issue parsing SOC % from the AIO associated battery. Should be fixed now in Release 722.

                                              admin Still don't think this is working. Although the SOC was 100% at 15:30 for a charge slot, I was expecting to see an entry in the log indicating this and advising that the charge instruction was skipped.

                                                  DualAIO You have an entry in your activity log from 15 mins ago:
                                                  Battery fully charged, skip charge instruction

                                                  But it does indeed not confirm whether it is working, as we'd need an instruction for that. You could try an export instruction instead?

                                                      admin Okay, so the logs can sometimes take a few minutes to appear.

                                                      It successfully called a charge window between 20:30 to 23:30.

                                                      However, the charge instructions were not called for the slots between 00:30 to 01:30 and 03:00 to 05:00.
                                                      Any idea why?