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: [URL=https://i.imgur.com/R6Ye9Qg.png][IMG]https://i.imgur.com/R6Ye9Qgh.png[/IMG][/URL]

@"admin"#p4136 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"#p4144 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: [URL=https://i.imgur.com/2aAi21L.png][IMG]https://i.imgur.com/2aAi21Lh.png[/IMG][/URL] 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"#p4145 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"#p4145 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"#p4188 Ah, OK - let us dig into this, will report back here. Thanks for providing those details.

@"DualAIO"#p4188 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"#p4209 Unfortunately this is still not working. I've reached out to the GivEnergy team to see if they can spot anything.

@"admin"#p4209 Actually, looking at the logs, WonderWatt is still sending the charge commands to the AIO and not the gateway. [URL=https://i.imgur.com/jDSSg5h.jpeg][IMG]https://i.imgur.com/jDSSg5hh.jpeg[/IMG][/URL]

Charge windows failing

admin

DualAIO Fixed now as part of Release 726.

DualAIO

admin Hooray, it has successfully sent a charge instruction for 11:00.

admin

DualAIO Great - thanks for reporting back!

« Previous Page