Hi all.
I am spending a lot of time trying to analyse the portal’s API logs to help figure out why Octopus cant get their Intelligent Octopus Flux scheduling working property on my fairly standard Givenergy hybrid inverter solar system. Its impossible to recognise patterns in the logs easily without downloading them so I can scroll through and search them easily in a spreadsheet.
The download button works fine for restricted sets of data, eg by using the filters for errors and matching responses, but when trying a full download I always get a timeout.
I’m sure its not a network speed problem because I can see the speed is always above 50 Mbs and the same logs can be sent to me by email so its not that the file size is too big. Givenergy admit there are some bugs in the logs stuff such as the search not working, but they say that there is nothing wrong with the download function, so I don’t know where to go.
is there anyone else having the same problem and are there other ways of getting this log data into a spreadsheet on a regular basis? Note that I currently use the Chrome browser on a Windows 10 machine, though I haven’t had any problems downloading other large files using it.
Givenergy have offered to send me the logs whenever I need them, but when I need them I need them now, not when the support staff get the time to send them.
More than familiar with this problem. Had a fruitless dialogue with Givenergy about it (summation of their advice was “Apply some filters”, “You might have a WiFi issue”…
I’ve been running with IOF for about 15 months, now. I’m currently having a (very intermittent) dialogue with Octopus about what I believe to be a bug with the IOF <> Givenergy API.
Can you try & persist with the Givenergy portal Logs - try switching OFF (default is ON) the “Filter Errors” option, and let me know whether you see a lot of “Inverter Offline”, “Inverter Timeout” “There was no response from comms. Please try again”, or “Request Failed. Please try again” responses. If you do, I expect they’re exclusively as a result of either “Enable ECO Mode”, or “Battery Reserve % Limit” messages. (I think there’s a couple of other messages that may cause the issue too, but they’re not usually used by IOF.)
If “yes” to the above, try setting ECO Mode ON, via the portal. I’m guessing that a while later you’ll see an “Enable Eco Mode” message from Octopus that is successful.
Pretty sure, from messages on Facebook fora, etc., that other IOF users are experiencing exactly the same issue.