Continuing the discussion from Dynamic ESS is now available for Octopus customers in the UK:
So I’m not sure if there is any change but intelligence price slots aren’t being picked up by my system. The pricing charts never change from the default tariff. Also I’ve noticed based on this the system is pulling from the grid during peak time even with plenty of battery life.
Let me know if you would like to look at my setup?
@h2009: can you provide the site id (the number in the vrm url) of your system?
I have the same problem, not importing the dynamic Octopus prices. I know the account number and key are right because it imported the fixed rate of 23p which I was on when I first set up DESS.
https://vrm.victronenergy.com/installation/482708/dashboard
(For now I’ve entered fixed prices to get the system to work sensibly)
“Everything works” means it will pull the tariff into Victron, it won’t pull any additional cheap slots that Octopus make available on-demand when your car is plugged in. Is that what you are referring to?
For this to work Octopus would need to expose this via API (I don’t beleive they do) and Victron would have to poll API much more regularly.
It really needs to be update the active additional time slots. There must be a way to get this information as HA can get the info.
Do you know how HA gets it? Via Octopus public API or via some other means? Do you have any information you can link to?
Interesting. So this uses GraphQL completedDispatches object, which isn’t exposed via ReST interface.
So while it’s possible to pull this, it would require Victron to:
completedDispatched object regularly to detect when car is plugged in and cheap slot starts.Thinking the problem might be on the Octopus side I took a look at these API end points - REST API | API docs
Firstly I found the Account API with my account number inserted into the URL correctly identifies my tariff as Agile, i.e. E-1R-AGILE-23-12-06-D. I used my API key as both username and password to authenticate.
Then I found that inserting the returned tariff into the Price endpoint returned the correct 48 half hour agile price points. (https://api.octopus.energy/v1/products/AGILE-23-12-06/electricity-tariffs/E-1R-AGILE-23-12-06-D/standard-unit-rates/?period_from=2024-09-30T00:00Z&period_to=2024-10-01T01:29Z)
However when I switch to dynamic pricing DESS sets the price to 25p for all future. It was 23p so it’s dynamic enough to know there was a price rise.
I know it’s probably more complicated than this, but I think I have at least proved that the problem is not on the Octopus side, it is possible to access the rates with my account number and API key.
One thing I did notice was that the Account end point returns a history of my past tariffs with Octopus, there are 3, the last in the list is the correct one. The first in the list is the variable tariff and that does return 25p. See below.
“agreements”: [
{
“tariff_code”: “E-1R-VAR-22-11-01-D”,
“valid_from”: “2024-08-15T00:00:00+01:00”,
“valid_to”: “2024-09-01T00:00:00+01:00”
},
{
“tariff_code”: “E-1R-AGILE-23-12-06-D”,
“valid_from”: “2024-09-01T00:00:00+01:00”,
“valid_to”: “2024-09-01T00:00:00+01:00”
},
{
“tariff_code”: “E-1R-AGILE-23-12-06-D”,
“valid_from”: “2024-09-01T00:00:00+01:00”,
“valid_to”: “2025-09-01T00:00:00+01:00”
}
It sounds like you’re facing issues with Octopus Intelligent Go not picking up the correct pricing slots. I’d be happy to help troubleshoot your setup; could you share your configuration details or screenshots of the issue?
There might be an issue with Victron selecting the correct tarrif. However this isn’t in any way related to @h2009 original post about Victon picking up additional Octopus Intelligent slots when car is plugged it, given you are on agile tarrif. Might make sense to use a seperate thread for this.
Apologies, I misunderstood the issue described as similar to mine. I’ve created another topic. Thanks for the polite correction.