question

nickdb avatar image
nickdb asked

Node Red - Eskom se Push integration for load shedding

Attached are two flows required to integrate ESP into node red for those that want to get load shedding forecasts and then use this data to automate behaviour in response to outages.

I have not got far enough to create a flow for auto-charging/topup yet, but will get there.

You will need to sign up for an API key at: https://eskomsepush.gumroad.com/l/api?layout=profile.

This is put into the "set header to token value" node.

You will also, using postman and the instructions available at ESP or online, find your region code URL and put that into the "check forecast status node".

Thanks to Phil Gavin for the ESP flow which I have modified.

The Load shedding flow will put the following on a dashboard.


screenshot-2023-04-14-at-133739.png

You can then use the various outputs to develop whichever behaviour you require in order to automate for load shedding.

I will post mine once available.

I am sure there are more efficient ways of doing this for those more experienced, but it works.


Node-RED
3 comments
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

nickdb avatar image nickdb ♦♦ commented ·
0 Likes 0 ·
flow-esp.zip (6.4 KiB)
flow-ls.zip (5.6 KiB)
myvicrocks avatar image myvicrocks nickdb ♦♦ commented ·
Ahhh @nickdb thats boss!!! - I dont have nodered on my Cerbo yet... the UI nodes in the flow is that the Victron nodes from the large image?
0 Likes 0 ·
nickdb avatar image nickdb ♦♦ myvicrocks commented ·
Several additional nodes will need to be added, such as moment, the ui (dashboard) nodes etc. I will compile a list.
1 Like 1 ·
4 Answers
Dirk-Jan Faber (Victron Energy) avatar image
Dirk-Jan Faber (Victron Energy) answered ·

I had not seen this post before, and I made https://flows.nodered.org/node/node-red-contrib-eskomsepush to easily connect the EskomSePush load-shedding API with setting the MinSOC.

5 comments
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

nickdb avatar image nickdb ♦♦ commented ·
Thanks. Somewhat more sophisticated than mine.
0 Likes 0 ·
andybrink avatar image andybrink commented ·
Hi Dirk-Jan,

there seems to be an issue with the node when there is no loadshedding which causes the query credits to be consumed too fast. Is there any chance that you have a look into this?

Thanks a lot!

0 Likes 0 ·
nickdb avatar image nickdb ♦♦ andybrink commented ·
Have you checked you are on the latest version of the node?
0 Likes 0 ·
andybrink avatar image andybrink nickdb ♦♦ commented ·

I recently updated to the latest version of the node (Version: 0.0.12) but it still seems to have the same issue.

0 Likes 0 ·
Dirk-Jan Faber (Victron Energy) avatar image Dirk-Jan Faber (Victron Energy) ♦♦ andybrink commented ·

If you check "Verbose: add extra logging when running", you might get some extra info that can help debug the cause in the debug tab.

Simple things to check:
- make sure that your GX device is set to the correct timezone
- make sure that the key is only used once

0 Likes 0 ·
andybrink avatar image
andybrink answered ·

Hi all,

as anyone experienced issues with the ESP API in the past 3 days? I understood that there were various issues with the Victron backend.

I am using the Node developed by Dirk-Jan (link above) but it seems that the quota is consumed already and I could not trace back why.

Thank you for any hints!

3 comments
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

nickdb avatar image nickdb ♦♦ commented ·
If you search it uses a lot of your available queries.

Haven't seen any myself and the node is independent of VRM so that shouldn't affect anything.

0 Likes 0 ·
ludwigo avatar image ludwigo nickdb ♦♦ commented ·

Hi, it seems that when loadshedding is suspended it does not see a result that can interpret and then retries until all your credits are used. Then because you have run out of credits it cannot configure your required level until the next day.

From their docs:

  • Note: An empty list means no events for that stage
0 Likes 0 ·
andybrink avatar image andybrink ludwigo commented ·
Hi all,


I do notice the same pattern and hoped that it would be resolved since Dirk-Jan updated the node ( 0.0.12 now). However, it still seems that whenever there is no loadshedding that the query credits are consumed too fast.


0 Likes 0 ·
ludwigo avatar image
ludwigo answered ·

Does anyone know how to update the ESP node to the latest version?


1 comment
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

nickdb avatar image nickdb ♦♦ commented ·
Go to manage palette and there will be an update button next to the node.
1 Like 1 ·
Dirk-Jan Faber (Victron Energy) avatar image
Dirk-Jan Faber (Victron Energy) answered ·

I have done some testing with version 0.0.12, but don't see any strange things in credit consumption rate.
1688554452213.png

I've used the flow here to graph the API calls.

If someone does encounter problems, please do report as much info as possible to help debug the cause. That includes area, screenshots and logging. And the best place to report issues is on the github site: https://github.com/dirkjanfaber/node-red-contrib-eskomsepush/issues


1688554452213.png (27.5 KiB)
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.