Octopus R&D Labs stopped sending ECO command 14th June

Has anyone else seen this:

Using Octopus R&D labs to set scheduled charge and discharge times, at the end of the timed block, the inverter was always returned to ECO mode - the Remote Control logs showed:

2023-06-13 17:00:07 You Enable Eco Mode Written Successfully false true true API - Inverter Settings
2023-06-13 17:00:06 You Enable DC Discharge Written Successfully true false false API - Inverter Settings

But from 14th June, the Enable Eco Mode true command is no longer being received and the inverter is remaining Idle rather than running in Eco and supplying the house demand.
I've tried resetting the inverter but the issue appears to be with the R&D labs.

Ryggwelter maybe your GE API key has expired?

Thanks @stevelewis. When I went to the R&D labs site to investigate a few days ago I did see that the API key had expired..but still appeared to be able to control the inverter. I regenerated and updated the key but still the issue continues.

Investigating the logs further I see that on 15 June (4pm), the Inverter received a final ECO mode off command then all ECO mode commands (on and off) stopped.
This still worked fine as when timed charge/discharge is turned off, the inverter reverts to its previous state (ECO). This is even described in the R&D Scheduler:

Attention!
These event settings will take precedence over the permanent settings set on the device’s page. Once the event is completed, the device will be set to default mode.

So all was working fine until 26th July (4pm) when the R&D labs sent an ECO Mode off command and now does this at the start of every Timed Discharge scheduled event (but not Timed Charge) and no corresponding ECO mode on command when the event finishes.
So this sounds like the issue. I have to manually re-enable ECO mode every day...end every day R&D labs turn it off.

I've notified Octopus Agile but would have thought lots of people would have this issue?

I think I had the same problem but thought I was imagining- think you have confirmed I wasn't.
Anyway I moved to HA so I can control things myself

Anyway I moved to HA so I can control things myself

That's my intention but I probably need to upgrade my RPi to 64 bit and bring HA up to date before I try to integrate the GivTCP....so a job I'm saving for winter :-)

Ryggwelter FWIW if you don't use the RPi for anything else, simply use HAOS and dedicate the hardware to your home automation. I did this (but with a Dell Wyse Terminal for the extra power) and it took me a very short time (maybe a couple of hours) to get everything installed and running, including GivTCP, DuckDNS and NGINX for remote access. I think it probably is 64bit OS but don't really care as it just works. I use HA for because it's a doddle to install and has truly splendid integrations but I use Node-RED (as an add on) for my automation logic.

Ryggwelter if you're on a normal time of use tariff (Go, IO, etc), the non-HA version of PALM might be useful ahead of your winter project www.github.com/salewis38/palm

So glad I found this thread.

I kept thinking it was me doing something wrong but did a test last night and had the same thing. No eco mode being set to on at the end of the discharge schedule.

Time to look into a HA solution then!

Has anyone reported this to octopus ? surely they would want to know.
agile@octopus.energy for r&d issues

Tim
Thanks Tim. Yes that sounds like a great route, but I do use the RPi for other stuff. It's all running in Docker containers and I'm not very experienced with it all so great for learning, but takes time :-)

positor1

I've notified Octopus Agile but would have thought lots of people would have this issue?

They have started to pick up the case and asked yesterday if I was still seeing the issue as they updated the software to better handle ECO mode 'a few weeks ago' (probably when it broke - lol!)

I notified them a while ago and then it seemed to bounce to the main Octopus help email address and then died in the maelstrom.

Ryggwelter Well, can confirm that last night it still didn't work for me on a discharge schedule I set up in the morning to run 4:30 - 6pm!