I run a number of standard repeating schedules that run overnight 7 days a week. Last night a charge schedule " Part 2 Charge" failed to execute @ 03:27 and it did not leave any reason or trace in the WW log files. I have had this happen once before and the next day it ran as normal without any modification. The schedule is a straight forward charge schedule to 100% with no conditions set. If you could take a look for me please circular- strategy

@"duplada"#p8625 Looks like the system data response from Giv was incomplete and we could not parse it due to the many null values, including things like SOC/percent. `Error parsing system data response: {"data":{"time":null,"status":"Unknown","solar":{"power":null,"arrays":[{"array":1,"voltage":null,"current":null,"power":null},{"array":2,"voltage":null,"current":null,"power":null}]},"grid":{"voltage":null,"current":null,"power":null,"frequency":null},"battery":{"percent":null,"power":null,"temperature":null},"inverter":{"temperature":null,"power":null,"output_voltage":null,"output_frequency":null,"eps_power":null},"consumption":null}}, txId: BGIrdHim` We will fix the bug and ensure this shows up in the activity log. And will be added to alerts.

That's a lot of Null's - Great Support Thank you

So because my SOC was around 17% this evening my export schedules Quick Discharge 1 - 4 didn't execute which is as expected. When WW executed "Quick Discharge 5" @ 22:50 which takes the battery down to 4% it errored out with the following. Looks as if the SOC % is missing. [URL=https://imgapi.wonderwatt.com/i/6wDSi27.png][IMG]https://imgapi.wonderwatt.com/i/6wDSi27h.png[/IMG][/URL] I will watch the system to see if my first Charge Schedule "Part 1 Charge" executes correctly @ 23:30 and report back. If you can take another look at it please.

Schedule "Part Charge 1" executed correctly @ 23:30 [URL=https://imgapi.wonderwatt.com/i/mPs88UF.png][IMG]https://imgapi.wonderwatt.com/i/mPs88UFh.png[/IMG][/URL]

I will see if "Part 1 Discharge" schedule executes @ 01:40 and let you know

@"duplada"#p8628 Yep, same issue, null values returned from Giv API, which we cannot do anything with. We need SOC. At least we now know the log fix is working!

So have GE updated their API and have an issue with it? It seems rather strange it has happened twice in 24 hours to me but not to other users. This has to be some sort of intermittent problem as the charge schedule which errored when I first reported the problem ran fine last night, but an export schedule that worked fine the day before errored last night, Neither have been amended. The three schedules that have run since the last error have all succeeded When that type of error is received, would it not be possible to retry the execution again? What is the way forward here, Do you have contacts at GE to explore this further as a consistently reliable system is essential for user confidence. Keep me updated and I will let you know if I see further instances of this issue. Thanks for looking at this on a weekend.

So I had another parsing failure in the early hours today [URL=https://imgapi.wonderwatt.com/i/AU4USzy.png][IMG]https://imgapi.wonderwatt.com/i/AU4USzy.png[/IMG][/URL] Can you give me some insight into the operation of WW as I have been trawling through my data logs to see if I can identify any communication problems or missing data in my GE logs. My dual AIO system records data about every 60 seconds and not the usual 5 minutes. In the past occasionally I have seen odd instances where some field data has been missing from a record in the GE logs. Is the error happening as a result of querying the GE data to see if the Schedule should be executed? or Is the error the result of actually trying to set up the schedule on the GE server.? what time window before a schedule time should I be looking for missing SOC data 2 of 3 minutes? Any information that you can provide would be useful as I am determined to get things operating successfully Would it be possible where you get a failure like the parsing error for general schedules to perform a retry a few minutes later? Retry on Failure Y/N?

@"duplada"#p8639 Sure, the API call is basically: HTTP GET: https://api.givenergy.cloud/v1/inverter/:serial/system-data/latest Where :serial param is your GW serial number. And you will need to sent your API token as a Bearer authentication header. You can try this with various tools like Postman. This seems to occasionally result in a bunch of null values. But because it's a valid JSON document and we get a valid HTTP status (200 OK) back, we don't retry these. This is ultimately something that Giv will need to sort out on why their dual AIO GW sometimes responds with all null values for that specific API call (`system-data/latest`). Hope that makes sense!

@"admin"#p8640 Well it sort of made sense. Both you and in particular me both know that GE is not going to sort anything out, as they just cannot cope, they won't even answer the phones these days. I have multiple open support tickets going all the way back to March. There is one person who knows and understands the dual AIO's and that is it at GE period. I fully realise that you have a system that supports multiple inverter manufacturers and you trying to make your system as flexible and reliable as possible. I have had 4 of these show stopping errors now. 1 was an Inverter Timeout and the other 3 have been the parsing errors where the SOC is missing. What I was suggesting with the retry option is since the WW system knows that there is a parsing error and is about to send a WhatsApp message, could it not execute a retry also a few minutes later. Also the timeout error in the log text also says "try again" so why can't the system try again automatically? It just makes sense to me. Thanks again for replying on a weekend.

Failed Execution of Standard Schedule Not Recorded in WW Logs

duplada

admin I certainly did notice that. In fact I got that excited that I didn't even notice that WW saved the day again by retrying in 5 with a parsing error @03:25. The first error, Invertor Timeout / Offline (below) was the internet dropping 2 minutes before my 23:30 charge schedule. It was if you had engineered a test to show off the new feature of WW. So far the new retry has saved the day 3 times in the last 2 days which is fantastic.

I did however have some events were I didn't receive a WhatsApp and one that I did, if you can let me know why please?

The WW system just gets better and better thank you so much. 🥳

Steve1

admin Hi, I have just added a 2nd GE AiO and are now getting similar error messages from WW, see below;

2025-10-18 05:30:06 N/A %
Error parsing system data response after 3 attempts, txId: Ek8UKk08
2025-10-18 05:03:06 80 %
Error setting discharge-rate schedule: There was no response from comms. Please try again [bk1NRGP1]

This has happened a few times in the last week or so

WindyMiller

WindyMiller Here's proof the 5 minute retry is working. End of hold at 4pm met with lots of Comms failures but the retry at 4.07pm got through. Nothing in the WW log though.

duplada

WindyMiller Nothing in the WW log though.

So it worked, but the WW log didn't specifically say it was retrying in 5 minutes? It would be better if it did let you know, an alert would stop you trying to correct manually if you caught that it hadn't executed.

duplada

I didn't know that the retry feature did multiple 5 minute retries? Are the parsing errors below due to actual null values being returned by the GE API as previously, or is it down to the Internet Outage that has affected the GE servers, and WW just can't get a reply?

admin

duplada Are the parsing errors below due to actual null values being returned by the GE API as previously,

Yep - parsing error is specifically down to invalid JSON responses. Not HTTP 502 or similar Gateway timeouts.

WindyMiller

duplada I didn't know that the retry feature did multiple 5 minute retries?

It doesn't look like 5 minute retries happen in every case though. I had this charge fail to get through. You can see the 2, 8 and 24 second retries firing off and all getting an offline response but then no 5 minute retry.

Might have been AWS issues yesterday?

KristianS

@duplada Have you, in your attempts to get any form of service from GivEnergy, tried to contact Paul L, from GivEnergy on LinkedIn? Paul was instrumental in the early testing of the dual AIO system. Just a thought

duplada

KristianS Have you, in your attempts to get any form of service from GivEnergy, tried to contact Paul L

Hi KristianS yes in fact he had a look at an issue I had identified with charging rates, "EDIT Sunday Afternoon Yesterday Afternoon" he is one of the few people that make an effort at GE, and I bet they don't appreciate him as much as they should either. Thanks for suggesting it I appreciate it. He made a few settings on the Portal that we cannot and it was fixed in a jiffy truly amazing. Similar to the support on here but remote controlled.

KevinD

duplada I saw a recent YouTube video from a trade show where Paul was being interviewed. He does seem to be a vital asset to the company, hope they don't burn him out.

https://www.youtube.com/watch?v=pY15GcypsB4&t=218s

duplada

admin Understood - Thanks

duplada

Null value parsing error reported to GE API Developer Team Again. Let's see what happens.

duplada

WindyMiller more than likely my logs have a number of timeout and Gateway Errors

duplada

KevinD I saw a recent YouTube video from a trade show where Paul was being interviewed

Yes just watched it, interesting stuff, makes me wonder how long spare parts will be available for the current technology that we all have installed, what with the rate of progress of new equipment. He is very good at his job though and a credit to the company.

duplada

@admin I hope you are well.

I found this post on the GE forum and wondered if it was related to the GE API 200 responses that you were explaining for us above.

https://community.givenergy.cloud/d/6146-api-read-setting-response-code-has-changed-in-junejuly-2025/2

duplada

Yesterday I received a reply from my GE Contact to say that our problems with Null values being returned for Dual AIO systems is receiving attention and they are working on it. So that is at least some progress to report.

Your 5 minute retry has saved me more or less every day this week. @admin Thank you so much I do appreciate your hard work, and remember my observations are ONLY in Jest. I wouldn't be here if I thought it wasn't the place to be. 😀

duplada

I had an upset with the clock change and a schedule that was about to execute, it left 42 sets of messages in the Activity Log.

It did execute and all went well, just advising rather than looking for a fix or anything.

duplada

Now having reviewed my Inverter logs and graphing I think you need to look at this for a fix see what it did to my inverter

admin

duplada Wow - that's very odd, we'll dig through the logs, thank you!

Update: Server fix now rolled out, this should not happen again.

duplada

admin Thank you

« Previous Page