Cloud API stopped working

for the last two days my automation script that sets how much to charge the battery to during cheap rate is not working. The script runs and uses the the HTTP API to set the percentage to charge the battery to. A good response is returned from the HTTP request BUT the new percentage to charge to does not take effect. It remains at the old setting.

Looking at the remote settings page on the portal there are no log entries to show these recent API requests.

So something very odd, the script and API has worked successfully for many moons is now not have the desired effect even though a good return code is received from the API request

Is anyone else seeing this, ideas as to how to resolve?
Cheers
Dave

same here. See evidence below.

Giv reports back that command is successfully coming through but when checking on inverter log, nothing happens. Also started with me 3 days ago.

I've seen other users on WonderWatt who are sending similar commands to Giv with the exact same issue also starting 3 days ago.

It's a general issue, any API commands from anywhere seem not to work anymore.

I also see that the API with Octopus which is reporting how many kwh charged and discharged on the Giv portal is no longer working. That also started 3 days ago.

GivEnergy, what is happening here please. At Wonderwatt they have done all the checks and are saying your API is responding correctly but many of us are not seeing the changes implemented on the inverter for the last 3 days. With multiple tariffs with more than one cheap window please either give us the option to set multiple battery charge cycles (after all you have done it for discharge cycles) in your own control software or sort out the issues with the third party initiation please.

Waking up at 4am to manually set a charge or trying to remember to manually reset at 1pm when at work is not great and without charging the battery in the cheap rates on octopus cosy means expensive heat pump power and reduces the value of the battery massively.

Thanks
Mark

The crest
Just to clarify - it's not only commands from WonderWatt - it's ALL API commands. Even sent manually from whatever tool.

Is it possible that the key expired? Could try generating new ones. Though the server shouldnt appear to accept requests if the key has expired.

DD as said by JMA this appears to be a GivEnergy issue with ALL API scripts not being written. I can confirm my keys are in date

Probably doesn't help, but my API scripts are working fine. So it's not a universal problem.

The crest also when keys are not valid an error is received which is not the case here. The API is accepted and returns a good return which under normal conditions mean the request has been actioned but not for the last few days!

As mentioned, there is nothing wrong with the API request and Giv does return a valid response.

Have there been any changes to the way presets work and are actioned on the Giv backend?

The charge schedule in question is preset 1.

Wonder Watt when you say that there's a valid response, do you mean a 201 response or that reading back the value confirms it has actually been set? I've recently seen a 201 in response to the write message but a "-6" when reading back what should be a time. Looks like an issue at the GivEnergy end.

@TheDragon (GivEnergy) would appreciate if you can get this looked at, not having a working API (that has worked for many moons) is a a royal pain,

A little more info its the post request to /chargeBattery API that is not working for me - it returns a 200 status - so all looks good but the request is never actioned.

stevelewis Yeah, it's a 201 HTTP status and valid JSON to say the preset setting has been written successfully.

{
    "data": {
        "success": true,
        "message": "Written Successfully"
    }
}

I'm unsure if this is related, but I had a strange behaviour yesterday evening where the battery paused even though I told it to be in eco mode (which it already was, so if it just ignored my API call then it would have kept going in eco mode). https://community.givenergy.cloud/d/3632-battery-paused-itself-for-an-hour

just spotted I was looking at an old part of my code that is no longer called. The problem is still the same but to clarify the code that is now in use

• is posting to the presets API (as opposed to old /chargeBattery)
• it returns 201 (as opposed to 200)

Have raised a bug report and also sending details to support.

Yeah, it does seem to be the presets mainly.

Is it broken right now for anyone else? My AIO battery has 40% remaining, and I can't get it to power the house via eco mode, or charge via the quick settings in the app, or respond to anything. The API requests are accepted, and the battery is reporting status to the app and the cloud, but it's just not doing anything when it's told to.

I received an updated by email from GivEnergy. They are aware of the issue with reports from multiple users and the developers are looking into it.

... and it just started working again.

KevinB been playing in home assistant tonight and can confirm mine now seems to be working (but didn’t set a max charge rate for the last few nights!)

Thanks for confirming naltsta

It would be nice if there was an update on https://givenergy.freshstatus.io/ when this happens, so (a) I'm not digging through all of the things I have control over to see if I screwed something up, and (b) to give some confidence that GivEnergy know that something is amiss.

still not working for me. Have provided developers info including code snippets. Looks like the API update on the 6th Dec is the point when it stopped working. The change log for the 6th shows no changes in the area of setting inverter settings.

Apologies all, we were notified of this issue and has been resolved.

We're preparing the API presets for multiple charge discharge slots but unfortunately the by-product caused a change in the API layer. The request will still work for the body as shown on this thread but we'll be releasing updates in the future for multiple charge discharge changes on the presets. Sorry to all those that have been affected by this

edit: The only layer affected was the modify preset endpoint. Other changes via app/local/portal were not affected

Mickey (GivEnergy) that is good news, will try it out when I get home

Wonderwatt instructions did not come through to my system at 11:40 today. Will try again tomorrow.

as of 15:00 can confirm my home automation script that sets time period and amount to charge is working again.

Success!